About the PLA Service Policy

About the PLA Service Policy

The PLA Service policy is delivered as a baseline module workflow policy in Policy Designer and is used to integrate PLA and the OT Connect feature. You can configure the instances of the PLA Service policy with OT Connect tags, and then link Production Profile records to Policy Instance records. After the policy instances are linked to the Production Profiles, any readings that are recorded in the associated OT Connect Tags will be used to create Production Data records automatically. The Production Data that is created appears in the Production Data workspace for each product.

Configure the PLA Service Policy

Before You Begin

  • Make sure that the following licenses are active:
    • Policy Designer
    • APM OT Connect
  • Make sure that the PLA Admin user is added to the following security groups:
    • MI OT Connect Viewer
    • MI Content Template User
    • MI Policy Designer
  • Make sure that the OT Connect server is configured.

About This Task

The PLA Service policy is available as a baseline module workflow policy. You can use this policy to integrate PLA and the OT Connect feature. This topic contains the steps that you need to perform to configure the PLA Service policy.

Procedure

  1. In the Applications menu, navigate to the TOOLS section, and then select Policy Designer.
    The Policy Designer Overview page appears.
  2. Select the Module Workflow Policies tab.
    The Module Workflow Policies section appears, displaying the list of module workflow policies.
  3. Select the PLA Service policy.
    The PLA Service policy details appear.
  4. Select the Design tab.
    The Design workspace appears displaying the policy model.
  5. Select the DataSource node.
  6. In the Value box of the Properties window, configure the Database ID.
  7. At the bottom of the Design workspace, select the Instances tab.
    The Instances pane appears.
  8. On the left side of the Instances pane, select .
    A new policy instance appears.
  9. Next to the OT Connect Tag box, select , and then select the OT Connect Tag.
  10. In the Point Value box, enter the Instance name.
    Important: The values are case sensitive. Make sure that the values in the Instance and Point Value boxes are exactly the same.
  11. On the right side of the Instances pane, above the grid, select .
    The policy instance is activated.
  12. On the Instances pane, select .
    The policy instance is saved.
    Note:
    • You can create more than one policy instance. However, for each instance, the OT Connect Tag must be unique.
    • If you delete a policy instance, make sure that the instance is unlinked from the production profile. The deleted instances may appear as junk values in the Policy Instance box of the Production Profile datasheet.
  13. Select the Security tab.
    The Security workspace appears displaying the list of assigned users and groups to the policy.
  14. Add the MI Production Loss Accounting Administrator security group to the policy, and then assign the following permissions:
    • Designer
    • User
    • Viewer
  15. Select .
    The security group is configured to the policy.

Configure PLA Service Policy Execution

Procedure

  1. In the Applications menu, navigate to the TOOLS section, and then select Policy Designer.
    The Policy Designer Overview page appears.
  2. Select the Module Workflow Policies tab.
    The Module Workflow Policies section appears, displaying the list of module workflow policies.
  3. Select the PLA Service policy.
    The PLA Service policy details appear.
    Note: The default Time Zone is in UTC. Do not change the Time Zone.
  4. Select the Scheduled Execution check box, and then configure the schedule frequency.
    Note: Make sure that all the instances are activated.
  5. If you do not want execute the policy for every trigger from the OT Connect tags, clear the Automatic Execution check box.
  6. Select .
    The PLA Service policy will be executed as per the scheduled interval, and the Production Data will be created or updated for the Production Profile associated plans.
    Note: The Production Data record is created by the MIJOB user, and not by the logged in user.