Incident Command System

Description

Cleveland Fire Brigade are currently soft market testing with a view to undertaking a procurement exercise for an Incident Command System. Any Incident Command System proposed should include the following functionality: • The command system should have a way of recording decisions. Whether that be written, verbally or video recording, this is a key requirement moving forward. • It should contain the ability to be updated in real time and ensure data is not lost if connection is lost. • Tall buildings management is vital; this will be required to share occupancy and resident status for all flats within a building to be shared amongst all users. This should be user friendly and easily populated with status updates such as fire survival guidance given, resident evacuated etc. • System must be able to be accessed by multiple users and devices at once. • An ability to record the command structure of an incident would be required. • An ability to record or upload ARA and ERA documents. • The option to pass info/instant message would be useful. • All interactions with the incident must be timestamped and auditable. • Ideally the system would be compatible to a number of devices, i.e. mobile phone, tablet, and laptop/desktop. • The potential to link into other information feeds and systems, such as local authority CCTV (if available), drone footage etc. • A mapping tool that allows for things like overheads, maps, cordons, overlays etc to be displayed and use. This would incorporate things like hydrants maps etc. • The ability to record personal accountability on the incident ground, including fire and non-fire personnel. • Ability to pick up staffing from CFB rostering systems • Ability to track fire appliances on a live map (linked to CFB mobilising system)