BSI PD ISO/TS 15638-12:2013
$198.66
Intelligent transport systems. Framework for collaborative Telematics Applications for Regulated commercial freight Vehicles (TARV) – Vehicle mass monitoring (VMM)
| Published By | Publication Date | Number of Pages |
| BSI | 2013 | 70 |
This part of ISO 15638 addresses the provision of “Vehicle ‘Mass’ Monitoring” and specifies the form and content of such data required to support such systems, and access methods (4.4) to that data.
This part of ISO 15638 provides specifications (4.46) for common communications and data exchange aspects of the application service (4.3) “Vehicle ‘Mass’ Monitoring” that a regulator (4.42) may elect to require or support as an option, including:
-
high level definition of the service that a service provider (4.44) 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, 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.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 document does not impose any requirements on nations in respect of which services for regulated commercial freight vehicles (4.41) 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.41)). 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) |
| 19 | 6 General overview and framework requirements 7 Requirements for services using generic vehicle data |
| 20 | 8 Application services that require data in addition to basic vehicle data 8.1 General 8.2 Quality of service requirements 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 |
| 22 | 9.5 Quality of service 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 Access control to data policy 9.12 Approval of IVSs and service providers 10 Vehicle mass monitoring (VMM) 10.1 TARV VMM service description and scope 10.1.1 TARV VMM use case |
| 23 | 10.1.2 Description of TARV VMM regulated application service |
| 24 | 10.1.3 Description of TARV ‘Vehicle mass monitoring’ (TARV VMM) application service 10.2 Concept of operations for TARV VMM 10.2.1 General |
| 25 | 10.2.2 Statement of the goals and objectives of the TARV VMM system 10.2.2.1 Monitoring the mass of the regulated vehicle for regulatory purposes 10.2.2.2 Monitoring the mass of the regulated vehicle for fleet operation management purposes 10.2.3 Strategies, tactics, policies, and constraints affecting the TARV VMM system |
| 26 | 10.2.4 Organisations, activities, and interactions among participants and stakeholders for TARV VMM |
| 27 | 10.2.5 Clear statement of responsibilities and authorities delegated for TARV VMM 10.2.6 Equipment required for TARV VMM 10.2.6.1 TARV IVS |
| 28 | 10.2.6.2 VMM Unit(s) (VMMU) |
| 30 | 10.2.6.3 Mass sensors capabilities and data |
| 32 | 10.2.6.4 `TARV VMM ‘app’ 10.2.6.5 Mass Records – MRQ A |
| 33 | 10.2.6.6 Mass Records – MRQ B |
| 34 | 10.2.6.7 On-board map 10.2.7 Calibration of mass sensors 10.2.7.1 General |
| 35 | 10.2.8 Alarm Records for TARV VMM 10.2.8.1 Alarm events for TARV VMM |
| 36 | 10.2.8.2 Alarm record data for TARV VMM 10.2.9 Operational processes for the TARV VMM system 10.2.10 Role of the jurisdiction for TARV VMM 10.2.11 1Role of the TARV VMM prime service provider |
| 37 | 10.2.12 Role of the TARV VMM application service provider 10.2.13 Role of the TARV VMM user 10.2.14 Generic characteristics for all instantiations of the TARV VMM application service 10.3 Sequence of operations for TARV VMM 10.3.1 General |
| 39 | 10.4 TARV VMM service elements 10.4.1 TARV VMM service element (SE) 1: Establish ‘Vehicle mass monitoring’ regulations, requirements, and Approval arrangements 10.4.2 TARV VMM SE2: Request system approval 10.4.3 TARV VMM SE3: User (operator) contracts with prime service provider 10.4.4 TARV VMM SE4: User (operator) equips vehicle with a devices to provide load information 10.4.5 TARV VMM SE5: User contracts with application service provider 10.4.6 TARV VMM SE6: application service provider uploads software into the TARV equipped vehicles of the operator 10.4.7 TARV VMM SE7: Time series or application service instigated recording of vehicle load |
| 40 | 10.4.8 TARV VMM SE8: ‘Interrogated’ request for vehicle mass monitoring data |
| 41 | 10.5 Generic TARV VMM data naming content and quality |
| 42 | 10.6 TARV VMM application service specific provisions for quality of service 10.6.1 General |
| 43 | 10.6.2 Tamper evidency 10.7 TARV VMM application service specific provisions for test requirements 10.8 TARV VMM application specific rules for the Approval of IVSs and ‘Service Providers’ 11 Declaration of patents and intellectual property |
