Scribd
Upload
37 views2 pages

Measures Required For The Creation of A User Programme Project Data

This document is a checklist for creating and modifying a user program. It contains yes/no questions to verify steps like performing a safety assessment, using approved programming components, removing force markers, reviewing and testing the program, and documenting the results. The checklist is to be completed before and after making changes to ensure proper procedures are followed.

Uploaded by

Garabig
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
37 views2 pages

Measures Required For The Creation of A User Programme Project Data

This document is a checklist for creating and modifying a user program. It contains yes/no questions to verify steps like performing a safety assessment, using approved programming components, removing force markers, reviewing and testing the program, and documenting the results. The checklist is to be completed before and after making changes to ensure proper procedures are followed.

Uploaded by

Garabig
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Measures required for Checklist No.

MEAP-0001-E
the creation of a user programme Version 2.1 / 02.07
Project data
Project designation File name of checklist /
archiving number

Notes, verifications yes no Comments

Prior to change
Is the configuration and the user program based on a safety
assessment?
Are programming guidelines used to create a user program?

Are only tested and approved programming organization units


(functions, function blocks, program) used to create the user
program?
Are functionally independent parts of the PES encapsulated by
the use of function and function building blocks?
Is it taken into consideration that after a change of variable
names and subsequent reload a re-initialization of the
variables is performed?
Is it taken into consideration that after a reload, set outputs will
remain set although these set outputs are not assigned a value
after the deletion of parts of the user logic?
If the online change of a constant is to be retained after reload:
Has this constant been adapted accordingly in the program
prior to the generation of the code?
After modification

Notes, verifications yes no Comments

Prior to loading

Have all force markers been removed from the application


program?
Has a review of the user program against the binding
specification been performed by a person not involved in the
implementation of the program?
Has the result of the review been documented and released
(date/signature)?
Has an off-line test been performed?

After loading

Is the RUN version of the program which can be changed


online identical to the RUN version of the program adapted
after an on-line change of constants?
Check at the diagnostic display:
Has the desired program been loaded?
Check at the diagnostic display:
Does the error display show non-existing modules or other
error messages?
Has a backup of the complete program been made after the
program has been loaded into the PES?
Has an online test been performed?

Has a sufficient number of tests been performed for all safety-


related logical circuits (including inputs and outputs) and for all
mathematical calculations (intermediate results, limits etc.)?
After the rejection of a modification of an online constant:
Has the program been reloaded or has the constant been reset
online to its original value?
Has the correct data transmission to other systems been
tested?
Has forced information been reset prior to safety-related
operation?

Date Created by

You might also like