For fire services

Whether you have the context of the incident when you get there.

You use Huvo on arrival, and see hot work in Permia from the incident commander's side, at sites running them.

The call today

  • An address
  • An alarm type

and nothing else

The call with the record under it

  • An address
  • An alarm type
  • The zone, and whether it was off
  • What work was live in it
  • A name, and a number

The fire service never pays for it

The same alarm call arriving twice, as a ringing bell above a printed slip in each of two columns. Today the slip is short: an address, an alarm type and nothing else. With the record under it the slip is long and lies on top of a ticked record sheet: the address, the alarm type, the zone and whether it was off, what work was live in it, and a name and a number to ring, and the fire service never pays for it.

You arrive knowing which zones are isolated and what work is live, at every site that runs Huvo.

You want the context yourself. With Huvo on the site, command has the zone context for the incident on arrival. The fire service never pays.

The zone layer on the record

What hot work was live, what was isolated for it and what was restored, with a name against each. Permia never enters the alarm chain.

What you need

  • If you want the site's context on arrival, you need Huvo on that site, and Huvo needs a panel.
  • If you also want the hot work on record, with a name against each step, you need Permia on that site.
  • Huvo reads the work record, so it only works where the site also runs Permia: a panel with no record behind it has nothing for Huvo to read.
  • You never need Priora, and the fire service never pays. Huvo is not priced yet; a site that wants it writes to us.

Huvo: questions from fire services

Nothing for you to buy

Book a demo as a fire service, or contact us with your questions.