Put NX designs in front of everyone who needs them, without an NX seat on every desk.
MXTechies builds browser and mobile apps for US manufacturers that show JT and PMI data from Siemens NX, route change requests and push NX data to ERP and MES. NX is never customized.
Certified Mendix partner250+ AI certified developersUS, India and UAE
NX CADSiemens CAD
Design review
Metadata sync
Change management
3D configurator
Simulation views
Mobile access
NX is never customized. Apps use CAD-derived data — JT, PMI, metadata and BOM structure — served through Teamcenter.
Quick answer
NX CAD applications on Mendix are browser and mobile apps that work with CAD-derived data — JT, PMI, metadata and BOM structures — rather than native NX part files. They reach that data through Teamcenter, so NX is never customized. MXTechies builds design review, change and configurator apps for US manufacturers.
CAD-derived data only: JT, PMI, metadata, BOM, drawings.
Data arrives through Teamcenter, where NX product data lives.
NX is never customized, so upgrades proceed normally.
Works with NX X and on-premises NX; apps embed in Teamcenter.
Built on five Siemens Marketplace modules; first app in two to six weeks.
NX is an authoring tool. Teamcenter is where the data lives.
A Mendix app never opens a native NX part file, and doesn’t need to. Downstream users need the shape, the annotations and the structure — all of it exists in lighter derived formats.
Data layer
What the app does with it
Native NX part files
Nothing. Authoring stays in NX.
JT lightweight geometry
Rotate, section and measure in a browser.
PMI and annotations
Tolerances and notes, shown with the geometry.
Metadata and BOM structure
Search, routing, approval.
Released drawings
Served to suppliers, scoped by permission.
So the integration is to Teamcenter, not to NX. NX and Teamcenter share a common data model, so the Teamcenter Connector moves clean data rather than translating it. We build on five Siemens Marketplace modules: 3D Viewer for Teamcenter, Teamcenter Connector, Connector Toolbox, Plan For Every Part and RocketUI. Four of the five are Teamcenter modules — that is the architecture, not an accident.
Design review · Bracket-4471 rev C · JT + PMI · opened in browser, no NX seat
What the buyer seesGeometry, PMI tolerances and the released revision, in a browser tab.
What the supplier seesOnly the parts they quote, scoped by permission, never inside your CAD environment.
What engineering seesOne review thread against the model instead of a chain of screenshots.
Who needs the design, and who needs a seat
In most US manufacturers, the people who need to see a design far outnumber those who author one. NX seats are priced for authors. Everyone else gets a screenshot in an email.
Role
Needs an NX seat?
What they use instead
Design engineer
Yes — this is what NX is for.
NX, unchanged.
Manufacturing engineer
Rarely.
PMI viewer with section and measure, on the shop-floor tablet.
Buyer, quality, program manager, sales
No.
Design review app: released revision, drawings, approval thread.
Supplier
No, and not inside your CAD environment.
Supplier portal: only the parts they quote, scoped by permission.
Three of those four rows are people a Mendix app serves. That is the business case, and it beats any speed claim.
Six applications we build
Each one serves people who need the design without authoring it. The second tag names the Siemens Marketplace module it is built on.
Design review
JT geometry, PMI and 2D drawings in a browser, with markup and an approval thread against the model.
Replaces the screenshot-in-an-email loop.
Manufacturing, quality3D Viewer for Teamcenter
Metadata sync to ERP and MES
Part attributes, revisions and BOM structure pushed from Teamcenter to SAP, Oracle or Opcenter on release.
Removes the re-keying step between engineering and the plant.
Engineering ITTeamcenter Connector
Change management
ECR and ECN routed to the right reviewers with the affected geometry attached, and full traceability to the released revision.
Change boards decide from the model, not a PDF.
Change boardsConnector Toolbox
3D configurator
Self-service product configuration from Teamcenter option rules, ending in a quote and a valid BOM.
Sales configures without an engineer in the room.
SalesPlan For Every Part
Simulation dashboards
Results from Simcenter and NX CAE surfaced as pass/fail against requirements, without the analysis files behind them.
Leadership sees the answer, not the solver.
LeadershipRocketUI
Mobile access
Released product data, drawings and JT on a tablet, on the floor or at a customer site, read-only and permission-scoped.
The field sees the same revision the plant does.
Field service3D Viewer for Teamcenter
US industries we have delivered in
Each has a review or change workflow that its quality regime makes slow. That is usually where the first app goes.
Medical devicesDesign history and lifecycle record views from work items.
Aerospace and defenseEvidence packs by assurance level, coverage visible.
Automotive and EVCoverage by safety level, and impact when a requirement changes.
Pharma and biotechValidation evidence and audit trail reporting on demand.
Industrial equipmentChange control and traceability across product lines.
Software and IoTDefect trends, release readiness, coverage dashboards.
MXTechies builds the tooling that makes evidence easier to produce and check. We do not certify systems, and your quality and export-control obligations remain yours.
Delivered in automotive and EV, aerospace and defense, industrial machinery, medical devices and electronics, each under its own quality regime.
We will say when a Teamcenter configuration change solves it without an app.
A US-based engagement lead in your time zone, with delivery teams in India and the UAE for follow-the-sun build.
Frequently asked questions
What is NX CAD and Mendix integration?
Browser and mobile apps that work with NX product data without customizing NX. Authoring stays in NX; review, change workflow and data sync move to the app.
Does Mendix read native NX files?
No. Apps use derived data — JT, PMI, metadata, BOM structure — served through Teamcenter. Native part files stay in NX.
Can we view NX models in a Mendix app?
Yes. The 3D Viewer for Teamcenter module shows JT geometry with PMI, section views and measurement in a browser or on a tablet.
Do our people need an NX license to use these apps?
Authors do. Manufacturing engineers, buyers, quality, suppliers and sales generally don’t. Licensing terms are set by Siemens, so confirm with your account team — we bring the role-by-role seat count to the assessment so that conversation is short.
How does the app get the CAD data?
Through Teamcenter, using the Teamcenter Connector. Direct NX API integration is possible for specific automation, but Teamcenter is simpler to maintain.
Does it work with NX X, the cloud version?
Yes. Apps run in the browser alongside NX X or on-premises NX, and deploy to Mendix Cloud, your tenancy or on-premises.
Will this customize our NX environment?
No. Apps run outside NX through published interfaces, so the CAD environment stays standard and upgrade-safe.
How long does a first NX application take?
Two to six weeks with the Siemens Marketplace modules: week 1 assess, weeks 1–3 a working prototype on your data, weeks 3–6 build and roll out. Timeline follows product structure and user roles, not geometry.
Can this be deployed for ITAR-controlled technical data?
The apps deploy on-premises or in a US-hosted tenancy you control, so controlled technical data stays inside your environment and access is scoped by role. MXTechies does not certify ITAR compliance; the export-control obligation remains yours, and we scope engineering access on the project to match it.
Who is waiting on a screenshot today?
Name the group that keeps asking engineering for a drawing. We’ll show you what they’d see in a browser instead, using your own data, and bring the seat count so you can see the licensing math. Forty-five minutes, no prep, scheduled in US business hours.
