For hospitals, universities, airports, mine sites and councils running extended or multi-agency incidents.
AIIMS-5 aligned — not certified. No software certification scheme exists for AIIMS.Upper-market deployments — the operators who need a formal incident-management structure with AIIMS alignment, IAP/SITREP outputs and span-of-control visibility.
Extended incidents, multi-department coordination, AIIMS alignment for tender compliance.
Incidents that span multiple operational periods — surge response, mass casualty, facility evacuation — need a formal command structure and a documented audit of function-officer appointments for clinical governance review.
Large campuses, multi-agency coordination during major events, formal IAP/SITREP outputs.
Vice-Chancellor-level governance, state-agency liaisons and stakeholder comms teams all expect an Incident Action Plan and scheduled SITREPs during extended events.
Complex stakeholder ecosystem, operational period management for rolling incidents.
Airline operators, ground handlers, emergency services and airport operations all need the same SITREP at the same time. Operational-period handover briefings give that hand-off a documented, repeatable shape.
Critical infrastructure, regulator scrutiny, span-of-control matters under fatigue.
State mine-safety regulator notifications, under-fatigue incident response and multi-shift extended events benefit from the span-of-control indicator’s live warning at seven direct reports per function officer.
Cross-service coordination, public information function, community evacuation orders.
Bushfire, storm and community evacuation responses involve Public Information officers coordinating with state agencies. Function-officer appointments and IAP versioning keep that coordination auditable.
The v1 scope is deliberately narrow. Here is exactly what it covers.
Per-incident appointment of Incident Controller and function officers — Planning, Operations, Public Information, Intelligence, Investigation — with full audit of appointment, stand-down and handover.
Structured authoring of objectives, strategies and tactics. Versioned per operational period. PDF export suitable for formal briefings.
Period start and end, automatic snapshot at period close, and an outgoing-to-incoming handover briefing document generated at transition.
AI-drafted from the incident timeline against a formal SITREP template. Issued on demand or on schedule. Distributed via the base platform’s existing stakeholder email flow. Function officer reviews before distribution — advisory output, no auto-send.
Visual warning when any function officer manages more than seven direct reports. Surfaced to the Incident Controller so the structure can be rebalanced in-period.
Generated per tenant, mapping each AIIMS-5 principle, function and artefact to enabled EMAction features. Suitable for procurement responses. Alignment documentation — not a certification claim.
These are the questions we get asked. These are the honest answers. If any of these are deal-breakers for you, tell us now and we will be straight with you about timing.
Logistics function — resources, crews, equipment, facilities tracking — is not in v1. Command handles the incident management structure and outputs; logistics is handled by your existing systems.
Multi-agency interoperability — shared incident IDs across agencies, CAP publication — is not in v1. Command supports single-organisation incident management. Multi-agency coordination happens through documented handoffs and stakeholder communications, not through shared data planes.
A formal Investigation workspace beyond the existing audit trail is not in v1. The audit trail captures every action with actor and timestamp; post-incident investigation workflows remain out of scope.
Training and accreditation integration is not in v1. Command does not manage your AIIMS training records, accreditation status, or competency matrices.
AIIMS-5 — the Australasian Inter-service Incident Management System — defines principles, functions and artefacts used by Australian emergency services. EMAction Command covers the AIIMS-5 surface that a software platform can meaningfully deliver. The per-tenant alignment statement PDF maps each applicable principle, function and artefact to enabled EMAction features for procurement review.
| AIIMS-5 concept | EMAction Command feature |
|---|---|
| Incident Controller role | Per-incident Incident Controller appointment with full audit of appointment, stand-down and handover. |
| Function-officer structure | Planning, Operations, Public Information, Intelligence, Investigation appointments — audited per incident. |
| Incident Action Plan | IAP builder with objectives / strategies / tactics, versioned per operational period, PDF export for formal briefings. |
| Operational periods | Period management with automatic snapshot at period close and outgoing-to-incoming handover briefing document. |
| Situation Reports | AI-drafted SITREPs against a formal template; human-published via the stakeholder email flow. |
| Span of control | Visual warning at more than seven direct reports per function officer. |
| Information management | Integrates with the base platform’s tamper-resistant audit trail and stakeholder email surface. |
Alignment is not certification. No AIIMS software certification scheme exists. The alignment statement is procurement documentation — not a certification claim.
At 09:40 on a Friday, a university’s severe-weather response activates. The Incident Controller appoints function officers through EMAction Command — Planning, Operations, Public Information, Intelligence — and each appointment is audited with actor and timestamp. The Incident Action Plan is drafted against v1 objectives and strategies: secure external spaces, assess structural risk, maintain communication with residential students. IAP v1 is published.
Operational period 1 runs for six hours. SITREPs issue to the Vice-Chancellor’s office and student communications team on schedule — AI-drafted from the incident timeline and reviewed by the Planning officer before distribution. The span-of-control indicator flags when one function officer reaches seven direct reports and the Incident Controller rebalances. At 15:40, period 1 closes; the system snapshot captures state and an outgoing-to-incoming handover briefing document is produced for the relieving team.
Operational period 2 begins with a new Incident Controller receiving the handover briefing and issuing new function-officer appointments; the outgoing IC stands down, audited. IAP v2 carries forward open objectives and adds new ones for the overnight period. SITREPs continue on schedule until the event closes, 18 hours after activation. Every appointment, IAP version, SITREP issued and span-of-control intervention is auditable after the fact.
EMAction Command layers onto the base platform’s AS 3745 warden structure. It does not replace Floor/Area Warden, Chief Warden or Incident Controller roles — it adds function-officer appointments, IAP, operational periods and SITREPs on top of them. For short-duration incidents where the base platform’s warden structure is sufficient, Command stays dormant; for extended or multi-function incidents, Command layers in.
The base platform is usable without Command; Command is not usable without the base platform. Command extends the audit trail, the stakeholder email flow, the tenant architecture and the AI model routing — all of which live in the base. It is activated per tenant via the base platform’s feature-flag surface, so an existing EMAction customer can add Command without re-onboarding.
SITREP generation uses the same reasoning-tier / fast-tier AI routing as the base platform’s advisory features. Every SITREP is AI-drafted and human-published — there is no auto-send, and the function officer reviews before distribution. AIIMS decisions remain with the Incident Controller.
EMAction Command is not AIIMS certified. No software certification scheme for AIIMS exists. Any vendor claiming “AIIMS certified” should be asked to name the certification body.
EMAction Command is not a multi-agency command platform in v1. Incidents are managed inside a single tenant. Multi-agency coordination happens through stakeholder communications and documented handoffs, not through shared incident IDs or CAP publication.
EMAction Command is not a training or accreditation system. Your AIIMS training records live with your training provider; Command does not track them.
The per-tenant alignment statement PDF maps each AIIMS-5 principle, function and artefact to enabled EMAction features. Procurement teams and emergency management leads use it to answer tender questions directly — we can send the template so you can see exactly what shape the evidence takes before we build yours.
Request a demo