Exterior models or internal structures: scoping floor separation and equipment cutaways
List the viewing actions first, then identify which surfaces and components each action exposes. An overview may need only exteriors; floor separation and opening enclosures require the visible interior, not an unsupported reconstruction of every engineering component.
On this page5 sections
Exterior and interior are not simply detail levels
A highly detailed building exterior may contain no rooms once its slabs are hidden. A visually simple machine may nevertheless organize the exact internal components needed for an explanation. Specify visible scope, object organization and detail separately. The phrase “high-precision model” does not resolve all three requirements.
This article concerns presentation assets. An internal model without specialist source confirmation should not support construction, maintenance safety or clearance feasibility decisions. Visual similarity alone does not demonstrate that structural loads, connections or operating principles have been verified.
Let viewing actions define the asset boundary
- Viewing a building from a site overview: prioritize silhouette, entrances and location. Rooms and pipes that are never shown can be explicitly excluded.
- Inspecting one floor: make that floor independently visible and assign its slabs, walls and required facilities to the correct grouping.
- Separating several floors: consider newly exposed undersides, edges and components crossing levels, so the separated view does not reveal an unintended shell.
- Opening an equipment enclosure: confirm visible internal components, the appearance of shell thickness and occlusion. List movement-ready assets and internal geometry separately.
Add an exclusion column to each action: what does this view not need to show? This prevents a local presentation request from expanding silently into an entire building or machine's engineering construction. It also provides a clear basis for explaining later scope additions.
Organize layers for actions, not just tidy folders
Use clear names for floors, enclosures and internal assemblies. Decide whether a component crossing levels follows one floor or is split, rather than allowing it to appear twice after separation. The official Three.js Group example shows multiple objects transformed together as a group. Checked on October 6, 2026, it illustrates the relationship between organization and operation; it does not guarantee that every export format preserves an author's hierarchy.
Consequently, the sample should actually hide, separate and restore a floor in the receiving tool. Check that unrelated components do not move with it. Neatly named folders in the source application alone cannot prove that the intended application will manipulate the delivered asset correctly.
Use a sample to resolve incomplete information
Choose one floor or one machine and show three states: assembled, separated and restored. Record unsupported areas, then choose between obtaining information, approving a simplification or restricting the viewing action. Do not fill an interior with plausible-looking structures that have no confirmed basis.
Hypothetical example: separated floors are used only to explain functional areas. Approved room boundaries and principal facilities may be sufficient, while concealed services are excluded. If the purpose later changes to maintenance instruction, that scope becomes inadequate and requires additional specialist information and review responsibility. This is a scope comparison, not a claim about the company's engineering capabilities.
Accept the model by performing the agreed actions
- Check the complete exterior in overview, then confirm required content remains present when layers are separated.
- Inspect edges and exposed surfaces for unintended holes or duplicate faces introduced by the division.
- Switch between floors or components and confirm labels, ownership and shared structures remain consistent without disappearance or duplication.
- Restore the assembly and verify that positions and visibility return to the approved default.
A fixed-camera demonstration may not require every interactive state. A model that users can freely inspect must be reviewed across its permitted range. Production effort depends on exposed parts, reliability of the source information and the number of required states. “Includes an interior” is too broad to justify a universal price or delivery period.
Mark ownership of shared components on the scope diagram, especially stairs and equipment crossing floors, so separate floor packages do not duplicate the same structure.
Before requesting floor separation or interiors, establish the viewing purpose against the digital-twin use cases, then plan switching and reset with the model and UI coordination guide. A brief for 3D modeling services (Chinese) should mark visible interiors, shared elements and closed areas excluded from production. That is more precise than asking for a model to be “complete.”