Importing & Exporting

Importing & Exporting - ProSET®
Importing & Exporting – ProSET®

ProSET®s importing and exporting functions allow for quicker creation of projects or Reports from CSV files:

  • Importing of SIFs
  • Importing of Initiating Events (LOPA / Risk Matrix) to Hazard
  • Import SRS to Hazard
  • Import Elements to Hazard
  • Import Branches
  • Import Branches to Hazard
  • Import Site Structures
  • Export Hazards
  • Export Elements

Importing HAZARDs

SIFs are imported by clicking on Tools -> Import SIFs.

ProSET® – Hazard Import Template.csv, which is also included in your installer file, contains the columns which can be imported and we recommend you use this template for imports.

The data is validated before importing which can cause warnings.? Help on this can be found in Troubleshooting guide below.

You can create your own import templates using the following headings:

Hazard Details

  • ID
  • SIF Tag / ID
  • SIF Description
  • PHA ID
  • Node
  • Hazardous Event
  • Drawing Number / Sheet Number
  • Site Structure Level 1 Name (reference)
  • Site Structure Level 2 Name (reference)
  • Site Structure Level 3 Name (reference)
  • Site Structure Level 4 Name (reference)
  • Recommendation
  • Note

SIL Determination

  • Determination Type
  • LOPA Consequences
  • Risk Matrix Consequences
  • Risk Matrix Likelihood
  • Risk Matrix Likelihood Justification
  • Selected Target
  • Selected Target ID
  • Custom PFD Target
  • Custom SIL Target
  • Assessment Justification
  • Selected Status
  • Custom Status

SIL Verification

  • Demand Mode
  • Process Safety Time

Importing Software Requirement Specification

Software Requiremnet Specifications are imported to Hazards by clicking on Tools -> Import Software Requirement Specification.

The SRS within your project is configurable so there are no supplied titles to import SRS data.? These shall be based on your SRS field names.

The refence details for the Hazard per row are:

  • Hazard ID ? The ID presented in the Hazards overview screen
  • Hazard SIF Tag ? The SIF Tag of the SIF used to mitigate the hazard
  • Site Structure Level 1 Name (reference)
  • Site Structure Level 2 Name (reference)
  • Site Structure Level 3 Name (reference)
  • Site Structure Level 4 Name (reference)

Importing Initiating Events & IPLs

Initiating Events and IPLs are imported to LOPA by clicking on Tools -> Import Initiating Events to Hazards.

Initiating Events and IPLs are imported to Risk Matrix SIL Determination method by clicking on Tools -> Import Risk Matrix Initiating Events to Hazards.

ProSET® – Initiating Events Import Template.csv, which is also included in your installer file, contains the columns which can be imported and we recommend you use this template for imports.

Initiating Events can only be imported for existing Hazards, by providing one of either the Hazard ID or SIF Tag in your import (If both are supplied the Hazard ID is used if a corresponding Hazard is found, otherwise the SIF Tag is used).

Note: It is not possible to export initiating events to a ?.csv? file.

The data is validated before importing which can cause warnings.? Help on this can be found in Troubleshooting guide below.

You can create your own import templates using the following headings:

  • Hazard ID ? The ID presented in the Hazards overview screen
  • Hazard SIF Tag ? The SIF Tag of the SIF used to mitigate the hazard
  • Site Structure Level 1 Name (reference)
  • Site Structure Level 2 Name (reference)
  • Site Structure Level 3 Name (reference)
  • Site Structure Level 4 Name (reference)
  • IE Description ? A description of the initiating event
  • IE Frequency ? The frequency of the initiating event. Note: The event frequency must be in the units of “per year”
  • IE Justification ? The justification for the frequency entered
  • Is Human Error Event
  • Probability of Error
  • IPL Type
  • IPL Custom Type
  • IPL Tag
  • IPL Description
  • IPL Justification
  • IPL Factor
  • Factor Category ID

To apply multiple IPLs/CMs to an imported Initiating Event, add a second row with blank Hazard and Initiating Event Fields and supply the details of the additional IPLs/CMs.? The parent Hazard and Initiating Event will be the last ones supplied.

Import Elements

Elements are imported by clicking on Tools -> Import Elements.

ProSET® – Elements Import Template.csv, which is also included in your installer file, contains the columns which can be imported and we recommend you use this template for imports.

Elements can only be imported for existing Failure Rates, by providing the Failure Rate properties in your import.

The data is validated before importing which can cause warnings.? Help on this can be found in Troubleshooting guide below.

You can create your own import templates using the following headings:

  • Failure Rate Type (reference)
  • Failure Rate Subsystem (reference)
  • Failure Rate Category (reference)
  • Failure Rate Manufacturer (reference)
  • Failure Rate Description (reference)
  • Failure Rate Source Short (reference)
  • Device Tag
  • Device Justification
  • MRT
  • PTC
  • PTI
  • PATC
  • PATI
  • Mission Time
  • Fail Safe
  • Energise To Trip
  • Site Structure Level 1 Name (reference)
  • Site Structure Level 2 Name (reference)
  • Site Structure Level 3 Name (reference)
  • Site Structure Level 4 Name (reference)

Importing Site Structures

Site Structures are imported by clicking on Tools -> Import Site Structures.

ProSET® – Site Structures Import Template.csv, which is also included in your installer file, contains the columns which can be imported and we recommend you use this template for imports.

You can create your own import templates using the following headings:

  • Level1 Name
  • Level1 IsSIS
  • Level1 Description
  • Level2 Name
  • Level2 IsSIS
  • Level2 Description
  • Level3 Name
  • Level3 IsSIS
  • Level3 Description
  • Level4 Name
  • Level4 IsSIS
  • Level4 Description

Import Branches

More details to follow

Import Branches on Hazards

More details to follow

Exporting SIFs

SIFs are exported by clicking on Tools -> Export SIFs.

SIFs can be exported from an existing project to a CSV file.

Calculated PFD Targets and SIL Targets from a SIL Determination are exported along with manually set Custom Targets. However only manually set Custom PFDs and Custom SILs can be imported back into SIL Comp, as the information required to calculate the PFD and SIL Targets was not exported/imported (ie. Initiating Events, IPLs, Conditional Modifiers and Consequences).

Export Elements

Elements are exported by clicking on Tools -> Export Elements.

Elements can be exported from an existing project to a CSV file.

Troubleshooting

Data to be imported is validated to ensure the integrity of a project.? Therefore the following should be kept in mind:

Before importing SIFs from a CSV file, the CSV file being imported must not be open or the following error will arise:

In the instance when columns have been deleted and / or columns have been left blank, the following error can arise:

When errors occur you can Continue which will import “valid” rows.? Clicking Cancel will not import any rows.? You can then correct any invalid rows and then re-import.

SIF Tags must be unique, so in the instance where a Hazard with a SIF Tag that already exists within the project is imported the following warning will be shown, and the SIF will NOT be imported.