Platform Modules

One spine, ten modules

Start with what you need most and build from there. Every module reads the same estate, so nothing has to be reconciled between them.

Disconnection is the actual problem.

Most estates do not lack systems. They have a BMS, a maintenance system, a compliance folder, an energy report and a spreadsheet holding the gaps. Each is defensible on its own. Together they cannot answer a question that crosses two of them, which is nearly every question worth asking.

Vairitas is built the other way round: one asset and building spine, with modules on top of it. The asset that raised this morning's maintenance job is the same asset whose consumption you are reading, and the same asset the statutory logbook is written against. Not an integration. The same record.

01The shared record

One spine, read by everything

01Customer
02Contract
03Building
04Floor and zone
05Asset

Every module reads this same spine.

04Honesty as a feature

We say what each module does not do

Where part of a module is still being completed, the module page names the part rather than leaving you to find out. Vairitas reads plant and records operating intent, and does not command plant. You will find both statements on the module pages themselves rather than in a footnote.

MeteredModelledAwaiting

Ready to see it on your estate?

A short call, a look at what you already run, and an honest view of what the platform would find.