IDM Street Community Emergency Management System -- Emergency Handling
Table of Contents
I Construction Objectives... 3
II Construction Principles... 3
2.3 Business Collaboration... 4
3.3 Basic Categories of Community Incidents... 5
3.4 Incident Reporting Content... 6
3.5 Community Emergency Application Information System... 6
IV Recommended Construction Steps... 8
4.1 Street Emergency Information Private Network... 8
4.2 Building the Street Emergency Management Information Platform... 8
4.3 Emergency Management System Application... 8
4.4 Emergency Management System Equipment... 9
V Community Duty Management (Emergency Shift, Normal Shift)... 9
5.1 One-Table Duty Roster... 9
6.1 Emergency Rescue Handling... 13
6.2 Rapid Activation of Emergency Incidents... 13
7.1 Basic Information Template Generated During Handling... 20
7.3 Incident Summary Report... 21
VIII Emergency Management... 21
8.3 Emergency Inspection... 24
9.1 Existing Street Emergency Resources... 26
9.2 Emergency Organizational Structure... 28
9.3 Emergency Personnel Management... 28
9.5 APP Emergency Resource Inspection and Reporting Content (Resource Tracking Management) 28
9.6 Resource Dispatch Order (Resource Usage Process Management)... 28
9.7 New Resource Information Release Form... 29
9.8 Resource Information Push... 29
VI Emergency Handling
6.1 Emergency Rescue Handling
Includes: emergency information reporting, emergency information acquisition, intelligent matching of emergency knowledge, emergency handling progress, and reporting of emergency incident-related information.
Specific implementation: rapid activation of emergency incidents, multi-channel information release, intelligent checklist reminders, instant messaging, emergency map, display of handling progress, and situational awareness of the incident (overall + real-time).
6.2 Rapid Activation of Emergency Incidents
(1). Emergency Information Reporting
u Upon receiving an emergency alarm, the alarm information must first be confirmed, including calling on-site personnel for confirmation and confirming through more technical means, such as cameras, monitoring, and other data sensors.
u After selecting the emergency plan, reporting is carried out first: the emergency information is reported to the supervising leader, and then the emergency plan is activated.
(2). Emergency Information Acquisition and Entry Form
u Includes on-site personnel reports, on-site sensor information, AI image recognition information, voice recognition information, incident keyword information, and information entry time, etc.
u Call/Alarm Receipt Form: incident type (aircraft-related, non-aircraft-related), incident location (airspace, ground, inside airport, outside airport), incident subcategory selection (items selectable from a list, cannot be self-filled), detailed description (incident type, community name, casualties, degree of failure, incident location, incident time, description).
(3). Emergency Knowledge Push
u Based on the keywords acquired from the emergency information, automatically match and display knowledge points retrieved from the emergency knowledge base.
(4). Based on existing emergency plans and checklists, select key information such as incident type, response level, location, and community name to form an activation command. One-click activation + group call, with support for displaying how many units have confirmed the group call, which have confirmed, and which have not.
u Based on the specific conditions of the incident, directly invoke the emergency plan information from the plan system, thereby achieving linkage between the plan and emergency incident handling. During the linkage process, the plan system can automatically match relevant plans based on the incident response level and type, and then activate the relevant plans. Subsequently, users can use the emergency auxiliary decision support system to query the emergency handling plans for the corresponding incident.
u Plan selection items: incident type, response level, location, community name.
u One-click activation + group call.
u Number of group calls: group call progress displayed sequentially.
u Confirmation information statistics.
6.3 Emergency Response
(1). Plan Execution Function
u Automatic tasks
n Such as sending mobile phone SMS, APP short messages, display information videos, broadcast playback files, and other methods that can be delivered quickly.
n Control commands: such as cutting off power, audible and visual alarms, opening safety doors, etc.
n Receiving feedback information: whether received, whether completed, and receipt time.
n Automatic phone calls: point-to-point calls, conferences, roll calls, polling, and other batch processing modes.
u Linked tasks
n Forward various preset tasks to linked organizations, providing original parameters: incident details, plan content, department tasks (including task name, content, responsible person, processing time requirements, and dispatched resources).
n After task dispatch, the system monitors according to the predetermined time requirements. If no correct result is received, alarms of different colors are triggered. If the time is exceeded, reminder SMS messages can be sent.
n After receiving tasks, linked units promptly report their action progress status information, including accepted, departed, arrived, controlled, and completed.
n Reporting methods: individual terminal (APP), vehicle-mounted computer, walkie-talkie voice reporting, mobile phone SMS, on-site one-key alarm post, etc.
u New tasks
n Task dispatch (tasks added but not executed before plan activation, or tasks that need to be executed but were suppressed).
n New tasks requiring manual activation; the incident record will include the task name ID, activation time, and other records.
n Temporary tasks.
n New tasks requiring manual activation; the incident record will include the task name ID, activation time, and other records.
(2). Multi-channel Information Release: After an emergency incident occurs, emergency information must be released through broadcast, intercom, text, images, maps, and other methods, with the ability to select recipients or pre-configure them.
u Activate the emergency dispatch release plan: select recipients (temporary selection, plan selection).
(3). When activating an emergency, one-click group call can be selected. Key information can be matched based on the preset information notification template and pushed to rescue units and relevant leaders. The mobile APP prompts via sound and vibration. Recipients must click to confirm, and only after confirmation can the voice or ringing be dismissed.
u One-click group call.
u Select information content.
u Search the recipient list based on the selection in the first step.
u APP corresponding mode: sound/vibration, reply confirmation.
u Confirmation information statistics.
(4). Supports linkage with emergency alarm bell and light devices of associated units.
u Alarm bell sound and light control, terminal confirmation, and central-side reset.
(5). Supports entry of vehicles and materials dispatched for emergency response.
u Entry form/display form: unit, vehicle name, license plate, vehicle contact ID, list of carried materials (material name, material quantity).
(6). Supports different units and roles in independently designing and editing their checklists. Checklists are intelligently matched based on incident type, response level, and emergency role. When an emergency incident is activated, the interface automatically jumps to the checklist screen.
u Checklist (emergency name, incident type, response level, emergency role, list of checklist items (list of possible incidents; list of proposed response plans)).
(7). Supports intelligent checklist reminders, with individual/unit handling progress entered based on the checklist.
u Handling checklist form.
u Checklist name and category.
u List of expected incident content.
u List of handling methods.
u Example: A fire breaks out in a room on the 2nd floor of Building 3. Expected incidents: 1. insufficient firefighters, 2. insufficient equipment, 3. electrical fire. Possible plans: 1. call nearby patrol personnel, 2. call the neighboring rescue team, 3. support from the nearby micro fire station, 4. shut off the main power supply.
6.4 Instant Messaging
(1). Supports one-to-one and one-to-many chat communication, supports sending text, voice, images, and video, and supports creating groups.
(2). Automatic group formation: groups are automatically formed based on the daily duty roster. Only the company's No. 1 leader / department duty leader of the day has the authority to dissolve the group.
(3). Supports information classification into levels such as command, key information, and general information. The information sender or designated authorized person can mark the information level, distinguished by font color and other means.
(4). QR code scanning to join a group: a group QR code can be generated. After scanning, the group owner must approve before the person can join the group.
(5). Functions
u The individual terminal is installed on an Android-based terminal; uses wireless ad hoc network communication on a designated frequency, or military/private network LTE base station communication; provides audio/video point-to-point calls and point-to-multipoint conference group calls; the individual terminal can connect to other individual terminals, network cameras, computer monitor window images, and various audio intercom and broadcast terminals. The audio/video interface provides a text interaction display window for command notifications; it can switch to instant messaging functions at any time to send and receive location, voice, text, numerical values, images, and short videos. Supports full media and functions including video, text, voice, files, images, emojis, and geographic location, to facilitate quick communication between users and customer service. Supports group information: adding or removing members, group name, group description, group announcements, shared files, and pinned chats. Supports big data collection based on group functions and user responsibilities, with data analysis, query, and statistics capabilities.
(6). Instant Message Operation Types
u Message monitoring, sending messages, recalling messages, deleting local messages, inserting group chat messages locally, marking group chat messages as read, creating text messages, creating @ messages, creating @all messages, creating image messages, voice messages, video messages, file messages, merged messages, forwarded messages, location messages, custom messages, quoted messages, card messages, custom emoji messages, clearing single chat message history, clearing group message history, searching messages, and marking messages as read.
(7). Group Operation Types
u Group relationship monitoring, inviting to group (direct entry without approval), removing group members, querying group member profiles, querying the list of joined groups, creating a group, editing group profile, querying group information, applying to join a group (requires administrator/group approval), leaving a group, retrieving one's own group join application records, administrator or group owner approving/rejecting someone's entry into a group, dissolving a group, enabling group mute (all group members prohibited from speaking), and muting group members.
6.5 Emergency Map
Implemented in GIS: confirm the incident location, determine the assembly point for rescue forces, optimize the rescue route, and provide real-time display of vehicles en route to the rescue site.
(1). Real-time Positioning
u Supports displaying the positioning of APP users of this system and vehicles dedicated to emergency response and rescue;
u Supports displaying dynamic information of aircraft and vehicles, among other content.
u Supports displaying the overall arrival status of units (total); clicking allows querying which specific units have arrived and which have not;
u Overall arrival status of vehicles, personnel, and materials (total); clicking allows querying the arrival details of vehicles, personnel, and materials, where personnel and vehicles are based on positioning, and materials are generated from entries made via PC or APP terminals of each unit;
(2). Emergency Routes
u Emergency route selection can be performed by setting standard routes (which can be periodically updated and optimized), or by temporary marking and designation from the command terminal. Route clearance functionality is available when entering controlled areas (including ATC control zones and apron control zones).
u Emergency route editing: emergency event name; number of route nodes; sequence position table
(3). Area Handover
u Colors are used to distinguish handed-over areas from non-handed-over areas; after area handover, annotations can be added.
u Area enablement permissions
(4). Line Drawing and Marking
u Supports marking any point on the map with different icons, visually displaying specific locations such as the incident area, core security cordon, temporary passenger assembly area, on-site command post, and rescue vehicle parking area;
u The above marked areas can be selectively displayed;
u Supports drawing lines with different colors and thicknesses; lines can be erased.