Experience with PI Cloud Connect (PICC) for JV Data Sharing

Transcription

1 Experience with PI Cloud Connect (PICC) for JV Data Sharing Presented by: Tony Goodreau, PI Global Administrator Hess Corporation Simon Wright, Founder & CEO Industrial Evolution Copyright 2014 OSIsoft, LLC.

2 Hess Overview Leading global independent energy company Pure- play explorabon & producbon (divested all refining, markebng, retail & trading) Focus on high growth, low risk 17% 22% 10% 8% Produc'on (2012) 17% 26% Onshore US Gulf of Mexico Asia Pacific West Africa North Sea Other Organized into 3 Business Units: Offshore ProducBon Onshore ProducBon ExploraBon HQ New York City By the Numbers (2013) Revenues $22 Billion Fortune 500 #75 ProducBon (oil equivalent) 289,000 Bbl/Day Reserves (oil equivalent) 1.3 Billion Bbl Capital expenditures $6.8 Billion Employees 4,000 March 25/26, 2014 OSIsob Users Conference, San Francisco, CA Page 2

3 Hess PI System selected as Enterprise Historian in 2005 Best in class for high volume, Bme- sequenced data capture & storage Standard across O&G upstream sector Largest number of interfaces to data sources of any historian PI System deployments PI System scope 12 PI servers (consolidated to 2 in 2014) 70,000 tags 350 users 100 s of PI ProcessBook displays March 25/26, 2014 OSIsob Users Conference, San Francisco, CA Page 3

