experience with pi cloud connect for jv data sharing with pi cloud connect for jv data sharing ......

© Copyr i gh t 2014 O SIs o f t , LLC .

Presented by:

Experience with

PI Cloud Connect

for JV Data Sharing

Tony Goodreau, PI Global Administrator

Hess Corporation

Simon Wright, Founder & CEO

Industrial Evolution

8%

26%

17%22%

17%

10%Onshore US

Gulf of Mexico

Asia Pacific

West Africa

North Sea

Other

Hess Overview

Production(2012)

• Leading global independent energy company

• Pure-play exploration & production (divested all refining, marketing, retail & trading)

• Focus on high growth, low risk

March 25/26, 2014

By the Numbers (2013)

Revenues $22 Billion

Fortune 500 #75

Production (oil equivalent) 289,000 Bbl/Day

Reserves (oil equivalent) 1.3 Billion Bbl

Capital expenditures $6.8 Billion

Employees 4,000

Exploration

Organized into 3 Business Units:

Onshore Production

Offshore Production

HQ New York City

OSIsoft Users Conference, San Francisco, CA

• PI System selected as Enterprise Historian in 2005

Best in class for high volume, time-sequenced data capture & storage

Standard across O&G upstream sector

Largest number of interfaces to data sources of any historian

PI @ Hess

March 25/26, 2014

• PI System scope

12 PI Servers (consolidated to 2 in 2014)

70,000 tags

350 users

100’s of PI ProcessBookdisplays

• PI System deployments


http://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&docid=TDIVVG1ijiy7KM&tbnid=pMMP0tYFP9pDzM:&ved=0CAUQjRw&url=http://loveada.com/&ei=b9IDU5T9KaXayAHz3YDYBg&bvm=bv.61535280,d.aWc&psig=AFQjCNFREmmfbp0EyVrQTPDinA7oyXvzzQ&ust=1392845730938696
















10 Years of PI Data Sharing Experience

March 25/26, 2014

Oil & Gas Business

• Extremely capital intensive

• Economically risky

Risk Mitigation

• Joint ventures

• Contract operations

• 3rd party reliance

Real-time Data Sharing Need

•Security

•Anti-trust

•Standards

•Support

Leads to… Results in…

JV Data 3rd Party Data

In From… Out To… In From… Out To…

