Source review
Confirm scope, accuracy, formats, coordinates and intended use.
Capabilities
Production organized around a usable result
Source data, accuracy and intended use define the workflow. These capabilities can be combined without forcing the project into a fixed package.
Operational hierarchy
Organize machines, modules, parts and interfaces so they can be selected and linked to status data.
Drawing and photo workflow
Use drawings for dimensions and structure, then photos for appearance, labels and as-built differences.
Line and piping organization
Coordinate equipment positions, connections, routes and the object granularity required by operations.
Runtime asset preparation
Create LOD, reusable materials, texture atlases and instances around viewing distance and device budgets.
Delivery Standard
Acceptance criteria before delivery
Specific values depend on the source data and target environment. Applicable criteria are agreed at the start instead of relying on vague quality labels.
| Typical input | Mechanical drawings, photos, dimensions and CAD |
|---|---|
| Primary output | Equipment models, production lines and LOD |
| Quality focus | Structure, identification and operations |
| Asset hierarchy | Objects organized by building, floor, system, equipment or component |
| Runtime fit | Optimization for the target browser, desktop or mobile environment |
| Review method | Pilot approval, milestone previews, issue list and final validation |
Workflow
Approve a pilot before batch production
A representative pilot validates source quality, accuracy, visual language, hierarchy and performance early in the project.
Pilot approval
Lock hierarchy, detail, materials and performance on a representative asset.
Batch production
Model, review and preview assets against the agreed manifest.
Final validation
Verify files, versions, hierarchy, performance and delivery notes.
FAQ
Frequently asked questions
What source data is needed for industrial equipment?
Assembly drawings, critical dimensions, multi-angle photos, an equipment list and the intended application provide the strongest start.
Does every mechanical part need to be modeled?
No. Separation should follow inspection, status, maintenance or training tasks and avoid detail with no operational value.
Can assets follow existing equipment codes?
Yes. Provide the asset register and naming rules before production so model objects align with the business system.
How are labels, cables and small details handled?
Critical labels can use textures or separate objects. Small repeated details are chosen according to viewing distance and performance.