Object Oriented SCADA

Transcription

1 Object Oriented SCADA Nate Powell PE Custom Controls Unlimited Inc. Robert Shull PE CAP Custom Controls Unlimited Inc ISA Water/Wastewater and Automatic Controls Division Symposium (WWAC) photocopying, recording or otherwise, without the prior written permission of the publisher. 1

2 Nate Powell PE & Robert Shull PE CAP Control Systems Engineers for Custom Controls Unlimited Inc. North Carolina State University Graduates, Nate (03/06), Robert (10,12) In charge of project management, programming, engineer consulting ISA Members since 2010 photocopying, recording or otherwise, without the prior written permission of the publisher. 2

3 Presentation Outline Description of Object Oriented SCADA Discussion of how SCADA HMI systems are traditionally developed. Our method of development using Object Oriented concepts. How we implement concepts across different platforms and technologies. SCADA system examples and graphics. Continued improvement and future developments. photocopying, recording or otherwise, without the prior written permission of the publisher. 3

4 Object Oriented SCADA Programming standardization Nothing New Advances in technology/software IEC (1993) Using Objects that are clearly defined, easily visible, and easily reusable. Challenge to Engineers and programmers: how do all the pieces tie together? I/O Program/ Processing Communicate Display/ SCADA HMI photocopying, recording or otherwise, without the prior written permission of the publisher. 4

5 Traditional Methods of SCADA Development -Field Side Start With Linking I/O to Program Tags Program Tags Used in Ladder, Structured Text, Function Blocks Table of Tags or Addresses served up for communications photocopying, recording or otherwise, without the prior written permission of the publisher. 5

6 Traditional Methods of SCADA Development -HMI Side Build Tags Again Possibly Import, CSV, XML, etc. Build from Scratch (Scaling, Data Type, Etc.) Create Graphics Link Graphics to tags Link Alarms to tags Link History to tags photocopying, recording or otherwise, without the prior written permission of the publisher. 6

7 How can we improve? Standardize Field Side How can we cut the amount of time to do these traditional methods? Reusable Logic Maintain Revisions Field Tested Account for many programming situations Prepare logic for communications Group variables and addresses Keep same methods across various programming platforms. Works with multiple PLC s and HMI s photocopying, recording or otherwise, without the prior written permission of the publisher. 7

8 How can we improve? Standardize HMI Side How can we cut the amount of time to do these traditional methods? Reusable Tag Types Quickly Link to PLC Addressing Choose what tags to create or not (tag counts cost money) Prepare logic for communications Group variables and addresses Keep same methods across various programming platforms. Works with multiple PLC s and HMI s photocopying, recording or otherwise, without the prior written permission of the publisher. 8

9 Examples Reusable Programming Objects Easily Reusable Different Software Same Concept Use I/O as required Pump example: Seal Fail, Over Temp, Overload, Run Fail photocopying, recording or otherwise, without the prior written permission of the publisher. 9

10 Examples Reusable Programming Objects Processes and Functions Change Parameters on the fly without modifying actual logic. photocopying, recording or otherwise, without the prior written permission of the publisher. 10

11 Maintaining Object Libraries PLC HMI Version Numbers of Objects User Notes, Author, Date Created, Date Revised Graphical Libraries Names Correspond to PLC Objects Tags Correspond to PLC Objects Group Effort Backup and save in centralized location Keep everyone informed of changes, versions, and how to implement (lunch and learn) photocopying, recording or otherwise, without the prior written permission of the publisher. 11

12 Benefits of Reusable Logic Saves time Easy to troubleshoot Instead of checking line after line of code the I/O are easily visible in one locations Link Objects together Traditionally had to link within code using addressing Standard Library Maintain Revisions Keep all users/programmers on the same page photocopying, recording or otherwise, without the prior written permission of the publisher. 12

