Use the shared Sample to preserve the installed baseline, assess an upgrade, add immutable revisions, collect FAT/SAT evidence, and establish a verified recovery state.
What this workflow records
Use the shared Sample to preserve the installed baseline, assess an upgrade, add immutable revisions, collect FAT/SAT evidence, and establish a verified recovery state. This guide uses the real revisions records shown in AutoNexit and follows their connection to an accountable, reviewable outcome.
Prepare the project context
Before starting, identify the authorized project, the current source record, the person responsible for the next action, and the evidence needed to recognize completion. Read-only Sample projects are suitable for exploration but cannot be edited or converted into customer work.
- Open the authorized Workspace and intended Project.
- Confirm your role includes the section and action used in this workflow.
- Prepare only approved source records and evidence; never use the shared Sample for private data.
Follow the workflow
- 01
Record the existing Installed and backup baseline
- 02
Create the change request and assess operational impact
- 03
Upload new PLC and HMI revisions without replacing predecessors
- 04
Link FAT and SAT evidence to implementation
- 05
Mark installed state and verify the new recovery context
Verify the recorded outcome
The old baseline remains recoverable while the new installed and As-Built state is supported by change, test, and backup evidence. Confirm the status, timestamps, ownership, linked evidence, and downstream references before leaving the page.
| Checkpoint | What to review | Expected record |
|---|---|---|
| Record the existing Installed and backup baseline | Before starting, identify the authorized project, the current source record, the person responsible for the next action, and the evidence needed to recognize completion. Read-only Sample projects are suitable for exploration but cannot be edited or converted into customer work. | The old baseline remains recoverable while the new installed and As-Built state is supported by change, test, and backup evidence. Confirm the status, timestamps, ownership, linked evidence, and downstream references before leaving the page. |
| Mark installed state and verify the new recovery context | Overwriting the old program or closing the change before backup verification removes the rollback context a brownfield site depends on. If a permission, capacity, stale-version, or synchronization message appears, resolve that condition instead of repeating the operation or assuming it succeeded. | This is a shared Sample scenario, not a customer case study, performance claim, or instruction to modify a live controller. Keep operational authorization, safety review, manufacturer instructions, and customer acceptance in their approved processes. |
Common failure modes
Overwriting the old program or closing the change before backup verification removes the rollback context a brownfield site depends on. If a permission, capacity, stale-version, or synchronization message appears, resolve that condition instead of repeating the operation or assuming it succeeded.
Engineering and security boundary
This is a shared Sample scenario, not a customer case study, performance claim, or instruction to modify a live controller. Keep operational authorization, safety review, manufacturer instructions, and customer acceptance in their approved processes.
Frequently asked questions
When should I use “Worked example: a brownfield PLC/HMI upgrade with old and new states preserved”?
Use the shared Sample to preserve the installed baseline, assess an upgrade, add immutable revisions, collect FAT/SAT evidence, and establish a verified recovery state. This guide uses the real revisions records shown in AutoNexit and follows their connection to an accountable, reviewable outcome.
What result should “Worked example: a brownfield PLC/HMI upgrade with old and new states preserved” produce?
The old baseline remains recoverable while the new installed and As-Built state is supported by change, test, and backup evidence. Confirm the status, timestamps, ownership, linked evidence, and downstream references before leaving the page.
What should I check when “Worked example: a brownfield PLC/HMI upgrade with old and new states preserved” does not work as expected?
Overwriting the old program or closing the change before backup verification removes the rollback context a brownfield site depends on. If a permission, capacity, stale-version, or synchronization message appears, resolve that condition instead of repeating the operation or assuming it succeeded.
What does “Worked example: a brownfield PLC/HMI upgrade with old and new states preserved” deliberately not do?
This is a shared Sample scenario, not a customer case study, performance claim, or instruction to modify a live controller. Keep operational authorization, safety review, manufacturer instructions, and customer acceptance in their approved processes.