2014 Software Global Client Conference

Transcription

1 2014 Software Global Client Conference

2 GEN INT-08 Multi-Galaxy Architecture Considerations for Large System Deployment Presented By: Richard Covington, DCP Midstream Pete Rullman, DCP Midstream Michelle Klein, SE Software Deliveries

3 Mobile App: Please take a moment Check into Session by: Select Detailed Schedule Select the specific session Click on Check in Take Session Survey by: Select Detailed Schedule Select the specific session Scroll Down to Survey and Provide Feedback 2014 Software Global Client Conference

4 Synopsis This session will describe the solutions for System Platform SCADA systems facing the management and development of large single galaxies. Provides an example of large single galaxy and solutions to segment large galaxies into multiple galaxies. Includes a case study with DCP Midstream.

5 Agenda # Topic Presenter 1 Synopsis of Session\Introductions Schneider Electric 2 Overview of the DCP Midstream DCP Midstream 3 History with Wonderware DCP Midstream 4 Key Business Challenges DCP Midstream 5 Considerations Schneider Electric 6 Solutions for Consideration Schneider Electric 7 Next Steps DCP Midstream 2014 Software Global Client Conference

6 DCP Midstream Case Study

7 MULTI-GALAXY SCADA ROADMAP Schneider Electric Global Customer Conference 2014

8 MIDSTREAM NATURAL GAS INDUSTRY The midstream natural gas industry is the link between the exploration and production of natural gas, and the delivery of its components to end-use markets. DCP Midstream is one of the few midstream companies with leadership in both Gathering and Processing and NGL Logistics 9

9 INDUSTRY LEADING POSITION #1 Gas Processor (1) #1 NGL Producer (1) #3 NGL Pipeline Operator (2) Natural Gas Processing (1) (MMcf/d) #1 DJ Basin (2) Front Range Pipeline #1 Permian Basin (2) Avalon / Bone Springs Lucerne 1 & Lucerne 2 (4) Plants Wattenburg NGL Pipeline Texas Express Pipeline Sand Hills Pipeline #2 Eagle Ford (2) #1 Midcontinent (2) Mississippi Lime SCOOP Granite Wash Southern Hills Pipeline 64 Plants (3) ~67,700 miles of Pipeline (3) Black Lake Pipeline DPM Owned or Joint Venture Plant / Fractionator DPM NGL Storage Facility DPM Owned or Joint Venture Pipeline DPM Owned or Leased Terminal DPM Plant under construction DCP Midstream Plant / Fractionator DCP Midstream Pipeline Keathley Canyon(4) NGL Production (1) (Bbls/d) 12% Percentage of the nation s gas supply we gather and/or process 17% 12 Percentage of the NGLs we produce in the US Round trips between NY and CA equals 67,700 miles of pipe (1) Source: Hart Energy Midstream Monitor/Midstream Business.com, August 2013, Top Gas Processors-NGL Producers of 2012 (2) Source: Bentek and Company data; Consolidated results include DPM (3) Stats include all assets in service as of June 30, 2014 (4) Under Construction DCP Midstream s large footprint and diversified portfolio provides significant growth opportunities 10

10 Today s SCADA Network 11

11 HISTORICAL SCADA Enterprise-wide SCADA project Pilot Began in 2007 Project Started in 2009 Purpose Gather the many independent DCP SCADA applications (multiple vendors) into one central source for better control and consistency across the business Historical SCADA 12

12 WONDERWARE PRODUCTS IN USE System Platform 2012 (3.5) Started at App Server 3.0 InTouch 9 (standalone) InTouch 10.1 (standalone) InTouch 10.5 (standalone / galaxy) InTouch for Terminal Services (Citrix) Historian w/reporting Services Historian Client WW Data Access Servers Today s SCADA 13

13 ACCOMPLISHMENTS System Areas 33 Total User Base 1,543 Concurrent Citrix Users 171 Galaxy Platforms 140 Configured IO Points 13,191 Historian Disk Usage 818 GB Data collection & storage since 2007 Today s SCADA 14

14 ACCOMPLISHMENTS Who uses our systems: Regulatory Commercial Environmental Operations Reliability Control Centers (Houston, Okarche, SENM) Today s SCADA 15

15 GALAXY FOOTPRINT GR View Client Object Server Historian 16

16 CURRENT ARCHITECTURE Today s SCADA 17

