Standartų projektų sąrašas

Paieškos frazė

Išplėstinė paieška

Žymuo

Direktyvos

Organizacija

ICS

Technikos komitetas

Užsienio komitetas

Darbo grupė

Etapas

Būsena

Komentavimo data

iki

Rezultatai

EN ISO 14819-2:2021/prA1:2025 Viešoji apklausa

Komentavimo iki data 2026-02-01

Intelektinės transporto sistemos. Informaciniai pranešimai apie eismą ir keliones, parengti naudojant pranešimų apie eismą kodavimą. 2 dalis. Įvykių ir informacijos kodai, skirti radijo ryšio duomenų sistemai. Pranešimų apie eismą kanalas (RDS-TMC), naudojantis ALERT-C. 1 keitinys (ISO 14819-2:2021/DAmd1:2025)

Skaityti, komentuoti projektą Peržiūrėti metaduomenis

prEN 12896-7 Viešoji apklausa

Komentavimo iki data 2026-02-01

Viešasis transportas. Pamatinių duomenų modelis. 7 dalis. Vairuotojų darbo valdymas

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.

Skaityti, komentuoti projektą Peržiūrėti metaduomenis

prEN 12896-4 Viešoji apklausa

Komentavimo iki data 2026-02-01

Viešasis transportas. Pamatinių duomenų modelis. 4 dalis. Veikimo stebėjimas ir valdymas

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

Skaityti, komentuoti projektą Peržiūrėti metaduomenis

prEN 12896-5 Viešoji apklausa

Komentavimo iki data 2026-02-01

Viešasis transportas. Pamatinių duomenų modelis. 5 dalis. Mokėjimo už važiavimą valdymas

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

Skaityti, komentuoti projektą Peržiūrėti metaduomenis

prEN 12896-3 Viešoji apklausa

Komentavimo iki data 2026-02-01

Viešasis transportas. Pamatinių duomenų modelis. 3 dalis. Laiko informacija ir transporto priemonių tvarkaraščiai

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

Skaityti, komentuoti projektą Peržiūrėti metaduomenis

prEN 12896-6 Viešoji apklausa

Komentavimo iki data 2026-02-01

Viešasis transportas. Pamatinių duomenų modelis. 6 dalis. Informacija keleiviams

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

Skaityti, komentuoti projektą Peržiūrėti metaduomenis

prEN 12896-2 Viešoji apklausa

Komentavimo iki data 2026-02-01

Viešasis transportas. Pamatinių duomenų modelis. 2 dalis. Viešojo transporto tinklas

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

Skaityti, komentuoti projektą Peržiūrėti metaduomenis

prEN 12896-1 Viešoji apklausa

Komentavimo iki data 2026-02-01

Viešasis transportas. Pamatinių duomenų modelis. 1 dalis. Bendrosios sąvokos

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

Skaityti, komentuoti projektą Peržiūrėti metaduomenis

EN 17240:2024/prA1 Viešoji apklausa

Komentavimo iki data 2025-12-21

Intelektinės transporto sistemos. El. sauga. Pagalbos iškvietos tiesioginio sujungimo atitikties tikrinimas, taikomas IMS paketinio ryšio sistemoms

This document defines the key actors in the eCall chain of service provision using IMS over packet switched networks (such as LTE/4G) as: 1) In-vehicle system (3.20) (IVS)/vehicle, 2) Mobile network Operator (MNO), 3) Public safety answering point (3.27) (PSAP), and to provide conformance tests for actor groups 1) - 3). NOTE 1 Conformance tests are not appropriate nor required for vehicle occupants (3.36), although they are the recipient of the service. NOTE 2 Third party eCall systems (TPS eCall) are not within the scope of this deliverable. This is because the core TPS-eCall (3.32) standard (EN 16102) does not specify the communications link between the vehicle and the TPS service provider (3.29). NOTE 3 These conformance tests are based an the appropriate conformance tests from EN 16454 which was published before Internet Protocol multimedia Systems (IMS) packet switched networks were available. This deliverable therefore replicates the appropriate tests from EN 16454 (and acknowledge their source); adapt and revise Conformance Test Protocols (CTP) from EN 16454 to an IMS paradigm; or provide new additional tests that are required for the IMS paradigm. Some 14 112-eCall (Pan European eCall) tests provided in EN 16454 are specific to GSM/UMTS circuit switched communications and not appropriate for the IMS paradigm and are therefore excluded from this deliverable. This document therefore provides a suite of ALL conformance tests for IVS equipment, MNO's, and PSAPS, required to ensure and demonstrate compliance to CEN/TS 17184. NOTE 4 Because in the event of non-viability or non-existence of an IMS supporting network at any particular time/location, IMS-eCall systems revert to CS networked eCall systems eCall via GSM/UMTS, IVS and PSAPs need to support, and prove compliance to both IMS and CS switched networks. The Scope covers conformance testing (and approval) of new engineering developments, products and systems, and does not imply testing associated with individual installations in vehicles or locations.

Skaityti, komentuoti projektą Peržiūrėti metaduomenis

EN 17184:2024/prA1 Viešoji apklausa

Komentavimo iki data 2025-12-21

Intelektinės transporto sistemos. El. sauga. Aukšto lygmens taikomųjų programų protokolai (HLAP), skirti pagalbos iškvietai per paketinio perdavimo tinklus, naudojant IP multimedijos posistemį (IMS)

In respect of pan European eCall (operating requirements defined in EN 16072), this document defines the high level application protocols, procedures and processes required to provide the eCall service via a packet switched wireless communications network using IMS (IP Multimedia Subsystem) and wireless access (such as LTE, NR and their successors). This document assumes support of eCall using IMS over packet switched networks by an IVS and a PSAP and further assumes that all PLMNs available to an IVS at the time an eCall or test eCall is initiated are packet switched networks. Support of eCall where eCall using IMS over packet switched networks is not supported by an IVS or PSAP is out of scope of this document. At some moment in time packet switched networks will be the only Public Land Mobile Networks (PLMN) available. However as long as GSM/UMTS PLMNs are available (Teleservice 12/TS12) ETSI TS 122 003 will remain operational. Both the use of such PLMNs and the logic behind choosing the appropriate network in a hybrid situation (where both packet-switched and circuit-switched networks are available) are out of scope of this document. NOTE 1 The objective of implementing the pan-European in-vehicle emergency call system (eCall) is to automate the notification of a traffic accident, wherever in Europe, with the same technical standards and the same quality of services objectives by using a PLMN (such as ETSI prime medium) which supports the European harmonized 112/E112 emergency number (TS12 ETSI TS 122 003 or IMS packet switched network) and to provide a means of manually triggering the notification of an emergency incident. NOTE 2 HLAP requirements for third party services supporting eCall can be found in EN 16102. This document makes reference to those provisions but does not duplicate them.

Skaityti, komentuoti projektą Peržiūrėti metaduomenis

Būtini slapukai

Statistikos slapukai

El. pašto prenumerata

Išplėstinė paieška

Rezultatai

Greitieji filtrai

Organizacija

Technikos komitetas

ICS