1 / 42

A New Model for SCADA and Measurement Hosts

ENTELEC Conference 2013. A New Model for SCADA and Measurement Hosts. Steve May CPU LLC Metairie, LA www.cpullc.com. SCADA. SCADA is an acronym that stands for S upervisory C ontrol a nd D ata A cquisition. . SCADA System Host:.

kylene
Télécharger la présentation

A New Model for SCADA and Measurement Hosts

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ENTELEC Conference 2013 A New Model for SCADA and Measurement Hosts Steve May CPU LLC Metairie, LA www.cpullc.com

  2. SCADA SCADA is an acronym that stands for Supervisory Control and Data Acquisition.

  3. SCADA System Host: A SCADA system host is the computer system that is used to gather data, view it, and control certain functions in the system. This system can also be used to Visualize data, perform Reporting, Well Testing and other functions.

  4. Measurement System Host: A Measurement system host is the computer system/software that is used to gather measurement (audit) data, Visualize the data, perform Reporting and other functions.

  5. SCADA/Measurement Differences: • SCADA – Real-time Data/Alarming • Measurement – Historical • SCADA – Control • Measurement – Audit • SCADA – PLC’s, RTU’s, sensors, etc. • Measurement – EFMs, Totalizers, etc.

  6. SCADA Foundations and Layers Business Processes and Work-Flow Layer Reporting, Well Testing, Allocations Layer Visualization, Mimics, Trending Layer Alarms, History, Scripting Layer Data Collection, Protocol Layer SCADA System Foundation (Vendor)

  7. SCADA History • Railroads • Utilities Panels of lights, buttons, switchs, knobs and dials

  8. Jubilee Train Line

  9. SCADA Hosts - 1970’s Business Processes and Work-Flow Layer Reporting, Well Testing, Allocations Layer Visualization, Mimics, Trending Layer Alarms, History, Scripting Layer Data Collection, Protocol Layer SCADA System Foundation (Vendor)

  10. SCADA Hosts - 1970’s

  11. Integration Challenges Then: • Getting the required data • Program Everything • Historians • Daily Production Reports • All you could do!

  12. SCADA Hosts - 1980’s Business Processes and Work-Flow Layer Reporting, Well Testing, Allocations Layer Visualization, Mimics, Trending Layer Alarms, History, Scripting Layer Data Collection, Protocol Layer SCADA System Foundation (Vendor)

  13. 1990’s - Yesterday Business Processes and Work-Flow Layer Reporting, Well Testing, Allocations Layer Visualization, Mimics, Trending Layer Alarms, History, Scripting Layer Data Collection, Protocol Layer SCADA System Foundation (Vendor)

  14. Integration Challenges Then (90’s): • Getting the required data • Program Most things • Integrate Historians • Custom Production Reports • Custom Well Testing • All you could do!

  15. Integration Challenges Still Today: • Getting the required data • Custom Production Reports • Custom Allocations • Custom Rollup Reporting • Custom Well Management • Custom Well Testing

  16. Integration Challenge Example 1: Custom Daily Production Reporting 2011-2012: • Customer had excel spreadsheet to manually do Daily Production Reports • Wanted to be integrated into the existing SCADA System.

  17. Integration Challenge Example 1:

  18. Integration Challenge Example 1:

  19. Integration Challenge Example 1:

  20. Integration Challenge Example 1:

  21. Integration Challenge Example 1: • 8 man-months – (2500 lines of code) • 2 other consultants spent 5 man-months trying to get the job completed. • Thus, 13 man-months * $150/hour = $312,000 That does not include company time!

  22. Integration Challenge Example 2: Well Testing 2009-2010: • Offshore Customer needed Well Testing solution. • Wanted to be integrated into the existing SCADA System.

  23. Integration Challenge Example 2: • Gather the data from the SCADA system, • Custom reporting, • Custom Screens, • Custom PLC Program.

  24. Integration Challenge Example 2: • Gather the data from the SCADA system • Custom reporting. • Custom Screens • Custom PLC Program

  25. Integration Challenge Example 2: • Gather the data from the SCADA system • Custom reporting. • Custom Screens • Custom PLC Program

  26. Integration Challenge Example 2: • 3 people – 15 month duration • 45 man-months • Thus, 45 man-months * $150/hour = $1,080,000 Again, that does not include company time!

  27. Review: • Program data gathering • Program Logic for Daily Production Report • Program Logic for Well Testing • Program Logic for Allocations • Program Logic for Rollup of information

  28. Today!!!!!!! - NEW MODEL Business Processes and Work-Flow Layer Reporting, Well Testing, Allocations Layer Visualization, Mimics, Trending Layer Alarms, History, Scripting Layer Data Collection, Protocol Layer SCADA System Foundation (Vendor)

  29. New Model – Program Nothing – Configure Everything: How?!?

  30. TM • Intelligent SCADA? • Smart SCADA? • NO! Relational SCADATM!

  31. Relational SCADATM: • Object Oriented – Create/Configure Objects • Device • Well • Test Separator • Separator • Tank • Facility • Company • Tag • Each have a relation to another object!

  32. Company Object: • Name • Todays Oil Production • Todays Gas Production • Todays Water Production • Yesterdays… • List of Facilities Facility Object: • Name • Todays Oil Production • Todays Gas Production • Todays Water Production • Yesterdays… • List of Wells • List of Test Separators

  33. Object Reporting: • Drop Company Object on Report • Assign the list of Facilities to a grid Object in Report • Assign columns of grid to fields in object • Have Rollup of all current Production! Since all Wells are related to Facilities and all Facilities related to the Company, the rollup of well oil, gas, and water are automatic. Thus, the Report is a simple drag-and-drop of information on a report and literally only takes minutes to configure!

  34. Object Reporting: • Drop Company Object on Report • Assign the list of Facilities to a grid Object in Report • Assign columns of grid to fields in object • Have Rollup of all current Production! • Name • Todays Oil Production • Todays Gas Production • Todays Water Production • Yesterdays… • List of Wells • List of Test Separators

  35. Savings of Object Reporting: 8 man-months vs 1 day of analysis and configuration OR $312,000 vs $1,200!

  36. Relational SCADATM Well Testing: • Create Well Test Scenario • Create Instance of Well Test • Put in test All Configuration based on the relations in the system!

  37. Relational SCADATM Well Testing Scenario: (Well A) + (Well B) = Test Separator Drag Well Object instances from the tree to the Well Test configuration screen to replace items in the scenario!

  38. Relational SCADATM Well Test: Well1 + Well2 = MainTS Put it in test!

  39. Savings of Relational SCADA Well Testing: 45 man-months vs 5 days of analysis and configuration OR $1,080,000 vs $6,000!

  40. Difference???: Custom Programming vs Configuration!!!

  41. Results?: • New Paradigm means: • Faster results • Better results • Easier to maintain • More Cost Effective • Quicker ROI

  42. TM Relational SCADATM Questions?? Steve May 504-432-7026

More Related