Building Control Strategies with Process Library Objects and Process Engineering Tools PlantPAx System Engineering

Transcription

1 Building Control Strategies with Process Library Objects and Process Engineering Tools PlantPAx System Engineering

2 Today s Agenda Building Your Control Strategies PlantPAx Library Add-On Instructions How they work together to add functionality Building Your HMI PlantPAx Graphic Symbols PlantPAx Faceplates Symbols and Faceplates for Built-In Instructions Current and Future Instructions Discussion 2

3 What are the Session Goals? Learn about the PlantPAx Library Add-On Instructions and Graphics for Logix and FactoryTalk View SE and View ME, where to get them, how to install them, and how to apply them Learn what many of the PlantPAx Library instructions do and how to tie them together to build powerful control strategies Learn how to quickly build HMI displays that are easy to use for Operators, Maintenance personnel and Engineers Learn what functions are currently available in the PlantPAx Library and what we are working on for future releases Learn where find online and reference documentation, and learn where to get help and support when you need it Learn about tools to help you build your own libraries of control strategies and displays and deploy them on your projects 3

4 Process Library Release 1.1 Posted on KnowledgeBase in March 2010 Includes first official release of advanced operator diagnostics 4

5 Process Library Release Posted on KnowledgeBase in September 2010 Included on the RSLogix 5000 v19 DVD Add-On Instruction Imports (L5X), Sample Applications (.ACD,.APA) Reference Manuals and Release Notes Look on Start Page under Sample Applications Or, using Windows Explorer: C: \RSLogix 5000 \Projects \Samples \ENU \v19 \RockwellAutomation \PlantPAx 5

6 PlantPAx Object Library Industry Use in 2010 Pulp & Paper PlantPAx Standard Library PlantPAx Standard Library Out of the box Out of the box Rubber Mixing Power Generation Fertilizers Water Treatment Oil & Gas Mining and Metals 6

7 PlantPAx Objects for OEM Applications: FactoryTalkView ME and Logix L23E/35E Development is completed Official release planned for Q1 FY11 with PlantPAx Object library 1.5. Beta is available. 7

8 Where are Rockwell Automation Process Solutions Being Used? Consumer North America Batch Chemical Process for Oral Care Consumer Latin America DCS Replacement for Milk Plant Life Sciences Asia Pacific Batch Process Control for Nutritionals Mfg. Life Sciences EMEA Solvent Recovery Unit Mining Latin America Plant Integration for Mining Port Operation Mining Asia Pacific Mine Automation and MES Minerals North America Dryer Optimization with Pavilion Technologies Oil & Gas EMEA Pipeline SCADA system Oil & Gas Latin America Compressor Station Controls Pulp & Paper EMEA DCS Replacement for Pulp Mill Power EMEA Primary control for 2 x 680 MW Units Water Utility North America DCS Replacement for Water Treatment Plant Ongoing success in hybrid and heavy industries, growing success in continuous applications 8

9 2010 Industry Awards Chemicals Mfg Electric Power Generation Food & Beverage Mfg Metals, Minerals & Mining Oil & Gas Extraction Petroleum Refining Pharma & Life Sciences Plastics & Rubber Mfg. Pulp & Paper Mfg Water & Wastewater Processing Continuous Regulatory Control Emerson Process Mgmt. Emerson Process Mgmt. Rockwell Automation Rockwell Automation Emerson Process Mgmt. Honeywell Emerson Process Mgmt. Emerson Process Mgmt. Emerson Process Mgmt. Rockwell Automation Batch Process Automation Emerson Process Mgmt. Rockwell Automation Rockwell Automation Rockwell Automation +1 Rockwell Automation (previously Emerson) Honeywell (previously Emerson) Emerson Process Mgmt. -1 Emerson Process (previously Rockwell) Rockwell Automation +1 Rockwell Automation (previously Emerson) Continuous Sheet/Web Monitoring & Control Honeywell No winner No winner Rockwell Automation No winner No winner No winner Honeywell ABB No winner Safety / Emergency Shutdown Invensys Process Systems +1 Rockwell Automation (previously Invensys) Rockwell Automation +1 Rockwell Automation (previously Siemens) Invensys Operations Management Invensys Operations Management Rockwell Automation Rockwell Automation Invensys Operations Management Rockwell Automation Sequential Logic Control Rockwell Automation Rockwell Automation Rockwell Automation Rockwell Automation Rockwell Automation Rockwell Automation Rockwell Automation Rockwell Automation Rockwell Automation Rockwell Automation In 8 of 10 industries, customers prefer PlantPAx RA picked up four new industry categories in 2010, a net gain of 3 9

