Take in the signals
Schedules, transactions, work orders, sensors, cameras and outside data. Each reading comes with its confidence.
It reads the systems a business runs, and any data it can reach, and helps the operator act. We are building it first for college and university campuses.
Room 214 is booked for 40. Occupancy reads 6.
Fourth Tuesday in a row, and the air handler runs a full schedule for it.
Your rule: under a quarter full for four weeks goes to space planning.
Sent to space planning with the evidence. Setback drafted for the facilities lead to approve.
An illustration. In a deployment it runs on your systems and your rules.
A business runs on several systems, each bought to do one job. Each holds a slice of the truth. The operator ends up as the integration, and decisions get made late, on partial information, by whoever is on shift.
A dashboard tells you what happened. Signals goes on to the decision, and with your permission, the action.
Schedules, transactions, work orders, sensors, cameras and outside data. Each reading comes with its confidence.
One reading rarely means much. Several that point the same way, in context, do.
What is happening, what it is costing you, and what to do next, by your thresholds.
To the person you named, or on a standing rule you set. Every outcome is recorded and sharpens the next call.
Manual by default. Automatic where you ask for it. How it works
A campus runs class scheduling, access control, building automation, work orders and space inventory side by side. Buildings cost money whether they are used or not, and the gap between scheduled and actual use matters to space planning, energy and capital requests.
Signals also applies to venues, senior living and operators with many sites.
YYZdata was founded by Ranjit Kohli and Amrit Bains. The prototype runs at our first site, and we are signing build partners who will shape the platform with us.
About a demo, a build partnership, or anything else.