IEC Certification Kit

Simulink® PLC Coder™

Conformance Demonstration Template

R2015a
How to Contact MathWorks
Latest news: www.mathworks.com
Sales and services: www.mathworks.com/sales_and_services
User community: www.mathworks.com/matlabcentral
Technical support: www.mathworks.com/support/contact_us
Phone: 508-647-7000
The MathWorks, Inc.
3 Apple Hill Drive
Natick, MA 01760-2098
IEC Certification Kit: Simulink® PLC Coder™ Conformance Demonstration Template
© COPYRIGHT 2010–2015 by The MathWorks, Inc.
The software described in this document is furnished under a license agreement. The software may be used or copied only under
the terms of the license agreement. No part of this manual may be photocopied or reproduced in any form without prior written
consent from The MathWorks, Inc.
FEDERAL ACQUISITION: This provision applies to all acquisitions of the Program and Documentation by, for, or through the
federal government of the United States. By accepting delivery of the Program or Documentation, the government hereby agrees
that this software or documentation qualifies as commercial computer software or commercial computer software documentation
as such terms are used or defined in FAR 12.212, DFARS Part 227.72, and DFARS 252.227-7014. Accordingly, the terms and
conditions of this Agreement and only those rights specified in this Agreement, shall pertain to and govern the use, modification,
reproduction, release, performance, display, and disclosure of the Program and Documentation by the federal government (or
other entity acquiring for or through the federal government)and shall supersede any conflicting contractual terms or conditions.
If this License fails to meet the government’s needs or is inconsistent in any respect with federal procurement law, the
government agrees to return the Program and Documentation, unused, to The MathWorks, Inc.
Trademarks
MATLAB and Simulink are registered trademarks of The MathWorks, Inc. See www.mathworks.com/trademarks for a
list of additional trademarks. Other product or brand names may be trademarks or registered trademarks of their respective
holders.
Patents
MathWorks products are protected by one or more U.S. patents. Please see www.mathworks.com/patents for more
information.
Revision History
September 2010 New for Version 1.2 (Applies to Release 2010a)
September 2010 Revised for Version 1.3 (Applies to Release 2010b)
April 2011 Revised for Version 1.4 (Applies to Release 2011a)
September 2011 Revised for Version 2.0 (Applies to Release 2011b)
March 2012 Revised for Version 2.1 (Applies to Release 2012a)
September 2012 Revised for Version 3.0 (Applies to Release 2012b)
March 2013 Revised for Version 3.1 (Applies to Release 2013a)
September 2013 Revised for Version 3.2 (Applies to Release 2013b)
March 2014 Revised for Version 3.3 (Applies to Release 2014a)
October 2014 Revised for Version 3.4 (Applies to Release 2014b)
March 2015 Revised for Version 3.5 (Applies to Release 2015a)
Contents
1 Introduction ...................................................................................................................................... 1-1
1.1 Conformance Demonstration Template Overview .................................................................. 1-2
1.2 Application Identification ........................................................................................................ 1-3
2 Design Verification .......................................................................................................................... 2-1
3 PLC Code Verification ..................................................................................................................... 3-1
4 Additional Considerations ................................................................................................................ 4-1

v
vi
1 Introduction
1.1 Conformance Demonstration Template Overview
This Conformance Demonstration Template can be used to demonstrate conformance with the
parts of ISO 26262-6/8, IEC 61508-3, or EN 50128 covered in the document

Simulink® PLC Coder™ Reference Workflow

To access the reference workflow document, on the MATLAB ® command line, type
certkitiec to open the Artifacts Explorer. The reference workflow document is in Simulink
PLC Coder > r2015a.

For each technique or measure:

 In the third column, state to what degree you applied the technique or measure for the
application under consideration by using one of the phrases: Used, Used to a limited
degree, or Not used.

 In the fourth column, state how you used the technique or measure in the application under
consideration. If the reference workflow includes alternative means for compliance,
indicate what variant you used. In addition, enter a reference to the document (for example,
test report or review documentation).

1-2
1.2 Application Identification
Applicant: <Insert information>
Application: <Insert information>

1-3
1-4
2 Design Verification
 Checklist 1: Design Verification

Technique / Measure Associated Requirements Used / Used to Interpretation in

a limited degree this application,
/ Not used Evidence
1 Model review  Inclusion of model components

(See “Reviews and Static

Analyses at the Model
Level” in the Simulink®
PLC Coder™ Reference
Workflow)
2 Adherence to modeling  Designation of a modeling
standard standard

(See “Reviews and Static  Review the modeling standard

Analyses at the Model as suitable for use
Level” in the Simulink  Restriction to modeling
PLC Coder Reference constructs suited for PLC code
Workflow) generation
 Evidence for using the
modeling standard
3 Static analysis at the  Evidence for using static
model level (if analyzers
applicable)

