Database Setup Strategies

The SOA platform and Plant Applications employ SQL databases running on SQL Server software to store information.

Merging an existing SOA database with an existing Plant Applications database to form a Unified Manufacturing Database (UMDB) requires detailed planning, The strategy you employ to set up database depends on your existing situation and your goals. For example, you can opt for a new installation with a new database, or you can upgrade an existing database to install a UMDB. It is probably a rare case that you would need to install a UMDB that combines existing SOA and Plant Applications databases. The UMDB can reside on the same machine as the Plant Applications server or on a separate server with SQL Server installed.

You can use one of the following basic strategies for establishing a database:

Create a New Database for New Data

Enter a new database name during the Workflow installation with the intention of starting fresh with new data for a new UMDB to hold and Plant Applications data. The necessary SQL database tables, compatible with the software versions, are set up.

When using Workflow Client to create equipment, material, and personnel, the entities are aspected to the Plant Applications data model for access in Plant Applications. In the same way, entities created in Plant Applications are aspected for use in the Workflow Client. To create a new database, enter a new database name. Refer to Plant Applications Client Help for information about Fully Qualified Domain Names.

You should back up an existing database before installing a new release of Workflow or Plant Applications. SQL Server changes to the SOA database, such as the addition of data models and tables included with software, cannot be reversed.

Point to an Existing Database

If you have an existing SOA or Plant Applications database, you can point to the database during the Workflow installation and a subsequent Plant Applications installation. To point to an existing database, enter its name when prompted for a database name. During the Workflow installation, SOA data tables are updated for compatibility with new software.

When Plant Applications is installed, the MESCore Service Provider adds the necessary Plant Applications tables and aspects to the SOA database to install a UMDB. If you are using only an existing Plant Applications database, it will not have any SOA data structures.

If upgrading an existing SOA database to a UMDB, refer to Preparing a SOA Database for UMDB Integration. After Plant Applications is installed, you must run the CreateAspect command from the command line with options to prepare the database for migration.

Create a New Database as a Placeholder

Enter a new database name as a placeholder during the Workflow installation with the intention of later pointing to an existing database. Database upgrade can be a slow process or you may want to follow a more complex strategy to merge data. Creating a new database during installation helps to not interrupt the installation process while providing options for handling database setup.

  • Use the utilities available with SQL Server to move a database from one server to another.
  • Historian data is stored in separate tables and may be in a separate database. It is useful for reporting to have the Historian database point to a Plant Applications database, because alarms are then kept in a common “alarms” table. When generating a custom report, you can report on alarms from both Historian and Plant Applications.

Aspecting

Aspecting cross-references objects residing in the Plant Applications database with objects that follow the S95 data structures used by Workflow.

Set the UseProficyClient site parameter to True, to enable aspecting. You cannot rename aspected items. Aspecting of user names uses the fully-qualified domain name (FQDN) specified for a Windows account. For more information, see the Plant Applications Help.

  • When using the Workflow client to create equipment, material, and personnel, the entities are aspected to the Plant Applications data model for access in Plant Applications. In a similar fashion, entities created in Plant Applications are aspected for use in the client.
  • Set the UseProficyClient site parameter to True to merge the Plant Applications and the SOA equipment models using the Workflow client. For more information, see Enabling the Proficy Client UI and Aspecting in the Plant Applications Help.