Download - Proficy Historian Creating KPIs

7/26/2019 Proficy Historian Creating KPIs

1/14

Document authored by The Industrial interface Company NZ Ltd Page | 1

PPrrooffiiccyyHHiissttoorriiaann--CCrreeaattiinnggPPrroocceessssKKPPIIss

Key Performance Indicators(KPIs) are assorted variables that organisations use to assess, analyse andtrack manufacturing/production processes. KPIs created within Proficy Historian use standard Tag attributes

and therefore can be viewed within any Historian client. KPIs can be used to determine and monitorVolumes, Rates, Reject Ratios, create Soft Sensors, Scrap/Waste, Energy Monitoring, Downtime, OEE,Emissions and much more.

KPI development using Proficy HistorianKPI development is generally completed on the central Proficy Historian server using the CalculationCollector. The Calculation Collector allows users to perform data calculations on values already in the dataarchiver, or via 3rdparty data-source, performs the calculation, and then stores the resulting values into newarchive Tag/s. Data is accessed like any other Historian tag.

KPIs can be developed for viewing and reporting via preconfigured displays and reports, or if an S95 Tag

naming standard (or structured naming) has been deployed within Historian Tags. Then formulas can bedeveloped enabling drag and drop options within client displays in addition to standard reporting options.

The Calculation Collector has additional attributes that include

Calculation Recovery: If all data within the calculation is from historical sources (Historian, SQL,etc) should an error occur, network failure, or a change in calculation Tag. Users can run therecovery trigger to recalculate the KPI results.

Collection can be polled, or based on a trigger Tag change of state, or value.

Enumerated values can still be applied to calculation results making meaning out of numberedvalues and error codes.

Historian Tag Naming ConventionTo provide a constant user experience within the product, choose a simple naming convention for all KPIs.This should be followed for any KPIs visible to the user. This should be something that the end-customerusers are familiar with.

It is good practice to make the DisplayName and the Description unique to identify the KPI fromthe UI list. For example, if there are two pumps each with Inlet Flow, Make the DisplayNames P1Inlet Flow and P2 Inlet Flow, not just Inlet Flow. The same applies to the Description.

When naming properties within the Proficy Client, try to make the properties unique within the firstfew characters. It is more efficient for the system to retrieve results when the first few characters areunique. For example, if you have two properties, it is more efficient to name them MinFlow andMaxFlow, than to name them FlowMin and FlowMax.

KPI Names:Use short but descriptive names for KPI names within the product. These should be short butmeaningful to a user familiar with the equipment. Some good examples include: 196-GT-101 OUTSPEED, K21_LT_02.PV.

KPI Descriptions:Can be longer and more descriptive than the KPI names. These can be used by users thatare less familiar with the equipment. Some examples: Line 101 Gas Turbine Output Shaft Speed, Pump21 Tank Level Backup Sensor Value.

Historian Sampling Modes and Calculation Modes (IMPORTANT)Historian includes predefined Sampling and Calculation modes to assist with developing simple and

advanced KPIs. These should be understood and used as they will substantially reduce development times. Sampling Modes: Current Value, Raw data options, Interpolated values, trend and Calculated

Calculation Modes: Count, State Count, State Time, Min, Max, Total, Average and Raw data


2/14


KPI Visual Managementis the process of displaying critical information such as KPIs that relatespecifically to production output, efficiency and quality to staff ensuring they have a better understanding oftheir process and production levels.

As Proficy Historian is an open-layered application data can be extracted by many different types of systemsincluding the Proficy Suite (Proficy iFIX, Portal, Proficy Historian Analysis (PHA), Vision, MES etc), ExcelAdd-IN, OLE (Microsoft SSRS, Crystal Reports, ERP systems, etc). By developing the KPI at the Historian

level all clients have access to the correct value The same version of the truth.

Example of a Downtime / OEE web part.

Underlined values are hyper links to more detailed information

Creating different types of KPIs

Creating Simple Run-time KPIssuch as Volume, Rate, Reject Ratio, Scrap, etc

A meter value against a time value

A percentage of a Tag in a particular state

The calculation requires a base Tag within Historian for each Asset/Meter. Sampling mode would beCalculated and the Calculation Mode would be Total. Volume =Meter Flow Rate * Time Segment

