Deliverables

Every deliverable on the project, its state, and what stands between it and the next one.

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

Why

Blockers are assembled from the project's gaps, comments and role assignments each time the page renders.

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

Deliverables

Draft

In check or review

Approved

With an open gap

Deliverables (8)
Number	Title	Type	Discipline	Rev	State	What is in the way
ZRF-CMP-0007	Commissioning Procedure - Cooling Water System 31	COP	COM	A	in check	open gap: Commissioning sequence: the system boundary for SYS-31-01 is in dispute	Open
ZRF-ETR-0004	Electrical Test Report - Utilities MCC	ETR	ELE	A	draft	open gap: Insulation test basis: the test voltage has not been confirmed	Open
ZRF-HTP-0015	Hydrotest Procedure - Condensate Export System 12	HTP	PIP	B	in review	open gap: Approved test pressure basis: the design pressure of P-1201A is in conflict between the datasheet and the line list	Open
ZRF-ITP-0003	Inspection and Test Plan - Piping Fabrication	ITP	QUA	A	approved	Nothing	Open
ZRF-ITP-0008	Inspection and Test Plan - Condensate Export Piping Supports	ITP	QUA	A	in review	Ready for the next step	Open
ZRF-LCR-0021	Loop Check Record - PIC-1201	LCR	INS	A	draft	open gap: Functional test criteria: the control narrative has not been issued	Open
ZRF-PEP-0001	Project Execution Plan	PEP	PMG	C1	issued	open gap: Client document numbering requirements: Appendix F has not been received	Open
ZRF-PEP-0001-RA	Project Execution Plan	PEP	PMG	A	superseded	Ready for the next step	Open

ZRF-CMP-0007

Commissioning Procedure - Cooling Water System 31

This can be drafted and cannot be approved

open gap: Commissioning sequence: the system boundary for SYS-31-01 is in dispute
open blocking comment: The system boundary for SYS-31-01 is taken from the drawn boundary on ZRF-PID-3101. The commissioning breakdown disagrees about HV-3101.

Drafting and approving are deliberately separate. A procedure can be written around a missing datasheet so the rest of it can be reviewed; it cannot be issued until the datasheet arrives.

Where it is

State: in check
Revision: A
Type: COP
Discipline: COM
Issued: not issued

Who holds it

Author: J. Novak
Checker: S. Lindqvist
Reviewer: none assigned
Approver: none assigned

The author may not be the checker or the approver.

Review comments

1 blocking1 open1 in all

CMT-0004blocking · open
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 or close a comment

A blocking comment stops approval until somebody closes it. The person who raised it closes it; whoever answered it may not.

Approval history

No approval decision has been recorded.

Every decision with who made it and when. An approval nobody can attribute is not an approval.

What it rests on

ZRF-PID-3101P&ID - Cooling Water Circulation (mixed)
ZRF-REG-LL-001Piping Line List

A deliverable is only as good as the documents behind it. Where one is superseded, the deliverable is drafted against a revision that no longer governs.

What it has to satisfy

REQ-A-021mandatory

Gaps in the draft

Commissioning sequence: the system boundary for SYS-31-01 is in dispute

An input the checklist could not satisfy. The draft is written around it rather than pretending it is answered.

Open the workspace

Approve

2 things stand in the way, listed above. Each has to be closed by somebody before this can be approved.

Generate the issue file

A controlled file is generated from an approved revision. Generating one from a draft would put a document in somebody's hands with an approval block nobody signed.