BSI PD ISO/TS 15638-8:2013
$198.66
Intelligent transport systems. Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) – Vehicle access monitoring (VAM)
| Published By | Publication Date | Number of Pages |
| BSI | 2013 | 64 |
This part of ISO 15638 addresses the provision of ‘Vehicle Access Management’ (and monitoring) and specifies the form and content of such data required to support such systems, and access methods (4.3) to that data.
ISO 15638 provides specifications (4.50) for common communications and data exchange aspects of the application service (4.6) vehicle access monitoring that a regulator (4.43) may elect to require or support as an option, including:
-
high level definition of the service that a service provider (4.48) has to provide, (The service definition describes common service elements; but does not define the detail of how such an application service (4.6) is instantiated, not the acceptable value ranges of the data concepts defined)
-
means to realise the service
-
application data, naming content and quality that an IVS (4.29) 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.33) to jurisdiction. This document 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 standardised 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.42)]. 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 |
| 18 | 5 Symbols (and abbreviated terms) |
| 20 | 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 |
| 21 | 8.3 Test requirements 8.4 Marking, labelling and packaging 9 Common features of regulated TARV application services 9.1 General |
| 22 | 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 |
| 23 | 9.6 Information security 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 Vehicle access management (VAM) 10.1 TARV VAM service description and scope – use cases 10.1.1 Jurisdiction – Safety enhancement 10.1.2 Sensitive/restricted zone managers – Access monitoring and management |
| 24 | 10.1.3 Vehicle operators – Access control monitoring and management 10.1.4 Jurisdiction – Assessment of levies 10.1.5 Sensitive/restricted zone managers – Assessment of levies 10.2 Concept of operations for vehicle access management 10.2.1 General |
| 26 | 10.2.2 Statement of the goals and objectives of the TARV VAM system |
| 28 | 10.2.3 Strategies, tactics, policies, and constraints affecting the system |
| 29 | 10.2.4 Organisations, activities, and interactions among participants and stakeholders |
| 31 | 10.2.4.1 Approaching sensitive/restricted zone – Planned |
| 32 | 10.2.4.2 Approaching sensitive/restricted zone – unplanned 10.2.4.3 Reporting and feedback |
| 33 | 10.2.5 Clear statement of responsibilities and authorities delegated |
| 34 | 10.2.6 Equipment required for TARV VAM 10.2.6.1 TARV IVS 10.2.6.2 Equipment periphery/connected to IVS 10.2.6.3 `TARV VAM ‘app’ 10.2.7 Operational processes for the system – Define & update sensitive/restricted zone |
| 35 | 10.2.8 Operational processes for the system – Approaching sensitive/restricted zone (planned and unplanned) 10.2.9 Operational processes for the system – Reporting and feedback |
| 36 | 10.2.10 ‘BigBubble’ approaching and leaving 10.3 Sequence of operations for TARV VAM 10.3.1 VAM service element (VAM SE1): Define sensitive/restricted zone 10.3.2 VAM service element (VAM SE2): Publish regulation 10.3.3 VAM service element (VAM SE3): Detect approaching regulated vehicle 10.3.4 VAM service element (VAM SE4): ASP notifies SZM of approaching vehicle 10.3.5 VAM service element (VAM SE5): Periodic or requested updates 10.3.6 VAM service element (VAM SE6): ‘Interrogated’ request for vehicle data |
| 37 | 10.3.7 VAM service element (VAM SE7): ASP updates SZM 10.3.8 VAM service element (VAM SE8): Vehicle egress 10.4 Generic TARV VAM data naming content and quality |
| 38 | 10.5 Specific TARV VAM data naming content and quality 10.6 TARV VAM application service specific provisions for quality of service 10.7 TARV VAM application service specific provisions for test requirements 10.8 TARV VAM application specific rules for the approval of IVSs and ‘Service Providers’ 11 Declaration of patents and intellectual property |
