EN ISO 18541-1:2014

SLOVENSKI STANDARD
01-december-2014
Cestna vozila - Standardiziran dostop do informacij o popravilih in vzdrževanju
avtomobilov (RMI) - 1. del: Splošne informacije in definicija primerov uporabe (ISO
18541-1:2014)
Road vehicles - Standardized access to automotive repair and maintenance information
(RMI) - Part 1: General information and use case definition (ISO 18541-1:2014)
Straßenfahrzeuge - Standardisierter Zugang zur Reparatur und Wartung - (RMI) - Teil 1:
Allgemeine Informationen und Beschreibung der Anwendungsfälle (ISO 18541-1:2014)
Véhicules routiers - Standardisation des accès aux informations de réparation et de
maintenance pour l'automobile (RMI) - Partie 1: Informations générales et définitions de
cas d'utilisation (ISO 18541-1:2014)
Ta slovenski standard je istoveten z: EN ISO 18541-1:2014
ICS:
43.040.15 $YWRPRELOVNDLQIRUPDWLND Car informatics. On board
9JUDMHQLUDþXQDOQLãNLVLVWHPL computer systems
43.180 'LDJQRVWLþQDYGUåHYDOQDLQ Diagnostic, maintenance and
SUHVNXVQDRSUHPD test equipment
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN ISO 18541-1
NORME EUROPÉENNE
EUROPÄISCHE NORM
September 2014
ICS 43.040.15; 43.180
English Version
Road vehicles - Standardized access to automotive repair and
maintenance information (RMI) - Part 1: General information and
use case definition (ISO 18541-1:2014)
Véhicules routiers - Normalisation de l'accès aux Straßenfahrzeuge - Standardisierter Zugang zur Reparatur
informations relatives à la réparation et à la maintenance und Wartung (RMI) - Teil 1: Allgemeine Informationen und
pour l'automobile (RMI) - Partie 1: Informations générales et Beschreibung der Anwendungsfälle (ISO 18541-1:2014)
définitions de cas d'usage (ISO 18541-1:2014)
This European Standard was approved by CEN on 13 March 2014.

CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European
Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national
standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN member.

This European Standard exists in three official versions (English, French, German). A version in any other language made by translation
under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management Centre has the same
status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania,
Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United
Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2014 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN ISO 18541-1:2014 E
worldwide for CEN national Members.

Contents Page
Foreword .3
Foreword
This document (EN ISO 18541-1:2014) has been prepared by Technical Committee ISO/TC 22 “Road
vehicles” in collaboration with Technical Committee CEN/TC 301 “Road vehicles” the secretariat of which is
held by AFNOR.
This European Standard shall be given the status of a national standard, either by publication of an identical
text or by endorsement, at the latest by March 2015, and conflicting national standards shall be withdrawn at
the latest by March 2015.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights.
According to the CEN-CENELEC Internal Regulations, the national standards organizations of the following
countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech
Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece,
Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal,
Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom.
Endorsement notice
The text of ISO 18541-1:2014 has been approved by CEN as EN ISO 18541-1:2014 without any modification.

INTERNATIONAL ISO
STANDARD 18541-1
First edition
2014-09-15
Road vehicles — Standardized access
to automotive repair and maintenance
information (RMI) —
Part 1:
General information and use case
definition
Véhicules routiers — Normalisation de l’accès aux informations
relatives à la réparation et à la maintenance pour l’automobile
(RMI) —
Partie 1: Informations générales et définitions de cas d’usage
Reference number
ISO 18541-1:2014(E)
©
ISO 2014
ISO 18541-1:2014(E)
© ISO 2014
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2014 – All rights reserved

