1.1本标准的一般范围本标准的主要目标是根据以下内容提出公共交通参考数据模型:-参考数据模型，EN 12896，称为Transmodel V5.1；-EN 28701:2012，智能交通系统-公共交通-公共交通中固定物体的识别（IFOPT），但请注意，本标准已被撤回，因为本标准成功发布后，本标准的第1部分和第2部分（EN 12896-1:2016和EN 12896-2:2016）中包含了本标准；包括以下要求:-EN 15531-1至-3和CEN\/TS 15531-4和-5:公共交通-公共交通运行实时信息服务接口（SIRI）；-CEN\/TS 16614-1和-2:公共交通-网络和时刻表交换（NeTEx），特别是长途列车运行的具体需求。特别注意数据模型结构和方法:-数据模型以模块化的形式描述，以便于理解和使用该模型；-数据模型完全用UML描述。考虑以下功能域:-网络描述:路线、线路、行程模式、计时模式、服务模式、计划停站点和停站地点；-定时信息和车辆调度（运行时间、车辆行程、与日型相关的车辆调度）；-乘客信息（计划和实时）；-票价管理（票价结构、销售、验证、控制）；-运行监控:运行日相关数据、车辆跟踪、控制措施；-司机管理:-驱动程序调度（与日类型相关的驱动程序调度），-排班（根据某些选择的方法将驾驶员职责按顺序排列），-驾驶人员配置（将逻辑驱动器分配给物理驱动器并记录驱动器性能）；-管理信息和统计（包括专用于服务绩效指标的数据）。将指定专用于覆盖上述域的大多数功能的数据模块。不同的功能域共享几个概念。这个数据域被称为“公共概念”。1.2功能域描述EN 12896-1:2016，公共交通-参考数据模型-第1部分:通用概念中描述了本文件中考虑的不同功能域（以上列举），其中数据已表示为参考模型。1.3本文件的特定范围本文件题为“公共交通-参考数据模型-第4部分:运行监控”包含以下数据包:-过时的生产部件模型；-呼叫模式；-生产计划模型；-监测模型；-控制作用模型；-事件和事件模型；-消息传递模型；-情景模型；以及-设施监测和可用性模型。本部分中表示的数据结构构成了对特定于某个工作日的操作的数据的描述（与为日类型计划的数据不同）。它们参考了EN 12896-1:2016中描述的结构，如版本框架或通用分组机制，但也参考了EN 12896-2:2016和EN 12896-3:2016。本文件由以下部分组成:-主要文件（规范性文件），为域操作监视和控制提供数据模型；-附录A（规范性附录），包含数据字典，即主文件中所有概念和属性表的清单以及定义；-附录B（规范性附录），是对EN 12896-1:2016的补充，尤其适用于公共交通参考数据模型的第4至8部分；-附录C（资料性附录），说明数据模型的演变；以及(.)

1.1 General Scope of the Standard The main objective of the present standard is to present the Reference Data Model for Public Transport, based on: - the Reference Data Model, EN 12896, known as Transmodel V5.1; - EN 28701:2012, Intelligent transport systems - Public transport - Identification of Fixed Objects in Public Transport (IFOPT), although note that this particular standard has been withdrawn as it is now included within Parts 1 and 2 of this standard (EN 12896-1:2016 and EN 12896-2:2016) following their successful publication; incorporating the requirements of: - EN 15531-1 to -3 and CEN/TS 15531-4 and -5: Public transport - Service interface for real-time information relating to public transport operations (SIRI); - CEN/TS 16614-1 and -2: Public transport - Network and Timetable Exchange (NeTEx), in particular the specific needs for long distance train operation. Particular attention is drawn to the data model structure and methodology: - the data model is described in a modular form in order to facilitate the understanding and the use of the model; - the data model is entirely described in UML. The following functional domains are considered: - Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places; - Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type-related vehicle schedules); - Passenger Information (planned and real-time); - Fare Management (fare structure, sales, validation, control); - Operations Monitoring and Control: operating day-related data, vehicle follow-up, control actions; - Driver Management: - Driver Scheduling (day-type related driver schedules), - Rostering (ordering of driver duties into sequences according to some chosen methods), - Driving Personnel Disposition (assignment of logical drivers to physical drivers and recording of driver performance); - Management Information and Statistics (including data dedicated to service performance indicators). The data modules dedicated to cover most functions of the above domains will be specified. Several concepts are shared by the different functional domains. This data domain is called "Common Concepts". 1.2 Functional Domain Description The different functional domains (enumerated above) taken into account in the present document, and of which the data have been represented as the reference model, are described in EN 12896-1:2016, Public transport - Reference data model - Part 1: Common concepts. 1.3 Particular Scope of this Document The present document entitled Public transport - Reference data model - Part 4: Operations monitoring and control incorporates the following data packages: - Dated Production Components MODEL; - Call MODEL; - Production Plan MODEL; - Detecting and Monitoring MODEL; - Control Action MODEL; - Event and Incident MODEL; - Messaging MODEL; - Situation MODEL; and - Facility Monitoring and Availability MODEL. The data structures represented in this part form descriptions of data that are specific to operations for an operational day (as opposed to those planned for day types). They reference to structures as described in EN 12896-1:2016, such as version frames or generic grouping mechanisms, but also to EN 12896-2:2016 and EN 12896-3:2016. This document itself is composed of the following parts: - Main document (normative) presenting the data model for the domain Operations Monitoring and Control; - Annex A (normative), containing the data dictionary, i.e. the list of all the concepts and attribute tables present in the main document together with the definitions; - Annex B (normative), providing a complement to EN 12896-1:2016, particularly useful for parts 4 to 8 of the Public Transport Reference Data Model; - Annex C (informative), indicating the data model evolutions; and (.)