BSI PD CEN/TS 17241:2019
$198.66
Intelligent transport systems. Traffic management systems. Status, fault and quality requirements
| Published By | Publication Date | Number of Pages |
| BSI | 2019 | 70 |
This document:
-
illustrates quality and performance criteria, and approaches to their evaluation, for the operation of traffic management systems, including factors affecting the effective integration of field and centre systems and services, and
-
specifies a data model for system status and faults of components of traffic management systems.
This document provides supporting information in a use case for the use of the quality and performance criteria, considering design, procurement, and performance management.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 2 | undefined |
| 10 | 1 Scope 2 Normative references 3 Terms and definitions |
| 11 | 4 Symbols and abbreviations |
| 12 | 5 Quality and performance criteria 5.1 Quality: fitness for purpose |
| 13 | 5.2 System quality 5.2.1 Availability and uptime 5.2.1.1 General |
| 14 | 5.2.1.2 Time 5.2.1.3 System |
| 15 | 5.2.1.4 Working properly |
| 16 | 5.2.2 System compatibility and integration 5.2.3 Configurability of systems |
| 17 | 5.2.4 Security |
| 18 | 5.2.5 Continuity of service and future proofing |
| 19 | 5.3 Device quality 5.3.1 Physical robustness 5.3.2 Failure modes |
| 20 | 5.3.3 Reliability and maintainability |
| 21 | 5.4 Functional quality 5.4.1 Stated requirements and compliance 5.4.2 Functional effectiveness |
| 22 | 5.4.3 Functional integration |
| 23 | 5.4.4 Usability 5.5 Data quality 5.5.1 Accuracy and related concepts |
| 25 | 5.5.2 Timeliness and granularity 5.5.3 Spatio-temporal granularity |
| 26 | 5.5.4 System data |
| 27 | 5.6 Quality and performance management 5.6.1 Lifecycle quality 5.6.1.1 Quality planning 5.6.1.2 Quality during procurement |
| 28 | 5.6.1.3 Quality during operations |
| 29 | 5.6.2 Quality evaluation |
| 30 | 5.6.3 Risk management |
| 31 | 6 System status and faults data model 6.1 Overview 6.2 General requirements |
| 32 | 6.3 Modelling principles 6.3.1 Technical modelling principles 6.3.2 Semantic modelling principles 6.4 Ā«D2PackageĀ» DevicePublication 6.4.1 Overview |
| 33 | 6.4.2 Semantics 6.4.2.1 DevicePublication class 6.4.2.2 DeviceTable class 6.4.2.3 Device class |
| 34 | 6.5 Ā«D2PackageĀ» StatusPublication 6.5.1 Overview |
| 35 | 6.5.2 Semantics 6.5.2.1 StatusPublication class 6.5.2.2 StatusOfAllDevicesFromTable class 6.5.2.3 Status class |
| 36 | 6.5.2.4 OperationalState class 6.6 Ā«D2PackageĀ» FaultPublication 6.6.1 Overview |
| 38 | 6.6.2 Semantics 6.6.2.1 FaultPublication class 6.6.2.2 FaultsOfAllDevicesFromTable class |
| 39 | 6.6.2.3 The AllFaultsOfASingleDevice class 6.6.2.4 Fault class 6.7 Ā«D2PackageĀ» Classes 6.7.1 Overview |
| 41 | 6.7.2 Semantics 6.7.2.1 Reference-related classes 6.7.2.2 CatalogueInformation class 6.8 Ā«D2PackageĀ» DataTypes |
| 43 | Annex A (normative)Status and fault data dictionary A.1 Disclaimer A.2 Overview |
| 44 | A.3 Data dictionary of Ā«D2ClassĀ» for āFaultAndStatusā A.3.1 āClassesā package A.3.1.1 Location of the āClassesā package |
| 45 | A.3.1.2 āClassesā package classes A.3.1.3 āClassesā package association roles |
| 46 | A.3.1.4 āClassesā package attributes A.3.2 āDevicePublicationā package A.3.2.1 Location of āDevicePublicationā package |
| 47 | A.3.2.2 āDevicePublicationā package classes A.3.2.3 āDevicePublicationā package association roles |
| 48 | A.3.2.4 āDevicePublicationā package attributes A.3.3 āFaultPublicationā package A.3.3.1 Location of āFaultPublicationā package |
| 49 | A.3.3.2 āFaultPublicationā package classes A.3.3.3 āFaultPublicationā package association roles |
| 50 | A.3.3.4 āFaultPublicationā package attributes A.3.4 āStatusPublicationā package A.3.4.1 Location of the āStatusPublicationā package |
| 51 | A.3.4.2 āStatusPublicationā package classes A.3.4.3 āStatusPublicationā package association roles |
| 52 | A.3.4.4 āStatusPublicationā package attributes A.4 Data Dictionary of Ā«D2DatatypeĀ» for āFaultAndStatusā A.4.1 General A.4.2 The Ā«D2DatatypeĀ» āObjectIdentifierā |
| 53 | A.5 Data Dictionary of Ā«D2EnumerationĀ» for āFaultAndStatusā A.5.1 General A.5.2 The Ā«D2EnumerationĀ» āDeviceOrSystemTypeEnumā A.5.3 The Ā«D2EnumerationĀ» āFaultImpactOnDataEnumā |
| 54 | A.5.4 The Ā«D2EnumerationĀ» āFaultSeverityEnumā A.5.5 The Ā«D2EnumerationĀ» āFaultTypeEnumā |
| 55 | A.5.6 The Ā«D2EnumerationĀ» āFaultUrgencyEnumā A.5.7 The Ā«D2EnumerationĀ» āGeneralDeviceStatusEnumā |
| 56 | A.5.8 The Ā«D2EnumerationĀ» āOperationalDeviceStateEnumā |
| 58 | Annex B (normative)ASN.1 specifications B.1 Introduction B.1.1 General B.1.2 Automatic creation of ASN.1 code from xsd code B.1.3 ASN.1 module TmsStatusFault |
| 59 | B.1.4 ASN.1 module PointLocation B.1.5 ASN.1 module DatexCommon B.1.6 ASN.1 module XSD B.1.7 ASN.1 module TmsMessageSet |
| 61 | Annex C (normative)Management of electronic traffic regulations C.1 Justification C.2 Status and faults |
| 62 | Annex D (normative)Electronic attachment |
| 63 | Annex E (informative)Example use case E.1 Introduction E.2 Scenario ātunnel projectā E.3 Use case ātunnel projectā E.3.1 Challenge E.3.2 Response |
| 64 | E.3.3 Mechanisms E.3.3.1 System Quality |
| 65 | E.3.3.2 Device Quality |
Related products
-
BSI PD CEN/TR 17868:2022
Intelligent transport systems. EU-ICIP. ITS standards deliverables (2022) Published By Publication Date Number of Pagesā¦