10 PlantPAx System Tools and Utilities The PlantPAx Process Add-On Instruction and Graphics Library The Logix View Utility (LVU) Process System Estimator for Logix Architect 10

11 Meet Phil Phil is the Lead Controls Engineer at Oklaxas Pipeline Some Phil Facts : Responsible for pipeline controls, instrumentation, SCADA networking and communication Working for Oklaxas (and predecessor pipeline operators) for over 20 years Has multiple projects at any given time Replacing PLC-2/20 and competitive controls, most without program documentation About Oklaxas Pipeline Company Crude oil pipelines across several southwestern states Over fifty pump stations Updating stations to include modern controls, implement required leak detection, and improve overall pipeline control and operation A fake company based in Amarillo, Texas Phil and Oklaxas Pipeline are Personas used in library development 11

12 Phil s Goals Code at all sites should be based on the same reusable modules Train all maintenance technicians on these modules and how they play together Self-documenting, obvious how code works Only differences in code should be for differences in equipment at each site Modules should do device diagnostics Determine when equipment has failed Determine when equipment is about to fail React appropriately to equipment failure Let maintenance techs know what to bring with them before heading out Allow maintenance using HMI Save time by not having to start up RSLogix 5000 and go online Easy to use but secure Truck drivers use the HMI too, not just pipeline controllers 12

13 New Application: Mosquito Station Mosquito Pump Station Located near Pecos, Texas It has two fixed-speed pumps, a pig catcher and a pig launcher, and numerous motoroperated valves It pumps crude oil coming in from Varmint Station out toward Cockroach Station It receives crude oil from trucks into two local tanks and pumps this oil out as well This is the first of many Oklaxas pipeline station applications which will use the PlantPAx Process Library Phil attended TechED 2010, so he got a head start He has downloaded the Library from RA KnowledgeBase Answer ID He already has some training on RSLogix 5000 and FactoryTalk View SE He has created a new RSLogix 5000 Project: MosquitoStation.ACD He has created a new FTView SE Application: MosquitoStation 13

14 Set up a Routine and Start Coding Phil is using Function Block Diagram coding to show the flow of information between blocks The same functions can be done easily in Ladder Diagram or Structured Text Don t forget to JSR to your new Routine (or just make it a Main Routine)! 14

15 First, I have a pump with a fixed-speed motor So Phil imports the P_Motor Add-On Instruction 15

16 All Dependencies are Imported The P_Motor instruction uses P_Alarm and P_Mode IMPORTANT: All dependencies are included in the AOI import file Embedded AOIs and all required Data Types (UDTs, STRINGs) 16

17 Add the P_Motor Instruction to the Code Add the P_Motor instruction Set up its Tag Oklaxas coding standard: use a Controller Tag 17

18 Now We Have a Pump Motor and wire its output 18

19 Default Configuration IMPORTANT: Every instruction defaults to its simplest, basic device configuration. Motors: outputs only with no run feedback Valves: outputs only with no limit switch feedback Additional features are used if you configure / enable them Details are in the Reference Manual for each instruction 19

20 Okay, Let s Test It! Verify, Download and Run the MosquitoStation.ACD project 20

21 Testing P_Motor With no other Modes requested, P_Motor defaults to Operator Mode It s ready to receive Operator Commands to Start and Stop 21

22 Testing P_Motor Check that both OCmd_Start and OCmd_Stop work 22

