ZEMERC Reference LNG and Utilities Facility
ZRF-LNG-2026 for Reference Gas Operating Company, under contract CTR-ZRF-2026-001. Detailed design.
Why
Every panel is computed from the project's own documents, registers, requirements and deliverables.
Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.
Documents
25
Read
22
3 not read
Asset records
50
Verified
1
by a person
Blocking findings
10
What the project holds
By document class.
| Class | Documents | Read |
|---|---|---|
| contract_appendix | 3 | 2 |
| datasheet | 3 | 3 |
| pfd | 2 | 2 |
| pid | 6 | 5 |
| cable_schedule | 1 | 1 |
| equipment_list | 1 | 1 |
| instrument_index | 1 | 1 |
| line_list | 1 | 1 |
| schedule | 2 | 2 |
| valve_register | 1 | 1 |
| single_line_diagram | 1 | 1 |
| specification | 2 | 2 |
| vendor_manual | 1 | 0 |
What has been read out of them
Per register, with how much of it a person has checked.
| Register | Records | Verified | In conflict |
|---|---|---|---|
| equipment | 17 | 1 | 1 |
| line | 8 | none | 1 |
| valve | 9 | none | 1 |
| instrument | 13 | none | 1 |
| cable | 3 | none | 0 |
Extraction quality
Per reading method, never averaged: OCR at 0.6 and a text layer at 0.8 are two different kinds of uncertainty.
Ceilings, not measurements. Why
What disagrees
Everything the system refused to resolve on its own.
- Conflicting attributes2
- Ambiguous readings1
- Drawn, in no register1
- Registered, never drawn1
- Boundary disagreements2
- Supersession candidates1
- Missing sheets7
- Unreadable1
Hierarchies
Several over the same assets, deliberately not merged.
| Hierarchy | Nodes |
|---|---|
| physical | 11 |
| system | 5 |
| test_pack | 2 |
| handover | 2 |
A pack that spans two units is ordinary. Why
Requirements and deliverables
- Requirements extracted
- 9
- Mandatory
- 8
- Suggested by the model, unverified
- 1
- In conflict with each other
- 1
- Deliverables
- 8
- Approved
- 1
- With an open gap
- 5
Safety-critical records nobody has checked