Creating Simple Soft Sensorsuch as Differential Pressure Switches (DPS) to identify filter failure. TheKPI is the difference between the Filter Inlet PSI and the Filter Discharge PSI.

The calculation requires both Tags to be in Historian for each Filter/Asset/Meter. For each Tag Samplingmode would be Current Value.DPS result = Filter Inlet PSI less Filter Discharge PSI

Creating a KPI against Expectations requires a predefined value that a current value to calculate against to

highlight the processes current performance. The target value may be stored in a 3rd

party system (SQL, ERP,LMS, etc). This KPI can be written to get the external data as part of the calculation, or often it is easier tocopy the value from the external system to an Historian Tag.

Example: Asset Runtime by 8 hour Shift (KPI: Operating Period)Fixed Value Variable (Maintenance being the 3rdparty variable) Fixed/Variable ValueTotal Possible Run-Time less Scheduled Maintenance Downtime less Scheduled Breaks Downtime480 minutes 0 minutes (maintenance) 30 15 15 minutes (Breaks) = 420 minutes


3/14


Historian Calculation Collector KPI development via the Administrator

1. Create a new Tag within Historian using the Tags tab then Add Tag Manually tab.

2. Add Name, Description, Data Store and set the Collector.

3. Collector will be ServerName_Calculation

4. Set the collection attributes. Either polled or via a trigger Tag. Use the Enumerated Set Name toconfigure an enumerated value. Finally use the Update button to save changes.

5. The new Tags configuration tabs

6. Once saved (Update) select the Tags Calculation tab and add the calculation using set Tags, or aTag formula (*Pu*). Users can type directly, or use the wizard included.

The calculation window is blank when firstopened, or will have Result=Null displayed.

Click Window to expand the calculation area


4/14


Example 1 Creating a Soft SensorCalculations for a Filter Differential PSI, or the difference between Inlet PSI and Discharge PSI

Create a new tag(as per previous page) Filter1_Differential_PSI Manually created

Set collector Servername_Calculation There could be multiple installed

Set collection Polled at 5s (timeout 1 hour) Or trigger from another tag

Set compression Archive compression If 0 only save if value changes

Calculation tab Complete calculation Test after developed

Calculation Tab:

1. The first rule of calculations is that you need aResult=so if required type this in the window

2.

Next add the first tag (Filter1_Inlet PSI) so click on the wizard button to the right.

a.

Type = Insert a value correct leave it as it isb. Function = Current value correct leave it as it isc. Browse for Tag (use filter) when selected it appears in Input Tag

3. The calculation now looks like

4. As we are going to subtract the discharge from the inlet value, type in a -sign within the calculation.Click the Wizard button and browse for, then select the second Tag again using the current value;(Filter1_Discharge_PSI).

5. The end formula should look like this.Click Test Calculation to check the syntax.

6. To save click the Update button


5/14


Historian Simplifies KPI development with Sampling and Calculation Modes

Example 2 Flow Meter Volume for 24 hrs: As a flow meter is not always constant over a time period eachsample collected needs to be captured and added together to create a volume for a particular time period.

Historian includes the required Calculation Modes to automatically perform this task for you.

The steps are similar to above

Create the KPI Tag and assign collection attributes.

Open the Calculation window (Results=) and select the Wizard

When selecting the Tag choose different options to the previous example of Type = Current Value

Select Function: Insert a Calculation

Function: Non-Filtered Calculation

Input tag: Searched for a Flow Tag

Calculation: Total (Not RAW Total)

Start Time: Default Start Time

End Time: Default End Time

The calculation would look like

Test calculation and Update to save changes

(Note: When using the calculation tab if you wish to expand the view click on the Window button)

TOTAL retrieves the time-weighted

total of raw and interpolated valuesfor each calculation interval. Thecollected value must be a rate per 24hours. This calculation modedetermines a count from thecollected rate.


6/14


Example 3 Flow Meter Volume whilst State Tag = value (x)For this example we want to monitor the volume whilst another Tag is in a specific state, for example whenthe process is in a: Divert State, Material through a valve, or pump volumes, Recipe analysis, raw materiallevels and much more.

Tag 1(Input Tag) is the same as previous example however we choose Function = Filtered Calculation aswe want to run our calculation against another Tag, State Tag.

Tag 2 (Filter Tag) we search for and select our device/process State Tag.

