Hazards Analysis Deployment
Deploy Hazards Analysis for the First Time
The following table outlines the steps that you must complete to deploy and configure this module for the first time. These instructions assume that you have completed the steps for deploying the basic system architecture.
These tasks may be completed by multiple people in your organization. We recommend, however, that the tasks be completed in the order in which they are listed.
Step | Task | Notes |
---|---|---|
1 | Define alternate search queries. | This step is required only if you do not want to use the baseline search queries. |
2 | Manage the types of Deviations in a HAZOP Analysis. To do so, add a code to the MI_HAZOP_DECIATIONS system code table. For more information, refer to the System Codes and Tables section of the documentation. | This step is required only if you want to add another value to the list of default values in the Deviation/Guideword list in the HAZOP Deviation datasheet. |
3 | Activate the SIS Management license. | This step is required only if you want to take advantage of the integration between the SIS Management module and Hazards Analysis. |
4 | Assign Security Users to the MI SIS Administrator or MI SIS Engineer Security Group. Tip: For more information, refer to the Security Group topic for this module. | This step is required only if you want to take advantage of the integration between the SIS Management module and Hazards Analysis. |
5 | Review the Hazards Analysis data model to determine which relationship definitions you will need to modify to include your custom equipment or location families. Modify any relationship definitions as needed via the Configuration Manager application. | This step is required only if you store equipment and location information in families other than the baseline Equipment and Functional Location families. |
6 | Assign Security Users to one or more of the Hazards Analysis Security Groups and Roles. | This step is required. |
Update the Query Parameter Type
About This Task
After the database for APM is upgraded, if the entity key fields are of the type string, you must modify the catalog query parameters to use the correct type by performing the following steps:
Procedure
Revert the Hazard Analysis Queries to Baseline
This action is required only if you have modified the Hazard Analysis queries.