About the Wonderware Data Historian activity
Manufacturers often collect data from monitored machines/equipment during production and then store the data in a Wonderware Historian SQL database. The collected data identifies the machine and date and time, but doesn't include the unit UID.
...
Note
Since many measurements are being recorded and the volume is huge, only sampled results are collected using the FactoryLogix Wonderware Data Historian activity.
Configure Wonderware database connection details
...
Before you can add the Wonderware Data Historian activity to a process definition in FactoryLogix Office, you need to configure the connection details for the Wonderware database. This configuration includes four settings found in the System Configuration > Settings area of FactoryLogix Office, under the Option Type: Wonderware Historian Activity in the Process Planning category of the Global Options tab.
...
Option | Description |
|---|---|
Server Address | The IP address of the Wonderware server |
Database Name | The name of the Wonderware database |
User Name | The user name associated with the Wonderware database |
Password | The password to log into the Wonderware database |
Add the Wonderware activity to a process definition in FactoryLogix Office
If you didn't configure the Wonderware database connection details in FactoryLogix Office Settings (see the previous topic), you will see this message:
...
Author the instructions for the shop-floor operator related to this activity.
Indicate whether the activity is required or optional.
Identify zero or more validation parameter tags to be validated before a unit can be processed (see Point A in the following illustration).
Identify zero or more trending measurement tags whose values are recorded against a unit while the unit is being worked on. To reduce the volume of data recorded in FactoryLogix, the process designer will specify the number of measurements to be recorded (between Point A and Point B in the following illustration).
Identify zero or more final value measurement tags whose values are against a unit in FactoryLogix.
What happens in Production?
After you configure the Wonderware Data Historian activity for a process definition in FactoryLogix Office, here's what happens in Production:
...
When the activity is recorded as Completed, the activity queries the Wonderware Data Historian for the data to record the trending measurements. Further, if any final value measurements were defined, the activity queries the Wonderware Data Historian for the data to record those measurements.
How does the query for trending measurements work?
The query to retrieve data for trending measurements returns all values recorded to the specified tags in the Wonderware Data Historian from the time the validation parameters were validated through the time when the operator marked the activity as Completed.
...
The Type is the parameter name.
The Value is the value returned by the query for the parameter.
The Activity is Wonderware Data Historian.
The Measurement Date Time is the date/time returned by the query.
Configure the Wonderware activity in FactoryLogix Office
When configuring the Wonderware Data Historian activity in FactoryLogix Office, process designers need to define the following on the Activity Details tab of the Settings dialog:
...
Note
All tag values must be of type Float.
Validation Parameters
You can configure zero or more Validation Parameters on the Activity Details tab of the Settings dialog:
Wonderware Tag Name - The tag name recorded in the Wonderware Data Historian database
Minimum Value - The minimum validation value
Maximum Value - The maximum validation value
Trending Measurements
The activity configuration allows you to define zero or more of these Trending Measurements on the Activity Details tab of the Settings dialog:
Wonderware Tag Name - The tag name recorded in the Wonderware Data Historian database
FactoryLogix Measurement Name - The tag name to be recorded in FactoryLogix
Sub Interval Count - An integer value with a minimum value of 1
The processing uses the reporting window (Point A to Point B in the following illustration) and returns a measurement for each sub-interval plus one.
Example: If the reporting window was from 1:00 PM to 2:00 PM and 4 measurement sub-intervals were requested, then 5 measurements will be recorded (the tag values at 1:00 PM, 1:15 PM, 1:30 PM, 1:45 PM and 2:00 PM).
Final Value Measurements
The activity configuration allows you to define zero or more of these Final Value Measurements on the Activity Details tab of the Settings dialog:
Wonderware Tag Name - The tag name recorded in the Wonderware Data Historian database
FactoryLogix Measurement Name - The tag name to be recorded in FactoryLogix
Querying the Wonderware Data Historian
Validation parameters
This query returns the most recently recorded value for each of the identified tags.
...
|
|---|
Trending measurements
This query returns all values recorded for the identified tag within the specified time window.
...
* These are the column names displayed on the Parametric tab in the Trace window in Production.
Final value measurements
This query returns the last recorded value within the specified time window for each of the identified measurements recorded.
...