GB 26875.6-2011Remote-monitoring system of urban fire protection - Part 6: Functional requirements for information management software (English PDF)

Foreword

This document complies with the provisions of GB/T 1.1-2020 "Standardization Work Guidelines Part 1: Structure and Drafting Rules of Standardization Documents".

Drafting.

This document is Part 6 of GB (/T) 26875 "Remote Monitoring Systems for Urban Firefighting". GB (/T) 26875 has the following published...

part.

---Part 1: General Technical Requirements;

---Part 2: Functional Requirements for Communication Service Software;

---Part 3: Alarm Transmission Network Communication Protocol;

---Part 4: Basic Data Items;

---Part 5: Software Functional Requirements;

---Part 6: Functional Requirements for Information Management Software;

---Part 7: Functional Requirements for Fire Protection Facility Maintenance and Management Software;

---Part 8: Monitoring Center External Data Exchange Protocol;

---Part 9: User Information Transmission Device;

---Part 10: Requirements for fire protection facility information collection devices and interfaces.

This document supersedes GB/T 26875.6-2011 "Urban Fire Remote Monitoring System Part 6: Functional Requirements for Information Management Software".

Compared with GB/T 26875.6-2011, apart from structural adjustments and editorial changes, the main technical changes are as follows.

a) The definitions of the terms "user" and "management" have been changed (see Chapter 3, Chapter 3 of the 2011 edition);

b) The content of the "Basic Requirements" has been changed and is now in section 4.3 (see section 4.3, Chapter 4 of the 2011 edition);

c) The requirements for user rights management have been changed (see 4.1, 5.1 in the 2011 version);

d) The requirement for the "check-in" function has been removed (see section 5.2 of the 2011 version);

e) Added user registration request requirements (see 4.2);

f) The function of managing monitoring center information has been removed (see 5.3 in the 2011 version);

g) The requirements for managing networked unit information functions have been changed (see 4.4, 5.4 in the 2011 version);

h) The search terms for statistical fire alarm information and fire protection facility operation status information have been changed (see 4.5, 5.5 in the 2011 version);

i) Added functions for call recording during the acceptance process, information processing operations, and time record query (see 4.7);

j) Added multiple statistical dimensions (see 4.8~4.10);

k) Change "Test Methods" to "Conformity Assessment" and make changes to the content (see Chapter 5, Chapter 6 in the 2011 edition).

Please note that some content in this document may involve patents. The issuing organization of this document assumes no responsibility for identifying patents.

This document was proposed by the National Fire and Rescue Administration.

This document is under the jurisdiction of the National Fire Protection Standardization Technical Committee (SAC/TC113).

Introduction

Urban fire remote monitoring systems, as an important component of "smart city" and "smart fire protection" construction, play a crucial role in improving the completeness of building fire protection facilities.

It has played a positive role in improving the fire safety rate, enabling timely identification and rapid response to initial fires, and enhancing the fire safety management level of social units.

With the deepening of a new round of technological revolution and industrial transformation, a large number of new technologies, systems, and business models with higher security are emerging, and the Internet of Things (IoT) is becoming increasingly important.

High-tech technologies such as the Internet, cloud computing, big data, and artificial intelligence have been deeply integrated and applied in the fire protection field, and urban fire remote monitoring systems are keeping pace with the times.

The demand, through technological iteration, plays a vital role in reducing fire safety risks, and empowers the transformation and upgrading of fire protection work. In order to adapt to the information age...

The development of information technology will promote the implementation of the main responsibilities of social entities, enhance the social fire safety governance capabilities and urban risk monitoring and early warning capabilities, and improve the system.

GB (/T) 26875 "Urban Fire Remote Monitoring System" is ordered. GB (/T) 26875 is planned to consist of ten parts.

---Part 1: General Technical Requirements. The purpose is to specify the architecture and composition of urban fire remote monitoring systems and to clarify system functions.

Requirements related to energy, performance, and safety.

---Part 2: Functional Requirements for Communication Service Software. The purpose is to specify the functional requirements of the application support platform in the urban fire remote monitoring system.

The functions implemented by the messaging service software.

---Part 3: Communication Protocol between User Information Transmission Device and Application Support Platform. The purpose is to specify the communication protocol between the user information transmission device and the application support platform.

Transmission protocols between application support platforms.

---Part 4: Basic Data Items. The purpose is to define the basic data items included in an urban fire remote monitoring system.

---Part 5: Software Functional Requirements. The purpose is to specify the manual requirements for the support platform used in urban fire remote monitoring systems.

The functions implemented by the agent handling software.

---Part 6: Functional Requirements for Information Management Software. The purpose is to specify the functional requirements of the supporting platform used in urban fire remote monitoring systems.

The functions implemented by information management software.

