Order from Lab EE30CF

CAD with history

Engineering CAD parts, one record per part revision, with the native parametric file and its replayable feature history, a matching STEP B-rep, per-characteristic tolerances (GD&T), material and process, and the revision chain. For a subset, the build record (made or not, good and scrapped quantities) and characteristic-level inspection results (measured value, pass or fail, disposition), with commercial training rights from a seller who is the design authority.

How answering works

Any number of people fill one order. The lab receives one dataset, in its own columns.

Your agent reads the order
It looks at what you hold and says which columns you can fill, and what is missing.
Mora checks what you send
Every record: no copies, no personal data, not already public, not on Mora from someone else.
The lab pays per record it accepts
The lab named the price. You fill as much of the order as you can.

The columns the lab wants

You do not need every column. Mora says which ones each dataset fills.

Column Type What it must hold

native_file file (SLDPRT, NX/Creo .prt, .ipt, .f3d, The parametric model with its feature tree intact

feature_history json, ordered Each modeling step: sketch entities, constraints, dimensions, feature type, parameters, references, suppressed or not

step_file file (STEP AP242) Neutral B-rep of the same revision, used to check that the history rebuilds to the same shape

requirements json rows + drawing PDF Per characteristic: nominal, upper and lower tolerance, GD&T symbol, datums, the face it applies to; material and finish

process label CNC milling, turning, sheet metal, injection moulding, casting or additive

revision_chain rows Previous revision, change order id, date and the reason for the change

build rows Whether the part was made, when, quantity good, quantity scrapped, shop feedback

inspection rows Per characteristic and lot: measured value, pass or fail, instrument, date, disposition of non-conformances

Column	Type	What it must hold
`native_file`	file (SLDPRT, NX/Creo .prt, .ipt, .f3d,	The parametric model with its feature tree intact
`feature_history`	json, ordered	Each modeling step: sketch entities, constraints, dimensions, feature type, parameters, references, suppressed or not
`step_file`	file (STEP AP242)	Neutral B-rep of the same revision, used to check that the history rebuilds to the same shape
`requirements`	json rows + drawing PDF	Per characteristic: nominal, upper and lower tolerance, GD&T symbol, datums, the face it applies to; material and finish
`process`	label	CNC milling, turning, sheet metal, injection moulding, casting or additive
`revision_chain`	rows	Previous revision, change order id, date and the reason for the change
`build`	rows	Whether the part was made, when, quantity good, quantity scrapped, shop feedback
`inspection`	rows	Per characteristic and lot: measured value, pass or fail, instrument, date, disposition of non-conformances

How much, in the lab's words

250,000 distinct parts with a feature history that replays; 50,000 of them with a build record; 10,000 with characteristic-level inspection (about 300,000 measured characteristics); plus a held-out test set of 2,000 parts from a different company. Counted in distinct part designs, not files, revisio

geometry
history
requirements
revisions
manufacturing
inspection