List of drafts

prEN 12896-7 Public enquiry

Comment end date 2026-02-01

Public transport - Reference data model - Part 7: Driver management

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 European 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, 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 7: Driver management incorporates the following data packages: - Driver Scheduling; Rostering; - Personnel Disposition; - Driver Control Actions. This document itself is composed of the following parts: - Main document (normative) presenting the data model for the concepts shared by the different domains covered by Transmodel, - 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; and - Annex C (informative), indicating the data model evolutions.

Read draft and comment View

prEN 12896-4 Public enquiry

Comment end date 2026-02-01

Public transport - Reference data model - Part 4: Operations monitoring and control

This document incorporates the following main data packages: - Dated Production Components; - Call; - Dated Call; - Production Plan; - Detecting & Monitoring; - Situation; - Messaging; - Control Action; - Operational Event & Incident; - Facility Monitoring & Availability; - Occupancy. It is composed of the following parts: - main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative); - Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative); - Annex B presenting the model evolution (informative); - Annex C detailing the mapping to DATEX-II and SIRI (informative). - Annex D, providing details of the significant technical changes between this document and EN 12896 4:2019 (informative).

Read draft and comment View

prEN 12896-5 Public enquiry

Comment end date 2026-02-01

Public transport - Reference data model - Part 5: Fare management

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 standard, 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 5: Fare Management addresses Fare Information for Public Transport and incorporates the following data packages: - Fare Structure; - Access Right Assignment; - Fare Pricing; - Sales Description; - Sales Transaction; - Fare Roles; - Validation and Control; - Explicit Frames for Fares. This document itself is composed of the following parts: - Main document (normative) representing the data model for the concepts shared by the different fare domains covered by Transmodel, - 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 the "Common Concepts" domain, particularly useful for parts 4 to 8 of the Public Transport Reference Data Model, Annex C (informative), indicating the data model evolutions from previous versions of Transmodel (EN 12896:2006).

Read draft and comment View

prEN 12896-3 Public enquiry

Comment end date 2026-02-01

Public transport - Reference data model - Part 3: Timing information and vehicle scheduling

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, EN12896, known as Transmodel V5.1, - CEN EN 28701, known as IFOPT, incorporating the requirements of - EN 15531-1 to -3 and TS 15531-4 and -5: Service interface for real-time information relating to public transport operations (SIRI), - TS 16614-1 and 2: Network and Timetable Exchange (NeTEx), in particular, the specific needs for long distance train operation. A 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. In particular, a Reference Data Model kernel is described, referring to the data domain: - Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places. This part corresponds to the Transmodel V5.1 Network Description extended by the IFOPT relevant parts. Furthermore, the following functional domains are considered: - 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 - Management Information and Statistics (including data dedicated to service performance indicators). - 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). 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 taken into account in the present standard and of which the data have been represented as the reference data model are described in “Public Transport Reference Data Model - Part 1: Common Concepts”. They are: - Public Transport Network and Stop Description - Timing Information and Vehicle scheduling - Passenger information - Fare Management - Operations monitoring and control - Management information - Personnel Management: Driver Scheduling, Rostering, Personnel Disposition. The aspects of multi-modal operation and multiple operators’ environment are also taken into account. 1.3 Particular Scope of this Document The present European Standard entitled “Reference Data Model for Public Transport – Part 3: Timing Information and Vehicle Scheduling”. incorporates - Journey and Journey Times Model: describes the time-related information at the level of vehicle journeys, i.e. planned timing for the vehicles at day-type level. - Dated Journey Model: describes the link of the timing information for a single operating day and the day type related timing, - Passing Times Model: describes all the different types of passing times for the day type related information, - Vehicle Service Model: describes the information related the work of vehicles as planned for days types. It constitutes the main part of the Vehicle Scheduling Data Domain. - Vehicle Journey Assignment Model: describes operational assignments (advertised vehicle labels, stopping positions) related to particular vehicle journeys. This document itself is composed of the following parts: - Main document (normative) representing the data model, (...)

Read draft and comment View

prEN 12896-6 Public enquiry

Comment end date 2026-02-01

Public transport - Reference data model - Part 6: Passenger information

The document incorporates the following main data packages: - Trip Description; - Passenger Information Queries. It is composed of the following parts: - main document representing the data model for the concepts shared by the different fare domains covered by Transmodel (normative); - Annex A, containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with the definitions (normative); - Annex B presenting the model evolution (informative). - Annex C, providing details of the significant technical changes between this document and EN 12896 6:2019 (informative).

Read draft and comment View

prEN 12896-2 Public enquiry

Comment end date 2026-02-01

Public transport - Reference data model - Part 2: Public transport network

This document incorporates the following main data packages: - Network Description; - Fixed Object; - Tactical Planning Components; - Explicit Frame. It is composed of the following parts: - main document representing the data model for the concepts shared by the different domains covered by Transmodel (normative); - Annex A containing the data dictionary and attribute tables, i.e. the list of all the concepts presented in the main document together with their definitions (normative); - Annex B presenting the model evolution (informative). - Annex C, providing details of the significant technical changes between this document and EN 12896-2:2016 (informative).

Read draft and comment View

prEN 12896-1 Public enquiry

Comment end date 2026-02-01

Public transport - Reference data model - Part 1: Common concepts

