Template library
The controlled templates a deliverable can be produced into, and what each one requires.
Why
The document model validates before rendering. A document missing its control fields is refused rather than produced with blanks.
Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.
Templates held
1
Client templates
0
Deliverable types
4
Validation problems in the sample
0
The sample is a worked example, not this project
No client template has been supplied
Templates
| Template | Owner | Produces | Requires | |
|---|---|---|---|---|
| EDS house template | ZEMERC | DOCX and PDFDownload a sample | Document number, title, revision, issue purpose, author, and a signature block | Available |
| Client controlled template | Reference Gas Operating Company | unknown | not supplied | Not held |
What the template requires before it renders
| Field | Required | Why |
|---|---|---|
| Document number | Yes | A document without one cannot be transmitted or cited |
| Revision and issue purpose | Yes | A reader has to know which issue they hold and what it was for |
| Author | Yes | Somebody wrote it and the document says who |
| Approver | For issue only | A draft has no approver; an issued document must |
| Draft watermark | Until approved | An unapproved document that looks issued is the one most likely to be used as though it were |
A precedent from another tenant is never offered
An approved document from a similar project is the most useful thing an engineer could be given, and it is also another customer’s commercial work. EDS does not surface one across a tenant boundary - not anonymised, not as a structure, not as an example. The isolation is the product.