CS-SRC-007 · SRC Source onboarding, ownership and retirement · 7 of 192
Replace a source without changing canonical identity
Integration Lead · Trigger: A PLC, historian, gateway or enterprise application is replaced.
Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.
Acceptance
2 of 3 steps satisfiedCanonical subject identities will remain stable and the cutover will expose any gap or overlap.
Run the remaining steps below. The result is read back from record state — nothing here is a toast.
Normal path
A source is registered, owned, approved and its custody evidence confirmed.
Step 1. Approve the source and move its lifecycle to active.
not yet satisfiedlifecycleactiveapprovalrejectedcustodyunknown
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: approval = approved, lifecycle = active
Step 2. Complete the access review that ownership depends on.
satisfiedOperates onACCE-015M. Tanaka (OT Integration Lead) → RGH OT controller A1Access record· OPTIMON-IND / Halol Packaging Line
staterevokedreviewacceptedretentioncurrent
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: review = accepted
Step 3. Verify the custody chain recorded for the source.
satisfiedOperates onEVID-019Asset/Meter-EM11 · defect_count evidence 19Evidence chain· OPTIMON-IND / Halol Packaging Line
custodyverifiedcompletenesscompletematurityproposed
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: custody = verified
Exception path
Different units, identities or missing history will block an unsupported equivalence claim.
Alternate path. Ownership cannot be evidenced: retire the source and open a downstream access review.
not yet satisfiedlifecycleactiveapprovalrejectedcustodyunknown
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: lifecycle = retired, custody = review
Workflow as specified
CoreSync will compare old and new bindings, run controlled parallel acquisition, reconcile overlap and promote the replacement under an approved cutover plan.
Evidence written in this session
Nothing run yet in this session. Record state shown above may already satisfy steps from the seeded fixture history.