SZDB/Z 116.1—2014 Technical Specification for Elevator Operation Monitoring System (II)

Shenzhen Municipal Standardization Guiding Technical Document SZDB/Z 116.1— 2014 **1** **Overall Architecture** **1.1** **Technical System Architecture** The overall architecture of the elevator operation monitoring system is divided into the perception layer, transmission layer, support layer, and application layer. — Perception layer: responsible for collecting data related to elevator operation and human behavior. — Transmission layer: responsible for transmitting various monitoring data collected by the perception layer to the data aggregation node of the support layer. The system constructor shall select an appropriate transmission network based on the transmission traffic and security confidentiality requirements of various monitoring data to ensure reliable data transmission. — Support layer: responsible for the aggregation, concentration, and upload of elevator operation monitoring data. — Application layer: supports the specific businesses of various market entities, among which supervision applications, rescue applications, and public applications are the key business application functions of the elevator monitoring system. Other applications also include maintenance unit applications, manufacturer applications, user unit applications, and inspection unit applications. **1.2** **Overall System Structure** The elevator operation monitoring system consists of three major parts: the municipal platform, the enterprise platform, and the front-end system. **1.2.1** **Municipal Platform** A central platform that comprehensively monitors and utilizes elevator operation data within the city (district) to provide services, composed of a data aggregation center and a business application platform. The municipal platform can connect through the data aggregation center to obtain the city-wide elevator basic data stored in the supervision database and the elevator monitoring data of enterprise subsystems, to ensure the normal operation and service provision of the monitoring system. — Data aggregation center: aggregates city-wide elevator operation monitoring data from various enterprise subsystems for use by the business application platform. — Business application platform: provides market entities with public business services related to elevator monitoring by utilizing data from the data aggregation center, mainly including elevator supervision applications, rescue applications, and public application service functions. **1.2.2** **Enterprise Platform** A back-end management platform used by enterprises undertaking elevator operation monitoring construction to monitor and control all their installed and commissioned front-end systems. The enterprise platform shall include at least two parts: a data aggregation node and mobile application services. — Data aggregation node: processes and aggregates the operation monitoring data of the front-end systems connected to it. The data aggregation node shall provide a data interface to the municipal platform in accordance with the specified communication protocol, ensuring that the municipal platform obtains the operation monitoring data of each elevator in a timely manner. — Mobile application services: an essential business of the enterprise platform for mobile clients, used to accept public inquiries and supervision in accordance with public and government requirements. **1.2.3** **Front-end System** A general term for front-end devices installed in or attached to elevators to collect various elevator operation monitoring data. The front-end system includes data acquisition devices and sensors or sensing devices that provide monitoring data. The acquisition device is responsible for collecting data from various sensors and, after necessary logic processing, transmitting it to the enterprise platform. **1.2.4** **Enterprise Subsystem** Composed of an enterprise platform and all front-end systems managed and connected by that enterprise platform. The enterprise platform may connect to one or more front-end systems from different enterprises, and communication between the enterprise platform and each connected front-end system shall be normal. **2** **Basic System Functional Requirements** **2.1** **Supervision Functional Requirements** Supervision functions shall include enterprise platform quality monitoring, rescue supervision functions, original event record query, and public complaint functions. **2.2** **Rescue Application Functional Requirements** Rescue applications shall include rescue resource management, rescue alarm receiving functions (telephone distress call receiving, manual distress call receiving, automatic distress call receiving), call validity confirmation functions, rescue dispatch functions, progress display functions, and rescue recording functions. **2.3** **Public Application Functional Requirements** The monitoring system shall provide the public with a mobile client through which the public can provide feedback on elevator operation conditions and query elevator operation data. The monitoring system shall provide the public with services such as telephone distress calls, manual distress calls, automatic distress calls, safety knowledge learning during elevator rides, and passenger reassurance in emergencies. **2.4** **User Unit Application Functional Requirements** The monitoring system shall provide user units with a client for receiving services provided by the monitoring system, such as dynamic monitoring, rescue management, maintenance management, and inspection reminders. **2.5** **Maintenance Unit Application Functional Requirements** The monitoring system shall provide maintenance units with services such as fault reminder services, inspection reminders, maintenance reminders, and maintenance result reporting. **3** **Reliability Requirements** Unless otherwise specified, the false alarm rate for elevator faults shall be less than 3%, and the missed alarm rate shall be less than 1%.