Incident Automation

Product

Decision SupportResource Management & Record KeepingLive Operational Picture
How it works Documentation About

The board becomes the plan

What turns the Tactics board into the documents an incident runs on?

Locations imported from the incident’s own map, resources from the orders that brought them, and people from their check-ins all meet on one board, held for one operational period at a time. What is on it becomes the Medical Plan, the unit log, the C&G/Safety map, and the paperwork that releases somebody at the end of their assignment.

  1. What the board is built from

    • The incident’s own map Divisions, camps and drop points brought in from the incident’s own maps, so nobody types them in. A point that was renumbered is recognized rather than added twice. Feeds: Locations.
    • The resource orders What was ordered, and under which order number — so a crew can be formed before anybody has arrived. Feeds: Resources.
    • The people who checked in Everybody on the roster, with the position they were ordered as and the days they are available. Feeds: Names, Resources.
    • The operational period and its shifts An IMT sets a time of day and a length — “0700, 24-hour periods” — and the shifts inside it. Which calendar day that lands on is a consequence, not a decision, and nobody types a date. Feeds: Assignments, The next period, planned, A past period’s record.

  2. The board

    • Assignments Every resource under the division and drop point it is working. Drag one to move it, and anything that needs a second look is gathered in one place. Feeds: Where each resource is working, The next period, planned, A past period’s record.
    • Resources The same period by resource rather than by place: crews, engines and individuals. Feeds: The crews.
    • Names Every person by name, for the questions that are about a person rather than a crew, with where they are working and who they are working with. Feeds: Where each resource is working.
    • Locations The incident’s layout: branches, divisions, camps and the points inside them, kept in step with who is assigned where so nobody is left on a division that no longer exists. Feeds: Where each resource is working.

  3. What it holds, one period at a time

    • Where each resource is working A division, a drop point and a shift, held for that period. Feeds: The ICS-206 Medical Plan, The C&G/Safety map, The unit ICS-214, Reconciling with the ICS-204s.
    • The crews Who works together, for a whole operational period. Crews change between periods, and the history of who was on which crew is kept. Feeds: The ICS-206 Medical Plan, Demob, The C&G/Safety map, Reconciling with the ICS-204s.
    • The next period, planned Tomorrow’s assignments are planned without disturbing today’s, including changes to the layout itself. Feeds: The ICS-206 Medical Plan.
    • A past period’s record Kept as it stood when the period ended, so later changes do not rewrite history. A person may correct it; nothing automatic changes it. Feeds: The ICS-206 Medical Plan, The transition briefing, The unit ICS-214.

  4. What is produced from it

    • The ICS-206 Medical Plan Prepared the day before the period it covers, from the plan for that period. A past period prints from its own record, never from today’s picture.
    • The unit ICS-214 Entries are filed under the period that was in force when they happened.
    • The C&G/Safety map Who is where, for Command and General staff standing around the display, and on their phones during a green incident within an incident.
    • Demob Releasing a crew includes the members who were working apart from it, so nobody is left behind.
    • The transition briefing What the incoming unit is handed, built from the periods the outgoing one worked.
    • Reconciling with the ICS-204s Matching this board against the assignments the planning section keeps — on an ICS-204, in Trello or Microsoft Planner, or in e-ISuite and IROC — so the two cannot quietly drift apart. Planned — what is planned