Field Instrument 131 · equipment data, checked at both ends
No file yet. Nothing leaves this machine: every byte is parsed in the browser.
No file yet.
An IFC model holds far more than equipment. Tick the entity types this crossing is about. Properties arrive flattened as PropertySet.Property, and the type's own properties are merged in underneath the element's own.
No file yet. The first export is the expensive one. The fourth should not be.
Three fixtures built from the shapes real projects hand you: a Revit mechanical schedule with title rows, totals and units in the cells; a CxAlloy equipment export with pipe delimited systems and contractor added kit; a COBie workbook with a missing Category; and a small IFC4 model carrying its equipment in property sets rather than columns.
Starter profiles ship for the common crossings. Save your own and carry it between projects as JSON.
Drag a field onto a destination line, or pick it from the line's own list.
Live against the first three real rows of the inbound cargo. Edit a transform above and this redraws.
Tried in order, top down, until a row finds a partner. Only the identifier key is stable across renames.
MANIFEST does not connect to Revit or to CxAlloy. It reads spreadsheets and writes spreadsheets, and it stays that way on purpose.