The Hazards Data Loader allows you to implement HAZOP Analysis when you have data in a legacy system that is not supported by Meridium Enterprise APM. To import data using the Hazards Data Loader, Meridium, Inc. provides an Excel workbook, Hazards.xlsx, which supports baseline Hazards Analysis in Meridium Enterprise APM. You must export your legacy system so that the data can be used to populate the workbook. The data from the workbook will then be imported into Meridium Enterprise APM using the Hazards Data Loader.
Note: The Excel template is referred to throughout this documentation as the data loader workbook.
The data loader workbook can be used in the following scenario:
Loading existing legacy HAZOP analysis data into Meridium Enterprise APM so that you can retain visibility into previous HAZOP analyses, view the risk mitigation graph and re-validation schedules.
After importing the data, the Hazards Data Loader creates the following records in Meridium Enterprise APM:
Hazards Analysis
Hazards Analysis System/Node
Hazards Analysis Deviation
Hazards Analysis Cause
Hazards Analysis Consequence
Hazards Analysis Safeguard
Independent Layer of Protection
Risk Assessment
Risk Assessment Recommendation
Human Resource
Note: This data loader workbook is not backward compatible to earlier versions of Meridium Enterprise APM.
There are two scenarios associated with modifications to the Hazards Data Loader:
Meridium, Inc. modifies the data model from one version to the next to enable a new feature or an enhancement to an existing feature. In this scenario, the data loader workbook will be modified and maintained by Meridium, Inc. between releases to accommodate the new or enhanced feature.
You want to extend the Hazards Data Loader to accommodate importing additional fields, which are not present in the baseline family, or you want to extend the Hazards Data Loader to accommodate importing additional families or other related entities that were not considered as part of the baseline Hazards Data Loader. This is currently not supported and will be a future consideration.