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 manually keyed job number. The rich data — the actual geometry, the spools, the connections, the quantities that already exist in the file — never becomes the operating system of the shop.

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 external. Integration became a feature request instead of a foundation. So every shop ends up with the same workaround culture: export, import, clean up, re-key, hope the revision matches.

That is not a training problem. It is an architecture problem. When the platform was never built to ingest and operate on the native files of the industry, the data can never become utilitarian. It remains archival.

ArciFab was not designed as a fixed product with a long list of optional add-ons. It was designed as a modular operating system for the shop. That single decision is why everything else becomes straightforward.

Adding a new user is not a seat negotiation that touches five systems. Adding a new job does not require a separate setup in the ERP, the scheduling tool, and the QA module. Bringing in drawings and native data — MAJs, DWGs, STEP files — is not an afterthought export/import dance. It is part of how the platform is structured. Machine integration is not a custom project that takes six months and a consultant. It is another module that sits on the same foundation.

Because the architecture is modular, the data does not have to be forced into a rigid shape that was decided years ago by a product manager who never ran a shop. The files can stay rich. The geometry, the spools, the quantities, the connections — they become live inputs instead of static references. That is the difference between a system that stores VDC data and a system that runs on it.

The difference is measurable in the hours that stop disappearing into translation and reconciliation. It shows up in fewer missed revisions, faster machine starts, and a floor that can finally trust the system because the system is finally reading the same files the shop already produces.