One bad test change can stop a production line. This supplier made that impossible.

An engineer edits a test sequence, hardware parameter, or model/variant directly in the portal — there's no separate change-request form to fill out first. Read-only (Level 3) users can view but can't touch production data.

The edit doesn't go live. It's automatically wrapped in a ticket carrying the real before-and-after diff, routed to the right approval group, and visible on the live dashboard the moment it's created — no manual step, nothing hidden.

Cross-functional reviewers see the exact diff and have roughly 20 minutes to approve or reject it. Miss the SLA and the ticket auto-delegates to the next eligible approver — a change never just sits in someone's inbox.

A second group reviews the same ticket under the same time-boxed rules. Every acknowledgment, decision, and any SLA breach or delegation is written to the audit trail as it happens.

Once approved, the change is shown against the current live version — the real data diff, not a text description of it — so an approver's final sign-off is based on exactly what will change.

The last gate before release: an offline mobile authenticator (built in Flutter) generates a 6-digit code tied to the approver's identity — built for plant floors where reliable internet can't be assumed.

The change goes live as a new version — prior versions are retained, never overwritten — with the complete record of who edited, who approved, any SLA breaches, and the RSA authorization event, ready for a functional-safety audit.