Your VDC files are still just files.

Walk into any mid-to-large fab shop and you’ll find the same pattern. Design hands over a MAJ or a coordinated model. Detailing produces DWGs. Someone exports STEP files for the machines or for the next trade. Then the production system gets a PDF, a CSV, or a job number somebody typed in by hand. The real data never makes it into the system that runs the shop: the geometry, the spools, the connections, the quantities that are already sitting in the file.

Current platforms treat these files as attachments or reference documents. You can upload them. You can link them. You can version them. What you almost never get is a system that reads the structure of a MAJ, understands the geometry in a STEP, or keeps the DWG tied to the live status of every piece on the floor. The file stays a file. The work still happens somewhere else.

That gap is expensive. It shows up as double entry, as “I thought the model had the latest revision,” as machines waiting on someone to translate data that already existed, and as managers spending nights reconciling what the software thinks is happening with what the shop is actually producing.

These systems were built around jobs, seats, and modules that get sold separately. The file formats that actually describe the work (MAJ for MagiCAD-heavy shops, native DWGs, STEP for fabrication and machine control) were treated as outside the system. Reading them became a feature request instead of the foundation. So every shop ends up with the same routine: export, import, clean up, re-key, and hope the revision on the table matches the one in the model.

You can’t train your way out of it. The software was built that way. A platform that was never built to read the industry’s native files can only store them, so the data sits in an archive while the shop runs on printouts.

We didn’t design ARCIFAB as a fixed product with a long list of add-ons. We designed it as a set of modules that share one foundation. That one decision is why the rest of this works.

Adding a user doesn’t mean a seat negotiation across five systems. Adding a job doesn’t mean separate setup in the ERP, the scheduling tool, and the QA module. Bringing in MAJs, DWGs, STEP files, and CSVs is part of how the platform is built, without the export-and-import routine. Machine integration is another module on the same foundation, without a six-month custom project and a consultant.

Because the modules share a foundation, the data doesn’t get forced into a shape decided years ago by a product manager who never ran a shop. The geometry, the spools, the quantities, and the connections stay in the file and become live inputs to the work. That’s the difference between a system that stores VDC data and one that runs on it.

You can measure the difference in hours: the hours that stop going to re-keying and reconciling. It shows up as fewer missed revisions, faster machine starts, and a floor that trusts the system because the system is reading the same files the shop already produces.