Date 17-Dec-2015
Item Definition
<PROJECT>
Revision
Page 1 of 13
Status In review / released
<Insert Product Group>
<PROJECT>
Item Definition
RELEASE/REVISION: RELEASE/REVISION DATE: RELEASED BY:
TBD DD-MMM-YYYY TBD
Template: Item Definition
Revision Number: 2.0 - Status: Released
Date 17-Dec-2015
Item Definition
<PROJECT>
Revision
Page 2 of 13
Status In review / released
USING THIS TEMPLATE
To create an instance of this document:
Insert relevant information on cover sheet and in placeholders throughout.
Insert relevant information in header page and tile page by updating the document properties, e.g. the keyword field needs to
contain the relevant project information
A yellow box containing CONTENTS OF THIS SECTION is provided at the beginning of most sections and subsections. After
determining what specific information will be included in your document, you can remove this yellow box or leave it to serve as
a quick-reference section overview for your readers.
Consider hyper-linking key words used in the document with their entries in the Reference section or other location in which
they are defined. Choose Insert > Hyperlink.
Note: The objective of the template is to give guidance in creating the specific work product by providing a predefined structure and
information of the expected content for each section which are derived from ISO26262 standards. The provided structure may be
tailored to suit specific tools.
Table of Contents
<PROJECT> 1
1 Document Management and Configuration Control Information 3
2 Purpose 4
3 Scope 5
4 Acronyms & Definitions 5
4.1 Acronyms 5
4.2 Definitions 5
5 Functional Description5
5.1 Function 1: <TBD> 5
5.2 Function 2: <TBD> 5
5.3 Function n: <TBD> 5
6 Non Functional Requirements 6
6.1 Environmental Conditions 6
6.2 Operational Requirements 6
6.3 Restrictions 6
7 Legal Requirements 6
8 Applied Safety Standards and legal Safety Requirements 6
8.1 Behavior achieved by similar functions 7
8.2 Behavior expected from item 7
8.3 Potential consequences of insufficient behavior incl. Failure modes and hazards 7
9 Boundaries 8
9.1 Internal Boundaries 8
9.2 External Boundaries 8
10 Interfaces 9
10.1 Mechanical Interfaces 9
10.2 Sensor Interface 9
Template: Item Definition
Revision Number: 2.0 - Status: Released
Date 17-Dec-2015
Item Definition
<PROJECT>
Revision
Page 3 of 13
Status In review / released
10.2.1 Internal Sensor-Interfaces 9
10.2.2 External Sensor-Interfaces 10
10.3 Actuator Interface 10
10.3.1 Internal Actuator-Interfaces 10
10.3.2 External Actuator-Interfaces 10
10.4 Communication with other ECUs 11
10.5 Signal / Bus Communication 11
10.6 Additional Control Inputs 11
10.7 Further Signals 11
10.8 Interaction with other items 12
10.9 Requirements from other items 12
10.10 Requirements on other items 12
10.11 Allocation and distribution of functions among the items and elements involved 12
11 LIMITATIONS 12
12 References 12
13 Stakeholders13
14 Approval 13
15 Distribution 13
1 Document Management and Configuration Control Information
CONTENTS OF THIS SECTION: This section identifies the release number, release date, and other relevant management and
configuration control information associated with the current version of the document. Optional items for this section include: change
history and an overview of significant changes from version to version.
Release Date Prepared By Reviewed By Remarks / Changes
N.M. DD-MMM-
YYYY
Template: Item Definition
Revision Number: 2.0 - Status: Released
Date 17-Dec-2015
Item Definition
<PROJECT>
Revision
Page 4 of 13
Status In review / released
2 Purpose
The document “Item Definition” has the purpose to identify and describe a core- or application development at its
initial phase whit focus on functional safety aspects.
It shall create an adequate understanding of it with the task that each activity defined in the safety lifecycle of the ISO
26262 can be performed adequately. According to the standard, the item definition is to develop a description of the
item with regard to its functionality, interfaces, environmental conditions, legal requirements, known hazards etc. The
boundary of the system and its interfaces, as well as assumptions concerning other items, systems and components
are determined.
Based on the Item Definition, various functional safety work products such as the Hazard Analysis and Risk
Assessment, safety concepts and safety analyses shall be carried out or derived from (see following figure).
Hazard analysis
and risk assessment
3-7
Functional safety
concept
3-8
Operation, service
and
decommissioning
7-6
Production
7-5
Production
planning
7-5.4.1
Operation
planning
7-6.4.1
4
Product development:
system level
HW
level
5
SW
level
6
Safety validation
4-9
Consider
Controllability
Allocation
to other
technologies
Consider
External
measures
In the case of a
modification, back to
the appropriate
lifecycle phase
Concept phase
Product development
After release
for production
Item definition
3-5
Initiation of the
safety lifecycle
3-6
Management of functional safety
2-5 to 2-7
Functional safety
assessment
4-10
Release
for production
4-11
Fig. 1: Functional Safety Lifecycle (ISO 26262)
Remark:
In general the system is defined as entire application or function within a vehicle, including input signals, control
function and output devices. For most applications/functions this can only be done by the VM (vehicle manufacturer).
Further relevant information on input and output signals should be listed in this document but these are assumptions
regarding the described elements. For these elements a separate Item Definition should created by the relevant
supplier(s) or VM(s).
Template: Item Definition
Revision Number: 2.0 - Status: Released