2014 International Conference of Advanced Informatics: Concept, Theory and Application (ICAICTA)

Ontology-based Knowledge Representation of Failure

Mode and Effect Analysis on Electric/Electronic
Architecture Modeling Conforming to the ISO 26262
Arthur Silitonga1), and Martin Hillenbrand2)
1)
Study Program of Electrical Engineering , President University, Indonesia
2)
Institute for Information Processing Technology (ITIV), Karlsruhe Institute of Technology, Germany
arthur@president.ac.id

Abstract—In this paper, we propose knowledge representation of
Failure Mode and Effect Analysis (FMEA) on Electric/Electronic
Architecture (EEA) tailored to ISO 26262. FMEA, EEA, and ISO
26262 are composed of abstract and concrete data. Description
and representation of abstract and meta models are complex.
Indeed, to simplify and feasibly represent the data for
software/hardware development of the EEA, we approach the
knowledge representation of the FMEA for the concrete and
abstract models of EEA using ontology. With the ontology,
FMEA, EEA, ISO 26262, and combination of the three aspects
can be presented using concrete models, and are able to be
defined in the form of class models. These class models will be
occupied for the development of the software aspect of FMEA for
EEA accommodating the ISO 26262. Hence, this type of
representation is considered to an adequate model to represent
the abstract, concrete and meta models of FMEA for EEA
conforming to ISO 26262.
Keywords—Concept, Ontology, Knowledge Representation,
Electric/Electronic Architecture, Failure Mode and Effect
Analysis, ISO 26262.
we can also represent abstract and meta models together with
concrete models.
II. MODEL OF ELECTRIC/ELECTRONIC ARCHITECTURE (EEA)
A. Modeling Concept of Electric/Electronic Architecture in
Modern Automobile
Common modern approaches used to develop modern
vehicles need to occupy the aspects of technical and functional
of a system. Whenever we try to list some important
parameters or aspects which may influence the cost function of
designing an automotive system, we come up with the aspects
of maintability, comfortability, safety, usability, reliability
redundancy, ergonomics during the operation, etc.
One model of electric/electronic architecture can be shown
on Fig. 1 below.

I. INTRODUCTION
The Standard ISO 26262 – Functionality Safety for Road
Vehicles describes a safety lifecycle for the development of
functional systems, based on electric and electronic devices or
components occupied in automobiles [3]. Developing safe, and
advanced units in automotive systems and systems of systems
are fundamentally needed.
We approach the analysis of safety and advanced units for
electric/electronic devices of automobiles based on the concept
of failure mode and effect analysis (FMEA). FMEA is
considerably adequate to analyze safety of subsystems and
systems. Combination or adaptive trait of FMEA to the
standard ISO/DIS 26262 is described using formal description,
i.e. ontology-based description.
On this paper, we explain the description of Failure Mode
and Analysis for electric/electronic architecture of automotive
systems conforming to the Standard ISO/DIS 26262 with
ontological description. With ontology, the development of
systems based on hardware and software parts will
Fig. 1. Electric and Electronic Architecture[6][9]
considerably reduce the development time of electric and
electronic in automotive subsystems or systems. Furthermore,
Based on the EEA model depicted in Fig.1, the model
consists of information of requirements, information of

978-1-4799-5100-0/14/$31.00 ©2014 IEEE 260

 2014 International Conference of Advanced Informatics: Concept, Theory and Application (ICAICTA)

software development, information of hardware development,

information of hardware networking, and information of
hardware topology [6][9]. The feature functionality network is
the software development in purpose to combine the
interfacing of hardware, especially for sensors, and actuators.
Interdependency of information engineering from the layer
of requirements to the layer of topology is definitely able to be
described using ontology-based description.
To create structured representation of knowledge, three
components of the representation are defined as concepts,
knowledge, and ontologies. In this paper, concepts are
described in three different terms, i.e. definition, organization,
and use. Furthermore, knowledge and ontologies will be also
Fig. 4. Conceptual Graph of EEA
stated in the same three different terms, such as definition,
organization, and use.
For the use of concept, the diagram can be described using
the CGIF (conceptual graph interchange form). It is very
common that DF (display form) is used to design a
communication with humans, and LF (linear form) is used to
design a communication between humans and machines. CGIF
has a simpler syntax and a bounded set, but CGIF is believed
an adequate method for transferring between information
technology systems that use CGs as their internal
representation. The LF of Fig.4 is :

