AI ENGINEER / PRODUCT

From P&ID to native SolidWorks assembly.

A deterministic engineering compiler that resolves approved native models from a customer-authorized PDM/model library, preserves process intent and returns a proof-carrying .sldasm—not newly imagined parts.

Concept illustration of P&ID intent becoming a directed engineering graph and an assembled equipment module
Concept illustration — MST binds approved existing component models; it does not regenerate qualified customer parts.

01 / PRODUCT CONTRACT

It assembles what your engineers already trust.

MST AI Engineer does not regenerate qualified valves, MFCs, blocks or fittings. In a configured deployment it resolves exact approved models from the customer’s authorized PDM/model-library scope—or from an approved controlled export—then converts P&ID intent into a traceable physical implementation.

  1. Recover intent from P&ID PDF

    Tags, symbols, linework, connections, flow direction, conditions and source evidence become typed observations.

  2. Build a directed engineering graph

    The graph preserves direction and conditional state instead of reducing the drawing to undirected connectivity.

  3. Bind customer PDM and geometry truth

    Authorized BOM/SAP/PDM identity, revision and lifecycle state are joined to the exact native model and its B-Rep interfaces.

  4. Solve the 3D physical realization

    Choose block, bridge, hole, plug, elbow and tube candidates; then solve XYZ position, 3D orientation, layer changes, spatial constraints and orthogonal 3D routing.

  5. Compile deterministic Assembly IR

    Create a versioned plan for parts, poses, mates, routing tasks, checks and evidence obligations.

  6. Execute and reverse-prove in SolidWorks

    Create a native .sldasm, reopen it, extract realized facts and verify each required path against the original intent.

Why PDF-to-assembly is the barrier

Reading native SolidWorks models is only one layer.

The difficult work is maintaining accountable meaning across document perception, directed topology, enterprise part identity, real interfaces, continuous 3D physical layout, SolidWorks execution and round-trip verification. Starting with an already-clean assembly skips most of that chain.

NO GUESSING

Fail closed on missing truth

Unresolved identity, interface or rule evidence blocks execution or requires explicit engineering approval.

PHYSICAL CONSEQUENCES

A routing change changes the design

Layer changes become real blocks, bridges, elbows, tubes and BOM consequences—not a line moved on screen.

REVERSE PROOF

Every required edge is accounted for

P&ID intent traces through the selected physical path to actual component, mate and face facts in SolidWorks.

02 / ASSEMBLY IR

One compiler contract.
Multiple CAD adapters.

The physical solution is represented before any CAD API is called. Assembly IR v1 separates engineering meaning from vendor-specific execution while preserving deterministic instructions and evidence obligations.

PHYSICAL RESULTcomponents + interfaces + connections + poses + evidence
UNIVERSAL ASSEMBLY COMPILERAssembly IR v1insert · pose · align · mate · fix · route · verify
CURRENT VALIDATED PATHSolidWorks Adapter
ARCHITECTURAL EXTENSIONFreeCAD Adapter
ADAPTER CONTRACTOther CAD systems

03 / VERIFIED ENGINEERING AI

AI proposes.
Engineering authority decides.

MST Engineering AI Kernel governs task orchestration, evidence, approvals, replay and regression. Learned patterns from approved historical assemblies may rank candidates or propose rules; only deterministic, versioned and approved authority may affect production compilation.

01Input identityP&ID · BOM · boundary · library · Rulepack · hashes
02Deterministic compileSame approved inputs and versions → same Assembly IR
03Real execution facts.sldasm · mates · rebuild · geometry · interfaces
04Explicit verdictAUTO_PASS · PASS_WITH_ENGINEER_REVIEW · FAIL_CLOSED · CANNOT_VERIFY

04 / VALIDATED BOUNDARY

A narrow claim is stronger than unlimited autonomy.

The current public product scope is modular semiconductor process-equipment assembly under controlled libraries, approved Rulepacks and defined engineering constraints. No engineer operates SolidWorks or intervenes during the controlled engineering process; customer authorization and production release remain outside it.

P&ID/BOM-driven assembly tasksValidated within controlled inputs
Arbitrary whole-machine autonomyNot claimed
Approved native component modelsCustomer libraries remain authoritative
Regenerating arbitrary qualified partsNot claimed
Native SolidWorks assembly executionCreated, reopened and inspected by AI
FreeCAD or universal CAD production supportArchitecture only; not claimed
Fail-closed evidence gatesPASS / FAIL / CANNOT_VERIFY
Production release without customer authorizationNot permitted

Bring a falsifiable case

Challenge the engineering boundary.

Ask for a controlled run using non-confidential inputs. We will show the assembly, the evidence and the refusal conditions.

Request a live challenge