Products

Tocsia

Every building’s alarms in one place. Each alarm opens with what the equipment read when it raised, what Detect found on that unit, and suggested checks for where to start. Acknowledge it in Tocsia and the building’s server has it within seconds.

Every building

One list, not a flood.

Alarms from each of your buildings arrive in one list, each with what happened in plain words: the reading, the limit and how long it has been in alarm. Repeats of the same alarm fold into one line per point.

  • What is open now, what was raised in the last day, and the typical time in alarm, at the top
  • Points that alarm every day are counted and can be set aside, so a nuisance alarm does not bury a new one
  • The last day, week or month, for one building or all of them
Tocsia · Alarms · All buildingsExample
2Open nowstill in alarm
4Raised in the last 24 hoursabout 5 a day
1Points alarming every dayof 9 points
14 minTypical time in alarmmedian
PointStateWhat happened
AHU-41 Return CO2Tower A · raised 6:12 AM · in alarm 2 h 9 minIn alarmHigh: 1,020 ppm, limit 1,000
Chiller 1 Leaving waterCentral plant · raised 7:55 AM · in alarm 26 minIn alarmHigh: 48.6 °F, limit 46.0 °F
VAV-3-07 Zone temperatureTower B · raised 5:40 AM · in alarm 2 h 41 minAcknowledgedHigh: 79.4 °F, limit 78.0 °F
Boiler 2 Supply waterCentral plant · raised 4:18 AM · in alarm 35 minClearedLow: 138 °F, limit 140 °F

Repeats of one alarm fold into one line per point. A point that alarms every day is counted, and can be set aside so it does not bury a new one.

Tocsia · AHU-41 Return CO2Example
In alarmTower A · raised 6:12 AM · High: 1,020 ppm, limit 1,000
6001,0001,4005:005:306:006:30

Where to start

Fan status reads off, so this sensor may be reading still air, not the rooms. If the fan is also commanded on, that points to a stopped fan or a bad status input: compare it with duct static.

What Detect found on AHU-41

Supply fan (critical, first seen 6:05 AM): commanded on, not proven.

The rest of AHU-41, what moved most first

Point30 min beforeWhen it raised
Duct static1.46 in. wc0.04 in. wc
Supply fan statusOnOff
Discharge air55.2 °F61.7 °F
Supply fan commandOnOn

When it raised

Every alarm opens with what was going on.

An alarm says one point crossed a limit. The first question is what else was happening, so the building records the rest of the unit at the moment the alarm raises, and Tocsia shows it on the alarm’s page.

  • The point, against its limit. The reading that raised the alarm and the point’s trend around it, with the limit drawn in.
  • The rest of the equipment, then. What every other recorded point on the unit read when the alarm raised, with what moved most in the half hour before at the top.
  • What Detect found. Where Detect watches the unit, each of its findings at that moment and when it was first seen.

Where to start

Suggested checks that fit the readings.

Tocsia reads the alarm against the readings around it and suggests where to look first. A CO2 alarm on a unit whose fan reads off points to a stopped fan or a bad status input before it points to the rooms.

The suggestions come from a fixed set of rules for each kind of measurement, and they are labeled as suggestions. Your team confirms and acts.

With Detect

The fault behind the alarm, already named.

Where Detect watches the unit, the alarm’s page shows what it found there at that moment: each finding, its severity and when it was first seen. The alarm says what crossed a limit; Detect says what the equipment is doing wrong.

Noisy points

The alarms nobody fixes, in plain sight.

The timeline shows every point’s alarms over the last week, month or quarter, one row per point. A point that alarms every working morning shows as one bright stripe, and that is usually a limit set too tight or a fault nobody has chased.

  • A point that alarms about every day says so on its alarm’s page: its limit or delay is set too tight, or the equipment has a problem nobody has fixed
  • A flood, more than ten alarms in ten minutes, is called out
  • Alarms by day of the week and hour of the day, so a pattern that follows a schedule shows
  • A page per building: what is open, the last thirty days, and the points that alarm most
Tocsia · Timeline · Tower AExample

186 alarms on 5 points · No floods

  • AHU-41Return CO2141
  • Supply fan status2
  • VAV-3-07Zone temperature17
  • Chiller 1Leaving water24
  • Boiler 2Supply water2

Each cell is six hours; the stronger the color, the more alarms started in it. A point that alarms every working morning shows as one bright stripe.

Tocsia · AHU-41 Return CO2Example

Sets this alarm aside until the time you choose. A new alarm on the same point still comes to the inbox.

Reason

New fan belt arrives tomorrow morning

In Tocsia

  1. NoteSupply fan belt slipping. Tensioned it; a new belt is on order.j.rivera@example.com · 7:05 AM
  2. Acknowledgment sent to the siteOn it.j.rivera@example.com · 6:20 AM

Acknowledge, shelve, note

Acknowledge it once, and the building has it.

Nothing here changes how equipment runs. An acknowledgment marks the alarm on the building’s own server and travels over the connection the building already keeps open to our cloud. Nothing is opened inbound.

  • Acknowledge. The acknowledgment reaches the building’s server within seconds and is recorded there, as one made on site would be.
  • Shelve. Set one alarm aside until a time you choose, with a reason everyone sees, while a repair is booked. A new alarm on the same point still comes through.
  • Add a note. What was found and what was done stays with the alarm for the next shift.
  • See who did what. Each of these is kept on the alarm, with who did it and when.

Alarm emails

The email says what happened.

An alarm email names the point, its reading against the limit, and what the rest of the equipment read when the alarm came in. Where a building turns it on, the email links straight to the alarm’s page. The people who need to know are told; nobody has to keep the portal open to find out.

Who sees what

Each person sees their buildings.

People see only the buildings they have been given, from one building to a whole portfolio. Tocsia is turned on building by building, and one sign-in covers Tocsia and Tessiq, where the building’s dashboards are.

InboxExample

One set of checks, four ways to act on them

Detect finds it. Tocsia flags it. Tessiq shows it. Insight explains it.

  • Detect

    Is each piece of equipment doing what it should?

  • Tocsia

    What needs attention now, and where do I start?

  • Tessiq

    What is the building doing now, and what has it been doing?

  • Insight

    What happened, why, and what should we do about it?

What would Smart Tenants find in your building?

Tell us about your building systems and we will show you what a morning briefing would say.