[Interconnection of Sensors and Actuators …] –

Fig. 2. Structured Representation of Knowledge Combined by
Ontologies and Concepts
Approaching the concept of Electric and Electronic
Architecture (EEA), we can define the definition of EEA based
on concept by definition defined using visualization [1].
Requirement Views
(Guidelines) – [Requirement Views]
(Agnt) – [EE Devices : Sensors, Actuators, ECUs]
(Intf.) – [Interfacing Media : Wire, LIN, CAN]
(Top-Asp.) – [Aspects of Topology : Installation, Location]
CGIF of Fig. 4 can be described as :
[Interconnection of Sensors and Actuators … *x] (Guidelines ?x [EE
Devices ‘Sensors, Actuators, ECUs’]) (Inf ?x Interfacing Media ‘Wire,
LIN, CAN’]) (Top-Asp. ?x ‘Installation, Location’])
B. Ontology Organization

Ontology is specification of a shared conceptualization [1],

Feature-Functionality-Network and Function and it is a description of the most useful, or at least most well-
Network of Electric and Electronic Parts troden, organization of knowledge in a given domain [2].
based on Requirements from users Impacting on
Activation & Location of Sensors and Actuators

Electric Sensors
and Actuators
Electronic CANs/LINs/MOSTs
Devices Wires
Object Symbol
Fig. 3. Concept Model of Electric and Electronic Architecture

The concept organization of EEA is described using a

conceptual graph shown on Fig. 4. Conceptual graph itself Fig. 5. Ontology Organization Proposed for EEA
explains a proportional content of many contents and their We modeled the ontology organization of EEA by
relationships. Concepts are represented by boxes, and occupying a basic model consists of requirement view, Electric
conceptual relations are symbolized by circles [1]. and Electronic Devices (EED), interfacing media, aspects of

261
 2014 International Conference of Advanced Informatics: Concept, Theory and Application (ICAICTA)
