Skip to content
ERMS
Sign in

Contact

Call or email. That's the whole process.

Mike Ryan handles demonstrations, evaluations and contracting. Support runs year-round and escalation reaches the engineers who build ERMS. A message from night dispatch sometimes gets answered before morning, and agencies tell us they had expected to wait until the next day.

Mike Ryan, Director of Partnerships

Grizzly Systems LLC, Irvine, California.

What to ask for

See your own agency in it before you decide anything.

We stand up your agency's own resources, team types and qualification records. Not a sample dataset. You will see your own people and apparatus as your system of record actually holds them, which is regularly where an agency finds something it did not know was there. Nothing to install and nothing to commit to. If you would rather watch a coalition already running, the Orange County deployment is worth these four things:

  • Daily availability discipline
    How status stays accurate between incidents.
  • A live resource order from posting through fill or UTF
    Including the IROC Resource Order Form attached to the thread.
  • Strike team assembly across OES and non-OES rotations
    Filled position by position, with approval state.
  • The audit trail of a completed deployment
    Who changed what, when, and from where.
  • An agency withdrawing its own resource availability
    No support request, no action required by anyone else. It falls out of how ownership is modeled.
Already using ERMS

Sign in.

Agencies with an ERMS account sign in at erms.app. This site is for people evaluating the platform; the production application is unchanged.