OPC UA Import Capability
OPC UA (OPen Connectivity Unified Architecture) was introduced into this release as a new method to connect to PlantState Suite. The goals of the OPC UA are to accomplish the following:
- Migrate from old OPC communications model (DCOM) to a cross-platform, service-oriented architecture
- Enhance data acquisition security
- Provide an information model
The OPC UA model implies no more OPC DA, AE or HDA. This is a unified data model; UA nodes can be variables, objects, methods, views and provide real time data access, events, history and methods. As OPC UA is embedded into hardware (e.g. PLC), it eliminates the need for OPC server installation and the proprietary protocol between the hardware and the OPC server.
To address backward compatibility, OPC DA servers will require a UA Wrapper to access UA client applications. To access UA servers, OPC DA clients will need a UA Proxy.
The first PAS import to take advantage of the OPC UA technology will be the Siemens T3000 data source connection.
Stale Alarms Reconciliation
Stale Alarms, Stale Alarms per Time Period & Standing Alarms analyses now calculate all alarms from beginning of recorded data to see what alarms are standing prior to the start of the date range of the parameter set and then merge those records with the standing calculations done over the date range of the parameter set. The following new snapshot imports have been introduced in this release:
- FoxIA Standing Alarms Snapshot Import
- Yokogawa CAMS Standing Alarms Snapshot Import
To further correct for any discrepancies, PSS can now accept insertion of virtual Return-To-Normal events (RTN). Virtual RTN events can be created in three ways:
Export from Missing Tags
- By a snapshot import. Any RTN event calculated from a snapshot import is marked as a virtual event in the ProcessAlarms table
- By an import where a shelving action is recorded and PSS needs to mark an alarm as no longer active. This again will show up in the ProcessAlarms table as a virtual RTN. The Experion event imports, the FoxIA AIM* imports, and the DeltaV imports are all examples of such situations where these events will be saved
- Manually created from the Alarm and Event Journal as well as the Alarm Analysis results windows. There a user can right click on an ALM event and choose to insert a RTN event for it. They will then be asked for a timestamp of the RTN and a comment
Missing Tags can be exported to Excel with the click of a button or selected in the grid and copied to the Windows clipboard by clicking Ctrl+C. In addition to print/export to Excel the user is now also able to add comments and view the point in time when the items were marked as “missing”.
Configured Field in Missing Alarms UI
Alarms that switch from Configured to Not Configured are displayed in the “Missing Alarms” window for user confirmation. Until the changes are confirmed, the alarms can be shelved. The alarms will also be marked in D&R with a red exclamation icon in the “Configured” field.
Force KPI Calculation
An option has been introduced in this release to enable KPI calculation without the requirement of another data point import after the time unit completion.
There is now a checkbox on the KPI details form to force it to calculate even if the data range is insufficient. Then those results are marked as "forced" and will be recalculated when there is enough data, like the ones that currently wait for retry. The KPI can only be forced to calculate if the KPI is actively scheduled. The KPI results are marked with an asterisk or some other indication when they are from a "forced" calculation, and that mark is removed when they are recalculated upon receiving the necessary data.
Use PI data instead of OPC DA
The ability to use PI data for checking PI violations instead of using OPC DA has been introduced in this release.
Tag.Parameters can address a variety of data servers, including OPC DA, UA, and PI. Tag.Parameters have a settable “Data Server Type” field, and address fields for DA, HDA, UA, and PI. This allows PI data to be used in inBound, Audit & Enforce, Dynamic Alarming, State logic expressions, and anywhere else that Tag.Parameters are required in the software.
PSS Data Collector to Serve Multiple PSS Servers
The PSS data collector has been enabled to serve data to multiple PSS servers.
The OPC Data Collector Status tool can be used to create a list of servers to allow for communication. Additionally the connection status for each server can be seen in this tool. Each PSS server is responsible for its own OPC connections / printer connection / TCP Printer Connections / PI connections.
Alarm & Event Journal Filtering
Alarm and Event Journal has been enhanced in the following areas:
Diagnostics Notifications per DSC
- Multiple Data Owner selection
- Custom Data Time Range Buttons
- Descriptive Column Headers
- Every single unique column
- Addition of “Search for Tag”
- Operational Area Filtering from Parameter set Filters.
A new diagnostic notification "NoCurrentEventDataImport" has been implemented for each event import.
The user is now able to send diagnostic notification e-mails if the Data Source Connection itself has “NoCurrentEventData” instead of only the Data Owner not having received events.
PV part of the TDP selection
The PV can now be part of the Tag.Parameter selection and imported automatically into PSS.
There is now a field in the Tags table that indicates what Tag.Parameter is the PV for the tag. If this field is filled in, then when a user of inBound goes to associate a PV, the existing parameter will already be listed. Additionally there are two new System-wide Settings that allow a site to choose the default acquisition intervals and recording intervals for the PV logic for inBound. Finally, there is a new import setting called "Associate PV with Tags on Import" that may exist for some point configuration imports, and if it does then the user can set the field to “True” and during the import, the PV will be associated with the tag automatically and the default intervals will be used to create the LogicBlock assigned to that inBound item already for the user. The first import to take advantage of this capability is the Honeywell File Point Configuration Import.
Imports Max Days to Query
A new configurable field has been added to the import to specify the maximum number of days to query.
There is a new import setting for any alarm and event import that gets data from a database. The name of the setting is "Max Days to Import" and the default value is 0. The setting only applies to "scheduled" imports and when a scheduled import occurs, if the value of that field is greater than zero PSS will truncate the date range of data that the import is trying to gather to only the number of days in that field. A setting of 2 means that for any scheduled import, PSS will not try to gather more than 2 days of data. If PSS needs 3 weeks of data to catch up to current time then it will get data 2 days at a time, each time the import is scheduled to run.
Lock Loop Configuration on Import
The Settling Time Specification may now be overwritten with the calculated value derived from the loop tuning settings in a Partial Import:
PSS now has a field in the control loop properties to "lock" the configuration from being updated in a future import. The field can also be set in the control loop status screen by right-clicking and selecting it. Additionally, in the ImportLib_CWDataFiles.dll version 188.8.131.52, the generic Control Wizard Configuration for OPC import now supports a column called ConfigLocked, where if it is a value of True/1/On/Yes it will set that loop to locked at the end of the import.
Stiction Analysis Diagnosis Enhancements
The loop assessment diagnoses have been modified for special cases:
- Valve (i.e. controller output) that barely moves
- Valve that stays near all the way open or closed
- High PV crossings per hour
Depending on the assessment data, some existing loop assessments with the "Oscillating due to valve stiction" diagnosis will stay the same upon reassessment; others will just drop the "stiction" part; others will add clauses like "possible valve sizing issue" or "possible noisy signal".
PSS inBound module has been enhanced to include two new columns:
- Time In Excursion – The time between the start of the excursion and the return-to-normal
- Peak Value – The minimum or maximum value during one excursion, depending on boundary direction
These columns have been added on the following user interfaces:
- Alarm & Event Journal, for excursion return-to-normal events
- Alarm & Event Analysis (Excursions per Time Period and Time in Excursion analyses).
To acquire the software please download it from the Technical Support Portal
or contact the Technical Support Team at RapidSupport@PAS.com
. You may view our Technical Updates
page to view the latest information regarding all PSS releases.