About Modular OS, software built for volumetric modular plants
Modular OS is an operating suite for the people who sell, design, build, certify, ship and bill modules. It is designed around how volumetric modular plants actually run, not a generic MES forced onto a factory floor.
Why does modular construction need its own software?
Modular construction moves most of the build indoors, away from weather and site delays. But once a project leaves the sales meeting, the tooling falls back to spreadsheets, binders and group chats: one place for the quote, another for drawings, paper travelers on the floor and a separate sheet for invoices.
Most production software assumes a continuous line of identical units. A modular plant builds projects. Each module has its own drawings, checks, labels, truck and set date, and the money follows events like design lock and delivery, not units shipped.
Modular OS keeps one record per module and per project across that whole path. The first market is small and mid-size wood-frame residential plants in Canada on the CSA A277 path, starting in Ontario; US plants can use it too.
Which ideas shape the product?
The floor is the source of truth.
Checks are signed where the work happens, by the person who did it, with the time. Records are not reconstructed after the fact.
Gates beat reminders.
A module cannot be released before design lock and cannot pass a hold point that has not been signed. Rules that matter are enforced, not suggested.
Be honest about what software can do.
Modular OS keeps records for the certification workflow; it does not certify. Default stations, checklists and payment schedules are starting points you edit.
One database, or it is not a suite.
Sales, design, production, shipping, billing and materials describe the same modules. Every handoff reads the same records.
Follow one module through the whole record.
Open the read-only demo now, or book a working session.