ISO 18541-1:2014(E)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms, definitions, symbols and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Abbreviated terms . 7
4 Document overview and structure . 7
5 General information . 9
5.1 Access to vehicle RMI . 9
5.2 Standardized access to RMI benefit examples .10
6 RMI use case overview and principles .11
6.1 Overview of basic principles .11
6.2 Overview of use case clusters .11
7 RMI use cases .14
7.1 UC 1 User authentication, authorization and administration .14
7.2 UC 2 Payment for RMI .19
7.3 UC 3 Vehicle identification .20
7.4 UC 4 Provide selection methods for RMI .22
7.5 UC 5 Retrieve information packages .24
7.6 UC 6 Vehicle diagnostics .30
7.7 UC 7 Updating, replacing and tuning of modules (ECUs) .31
7.8 UC 8 Electronic maintenance history .33
7.9 UC 9 Repair assistance technical support .33
7.10 UC 10 Request contact for specific RMI .33
7.11 UC 11 Courses and training information .38
Bibliography .39
ISO 18541-1:2014(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity
assessment, as well as information about ISO’s adherence to the WTO principles in the Technical Barriers
to Trade (TBT) see the following URL: Foreword - Supplementary information.
ISO 18541-1:2013 was prepared by the European Committee for Standardization (CEN) Technical
Committee CEN/TC 301, Road vehicles, in collaboration with ISO Technical Committee ISO/TC 22, Road
vehicles, Subcommittee SC 3, Electrical and electronic equipment, in accordance with the agreement on
technical cooperation between ISO and CEN (Vienna Agreement).
ISO 18541 consists of the following parts, under the general title Road vehicles — Standardized access to
automotive repair and maintenance information (RMI):
— Part 1: General information and use case definition
— Part 2: Technical requirements
— Part 3: Functional user interface requirements
— Part 4: Conformance test
ISO 18542, Road vehicles — Standardized repair and maintenance information (RMI) terminology, is a
complementary standard that defines standardized RMI terminology and consists of two parts:
— Part 1: General information and use case definition
— Part 2: Standardized process implementation requirements, Registration Authority
The standardized RMI terminology is contained in a so-called ‘Digital Annex’ that is maintained and
published by the CEN-appointed Registration Authority.
iv © ISO 2014 – All rights reserved

ISO 18541-1:2014(E)
Introduction
This set of standards includes the requirements to be fulfilled by Repair and Maintenance Information
(RMI) systems as applied by the European Commission — Enterprise and Industry Directorate-General,
[[5]]
Consumer goods — Automotive industry EC mandate M/421 , dated Brussels, 21 January 2008.
This mandate relates to the EC type-approval system for vehicles falling into the scopes of Directives
70/156/EEC (replaced by 2007/46/EC [8]), 2002/24/EC [6] and 2003/37/EC [7] and, in particular, to
requirements for access to vehicle repair and maintenance information by independent operators.
This International Standard only covers access to automotive repair and maintenance information for
light passenger and commercial vehicles (see NOTE 1) and heavy duty vehicles (see NOTE 2) based on
Directive 70/156/EEC (replaced by 2007/46/EC [8]).
The purpose of the EC Mandate M/421 is to develop a standard or set of standards which specify the
requirements to provide standardized access to automotive repair and maintenance information (RMI)
for independent operators.
The information included in this part of ISO 18541 derives from the legislative requirements on European
level in the field of RMI and related security requirements and can be referenced by legislation in other
countries.
NOTE 1 Regulation (EC) No 715/2007 of the European Parliament and of the Council of 20 June 2007 on
type-approval of motor vehicles with respect to emissions from light passenger and commercial vehicles
(Euro 5 and Euro 6) and on access to vehicle repair and maintenance information and Commission Regulation
(EC) No 692/2008 of 18 July 2008 implementing and amending Regulation (EC) No 715/2007 of the European
Parliament and of the Council on type-approval of motor vehicles with respect to emissions from light passenger
and commercial vehicles (Euro 5 and Euro 6) and on access to vehicle repair and maintenance information and
amending Commission Regulation (EU) No 566/2011 of 8 June 2011 amending Regulation (EC) No 715/2007 of
the European Parliament and of the Council and Commission Regulation (EC) No 692/2008 as regards access to
vehicle repair and maintenance information.
NOTE 2 Regulation (EC) No 595/2009 of the European Pparliament and of the Council of 18 June 2009 on type-
approval of motor vehicles with respect to emissions from heavy duty vehicles (Euro VI) and on access to vehicle
repair and maintenance information, Commission Regulation (EU) No 582/2011 of 25 May 2011 implementing
and amending Regulation (EC) No 595/2009 of the European Parliament and of the Council with respect to
emissions from heavy duty vehicles (Euro VI), and Commission Regulation (EU) No 64/2012 of 23 January 2012
amending Regulation (EU) No 582/2011 2011 implementing and amending Regulation (EC) No 595/2009 of the
European Parliament and of the Council with respect to emissions from heavy duty vehicles (Euro VI).
INTERNATIONAL STANDARD ISO 18541-1:2014(E)
Road vehicles — Standardized access to automotive repair
and maintenance information (RMI) —
Part 1:
General information and use case definition
1 Scope
This part of ISO 18541 provides a general overview and structure of each part of ISO 18541. It also
specifies use cases related to repair and maintenance information (RMI) systems in order to standardize
the access to RMI for independent operators.
This part of ISO 18541 also describes the use cases applicable to the standardized access to automotive
RMI. The use cases address real world scenarios (e.g. servicing vehicles) in regard to the information
access necessary to perform vehicle roadside assistance, inspection, diagnosis, repair and maintenance,
including the updating and replacement of Electronic Control Units (ECU).
The RMI systems used by personnel to perform the services consist of:
— a Web-based system, which provides access to RMI needed to perform the service(s);
— contact information for specific RMI;
— a security framework to protect access to security related RMI.
This part of ISO 18541 provides an overview of the entire standard and how it applies to the automotive
industry.
This part of ISO 18541 is applicable to light passenger and commercial vehicles as defined in regulation
[15]
(EC) 715/2007 Article 2.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are
indispensable for its application. For dated references, only the edition cited applies. For undated
references, the latest edition of the referenced document (including any amendments) applies.
ISO 18541-2, Road vehicles — Standardized access to automotive repair and maintenance information
(RMI) — Part 2: Technical requirements
3 Terms, definitions, symbols and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1.1
access level
level of access to RMI which is either relevant to security or not relevant to security
EXAMPLE One might consider an access to RMI relevant to security and another one to RMI not relevant to
security. They represent two different access levels.
ISO 18541-1:2014(E)
3.1.2
accessories
supplementary features and components selected by a vehicle owner to enhance safety, performance,
comfort, etc. and whose fitting does not impact on the vehicle approval
3.1.3
alternate fuel
type of fuel that is either gaseous at atmospheric temperature and pressure or substantially non-mineral
oil derived
[15]
Note 1 to entry: Adopted from Regulation (EC) 715/2007.
3.1.4
alternate fuels retrofit systems
engine systems mounted on an already registered vehicle for the purpose of operation with alternative
fuels
3.1.5
alternative fuels system manufacturer
manufacturer of an engine system operating with an alternative fuel
3.1.6
appropriate software level
applicable software version for the individual vehicle
3.1.7
authorized repairer
AR
provider of repair and maintenance services for motor vehicles operating within the distribution system
set up by a supplier of motor vehicles
[10]
Note 1 to entry: See Regulation (EC) 461/2010 Article 1 (1)(c).
3.1.8
certificate
electronic document which uses a digital signature to bind a public key with an identity
3.1.9
converted vehicle
factory-produced vehicle which has been altered by the addition, deletion, substitution or modification
of the body, chassis or essential parts that resembles, but is no longer identical to, the original vehicle for
a special purpose e.g. to act as rescue vehicle or taxicab
3.1.10
detailed diagnosis
diagnostic process that identifies, with precision, potential malfunction causes
Note 1 to entry: A precise diagnosis can be achieved in several steps, whereby the user might be requested to
perform test actions on the vehicle or to enter symptoms.
3.1.11
diagnostic information
description of an error or symptom and a list of potential causes or hints for further investigation to the
same level and content as provided to the AR
3.1.12
diagnostic trouble code
DTC
numeric or alphanumeric identifier which identifies or labels a malfunction
[16]
Note 1 to entry: Adopted from United Nations Global Technical Regulation No.°5.
2 © ISO 2014 – All rights reserved

ISO 18541-1:2014(E)
3.1.13
electronic maintenance history
digital information package with virtual stamps that confirms the execution of the prescribed
maintenance actions according to the VM’s schedule
3.1.14
global technical regulation
GTR
World-Wide Harmonized On-Board Diagnostics Global Technical Regulation No.°5
[16]
Note 1 to entry: See Reference.
3.1.15
independent operator
IO
company or legal entity other than authorized dealers and repairers who is directly or indirectly
involved in the repair and maintenance of motor vehicles
EXAMPLE Repairers, manufacturers or distributors of repair equipment, tools or spare parts, publishers of
technical information, automobile clubs, roadside assistance operators, operators offering inspection and testing
services, operators offering training for installers, manufacturers and repairers of equipment for alternative fuel
vehicles.
3.1.16
IO approval
process by which, upon payment of a reasonable and proportionate fee, the CAB sanctions or approves
a legitimate commercial enterprise to engage in security-related RMI activities
3.1.17
IO authorization
process by which, upon payment of a reasonable and proportionate fee, the CAB assesses that an
individual employee of an approved IO complies with the requirements specified in this part of ISO 18541
and is entitled to be given access to security-related RMI
Note 1 to entry: As part of this authorization, the individual employee will be allocated, upon payment of a
reasonable and proportionate fee, a secure hardware token containing a personal digital certificate and a PIN
that will be supplied by the Trust Centre
3.1.18
IO legal representative
natural person empowered to legally represent the IO in all aspects of the access to vehicle RMI
3.1.19
information package
collection of information provided by the VM’s RMI system in response to a specific request
3.1.20
information type
category, group or set of information
EXAMPLE Workshop procedures (for body repair, temporary repair, periodic technical inspection), wiring
diagrams, technical service bulletins, recall information and maintenance information.
3.1.21
integrated diagnostics
process which interprets via an integrated application the memory content of ECUs and provides a
diagnostic and repair recommendation
Note 1 to entry: Diagnostic application and VM RMI systems cooperate online, so technical information is provided
during the diagnostics process and used for the diagnostic steps.
ISO 18541-1:2014(E)
3.1.22
IO employee
natural person employed by the IO
3.1.23
maintenance history
history of the performed, prescribed actions for maintaining a vehicle
EXAMPLE Oil changes and other periodic maintenance.
3.1.24
maintenance schedule
prescribed sequence of maintenance actions for a vehicle following the requirements of the manufacturer
3.1.25
on-board diagnostics
OBD
system on board a vehicle or engine which is capable of detecting malfunctions and, if applicable, of
indicating their occurrence by means of an alert system, identifying the likely area of the malfunctions
by means of information stored in computer memory, and/or communicating that information off-board
[16]
Note 1 to entry: Module ‘A’ of GTR No.°5 concerns the whole vehicle. By referring to that module, the OBD
definition is understood as not being restricted to emissions.
3.1.26
p-code
standardized DTC for powertrain errors according to ISO 15031-6
3.1.27
partnered accessories
accessories which have been tested, quality assured and certified by the VM and for which the VM
assumes product liability
3.1.28
potential repair descriptions
list of potential causes and possible actions recommended to fix a problem
3.1.29
product features
features of a specific vehicle that may be used for navigation through the VM RMI system
EXAMPLE Engine type (petrol/diesel), transmission type (manual/automatic).
3.1.30
product structure
inter-related set of units and sub-units in which a vehicle can be divided
Note 1 to entry: The product structure is VM specific.
3.1.31
periodic technical inspection service
PTI service
particular procedure for testing a vehicle during a PTI
EXAMPLE Procedure for testing brake lights.
3.1.32
recall
process whereby a VM notifies all owners of a specific vehicle of a condition or defect that could affect
safety, safe operation or environmental issues of that vehicle
4 © ISO 2014 – All rights reserved

ISO 18541-1:2014(E)
3.1.33
redistributor
IO offering RMI within their own internal (closed) network
EXAMPLE RAC, ADAC, garage networks.
3.1.34
remanufacturing
process of overhauling an engine, major assembly or component, to return the engine, major assembly
or component to the VM’s original specification
3.1.35
repair and maintenance information
RMI
all information required for diagnosis, servicing, inspection, periodic monitoring, repair, re-programming
or re-initialising of the vehicle and which the manufacturers provide for their authorized dealers and
repairers, including all subsequent amendments and supplements to such information
Note 1 to entry: This information includes all information required for fitting parts or equipment on vehicles.
[9]
Note 2 to entry: Adapted from Regulation (EC) 715/2007.
3.1.36
republisher
IO who publishes RMI to an external network using the RMI of the VM
3.1.37
security framework
set of processes, roles and technical devices for access to security-related RMI recommended by the EC
Forum on Vehicle RMI to the EC
[15] [14]
Note 1 to entry: As mandated in the Regulations (EC) 715/2007 and (EC) 692/2008.
Note 2 to entry: The framework is based on the approval and authorization of IOs by certified entities to access
security related RMI at the VM RMI system. The physical access to the VM RMI system for security related RMI is
bound to a digital certificate.
3.1.38
security-related RMI
RMI subject to protection measures in the security framework
3.1.39
security repair and maintenance information
SERMI
de-facto association founded by IO and VM organizations to act as the owner for the process and scheme
defined in the EC Forum for Access to Vehicle RMI, Report on Access to security-related RMI, version 1.1
3.1.40
selection methods
possible methods of selecting RMI
EXAMPLE Searches for a term in the document titles, information type, document ID or other criteria.
3.1.41
standardized non-proprietary VCI functionality
current standards for communication with a vehicle
EXAMPLE ISO 22900-2, SAE J2534–1/2.
ISO 18541-1:2014(E)
3.1.42
technical service bulletin
TSB
bulletin issued by the manufacturer detailing a fix for a known concern
Note 1 to entry: The bulletin is for informational purposes only.
3.1.43
temporary repair procedure
temporary solution to a problem that is usually available at roadside services
EXAMPLE Closing the roof of a convertible.
3.1.44
vehicle communication interface functionality
VCI functionality
set of functions to provide communication between vehicle systems and a software application for
diagnostics or reprogramming according to the requirements specified in ISO 18541-2
3.1.45
vehicle identification number
VIN
unique 17-character serial number given by the VM to identify individual motor vehicles
3.1.46
vehicle manufacturer
VM
person or body who is responsible to the approval authority for all aspects of the type approval or
authorization process and for ensuring conformity of production of a vehicle
Note 1 to entry: It is not essential that the person or body be directly involved in all stages of the construction of
the vehicle, system, component or separate technical unit which is the subject of the approval process.
[8]
Note 2 to entry: Adapted from Directive 2007/46/EC.
3.1.47
vehicle manufacturer repair and maintenance information system
VM RMI system
information system by which the VM provides access to RMI through a website
3.1.48
workshop procedure
information provided by a VM describing specific repair and maintenance
EXAMPLE Repair procedures, working advice or other instructions.
6 © ISO 2014 – All rights reserved

ISO 18541-1:2014(E)
3.2 Abbreviated terms
AR authorized repairer
BP basic principle
CAB conformity assessment body
DRP direct re-publisher
DTC diagnostic trouble code
ECU electronic control unit
GTR global technical regulations
GUI graphical user interface
HMI human machine interface
IO independent operator
IR independent repairer
MI malfunction indicator
OBD on-board diagnostic
PIN personal identification number
PTI periodic technical inspection
PTT pass-thru tool
RMI repair and maintenance information
SERMI security repair and maintenance information
TSB technical service bulletin
VCI vehicle communication interface
VIN vehicle identification number
VM vehicle manufacturer
4 Document overview and structure
The ISO 18541 document set provides an implementer with all documents and references required to
support the implementation of the requirements related to standardized access to automotive RMI in
accordance with the requirements set forth in EC mandate M/421.
— This part of ISO 18541: General information and use case definition
This part provides an overview of the document set and structure along with the use case
definitions and a common set of resources (definitions, references) for use by all subsequent parts.
The standardized access to Automotive RMI shall be implemented by the VMs in their RMI systems.
— ISO 18541-2: Technical requirements
Part 2 specifies all technical requirements related to a VM RMI system. These requirements will
reflect the deriving needs from the use cases as specified in Part 1.
ISO 18541-1:2014(E)
EXAMPLE (not a complete list):
— access-related data administration;
— information technology architecture;
— external interfaces;
— technical infrastructure recommendations;
— operations.
— ISO 18541-3: Functional user interface requirements
Part 3 specifies all functional user interface requirements related to a VM RMI system e.g.
navigational pathway and user guidance. These requirements will reflect the deriving needs from
the use cases as specified in Part 1.
— ISO 18541-4: Conformance test
Part 4 specifies conformance test cases for a self-conformance test by the
provider of the VM RMI system. The conformance test cases will follow the
use case definition of Part 1 as well as the requirements stated in Parts 2 and 3.
The purpose of Part 4 is to provide information to the VM RMI system provider to build and test the
VM RMI system against the conformance test cases. This final step in the development process of
the VM RMI system is an enabler for all providers that their VM RMI system meets a high degree of
functional requirements expected by the end user.
Figure 1 illustrates the document structure of ISO 18541 with reference to ISO 18542.
Figure 1 — Document structure
8 © ISO 2014 – All rights reserved

ISO 18541-1:2014(E)
5 General information
5.1 Access to vehicle RMI
This part of ISO 18541 specifies use cases and requirements to be supported by VM RMI systems.
Figure 2 illustrates a typical example of an implementation scenario of a VM RMI, Diagnostics and Flash
Programming Web-based server environment. The Independent Operators use RMI clients (meeting the
specification in ISO 18541-2:2014, Annex A) which shall have access to the Internet.
Multiple VM RMI system configuration scenarios related to the server and client software architecture
are possible and a purely online solution is not precluded. It is the VM’s responsibility to support an RMI
system configuration scenario which meets the requirements and objectives of standardized access to
automotive RMI from a user’s point of view.
VM RMI system configuration scenarios are described in ISO 18541-2. The following VM RMI system
configuration scenarios are examples and should not be considered a complete list of possible
configurations to satisfy the use cases and requirements.
— Configuration scenario #1 describes the following server and client installation:
— Server(s): VM RMI Web system, VM Diagnostic software and configuration data for download
by all clients, VM Flash Programming software and ECU files for download by all clients;
— Client(s): Browser capable computing hardware platform, diagnostic software installation
downloaded from the server, Flash programming software installation downloaded from the
server, VCI connected to vehicle and computing hardware platform with vehicle communication
protocol support to retrieve data from the vehicle through the diagnostic connector, diagnostics
and Flash programming executed on the client computing hardware platform.
— Configuration scenario #2 describes the following server and client installation:
— Server(s): VM RMI Web system, VM diagnostic software and configuration data for download
by all clients, VM Flash programming software and ECU files for download by all clients,
diagnostics and Flash programming executed on the server for all clients;
— Client(s): Browser capable computing hardware platform, diagnostic software installation
downloaded from the server, Flash programming software installation downloaded from the
server, VCI connected to vehicle and computing hardware platform with vehicle communication
protocol support to retrieve data from the vehicle through the diagnostic connector, the
diagnostics and Flash programming user interface is separated from the server applications
and executed on the client computing hardware platform.
Figure 2 depicts a typical example of the access to vehicle RMI.
ISO 18541-1:2014(E)
Key
1 Repair and Maintenance Information
2 Vehicle Communication Interface
Figure 2 — Typical example of access to vehicle RMI
5.2 Standardized access to RMI benefit examples
5.2.1 Independent operators
The following benefits are applicable to independent repairers:
— similar functional GUI for all vehicle brands,
— same functional RMI search terminology,
— functionally equivalent RMI navigational pathway,
— single PC connected to Internet to access RMI of all vehicle brands.
5.2.2 Vehicle manufacturers
The following benefits are applicable to the vehicle manufacturer service department and repair shops:
— improved sales of RMI to independent operators,
10 © ISO 2014 – All rights reserved

ISO 18541-1:2014(E)
— streamlining of access to RMI to a single method,
— simplification of future RMI system development,
— provision of a consistent interface between RMI, diagnostics and other information.
6 RMI use case overview and principles
6.1 Overview of basic principles
Basic principles have been established as a guideline to define the RMI use cases:
— BP1: RMI use cases describe the interaction between an independent operator and the VM websites
for RMI access.
— BP2: The use cases in the RMI standard define a common way to organize VM websites for RMI
access.
— BP3: The content of the technical information provided by the VM website for RMI and the quality
of the access implementation is the responsibility of the VM.
[9]
— BP4: Actors for the use cases are independent operators as defined in regulation EC 715/2007, VM
RMI system and VM. Special roles for specific use cases may be defined and explained in 3.1.
— BP5: Security use cases are a subset of RMI use cases.
— BP6: The primary purpose of the RMI standard is to support the existing relevant European
legislation for access to RMI. In addition, it has been developed in a way that can be referenced by
legislation in other countries.
— BP7: The VM is required to provide for the purposes of repair and maintenance the same information
that it provides to its ARs in a non-discriminatory manner.
— BP8: The VM is only expected to provide the VM RMI system and information in the languages as
provided to its ARs.
6.2 Overview of use case clusters
Table 1 provides an overview of the main RMI use cases. A main RMI use case cluster may have one or
more use cases.
Table 1 — Main use case clusters
Main title of use
# Brief description Use case reference
case cluster
1 User The use cases belonging to this cluster describe how UC 1.1 Register IO for use of
authentication, to obtain a license to use the VM RMI system, keep the VM RMI system
authorization and user data and access level up to date, protect RMI
UC 1.2 Register IO employee
administration against misuse and how to get access to the VM RMI
for use of the VM RMI system
system.
UC 1.3 Maintain IO status
UC 1.4 Maintain user status
UC 1.5 Request to de-register
IO employee
UC 1.6 Login to VM RMI system
UC 1.7 Grant access to security-
related RMI
ISO 18541-1:2014(E)
Table 1 (continued)
Main title of use
# Brief description Use case reference
case cluster
2 Payment for RMI The use cases belonging to this cluster describe the UC 2 Payment for RMI
handling of payments.
3 Vehicle The use cases belonging to this cluster describe how UC 3.1 Vehicle identification
identification to identify a specific vehicle, vehicle summary and through use of the VIN
type of vehicle. The identification methods are:
UC 3.2 Vehicle type identifica-
— by VIN search and/or tion via product features
— product feature.
4 Provide selection The use cases belonging to this cluster describe how UC 4.1 Select information type
methods for RMI to choose the preferred method to locate and select
UC 4.2 Search by standardized
information.
terms
The VM RMI system presents a list of all selection
UC 4.3 Navigate using product
methods supported by the system. A combination of
structure
methods shall be possible. The user can for instance
request for a term in document titles of a single type.
UC 4.4 Select by document
The different access methods are alternative ways to
find the same documents in the VM system.
The purpose of these use cases is to enable the user to
find the required information. There shall be ways to
find this information by at least one of the predefined
selection methods (see 7.3).
The selection methods supported are:
— by information types,
— by standardized terms,
— by product structure and
— by document identifier.
5 Retrieve The use cases belonging to this cluster describe the UC 5.1 Workshop procedures
information retrieval of selected repair and maintenance informa-
UC 5.2 Wiring diagrams
packages tion packages.
UC 5.3 Technical service bul-
The user selects one of many documents in the search
letin
result list. The VM RMI system displays the selected
package of information which are:
UC 5.4 Recall information
— workshop procedures (for body repair, tem- UC 5.5 Maintenance schedule
porary repair, periodic technical inspection),
UC 5.6 Spare parts
— wiring diagrams,
UC 5.7 Accessories
— technical service bulletins,
UC 5.8 Labour times
— recall information,
UC 5.9 Converted vehicles
— maintenance information,
UC 5.10 Special tools
— etc.
6 Vehicle The use cases belonging to this cluster describe the UC 6.1 DTC resolution
diagnostics support for:
UC 6.2 VM symptom resolution
— DTC resolution,
UC 6.3 Integrated diagnostics
— symptom resolution and
— integrated diagnostics.
12 © ISO 2014 – All rights reserved

ISO 18541-1:2014(E)
Table 1 (continued)
Main title of use
# Brief description Use case reference
case cluster
7 Updating, The use cases belonging to this cluster describe the UC 7.1 Updating and replacing
replacing and support of the legitimate update or replacement of modules
tuning of modules vehicle modules/ECUs to return to an operational
UC 7.2 Tuning kit
(ECUs) state after repair or tuning with a VM application
using approved and known VCIs which meet the
standards required by legislation.
8 Electronic The use cases belonging to this cluster describe how UC 8 Electronic maintenance
maintenance to get access and to update the history of VM pre- history
history scribed maintenance actions.
9 Repair Assistance, The use cases belonging to this cluster describe how UC 9 Repair assistance techni-
Technical Support to get advice from the VM if repair assistance or tech- cal support
nical support is needed.
10 Request contact The use cases belonging to this cluster describe how UC 10.1 Electronic tool infor-
information to request contact information in order to receive mation (Diagnostic, Repro-
information about: gramming, VCI)
— electronic tool, UC 10.2 Test equipment and
diagnostic tool manufacturers
— diagnostics,
UC 10.3 Training material (del-
— VCI,
egate information)
— training material,
UC 10.4 Redistributors
— etc.
UC 10.5 Republishers
UC 10.6 Inspection and testing
services
UC 10.7 Alternative fuels retro-
fit systems
UC 10.8 Engine and compo-
nents remanufacturing
UC 10.9 Component and parts
manufacturers
UC 10.10 Validation of indepen-
dently developed non-proprie-
tary VCIs
11 Courses and The use cases belonging to this cluster describe how UC 11 Courses and training
training to get information regarding training course avail- information
information ability (online or Web-based training).
Figure 3 illustrates all use case clusters and associated use cases.
The detailed definition of each use case is defined in Clause
...