13 Challenges - Communications How To Simplify Data Transfer to SCADA HMI Modbus Sequential Data Start of Data, End Of Data Packet Together Ethernet IP Group Data into Similar Data Files OPC, CIP (tag names) Repeatable Sytanx Pump1.Running, Pump2.Running, Pump3.Running Etc. photocopying, recording or otherwise, without the prior written permission of the publisher. 13

14 Program Objects to HMI Objects Simplify Tag Creation PLC HMI Tag Type photocopying, recording or otherwise, without the prior written permission of the publisher. 14

15 Program Objects to HMI Objects Reusable Graphics photocopying, recording or otherwise, without the prior written permission of the publisher. 15

16 Use As Needed Every Application is Different Pick and Choose Pieces names Use Parameters Toggle Visibility Increment IO Addresses Pump1.Fail Pump2.Fail photocopying, recording or otherwise, without the prior written permission of the publisher. 16

17 Different HMI Platform? Same Concept PLC Object HMI Tags HMI Graphics photocopying, recording or otherwise, without the prior written permission of the publisher. 17

18 Finished Product System Build On Objects photocopying, recording or otherwise, without the prior written permission of the publisher. 18

19 Finished Product System Build On Objects photocopying, recording or otherwise, without the prior written permission of the publisher. 19

20 Improving Efficiency Using Existing Tools Don t re-invent the wheel Create Reusable Logic Create Reusable Tag Structures Create Reusable Graphics Learn from experience Don t need different versions of same items (pump with flowmeter/pump without flowmeter) Incorporate it all and use what you need Include items for alarming and scaling to easily adapt to different control schemes. photocopying, recording or otherwise, without the prior written permission of the publisher. 20

21 Savings On Time* Per Process (Pump Example) 25 Tags PLC Programming Communications (Addressing) HMI Building Tags HMI Graphics TOTAL Traditional Methods (Minutes) 30 Minutes: Logic Linking Tags 30 Minutes: Assigning to table on a per tag address 20 Minutes: From Scratch or Import Then Configuring Settings 10 Minutes: From Scratch Link Tags 90 Minutes Object Oriented (Minutes) 5 Minutes: Standard Block Attach Variables 2 Minutes: Start Address, End Address for sequential Variables 5 Minutes: Create Instance of Tag type and define settings 2 Minutes: Draw Linked Graphic 14 Minutes * Data collected from years of experience by the good people at Custom Controls Unlimited Inc. photocopying, recording or otherwise, without the prior written permission of the publisher. 21

22 Savings On Time Over 50 % Time saved Potentially Days of Configuration Can be developed by multiple users simultaneously due to standardized object libraries Not just one person who knows what s going on in the programming and HMI Easier to Quote Jobs, Win Bids, Keep Customers photocopying, recording or otherwise, without the prior written permission of the publisher. 22

23 End User Benefits Don t have to be a genius to understand End Users Can be easily trained and understand the programming and technology that runs their process. Easy to add pieces Adding pump, changing I/O, no longer a huge hassle, trained customer could complete without assistance. Lower cost for ultimately more features Open non-proprietary protocols and programming languages photocopying, recording or otherwise, without the prior written permission of the publisher. 23

24 Continued Improvement Keep up with Engineer Specifications Account for new features and new I/O required for jobs Manage Library and Graphic objects on a scheduled basis Learn from every new job New Objects Changes to logic photocopying, recording or otherwise, without the prior written permission of the publisher. 24

25 Future Development Easier ways to integrate sequential tag addressing for protocols like Modbus, Siemens, Ethernet IP Create OEM layers for SCADA HMI to allow a starting template with graphics already available (no importing or linking to shared libraries of objects) Externally manage object libraries in centralized location Object for different software packages Check in check out (two people not modifying at the same time) Documentation of what versions were used on what projects photocopying, recording or otherwise, without the prior written permission of the publisher. 25

26 Thank You!! We are pleased to be a part of the 2017 WWAC Symposium and share how we are doing things at Custom Controls! QUESTIONS/COMMENTS?? photocopying, recording or otherwise, without the prior written permission of the publisher. 26