(See “Reviews and Static

Analyses at the Model
Level” in the Simulink
PLC Coder Reference
Workflow)
4 Supporting activities  Documentation of the results of
reviews and analyses
(See “Reviews and Static
Analyses at the Model  Corrective action on failure of
Level” in the Simulink reviews and analyses
PLC Coder Reference
Workflow)

2-2
 Technique / Measure Associated Requirements Used / Used to Interpretation in
a limited degree this application,
/ Not used Evidence
5 Module and integration  Inclusion of model components
testing at the model level
 Consideration of intended and
possible unintended functions
(See “Module and
Integration Testing at the  Systematic design of test
Model Level” in the vectors
Simulink PLC Coder
Reference Workflow)  Inclusion of test vectors being
derived from the specification
according to established criteria
 Consideration of model
integration stages
 Consideration of module
interaction
6 Supporting activities  Documentation of the results of
module and integration tests,
(See “Module and including test results and
Integration Testing at the achievement of test objectives
Model Level” in the and criteria
Simulink PLC Coder
Reference Workflow)  Corrective action on failure of
module and integration tests
 Impact analysis

2-3
2-4
3 PLC Code Verification
 Checklist 2: PLC Code Verification

Technique / Measure Associated Requirements Used / Used to Interpretation in

a limited degree this application,
/ Not used Evidence
7 Equivalence test vector  Structural coverage with respect
generation to applicable model coverage
metrics (SIL 2 and above); see
(See “Equivalence Test table “Model Coverage
Vector Generation” in Analysis”
the Simulink® PLC
 Creation of additional test
Coder™ Reference
vectors (if applicable)
Workflow)
 Assessment of or justification
for uncovered model parts
8 Equivalence test vector  Stimulation of the model used
generation for PLC code generation
 Stimulation of the PLC IDE
(See “Equivalence project derived from the
Test Vector Generation” generated Structured Text code
in the Simulink PLC
Coder Reference  Test execution in a target-like
Workflow) environment or analysis of the
differences between testing and
the target environment
 Assessment of model parts used
for simulation but not for PLC
code generation
9 Signal comparison  Designation of a suitable
comparison algorithm and
(See “Signal acceptance threshold
Comparison” in the
 Comparison of simulation
Simulink PLC Coder
results and execution results
Reference Workflow)
10 Supporting activities  Corrective action on failure of
equivalence tests
(See “Equivalence
 Evidence for using automated
Testing Model Versus
equivalence testing tools
Structured Text” in the
Simulink PLC Coder  Evidence for validation of
Reference Workflow) equivalence testing tools

3-2
 Technique / Measure Associated Requirements Used / Used to Interpretation in
a limited degree this application,
/ Not used Evidence
11 Prevention of  Traceability review
unintended functionality
(SIL 2 and above)  Assessment of or justification
for issues revealed
(See “Prevention of
Unintended
Functionality” in the
Simulink PLC Coder
Reference Workflow)
12 Supporting activities  Documentation of the results of
demonstrating the absence of
(See “Prevention of unintended functionality
Unintended
 Corrective action on failure to
Functionality” in the
demonstrate the absence of
Simulink PLC Coder
unintended functionality
Reference Workflow)

3-3
3-4
4 Additional Considerations
 Checklist 3: Additional Considerations

Technique / Measure Associated Requirements Used / Used to Interpretation

a limited degree in this
/ Not used application,
Evidence
13 Deviation from the  Documentation and justification
reference workflow for deviations from the reference
workflow by using a deviation
(See “Deviation from procedure, if applicable
the Reference
Workflow” in the
Simulink® PLC Coder™
Reference Workflow)
14 Integration with the  Documented software safety
software safety lifecycle lifecycle, including application-
specific verification and validation
(See “Integration with activities
the Software Safety
Lifecycle” in the
Simulink PLC Coder
Reference Workflow)
15 Configuration  Revision control for artifacts to be
management and validated or verified
revision control
 Configuration management for
artifacts to be validated or verified
(See “Configuration
(SIL 2 and above)
Management and
Revision Control” in the
Simulink PLC Coder
Reference Workflow)
16 Installation integrity and  Validation of modification and
release compatibility additions to shipping tools (if
applicable)
(See “Installation
 Compatibility of product versions
Integrity and Release
for model creation, code
Compatibility” in the
generation, and translation
Simulink PLC Coder
validation
Reference Workflow)

4-2
 Technique / Measure Associated Requirements Used / Used to Interpretation
a limited degree in this
/ Not used application,
Evidence
17 Bug reporting  Assessment of bug report
information provided by tool
(See “Bug Reporting” in vendors and compliance with
the Simulink PLC Coder recommendations and
Reference Workflow) workarounds (during development
and after deployment)
 Reporting of issues with
MathWorks® products
18 Competency of the  Evidence for competence of
project team project team members

(See “Competency of
the Project Team” in the
Simulink PLC Coder
Reference Workflow)

4-3