{"id":231692,"date":"2024-10-19T15:05:36","date_gmt":"2024-10-19T15:05:36","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bsi-pd-cen-ts-172412019\/"},"modified":"2024-10-25T09:26:12","modified_gmt":"2024-10-25T09:26:12","slug":"bsi-pd-cen-ts-172412019","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bsi-pd-cen-ts-172412019\/","title":{"rendered":"BSI PD CEN\/TS 17241:2019"},"content":{"rendered":"
This document:<\/p>\n
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<\/p>\n<\/li>\n
specifies a data model for system status and faults of components of traffic management systems.<\/p>\n<\/li>\n<\/ul>\n
This document provides supporting information in a use case for the use of the quality and performance criteria, considering design, procurement, and performance management.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
10<\/td>\n | 1 Scope 2 Normative references 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
11<\/td>\n | 4 Symbols and abbreviations <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | 5 Quality and performance criteria 5.1 Quality: fitness for purpose <\/td>\n<\/tr>\n | ||||||
13<\/td>\n | 5.2 System quality 5.2.1 Availability and uptime 5.2.1.1 General <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 5.2.1.2 Time 5.2.1.3 System <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 5.2.1.4 Working properly <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 5.2.2 System compatibility and integration 5.2.3 Configurability of systems <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 5.2.4 Security <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 5.2.5 Continuity of service and future proofing <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 5.3 Device quality 5.3.1 Physical robustness 5.3.2 Failure modes <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | 5.3.3 Reliability and maintainability <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 5.4 Functional quality 5.4.1 Stated requirements and compliance 5.4.2 Functional effectiveness <\/td>\n<\/tr>\n | ||||||
22<\/td>\n | 5.4.3 Functional integration <\/td>\n<\/tr>\n | ||||||
23<\/td>\n | 5.4.4 Usability 5.5 Data quality 5.5.1 Accuracy and related concepts <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 5.5.2 Timeliness and granularity 5.5.3 Spatio-temporal granularity <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 5.5.4 System data <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 5.6 Quality and performance management 5.6.1 Lifecycle quality 5.6.1.1 Quality planning 5.6.1.2 Quality during procurement <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | 5.6.1.3 Quality during operations <\/td>\n<\/tr>\n | ||||||
29<\/td>\n | 5.6.2 Quality evaluation <\/td>\n<\/tr>\n | ||||||
30<\/td>\n | 5.6.3 Risk management <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 6 System status and faults data model 6.1 Overview 6.2 General requirements <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 6.3 Modelling principles 6.3.1 Technical modelling principles 6.3.2 Semantic modelling principles 6.4 \u00abD2Package\u00bb DevicePublication 6.4.1 Overview <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 6.4.2 Semantics 6.4.2.1 DevicePublication class 6.4.2.2 DeviceTable class 6.4.2.3 Device class <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | 6.5 \u00abD2Package\u00bb StatusPublication 6.5.1 Overview <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | 6.5.2 Semantics 6.5.2.1 StatusPublication class 6.5.2.2 StatusOfAllDevicesFromTable class 6.5.2.3 Status class <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 6.5.2.4 OperationalState class 6.6 \u00abD2Package\u00bb FaultPublication 6.6.1 Overview <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 6.6.2 Semantics 6.6.2.1 FaultPublication class 6.6.2.2 FaultsOfAllDevicesFromTable class <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 6.6.2.3 The AllFaultsOfASingleDevice class 6.6.2.4 Fault class 6.7 \u00abD2Package\u00bb Classes 6.7.1 Overview <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 6.7.2 Semantics 6.7.2.1 Reference-related classes 6.7.2.2 CatalogueInformation class 6.8 \u00abD2Package\u00bb DataTypes <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Annex A (normative)Status and fault data dictionary A.1 Disclaimer A.2 Overview <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | A.3 Data dictionary of \u00abD2Class\u00bb for \u201cFaultAndStatus\u201d A.3.1 \u201cClasses\u201d package A.3.1.1 Location of the \u201cClasses\u201d package <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | A.3.1.2 \u201cClasses\u201d package classes A.3.1.3 \u201cClasses\u201d package association roles <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | A.3.1.4 \u201cClasses\u201d package attributes A.3.2 \u201cDevicePublication\u201d package A.3.2.1 Location of \u201cDevicePublication\u201d package <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | A.3.2.2 \u201cDevicePublication\u201d package classes A.3.2.3 \u201cDevicePublication\u201d package association roles <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | A.3.2.4 \u201cDevicePublication\u201d package attributes A.3.3 \u201cFaultPublication\u201d package A.3.3.1 Location of \u201cFaultPublication\u201d package <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | A.3.3.2 \u201cFaultPublication\u201d package classes A.3.3.3 \u201cFaultPublication\u201d package association roles <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | A.3.3.4 \u201cFaultPublication\u201d package attributes A.3.4 \u201cStatusPublication\u201d package A.3.4.1 Location of the \u201cStatusPublication\u201d package <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | A.3.4.2 \u201cStatusPublication\u201d package classes A.3.4.3 \u201cStatusPublication\u201d package association roles <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | A.3.4.4 \u201cStatusPublication\u201d package attributes A.4 Data Dictionary of \u00abD2Datatype\u00bb for \u201cFaultAndStatus\u201d A.4.1 General A.4.2 The \u00abD2Datatype\u00bb \u201cObjectIdentifier\u201d <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | A.5 Data Dictionary of \u00abD2Enumeration\u00bb for \u201cFaultAndStatus\u201d A.5.1 General A.5.2 The \u00abD2Enumeration\u00bb \u201cDeviceOrSystemTypeEnum\u201d A.5.3 The \u00abD2Enumeration\u00bb \u201cFaultImpactOnDataEnum\u201d <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | A.5.4 The \u00abD2Enumeration\u00bb \u201cFaultSeverityEnum\u201d A.5.5 The \u00abD2Enumeration\u00bb \u201cFaultTypeEnum\u201d <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | A.5.6 The \u00abD2Enumeration\u00bb \u201cFaultUrgencyEnum\u201d A.5.7 The \u00abD2Enumeration\u00bb \u201cGeneralDeviceStatusEnum\u201d <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | A.5.8 The \u00abD2Enumeration\u00bb \u201cOperationalDeviceStateEnum\u201d <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | 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 <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | Annex C (normative)Management of electronic traffic regulations C.1 Justification C.2 Status and faults <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Annex D (normative)Electronic attachment <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | Annex E (informative)Example use case E.1 Introduction E.2 Scenario \u201ctunnel project\u201d E.3 Use case \u201ctunnel project\u201d E.3.1 Challenge E.3.2 Response <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | E.3.3 Mechanisms E.3.3.1 System Quality <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | E.3.3.2 Device Quality <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Intelligent transport systems. Traffic management systems. Status, fault and quality requirements<\/b><\/p>\n |