GB/T 26875.5-2026Remote monitoring system for urban fire protection - Part 5: Functional requirements for receiving 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 5 of GB (/T) 26875 "Urban Fire Remote Monitoring Systems". GB (/T) 26875 has the following published... part.

1.General Technical Requirements;

2.Functional Requirements for Communication Service Software;

3.Alarm Transmission Network Communication Protocol;

4.Basic Data Items;

5.Software Functional Requirements;

6.Functional Requirements for Information Management Software;

7.Functional Requirements for Fire Protection Facility Maintenance and Management Software;

8.Monitoring Center External Data Exchange Protocol;

9.User Information Transmission Device;

10.Requirements for fire protection facility information collection devices and interfaces. This document replaces GB/T 26875.5-2011 "Urban Fire Remote Monitoring System Part

5.Functional Requirements for Acceptance Software", and is consistent with... Compared with GB/T 26875.5-2011, apart from structural adjustments and editorial changes, the main technical changes are as follows:

a) The scope has been changed (see Chapter 1, Chapter 1 of the.2011 edition);

4 Functional Requirements

4.1 After the software starts running or after logging in, it should automatically enter the processing state.

4.2 The software should have operation confirmation prompts for parameter configuration, shift handover, on-duty/off-duty status switching, and exit.

4.3 The software interface should be displayed in Chinese and should include text, geographic, and video information. It should also display, but is not limited to, text, geographic, and video information. The following information.

a) Information not accepted;

b) Date and time information;

c) Software version information;

d) Information on the receptionist and reception staff;

e) Information on whether the person handling the transaction is present or absent;

f) Communication connection status information. In the above information,

a) should not be covered.

4.4 When two or more agents are simultaneously online processing information, the software should have functions for assigning unprocessed information to designated seats and for handling information on behalf of others. It can transfer and push information functions.

4.5 There should be instructions on the acceptance process during information processing, and alarm prompts should be given for any violations.

4.6 The display interfaces for text information, geographic information, and video information should have associated operation functions. Newly received letters should be displayed on the text information interface. When processing information, the geographic information display interface and video information display interface should automatically switch to the corresponding geographic location and video interface; in the geographic... When performing a location operation on the text information display interface, the relevant location information should be able to be extracted into the text information display interface.

4.7 The software should be able to record and query the time of arrival and departure of service personnel, the handover time of service personnel, and the duty log, and should have operational functionality. Log viewing functionality. The runtime log should include, but is not limited to, software startup and exit times, parameter configuration modification times and content, and software errors. The system displays the time and content of notifications, as well as the time and status information of changes in communication connection status.

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.