CS-HIS-005 · HIS Historian access and operational data federation · 39 of 192
Combine canonical historical access across providers
Data Engineer · Trigger: A use case spans plants with different historians.
Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.
Acceptance
3 of 4 steps satisfiedEquivalent test requests will retain canonical meaning without concealing provider-specific gaps.
Run the remaining steps below. The result is read back from record state — nothing here is a toast.
Normal path
Historian history is federated, with a bounded backfill planned and its evidence verified.
Step 1. Test acquisition and confirm checkpoint behaviour.
not yet satisfiedacquisitiondegradedcontractsupersededbacklogbacklogged
Moves the record and writes evidence. Permission: test.
Acceptance for this step: acquisition = healthy
Step 2. Preview the bounded impact of the history request before running it.
satisfiedOperates onRECO-009Reprocessing — RGH Relational database A25 → canonical flowRecovery plan· OPTIMON-IND / Raigarh Melt Shop
planplannedauthorityapprovedverificationverified
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: plan = planned
Step 3. Verify reconciliation against the historian's own totals.
satisfiedOperates onRECO-016Replay — NGD Vision system F18 → canonical flowRecovery plan· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
planplannedauthorityrejectedverificationverified
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: verification = verified
Step 4. Verify the custody chain for the federated history.
satisfiedOperates onEVID-023Asset/PackLine-3 · energy evidence 23Evidence chain· OPTIMON-IND / Halol Packaging Line
custodyverifiedcompletenesscompletematurityproposed
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: custody = verified
Exception path
Unsupported cross-provider equivalence or incompatible units will require explicit remediation.
Alternate path. The historian throttles or refuses the window: escalate rather than retry blindly.
satisfiedOperates onINCI-002Schema drift detected — Halol Packaging LineIncident· OPTIMON-IND / Nagda Warehouse
triagein reviewimpactblockedremediationproposed
Moves the record and writes evidence. Permission: annotate.
Acceptance for this step: impact = blocked
Workflow as specified
CoreSync will resolve canonical bindings to provider-specific requests and expose consistent quantity, time and result metadata while retaining provider distinctions.
Evidence written in this session
Nothing run yet in this session. Record state shown above may already satisfy steps from the seeded fixture history.