PBWW222 IntelaTrac Advanced Features – Getting More Out of Your IntelaTrac Investment

2. PBWW222 IntelaTrac Advanced Features – Getting More Out of Your IntelaTrac Investment Presented to OpsManage‘11 Presented by Lance Zhou 11/09/11 Invensys proprietary & confidential

3. Introduction • The purpose of this session is to provide you with in-depth information on powerful IntelaTrac features you probably are not using, but which could really pay off if you used them at your facility. • We will cover: • Using Decisions in a Procedure • Using the Expression Editor • Utilizing the New Features in IntelaTrac 4.1 • Asset Type Properties • “Use Last Value” in Asset Properties in Calculation

4. Invensys Enterprise Control Offerings Corporate Systems Industry Solutions Services: Consulting, Project Execution, Learning, Operational Improvement, Maintenance & Support Partner Ecosystem Corporate Software Applications Invensys and Third Party Manufacturing / Production Operations Automation Invensys and Third Party Enterprise Control System IT Platform Integration and Collaboration Platform

5. Where The Offerings We Will Discuss Fit Within TheInFusion Enterprise Control System Execution Integration & Collaboration Platform Enterprise Asset Management Mobile Workforce Management Manufacturing Execution Systems Batch Performance Software Applications Enterprise Manufacturing Intelligence Asset Performance Performance Measurement and Reporting Enterprise Integration Visualization Quality Optimization Workflow Advanced Process Control Simulation / Optimization Design Operator Training Third-Party Offerings Open Device Integration Web Portal Control Automation Software Applications DCS PAC SCADA HMI Application Toolkit Safety Turbomachinery Control Safety Instrumented Systems General Purpose Safety Historian Measurement & Instrumentation Recorders Instrumentation Controllers

6. Pillars of Operational Excellence and Focus of This Discussion Operational Excellence Level 3 (Multi-plant/Multi-site) Environment And Safety People Level 2 (Plant Floor/Area) Asset Level 1 (Resource/Asset) Control

7. IntelaTrac Captures Stranded Data Typically 40-60% of assets in a plant are not instrumented IntelaTrac solution is a necessity even in newly built, fully instrumented manufacturing plants 7

8. Provides Mobile Solutions, but ALSO… Operator Training Process Data Operator Rounds Operation Logbook Product Changeover Manual Maintenance Alarms and Events Lock Out/Tag Out Compliance Startup Procedures

9. Task-Specific Decision Tree Check Pump Manual Operation Manual Data Oil Condition Good Bad Manual Input OR ? YES NO Predefined Decision Trees By Role, Process, Task IF OIL GOOD GO TO NEXT TASK CHECK TEMP Good Bad Predefined Decision Trees By Role, Process, Task Predefined Decision Trees By Role, Process, Task OR ADD OIL THEN GO TO NEXT PUMP SHUTDOWN THE PUMP Mobile Solutions: Superuser- Intelligent Workflow… IntelaTrac Approach Linear Procedures VS Decisions

10. 1 • Using Decisions in a Procedure

11. To Demonstrate, Let’s Start with a Simple Problem • Q: How do we set up a Task that should only be executed between 9:30 a.m. and 3:30 p.m.? • A: Use Decision instead of Condition.

12. 2 • Using the Expression Editor

13. More Difficult Problem • Q: What is the weight of the fluid in the tank during the fall season? • A: Considering the only data point collected is the tank level, we need to calculate for volume, and multiply by relative density. • Using the Expression Editor, this could be solved in one step.

14. Data Collection • A typical data collection procedure works like this: • Operator collects data point • Operator brings collected data to Server • Data value is evaluated • Based on the evaluation, actions are taken (hopefully) • Example: The temperature of the pump needs to be collected. What is the temperature? • [ … ] deg F

15. Reaction via Calculation • A typical reactionary procedure works like this: • Operator collects data point • Data value is evaluated • Based on the evaluation, actions are taken • Example: The temperature of the pump needs to be collected.What is the temperature? If the temperature is: • Lower than 200 deg F – No additional actions, go on to the next task • Between 200 deg F and 300 deg F – check coolant level, refill coolant if needed • Above 300 deg F – Stop pump immediately, report incident to proper personnel, check coolant, refill coolant if needed, replace coolant if needed, test pump, check for leaks

16. Using Historical Values in Calculation • By using Historical Values in a calculation, we can compare current data points with historical data values. • Example: The temperature of the pump needs to be collected. • What is the temperature? • What was the temperature yesterday? • Is the temperature getting higher?