We want to include Time after the state change and when the filter Tag equals the Divert statewhich in our case is 5.

How many times did the Tag enter that State?For example if creating a KPI for a Divert sequences you may also want to know how many divertshappened for the last 24 hours. Generally a Valve will open and close when the Divert occurs so for this wewould simply need to count how many times it has opened.

Sampling Mode would be Calculation

Calculation mode would be State Count

Proficy Historian Electronic Books Retrieval Topicyou will find explanations for all of the differentSampling Modes and Calculations Modes. To use calculation modes the Sampling Mode = Calculated.

Sampling Modes: Current Value, Interpolated values, trend, Calculated and Raw data options

Calculation Modes: Count, State Count, State Time, Min, Max, Total, Average and Raw data

Hybrid Modes: This mode of sampling has the ability to switch between sampled (likeinterpolated or trend) and raw data based on the actual and requested number of samples or aspecified time interval.

Query Modifiers: are used for retrieving data that has been stored in the archive. They areused along with sampling and calculation modes to get a specific set of data. (Only Good,Include Bad, Only Raw Samples, etc)


7/14


Base Tag Requirements to Develop KPIsTo create KPIs base Tags are required from the process, asset performance related and from the ERP systemsuch as order requirements and shifts operating. Many will already be been collected although could be inmultiple systems. Example of Tags that could be required based on the KPIs you wish to develop.

Historian Base Tag Examples

Shift ID Single Tag for all by Process Records duty shift ID (change of shift)

Asset ID Part of Tagname, or add Tag Can add Asset/Equipment name in spare configuration field

Process ID Part of Tagname, or add Tag Can add Asset/Equipment name in spare configuration field

Factory ID Part of Tagname, or add Tag Can add Asset/Equipment name in spare configuration field

Asset State ID Tag per asset Records the asset state options (stop, run, divert, maintenance, etc)

Asset Run Hours Tag per asset Records total run hours for an Asset

Asset Stop - Category Tag per asset Records reason for asset stoppage stored in the PLC (electrical, etc)

Valve Counts Tag per asset records total events of an Asset

Flow Rate Tag per asset passing a point - flow meter

Level Tag per asset Current level within an asset

Quantity Count / Yield Tag per Process Units / volume produced

Quality Tag per Process Pass / Fail (Unit/volume Quality Control check)

Rework Count Tag per Process Bad quality items reworked (item/volume)Electricity Usage Tag per asset KW used per time frame set (by Asset, Process, Factory)

Gas Usage Tag per asset Kg used per time frame set (by Asset, Process, Factory)

"Other Energy" Usage Tag per asset Kg/Ltr used per time frame set (by Asset, Process, Factory)

Vibration Tag per asset measures vibration of an Asset / Asset component

External Temperature Tag per meter records production area atmospheric temperature

External Humidity Tag per meter records production area atmospheric humidity

Emissions Tag per meter records emissions from the site

Historian Predictive Tag Examples (linked to, or updated from 3rdparty data-sources)Time slots KPI: Energy Need to be relevant to process

Process Predicted Time KPI: ACT Average time to complete task (Unit/ Ltr, etc)

Production Predicted Time KPI: ACT Expected time from start to finish less breaks

Production Predicted Rate KPI: OE_P Expect units/volume completed (time per unit)

Units / Volume Required KPI: Non completed Assigned units, or volume by average time / order

Asset Capacity / Level KPI: Remaining Capacity Total Level Capacity assigned to an Asset

Network Flow Capacity KPI: Total Flow Capacity Total volume the physical pipes (Network) can manage

Asset Scheduled Maintenance KPI: Asset Availability Total Maintenance time scheduled for an Asset

Operating Period / Shift KPI: Asset Availability Total hours an Asset can run less breaks per time period (shift/day)

Energy (Tag per type) KPI: Gas, Electric, other Expected Usage for an asset by Energy type

Relational database Data (SQL Server)

Downtime Reasons Adds to Downtime KPI SQL Look up reason Codes Operator selection - reason written to SQL

Shift / Personnel Adds to Shift ID SQL look up personnel per shift Operator selection - updates written to SQL

Alarm and Event DataBy including Alarm and Event Data (AE) within your reports users can more easily identify root-causes andvisually see trends that are impacting on performance. Proficy Historian has an AE Server options that ishighly recommended as it links the Process and Alarm data automatically reducing configuration and reportdevelopment requirements.

