SIS Management Deployment

Deploy SIS Management 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	Modify threshold values in the SIL Threshold family.	This step is required only if you want to modify the default boundary values specified in the SIL Threshold family. Tip: To prevent ambiguity in SIL values for driving risk ranks that fall on the boundary value of two SIL thresholds, avoid specifying contiguous boundary values where the lower boundary value of one threshold is the upper boundary value of the preceding SIL threshold. For example, for the SIL value of 1, if you have specified a SIL threshold of 10 through 100, then, for a SIL value of 2 you can specify the SIL threshold of 100.1 through 1000.
3	Import data from an Exida project file.	This step is required only if you want to create SIL Analyses using an Exida project file.
4	Export data from an Exida project file.	This step is optional.
5	Activate the Hazards Analysis license.	This step is required only if you want to take advantage of the integration between the SIS Management module and Hazards Analysis.
6	Assign View permissions to the Hazards Analysis family to SIS Management Security Groups in Configuration Manager. As needed, you can assign additional privileges.	This step is required only for Security Groups that will be used in the integration between the SIS Management module and Hazards Analysis.
7	Review the SIS Management 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 using the Configuration Manager.	This step is required only if you store equipment and location information in families other than the baseline Equipment and Functional Location families.
8	Assign Security Users to one or more of the SIS Management Security Groups and Roles.	This step is required.
9	Configure SIS Management ActiveMQ Settings for SafetyExecution Service	This step is optional. You can perform this step if you want to modify the default retries or concurrency settings.
10	Ensure that the Meridium SafetyExecution Service is installed and running.	If the basic APM system architecture is already installed, the Meridium SafetyExecution Service is automatically installed, and the service runs automatically.

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

Access the Query page
Select Browse.
The Select a query from the catalog window appears.
Navigate to the folder containing the query that you want to update, and select the link for the query.
The Results workspace appears.
Select the SQL tab.
The SQL workspace appears, where you can modify the SQL code.
Modify all the entity key numeric parameters to string.
For example, (? :n) must be updated to (? :s).
Select Save.
The modified query is saved.

Revert the SIS Management Queries to Baseline

This action is required only if you have modified the SIS Management queries.

About This Task

If you have modified the SIS Management queries, perform the following steps to revert the query to baseline.

Procedure

Access the Catalog page.
Navigate to the Public folder for the query that you want to revert.
For SIS Management, the public queries are stored in the following folder:
Public\Meridium\Modules\SIS Management
Select the check box next to the query that you want to revert, and then select .
The Confirm Delete window appears, prompting you to confirm if you want to delete the selected query.
Select OK.
The selected query is deleted.
Navigate to the Baseline folder for queries.
For SIS Management, the baseline queries are stored in the following folder:
Baseline/Meridium/Modules/SIS Management
Select the check box next to the query that you want to revert, and then select .
The Catalog Folder Browser window appears.
Navigate to the folder containing the public query that you deleted in step 3.
Select OK.
A success message appears indicating that the selected item has been copied successfully.
Repeat Steps 2-8 for each query that you want to revert to baseline.

Configure SIS Management ActiveMQ Settings for SafetyExecution Service

The SafetyExecution Service,on each APM Server serves SIS Management module queues. This service is configured to use a single shared ActiveMQ queue service across APM. Available queue configuration options include retries and concurrency limit.

Procedure

On the APM Server, access the folder that contains the SafetyExecution Service files.

Note: If you have installed APM in the default location, you can locate the folder in C:\Program Files\Meridium\ApplicationServer\safety-execution
Access the appsettings.json file in an application that can be used to modify JSON files (for example, Notepad++).
In the file, locate the following text:
```
"Queue_Config": {
	    "Queues": [
	      {
	        "Name": "COPY_IF_Queue", 
	        "ConcurrencyLimit": 100,
	        "Retries": 5,
               "LimitPerTenantRequired": true
	      }
	    ]
          }
```
Note: ConcurrencyLimit indicates the maximum number of messages that will be consumed concurrently. Retries indicates the number of times it retries to send the messages to ActiveMQ if it fails. LimitPerTenantRequired indicates whether Maximum Concurrency limit per Tenant is specified in scheduler service for the queue.
Update the key values as desired.
Save and close the file.
The updated settings will be applied when the SafetyExecution Service is stopped and restarted.