23 But I Need to Start and Stop the Pump from my HMI Add the library components to your HMI Application First, import the Images (all the.bmp files) Then, import the Global Objects (all the.ggfx files) Finally, import the Displays (only the GFX files you need) The order is important: each later item depends on the previous items 23

24 Don t Forget the Embedded AOIs Each Faceplate or Help Popup counts as only ONE Display even though the Faceplate has multiple tabbed views. P_Motor uses P_Mode and P_Alarm within it, so don t forget to include their Help Popup Displays when you import the GFX files. 24

25 Add the Pump Symbol Create a new Display if needed Add a Pump object from the P_Motor Global Objects Open the Library GGFX file Drag and Drop onto your Display 25

26 Configure the Tag All you need is ONE Global Object Parameter 26

27 Start the Client and Call Up the Faceplate Click the Graphic Symbol to call up the faceplate Start and Stop the Pump 27

28 But the Names are Generic Open the Engineering Tab of the faceplate and type your application text 28

29 Here s Where These Strings Are Used Text entered on the Engineering Tab of the faceplate is stored in Local STRING Tags within the Add-On Instruction Instance Data. Cfg_Desc (Description) is used for: Faceplate Title Bar Graphic Symbol Tooltip Cfg_Label (Label) is used for: Graphic Symbol Label Cfg_Tag (Tagname) is used for: Faceplate Operator Tab Tagname Graphic Symbol Tooltip Some AOIs have text for Device States, Engineering Units, or other functions The actual Logix tagname is shown in the Tooltip for the Tag name entry field 29

30 But my Motor has Run Feedback First, connect the run feedback input to the block This edit can be done online 30

31 Adding Run Feedback Then open the faceplate and enable Run Feedback checking Engineering tab: it HAS Run Feedback; Maintenance tab: USE it! 31

32 HAS and USE Has means the function exists, is coded, and is intended to be used. Under control of Engineering If an AOI is configured to not HAVE a function, it is not visible to Operators or Maintenance Use means the function should be used as intended Under control of Maintenance Allows Maintenance to bypass or disable a function temporarily. Maintenance Bypass Indicator appears when a function is bypassed ( Has but not Used ). 32

33 But I need an Interlock The motor should stop if the Pump Case Temperature is high (TSH) Add a Discrete Input, and interlock on a high temp (contact opens) First, import the Discrete Input AOI (You can do this online!) 33

34 Adding Discrete Input Add the discrete input instruction, create the tag, wire the input These additions can be done online 34

35 Adding Discrete Input Add a Discrete Input Graphic Symbol on the Display Import the needed GFX files Drag and Drop the Discrete Input symbol NOTE: common symbols are in the Process Graphics Library GGFX Look there first, then look in other files for specialized symbols 35

36 Adding Discrete Input Tie the Graphic Symbol to the controller Tag (remember how?) Global Object Parameter Run the HMI Application (if already running, just call up the Display) and test it 36

37 Connect Discrete Input as an Interlock Set up the text Wire it as an Interlock 37

38 Okay, Let s Test It! Start the motor Change the TSH input to 0 (or use Substitute PV) Note that the motor Interlock stops the motor and keeps it from starting. 38

39 It s a big motor I Need to Enforce the 3-start Rule The thermal mass of the motor is small compared to its winding Applying starting current too often will overheat the windings Allow three successful starts within a given period of time The running motor has a fan to cool it Enforce a restart delay after the third start unless the motor has run long enough to cool off If the motor fails to start at any time, enforce a restart delay These rules are enforced by the Restart Inhibit (P_ResInh) Add-On Use P_ResInh as a Permissive IMPORTANT: Interlocks vs. Permissives Interlocks are checked at all times,will stop a motor and keep if from starting. Permissives are checked when a start command is received and only prevent starting. Once the motor is running, Permissives are ignored. 39

40 Add the Restart Inhibit Instruction As before, Import the AOI. Then add an instance to the code and wire it. NOTE: Because the wire loops back, you need to right-click the wire and mark it Assume Data Available to resolve the loop 40

