BSI PD ISO/TS 15638-18:2013
$198.66
Intelligent transport systems. Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) – ADR (Dangerous Goods) transport monitoring (ADR)
| Published By | Publication Date | Number of Pages |
| BSI | 2013 | 68 |
This part of ISO 15638 addresses the provision of ‘ADR (Dangerous goods)’ and specifies the form and content of such data required to support such systems, and access methods (4.1) to that data.
This part of ISO 15638 provides specifications (4.43) for common communications and data exchange aspects of the application service (4.3) ADR [dangerous goods (4.17)] that a regulator (4.39) may elect to require or support as an option, including:
-
high level definition of the service that a s ervice provider (4.41) has to provide (the service definition describes common service elements, but does not define the detail of how such an application service (4.3) is instantiated, nor the acceptable value ranges of the data concepts defined);
-
means to realise the service;
-
application data, naming content and quality that an IVS (4.26) has to deliver.
The definition of what comprises a ‘regulated’ service is regarded as an issue for national decision, and may vary from jurisdiction (4.30) to jurisdiction. This part of ISO 15638 does not impose any requirements on nations in respect of which services for regulated vehicles jurisdictions will require, or support as an option, but provides standardized sets of requirements descriptions for identified services to enable consistent and cost efficient implementations where instantiated.
ISO 15638 has been developed for use in the context of regulated commercial freight vehicles [hereinafter referred to as ‘regulated vehicles’ (4.38)]. There is nothing, however, to prevent a jurisdiction extending or adapting the scope to include other types of regulated vehicles, as it deems appropriate.
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 11 | 1 Scope 2 Conformance |
| 12 | 3 Normative references 4 Terms and definitions |
| 17 | 5 Symbols and abbreviated terms |
| 19 | 6 General overview and framework requirements 7 Requirements for services using generic vehicle data 8 Application services that require data in addition to basic vehicle data 8.1 General 8.2 Quality of service requirements |
| 20 | 8.3 Test requirements 8.4 Marking, labelling and packaging 9 Common features of regulated TARV application services 9.1 General |
| 21 | 9.2 Common role of the jurisdiction, approval authority, service provider and user. 9.3 Common characteristics for instantiations of regulated application services 9.4 Common sequence of operations for regulated application services 9.5 Quality of service 9.6 Information security |
| 22 | 9.7 Data naming content and quality 9.8 Software engineering quality systems 9.9 Quality monitoring station 9.10 Audits 9.11 Data access control policy 9.12 Approval of IVSs and service providers 10 TARV ADR consignment monitoring (ADRm) 10.1 ADRm service description and scope |
| 23 | 10.1.1 ADRm use case 10.1.2 Description of ADRm regulated application service |
| 24 | 10.2 Concept of operations for ADRm 10.2.1 General 10.2.2 Statement of the goals and objectives of ADRm 10.2.3 Strategies, tactics, policies, and constraints affecting ADRm |
| 25 | 10.2.4 Organisations, activities, and interactions among participants and stakeholders in ADRm |
| 26 | 10.2.5 Clear statement of responsibilities and authorities delegated for ADRm 10.2.6 Operational processes for the ADRm |
| 27 | 10.2.7 Role of ADRm service provider 10.2.8 Role of ADRm user 10.3 Sequence of operations for ADRm |
| 28 | 10.4 ADRm naming content and quality 10.5 Specific ADRm data naming content and quality |
| 29 | 10.6 ADRm service elements 10.6.1 ADRm SE1: Establish jurisdiction regulations or system specification for ADR monitoring 10.6.2 ADRm SE2: Request system approval 10.6.3 ADRm SE3: User (operator) contracts with prime service provider 10.6.4 ADRm SE4: User (operator) equips vehicle with a means to provide consignment data 10.6.5 ADRm SE5: User contracts with application service provider 10.6.6 ADRm SE6: application service provider uploads software into the TARV equipped vehicles of the operator |
| 30 | 10.6.7 ADRm SE7: Recording of vehicle consignment data 10.6.8 ADRm SE8: ADRm Trigger 10.6.9 ADRm SE9: Contact predetermined IPv6 address |
| 31 | 10.6.10 ADRm SE10: Obtain consignment data 10.6.11 ADRm SE11: ‘Interrogated’ request for ADR data 10.6.12 ADRm SE12: Notification to operator |
| 32 | 10.7 ADRm access methods to provision and retrieve data |
| 37 | 10.8 ADRm application service specific provisions for quality of service 10.9 ADRm application service specific provisions for test requirements 10.10 ADRm application specific rules for the approval of IVSs and ‘Service Providers’ |
| 38 | 11 Declaration of patents and intellectual property |
| 46 | CTP 10.1.1 Instigated ADR – Dangerous Goods Monitoring using 2G |
| 48 | CTP 10.1.2 Interrogated ADR – Dangerous goods monitoring using 2G |
| 50 | CTP 10.1.3 Interrogated ADR – Dangerous goods monitoring using 5.9GHz and responding using 2G or 3G |
| 52 | CTP 10.2.1 Instigated ADR – Dangerous goods monitoring using 3G |
| 54 | CTP 10.2.2 Interrogated at 5.9 GHz and send of ADR – Dangerous goods monitoring using 3G |
| 56 | CTP 10.3.1 Instigated ADR – Dangerous goods monitoring using 802.11p (WAVE) 5.9 GHz |
| 58 | CTP 10.3.2 Interrogated ADR – Dangerous goods monitoring using 802.11p (WAVE) 5.9 GHz |
| 60 | CTP 10.4.1 Instigated ADR – Dangerous goods monitoring using Mesh WiFi |
| 62 | CTP 10.4.2 Interrogated ADR – Dangerous goods monitoring using Mesh WiFi |
