Explore all industries
Browse the industries where Zixel is most often used to connect design review, change control, service delivery, and downstream enablement.
View industries
Who this is a good fit for
Technical teamsSystem integratorsCustomer-side engineersQuality engineers
Bring 3D viewing, locating, annotation reading, and interaction events directly into quality, service, or in-house platforms.
Common example situations
- 3D-linked quality inspection with PMI extraction
You may be running into these problems
If several of these sound familiar, this theme is usually worth reviewing first.
Business systems do not have native 3D capability
In quality, service, and custom-built systems, users often have to leave the workflow and jump into another tool just to look at a model.
PMI and annotation data are hard to use
Important model annotations often fail to flow back into business steps cleanly, so teams still rely on manual entry.
Linkage between business objects and models is weak
Going from a business record to the right model object — and back again — can be clumsy for both developers and end users.
What customers usually ask for
These are the requests that tend to surface early in real conversations.
We want people to preview 3D files directly in the systems they already use instead of switching tools all day.
We want PMI, annotations, and object selections to link back to business data and reduce manual checking.
We want an integration path that can start small, prove one key workflow, and then expand.
How teams usually roll this out
You do not need a massive transformation on day one. The best first step is usually the part of the workflow that is slowing people down the most.
1
Choose one high-frequency business entry point
Start with a task such as quality review, after-sales issue locating, or engineering object verification.
2
Embed 3D capability
Use SDK or API-based integration to bring model viewing, locating, and interaction into the current system.
3
Connect business objects and model objects
Map IDs, annotations, events, and model positions so the system and the model can drive each other.
4
Expand from one working use case
Once one action works smoothly, extend into more workflows, more data objects, and broader process coverage.
Recommended product mix
You can phase these in over time. Not every module has to go live on the same day.
| Module | What it does in this solution |
|---|---|
| 3D Viewer | Provides embedded viewing, core interaction, and model presentation capabilities. |
| PDM | Can be added when the project also needs permission control, version governance, and model source management. |
Deployment and integration
The right rollout depends on security requirements, the systems you already have, and how many teams need to be involved first.
Deployment options
This is usually rolled out in an SDK / API pattern and works well for custom-built platforms and industry-specific systems.
Integration path
Typical integrations include quality systems, internal platforms, file stores, permission systems, and master data services.
Best place to start
The fastest path is often the workflow with the highest PMI dependency and the most manual cross-checking today.
What teams usually see first
Every organization is different, but these are the early changes teams most often notice once the workflow is running.
Users switch systems less often, so the workflow feels shorter and cleaner.
PMI and annotation data become more usable, reducing manual entry and manual comparison.
Business objects map to the right model context faster, which speeds up issue locating.
Once the first workflow is running, the same 3D capability can be reused across more systems later.
Frequently asked questions
If you already have CAD, PLM, MES, ERP, or in-house systems in place, these questions are usually a good place to start.
Is this only for quality inspection systems?
No. It can also support after-sales service, engineering management, project delivery, and any workflow that needs 3D viewing and business linkage.
Will integration be heavy?
Most teams succeed by starting with one high-frequency action and expanding after the value is clear.
What if we also need permission control and version management?
That is where PDM can be added to manage model source, permissions, and version status more clearly.
You may also want to review these themes
If the problem you are solving touches more than one workflow, these pages often go together.
Drawing Conversion & PLM
Drawing Conversion & PLM
Standardize drawing conversion, naming, BOM-based distribution, and downstream access without disrupting the existing PLM backbone.
Multi-CAD & Large Models
Multi-CAD & Large Models
Bring models from multiple CAD systems, large-assembly review, online feedback, and version coordination into one practical workflow.
Want to see how this could fit your team?
Tell us what systems you use today, who needs access, and where the handoff is breaking down. We can help you decide the best place to start.