41 Using the Restart Inhibit Faceplate On the HMI, import the Restart Inhibit Faceplate GFX file Then, on the Motor Graphic Symbol (pump), add the Tag Remember: Global Object Parameter The Restart Inhibit Faceplate is called up from a button on the Motor Faceplate 41

42 Using the Restart Inhibit Faceplate Finally, on the Motor Faceplate, enable the new function It s a HAS function ( has restart inhibit ), so it s on the Engineering Tab Enabling it makes the Operator Tab button VISIBLE 42

43 Okay, Let s Test It! Start and Stop the pump motor three times in succession The Permissive indicator shows you cannot start again Click the hourglass to call up the Restart Inhibit Faceplate 43

44 Restart Inhibit Faceplate Features The Restart Inhibit Faceplate serves three purposes, even though it has only one (Home / Operator) Tab It shows how the function works (State Diagram) It shows the current status (bold-lined state), and the time remaining before you can start again (at the top) It allows Maintenance to change the configuration of the timer presets via the data entry fields 44 44

45 About Time Even though time in the controller is handled in milliseconds, all time configuration parameters in the PlantPAx Library instructions are entered in SECONDS. Some are integer (DINT) seconds. e.g., Alarm Minimum Duration times REAL seconds are used where the parameter is like to be less than one second or where fractional seconds matter. e.g., Discrete Input debounce time Times are generally displayed in seconds. Exceptions: Restart Inhibit: the time remaining until ready to run is in minutes and seconds Run Time Accumulator (P_RunTime instruction): equipment run times (total, last, longest) are reported in hours, with displayed resolution of 0.1 hours Just like the Hour Meter on your MCC 45

46 Many Process Object Faceplates have Multi-function Diagrams like P_ResInh Examples: Discrete Input, Analog Output (Maintenance Tab) Diagrams (1) show how the instruction s functions work, (2) show the device s current state or dataflow, and (3) allow entry of device configuration 46

47 But I Need to Jumper Out Interlocks and Permissives can be Bypassable or Non-Bypassable Bypassable Interlocks and Permissives can be bypassed by Maintenance Bypassed when the instruction is in Maintenance Mode Bypassed when the instruction is in Override Mode if so configured Maintenance can leave them bypassed temporarily for Operators Non-Bypassable Interlocks cannot be bypassed No need to open RSLogix 5000, go online and force I/O or modify code Everything can be done from HMI Faceplates Built into motor, valve, drive and other device instructions Secured Must be logged in as Maintenance to switch to Maintenance Mode or enable Bypass function 47

48 We Wired Ours as Bypassable. Test it! Go to the Motor Faceplate, Maintenance Tab Bypass the Interlocks and Permissives Test it! Run the pump with high case temperature The Maintenance Bypass Indicators are there to remind you that you have bypassed an intended function Note: Inp_NBIntlkOK, Inp_NBPermOK are the Non-Bypassable inputs 48

49 User Based Mode Model Mode Model is fashioned after practical user access rules. 49

50 User Based FactoryTalk View Security Model Security model aligns faceplate actions with user class. 50

51 Operator is Kept Informed Interlock and Permissive Bypassing is also shown on the Operator (Home) Tab of the Faceplate Note the yellow square: it warns that an Interlock is NOT OK, but is being BYPASSED. See the little bypass map? Permissives are OK and are being bypassed You have been warned! 51

52 How Do I Remember All Those Indicators? You only have to remember THIS ONE: Every Faceplate has a Help Popup that shows all the indicators that appear on the faceplate. Sub-topic help is available for Alarm and Mode indicators 52

53 But I Have More Interlocks and I want to see which one tripped out the pump! P_Intlk instruction supports: Up to 16 interlock conditions each configurable for OK State = 1 or 0 (not in OK State shuts down) each configurable as Bypassable or Non-Bypassable each configurable as Latched (requires Reset) or Not Latched Its own faceplate with First-Out indication (bar) and configurable text for each interlock condition 53

