Use this guide when a model asset needs to become reusable in simulation, layout planning, robotics context, or external runtime handoff.
Package Flow
Prerequisites
| Requirement | Why it matters |
|---|
| Source file owner | Confirms source format, version, and permitted use. |
| Geometry reviewer | Confirms scale, orientation, origin, and component breakdown. |
| Simulation owner | Reviews physical parameters and assumptions. |
| Input | Required preparation |
|---|
| Model asset | ID, name, source file, source format, metadata, and tenant scope. |
| Version record | Source version, checksum, import date, and change reason. |
| Component geometry | Addressable parts, bounds, materials, and semantic labels. |
| Physical assumptions | Mass, collision, articulation, constraints, speed limits, and safety zones where available. |
| Validation notes | Reviewer, known simplifications, missing parameters, and approved uses. |
Procedure
- Register the model asset and source metadata.
- Create a version whenever geometry or source data changes.
- Extract or register component geometry for addressable parts.
- Add semantic labels and physical assumptions.
- Bind the package to the related unified twin object.
- Review coordinate system, units, assumptions, and intended runtime.
- Store validation notes with the package.
Expected Output
The output is a reusable asset package that connects visual geometry, semantic meaning, physical assumptions, and governed identity.
Validation Checklist
- Model asset ID, version ID, and component references are visible.
- Coordinate system, scale, units, and orientation are recorded.
- Semantic labels support the intended scenario.
- Physical assumptions and missing parameters are visible.
- Reviewer and approved use are recorded.
Failure Handling
| Symptom | Response |
|---|
| Component extraction is incomplete | Limit reuse to visual planning until required parts are modeled. |
| Units are uncertain | Do not use the package for simulation until scale is confirmed. |
| Physical parameters are missing | Record assumptions and request engineering review. |
| Runtime rejects the package | Check adapter requirements, geometry format, and semantic fields. |