The following structures are called Primary Structures, because it is assumed that most operators and application engineers will perform the majority of their work within these structures.
• Asset Structure.
• Control Structure.
• Functional Structure.
• Location Structure.
Use the following guidelines when creating 800xA System users in the DMS system:
• Users must be both Windows and 800xA System users.
• Do not prefix the DMS user name with the Windows domain name or the computer name.
Assigning access rights (permissions) to users, defining division roles and groups, and joining users to groups must be done after each division creation.
• Object Type Structure.
• User Structure.
• Workplace Structure.
These structures are built by placing objects into the structures according to their hierarchical relations.
The object is a key concept in the Plant Explorer Workplace. The Plant Explorer Workplace is where the most basic elements of the system are created. These are the simple objects. Simple objects can be placed directly into a structure, but they can also be parts of other objects called composite objects. Simple objects can be pipes or valves or other basic elements used to build a more complex unit.
Composite objects, which can contain several other simple objects, are called parent objects. They are composed of a number of subordinate objects, called children or descendents. When a new object is created, the parent object can be selected, to which the new object will be a child.
Building the various structures is beyond the scope of this instruction. Refer to the appropriate Industrial IT 800xA documentation for detailed information and definitions of the various structures.
Managing Data Source Connections
Asset Monitoring Engines manage connections to the data sources required by the Asset Monitors. The data sources are specified during Asset Monitor configuration under the Input Records Tab.
Each data source is defined by one Asset Monitor Data Source aspect. The Asset Monitor Data Source identifies the data server type and its connection parameters.
The defined data server is used by the Asset Monitors to access the OPC item values that are needed to assess the current asset conditions.
The Asset Optimization Server system extension provides an Asset Optimization Object that is placed in the root of the Control Structure.
After Asset Optimization installation, the Asset Optimization Object automatically contains one Afw OPC-DA Asset Monitor Data Source.
When the various structures are set up as desired, it may become necessary to move some Asset Optimization aspects to other areas in the structures by using the drag-and-drop method. Do not attempt to move any Asset Optimization aspects when the Asset Monitoring Server is running, as this will result in the following loss of configuration:
• Asset Monitoring Server: Do not move. All aspects referencing moved Asset Monitoring Server point to nothing.
• Asset Monitor Data Source: Do not move. All aspects referencing moved Asset Monitor Data Source point to invalid Global Unique Identifiers (GUIDs).
• Asset Reporter and Asset Viewer: No problems.
• CMMS Views: Must also move the associated Maximo Equipment ID.
To avoid these problems, copy and paste the aspects to the desired location, and then delete them from the original location.
When an object containing Asset Monitors is moved using the drag-and-drop method, reload each Asset Monitor in the object to make them aware of their new location.
Renaming an Asset Monitor Data Source aspect to the same name as an existing Asset Monitor Data Source aspect is not a valid configuration.
The Afw OPC-DA Asset Monitor Data Source is contained in the Asset Optimization Object located in the root of the Control Structure. This Asset Monitoring Engine Data Source is preconfigured, during Asset Optimization installation, to be the default data source for Asset Monitors. This data source points to the 800xA System OPC Server located in the same node where the Asset
Monitoring Engine is running (OPC Sever Node = localhost).
1. Use the Structure Selector to select the Control Structure.
2. Navigate to:
Root, Domain > Asset Optimization, Asset Optimization 3. Select Afw OPC-DA Asset Monitor Data Source in the Aspect List
Area to produce the Config view of the Afw OPC-DA Asset Monitor Data Source in the Preview Area as shown in Figure 39.
The fields in the Asset Monitor Data Source are defined as follows:
– Server Type: Defines the application program interface (API) used for connectivity (e.g. OPC DA).
– Description: Data source description.
This procedure provides access to the Config view of the Afw OPC-DA Asset Monitor Data Source. ABB recommends using the default values.
TC04667C
Figure 39. Afw OPC-DA Asset Monitor Data Source Setup
– Enable Write Access: Global switch to control write permission. Makes it possible to write values from an Asset Monitor.
– Default Data Source: Leave this check box checked to mark the selected data source as the default during Asset Monitor configuration.
– Connection Parameters: Server type specific information required to connect to the data source.
– Browse OPC servers (OPC Specific Connectivity): If the logon user has OPC browsing privileges on the selected OPC server node, clicking Browse OPC servers lists available OPC servers in the specified node.
The connection parameters for an OPC DA server are:
– OPC Server Node: The hostname or address of the node hosting the OPC server.
– OPC Server Name: The ProgID of the OPC server to connect to.
Whenever possible the OPC Server Name should be set to
ABB.AfwOpcDaSurrogate since this OPC Server provides access to any other OPC servers integrated in the 800xA System.
– OPC Group Update Rate (ms): Used by the OPC server for
performance/scalability tuning purposes. Refer to the specific OPC server documentation for more information.
If the OPC Server Name is ABB.AfwOpcDaSurrogate, then the OPC Server Node must be set to localhost.
If a different OPC Group Update Rate is needed (i.e., for
ABB.AfwOpcDaSurrogate) do not modify the default settings. Create a new Asset Monitor Data Source instead. This will avoid imposing the new settings on all Asset Monitors pointing to the default data source.
4. If changes have been made, click Apply to save the entered data.
OPC connectivity to an OPC server located on a different node than the Asset Monitoring Server Engine uses DCOM protocol. Table 10 is a brief
troubleshooting guide for typical OPC-DCOM connectivity problems. Refer to the specific OPC server documentation for additional troubleshooting.
Managing the Connection Between the 800xA System and the DMS System A DMS Division is a high level entity used to group related devices. A DMS Division can be as small as a single device or as large as the entire enterprise. Asset Optimization DMS Calibration Integration allows for the mapping of one or more DMS Divisions into 800xA Object Structures.
Typically one DMS Division is mapped to an 800xA System object representing the Control Network in the Control Structure (requires AC800M Connect). If the HART Device Integration system extension is installed, the Control Network object will contain the DMS Division aspect.
When the DMS Division aspect is created in the 800xA System, it connects to a corresponding DMS Division in the DMS system (if it is not already connected to another 800xA System object) or creates and connects to one if the corresponding
Table 10. OPC-DCOM Connectivity Troubleshooting Guide
Problem Solution
Incorrect network protocol Use dcomcnfg.exe and make sure that TCP/IP is specified in the Default Protocol tab of both nodes. Ideally TCP/IP should be the first in the list unless other applications have different needs.
Incorrect Launch/Access user credential
Use dcomcnfg.exe to add the identity used by the 800xA Service Account in the Launch/Access lists (Security tab) for the OPC server.
Some OPC servers need to run under a specific user account (e.g. interactive user or a specific NT account)
Use dcomcnfg.exe to modify the OPC server application identity settings (Identity tab) and select the appropriate user.
DMS Division is not already there. By default, the DMS Division name is the same as the 800xA System object name.
Creating a DMS Division differs depending on which system extensions are installed:
• Fieldbus Builder P/H and HART Device Integration system extensions not installed: DMS Division aspect must be manually created.
• Fieldbus Builder P/H system extension installed, HART Device Integration system extension not installed: Add Control Network object to root of Control Structure and manually create the DMS Division aspect on the Control Network object.
• Fieldbus P/H and HART Device Integration system extensions installed:
Add Control Network object to root of Control Structure and the DMS Division aspect is automatically created on the Control Network Object.
After creating the DMS Division aspect, set it up as follows:
1. Use the Structure Selector to select the Control Structure.
2. Select DMS Division in the Aspect List Area.
All 800xA System users must be configured as a DMS user to access DMS information. The system engineer configuring DMS in the 800xA System must also have Division Creation privileges in the DMS system. Refer to Meriam Process Technologies Device Management System User’s Guide for detailed information.
The 800xA Service User must be set up as a user in the DMS system for each DMS Division. Once the DMS Division has been created in the DMS system, the creating user will be added as an administrator for that DMS Division. All other 800xA System users must be added to the DMS Division manually. Refer to Meriam Process Technologies Device Management System User’s Guide for detailed information.
3. Click on the View Selector and select Config to open the Config view in the Preview Area to produce the view shown in Figure 40.
4. The fields in the DMS Division are defined as follows:
– Division Root Structure: Defaults to the Control Network. This represents the structure in which the DMS Division maps all device descendants to the corresponding DMS devices. Each device in the 800xA System that belongs to the DMS Division is represented by a DMS aspect in the child node in this structure. This value represent the hierarchy that is mapped to the DMS system. All objects under the current object in this structure will be part of this DMS Division.
– DMS Server Location: Points to the DMS Server node. The DMS Client installation prompts for this value.
TC05355A
Figure 40. DMS Division Setup
Do not set the DMS Server Location to http://localhost/ on a multinode system. It must be set to point the DMS Server node. This value is set during DMS Client installation and should not be set here.
– DMS Division Name: Defaults to the 800xA System object name on which the DMS Division was created. This can be changed to map to an object named differently in the DMS system.
5. A Service Account must be added as a valid user for the DMS Division. Select:
Division > Roles > Create New Role as shown in Figure 41.
TC08110A
Figure 41. Adding a Service Account for the DMS Division
6. Configure the role as shown in Figure 42.
7. A Service Group must be added. Select:
Division > Groups > Create New Group as shown in Figure 43.
TC08111A
Figure 42. Configuring the DMS Role
8. Add 800xA Service account to this new 800xAServiceGroup by going to the User Membership tab.
9. Use the Role Association tab to associate the 800xAServiceGroup with the new 800xAServiceRole, as shown in Figure 44.
Refer to DMS Calibration Integration on page 145 for configuration procedures.
TC08112A
Figure 43. Adding a Service Group for the DMS Division
TC08114A
Figure 44. Associating the 800xAServiceGroup with the 800xAServiceRole