54 Add the P_Intlk Instruction, Wire it up Import P_Intlk Add-On Instruction into project Wire IntlkOK Status outputs to corresponding P_Motor Inputs Wire Bypass Active status of Motor back ( Assume Data Available ) Wire interlock conditions to inputs (8 exposed by default, 16 available) 54

55 Add the HMI Faceplate and Link from Motor Import the Interlock Faceplate GFX One Help Popup for both P_Intlk and P_Perm (Permissives) Instructions Add the Global Object Parameter on the Pump Symbol 55

56 Enable the Feature ( HAS ) On the P_Motor Faceplate Engineering Tab, enable the link to P_Intlk The Interlock Status Indicator becomes a Button to call up the Faceplate 56

57 Call Up the Interlocks Faceplate By default, there is a single condition text entry Each condition with non-null text (Engineering Tab) is made VISIBLE 57

58 Configure Each Interlock Condition Enter descriptions for all Interlock conditions connected to block inputs Configure OK State, latching and bypass ability for each condition 58

59 I Have All These Bearing RTDs Bring in via RTD input cards, and use P_AIn (Analog Input) objects You know the drill! Import the new AOI if needed Add instances to your Routines Create/Modify Tags per your coding standards Wire to your I/O 59

60 Add Analog Inputs to HMI You know the drill here too! Copy needed GFX files into HMI application Drag Graphic Symbol from GGFX to your Display Enter Global Object Parameters Run it and enter configuration via Faceplate 60

61 Don t Forget Scaling and Engineering Units TIP: Input (raw) or PV (scaled) can be reverse-scaled The bar graph will still increase upward. (It knows!) 61

62 Invalid Configuration Indicator Appears on Graphic Symbol and Faceplate if any configuration parameter is invalid Follow the trail of breadcrumbs: to get to the item and fix it. The item to fix will have the Invalid Configuration Indicator or will be in a magenta box. In this case, the scaling minimum and maximum (raw pair or scaled pair) cannot have the same value. 62

63 Don t Remember What a Symbol Means? LOOK IN THE? POPUP. hint: 63

64 I Want Special Interlock Logic Phil s Interlock Logic Requirement (for this project): If ANY bearing temperature is High-High, or If a MAJORITY of bearing temperatures are High, then Shut down the pump. Phil s Capture Requirement: Capture the logic state when it trips so I can see which condition(s) shut us down. RSLogix 5000 online only displays the current logic state. I d have to write special buffering code to copy all the states when it trips. Phil s Display Requirement: Show the interlock logic on the HMI so I don t have to open RSLogix 5000 and walk through the ladder code to see it. We might not have RSLogix 5000 at the site. Phil s Would Be Nice Requirement: Let me (and only me) modify the logic online. 64

65 There s (soon) an Easier Way P_Logic, coming soon, lets you do up to 8 logic (bit) functions in an AOI. It s designed for complex interlocks. It captures a snapshot of the logic state when it trips so you can see what condition(s) shut the system down. The Faceplate displays the interlock logic so you don t have to open RSLogix 5000 and walk through the ladder code. The logic is displayed using common symbols. e.g., like ANSI/ISA (Table 5.7: Binary Logic Symbols) An Engineer can modify the logic online. It includes AND, OR, XOR, Select, Majority (Voter / Qualified OR) and Set / Reset (latch) gates with up to four inputs per gate. There s no separate NOT gate. Every gate input can be configured as inverting. 65

66 P_Logic: Complex Interlocks and more Has 8 inputs, 8 gates, timer for final output Fully online configurable Info breadcrumb indicates snapshot available 66

67 You ve Built a Strategy Now What? The Logix View Utility lets you build a Library of Control Strategies Add-On Instructions Routines, Programs Graphic Symbols Displays Sub-Strategies Reuse Strategies in your applications Instantiate code and HMI together Fill in only unique data, and in one place Need more info? Contact your local SA/TC/GPTC 67

68 LogixView Utility (LVU) What is it? Software tool for reducing configuration time of Logix controllers and FactoryTalk View HMI applications. Development time is reduced through the application of user-configurable Logix code libraries and HMI component libraries. LVU is an engineering workstation software that is intended to complement, not replace, the use of RSLogix 5000 and FactoryTalk View Studio. 68

