Discover - Design Phase
When it comes to risk reduction by controls, the SRS (Safety Requirement Specification) define what needs to be accomplished by an associated safety function. ADVANTIS automatically produces a list of all the SRS as the result of the Risk Assessment. This list can be seen as the to do list for the control system design engineer. This job is not done until all SRS are being addressed by an according safety function design.
This is the most important part in the Design phase.
Select a SRS in the SRS list.
Each Safety Function Design will be associated with a SRS unique.
SRS = Safety Requirement Specification
A safety function design contains the following parts:
- SRS (Safety Requirement Specification)
- Hardware - Block Diagram
- Hardware - Subsystem Design (Input, Logic Solver, Output)
- Hardware - SISTEMA Verification
- Software - Block Diagram
All relevant information needed for the design of a safety function.
The first part of the safety function design is dedicated to the used hardware (devices) and their interaction with each other (wiring). The so called top level block diagram visualizes the safety function for better understanding. This diagram is automatically generated by ADVANTIS based on sub-system information provided by the user.
This reflects the core of the hardware design. Here the design engineer documents which device he is using and how this device is connected to other devices. All sub-systems are divided into the three areas input, logic solver and output.
This reflects a simple reference to the actual SISTEMA file and associated safety function. In a future release of ADVANTIS we will integrate SISTEMA calculations so that the user has a fully integrated tool on hand.
Similar but different is the documentation of the PLC code (software) for any given safety function. ADVANTIS lets the user define his own so called blocks based on how he structured his PLC code. Every block should represent a part of the PLC code independent of the programming language used. Each block then has a reference to the PLC code as well as an explanation of the purpose and its function.
After each printing of a FINAL Design Verification Report, it will be logged here
Printing of a DRAFT DVR will not have an effect on the change history entry. The entry can be edited.
Printing of a FINAL DVR will finalize the change history entry. The entry can no longer be edited.