Chapter 1 Business System
1.1 Organizational structure of the emergency platform
The organizational structure of the provincial emergency response platform is shown in the following figure:
1.2 Business processes of the emergency platform
The picture above shows the overall business process of the provincial emergency platform, and there are 2 main lines in the entire business process, one is the government emergency platform and the other is the special command. In the event of a sudden emergency, the special command center of the prefecture (county) is responsible for receiving the police.
When the municipal special command receives the alarm information, it reports to the prefectural city (county) emergency platform on the one hand, and at the same time reports to the special command center at the next higher level. When receiving emergency information, the prefectural (county) emergency platform judges the level of the emergency, and coordinates the professional departments to deal with the emergency on the spot for the general and large emergencies; for extraordinarily large and major emergency incidents, it is reported to the provincial emergency platform, and the provincial emergency platform is reported to the State Council emergency platform as needed, while coordinating all units and departments to jointly deal with emergencies.
Chapter 2 Overall Design
2.1 Overall objectives and functions
2.1.1 The overall objectives of the construction
On the basis of integrating and utilizing the existing conditions of the city, using advanced technologies such as modern information, a highly intelligent XXX provincial emergency response platform is established, including:
l Docking with the Emergency Platform of the State Council;
l Docking with the prefectural (county) emergency platform;
l Docking with professional emergency platform;
l Integrate all kinds of emergency information and emergency resources in the province;
l Perfect business system.
Through the telecommunications network, it is networked with the emergency platforms that have been built in the province to achieve information sharing, unified coordination, and auxiliary decision-making, and at the same time accelerate the construction of other emergency platforms at all levels, and ultimately achieve coverage of the province's emergency network.
2.1.2 The main functions of construction
The provincial emergency platform is an important part of the national and provincial emergency platform system, interconnected with the State Council emergency platform, the provincial professional emergency platform, and the prefectural and municipal emergency platform, and has the corresponding functions of the State Council emergency platform. The main functions are:
l Through interconnection with professional emergency platforms and the use of professional department monitoring networks, dynamic monitoring of hidden dangers of public emergencies, especially the spatial distribution and operation status analysis of major hazard sources, critical infrastructure and important protection targets;
l Integrate the province's emergency information and emergency resources;
l Command and coordinate various professional departments, and the prefectural and municipal emergency response platforms to coordinate the handling of particularly major and major emergencies;
l Information release and notice;
l Summary of post-evaluation
2.2 The principles, basis and standards of design
2.2.1 Principles of Design
XXX Provincial Emergency Platform Construction Project is a complex structure, technical difficulty, strong functions, involving a wide range of information construction projects, in order to ensure that the project to achieve the expected purpose, engineering construction should follow the basic principles of practicality, reliability, economy and advanced, embodied in:
l System construction should follow the principle of "overall layout, step-by-step implementation, practical and advanced". Application-driven, under the condition of making full use of existing facilities and resources, we strive to start from a high starting point to meet both short-term needs and long-term development needs.
l Adhere to the principle of standardization and openness. Fully consider the rapid development of modern information technology, adapt to the requirements of future functional upgrades, so that the system has openness, compatibility, expansion, system construction should give priority to the selection of products and technologies that meet openness and international standardization, and follow the relevant specifications.
Adhere to the principle of ensuring safety. The system design and construction meet the corresponding safety level according to the requirements to ensure that the system operates with a high degree of reliability and safety.
l Adhere to the principle of tracking, feedback, update and improvement, so that the system is constantly close to the needs of production practice.
2.2.2 Basis of design and main standards
2.2.2.1 Policies, regulations, norms and standards of national, local and relevant departments
2.2.2.2 Current international and domestic relevant standards and industry norms
2.3 Overall structure of the system
The overall structure of the system is shown in the following figure:
From bottom to top, there are four levels, in order:
1. Foundation support system
The basic support system includes a computer network system, a host storage and a backup system
2. Information Repository
The information resource database mainly includes the expert database, the plan database, the knowledge base, the emergency material database, and the basic geographic information database.
3. Data exchange platform
The data exchange platform is a data exchange platform that can realize both data exchange between heterogeneous systems and business process automation between heterogeneous systems.
4. Application software system
The application software system includes an integrated business management system, a risk monitoring and early warning access system, a collaborative consultation auxiliary decision-making system, an intelligent plan system, a geographic information system, an emergency resource management system, an emergency assessment system, an emergency drill system, and an information release system. Users use these business systems by logging in to the emergency portal.
Chapter 3: Information Repository Design
3.1 Construction ideas
The construction of the provincial emergency platform information resource database mainly includes four aspects:
1. Hierarchical classification of information repositories
Information resources can be classified according to the real-time, criticality, and frequency of use of data.
2. Clarify the information resources that the provincial emergency response platform needs to manage
This part of the resources mainly includes the province's overall plan database, expert database, major hazard source database, case database, etc.
3. Identify the information resources that need to be stored centrally
Centralized storage of information resources may include data that is not highly real-time, frequently used, and critical.
4. Integrate the information resources of provincial-level professional departments and prefectures and cities
The integration of information resources simply has three steps, one is to develop the standard specification of integration, the second is to model the information resources, and the third is to make a request through the data exchange platform to obtain the required data.
3.2 Construction content
3.2.1 Base geodatabase
The extension of basic geographic data is very extensive, including basic terrain data, land use data, underground pipeline data, geological data, cadastral data, real estate data and corresponding attribute data. In terms of data form, the most important urban spatial data are digital lineline topographic maps (DLGs), digital orthophoto data (DOM), and digital elevation model data (DEM). As far as data applications are concerned, they are divided into spatial geographic information basic data, thematic data, e-government application spatial data, public service spatial data and so on. The basic geodatabases that need to be built by the provincial emergency platform mainly include the following two types:
l Base Terrain Database (DLG)
Includes basic topographic maps at scales such as 1:10,000, 1:50,000, and 1:250,000. The basic topography database includes nine major categories of elements, including survey control points, residential land, industrial and mining buildings (structures) and other facilities, transportation and auxiliary facilities, pipelines and fences, water systems and auxiliary facilities, realms, landforms and soils, and vegetation, that is, the so-called all-element topographic map.
l Image database (DOM)
Digital orthophoto data include: aerial digital orthophoto data (DOM-AP1), Ikonos satellite image with a resolution of 1 meter, QuickBird satellite image data with a resolution of 0.61 meters, TM digital orthophoto data (DOM-TM30), and SPOT digital orthophoto data (DOM-S10). Pyramids are established after these data are stored. It is mainly used as the basic positioning data for data updates and data overlays, and it is also an important image data for detailed understanding of an area.
3.2.2 Emergency Thematic Database
1. Emergency Expert Database
The expert database stores the personal information of relevant industry experts who need to be consulted to deal with different emergency incidents, and is mainly composed of expert basic information, work resumes, emergency incident consultation records and other entities, which can provide various vague queries. The following are the entities involved and their properties:
The basic information of experts mainly includes the following data items: ID, name, gender, date of birth, highest education, graduation school, graduation year, recent photo, current work unit, current professional, current professional years, position, technical title, professional expertise, industry category, mobile phone, unit telephone, residential telephone, other contact information, expert group number (such as medical treatment group, health education group, mental health group, law group, etc.), employment position (such as team leader, team member), recommending unit opinions, recommenders, Audit opinions, audit units (such as health bureaus), auditors, start date, expiration date, remarks, etc.
The work resume (filled in from the university) mainly includes the following data items: start date, end date, employment unit, department, position, etc.
Emergency incident consultation records, storing the consultation of experts who have participated in emergency incidents, mainly including the following data items: participation time, emergency event ID, recommended measures, effect evaluation, etc.
Technical titles, with reference to the national standard coding table, include the following data items: title code (must be 3 digit code), title name.
Industry categories, including the following data items: industry category code, industry category name.
2. Emergency Plan Library
The emergency plan library includes various types of plans for various public emergencies, such as poisoning, poisoning, epidemic, nuclear prevention, biochemical prevention, earthquake, fire, flood prevention and drought control, typhoon, maritime search and rescue, etc.
3. Reservoir of major hazard sources
The Hazards Database stores the distribution of long-term or temporary units (including places and facilities) for the production, handling, use or storage of dangerous goods (jointly constructed with the Safety Supervision Bureau), mainly composed of entities such as hazard sources, to meet the management needs of major hazard sources, dangerous goods transport vehicles, high-risk factories and enterprises, special equipment, etc. The following are the entities involved and their properties:
Hazardous source data sheet, mainly including the following data items: the name of the hazard (such as dangerous goods and chemical production sites), the category (such as production, storage sites), the nature (such as long-term, temporary), the form of expression (such as collapse, fire, chemical/physical explosion, etc.), the name of the dangerous goods, the storage location, the unit of measurement, the quantity, the physical and chemical characteristics, the category to which the dangerous goods belong, the safety impact (such as personal injury, property damage, the damage to the operating environment), the scope of harm, the degree of harm, the level of danger, the competent unit, the responsible person, Emergency plans (including measures, emergency rescue flow charts, etc.) and so on.
4. Emergency Team Database
The emergency team database stores information and communication and contact information on the composition of the emergency team covering all kinds of emergency departments, emergency rescue teams, experts, districts, towns (streets), villages (neighborhood committees) and relevant functional departments in our city, mainly composed of emergency teams and other entities. The following are the entities involved and their properties:
The emergency response team mainly includes the following data items: team ID, team name, team group, main responsibilities, subordinate units (such as the municipal fire brigade, the municipal gas company, the municipal armed police squadron, a street, etc.), equipment and equipment (including the number, status), personnel composition, distribution location, office telephone, mobile phone, contact person, other contact information, etc.
The team group mainly includes the following data items: team group, team group name (such as emergency repair team, fire protection group, safety vigilance group, rescue and evacuation group, medical rescue group, material supply group, etc.), responsibilities, scale level, etc.
5. Emergency Supplies Database
The emergency material support database provides information on the distribution, quantity, and composition of the city's emergency rescue team, natural disasters, accident disasters, public health events, and social security incidents, and is mainly composed of entities such as the types of rescue materials and emergency relief materials. The following are the entities involved and their properties:
The categories of rescue materials mainly include the following data items: category ID, type name (such as communication equipment, analytical instruments, testing equipment, fire fighting equipment, anti-virus appliances, explosion-proof appliances, engineering machinery, hardware tools, means of transport, plugging tools, warning supplies, medical equipment vehicles, medicines, protective supplies, clothing and other rescue materials) and so on.
Emergency relief materials mainly include the following data items: material and equipment name, category, quantity, specifications and models, size, status (good condition /validity period), use, use method, storage location, person in charge, and transfer method, contact information, etc.
6. Emergency Regulations Database
The laws and regulations database stores legal and regulatory information related to public emergencies, and is mainly composed of entities such as laws and regulations. It mainly includes the following data items: the name of laws and regulations, the ID of the public emergency, the level (national/provincial/prefectural), the industry category, the content of the regulations, the promulgating agency, the date of promulgation, etc.
7. Emergency Case Library
The typical case database provides various historical events and examples at home and abroad, and the occurrence, scope of impact, loss scope, solution, etc. of various major events, mainly composed of typical cases and other entities. It mainly includes the following data items: event name, level, event description, event nature, change trend, cause of the event, place of occurrence, unit of occurrence, time of occurrence, number of people involved, scope of impact, loss situation, solution, prevention and recommendation of similar events, information sources, etc.
Chapter 4 Data Exchange Platform Design
4.1 Requirements Analysis
In order to realize the interconnection and interaction between the special (departmental) command centers, the command sites of the provincial emergency office and the emergency command center for various types of social public information and professional business information sharing and application systems, the demand for heterogeneous database data exchange between systems, including cross-industry systems and between different systems in the same industry, and the business process automation between application systems has become more and more intense, in order to effectively solve this problem. We needed a data exchange platform that could enable both data exchange between heterogeneous systems and business processes between heterogeneous systems.
The data exchange system is the core of the entire public safety emergency command system business and application platform system.
4.2 System Structure
The design of the data exchange platform needs to be divided into three levels: the provincial emergency platform, the prefecture (county), and the special (departmental) emergency command center in accordance with the multi-level and distributed way. The configuration and deployment of the three levels are the same, and the functions implemented are also the same.
The following diagram shows the overall design structure:
4.2.1 Information extraction of cities, counties, institutions and systems in various places
Information extraction based on files and messages can be adopted, and files and messages are generated by the prefectural city, county, and institutional systems. Secondly, for example, HTTP (the protocol used in Internet service programs), Email and other methods can be used as data entry terminals.
For users of the government private network, if the other party allows it to use a variety of information extraction methods, hierarchical information extraction, such as database layer, application system layer and so on.
Ø Communication layer:
Because the emergency information system needs to connect cities and counties, institutions, companies and other institutions, the emergency information system can support various network environments at the communication layer, such as various private networks, Internet public networks, etc.; it must also support various common communication protocols, such as HTTP (the protocol used in Internet service programs), FTP (file transfer protocol), TCP/IP (transmission control protocol/network protocol), Email and so on.
Ø Database layer:
If cities, counties, institutions, companies, etc. provide databases that can be connected to emergency information systems, the central platform provides support for various mainstream databases, such as Oracle, DB2, Sysbase, SqlServer, Infomix, etc.
Ø Application layer:
When local agencies do not have a database available for central platform access, they can connect their application systems, and both tight coupling and loose coupling can be used, which is also a necessary condition for information automation.
Ø Data format layer:
Since the information obtained by the central platform comes from different municipalities, institutions and companies, which have their own data standards, the central platform supports various data formats, including standard data formats, such as XML (Extensibility Markup Language), EDI (Electronic Data Interchange), ebXML (an e-commerce standard), etc., as well as user-defined data standards.
Ø Language call layer:
In order to ensure the system's support for various institutional legacy systems, the central platform supports the invocation of various mainstream languages.
4.2.2 Transmission of information to cities, counties and institutions in various regions
From the overall architecture diagram above, it can be seen that the emergency information system can support a variety of communication protocols and network environments. For government private network and public network users, the central platform can be well supported.
Various prefectures, counties, institutions, etc. can adopt appropriate transmission methods, such as Http (the protocol used in the www service program), Email, FTP (file transfer protocol) and so on. In order to give cities, counties and institutions greater flexibility, the central platform does not restrict its transmission mode, and ensures that in addition to the government private network, it must also support public network-based transmission, and support firewalls to ensure the security of data transmission.
4.2.3 Information Processing of the Central Platform
Emergency information system, to establish an information center, the organization and storage of various business data, then the need for data extraction, transformation and mapping, the platform can make the information center and the city, county and agency interconnected through various communication protocols. The following are the main information processing functions:
Ø Support conversion between various data:
Cities and counties, institutions, and systems around the world have their own data formats, in order to achieve the identification and processing of various data formats, the emergency information system can realize the conversion between various data formats.
For example, a custom format is used for an emergency system, and the emergency information system needs a format defined according to national standards (assuming that it is based on XML-Extensible Markup Language), so that the emergency information system must be able to automatically extract emergency information and convert it into XML (Extensible Markup Language) format.
Ø Graphical format conversion tools:
In order to improve the efficiency of data conversion, it is necessary to provide effective graphical format conversion tools to simplify the process of data conversion.
Ø Data processing and storage can be carried out conveniently:
At the same time as data conversion, data items can be processed and manipulated, such as merging statistics between similar information, etc., as well as support database operations to achieve data storage and backup.
4.3 System Functions
4.3.1 Heterogeneous data exchange functions
Database connection: Support various common types of database management systems such as SqlServer, DB2, Sybase, Oracle, etc., and can achieve transparent connection with the data to be hooked.
Extract: Extracts from specified database tables and organizes data to automatically generate a standard data format.
l Data transmission: Support asynchronous, real-time transmission of data, will send the received messages to the data exchange center and receive messages from the data exchange center, and can ensure the reliability of data transmission and acceptance.
Data validation: Verify the data information sent and received.
l Data splitting and merging: Before sending, the large-capacity data information is split into several data information units, and the received data information units are merged. Encrypt and compress the transmitted data.
l Data conversion: User-defined data format definition tool with graphical user interface, supports XML format processing, and supports data format conversion from any format to any format.
The management configuration module can implement route management of messages.
l Provide users with system health information, including application information to access the system, data transmission time statistics, system traffic statistics, logs and other information.
Support XML, Web services and other technical specifications.
4.3.2 Heterogeneous application system integration functions
Support distributed applications, the entire platform can be distributed on multiple machines, working together;
l The system provides node address management, which can easily realize the routing and forwarding of messages;
Provide a message queuing mechanism to achieve various forms of message sending (point-to-point, point-to-many, point-to-group, point-to-group);
● With a recovery mechanism, when an abnormal connection interruption occurs during data transmission, the recovery of data can be ensured, that is, the message cache retransmission mechanism;
Integrated with the PKI system, it supports data encryption transmission and compression transmission, and ensures the security, integrity and non-repudiation of data at the transmission layer;
l Provide a variety of networking methods, adapt to business needs, have good performance and data throughput capabilities, and can be flexibly expanded to adapt to the development of the system;
Provide rich access methods, inter-system message and data exchange support both traditional file formats and XML specifications, greatly improving the extensibility of service customization messages, and realizing the interface with common Web services and other products compatible with XML specifications;
Provide adaptive resource state management function, terminal applications can subscribe, register, obtain resource status according to their own needs, and provide customizable trigger operations according to resource changes, so as to achieve unified processing of separated resources;
Support continuous change of application architecture. Can be easily reconfigured to add or remove systems without affecting other systems;
l Provide perfect group permission control, and set different permissions for message types, operator types, group types, account numbers and other schemes, ensuring data security at the business logic layer;
l With system self-diagnosis mechanism, the resource status can be analyzed according to the pre-set combination conditions and fault alarm can be carried out;
l Built-in disaster recovery system to ensure the robustness of the system and the security of data;
l Strong secondary development support, simple and easy-to-use customized development of access services, to meet the needs of various rapid realizations of the bureau or government;
Cross-platform, providing platform versions on Windows, Unix, Linux and other operating systems.
4.3.3 System Management Tools
The system management tool can monitor the operating status of the system, provide traffic analysis, logging, a variety of fault alarms and other functions; have a perfect tracking and auditing function for the characteristics of the application integration application; can easily establish a connection with the alarm system, so that when the system error occurs, you can remind the management personnel. It also has a perfect data backup function.
Chapter 5: Integrated Application System Design
5.1 Integrated Business Management System
The emergency comprehensive application system can provide comprehensive management of the whole process of daily and emergency work involved in each unit, and the content involved in the system mainly includes: emergency duty, information reporting, publication reports, etc.
Pay attention to my technical public account, every weekday there are high-quality technical article push and electronic version of the program download. Please pay attention to the same number WX to download the electronic version of the program.