• Populate the Production Data Log for a batch recipe and create logs as a result of using batch start/end, phase start/end, and so forth. This includes the use of:
– Task Variables – History Association
– Message Log and PDL Log association
• Pass parameters from the Batch Recipe to the Schedule argument structure and into the report.
• Create reports using typical queries and views.
• Define batch archiving and aging of the online data.
These activities are designed to follow the flow of information from Batch Management into the Information Manager, out to reports and finally the safe off line storage of the Batch Production Data in an archive.
Section 2 Configuring Basic Functionality
Upon completion of this tutorial you will be able to use SoftPoint and Calculation Services to simulate a live process, configure History Services to collect process and alarm/event data from the SoftPoints, and view the data using Information
Management desktop tools. Mostly, base 800xA System functionality is used in this part of the tutorial. Any extended Information Management functionality is
identified to show the benefits of using extended methods.
To meet these objectives you will:
• Use the Information Management Configuration Assistant to ensure that you have:
– met the minimum system requirements.
– installed all required software.
– performed all required post-installation procedures.
• Use the SoftPoint and Calculation Services to build a process simulator that produces moving data points. These data points will serve as data sources for historical logs configured in History Services.
• View historical data using DataDirect.
Verifying Installation of Information Management Section 2 Configuring Basic Functionality
The system architecture for this tutorial is illustrated in Figure 1.
Verifying Installation of Information Management
Use the Information Management Configuration Assistant to ensure you have completed all procedures required to install and set up an Information Management server (if used). If you find that any of these requirements have not been met, then return to the installation and post installation activities for an Information
Management server.
To launch the assistant, from the Windows task bar, choose:
ABB Start Menu > ABB Industrial IT 800xA > Information Mgmt > IM Figure 1. System Architecture for this Tutorial
Section 2 Configuring Basic Functionality Log-In User Authority
Log-In User Authority
This tutorial requires creating object types in the Aspect Directory. To do this, log in as a user belonging to the IndustrialITAdmin user group.
Building a Process Simulation
The purpose of this exercise is to provide moving data points to serve as the data sources for historical data collection.
SoftPoint Services is used to configure and use internal process variables not Figure 2. Configuration Assistant
Use the SAME user that installed the Information Management software. New users are required to add DataDirect and Bulk Import add-ins to Microsoft Excel.
These procedures are covered in the operation and configuration books for Information Management.
Configuring SoftPoints Section 2 Configuring Basic Functionality
may be accessed by other 800xA system applications as if they were actual process points.
Each SoftPoint object will have:
• An integer signal driven by a calculation that counts from 0 to 100 and back to 0.
• Historical data for each signal collected by a property log configured in History Services.
• A second integer signal used to support the calculation logic.
• High and low limits will be configured for the signals so that alarms will be generated. These alarms will be collected by the system message services and may be viewed via alarm and event list aspects for the SoftPoint signal objects.
As an option, a message log may be configured in History Services for extended online storage and offline archival of alarm/event data. This is described in another lesson in Section 5, Configuring Additional Functionality.
Configuring SoftPoints
SoftPoint objects are instantiated from SoftPoint object types configured in the Object Type Structure. The object types are templates from which the actual SoftPoint objects are instantiated.
Set-up Requirements for SoftPoints
SoftPoints are instantiated in the Control Structure under a SoftPoint Generic Control Network object. This object establishes the connection with a specific SoftPoint server. Configuration of the SoftPoint Generic Control Network and related objects is completed as a post installation procedure and should already be done (refer System800xA 6.0 Post Installation (2PAA111693*)). This will
automatically configure the following:
• SoftPoint service group object and service provider object(s).
• Virtual control network by which other system applications (History, desktop
Section 2 Configuring Basic Functionality Set-up Requirements for SoftPoints
• Source Definition aspect for each network. This is used to deploy the SoftPoints on their respective nodes.
• Integrates the SoftPoint alarm and event messages into the 800xA system message service.
Before beginning this tutorial, confirm that this configuration has been completed. If this setup is complete, skip to Adding a New SoftPoint Object Type on page 27.
Open the Workplace
Use the Plant Explorer workplace to access the Structure Selector.
1. From the Windows task bar choose:
ABB Start Menu > ABB Industrial IT 800xA > System > Workplace.
2. Select Plant Explorer Workplace, and click Open. The initial view of the Plant Explorer Workplace shows the 800xA system objects and aspects within their structural organization.
3. Use the Structure drop-down list in the upper left part of the Plant Explorer (Figure 3), to select the Control Structure.
Configuring SoftPoint Services
1. In the Control Structure, select the Root, Domain and choose New Object from the context menu. This displays the New Object dialog.
2. Expand the Object Types category, and select SoftPoint Generic Control Network (under SoftPoint Basic Object Types). Enter a name to identify the Figure 3. Plant Explorer Initial View - Selecting Control Structure
Set-up Requirements for SoftPoints Section 2 Configuring Basic Functionality
3. Select the Generic Control Network Configuration aspect of the new object and click on the Configure tab as shown in Figure 4.
4. Click the Server Settings Configure button (Figure 4).
Figure 4. Generic Control Network Configuration Aspect
Section 2 Configuring Basic Functionality Set-up Requirements for SoftPoints
6. Click OK at the configuration completed message. The configuration of the server settings for a non-redundant SoftPoint network is complete (Figure 6).
Figure 5. Choose Connectivity Server Node (Primary)
Figure 6. Generic Control Network Configuration (Primary Server)
Set-up Requirements for SoftPoints Section 2 Configuring Basic Functionality
8. Check the box Node is redundant provider and then select the redundant Connectivity Server Node where SoftPoints is installed (Figure 7) and click OK.
9. Click OK at the configuration completed message. The configuration of the server settings for a redundant SoftPoint network is complete.
Integrating SoftPoint Alarms and System Messages
In order for the system message service to collect alarms and events from the SoftPoints on this network, the ABB 800xA Soft Alarms OPC Server must be added to an Event Collector, Service.
This is done automatically when the Alarm and Event Settings part of the Generic Control Network Configuration aspect is configured:
1. Click the Alarm and Event Settings Configure button (Figure 6).
2. Add providers in the same way was done for the Server Settings.
Figure 7. Choose Connectivity Server Node (Redundant)
Section 2 Configuring Basic Functionality Adding a New SoftPoint Object Type
Adding a New SoftPoint Object Type
Create an object type template. This template will be used to instantiate SoftPoint objects into the Control Structure under the SoftPoint Generic Control Network object.
1. Open the Object Type Structure using the Structure selector.
2. Select SoftPoint Object Types and choose New Object from the context menu as shown in Figure 8.
Figure 8. Creating a New SoftPoint Object Type
Configuring the SoftPoint Object Type Section 2 Configuring Basic Functionality
3. In the New Object dialog (Figure 9) select SoftPoint Process Object Type, assign a name to the new object (Counter in this example), then click Create.
Configuring the SoftPoint Object Type
Add an integer signal type via the Process Object Configuration aspect (Figure 10):
1. Select the new SoftPoint object type in the Object browser (left hand pane).
2. Then click on the Process Object Configuration aspect in the object’s aspect list (right hand pane).
Figure 9. New Object Dialog, Counter
Section 2 Configuring Basic Functionality Adding a Signal
Adding a Signal
The Add Signal buttons are located in the upper left part of the SoftPoint Process Object Configuration aspect as shown in Figure 11.
To add the integer signal type, 1. Click the Integer signal button.
Figure 10. Configuring the New Object Type
Figure 11. Add Signal Buttons
Configuring Signal Properties Section 2 Configuring Basic Functionality
3. Click OK.
Configuring Signal Properties
Signal properties that may be configured include range (high/low limits), engineering units label, and whether or not the signal should be controllable.
To configure signal properties:
1. With the new signal type selected, click the Signal Configuration aspect (Figure 13).
2. The signal must be made controllable to let the calculation drive the signal value. To make a signal controllable, click the Controllable tab, and then click the Is Controllable check box (Figure 14), and then click Apply.
Figure 12. New Signal Type Dialog, Count
Figure 13. Displaying the SoftPoint Signal Configuration Aspect
Section 2 Configuring Basic Functionality Configuring Alarm Trip Points
For this tutorial, DO NOT check the Log operator actions check box. This would cause every signal value change to be logged as an event (calculation updates to SoftPoints are treated as operator actions).
3. To set limits for signal, click the Range tab, key in the required limits, and click Apply. In the example shown in Figure 15, the Low limit is 0 and the High limit is 100.
Configuring Alarm Trip Points
SoftPoint limiters are trip points in the signal’s overall range that, when crossed, Figure 14. Making the Signal Controllable
Figure 15. Setting the High and Low Limits
Configuring Alarm Trip Points Section 2 Configuring Basic Functionality
services. Up to eight limiters can be specified for a signal. To do this (reference Figure 16):
1. With the signal type selected in the left pane, select the Alarm Event Configuration aspect.
2. On the Limiter tab, select 1 Limiter1 and enable the Use Limiter option. This activates the limiter configuration fields.
Reference Figure 17 for Step 3 through Step 6.
Figure 16. SoftPoint Limiters Configuration Aspect
Section 2 Configuring Basic Functionality Configuring Alarm Trip Points
3. The name defaults to Limiternumber. Rename the limiter to make it more easily identifiable, for example: CountHigh.
4. Specify the Type to indicate whether the limiter will trigger an event when the signal rises above a maximum value (Max), or drops below a minimum value (Min).
5. Enter a Limit. This is the threshold that the signal must cross to trip an alarm (drop below if type is Min, or exceed if type is Max).
The Hysteresis may be set to filter spurious alarms caused by signals that fluctuate around the limit. This is optional and is not covered here.
6. Click Apply.
7. Repeat Step 2 through Step 6 to configure up to four limiters. An example of a completed limiter list is shown in Figure 18.
Summary:
CountHigh, Max, 95 CountMidHigh, Max, 90 CountMidLow, Min, 10 Figure 17. Adding a Limiter
Configuring Alarm Trip Points Section 2 Configuring Basic Functionality
The limiter can be deactivated by selecting the limiter and unchecking the Use limiter option.
8. To enable the alarms for this signal:
a. Check the Is an event option on the Event tab.
b. Select a limiter signal and check Is an alarm (Figure 19) on the Alarm tab. Repeat this for each limiter. Then click Apply.
Figure 18. Example, Completed Limiter List
Section 2 Configuring Basic Functionality Adding a Signal to Support the Calculation Logic
Adding a Signal to Support the Calculation Logic
The calculation logic that drives the Count signal value requires an integer variable whose value is set to 1 or -1, depending on whether the signal value is being increased or decreased. This is implemented by adding an integer signal to the SoftPoint object, and then writing the integer value (1 or -1) from the calculation.
1. Select the Counter, SoftPoint Process Object Type as shown in Figure 10.
2. Select the Process Object Configuration aspect.
3. Use the Add Integer Signal button (Figure 11).
Figure 19. Enabling Alarms for this Signal
Applying the Calculation Section 2 Configuring Basic Functionality
4. Give this signal the name upDown as shown in Figure 20.
5. Configure signal properties to make the signal controllable as demonstrated in Figure 14 and Figure 15.
Applying the Calculation
Add a Calculation aspect to the SoftPoint object type to drive the SoftPoint’s Count signal value and thus simulate a live process. By adding the aspect to the object type, the Calculation may be applied to each object instance that is created from the object type. To begin (reference Figure 21):
1. Select the Counter object type and choose New Aspect from the context menu.
2. In the New Aspect dialog select the Calculation aspect.
3. Enter a meaningful name, for example: CountUpDown, then click Create.
Figure 20. New Signal Type Dialog, UpDown
Section 2 Configuring Basic Functionality Applying the Calculation
4. Click on the Calculation aspect to display its configuration view (Figure 22).
Figure 21. Adding a Calculation Aspect
Figure 22. Displaying the Calculation Aspect View
Applying the Calculation Section 2 Configuring Basic Functionality
signals are mapped to the Value property), Figure 23. Both are declared as Output variables so the calculation will update the signal values each time the calculation executes.
a. Use the Insert Line button on the tool bar to add a line in the variable grid (Figure 24). Two variables are required: OutputVar and upDown.
Complete the mapping as shown in Figure 23 and as described below.
b. Declare an output Variable named OutputVar and upDown as shown in Figure 23. Use the Object and Property columns to specify the signal’s Value property as a data point to be updated by the calculation.
c. Specify the Object as a relative object reference (./). Relative referencing allows the same calculation to be used for multiple object instances without having to change object references. Check case sensitivity to ensure the correct object is referenced.
d. Select the Property from the pull-down list. The contents of this list is based on the object specified.
e. Select the Direction as Output from the pull-down list. Output values are Figure 23. Mapping Variables
Figure 24. Insert Line Button
Section 2 Configuring Basic Functionality Applying the Calculation
f. Set the State to Online for both signals.
g. Enter an initial Offline Value of 1 for OutputVar and -1 for upDown.
6. Enter the calculation script as shown in Figure 25. This script ramps the Count value up to 100 and then back to 0.
7. Click the Editor/Scheduler toggle button on the toolbar to change the view to Scheduler. This is used to specify either a cyclic schedule, or a time-based schedule. For this tutorial, specify a cyclic schedule (Figure 26).
8. Check the Cycle check box. In the corresponding fields specify the interval unit (hours, minutes, seconds), and the number of intervals. The example in Figure 27 shows a 2-second cycle. This will cause the calculation to execute, and the Count signal value to change, every two seconds.
Figure 25. Calculation Script
Figure 26. Change to Scheduler Button
Applying the Calculation Section 2 Configuring Basic Functionality
9. Save the calculation configuration by clicking the Save button on the tool bar (Figure 28).
Check whether or not the calculation is working by manually executing the
calculation off line. To do this, click the test off line button a few times (Figure 29).
If the calculation is working. The Offline Value for the OutputVar variable will be incremented or decremented by one each time the button is clicked.
Figure 27. Cyclic Schedule
Figure 28. Save Button
The Calculation Editor View does not prompt the user when exiting and changes are pending. Use Save button before leaving the display.
Section 2 Configuring Basic Functionality Specify that the Calculation be Copied to Instantiated
Specify that the Calculation be Copied to Instantiated SoftPoints
Even though the calculation aspect was added to an object type, the calculation will not be copied into the instantiated objects created from the object type unless this functionality is specified. To do this (reference Figure 30):
1. Go to the Counter Type Definition aspect for the SoftPoint object type.
2. Click the Aspect Control tab.
3. Select the Calculation category, in this case: CountUpDown.
4. Check the box labeled Copy to all instances.
5. Click Apply.
Figure 29. Test Off Line
Instantiating and Deploying SoftPoints Section 2 Configuring Basic Functionality
Instantiating and Deploying SoftPoints
SoftPoint objects are instantiated in the Control Structure. The objects can be created one-object-at-a-time or a bulk instantiation of a specified number of objects of the same object type can be performed. This section demonstrates the bulk instantiation method. To do this (reference Figure 31):
Figure 30. Type Definition Aspect
The calculations must be enabled once they have been instantiated in the Control Structure. How to instantiate the SoftPoints and then enable the calculations is covered in the following sections.
Section 2 Configuring Basic Functionality Instantiating and Deploying SoftPoints
1. Go to the Control Structure using the Structure selector.
2. Select the SoftPoint Generic Control Network object in the Control Structure, and click the Generic Control Network Configuration aspect.
3. Click the Create New Object button in the top left corner of this aspect view.
This displays the Create New Object dialog (Figure 32).
4. Select the Counter SoftPoint object type from which to instantiate the new SoftPoint objects as shown in Figure 32.
Figure 31. Selecting the SoftPoint Process Objects Group
Instantiating and Deploying SoftPoints Section 2 Configuring Basic Functionality
5. Create 10 new objects with a starting number of 1 and enter the object name, in this case counter.
6. Click OK. The result is shown in Figure 33. A unique name is created for each new object consisting of the basic name plus a sequential numeric suffix starting with the specified Starting number.
Figure 32. Create New Object Dialog
Section 2 Configuring Basic Functionality Instantiating and Deploying SoftPoints
7. After creating new objects in the Control Structure, rename all the Count and upDown SoftPoint Signal types with the parent object name as the prefix. For example, rename Count and upDown SoftPoint Signal type under Counter1 SoftPoint object type, as Counter1 Count and Counter1 upDown
respectively. Repeat the same for all the Count and upDown SoftPoint Signal types under Counter2 to Counter10 SoftPoint objects instantiated. Refer to Figure 34.
Figure 33. Bulk Instantiation Result
Instantiating and Deploying SoftPoints Section 2 Configuring Basic Functionality
Figure 34. Renaming Count and upDown SoftPoint Signal types
Section 2 Configuring Basic Functionality Deploying a SoftPoint Configuration
Deploying a SoftPoint Configuration
Whenever new SoftPoint objects are created, or changes to existing SoftPoint objects made, the new configuration will not go into effect until the changes are deployed. While SoftPoint configurations are being deployed, SoftPoint processing is suspended, current values and new inputs are held. This process is generally completed within five minutes, even for large configurations. To do this (reference Figure 35):
1. In the Control Structure, select the SoftPoint Generic Control Network object for the node where the SoftPoints will be deployed.
2. Select the Deploy aspect.
3. Click the Deploy button to start the deploy process. Completion of the deploy process is indicated by the Deploy ended message, Figure 36.
Figure 35. Deploying the SoftPoint Configuration
Enabling the Calculations Section 2 Configuring Basic Functionality
Enabling the Calculations
The calculations will not execute until they have been assigned to a Calculations service provider and enabled. Use the Calculation Status Viewer.
To do this (reference Figure 37):
1. Open the Service Structure using the Structure selector.
2. Select the Calculation Server, Service.
3. Select the Calculation Status Viewer aspect.
4. Select the calculations in the viewer and choose Service from the context menu.
Figure 36. Deploy Ended Indication