Skip to main content

COMMAND//hub

In development

COMMAND//hub is the command view of connected equipment and apparatus. The product name is COMMAND//hub. If you searched for FLEET//command, this is the page.

It is the Command layer in Equipment → Gateway → Cloud → Command. It does not replace radio or the officer on the ground.

See the deployment, not the data. The aim is awareness — what is on scene, what needs attention — not a wall of live readings.

Until it ships, day-to-day support stays in the PRO//connect app. Submit a ticket if you need help.

Purpose​

Command needs a picture of the assignment, not a second workstation of charts. COMMAND//hub is intended to summarize what equipment and vehicles are doing so people can decide, then look closer only when they choose.

Wildland and long assignments​

On a long or spread-out assignment, more signals can make the picture worse. COMMAND//hub is intended to keep awareness useful: fewer raw streams, more “what changed” and “what needs a look.” It is not meant to replace the radio or the officer on the ground.

Radio and status​

Radio stays the voice path. Status that can travel alongside radio — unit up, unit down, needs attention — may reduce some back-and-forth. That benefit is intended. It is not a claim that radio traffic goes away.

Proactive awareness​

COMMAND//hub may highlight exceptions (a unit that stopped reporting, a state that needs a check). Treat those as awareness, not as automated command. Language here is intended and may change as the product is built.

Fleet view and incident view​

Two views are planned:

  • Fleet — apparatus and equipment you own, between calls.
  • Incident — what is assigned to this event.

Neither view is released. Labels below are the intended split, not a live screen.

How the interface should behave​

The intended order is:

  1. Aggregate what is on the assignment.
  2. Summarize in language a person can scan.
  3. Alert by exception, not by every reading.
  4. Open detail on demand.

No dashboards or sample screens are published here.

What founding partners could contribute​

RAMFAN, Kraken Power, and NOMAD are examples of equipment families that could contribute identity, status, or support context to this picture. That is not a claim that every field is deployed today.

Manufacturers and integrators: see the Partner Program.