Menu

Standards library

Every standard and specification the project's requirements cite, whether the project holds a copy, and whether its text may be reproduced.

Demonstration project - no figure here describes a real facilityChanges are not saved
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

Standards and specifications cited (5)
ReferenceBodyTitleRequirementsHeldText
ZRF-CTR-APX-AContract
Contract Appendix A - Scope of Work
2HeldMay be quoted
ZRF-CTR-APX-DContract
Contract Appendix D - Quality and Inspection Requirements
2HeldMay be quoted
ZRF-SPC-3300Project specification
Piping Material and Pressure Testing Specification
3HeldMay be quoted
ZRF-SPC-4100Project specification
Instrumentation and Control Specification
1HeldMay be quoted
ISO 15649ISO
not held, so no title
1Cited onlyCite only

Cite only means cite only

A standard the project holds no licence for may be referenced by number and clause. Its text may not be reproduced in a deliverable, and EDS will not do it: the reference is the project’s own work, the text belongs to the standards body, and a deliverable that quotes it hands the client a copyright problem.

Precedence between them

  1. The contract and its appendices
  2. Project specifications
  3. Company standards
  4. 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.

Project documents