Alarms duringthe process


8/14


KPI Examples GeneralMost of these would be applied against a defined time period, shift, or whilst as Asset is in a particular state.Historian includes specific calculation modes to assist with KPI development such as the Total option.

Volume Amount that passed a point for a time period Flow Rate * Minutes (Time Difference)

Tags required Digital: Asset Run / Stopped Analog: Flow Rate User defined Time Period / Shift

Divert Volume Amount that passed during divert ID Flow Rate for Asset ID where Asset State ID = Divert * Minutes

Tags required Analog: Divert ID Digital: Change of State Analog: Flow rate

Level Capacity Level against Asset total capacity Asset Total capacity less Asset Current Level

Tags required Target 3rp party Value Analog: Current level Value

Flow Capacity Flow against maximum Flow capacity Asset maximum Flow Rate less Current Flow Rate

Tags required Target 3rp party Maximum Flow Analog: Current Flow Rate Analog: Asset ID

Rate (units) Asset / Process operating Speed Unit Count * Minutes

Tags required Analog: Unit Count User defined Time Period / Shift

Rate (volume) Asset / Process operating Speed Volume * Minutes

Tags required Analog: Total Volume User defined Time Period / Shift

Reject Count Total Units that fail QC process Quantity Count where Quality ID not= Pass

Tags required Analog: Quantity Count Digital: Pass ID / Fail ID

Reject Ratio Good to bad ratio Percentage of Pass to Failure

Tags required Digital: Pass ID / Fail ID

Scrap Rejects not/cant be reworked Reject Count less Rework Count

Tags required Quantity Count Analog: Count Rework Count Analog: Count

Non CompletedRemaining Units / Litres Quantity Target less (Quantity Count less Reject Count) plus+ Reject

Count with Quality ID = Pass

Tags required Target 3rp party Analog: Quantity Value KPI: Quantity - Rejects KPI: Rework Count = Pass

Order Count Total Order Count where quality = pass Quantity Count where Quality ID = Pass + Rework count whereQuality ID = Pass

Tags required Rework Count Quantity Count Quality ID

Vibration Monitoring Vibration within Asset Vibration Rate Value against Target Vibration Value

Tags required Target 3rp party Analog: Value Analog: Vibration Current Value

AOT

Asset Outage Time

Displays time an Asset was in Failure Asset where State (not=) RUN by Minutes

Tags required Analog: Asset ID Asset State ID User defined time / Shift ID

Asset Availability Total minutes an asset/process is available Operating Period less Scheduled Maintenance

Tags required Target 3rdParty: Maintenance Time Analog: Operating Minutes

Asset Up-Time Displays time an Asset was Running Asset Availability less AOT

Tags required Analog: Asset Availability KPI: AOT User defined time / Shift ID

Process Cycle Time Average time a process takes to complete atask - all units required with quality of pass.

Target Cycle Time against Actual Cycle Time for Asset ID (by shift)

Tags required Target 3rp party Analog: Total Minutes KPI: Order Count Time: End Time - Start Time

(A plant may have several assets that perform the same task. Monitor the Cycle Time as a performance measure between them)

TakT Time The available production time divided by

customer demand ( time per unit)

Asset Availability / Order Count for Asset ID (by shift)

Tags required Target 3rp party Analog: Order Count KPI: Asset Availability Time: End Time - Start Time

(The purpose of takt time is to precisely match production with demand, enables sales delivery schedules to be met)


9/14


KPI Examples DowntimeDowntime KPIs are used to create specific Asset / Process reports that outline the reason why downtimeoccurred. Failure for an asset by category.

Base Tags Include:

Asset/Process Run Hours, Failure Category ID, Asset/Process ID, Shift ID

Humidity and Temperature

Other tags that directly impact on asset performance rates.

SQL: Operator inputs for shift changes and Downtime ReasonsUse the Historian enumerated value function to change ID values to meaningful test

Downtime Planned Same as Asset Availability

Asset Availability Total minutes an asset/process is available Possible Run time less Scheduled Maintenance less Scheduled Breaks

Tags required Variable Value: Maintenance Time Time Period, Shift, 24 hrs, etc Time Period, 1 hr, 15 mins, etc

Asset Availability

Rate

% Total actual minutes an asset/process isavailable vs Expected Available time

