Incident Command Development Update

As many of you will have seen at our User Forum, work has already started on the ScResponse Incident Command module. Designed to be installed on all appliance MDTs, it enables the first responder to immediately start planning in reaction to the incident by knowing which other crews are on route, initial cordon planning, access to risk information, etc. Once the Incident Commander has arrived on site, they immediately know who has been allocated to the incident, their status and location, and the actions taken and messages exchanged already, thus minimising the time required to “get up to speed”.

As ScGateway already enables the exchange of mobilisation, status and text messages, using ScResponse Incident Command enables access to full communications functionality and full incident message log. All data messages sent, via ScGateway, between mobilised resources will be available within SIC Message Log to give the Incident Commander a complete overview of the incident’s history and current position. All items added to the Incident plan, within ScResponse Incident Command, will be relayed to all mobilised ScResponse Incident Command enabled resources ensuring the plan data currency is near real time and not time delayed. Along with ScGateway’s ability to retry messages over multiple bearers brings enhanced plan availability and resilience to Incident Management. 

ScGateway integration will also enable the creation of a Resource Pool containing all call signs mobilised to the incident. The Standard Crew Riding module provides functionality to complete the Officer in Charge of each appliance as well as the number of crew. The enhanced Crew Riding module, if deployed, will facilitate the addition of crew names to the Resource Pool. Assets selected from the Resource Pool or manually created can be added to the map or the Command Structure to allow the Incident Plan to be displayed graphically and structurally.

The Incident Commander will be able to draw hazmat cordons with the ability to add Radiated cordons and Sectorised cordons and ScResponse Incident Command uses the same Risk Data, SOPS, Datashares, Overlays, Chemdata, CRS and mapping as the Mobile Data MDTs, saving data preparation time, avoiding duplication and reducing potential for data discrepancies between systems, to evaluate and progress the incident.

Incident Command Development Update

As with all of our products and modules, we have already identified an extensive roadmap for the ScResponse Incident Command module; however, version 1 will include:

Resource Planning

  • Resource Pool for Mobilised resources (Appliances/Call signs only)
  • Resource Pool Assigned resources
  • Manage Operational Organisation Chart / Command Structure
  • Manage Operational / Incident Resources
  • Operational Resource Allocation from C2
  • Manually Add / Remove Operation Resources

Governance & Reporting

  • Send Analytical Risk Assessment
  • Send Decision Log Submission
  • Allocate / Reallocate Incident Commander
  • Receive Incident Timeline

Advanced Cordons

  • Place / Remove Cordon (Basic Hazmat Circular Cordons only)
  • Place / Remove Cordon (Advanced Hazmat Circular Cordons only)
  • Send Basic Cordon to others as a message
  • Send Hazmat Cordon to others as a message
  • Place Multiple Cordons (Inner and Outer Cordon only)
  • Search Gazetteer using Cordon

GIS Redlining

  • Display redline points, lines and shapes in GIS (styling set in config)
  • Draw points, lines and shapes in GIS (touchscreen)
  • Send/Receive redline data as a message(s) over ScGateway
  • Save Redline to File / Load Redline from File
  • Place Free Text
  • Basic Redline Edit Tools

Visual Planning (advanced redlining)

  • Place sector markers on Map

Don’t worry, we’ve taken on board the advice from everyone at the User Forum and will be “keeping it simple”! We’ve already established a small Working Group to provide us with feedback during development and expect to demonstrate our progress to them before Christmas. We’ll start demonstrating to our wider user-base by late January. Currently, we’re still on target to release ScResponse Incident Command v1 in early Q2 2017.

 

Incident Command Development Update