Toimialayhteisöt

 

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.

 

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, (...)

 

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).

 

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).

 

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. (...)

 

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).

 

This document specifies requirements and test methods for pipes and fittings which are part of piping systems for the rehabilitation, by means of renovation and trenchless replacement, of underground non-pressure drains and sewers 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 the following technique families for renovation: and intended to be used at a service temperature not exceeding 45 °C according to material as follows: in both cases with re-rating factors on mechanical characteristics for service temperatures in excess of 35 °C determined by dedicated type testing. 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.

 

This document specifies a test method for the determination of gross beta activity concentration in non-saline waters. The method covers non-volatile radionuclides with maximum beta energies of approximately 0,3 MeV or higher. Measurement of low energy beta emitters (e.g. 3H, 228Ra, 210Pb, 14C, 35S and 241Pu) and some gaseous or volatile radionuclides (e.g. radon and radioiodine) might not be included in the gross beta quantification using the test method described in this document. This test method is applicable to the analysis of raw and drinking waters. The range of application depends on the amount of total soluble salts in the water and on the performance characteristics (background count rate and counting efficiency) of the counter used. It is the laboratory's responsibility to ensure the suitability of this method for the water samples tested.

 

ISO/IEC 29146:2024 defines and establishes a framework for access management (AM) and the secure management of the process to access information and Information and Communications Technologies (ICT) resources, associated with the accountability of a subject within some context. ISO/IEC 29146:2024 provides explanations about related architecture, components and management functions and concepts, terms and definitions applicable to distributed access management. The subjects involved in access management might be uniquely recognized to access information systems, as defined in ISO/IEC 24760.

 

This document gives guidance on developing, managing and implementing public warning before, during and after incidents. This document is applicable to any organization responsible for public warning. It is applicable at all levels, from local up to international. Before planning and implementing the public warning system, the risks and consequences of potential hazards are assessed. This process is not part of this document.

 

This document specifies a method of measuring the dimensions of conductors and cables. It is used together with EN 3475-100.

 

This document specifies a range of cable outlets, style K, 90°, shielded, sealed, self-locking (anti-rotational), for heat shrinkable boot, and/ or metallic bands for use under the following conditions: The mating connectors are listed in EN 3660-002. Temperature range, Class N: -65 °C to 200 °C; Class K: -65 °C to 260 °C; Class W: -65 °C to 175 °C; Class T: -65 °C to 175 °C (Nickel PTFE plating); Class Z: -65 °C to 175 °C (Zinc nickel plating). Class V: -65 °C to 175 °C (Tin zinc plating non reflective). Class D: -65 °C to 175 °C (Tin zinc plating dark non reflective). Associated electrical accessories are specified in EN 3660-033 Metallic band (for shield termination). These cable outlets are designed for termination of overall shielding braid and/or individual cable shields. They accommodate/permit the termination of heat shrinkable boots.

 

This document defines a range of cable outlets, style K, straight, shielded, sealed, self-locking (anti-rotational), heat shrinkable boot, and/or metallic bands for use under the following conditions: Associated electrical connector(s) EN 3660-002. Temperature range Class N: -65 °C to 200 °C; Class K: -65 °C to 260 °C; Class W: -65 °C to 175 °C; Class T: -65 °C to 175 °C (Nickel PTFE plating); Class Z: -65 °C to 175 °C (Zinc nickel plating). Class V: -65 °C to 175 °C (Tin zinc plating non reflective); Class D: -65 °C to 175 °C (Tin zinc plating dark non reflective). Associated electrical accessories: EN 3660-033 Metallic band (for shield termination). These cable outlets are designed for termination of overall shielding braid and/or individual cable shields. They accommodate/permit the termination of heat shrinkable boots.

 

This document describes a highly specific method for the enumeration of Escherichia coli (E. coli) in water. The method is based on membrane filtration followed by culture at 44 °C on chromogenic agar medium containing an ingredient for the detection of the enzyme ß-glucuronidase, and calculation of the number of target organisms in the sample[5,6,13]. Because of the high specificity of the method, this document is suitable for waters with high levels of background bacteria, such as surface waters including bathing water and wastewater provided that they contain little particulate or colloidal matter relative to the E. coli concentration. The method can be used for fresh water and, with an adaptation, for marine water. E. coli strains which do not grow at 44 °C and those that are ß-glucuronidase negative, such as E. coli O157, will not be detected as E. coli by this method. This method is not applicable to the enumeration and detection of coliform bacteria other than E. coli.

 

In order to reduce the impact of predictable natural hazards on railway operation, this document specifies a general concept and basic requirements for the planning of railway operation in the events of predictable natural hazards, focusing on heavy rainfall and strong wind. The given concepts and basic requirements do not apply to regions where the consequences of the addressed predictable hazards for railway operation are low or non-existent. The definition of such regions is out of the scope of this document. This document includes measures directly related to railway operation to reduce the impact in the events of predictable natural hazards. Furthermore, this document does not include specific measures which ensure passenger safety or which provide protection against railway-operational damage caused by the predictable natural hazards. Therefore, residual risk can remain.

 

This document sets out the fundamental principles of determining the groundwater remediation targets for post in situ leach (also referred as in situ recovery) uranium mining. It also delineates the environmental investigation requirements for groundwater remediation, stakeholder identification and engagement, groundwater remediation technical options and their analysis of effectiveness, and procedure for the determination of groundwater remediation target values. This document is applicable to controlling and mitigating groundwater impact and conducting groundwater remediation for in situ leach uranium mining. It can also serve as a reference for contamination control, mitigation and remediation of groundwater for other in situ leach metal mining projects.

 

This document specifies basic control strategies, minimum functional requirements, basic driver interface elements, and test procedures for verifying the system requirements for collision evasive lateral manoeuvre systems (CELM). A CELM is a safety system aimed at supporting the driver’s vehicle operation by avoiding collisions with objects in the forward path of the vehicle. When a collision is predicted, the CELM controls lateral movement of the vehicle by generating yaw moment. The lateral control manoeuvres can be performed automatically by CELM or can be initiated by the driver and supported by CELM. Specific methods for object detection and other environmental perception technologies are not described in this document. This document applies to light vehicles[1] and heavy trucks[1]. Vehicles equipped with trailers are not within the scope of this document.

 

 

This document describes an analytical procedure for the determination of main components in Li composite oxides for Li-ion batteries (LiB). These are in particular the elements: Lithium, cobalt, iron, manganese, nickel, phosphorus, titanium and aluminium, depending on the composite oxide of interest. The determination is applicable to all types of LiBs (table 1). The determination is performed by optical emission spectrometry with inductively coupled plasma (ICP OES) using an internal standard. The method of atomic emission spectrometry with inductively coupled plasma (ICP AES) is interchangeable with ICP OES. This test is recommended as the preferred method for determining the stoichiometric composition of several elements in LiBs. This standard establishes a test procedure for a high precision determination of stoichiometric composition of the elements in LiBs.