4 10 Years of PI Data Sharing Experience Oil & Gas Business Leads to Risk MiRgaRon Results in Real- Time Data Sharing Need Extremely capital intensive Economically risky Joint ventures Contract operabons 3rd party reliance Security AnB- trust Standards Support JV Data 3rd Party Data In From Out To In From Out To Shell (Field #1) (PI) Shell (Field #2) (PI) Shell (Field #3) (PI) BHP Billiton (Field #1) (PI) BHP Billiton (Field #2) (PI) Anadarko (CygNet) Anadarko (CygNet) Baker- Hughes (elynx) Baker- Hughes (elynx) March 25/26, 2014 OSIsob Users Conference, San Francisco, CA Page 4

5 Data Sharing Concerns Security VPN tunnel required Double trouble - major scrubny by Hess & partner security Long lead Bme AnB- trust Desire not to connect Hess network & systems to compebtors Want to be seen to comply Standards PI System may be biggest and best, but not the only data source Partners use: CygNet, Wonderware, PHD, elynx & various SCADA s Cannot rely on partner s standard matching Hess s Support Partners want the data, not the system Hess cannot extend support outside Hess Hess wants one throat to choke March 25/26, 2014 OSIsob Users Conference, San Francisco, CA Page 5

6 Data Sharing Architecture Local Local PItoPI via VPN Enterprise Local Local Local March 25/26, 2014 Enterprise Hess Corpora'on PItoPI via VPN Industrial Evolu'on Secure Data Center (PI Inside!) PItoPI via VPN PI- OPC via VPN Flat File via FTP OSIsob Users Conference, San Francisco, CA Enterprise Enterprise CygNet elynx SCADA Partners Page 6

7 PotenRal Impact of PICC What changes? Eliminates need for VPN between Hess and DaaS service provider Removes Hess s VPN vulnerability Speeds up data sharing when 3 rd party also has PI System Aligns with OSIsob product road map What does not change? SBll need intermediate DaaS service provider Maintains Hess s anb- trust compliance needs Handles all Hess s support needs with 3 rd parbes Handles all 3 rd parbes support needs without involving Hess Complies with all data standards, not just PI System March 25/26, 2014 OSIsob Users Conference, San Francisco, CA Page 7

8 PICC Overview Features Transfers PI data between a Publishing Node and any number of Subscribing Nodes via mirrored PI AF structure PublicaBon and SubscripBon done asynchronously à eliminates the need for coordinabng efforts between parbes Presents itself via web- based PICC Customer Portal, managed by OSIsob InstallaBon PI Connect client must be installed on a PICC Node at both Publishing & Subscribing ends (PI server, PI AF server or any other computer may act as PICC node) PICC node requires PI access & internet access to communicate with the PICC Customer Portal PI AF client tool must be installed on the PICC node, plus PI data & tag configurabon access privileges Auto- Behavior PI AF creabon and maintenance (AF Structure, Elements, Aoributes and PI tags) done automabcally upon successful subscripbon March 25/26, 2014 OSIsob Users Conference, San Francisco, CA Page 8

9 PICC Customer Portal March 25/26, 2014 OSIsob Users Conference, San Francisco, CA Page 9

10 Hess s Chosen PICC Architecture Publishing PI Connect Node Enterprise PI Connect Client PI AF Client PI AF Server PI Server Hess Corpora'on PI AF Structure Mirroring PI Connect Client PI AF Client PI AF Server PI Server Industrial Evolu'on PI Connect Node Shared Subscribing March 25/26, 2014 OSIsob Users Conference, San Francisco, CA Page 10

11 Hardware/So^ware Requirements PI Connect Client PI AF Client PI Connect Node Ability to communicate to the internal PI AF servers and PI servers involved in the data sharing Internet access is required OperaBng System: 32/64 bit versions of Windows Vista SP2, Windows 7 or Windows 8 32/64 bit versions of Windows Server 2008 SP2 64 bit versions of Windows Server 2008 R2 or Server 2012 Microsob.NET Framework 4.5 or higher PI AF Client 2012 SP2, Versions x or higher PI AF Server PI Server Any PI AF 2.x version Enterprise March 25/26, 2014 OSIsob Users Conference, San Francisco, CA Page 11

12 Trial EvaluaRon Process Hess & Industrial EvoluBon independently CTP (Customer Technology Preview) Program Pre- Trial (in Industrial EvoluBon Environment) Set up 2 test servers in Industrial EvoluBon test center Configure 1 test server as PICC publisher Configure 2nd test server to subscribe to published data Monitor data flows speed and reliability Trial (between Hess & Industrial EvoluBon) Configure Hess desktop as PICC publisher Re- configure Industrial EvoluBon subscriber to subscribe to Hess published data Monitor data flows speed, reliability & security Roll- Out? March 25/26, 2014 OSIsob Users Conference, San Francisco, CA Page 12

13 PublicaRon Set- Up PI AF PICC Node Portal Created a dedicated sharing PI AF structure on publishing PI AF server y Structure Name (e.g. PI_Share_Hess) y Element_001 (e.g. PI tag #1 descriptor) w Aoribute_001 (PI tag #1 ID) y Element_002 (e.g. PI tag #2 descriptor) w Aoribute_002 (PI tag #2 ID) y Element_003 (e.g. PI tag #1 descriptor) w Aoribute_003 (PI tag #3 ID) ExisBng desktop PC at Hess Connected to source PI AF server & with Internet access Installed PI AF client tool Installed PI Connect client à RelaBvely straight forward and managed by wizard Configured PI Connect client via PICC Customer Portal Created publicabon on the PICC Customer Portal and granted access to Industrial EvoluBon No IT involvement since ports required allow outgoing traffic by default March 25/26, 2014 OSIsob Users Conference, San Francisco, CA Page 13

14 SubscripRon Set- Up PI & PI AF PICC Node Portal Set up a dedicated PI System (including PI AF) at Industrial EvoluBon to receive subscribed data Set up dedicated PICC node Ensured desbnabon PI server set as PI AF client tool default Installed PI Connect client Connected PICC node to PICC Customer Portal Subscribed to published data via PICC Customer Portal PICC recreated the published PI AF structure into the default (i.e. the desbnabon) PI server & created all associated PI tags March 25/26, 2014 OSIsob Users Conference, San Francisco, CA Page 14

15 Post Set- Up ObservaRons 1 PI tags were the same as on the source PI server, plus the prefix PIC_ à Hardcoded in PICC and cannot be changed (at this Bme) 2 3 If the PI tag had already existed on the desbnabon PI server, it would not have been created and informabon to that effect will appear in the log file All PI tags inherited the same aoributes as for the publishing PI system digital statesets were automabcally created where they did not exist 4 Only results of calculated tags (Performance EquaBons, Totalizers) are mirrored March 25/26, 2014 OSIsob Users Conference, San Francisco, CA Page 15

16 PotenRal Data Sharing Architecture Local Local Enterprise Local Enterprise Enterprise Local Local March 25/26, 2014 Hess Corpora'on Industrial Evolu'on Secure Data Center (PI Inside!) PI- OPC via VPN Flat File via FTP OSIsob Users Conference, San Francisco, CA Enterprise CygNet elynx SCADA Partners Page 16

17 Current LimitaRons 1 PI NoBficaBons not supported 2 PI Event Frames not supported For Table Lookups, stabc PI AF tables must be transferred via PI AF import/ export History recovery not supported prior to date of inibal configurabon in version tested but available now PICC does not yet support deliberate delays in data publishing PI AF client tool default server forces each share to use a separate PICC node OSIsob Go- to- Market not yet rolled out March 25/26, 2014 OSIsob Users Conference, San Francisco, CA Page 17

18 Results March 25/26, 2014 OSIsob Users Conference, San Francisco, CA Page 18

19 Conclusions PICC shows potenbal to be a useful replacement for PItoPI over VPN 50% of Hess shares are not to/ from PI System Hess will conbnue to use Industrial EvoluBon s DaaS services as an unbiased 3rd party go- between on maoers of support, outages Pricing model maoers PICC works as adverbsed Speeds up DaaS deployment in an All PI System environment Limited tesbng on scalability due to CTP restricbons March 25/26, 2014 OSIsob Users Conference, San Francisco, CA Page 19

20 Presenter: Co-Presenter: Tony Goodreau Simon Wright Tel: +1 (713) Tel: +1 (602) PI Global Administrator Founder & CEO Hess Corporation Industrial Evolution Copyright 2014 OSIsoft, LLC. 20

21 Brought to you by Copyright 2014 OSIsoft, LLC.