Objective
A new system configuration and device are proposed to enhance commercially available Personal Computers (PCs) towards the compliance with safety standards and the enhancement of the overall dependability. In addition, the implications and benefits of an integration of such components into interconnected critical infrastructure will be examined. Enhanced PCs including hardware and software add-ons would open the market of controlling systems for critical applications for entrepreneur due to much better cost/benefit ratios and usability. In this way, the SAFE-PC project would stimulate any new dependability concept involving which involves the use of ubiquitous standard PCs. The approach presented in this project allows the definition of simplified models for PC configurations and related commercial off-the-shelf (COTS) components.
Objectives:
The project aims at the following objectives:
1. Develop a Distributed System Architecture consisting of one or more dependability enhanced PC(s) and commercially available physical I/O units to implement even complex safety applications;
2. Enhance a commercially available PC by a Safety Layer such that it meets the safety requirements of the upcoming European Standard EN (IEC) 61508, SIL1 and SIL2, and of the existing EN 60601-1-4;
3. Additional commercially available tools shall be selected to enhance the quality of the user program, in particular with respect to Safety Communication. Regarding the graphical user interface (GUI), a subset of library shall be defined to meet the safety requirements of the upcoming European Standard EN (IEC) 61508, SIL1, and of the existing EN 60601-1-4;
4. Evaluation the new approach in real environments (Safety Cases) through safety assessment for various scenarios. It is foreseen to use a scenario from industrial automation and from medical area.
Work description:
The work will be split into subprojects according to the project objectives and the work of these subprojects will be organised in several workpackages according to a usual development life cycle. The subprojects related to objectives 1 and 2 are
(1) "Safety Requirements Specification";
(2) "Specification of the pre-existing system architecture in UML", and;
(3) "Design of the Safety Layers".
Subprojects (4) on "Specification of the pre-existing safety-related user interface concept" and (5) on "Commercially available Safety Communication" are related to objective 3. Finally, objective 4 will be tackled by the subprojects (6) "Prototype Implementation" and (7) "Pilot Installation".
The workload of these subprojects will be distributed into the following workpackages:
Workpackage 1:Management
Workpackage 2:Development of the Safety Requirements Specification compiling user requirements resulting from user surveys and the tailoring of the safety requirements of EN (IEC) 61508.
Development of the Preliminary System Specification incorporating the pre-existing safety-enhanced PC Architecture and the User Interface safety concept.
Workpackage 3:Development of Management System for Functional Safety in which the V&V plan for the whole project will be established.
Workpackage 4:Refinement of the existing system architecture using UML in which the software safety layers, the test framework and the safety-related user interface will be specified in detail.
Specification and selection of the distributed protective hardware unit and a commercially available safety communication protocol and software stack.
Workpackage 5:Prototype implementation in which both the software and hardware will be implemented and verified against EN (IEC) 61508 by Software Criticality Analysis, Software HAZOP and unit testing.
Adaptation of the distributed protective hardware unit and a commercially available safety communication protocol and software stack to the PC hardware and operating system software environment.
The safety integrity of the system configuration and its hardware implementation will be verified against EN (IEC) 61508 by a Failure Mode, Effect and Diagnostic Analysis (FMEDA) and a probabilistic calculation of the Probability of Dangerous Failure of the complete configuration.
Workpackage 6:Integration and testing in which laboratory integration testing and safety validation through fault insertion will performed.
Workpackage 7:Pilot installation and Functional Validation:
· Installation and application specific programming of the SafePC prototype in parallel to an existing safety system at a process industry application;
· Back-to-back testing of the application running on the SafePC prototype against the application running on the existing safety system;
· Feedback from the pilot customer and introduction of minor modifications such as bug fixes.
Workpackage 8:Dissemination and Exploitation, focusing on three areas:
1. Achieve a Consortium Contract which details the commercial agreement among the partners on the later rights for use of the results of the project;
2. Efforts to attract industrial key end-users by collaboration with standardisation committees, set-up of a workshop and/or presentation at events and conferences, a website for the project, press releases;
3. Develop a license model for two customer groups:
o End-users
primarily those users whose project needs exceed today's safety systems performance;
o Automation system vendors.
Milestones:
The project will develop both a full methodology framework for PC-based Distributed System Design and a first prototype implementation used in a selected pilot scenario. The methodology framework will include a full scale V&V safety case.
Major milestones are:
Milestone 1 (month 5):Specification of the functional and safety integrity requirements;
Preliminary System Specification;
Functional Safety Management Plan
Milestone 2 (month 8):Detailed design in UML
Milestone 3 (month 15):First prototype available
Milestone 4 (month 24):Result of user assessment.
Fields of science (EuroSciVoc)
CORDIS classifies projects with EuroSciVoc, a multilingual taxonomy of fields of science, through a semi-automatic process based on NLP techniques. See: The European Science Vocabulary.
CORDIS classifies projects with EuroSciVoc, a multilingual taxonomy of fields of science, through a semi-automatic process based on NLP techniques. See: The European Science Vocabulary.
- natural sciences computer and information sciences software software applications system software operating systems
- engineering and technology electrical engineering, electronic engineering, information engineering electronic engineering control systems
- social sciences economics and business business and management entrepreneurship
- social sciences sociology industrial relations automation
You need to log in or register to use this function
We are sorry... an unexpected error occurred during execution.
You need to be authenticated. Your session might have expired.
Thank you for your feedback. You will soon receive an email to confirm the submission. If you have selected to be notified about the reporting status, you will also be contacted when the reporting status will change.
Programme(s)
Multi-annual funding programmes that define the EU’s priorities for research and innovation.
Multi-annual funding programmes that define the EU’s priorities for research and innovation.
Topic(s)
Calls for proposals are divided into topics. A topic defines a specific subject or area for which applicants can submit proposals. The description of a topic comprises its specific scope and the expected impact of the funded project.
Calls for proposals are divided into topics. A topic defines a specific subject or area for which applicants can submit proposals. The description of a topic comprises its specific scope and the expected impact of the funded project.
Call for proposal
Procedure for inviting applicants to submit project proposals, with the aim of receiving EU funding.
Data not available
Procedure for inviting applicants to submit project proposals, with the aim of receiving EU funding.
Funding Scheme
Funding scheme (or “Type of Action”) inside a programme with common features. It specifies: the scope of what is funded; the reimbursement rate; specific evaluation criteria to qualify for funding; and the use of simplified forms of costs like lump sums.
Funding scheme (or “Type of Action”) inside a programme with common features. It specifies: the scope of what is funded; the reimbursement rate; specific evaluation criteria to qualify for funding; and the use of simplified forms of costs like lump sums.
Coordinator
76128 KARLSRUHE
Germany
The total costs incurred by this organisation to participate in the project, including direct and indirect costs. This amount is a subset of the overall project budget.