IDM Street Community Emergency Management System - Emergency Review and Emergency Management
Table of Contents
1 Construction Objectives... 3
2 Construction Principles... 3
2.3 Business Collaboration... 4
3.1 Emergency Response Teams... 4
3.3 Basic Categories of Community Incidents... 5
3.4 Incident Reporting Content... 6
3.5 Community Emergency Application Information System... 6
4 Recommended Construction Steps... 8
4.1 Street Emergency Information Private Network... 8
4.2 Construction of Street Emergency Management Information Platform... 8
4.3 Emergency Management System Application... 8
4.4 Emergency Management System Equipment... 9
5 Community Duty Management (Emergency Shift, Regular Shift)... 9
6.1 Emergency Rescue Disposal... 13
6.2 Rapid Activation of Emergency Incidents... 13
7.1 Basic Information Templates Generated During Disposal... 20
7.3 Incident Summary Report... 21
8.3 Emergency Inspection... 24
9.1 Existing Emergency Resources of the Street... 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
7 Emergency Review
7.1 Basic Information Templates Generated During Disposal
(1). Incident Progress List
u Release, receive, arrival, disposal, summary, archiving node table
(2). Unit Disposal Progress List
7.2 Path Review
(3). Review combined with GIS map, positioning, etc., with annotation capability; path, time, and annotation (incident + key nodes) form a video review
u Review can be conducted for units and individuals
u Sequence number, path node longitude, latitude, time, annotation
u Colors can be used to indicate traversed paths and future paths; the open attribute of the path or area at that time is also available
7.3 Incident Summary Report
(1). After filling in basic information and disposal logs, a report and case are generated according to the configured format;
(2). Basic Information Form: emergency incident name, occurrence time, alarm receiving personnel, plan trigger matching parameters, plan activation time, situation description. Disposal Log Form: disposal team list, arrival time list, disposal node list, completion time, loss summary.
(3). Document attachments, video attachments.
(4). Accident Summary Template: accident process, accident cause, personnel and property losses, accident responsibility allocation.
8 Emergency Management
8.1 Emergency Plans
(1). Index categories: category, level, incident type, response level, location, community name, call group list, call content message document and voice document
(2). Implement electronic management of all currently effective emergency plans of the street community, searchable by category (overall/special; community management area, urban management area, traffic management area, etc.), level (street, community, residential area), supporting dynamic updates;
(3). Support add, delete, modify, and query of the source database
(4). Plan workflow elements
u Emergency organizational structure
u Plan workflow nodes
Standard node content: configure task information, emergency support, emergency knowledge, external services, and other resources and functions
Node information includes task name, task purpose, task execution location, task time requirement, task importance, task content, task undertaking entity, and task execution conditions;
Parent nodes can aggregate all attribute information of child nodes, such as tasks and resources.
u Support resource configuration
Call resource information from the emergency support database and match it to the task;
Resource information includes resource name, resource type, resource requirement, resource quantity, resource location, resource contact information, etc., and is displayed on the GIS map.
u Knowledge configuration
Manage the relevant emergency knowledge required for task nodes in the flowchart; call relevant knowledge information from the knowledge base and match it to the task.
Emergency knowledge information includes knowledge name, knowledge type, corresponding chapter, etc.
u External service management
Manage the relevant external services required for task nodes in the flowchart.
Including GIS services, communication services, models, external related system interfaces, etc. During configuration, corresponding parameters need to be set to facilitate rapid activation of relevant services when the plan is invoked.
(5). Plan activation mode configuration
u Masking partial plans
Plans not currently needed can be masked and will not participate in matching searches. They can be manually executed when needed.
u Adding new tasks to a plan
Temporary tasks can be added due to temporary needs (can also be an embedded on-site execution plan) and can be activated simultaneously at startup. Temporary tasks are only executed for this instance and will not be saved to the plan.
u Changing the plan task workflow
Modify the sequence or logical relationship of corresponding workflow nodes, effective only for this activation, and not saved to the plan.
(6). Plan related information
u Risk hazard association
Associate risk hazard information that may be affected by such incidents, including the types of dangerous sources, risk hazards, key protection targets, etc., that may be affected, the range from the incident location, and the impact method. Also provide association of specific dangerous sources and protection targets.
u Image service association
Associate camera information within the range that may be affected by such incidents, facilitating the retrieval of relevant on-site video information when an incident occurs. When command & dispatch is performed, this parameter can be directly passed to the GIS service to query all cameras within that range.
u Emergency case association
Associate cases related to such incidents based on the incident classification information of the plan, and call relevant case information from the case database. Emergency case information includes case name, case task information, case task resource configuration information, etc.
u Secondary incident plan association
Associate plans related to such incidents based on the incident type targeted by the plan and the secondary derivative incident information of such incidents, and call relevant plan information from the plan database.
8.2 Emergency Cases
(1). Implement entry of emergency cases within the industry according to the configured format; emergency incidents that have occurred in the street (using this system) are automatically generated, can include documents, videos, and other forms, and support permission-based editing;
u Local city cases
u Industry case database
u Basic incident information, primary cause, secondary cause, handling process, plan invocation status, resource invocation status, losses incurred, personnel responsibility allocation. Report name, submitter, time, summary
8.3 Emergency Inspection
Implement electronic recording of regular inspections by emergency management departments of relevant departments and units regarding emergency rescue plans, personnel training, drills, material reserves, equipment maintenance, etc., based on the annual emergency management supervision and inspection plan, including the inspected unit, inspection time, inspection content, problem description, rectification basis, rectification deadline, etc., and conduct closed-loop tracking management of identified problems.
(1). Electronic record form names
u Personnel training form: training name, training time, training content. System login records (login name, login time), operation record table, training results, summary
u Emergency drill form: drill name, drill time. Login records (login name, login time), operation record table; drill results, summary
u Rescue plan form: (see emergency plan database form)
u Material reserve form: (see material management database)
u Equipment maintenance form: equipment name, equipment ID, maintenance content, maintenance cycle, maintenance time, whether overdue, maintenance unit, contact phone, equipment status assessment
(2). Emergency supervision and inspection form
u Includes: inspecting unit, inspected unit, inspection time, inspection content (the above 5 types of electronic record forms), problem description, rectification basis, rectification deadline
(3). Daily emergency inspection plan
u Regular inspection plans for emergency materials, emergency facilities, emergency sites, etc.
u Daily emergency inspection management
u Inspection and reporting of emergency materials according to plan, with inspection standards and inspection records for inspection items, including upload management of text, images, video, digital, and other data
(4). Emergency drills
u Organize emergency units and emergency personnel to train and study various plans and conduct corresponding drills.
u Organize plan training through the system platform, implement desktop plan drills, and manage the training and drill process and record data;
u Supervisory authorities can supervise emergency plan training and drill status through the system
(5). Drill objectives
Through plan drills, aggregate organizational structure, support resources, emergency knowledge, external services, risk hazards, image services, emergency cases, secondary incident plans, and other information, making the plan truly executable and operable
- Improve emergency decision-making and procedures before accidents occur; 2) Identify lacking human and material resources; 3) Improve coordination levels among various emergency response personnel, departments, and agencies; 4) Gain public recognition and confidence in emergency management capabilities; 5) Enhance the proficiency and confidence of emergency response personnel; 6) Clarify individual positions and responsibilities; 7) Strengthen cooperation and coordination among emergency organizations; 8) Improve overall emergency response capability.