topology, Feature-Functionality Network (FFN), and
Functionality Network (FN). It is considered that the Feature-
Functionality-Network (FFN) and Functionality Network (FN)
are the main contents of EED, Interfacing Media, and Aspects
of Topology.
C. Ontology Use
Since the aim of this knowledge management is to simplify
the software design aspect of a hardware/software co-
development, we approached the ontology organization of
EEA into the ontology-use-perspective of the EEA. We
consider the functionality network consisting of FFN and FN to
be the parent of three classes. Moreover, the functionality
network will be the object of the requreiment view.
Class diagram is used to define the ontology use of EEA
since the existing software development of EEA conforming to
FMEA and ISO 26262 is based on the development of the
software using object-oriented language, such as C++ or Java.
Fig. 6. Ontology Use for EEA
III. FAILURE MODE AND EFFECT ANALYSIS
Identification and obviation of a product and process
problems before the the product and process problems occur
can be defined in a systematic method. This method is called
Failure Mode and Effect Analysis (FMEA) [4][5].
There are different types of FMEA which are already
created and used in automotive system design and
development, especially in the electric and electronic
architecture of the automotive system. Specializations of
FMEA are normally related to design, construction, products,
and product processes.
The Failure Mode and Effect Analysis can be assumed as a
common method which is technically applied to increase
quality of a product. Using the FMEA, subsystems or systems
will be analyzed based on the occurance of faults and failures
which have to be prevented in early development phases. Since
faults and failures are normally related to safety, aspect of
safety plays a role in the analysis of systems and subsystems.
According to German Verband der Automobilindustrie e.V
– VDA, FMEA is composed of five steps [4][7]. The steps are :
1. Structural analysis phase.
2. Functional analysis phase.
3. Failure analysis phase.
4. Activity analysis phase.
5. Optimization and documentation phase.
The steps issued by VDA is used in purpose to address the
analysis of failure mode and effect. After the fifth step is
already done, result of a FMEA is issued officially and
technically using a FMEA form. Some experts will accomplish
the FMEA based on a discussion of results of the FMEA. An
existing method used to describe analysis suffers complexity,
especially in bridging meta and abstract models of requirement
and specification to concrete models based on software and
hardware developments.
We approached the description of combined five steps of
the FMEA mentioned above based on its concept description,
and ontology description. With ontology, we give credence that
at least software development combined with requirement and
specification can be developed and processed considerably
faster, based on evidence, rather than without using ontology.
A. Concept Description & Use of FMEA
Concept description and the concept use of FMEA are
shown in Fig. 7 and Fig. 8. Complex and unstructured
knowledge of Failure Mode and Effect Analysis can be
organized based on its concept using a visualization. Failure
Mode and Effect Analysis is constructed by five main
components, i.e. Failure Analysis, Failure Prevention and
Activities, Elements’ Interaction, Defining Functionalities, and
Reassessment and Documentation depicted in Fig. 7.
Fig. 7. Concept of FMEA
Moreover, the concept use of Failure Mode and Analysis is
shown in Fig. 8. This concept use describes the main
components constructing Failure Mode and Effect Analysis
(FMEA) and the role of its component. For instance, failure is
the agent, failure prevention is the action, definition is defined
in functionalities, interfacing for any electric/electronic
interaction, and the reassessment & report of the FMEA using
a certain method in database knowledge management.
262
 2014 International Conference of Advanced Informatics: Concept, Theory and Application (ICAICTA)
Fig. 8. FMEA in Conceptual Graph
B. Ontology Organization & Use of FMEA
Considering that FMEA consists of five steps and
simplifying the knowledge representation of Failure Mode and
Effect Analysis , we decide to choose Failure Analysis in
FMEA as the main concern. With the Failure Analysis, other
steps will be combined and associated together. Hence, the
model of FMEA can be modeled using the concept of ontology
based on the Fig. 9.
Structural Analysis will be the meta model of the Function
Analysis, and Failure Analysis will consist of several Activity
Analyses and Optimization & Documentation.
Fig. 9. FMEA in Ontology Organization
Due the abstraction of some analyses in FMEA, such as
Structural Analysis and Functional Analysis, idea of meta
models can be analyzed using the concept of object-oriented
model. Structural Analysis will be meta model of Functional
Analysis, or the Functional Analysis is the instance of
Structural Analysis.
Fig. 10. Class Diagram of FMEA’s Ontology Use
Failure Analysis itself is considered as the instance of
Functional Analysis since Failure Analysis can be only done if
the Functional Analysis has been analyzed or investigated.
Concept of describing the meta models of FMEA to the
concept of Object-Oriented Class Models is shown generally in
Fig. 10.
IV. ISO 26262 LIFECYCLE
ISO 26262 or ISO/DIS 26262 is a adapted lifecycle of IEC
61508 which will be dealing with application sector for design
and development of electric and/or electronic systems for road
vehicles.
The standard concerns also to safety as important key for
future road vehicle development. The role of hardware
development and software development in mechatronic
implementation has been increasing the complexity of software
development. The complexity may cause the occcurance of
system failures and hardware failures. As an important
standard, ISO 26262 is aimed to guide and describe many
possible risk of system’s failures by providing necessary
requirements and processes [8].
Fig. 11 below exhibits the complete structure of ISO26262
which consists of ISO 26262-3, ISO 26262-4, ISO 26262-5,
ISO 26262-6, and ISO 26262-7.
Fig. 11. Overview of ISO 26262 [3]
From the point of view of system-level development and
analysis, Electric/Electronic Architecture (EEA) can inserted
on the V-Model shown in Fig. 11, and EEA requires
developments in hardware and software aspects. From the
perspective of software aspect, we propose that the EEA can be
reconfigured and redeveloped using the concept of ontology.
Further approach and proposed idea of ontology-based
knowledge of EEA in FMEA according to the standard
ISO/DIS 26262.
263
 2014 International Conference of Advanced Informatics: Concept, Theory and Application (ICAICTA)