69 Logix View Utility How it fits Logix View Utility Logix Library Builder Controller Configuration Builder Building Library Building Application HMI Display Template Builder HMI Configuratio n Builder 69

70 Intended Users for LVU The software can be used by two types of users: library builders and process control engineers or configuration technicians. An example of library builders is Corporate Engineering responsible for maintaining consistency and standards across all the company production plants. Corporate Engineering is responsible for developing (or purchasing) thoroughly tested libraries for reuse in the plants. Another example of library builders is System Integrators (SI). SI wants to increase profitability by reducing engineering cost through the reuse of configuration templates. Process control engineers or configuration technicians are responsible for building the Logix controller configuration and HMI application by deploying the library templates. 70

71 Building Process Application Libraries with Logix View Utility Control libraries are created with RSLogix 5000 using any of the programming languages.the source template can contain AOIs, UDTs, routines, equipment phases. Logix Library Builder Tool is provided for defining the substitution variables, parameters, and associated HMI elements (displays, faceplates, alarms). Configure the template definition. Add title, description, and optional help file. Define variables in the source code that will be replaced when instantiated. Parameterize the control template with generic variables. Define how tags are to be deployed and if it will be aliased to IO. Define Mapped (buffered) IO tag elements (if any). Configure any associated FactoryTalk View HMI display templates. Build display template using FactoryTalk View Studio. Use tag placeholders as substitution variables. Export the file in XML format. LogixView HMI Display Template Builder Tool provides an interface for defining how the tag placeholders are to be replaced when the template is instantiated. Define which backing tag variable is mapped to the tag placeholders and define what values (e.g., tag address, tag description) are to replace the placeholders when instantiated. 71

72 Building Process Application with Logix View Utility Add Control Strategies From Libraries Fill in the Blanks Configuration, target tag names, description, numeric parameters, etc Tool adds the target tags, routines, and dependent data types to the target controller file. Tags can be pre-marked as being aliased or buffered to IO tags. ST mapping code is automatically generated. Display Templates can be associated to the Control Strategy Template. Display instances are generated automatically. Process display can also be built by dragging-and-dropping Logix tags to the display builder. Tool replaces placeholders on display template with Logix tags and adds tag associated faceplates 72

73 LogixView Utility Version 5 New Features Configure Multiple Controllers and Multiple HMI Servers

74 LogixView Utility Version 5 New Features (Cont) Project Organizer Group Control Strategies from Multiple Controllers In User-Defined Folders

75 Market Access Model for LogixView Utility Project SI/SP/Corporate Eng. LVU user 90% of complexity is on this level Pre-qualified to use tool (i.e. advance Logix/View training) Logix View Utility LVU Libraries Control Strategies Device Objects Library Support Components (UTDs, AOIs, GOs) SI/SP/Corporate Eng. LVU Library Developer SA/TC GPTC/GOTC GATC Process System Engineering Logix View Utility (PlantPAx Standard/Base Device Library) 75

76 Support Model for LogixView Utility LVU is not a typical (standard) product that can be supported through Technical (Phone) Support for the following reasons: Main complexity is in development of the LVU user specific libraries i.e. development of application components LVU will have comparatively limited proliferation off-line tool for design automation during development time Primary mode of support for the tool itself is documentation (manual) For reporting issues and training we ll use the following model: LVU District/Account Champions Support Support Support Process System Engineering GPTC, GOTC, GATC, SA/TC Validate LVU Lib developer LVU project developer Report Issues with Tool 76

77 Support for the PlantPAx Library Technical Support Specialists have been trained Call your Technical Support number Ask for PlantPAx Support But first: Check the Help Screens Check the Reference Manuals We suggest placing these in a C:\RSLogix5000\Library\ subfolder Also online in Literature Library 77

