Every building problem becomes a coordination problem.
Mono connects the fault, the parts, the people and the next decision.
Simulation with synthetic data. A fictional hospital, people and vendors.
No patient data. No real-world purchases or vendor contact.
Watch the fault become a plan—and a request for human approval.
Product film · 16-second excerpt · synthetic demonstration
An operations layer, not another dashboard
Air handlers, chillers, boilers and utility systems.
One place to follow the fault and coordinate the response.
In a synthetic hospital, a facilities operator asks Mono about operating-room humidity. The workspace connects the question to AHU-07, its readings and work history.
A rising humidity chart and an activity record show the reported fault, diagnostics, technician availability and vendor responses. These are illustrative simulation records.
The scene moves through equipment dependencies, a proposed work order and an above-limit spending request. A person reviews the request; Mono does not approve its own spending or close the work order.
The coordination work, handled
A reading crosses its limit. Mono links the signal to the equipment.
Intake opens the work order. Diagnostics reads the equipment history and sensor readings before the plan moves forward.
A work order carries the equipment, source conversation and reported symptom together. Diagnostics reads the history and readings instead of filling in missing facts.
Planner + Sourcing · illustrative workflow
Planner coordinates people and time. Sourcing checks stock, vendor conversations and the approval needed for spending.
Technician availability, stock, vendor conversations and schedule constraints shape the plan. Life-safety and regulatory blocks stay protected.
Database policies enforce the configured limits. Mono requests approval above those limits; people approve spending and close work.
Above-limit spending becomes an approval request. Mono cannot approve that request or close the work order itself. Evidence stays attached to the decision.
Mono / working thread
A fault shouldn’t become six disconnected conversations. Mono keeps the evidence, the repair and the next decision in one thread.
Air handler / humidity alert Synthetic example
Equipment, readings and work history—together.
A proposed repair, with its dependencies attached.
People approve spending and close work orders.
People provide missing context and decide what needs attention.
Mono reports readings. People make safety and clinical judgements.
Protected life-safety and regulatory blocks never move.
Purchases in this deployment are simulated. No real vendor is contacted.
Mono cannot approve its own spending request.
People make the final decision to close a work order.
Synthetic walkthrough—not a live activity feed. Actual actions depend on the available records and the facility’s configured rules.
A connected workspace
Follow equipment, work, parts and conversations in the same facility context.
Built to be checked
Actions stay inside the facility’s rules. Spending above configured limits waits for a person. Mono cannot approve its own request.
A plan, an agent report and a verified fact are not the same thing. Evidence labels show what is known and what still needs checking.
The sensors, staff, vendors and incidents are synthetic. This is facilities operations—not patient care, clinical advice or real-world purchasing.
Before you explore
What you are looking at, what Mono can do, and what stays with people.
No. The facility, people, vendors, sensors and incidents are synthetic. There is no patient data, clinical decision-making, real-world purchasing or contact with real vendors.
No. Actions within configured limits can proceed in the simulation. Above-limit spending and restocking wait for a person. Mono cannot approve its own request, and people close work orders.
Work orders, equipment and readings, parts, schedules, conversations, people, vendors and rules share the same facility context. The workspace links open those views.
No. This page uses labelled examples to explain the workflow. The separate Mono app reads the simulation records; its activity depends on the simulation and agent runners.