CAPE-SAFE Data Model

In this section the physical data model of the proposed CAPE-SAFE within PEEE will be specified in more details. 

Examples of the data structures for different data groups within CAPE-SAFE are illustrated in appendix 3. 

Conduct Hazard Evaluation (Manually) Hazard Evaluation Results (Manual. History)  

Evaluation Results into Structured HE within CAPE-SAFE J 

Java program connected to SQL Server database to extract the keywords from the hazard evaluation text files, produced by experts over years in chemical/ petrochemical plants 

---

A prototype system framework of PEEE has been developed using Java and Visual Basic as object-oriented programming languages, while SQE server and MS-Access are used as RDBMS for data repository for the plant model elements. Such prototype solution will enable all plant users to utilize a standard user interface to manipulate plant lifecycle data/information/knowledge. The prototype system can be used as the framework to develop CAPE-SAFE as well as other components within PEEE. 

Figure 8-1 shows the data groups of the conceptual data model of CAPE-SAFE. In this diagram, PSP index includes the data related to downloading and uploading of safety data with PSPs. For consistency purposes, physical, behavior, and operation models of the plant process are represented in this picture although they are part of the plant design environment. 

Figure 9-16 shows another example where CAPE-SAFE is integrated with RCM-based CMMS to provide detailed information about the failure model. The safety-related data in the data warehouse proposed in the RCM-Based CMMS solution will be maintained from CAPE-SAFE module using predefined database scripts (SQL Server database procedures). 

In this section the proposed physical data model of CAPE-SAFE will be highlighted as extracted from the database created in SQL Server. In this experiment, MS-Access has been used as a front-end user interface to display and manipulate the data structure created within SQL Server. 

---