Know the equipment.
Understand the connections.
A procedure names an asset. Your engineer needs to know what supplies it, what depends on it, and which information can be trusted. Start with a site model your team can inspect and validate.
One asset.
Follow what it touches.
Select equipment, switch the evidence source, and introduce a drawing revision. Connectivity and live operating state answer different questions.
UPS-B → PDU-B → Hall 02. Select a different asset to follow its documented relationship.
Make site knowledge
inspectable.
The model becomes useful when an engineer can follow the connection and challenge the information behind it.
Connect the equipment
Bring one-lines, asset lists, internal components, and alternate paths into the scope your team validates.
Keep the source close
Relate manuals, sequences of operation, drawings, aliases, and procedure references to the equipment they describe.
Keep uncertainty visible
Distinguish a documented arrangement from a field observation or a sensor reading. Give missing or conflicting information a clear owner.
Build from the information
you already have.
A focused first system gives your site experts something concrete to check.
Discuss systems and integrationsDrawings and asset data
Current one-lines and asset information establish equipment names, relationships, and the boundary of the first model.
Manuals and operating requirements
Add relevant OEM instructions, sequences of operation, existing procedures, and site rules to give the equipment practical context.
Site validation
Have the people who know the facility verify aliases, connections, and important omissions. Keep documented and observed differences visible.
Change control
Agree who supplies revisions, who validates changes, and which dependent procedures need another look when the site record changes.
A useful conversation
starts with real work.
Choose a representative task, record the baseline, and agree what a useful result must demonstrate.
Open the evaluation plannerBring to the conversation
- One current one-line and the related asset information
- Manuals or sequences for the system in scope
- A site expert who can validate names and relationships
Measure in the evaluation
- Correct equipment mapping and documented connections
- Useful handling of gaps, aliases, and revisions
- Traceability from a procedure to its site context
The questions
behind the decision.
Get the details clear before committing to a rollout.
Security and deploymentPricing and scopeIs this just a 3D visualization?
The useful foundation is the equipment and its relationships to sources and work. A visual model helps people inspect that context; it does not replace validation of the underlying equipment, connections, or operating conditions.
Do we need perfect as-built drawings first?
Start with what you have for a bounded system. Identify missing, ambiguous, or outdated information with your site team and decide what must be resolved before a particular workflow can be evaluated.
Can it handle equipment aliases and internal components?
Include those in the model scope. Test the names people use in procedures against the drawings and asset records, including internal components and alternate paths that affect the work.
Does a connection mean the equipment is energized?
No. Connectivity and operating state are separate. A drawing records an arrangement; a field check records an observation; telemetry records a measurement with a timestamp. Each must retain its provenance.
What happens when our site changes?
Agree a revision process: ingest the new information, validate the affected relationships, and identify work that may need to be reviewed again. The example shows why source changes should remain visible.
How does this help with a new acquisition or facility-manager handover?
A validated site record gives the incoming team a starting point for equipment, source documents, and open gaps. Define the handover responsibilities and the procedures that still need to be confirmed for the new operator.
Site context supports the core procedure workflows. Live states require the relevant integration, verified mapping, and timestamps.
Bring a one-line.
Let’s follow the site.
Choose one system and the work it supports. We’ll map the starting information, validation needs, and a useful first demonstration.
We’ll agree how to share them if an evaluation follows.