17 TODAY S SCADA The 2009 project along with DCP Midstream growth has proceeded to the point where the majority of our system data is coming through a single, large SCADA galaxy There are a few remaining legacy systems that are to be integrated into the larger system DCP Acquisitions (Gas and new entry into NGL) have increased the data load and maintenance requirement in the SCADA System Today s SCADA 18

18 KEY BUSINESS CHALLENGES Separate the Production and Development systems Align Production Areas to address concerns around - Reliability Scalability/Growth Supportability/Maintenance Flexibility Standards Offline Test System for - Proving system patches/upgrades (OS and software) Developmental testing of new assets or technology Network security & infrastructure testing How many galaxies do we really need? Complex vs Simple Tomorrow s SCADA 19

19 Considerations When Planning Galaxy Segmentation

20 One Galaxy

21 One Galaxy Reliability

22 One Galaxy Scalability

23 One Galaxy Maintenance

24 Considerations for Galaxy Segmentation

25 Considerations to Split SP Very Scalable Led to Massive Galaxies Within a Single Galaxy may be logically split: Geographical Technological Jurisdictional Commercial Political Integration of products/technologies across galaxies should not be achieved by creation of automation objects For many customers the practical size of a Galaxy is smaller than the technical limits. Platforms communicate with other platforms continuously; although data on the platform have no logical relationship, other than being in the same galaxy

26 Multiple Galaxies $Template Master

27 Key Benefits Reliability Scalability Maintenance No Single Point of Failure Expand Galaxy Multiple Engineers at Once; Restricted Access Autonomous Systems Create New Galaxies for Large Assets Engineered Solutions Per Galaxy Redundancy at All Galaxies Focused Modifications Controlled Rollout

28 Shared Data Requirements $Template Master.Station04Flow.Station04Flow

29 Data Between Galaxies ArchestrA Service Bus

30 Multi-Galaxy Communication MGC\ASB Turn one, or more, galaxies into data sources for another Automation system comprised of multiple, individual, galaxies At a Common Control Room, browse attributes at a Central Galaxy from a paired Remote Galaxy Subscribe to attributes in runtime; read and secured write One galaxy of the automation system can be used for central monitoring

31 MGC Configuration - Paring

32 Galaxy Concentrator $Template Master Galaxy Concentrator.Station04Flow.Station04Flow.Station04Flow

33 Multi-Pairing $Template Master.Station18Flow.Station04Flow.Station04Flow.Station18Flow

34 Considerations for Segmentation Engineering Consistency Operations InTouch Galaxy Boundaries Standardization Access to Dashboard Remote References Location of Nodes Master Template Galaxy Common Alarm Display Indirect Tagging Future Planning Protected Objects Access to InTouch View Native InTouch Graphics

35 Not Changed Alarms: The Alarm/Event subsystem functions no differently in a multi-galaxy compared to a single galaxy implementation It does not utilize ASB services Alarm display query syntax remain the same Ack still requires credentials per Active Directory History: ASB services are not directly involved in the Historian communication links There is no Paired Galaxy concept for Historian There is absolutely no difference for configuration of Historian when used in Multi-Galaxy architectures

36 DCP Midstream Tomorrow s SCADA System

37 NEXT GENERATION VISION Update Standards & Processes for the large/multi-galaxy SCADA system environment DCP / WW Joint Galaxy Review for best path forward Highlighting the pros and cons of multi-galaxy scenarios DCP SCADA Upgrades Template Galaxy - Centralized Object Version Control Test Galaxy Multi-Galaxy Communications Allows alignment of production areas and enables data communication Tomorrow s SCADA 43

38 VISION DELIVERABLES Improved Development Control Multi-Galaxy focused Standards De-centralized Production System Maintenance Less disruption during maintenance across the DCP SCADA Network Galaxy software/hardware incidents are isolated to that specific galaxy Tomorrow s SCADA 44

39 2015 AND FORWARD ROADMAP PROJECTS Develop SCADA Standards Develop SCADA Architecture Template Galaxy Template Structure Build out Workflow Process Galaxy 1 Build out Test Galaxy H/W & S/W Design Workflow Process Procure H/W & S/W Install & Configure Galaxy Migration Standalone Apps to Sys Plat 2014 Sys Plat 2012 to Sys Plat and Forward Roadmap 45

40 FUTURE SCADA NETWORK ARCH Tomorrow s SCADA 46

41 2014 Schneider Electric. All Rights Reserved. All trademarks are owned by Schneider Electric Industries SAS or its affiliated companies or their respective owners. 47