Production Loss Analysis Deployment

Deploy PLA 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	Review the PLA data model to determine which relationship definitions you will need to modify to include your custom equipment and location families. Via Configuration Manager, modify the relationship definitions as needed.	This step is required only if you store equipment and location information in families other than the baseline Equipment and Functional Location families.
2	Assign Security Users to one or more of the Production Loss Analysis Security Groups and Roles.	This step is required. Users must have permissions to the PLA families to use the PLA functionality.
3	Change the default currency symbol.	This step is optional. By default, the currency symbol is set to $ and appears in the following places: Default Margin field on the Production Profile datasheet. Production Summary workspace.
4	Define all products.	This step is required. You must define all products whose production you plan to track using PLA. Each product is stored in a Product record.
5	Define Production Units.	This step is required. You must identify the Production Units that produce the products you defined in the previous task. A single product can be produced by more than one Production Unit. A single Production Unit can also produce more than one product. Each Production Unit is stored in a Production Unit record, which can be linked to an existing Functional Location record that contains detailed information about the Production Unit.
6	Define Production Profiles.	This step is required. For each Production Unit that you defined in the previous step, you must identify all the products that it produces and information about those products, such as the maximum demonstrated rate of production and the amount of profit one of those products yields. The combination of data about a product and the corresponding Production Unit is the Production Profile for that Production Unit. A Production Unit will have one Production Profile for each product it produces. Each Production Profile is stored in a Production Profile record, which is linked to the corresponding Product record and Production Unit record.
7	Define Production Event Codes.	The baseline APM database contains Production Event Code records that define a set of basic production event codes. Therefore, this step is required only if you do not want to use the baseline production event codes or if you want to use codes in addition to those that are provided. You must use Production Event Codes to categorize the types of events that can cause you to produce less than the maximum sustained capacity amount. Production Event Codes define the cause of lost production and answer the question: Why are we losing production? You can also group the types of events by structuring them in a hierarchy. For example, you might group event types into planned and unplanned, where planned events are events such as maintenance down days or employee holidays, and unplanned events are events such as equipment failures or natural disasters (e.g., floods or hurricanes). Each production event code will be stored in a separate Production Event Code record.
8	Define Impact Codes.	The baseline APM database contains Impact Code records that define a set of basic Impact Codes. Therefore, this step is required only if you do not want to use the baseline Impact Codes or if you want to use codes in addition to those that are provided.
9	Define OEE Codes.	The baseline APM database contains OEE Code records that define a set of basic OEE Codes. Therefore, this step is required only if you do not want to use the baseline OEE Codes or if you want to use codes in addition to those that are provided. For non-baseline codes to be included in the OEE Metric View, however, they must be children of the baseline parent codes.
10	Configure PLA for OT Connect integration: Deploy OT Connect. Note: Deploying OT Connect requires the OT Connect license. Configure the PLA Service policy. Link Production Profile records to Policy Instance ID records.	This step is required if you want to use the integration between PLA and the OT Connect feature where Production Data records are created automatically using the baseline PLA Service policy in Policy Designer.
11	Replace the Top 10 Bad Actors query for the PLA Overview page.	This step is optional. The Top 10 Bad Actors query is used by APM to populate the Top 10 Bad Actors graph on the PLA Overview page. In some databases, when viewing this graph, you may receive an error that prevents the graph from populating correctly. If this error occurs, replace the Top 10 Bad Actors query.