78 Current PlantPAx Library Input Processing P_AIn: Analog Input P_AInAdv: Advanced Analog Input P_AInDual: Dual Sensor Analog Input P_DIn: Discrete Input Motors P_Motor: Single-Speed Motor P_Motor2Spd: Two-Speed Motor P_MotorRev: Reversing Motor P_MotorHO: Hand-Operated Motor (monitor only, optional trip) P_VSD: Variable-Speed Drive Valves P_ValveMO: Motor-Operated P_ValveSO: Solenoid-Operated P_ValveHO: Hand-Operated Output Processing P_AOut: Analog Output (manual loading station) Permissives and Interlocks P_Intlk: Interlocks with First-Out P_Perm: Permissives Dosing (Ingredient Addition P_DoseFM: Flowmeter Dosing P_DoseWS: Weigh Scale Dosing Monitoring P_ResInh: Restart Inhibit P_RunTime: Run Time and Starts L_CPU: Logix CPU Utilization Common Elements P_Alarm: Common Alarm Block P_Mode: Common Mode Block P_Reset: Central Reset (can propagate in a hierarchy) 78

79 Library Graphics for Built-In Instructions Version 1.1 of the Library now includes Faceplates and Graphic Symbols for these built-in Process Instructions (Function Blocks): PIDE: Enhanced PID TOT: Totalizer RMPS: RampSoak 79

80 Library Objects In Development These Library Objects are in development for the next release (2.0): P_AInMulti: Multiple Analog Input (up to 8), use Average or Median P_CtrlValve: Analog or Pulse output valve with position feedback (optional for analog) P_D4SD: Discrete 4-state (or 2-state, 3-state) Device P_DOut: Discrete Output, includes nameable states, pulsing / blinking P_Fanout: One CV fans out to up to 8 outputs, with initialization (back-calc) up. P_Logic: As shown earlier, 8 inputs and 8 gates of boolean logic P_nPos: n-position Device (up to 8), e.g., for multi-port valves P_PTComp: Pressure / Temperature Compensation, basic PV=nRT compensator P_ValveMP: Mix-Proof Valve, supports seat lift and SIP / CIP connections P_ValveStats: Valve Statistics: travel time, total strokes, etc. Essentially, a P_RunTime for Valves Steam Table Instructions P_PSat, P_PSatAdv: Saturation Pressure, given Temperature P_TSat, P_TSatAdv: Saturation Temperature, given Pressure P_Steam: Entropy, Enthalpy and Specific Volume given P and T L_Redun: Monitoring of Redundant Controller Pair, can initiate switchover L_TaskMon: Monitoring of a Controller Task, alarm if task time exceeds plan Beyond 2.0: Lead/Lag/Spare Strategy samples, more sample applications What do you need? 80

81 Enhancements Across the Library Several 2.0 Library-wide enhancements are in development More Breadcrumbs Operator Information Available Device Not Ready Other HMI Changes (see next slides) Tool to configure colors (or lack thereof) to your standard V19 Enhanced Redundancy Support And leveraging other V18 / V19 RSLogix 5000 features 1.5: FactoryTalk View ME 5.1 Graphics and Faceplates Fully functional and supported Fit on 640 x 480 screen 81

82 Why is the HMI Changing? Because you told us to To align with industry standards Emerging ISA Standard NAMUR ASM Conservative use of color on Graphic Symbols Stronger highlighting of abnormal conditions Consistency among library objects Updated graphics (keeping up with the Jones) 82

83 Changes on the Graphic Symbols Smaller display area Simpler graphics, less use of color for normal conditions Active alarms Indicated by: A & E style symbols Label changes color Colored border around object NAMUR symbols for Comm Failure Comm Uncertain (out of spec) Maintenance Bypass (check function) New Not Ready to Operate symbol Old (1.5): New (2.0): 83

84 Changes on the Faceplates? Bigger alarm bell in tab keys with A & E symbols Entire alarm indicator blinks for alarms needing reset or acked Object spacing and justification to enhance readability Important data points (like PV) now have a dark gray background and bold text New windows style groups using shaded lines rather than boxes to separate data Mode objects are now in their own global object file New (2.0): Old (1.5): 84

85 Questions?