1.1 General scope of the Standard The main objective of this European Standard is to present the Public Transport Reference Data Model based on: - the Public Transport Reference Data Model published 2006 as EN12896 and known as Transmodel V5.1, - the model for the Identification of Fixed Objects for Public transport, published 2009 as EN 28701and known as IFOPT, incorporating the requirements of - EN15531-1 to 3 and TS15531-4 and 5: Service interface for real-time information relating to public transport operations (SIRI), - TS16614-1 and 2: 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 understanding and use of the model, - the data model is entirely described in UML. In particular, a Reference Data Model kernel is described, referring to the data domain: - Network Description: routes, lines, journey patterns, timing patterns, service patterns, scheduled stop points and stop places. This part corresponds to the network description as in Transmodel V5.1 extended by the relevant parts of IFOPT. Furthermore, the following functional domains are considered: - Timing Information and Vehicle Scheduling (runtimes, vehicle journeys, day type-related vehicle schedules) - Passenger Information (planned and real-time) - Operations Monitoring and Control: operating day-related data, vehicle follow-up , control actions - Fare Management (fare structure and access rights definition, sales, validation, control) - Management Information and Statistics (including data dedicated to service performance indicators). - 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). 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 1.2.1 Public transport network and stop description The reference data model includes entity definitions for different types of points and links as the building elements of the topological network. Stop points, timing points and route points, for instance, reflect the different roles one point may have in the network definition: whether it is used for the definition of (topological or geographical) routes, as a point served by vehicles when operating on a line, or as a location against which timing information like departure, passing, or wait times are stored in order to construct the timetables. The line network is the fundamental infrastructure for the service offer, to be provided in the form of vehicle journeys which passengers may use for their trips. The main entities describing the line network in the reference data model are the line, the route and the journey pattern, which refer to the concepts of an identified service offer to the public, the possible variants of itineraries vehicles would follow when serving the line, and the (possibly different) successions of stop points served by the vehicles when operating on the route. The functional views of the network are described as layers. A projection is a mechanism enabling the description of the correspondence between the different layers. This mapping between the layers is particularly useful when spatial data from different environments (sources, functional domains) have to be combined. An example of such a situation is the mapping of the public transport network on the road network. (...)

Read draft and comment View

prEN ISO 24223 Public enquiry

Comment end date 2026-02-03

Milk and milk products - Guidance on sample preparation for physical and chemical testing (ISO/DIS 24223:2025)

This document gives guidance on the sample preparation of milk and milk products for physical and chemical analysis, including analysis by applying instrumental methods. This document describes the (sub)sampling, and sample preparation steps carried out after sampling according to ISO 707 | IDF 50 (1) and prior to method-specific sample preparations, e.g. as with analytical methods listed in References (2) to (21). NOTE Analysis on volatile substances, minor components or allergens can require additional precautionary measures in sample preparation in order to avoid loss of or contamination with one or more target analytes.

Read draft and comment View

prEN ISO 11300-4 Public enquiry

Comment end date 2026-02-03

Piping systems for rehabilitation of underground drains, sewers and water supply networks - Part 4: Thermoplastic composite materials (ISO/DIS 11300‑4:2025)

This document specifies requirements and test methods for pipes and fittings which are part of piping systems for the renovation of underground non-pressure drainage and sewerage networks. It is applicable to pipes, fittings and assemblies, made from thermoplastic composite materials, as manufactured and as installed. It is not applicable to the existing pipeline. It is applicable to technique families for renovation: — lining with spirally-wound (SWO) pipes; — lining with a rigidly anchored plastic inner layer (RAPL). and intended to be used at an operating temperature of 20 °C as the reference temperature. In the case of lining with SWO pipes, where the pipes, are formed on site, to a fixed or variable diameter, by spirally winding and jointing a pre-manufactured profiled plastics strip, this document applies to, strips made of unplasticized poly(vinyl chloride) (PVC U), or of polyethylene (PE), with or without steel stiffening elements, and installed with or without integral locking mechanism. In the case of lining with RAPL, where a single rigid annulus of structural cementitious grout is formed behind a plastics inner layer serving as permanent formwork anchored to the grout. This document applies to integrally joined profiled plastics strips of PVC-U or PE or studded sheets of PE, and grout systems with or without steel reinforcement. It does not apply to the structural design of the lining system. NOTE Systems with multiple annuli are available, but these are controlled by patent rights and not covered by this document.

Read draft and comment View

prEN ISO 9994 Public enquiry

Comment end date 2026-02-03

Lighters - Safety specifications (ISO/DIS 9994:2025)

This document specifies requirements for lighters to ensure a reasonable degree of safety for normal use or reasonably foreseeable misuse of such lighters by users. This document applies to all flame-producing products commonly known as cigarette lighters, cigar lighters and pipe lighters. It does not apply to matches and flame-producing products intended solely for igniting materials other than cigarettes, cigars, and pipes.

Read draft and comment View

prEN 302 194-1 V2.0.0 (2025-11) Public enquiry

Comment end date 2026-02-01

Navigation radars used on inland waterways; Harmonised Standard for access to radio spectrum; Part 1: Magnetron Radars

Read draft and comment View

prEN IEC 60068-2-64:2025 Public enquiry

Comment end date 2026-01-30

Environmental testing - Part 2-64: Tests - Test Fh: Vibration, broadband random and guidance

Read draft and comment View

prEN IEC 61300-3-48:2025 Public enquiry

Comment end date 2026-01-30

Fibre optic interconnect devices and passive components - Basic test and measurement procedures - Part 3-48: Examinations and measurements - Spring compression force of the coupling sleeve for rectangular ferrule multi-fibre connectors

Read draft and comment View

prEN 3475-203 Public enquiry