% Run Hours / Asset Availability

Tags required KPI: Asset Availability Analog: Total Run Hours Analog: Scheduled Breaks

Downtime Actual Asset Actual downtime Total asset Run Hours where state (not=) Run

Tags required Analog: Asset Run Hours User defined Time period

Downtime

Unscheduled

Actual Downtime less Scheduled Downtime Total asset Run Hours where state (not=) Run less Asset Availability

Tags required Analog: Asset Run Hours KPI: Asset Availability User defined Time period

Asset Alarms

Downtime

Alarms for the asset / process during thedowntime period.

Historian AE Server

Downtime Bottleneck Used to identify bottlenecks in production Rate* Reject Ratio

Tags required KPI: Rate KPI: Reject ratio User defined Time period

The report/display would also include shift and downtime reasons from SQL, ideally correspondingAE data from Historian and downtime categories from Historian.

KPI Examples OeeThe below examples are included to complete a detailed Downtime solution, not to develop a custom OEEsolution that could end up costing more than Proficy Efficiency, a GEIP off-the-shelf OEE module. We willrefer to these KPIs as Oee.

OEE = Performance * Availability * Qualityo Performance = Actual production / Possible productiono Availability = Actual production time / Possible production timeo

Quality = Product produced (Less Scrap and Rework) / Product produced

Oee_P %

Performance

OEE rating against potential machineoperations

(Rate * Rejection Ratio) / (Rate) by user defined time / shift ID

Tags required KPI: rate * Reject ratio Target: Potential Production Rate User defined Time period

Oee_A %

Availability

The Actual production time / Potentialproduction time.

Asset Runtime Time / Asset Availability for selected time period

Tags required KPI: Asset Outage Time KPI: Asset Availability User defined Time period

Oee_Q %

Quality

OEE type quality calculation (Quantity Made less (Scrap + Rework)) / Quantity Made

Tags required Analog: Count Analog: Count of rejects used +

KPI: Scrap

User defined Time period

Oee % OEE = A * P * Q Oee_P * Oee_A * Oee_Q


10/14


KPI Examples Energy MonitoringThese KPIs can be applied to numerous types of energy sources; Electricity, Gas, Diesel, Coal, etc.

Base Tags Include:

Process ID, Asset ID, Shift ID

Meter usage rate as granulated as possible (asset, process, site)

Past energy bills and breakdowns to ascertain predictive usage

Humidity, Temperature and other tags that directly impact on asset performance rates.

A predefined time slot to measure power. (peak pricing times should be a time slot)o Peak Pricing Examples: Between (7am 8:30am) and (6pm7:30pm)

Electricity Used

(per time-slot)

Usage Rate per time-slot Electricity Meter usage rate by selected Time Slot

Tags required Analog: Energy Usage Rate User defined Time period

Electricity Peak

Identification

Identify high usage time-slots per shift/dayfor weekly, monthly and annual reports

Rank time slots from high value to low value per day/shift over amonth (or year to see seasonal trends)


Process ElectricityBreakdown

Group of assets used for a process % per asset of energy consumption to complete the process


Predicted Electricity

Usage

Asset / Process: predicted rates per time-slotthat can be tracked against in real-time.

Tags required Analog: Energy Usage Rate Target 3rp party Analog: Value User defined Time period

Electricity

Monitoring

Factory against Supplier readings. The totalfrom all meters compared to suppliercharges.

Total energy from all meters


The above are used for all energy types (CNG, LPG, Diesel, etc)

Total Energy Used

for the Process

Combines all energy sources used, Power,Gas, etc. $$ amounts can be applied

Total of Electricity, Gas & Other - defined user/batch time period

Energy usage per

unit

Used to calculate energy required per unitmade, or litre processed

Total of Energy used divided by units (litres) produced - user definedtime-period

Process Emissions

per time slot

Records emissions for an asset/process perenergy time-slot (per emissions meter)

Asset/Process Emissions per defined time-slot

Total Emissions

per time slot

Total of all emissions meters per energy

time-slot

Total of all Emissions meters per defined time-slot

Process Emissions

by user defined time

Records process emissions per user definedtime

Asset/Process Emissions per user defined time period

Total Emissions

by user defined time

Total of emissions meters per user definedtime

Total of Usage meters per user defined time period

Time Slot Emissions

Monitoring

