T/HNIT 1-2021 Technical Specifications for the Information Platform of the Enterprise Dual Prevention System
T/HNIT 1-2021
Basic Information
Scope
Scope: This document specifies the terms and definitions, abbreviations, construction principles, system framework, functional specifications, data specifications, operation indicators, and information security requirements of the enterprise dual-prevention information platform (hereinafter referred to as the dual-prevention information platform). This document is applicable to enterprises and related parties in the design, implementation, acceptance, and operation and maintenance of the dual-prevention information platform; Main technical content: 6.1 Technical framework The dual-prevention information platform should coordinate with the enterprise's safety production involving regional sites, equipment facilities, post operations, basic management, and work activities. It should also provide early warning, statistical analysis, and decision-support for risk-grading control and hidden danger inspection and treatment activities. In terms of implementation, it is recommended to implement risk and hidden danger control and treatment at four control levels: enterprise, department/workshop, team, and post, and to classify, grade, and specialize in risk and hidden danger control and treatment according to different professions. 6.2 Basic requirements of the dual-prevention information platform 6.2.1 It should have functions such as enterprise basic information, risk-grading control, hidden danger inspection and treatment, hidden danger alerts, and statistical analysis. 6.2.2 It should have functions such as monitoring and evaluating the operation of enterprise risk-grading control and hidden danger inspection and treatment. 6.2.3 It should have functions such as uploading and downloading information, tracking and alerting for enterprise hidden danger inspection and treatment. 6.2.4 Relevant modules should have functions such as adding, deleting, modifying, querying, importing, and exporting. 6.2.5 It should adopt a B/S architecture. 6.2.6 It should meet