1 / 23

Message-Based Communications for Pipeline SCADA

Message-Based Communications for Pipeline SCADA. Stephen Koenig, P.E. Smarter Infrastructure for Oil and Gas December 3, 2013 Houston, TX. source: http://www.epa.gov/gasstar/images/newsroom/fall11-valve.jpg. source: http://www.welkereng.com/wfms/portfolio/images/pipeline.jpg.

diella
Télécharger la présentation

Message-Based Communications for Pipeline SCADA

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. Message-Based Communications for Pipeline SCADA Stephen Koenig, P.E. Smarter Infrastructure for Oil and Gas December 3, 2013 Houston, TX source: http://www.epa.gov/gasstar/images/newsroom/fall11-valve.jpg

  2. source: http://www.welkereng.com/wfms/portfolio/images/pipeline.jpg

  3. Data stored in the Corporate Accounting System Data calculated by meter station Flow Computer Sensor Data Data stored in the meter station Flow Computer source: http://www.transport4.com/PublicSite/t4publicweb/home.aspx

  4. Network Subscribe Publish Data Source Data Destination Message Broker Data Source Data Destination Data Source Data Destination Data Source Data Destination Message Format Topic Payload Messaging - Basic Concepts • Multiple data sources (publishers) send messages to multiple data destinations (subscribers) • Destinations subscribe by “topic” • Payload can be anything: text, binary, fixed fields, etc up to 250Mbytes in size • Broker supports multiple delivery options (QoS)

  5. Automation to SupportPipeline Operations Tank Gauging System Flow Computer Remote Terminal Unit Comm Processor Satellite Link to Control Center P T F

  6. source: http://www.northerngateway.ca/assets/498x245_contentimages/EnvironmenatlResponsibility/Pipelineassesment.jpg

  7. source: API RP 1165 – Recommended Practice for SCADA Displays

  8. Traditional Approach to SCADA Poll/Response • Host & RTU’s are serial devices – typically Programmable Logic Controllers • “Round Robin” polling • Data format optimized for mininimum overhead

  9. Problems with Poll/Response systems • Host “owns” communications link • Dedicated circuits are too expensive • Alarm latency increases with RTU count

  10. Evolution to Message-Based Communications Step 1

  11. Evolution to Message-Based Communications Step 2

  12. Evolution to Message-Based Communications Step 3

  13. Evolution to Message-Based Communications Step 4

  14. Challenges in Use of Message-BasedCommunications for SCADA • Controls – limited life in system • Stale Data – replace poll/response functionality in event-driven system • Security • Flexible architecture may result in new vulnerabilities • Message-based system must be as secure as traditional poll/response • Need for continuous improvement

  15. Benefits of Message-Based Approach to SCADA • Topic/Payload Message Structure • IP Routing • Intelligent Front-End Processor • Many-to-Many Architecture

  16. Benefits - Topic/Payload Message Structure • “Wildcard” subscriptions • Support for multiple applications on one message broker • Use of version number in topic • Facilitate prototype and test of new clients • Allows site-by-site migration strategy

  17. Benefits – IP Routing Scalability

  18. Benefits – IP Routing -- Redundancy Reducing the Impact of Failure Broker1 Broker2 Broker3 Broker4 • Provisions for broker equipment failure • Provisions for loss of primary communications link – backup link

  19. Benefits – Intelligent Front-End Processor Broker1 Broker2 Broker3 Broker4 • Adapt Serial Devices to IP/VSAT • Move polling/response to field • Ability to handle multiple RTU protocols • Local intelligence can supplement or enhance control system

  20. Benefits – Many-to-Many Architecture • Significantly reduced project schedules • Off-line systems receive live data for testing

  21. Future Opportunities for Message-Based SCADA Systems(from a 2005 perspective) • “Flight Simulator” for pipeline Controllers • Interface to business systems • Real-time meter ticket transactions to shippers and other carriers’ business systems • Distributed SCADA

More Related