CS-SRC-001 · SRC Source onboarding, ownership and retirement · 1 of 192
Register an enterprise or plant source
Integration Lead · Trigger: A new system must contribute data.
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 satisfiedA registered source will have an owner, unique scoped identity, explicit permissions and traceable approval.
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.
satisfiedlifecycleactiveapprovalapprovedcustodyverified
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-009A. Kulkarni (Integration Engineer) → RGH Document library E17Access record· OPTIMON-IND / Raigarh Melt Shop
stategrantedreviewacceptedretentioncurrent
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.
not yet satisfiedOperates onEVID-016Asset/Furnace-1 · temperature evidence 16Evidence chain· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
custodyunknowncompletenessmissingmaturityconformant
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: custody = verified
Exception path
Duplicate registrations or an absent accountable owner will require resolution before activation.
Alternate path. Ownership cannot be evidenced: retire the source and open a downstream access review.
not yet satisfiedlifecycleactiveapprovalapprovedcustodyverified
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: lifecycle = retired, custody = review
Workflow as specified
CoreSync will capture the source owner, purpose, tenant/site scope, supported acquisition interfaces, data classifications and permitted uses, then create a stable source record independent of its current address.
Evidence written in this session
Nothing run yet in this session. Record state shown above may already satisfy steps from the seeded fixture history.
Journeys that include it
Not part of a composite journey; exercised through its family views.