17. Preventive Maintenance via Predictions • A typical predictive procedure works like this: • Operator collects data point • Data value is evaluated • Historical data value from the same task/asset is evaluated • Based on the evaluation, preventive actions are taken • Example: The temperature of the pump needs to be collected.[Task] What is the temperature? • [Internal] What was the temperature the last time this pump was inspected? • [Internal] If the temperature is rising quickly (even though it is still under the high-temperature alarm level) • [Action] Ask the operator to shut down the pump and perform full maintenance. (Launch maintenance procedure.)

18. 3 • Utilizing the New Features in IntelaTrac 4.1

19. NEW in 4.1 – Asset Centric Data Model • Task Group Status and Tasks can be predefined for Assets to facilitate consistent and faster procedure configuration • Example: All pumps of a certain type use the same Status choice list • Calculations designed to “Use Last Value,” including Asset Status, will now include values entered in different procedures • Example: One procedure configured for “Monday-Friday” data collection and another configured for “Weekend” data collection will share history for the same task, even if the task title is different • “As-Found/As-Left” data for tasks will now be easier to capture, as the Task history can include both conditions, even in the same procedure • Example: Now, with the use of “Conditional Tasks,” a procedure can be configured for follow-up data collection after a condition starts, providing a clearer picture to Supervision of what was done and why • Reports in Auditor Plus based on Asset Types and Shared Data

20. Designated Task and Group History • Procedure Configurator can assign the data history that will be available to the field operator for each individual Task Group or Task • The configuration can be selected by either number of points or number of days • Example: Tasks in a “Monthly” procedure can be configured to deliver the last 10 points (10 months), whereas tasks in the “Daily” procedure are configured to deliver the last 15 days (30 points)

21. Procedure Configuration and Management • Asset may now be assigned at the Task level, independent of the asset assigned at the Group level

22. Asset Centric Configuration • Three-Step Process: • Configure Asset Types and Associated Properties • Fin Fan, Pump, Vessel, Valve, and so on. • Assign Assets to Assets Types (Assets inherit Properties) • Pump 123, Tank 575a, Mixing Machine 1, and so on. • Procedure Configuration Using Asset Properties 1 2 3

23. Step 1: Asset Type Properties Setup • Asset Types are hierarchical • Hierarchy determined by the customer • Each Asset Type level can have associated Properties

24. Step 1: Asset Type Properties Setup • Asset Types are hierarchical • Hierarchy determined by the customer • Each Asset Type level can have associated Properties • Title (Default Task Group or Task Title) • Data Type (Including Item Response & Status)

25. Step 1: Asset Type Properties Setup • Asset Types are hierarchical • Hierarchy determined by the customer • Each Asset Type level can have associated Properties • Title (Default Task Group or Task Title) • Data Type (Including Item Response & Status) • Mobile History • Days • Points

26. Step 1: Asset Type Properties Setup • Asset Types are hierarchical • Hierarchy determined by the customer • Each Asset Type level can have associated Properties • Title (Default Task Group or Task Title) • Data Type (Including Item Response & Status) • Child Asset Types inherit properties of their Parents

27. Step 2: Assigning Assets & Types • Find Assets • Browse Hierarchy • Use Search

28. Step 2: Assigning Assets & Types • Find Assets • Browse Hierarchy • Use Search • Modify Assets • Display Name • Type (Browsing)

29. Step 2: Assigning Assets & Types • Find Assets • Browse Hierarchy • Use Search • Modify Assets • Display Name • Type (Browsing) • Type (Drag & Drop)

30. Step 2: Assigning Assets & Types • Find Assets • Browse Hierarchy • Use Search • Modify Assets • Display Name • Type (Browsing) • Type (Drag & Drop) • Properties Assigned

31. Step 3: Configure Procedures • Drag & Drop • Task Group Status • One or more Task Properties

32. Step 3: Configure Procedures • Drag & Drop • Task Group Status • One or more Task Properties

33. Task Group Edit Panel • Asset Property • Select Status • Mobile History • Select Days or Points

34. Task Edit Panel • Asset Property • Select from list • Mobile History • Select Days or Points • Assets can be assigned to Tasks independent of Groups

35. Lance Zhou, Invensys Training Lance.zhou@invensys.com tel. (949)639-8648

36. 4 • Questions and Answers

37. Q & A