Actual against predicted emissions per timeslot to ensure compliance is met

Emissions Actual against predicted by predefined time slot.

Daily Emissions

Monitoring

Actual against predicted emissions per dayfor a user defined time period

Emission daily totals for last 30 days.


11/14


Historian Enumerated ValuesAn Enumerated Data Set provides an enhanced way of displaying data. It enables you to retrieve numericdata as string state values. The string values can be used in reports or displays, improving flexibility indefining string values that suit your requirement. For example, a stored value of 1 can be returned as a stringvalue Running.

Creating enumerated values

The original/field value must be numeric You can define the state value as any data except BLOB and Scaled types

Arrays and Strings cannot be utilised for enumerated values

You must create an enumerated set and assign values to use enumerated results

An enumerated set can be applied to multiple Tags

Examples for device/asset Tags that could be enumeratedDescription Stored in PLC/SCADA as a number Enumerated To

Factory ID 543 Dry SideProcess/Machine ID 22 Drier 1

Asset/Device ID 113 Filler

Asset/Device State ID (Pump, Valve, etc) (0 or 1), (100 or 102) etc Stopped & Running or Open & Closed

Error Codes (Downtime Category code) 0, 1, 2, 3, ... Electrical, Mechanical, Blocked, etc

Shift ID 1, 2, 3, 4... Different duty shift names

Operator ID 1, 2, 3, 4.... Bob, John, Tania, Barry, etc

For best practice these IDs should match the corresponding IDs within your existing systems (SQL, Oracle, etc) such as shift details,machine / process names and IDs, error codes, etc.

We have chosen these examples as the information would be required in multiple different report types andnot just for Downtime Monitoring. Often the FactoryID, MachineID and AssetID are part of the Tagnameand therefore do not require a separate Tag to be captured.

Search Historian Tag Database

Select the Tag that you wish tocreate an enumerated set for.

View by Tagname, or Tagdescription.

On the Collections tab use thedropdown for Enumerate SetName

Click on Create New Set button.Configure the Set

Enter Name and description IE Control Valve State

Set the State (IE Open)

Set the Value (IE 1)

Add description

Click Save to List

Repeat to add more States tothe set as required.

Click on Save Set and OK oncecompleted


12/14


HMI Tagnaming convention: Proficy iFIX and other brandsThe Tagnaming convention deployed within the iFIX Server database could alsoidentify the machine andpiece of equipment been monitored negating the need for separate identification Tags.

We want the Tags within Historian and iFIX to be the same name so the Alarm and Event data can

be applied easily to the respective Historian Data Tags. We dont recommend changing the

Tagname within Historian to create a naming convention at this level

Example: Tag Name Convention: SM_BS_15_245.F_CVFactory ID SM Sawmill

Work Centre BS Bin SorterProcess / Machine ID 15 Machine code Plainer

Equipment ID 245 Equipment code In-feed Hydraulics

If your site has not deployed a detailed Tagnaming convention we can use other Historian fields to store theasset/device name for reporting purposes.

Example of an iFIX Tag: IFIX1_BATCH_TANK1LEVELExample of the description: Chemical Tank #1 Level

Only very limited information is available via the Tagname. Should you wish to add more descriptiveinformation this can be added to the Spare Configurationfield for the Tag stored within Historian.

To retrieve this data when building a report you will need to query the CollectorGeneral2 field.

To enable a report search by location the query maybe used several times however each one will

search for a different part of the entry; Saw Mill, Bin Sorter, Plainer, etc. For instance if we wanted

to create a downtime report for an area (all assets within the Plainer process/machine) we need to

be able to associate the Tag with the plant area. Alternately just use the Machine/Process name.

Note: Step Value on the above Tab enables square-tooth data representation often seen within HMIdisplays rather than sharp saw-tooth representation. Especially good for digital On/Off, Stop/Run views.


13/14


DDiissppllaayyiinnggKKPPIIssaannddDDeevveellooppiinnggRReeppoorrttss

There are numerous clients available to access and display Historian KPI tags. Often existing reportscurrently utilised can be altered to include Historian data. As KPI tags within Historian have standard Tagattributes they can be access by out-of-the-box tools included with GEIP products, or any OLE client.

Proficy iFIX HMI/SCADA- Use the standard tools provided out-of-the-box.As iFIX is an Operations based system generally it is used to display Operations-based KPIs

