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.
Performance baseline
Measure triangles, vertices, nodes, materials, textures, draw calls, transfer size and representative loading behavior.
Geometry and hierarchy
Remove hidden or repeated geometry and apply LOD, instancing, batching and spatial partitions around visual error.
Materials and textures
Consolidate materials, resize and compress textures, and select formats for the target devices.
Web and 3D Tiles tuning
Tune compression, tiles, geometric error, caching and progressive loading for GLB, GLTF and 3D Tiles.
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 | BIM, CAD, DCC and reality models |
|---|---|
| Primary output | Optimized assets, LOD and streamed resources |
| Quality focus | Size, frame rate and usability |
| 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
How much can a 3D model be compressed?
There is no universal ratio. It depends on repeated geometry, hidden detail, textures, materials and acceptable visual error.
Will polygon reduction damage the appearance?
Critical silhouettes, near views and normal shading must be protected and reviewed on fixed views and target devices.
Does a small GLB always load quickly?
No. Decode cost, GPU memory, node count, material switches, texture size and request patterns also matter.
Can optimized assets still support object queries?
Yes when the required object granularity and ID mapping are defined before batching or instancing.