Documents
Control
Document Control
Documents linked to tags, systems, and subsystems — document tracking is the work type inside this pack.
Completions document control is “the right revision on the right tag”. The documents register holds files and revision history. Entity references pin a revision to tags, hierarchies, activities, and procedures. The viewer opens the drawing with scrape overlays when that extract exists.
Prep brings drawings and metadata in. Template Builder binds printable ITR layouts. This is not transmittals, distribution lists, or a collaborator EDMS. Handover PDF packs are not generated here. It is the completions-side register that sits next to whatever DMS the project already bought.
The drawing sits on the tag
If the P&ID is only in the DMS, the ITR assignee will not open it. If the revision is referenced on the tag, they will. That link, plus scrape overlays, is the document-control story that belongs in completions.
What it does
- ✓Maintain a project document register with revision history
- ✓Link document revisions to equipment tags and system or subsystem hierarchies
- ✓Import drawing sets and metadata through Prep scrape and spreadsheet import
- ✓View linked drawings from tag and activity panels without leaving the app
- ✓Open scrape overlays on revisions that have extract data
- ✓Build printable procedure templates bound to document layouts
- ✓See procedure coverage across hierarchy nodes in Procedure Hub
- ✓Filter documents by labels, type, and dates; export via Data Hub
- ✓Attach controlled revisions to activities for traceability
- ✓Document tracking activities chase receipts and outstanding packs from the same model
Highlights
- • Revision-pinning on references — activities point at a specific revision
- • Complements a customer DMS rather than replacing it
- • No transmittal workflow or handover-pack zip in this solution
- • Quota metering applies to stored files
Demo
Demo video coming soon
See the rest of the platform, or talk to us about a demo.