Shell (Field #1) (PI)

Anadarko (CygNet) Baker-Hughes (eLynx) Baker-Hughes (eLynx)



BHP Billiton (Field #1) (PI)

BHP Billiton (Field #2) (PI)

Anadarko (CygNet)


Data Sharing Concerns

March 25/26, 2014

• VPN tunnel required

• Double trouble - major scrutiny by Hess & partner security

• Long lead timeSecurity

• Desire not to connect Hess network & systems to competitors’

• Want to be seen to complyAnti-trust

• 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’sStandards

• Partners want the data, not the system

• Hess cannot extend support outside Hess

• Hess wants one “throat to choke”Support


Data Sharing Architecture

March 25/26, 2014

Enterprise

PI System

Industrial EvolutionSecure Data Center

(PI Inside!)Hess Corporation

Local

PI System

Local

PI System

Local

PI System

Local

PI System

Local

PI System

Enterprise

PI System

Enterprise

PI System

Enterprise

CygNet

eLynx

SCADA

Partners

PI to PI via VPN

PItoPI via VPN

PItoPI via VPN

PI-OPC via VPN

Flat File via FTP


• What changes? Eliminates need for VPN between Hess and DaaS

service provider Removes Hess’s VPN vulnerability

Speeds up data sharing when 3rd party also has PI System

Aligns with OSIsoft product road map

• What does not change? Still need intermediate DaaS service provider

Maintains Hess’s anti-trust compliance needs

Handles all Hess’s support needs with 3rd parties

Handles all 3rd parties’ support needs without involving Hess

Complies with all data standards, not just PI System

Potential Impact of PICC

March 25/26, 2014 OSIsoft Users Conference, San Francisco, CA

PICC Overview


Features

• Transfers PI Data between a “Publishing Node” and any number of “Subscribing Nodes” via mirrored PI Asset Framework (PI AF) structure

• Publication and Subscription done asynchronously eliminates the need for coordinating efforts between parties

• Presents itself via web-based PICC Customer Portal, managed by OSIsoft

Installation

• 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 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 configuration access privileges

Auto-Behavior

• PI AF creation and maintenance (PI AF Structure, Elements, Attributes and PI Tags) done automatically upon successful subscription

PICC Customer Portal


Hess’s Chosen PICC Architecture


PI Server

PI AF Server

En

terp

rise P

I S

yste

m

PI AF Client

PI Connect ClientP

I C

on

nect

No

de

PI Server

PI AF Server

Sh

are

d P

I S

yste

m

PI AF Client

PI Connect Client

PI C

on

nect

No

de

PI AF

Structure

Mirroring

Hess Corporation Industrial Evolution

Pu

bli

sh

ing

PI S

yste

m

Su

bscri

bin

g P

I S

yste

m

• Ability to communicate to the internal PI AF servers and PI Servers involved in the data sharing

• Internet access is required

• Operating 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

• Microsoft .NET Framework 4.5 or higher

• PI AF Client 2012 SP2, Versions 2.5.2.x or higher

Hardware/Software Requirements


PI Server

PI AF Server

PI AF Client

PI Connect Client

PI Connect Node

Enterprise PI System

• Any PI AF 2.x version

Trial Evaluation Process


CTP(Customer

Technology Preview) Program

Pre-Trial (in Industrial Evolution Environment) Set up 2 test servers in Industrial Evolution 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 Evolution) Configure Hess desktop as PICC publisher Re-configure Industrial Evolution subscriber to subscribe to Hess published data Monitor data flows – speed, reliability & security

Roll-Out?

Hes

s &

Ind

ust

rial

Evo

luti

on

ind

epen

den

tly

Publication Set-Up


PI AF

• Created a dedicated sharing PI AF structure on publishing PI AF server

PICC Node

• Existing desktop PC at Hess

• Connected to source PI AF server & with Internet access

• Installed PI AF client tool

• Installed PI Connect client Relatively straight forward and managed by wizard

Portal

• Configured PI Connect client via PICC Customer Portal

• Created publication on the PICC Customer Portal and granted access to Industrial Evolution

• No IT involvement since ports required allow outgoing traffic by default

Structure Name (e.g. PI_Share_Hess)

Element_001 (e.g. PI Tag #1 descriptor)

Attribute_001 (PI Tag #1 ID)





Subscription Set-Up


PI System• Set up a dedicated PI System

(including PI AF) at Industrial Evolution to receive subscribed data

PICC Node• Set up dedicated PICC node

• Ensured destination PI server set as PI AF client tool default

• Installed PI Connect client

• Connected PICC node to PICC Customer Portal

Portal• Subscribed to published data

via PICC Customer Portal

• PICC recreated the published PI AF structure into the default (i.e. the destination) PI server & created all associated PI tags

Post Set-Up Observations


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 time)

2• If the PI Tag had already existed on the destination PI Server, it would not have

been created and information to that effect will appear in the log file

3• All PI Tags inherited the same attributes as for the publishing PI System – digital

statesets were automatically created where they did not exist

4• Only results of calculated tags (Performance Equations, Totalizers) are mirrored

Potential Data Sharing Architecture

March 25/26, 2014

Enterprise

PI System

Industrial EvolutionSecure Data Center

(PI Inside!)Hess Corporation

Local

PI System

Local

PI System

Local

PI System

Local

PI System

Local

PI System

Enterprise

PI System

Enterprise

PI System

Enterprise

CygNet

eLynx

SCADA

Partners

PI Interface for OPC via VPN

Flat File via FTP


Current Limitations


PI Notifications not supported

PI Event Frames not supported

For Table Lookups, static PI AF tables must be transferred via PI AF import/export

History recovery not supported prior to date of initial configuration 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

OSIsoft “Go-to-Market” not yet rolled out

1

2

3

4

5

6

7

Results


Conclusions

• PICC shows potential to be a useful replacement for PI to PI over VPN

• 50% of Hess shares are not to/from PI System

• Hess will continue to use Industrial Evolution’s DaaSservices as an unbiased 3rd party go-between on matters of support, outages

• Pricing model matters

• PICC works as advertised• Speeds up DaaS deployment in an

“All PI System” environment• Limited testing on scalability due

to CTP restrictions


© Copyr i gh t 2014 O SIs o f t , LLC . 20

Presenter: Co-Presenter:

Tony Goodreau Simon [email protected] [email protected]

Tel: +1 (713) 609-4437 Tel: +1 (602) 867-0416

PI Global Administrator Founder & CEO

Hess Corporation Industrial Evolution

experience with pi cloud connect for jv data sharing with pi cloud connect for jv data sharing ......

Documents