A. Concept Representation (Definition) of ISO 26262
ISO 26262 can be assumed as a regulated model used in
designing and developing electric/electronic components for
automobiles. We state the product development of
electric/electronic architecture is a concept constructed by
several significant factors depicted in Fig. 12, such as Concept
Phase, Supporting Phase, Management of Functional Safety,
ASIL-oriented and Safety-oriented Analyses, Levels or Scopes,
Production and Operation, and Guideline on ISO 26262.
Fig. 12 Concept Definition of ISO 26262
B. Ontology-based Organization, and Use of ISO 26262
ISO/DIS 26262 is an abstract description of a full
guidelines in designing Electric/Electronic Architecture for
automobiles from requirement view to test, operation, and
verification of the design at system level.
1. Ontology Organization
Fig. 13 Ontology Organization of ISO 26262
The ontology representation of ISO/DIS 26262, especially
the ontology organization, can be described using the
hierarchy of object-oriented (class) model of a software
development. The top hierarchy is the Management of
Functional Safety, and it has two main objects, i.e. Product
Development and ASIL-oriented & Safety-oriented Analyses
described in Fig. 13.
2. Ontology Use
Moreover, the ontology organization of ISO 26262 can be
used in software development of the system based on the
description shown in Fig. 14. All meta models and abstract
models can be defined using a class model.
Fig. 14 Ontology Use of ISO/DIS 26262
V. ONTOLOGICAL DESCRIPTION OF META MODEL COMBINING
EEA, FMEA, AND ISO/DIS 26262
A. Concept Definition of EEA, FMEA, and ISO/DIS 26262
The combination of EEA, FMEA, and ISO/DIS 26262 is
the main concern of the theoretical approach of this research.
Real and abstract aspects of the combination EEA, FMEA, and
ISO/DIS 26262 has been processed and described using
ontological approach. Ontological approach is very beneficial
to design a system from the perspective of software design and
development to avoid difficulties in stating the abstract models
of the combination of EEA, FMEA, and ISO/DIS 26262.
Fig. 15 Concept Definition of EEA, FMEA, and ISO/DIS 26262
The FMEA will depend only five important aspects relating
to the EEA, and ISO/DIS 26262. The five aspects are Failure
Analysis, Defining Functionalities, Failure Prevention and
Activities, Reassessment and Documentation, and Element’s
Interaction depicted in Fig. 15.
B. Ontology Organization of EEA, FMEA, and ISO/DIS 26262
Ontology-based organization in combining EEA, FMEA,
and ISO/DIS 26262 can be depicted in Fig. 16. The basic idea
of metamodeling of EEA, FMEA, and ISO/DIS 26262 is to use
five phases of FMEA. The highest level of the model is the
structural analysis which consists two lower levels, i.e.
functional analysis and defining functionalities.
Defining functionalities is constructed by blending concept
of EEA and ISO 26262. On the other hand, functional analysis
264
 2014 International Conference of Advanced Informatics: Concept, Theory and Application (ICAICTA)
