OptimonCoreSync Studio
IE
CS-DQ-007 · DQ Quality validation, drift and remediation · 127 of 192

Apply a time-bounded quality exception

Authorized Data Owner · Trigger: A use case proposes limited acceptance of qualified data.

Simulated fixture data. Every record, receipt and timeline entry on this screen is demonstration material. It is never production evidence.

Acceptance

1 of 3 steps satisfied

Consumers will see the qualification and the exception will cease at its declared expiry.

Run the remaining steps below. The result is read back from record state — nothing here is a toast.

Normal path

A quality failure is held, corrected under authority and reflected in consumer readiness.
Step 1. Propose the correction for the held payload.
satisfied
Operates onQUAR-009Out-of-range value · lot 9Quarantine item· OPTIMON-IND / Raigarh Melt Shop
holdingheldcorrectionproposedreleaseAuthoritypending
Moves the record and writes evidence. Permission: remediate.
Acceptance for this step: correction = proposed
Step 2. Release under authority; the original payload is retained.
not yet satisfied
Operates onQUAR-016Missing mandatory field · lot 16Quarantine item· NORTHBRIDGE-ALLOY / Sheffield Bar Mill
holdingarchivedcorrectionrejectedreleaseAuthorityblocked
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: holding = released, releaseAuthority = granted
Step 3. Re-evaluate the readiness condition the failure affected.
not yet satisfied
Operates onREAD-023OEE — input 23Readiness item· OPTIMON-IND / Halol Packaging Line
conditionmissingevidencepartialtrenddegraded
Moves the record and writes evidence. Permission: test.
Acceptance for this step: condition = satisfied, evidence = complete

Exception path

A temporary exception will not change bad data into good data or bypass safety-related hard gates.
Alternate path. The correction is not defensible: reject it and retain the evidence.
not yet satisfied
Operates onQUAR-009Out-of-range value · lot 9Quarantine item· OPTIMON-IND / Raigarh Melt Shop
holdingheldcorrectionproposedreleaseAuthoritypending
Separation of duties: Integration Engineer may not do this. Act as
Acceptance for this step: correction = rejected, holding = held

Workflow as specified

CoreSync will require explicit scope, rationale, expiry and consumer visibility, preserving the original quality condition and protected non-overridable controls.

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.