Before You Begin

Before you install Plant Applications, complete the tasks described in this section.

Review Time Zone Settings

Ensure that the system time and time zone of the server and client that you want to use for Plant Applications are correct and in sync.
Note: Ensure that you must set the Plant Applications Server and the Database Server to the same time zone as that of the Default time zone site parameter.

Review Architecture Requirements

You must install a historian such as GE Digital Historian as well as prerequisite software such as SQL Server. Plant Applications supports Historian (standard or enterprise) 8.1.

Due to the competition for ports, “all-in-one” deployments are no longer supported. We recommend that Historian and Web Client be installed on separate server nodes.

Refer to Test and Production Environments to learn about architecture strategies to meet the needs of particular environments.

Review Upgrade References

If you are upgrading from version 7.0 SP5 and later, refer to Upgrade from Plant Applications Version 7.0 SP5 and Later for additional steps.

If you are installing the Plant Applications Server, Clients or Web Server report components in a clustered environment, review the information in Appendix B at Cluster Overview.

If upgrading the Unified Manufacturing Database (UMDB), refer to these sections:

System Requirements Location

Plant Applications Server and Client Requirements outlines system requirements.

Preparing for a UMDB Implementation

The UMDB essentially combines the SOADB database (S95 data model) and GBDB database (Plant Applications data model). You can choose to use only the Plant Applications data model by disabling UseProficyClient configuration parameter (ID 87). The following items are important to consider as a part of installation planning:
  • Strategy
    • Using the new, combined data model offered by the UMDB enables you to define a plant environment in an S95 structure while providing a strict and formal definition that was not possible with Plant Applications. Thus, it is advantageous to define all configuration information through the Client interface and to use Plant Applications for features that are unique to Plant Applications such as specifications, alarms, and downtime.
    • Although it may be helpful to configure some units in an S95 model, it may be practical to maintain the configuration of some units in Plant Applications. In this situation, it is important to carefully manage the configurations. Once data is extracted from Plant Applications to the S95 model, it retains characteristics of the S95 model. If units are defined in both models, problems with orphans can arise.
    • See Working with a Merged System and UMDB in Plant Applications Help for a description of the new Client interfaces and changes to the Plant Applications Administrator.
  • Database purges: Plant Applications supports a Unified Manufacturing Database (UMDB) to combine a SOA database employing an S95 data model with a Plant Applications database. Purging data from the UMDB is a two-step process involving both the Plant Applications and SOA purge utilities. The following notes apply to a purge of the Plant Applications database:
    • Perform online purges to Plant Applications databases before upgrading to the latest version.
    • For sites using only the Plant Applications data model, there are cursor purges that can be executed to trim the database as an interim solution.
    • For sites incorporating both the Plant Applications and S95 data models, do not purge the PA database as this will orphan data on the WF side and could introduce issues.
  • Conversion of custom containers and displays remains a GE IP Services function.
  • Moving or renaming a server after migrating to a UMDB.
    • Standard Plant Applications 5.0 scripts work with Plant Applications 8.1 to move or rename the server.
    • Refer to Workflow documentation for information about scripts and related procedures.
  • Recommended installation paths
  • New naming convention for specific Plant Applications tables starting in version 6.1.
    • UMDB tables have a _Base naming convention and are associated with SQL Views for improved performance and to enable modifications without impacting existing structures. Data is linked in a view to maintain compatibility between the S95 and Plant Applications models.
      Table SQL View
      Product_Base dbo.Products
      Prod_Lines_Base dbo.Prod_Lines
      Prod_Units_Base dbo.Prod_Units
      Departments_Base dbo.Departments
      Users_Base dbo.Users
      Variables_Base dbo.Variables
    • Modification of existing spLocals when upgrading to Plant Applications is not needed.
    • Table limitations on the Plant Applications side are not enforced in for the S95 structures to SOA to enable incorporation of proactive error checking for conditions inside workflows. It is recommended to incorporate field size limitations in documents where appropriate. For example, limit event_num.Events to 25 characters.
  • Reporting
    • Plant Applications has two reporting structures.
    • Plant Applications continues to have Web Reports for information that is specific to Plant Applications.
    • The SOA database (S95 data structure) has its own reporting.