is related directly to failure analysis of the system, and this
module is constructed by one module, called as ASIL-oriented
and Safety-oriented Analysis of ISO 26262,
Furthermore, the failure analysis aspect has a strong
relation to optimization and documentation of ISO 26262, and
to activity analysis concerning aspects of EEA and ISO 26262.
Fig. 16 Ontology Organization of EFI (EEA, FMEA, and ISO 26262)
C. Ontology Use of EFI (EEA, FMEA, and ISO/DIS 26262)
Indeed, the ontology of combining EEA, FMEA, and
ISO/DIS 26262 abbreviated as EFI consists of fourteen classes.
The number of hierarchies is up to four levels shown in Fig. 16.
Design and development of Electric/Electronic Architecture
based on the concept Failure Mode and Effect Analysis
according to ISO/DIS 26262 is possibly described in meta
models which normally have many abstract data types or
classes. However, the difficulty in describing abstract objects
can be solved using ontology as the knowledge representation.
Fig. 17 Ontology Use of EEA, FMEA, and ISO/DIS 26262
VI. CONCLUSIONS & FURTHER DISCUSSIONS
We are able to describe and represent the knowledge of
Electric/Electronic Architecture in the view of Failure Mode
and Effect Analysis based on the standard of ISO/DIS 26262.
This knowledge representation follows the concept of
ontology, and ontology is believed that it is able to describe
meta models of a system or abstract objects of a system.
Furthermore, the ontology use shown in many class models
will be definitely possible to be implemented using a certain
object-oriented programming languages, such as Java or C++
for the design and development of a system.
The proposed knowledge representation will be
implemented in the real software/hardware design &
development, and is expected to decrease the development time
of implementing EEA based on FMEA and ISO/DIS 26262.
One more possible added value obtained in using this
knowledge presentation is the combination of EEA, FMEA,
and ISO 26262 is modeled with a clear hierarchy using
ontology. For futher development of this research, a particular
study is needed to verify whether the performance of software
development using ontology will reduce its processing time, or
it will not.
REFERENCES
[1] J. Sowa, W. Tepfenhart, W. Cyre, “Conceptual Graphs: Draft
Proposed American National Standard," Springer-Verlag,
Berlin, Germany, Lecture Notes in Computer Science, 1999, pp.
1-65.
[2] C. Wei Qi, L. Juan Zi, W. Ke Hong, “CAKE: The Intelligent
Knowledge Modeling Web Services for Semantic Web,” The
8th International Conference on Computer Supported
Cooperative Work in Design Proceedings 26-28 May 2004,
Xiamen, China., 2004.
[3] International Organization for Standardization, “ISO/DIS 26262
Road Vehicles – Functional Safety, Part 1 – 10,” International
for Standardization www.iso.org, Tech. Rep., 2010.
[4] Verband der Automobilindustrie, “Produkt- und Prozess-FMEA.
Band 4. Sicherung der Qualität vor Serieneinsatz,
Qualitätsmanagement-Center (QMC),“ Verband der
Automobilindustir e.V. VDA, Tech. Rep., 2009.
[5] R. E. McDermott, R. J. Mikulak, and M. R. Beauregard, “The
Basics of FMEA (The 2nd Edition),” New York, USA :
Productivity Press., 2009.
[6] M. Hillenbrand, M. Heinz, J. Matheis, and K.D. Mueller-Glaser,
“Development of Electric/Electronic Architectures for Safety
Relevant Vehicle Functions,” Software – Practice and
Experience Vol. 42. New York : John Wiley & Sons, Ltd., 2012.
[7] M. Hillenbrand, M. Heinz, N. Adler, J. Matheis, and K.D.
Mueller-Glaser, “Failure Mode and Effect Analysis Based on
Electric and Electronic Architectures of Vehicles to Support the
Safety Lifecycle ISO/DIS 26262,” Proceedings of the 21st IEEE
International Symposium on Rapid System Prototyping,
Virginia, USA., 2010.
[8] M. Hillenbrand, M. Heinz, N. Adler, K.D. Mueller-Glaser, J.
Matheis, and C. Reichmann, “ISO/DIS 26262 In The Context of
Electric and Electronic Architecture Modeling,” Proceedings of
the 1st International Symposium on Architecting Critical
Systems (ISARCS) 2010, Prague, Czech Republic., 2010.
[9] M. Hillenbrand, M. Heinz, K.D. Mueller-Glaser, N. Adler, J.
Matheis, and C. Reichmann,“ An Approach for Rapidly
Adapting the Demands of ISO/DIS 26262 to Electric/Electronic
Architecture Modeling” Proceedings of 21st IEEE International
Symposium on Rapid System Prototyping, Virginia, USA.,
2010.
265