Menu

ZRF-CMP-0007 validation

Every gate between this deliverable and issue, with what would have to happen for each failure.

Demonstration project - no figure here describes a real facilityChanges are not saved
Why

Each gate is evaluated against the project's own records when the page renders.

Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.

Gates

8

Passed

4

Failed

4

Blocking issue

3

This deliverable cannot be issued

3 gates fail. A validation page that reported a score would let somebody read “eight of ten passed” as nearly ready, when one of the two failures is a safety-critical value two documents disagree about.

Gates

Validation gates
GateOutcomeWhat was foundWhat would fix it
Required inputs presentFailCommissioning sequence: the system boundary for SYS-31-01 is in disputeobtain the missing input, or record a deviation
Source documents readablePassevery source document has been read—
Requirements acceptedPassevery attached requirement has been accepted—
No open blocking commentFail2: The system boundary for SYS-31-01 is taken from the drawn boundary on ZRF-PID-3101. The commissioning breakdown disagrees about HV-3101.answer the comment; only the reviewer who raised it may close it
Independent check assignedPasschecked by S. Lindqvist—
Approver is not the authorPassno approver assigned yet—
No safety-critical value in conflictFailP-1201A, PT-1201, HV-3101, 12-CD-1201-150-A1A in conflictdecide which document governs on the reconciliation page
Template conformanceCannot be checkedno client template has been supplied, so conformance cannot be checkedobtain the client's controlled template
A gate nobody can check

Template conformance is reported as not checkable rather than as passing. No client template has been supplied, so there is nothing to conform to - and a gate that passes because the check was skipped is worse than one that fails, because it appears in the record as evidence.