---Part 7: Functional Requirements for the Maintenance Unit's Application Platform. The purpose is to specify the maintenance requirements for the urban fire remote monitoring system.

The functions implemented by the application platform of the nursing unit.

---Part 8: System External Data Exchange Protocol. The purpose is to define the data exchange protocol between the urban fire remote monitoring system and external information systems.

Data exchange protocol between them.

---Part 9: User Information Transmission Devices. The purpose is to specify the user information transmission devices in urban fire remote monitoring systems.

Functional and performance technical requirements.

---Part 10: Requirements for Fire Protection Facility Information Acquisition Devices and Interfaces. The purpose is to specify the requirements for fire protection facility information acquisition devices and interfaces in urban fire protection remote monitoring systems.

Requirements for information collection devices and interfaces for fire protection facilities.

Urban fire remote monitoring system Part 6: Functional Requirements for Information Management Software

1 Scope

This document specifies the functional requirements and compliance evaluation of the information management software used in the application support platform of the urban fire remote monitoring system.

This document applies to the design and development of information management software (hereinafter referred to as "software") for the application support platform in urban fire remote monitoring systems.

And testing.

4 Functional Requirements

4.1 The software should have administrator and regular user accounts. The administrator account has advanced privileges and can register and close accounts for regular users.

It can manage and assign access permissions to data within the application support platform to users based on their different user roles.

4.2 The software should have functions for user registration requests, registration information verification, and notifying users whether registration was successful. Basic user information should be...

Information including name, gender, ethnicity, date of birth, type of identification document, mobile phone number, identification document number, and affiliated organization should be included. Basic information for organizational users should...

This includes the organization's (unit's) name, unified social credit code, address, date of establishment, name of legal representative, type of legal representative's identification document, and legal status.

Information such as the representative's identification number.

4.3 The software shall meet the following requirements.

a) The software interface should be displayed in Chinese;

b) If an abnormal situation occurs during software operation, the user should be notified of the software malfunction;

c) The software should have a unified login portal and should support at least one login method among username, mobile phone number, and ID card number.

4.4 The software should have the function of managing the following information of networked units.

a) Basic information of the networked entity; see Table B.1 of GB 25506-2010 for details.

b) Information on the main buildings and structures of the networked unit, detailed in Table B.1 of GB 25506-2010.

Content;

c) Information on key fire safety areas within networked units (premises), detailed information can be found in Table B.1 of GB 25506-2010.

Contents of information on key fire safety areas within the building;

d) Information on indoor and outdoor fire protection facilities of networked units. Specific information can be found in Table B.1 of GB 25506-2010.

content;

e) Information on the regular inspection and maintenance of fire protection facilities of networked units; see Table B.1 for details in GB 25506-2010.

Information on regular inspections and maintenance;

f) Daily fire prevention patrol information of networked units; specific information can be found in Table B.1 of GB 25506-2010, Daily Fire Prevention Patrol Records.

content;

g) Fire information of networked units; details are provided in Table B.1 of GB 25506-2010.

h) Information on the operational status of fire protection facilities of networked units, for details please refer to Table A.1 in GB 25506-2010.

4.5 The software should have classification, retrieval, and statistical functions, and should generate corresponding statistical reports. For fire alarm information and fire protection equipment of networked units...

The operational status information should be searched and statistically analyzed using the following search terms.

a) Date;

b) Name of the unit connected to the network;

c) Categories of networked units;

d) The region to which the networked unit belongs;

e) Building category;

f) Building area;

g) Fire compartments in buildings;

h) Building usage;

i) Building structure type;

j) Types of building fire protection facilities;

k) Types of building fire protection system components;

l) Name of the manufacturer of the building fire protection facilities;

m) Name of the manufacturer responsible for the maintenance and repair of building fire protection facilities.

4.6 The software should have the functions of archiving and printing statistical reports (see 4.5).

4.7 The software should have the function of querying audio and video recording information and information processing records during the acceptance process.

4.8 The software should have information on the number of networked units connected to the application support platform, the type and quantity of fire protection facilities, their online status, and the types and numbers of alarms.

It has the function of statistical analysis of quantity, operation status, etc.

4.9 The software should have information on the number of registered users on each application platform connected to the application support platform, the information uploaded, received, and processed by users, and other relevant data.

It has the function of statistical analysis of line conditions, etc.

4.10 The software should have the function of statistical analysis of the amount of information exchanged with other systems or platforms outside the system.

5 Conformity Assessment

5.1 The user documentation for the software shall comply with the provisions of 5.2 in GB/T 25000.51-2016.

5.2 Conduct a conformity assessment of the software according to the requirements of Chapter 7 of GB/T 25000.51-2016, and verify whether the software's functions comply with Chapter 4.

The provisions of the chapter.