Standards library
Every standard and specification the project's requirements cite, whether the project holds a copy, and whether its text may be reproduced.
Why
The library is built from what the requirements actually cite, so it cannot drift from what the project relies on.
Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.
Documents cited
5
Held by the project
4
Cited and not held
1
Text may be reproduced
4
| Reference | Body | Title | Requirements | Held | Text |
|---|---|---|---|---|---|
| ZRF-CTR-APX-A | Contract | Contract Appendix A - Scope of Work | 2 | Held | May be quoted |
| ZRF-CTR-APX-D | Contract | Contract Appendix D - Quality and Inspection Requirements | 2 | Held | May be quoted |
| ZRF-SPC-3300 | Project specification | Piping Material and Pressure Testing Specification | 3 | Held | May be quoted |
| ZRF-SPC-4100 | Project specification | Instrumentation and Control Specification | 1 | Held | May be quoted |
| ISO 15649 | ISO | not held, so no title | 1 | Cited only | Cite only |
Cite only means cite only
Precedence between them
- The contract and its appendices
- Project specifications
- Company standards
- International standards
Usually - the order is itself a term of the contract. Why
Cited and not held
A requirement citing a standard the project has no copy of is still a requirement - somebody wrote it down - and nobody can check it against the clause it claims to come from. That is a procurement question, not a data defect.