Historical Datalinks

Enhanced Charts

(SQL Block / Visiconx / VBA) to display and update data to SQL (shift and downtime reasons)

Proficy Historian Analysis (PHA) Use the standard tools provided out-of-the box.PHA is a Proficy Vision plug-in that is the primary companion visualization tool for Proficy Historian, andsupports both flat-tag and contextual, or model-based searching and trending of Historian tag data. It is easyto use, supports drag and drop, and is tightly integrated with Historian and Vision.

Standard time-based, XY and area charts Current value KPI tables

Historian Alarm & Event database table

The ability to do ad-hoc analysis, or save analysis sessions as favourites for fast recall andcollaboration

Print to PDF or Word

Proficy Portal (RTIP)- Use the standard tools provided out-of-the-box.Portal is perfect for root-cause analysis and process efficiency reporting, especially where trending andadhoc reports are required. It is fast and easy to set-up, supports drag and drop, includes an expression editor

and can link data from numerous data-sources (connectors maybe required). Standard Time-based, XY, Statistical and Category Charts

Historical Grids

Datalinks

Gauges and Dials

Heat Map visual to quickly display plant and process throughputs

Print to PDF, attached to email, send to recipients

Proficy Vision(Web Server Hosting) - Use the standard tools provided out-of-the-box.The ProficySOA server manages connections to many different systems including Historian, iFIX, SQL,Oracle, ERP systems, MES, Maintenance Systems and much more. It contains enhanced security andmanyS95 models such as Equipment, Process Procedures and Personnel; it includes a basic Visual Studiodevelopment tool to create basic reports. The full version of Visual Studio can be installed, or reportsdeveloped remotely can be copied to the ProficySOA system.

By installing Proficy Vision on the ProficySOA Server it enables almost any web-server to be hosted withinVision making them all accessible via a single URL, simplifying access to users from PC,s Tablets/iPads,Smart Phones, etc. ProficySOA and Proficy Vision are free to all users with a current GlobalCare supportpolicy and can host web sites from numerous remote servers.

iFIX WebSpace

Proficy Portal

SSRS Web server

Excel WebPages Almost any web server can be hosted within Proficy Vision


14/14


SQL Server Reporting Services (SSRS)- Use the standard tools provided out-of-the-box.SSRS utilises an OLE connection to access Historian data and is perfect for daily, weekly, monthly, annualreports where data requests are generally not changed (predefined attributes). SSRS is great for reports thatmany people access/view using tabular grids and data links. Historian supports direct connectivity, SQLLinked Server and Pass Through options enabling any configuration to be deployed maximising anyprevious investments made.

Tabular Grids

Datalinks

Some specific objects (Dials, Levels, etc) that support OLE connections

Often a complete Proficy Vision solution will include Proficy Portal, PHA, SSRS and some .Net displays.

Proficy Historian Excel Add-in - The included MS Excel Add-in offers administrative and reportingcapabilities. Both topics are covered within the Historian Electronic Books. There are also sample reportsincluded with the Historian install that can be easily modified to perform a variety of tasks. Reportsdeveloped in Excel can be converted to a web report and viewed with Proficy Vision.

Sample Reports on the Historian Server: C:\Program Files\Proficy\Proficy Historian\Samples Alarm and Events, Batch, Daily, Statistic Analysis example reports

The Historian OLE DB Provideris a data access mechanism (defined by Microsoft) that allows you toquery Historian product data using Structured Query Language (SQL) statements or other client reportingtools. It adds tremendous value to the Historian product by providing simple access to data from within theSQL environment, without the need for complex scripting.

Furthermore Proficy Historian OLE DB Provider includes standard Linked Serverfunctionality thatenables a remote Historian Server to appear as a local SQL Table again simplifying data retrieval and reportdevelopment.

For example there could also be an existing solution developed utilising a relational database (SQL,MYSQL, Oracle, etc) that you simply want to enhance. Use the OLE DB Linked Server option to add yourHistorian data to the existing system.

A test tool Historian Interactive SQL Tool is installed for testing your scripts before addingthem to your displays / reports.

There are OLE query examples within the Historian Electronic Books under the headingList of Examples.

For any assistance, or additional explanations please contact your GE Intelligent Platforms representative

Download - Proficy Historian Creating KPIs

Top Related