为增加行业管理技术手段，从城市轨道交通运营主管部门的安全监管职责入手，进行了城市轨道交通智能管理系统框架设计。基于行业重点管理事项，梳理了管理系统各模块具体的功能点，形成面向运营安全监管的智能管理系统功能需求调研问卷并在全行业市级城市轨道交通相关单位开展调研。研究表明：①智能管理系统应具备基础信息、客流监管、行车监管、设施设备监管、安全信息管理和应急管理等6个方面共计31个功能点；②公交站点地图显示等2项应采用地图数据采集的方式获取数据，车站客运量等5项应通过接入运营单位生产系统获取数据，安全评估报告管理等6项数据应主要由主管部门填报，其余 18项应采用运营单位填报、主管部门审核的方式进行管理；③车站乘客进出站量、线路客运量和开行列次等功能点应按日统计数据，线网高峰时段最大断面客流量、最大载客率等功能点应按日或按月统计数据，关键设施故障率等功能点应按月统计数据，延误报告阈值设定为15 min，其他功能点应在内容有更新时或按年度填报数据。

In order to increase the technical means of industry management, the framework design of an intelligent management system for urban rail transit was carried out starting from the safety supervision and management responsibilities of industry regulatory departments of urban rail transit. Based on key management issues in the industry, the specific functional points of each module of the management system were sorted out, and a survey questionnaire on the functional requirements of intelligent man‐agement systems for operational safety supervision was formed. The survey was conducted in relevant units of urban rail transit at the city level throughout the industry. The results show that: ①the intelli‐gent management system should have a total of 31 functional points in 6 aspects, including basic infor‐mation, passenger flow supervision, driving supervision, facility and equipment supervision, safety in‐formation management, and emergency management; ②the data of display of bus stop maps and an‐other item should be obtained through map data collection, while the data of passenger volume of sta‐tion and other 4 items should be obtained through connecting to the production system of the operating unit; the management of safety assessment reports and other 5 items should mainly rely on the compe‐tent department to fill in and submit, while the remaining 18 items should be managed through filling in by the operating unit and reviewing by the competent department; ③the data of functional points such as station entry and exit passenger volume, line passenger volume, and operating train numbers should be counted on a daily basis, the data of maximum cross-sectional passenger flow during peak hours of the network, maximum passenger capacity and other functional points should be counted dai‐ly or monthly, and the data of key facility failure rate and other functional points should be counted monthly; the delay reporting threshold should be set at 15 minutes, and the data of other functional points should be reported when the content is updated or on an annual basis.