1 / 15

Standards for production allocation Improving IT/IM infrastructure decisions, 29 May 2013

Standards for production allocation Improving IT/IM infrastructure decisions, 29 May 2013. What is production allocation?.

soo
Télécharger la présentation

Standards for production allocation Improving IT/IM infrastructure decisions, 29 May 2013

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. Standards for production allocationImproving IT/IM infrastructure decisions, 29 May 2013

  2. What is production allocation? “The process by which measurements of commingled streams are related to multiple points of production, thereby supporting determination of ownership. Allocation may potentially involve oil, gas and water.”

  3. Integration challenges

  4. Cisco Global Cloud Index 2011-2016

  5. CERN releases web technology Java 1.0 RSS 0.9 First blog 1993 XML 1.0 XHTML 1.0, SOAP 1.1, REST (Fielding) Netscape founded Palm Pilot 1000 Facebook started Twitter founded, AWS launched 3m web sites 2003 1994 2002 2004 1995 2010 1999 1997 2006 2008 2009 1998 2007 2005 1996 2012 2000 2011 iPhone released, Linking Open Data Netscape disbanded WSDL 1.1 iPod YouTube founded Windows 7, Node.js Mobile Flash dead Web 20th anniversary 2013 2001 HTML5 LHC live, RDFa 1.0 iPad released, energysys.com

  6. The web as archetype: REST • Stateless • Uniform interface • Identification of resources • Manipulation of resources via representations • Self-descriptive messages • Hypermedia as the engine of state

  7. Standard needs • Process standards • Data standards (agreed content-type) • Service standards

  8. Markup soup

  9. PRODML: The Good • DTS measurement • Fluid analyses and samples • Flow networks • Production operations reports • Production reports • Historian data • Well tests • Wireline formation tests

  10. PRODML: The Bad • Implicit relationships • Lack of hyperlinks • Rigid structures

  11. PRODML: The Ugly • SOAP-based web service • GetData method • PutData method • DeleteData method • Service not discoverable • Data model not extensible • No URI for representations

  12. Imagine • GET https://live.energysys.com/123456 • Returns asset information • PUT https://live.energysys.com/123456 • Load data to the asset • PUT https://live.energysys.com/process/12224 • Load parameters for a process and run it • Return document is the URI for the executing process

  13. Imagine

  14. Our goal To be a first class participant in a RESTful service-oriented architecture

  15. Watch the video of Dr Peter Black delivering this presentation in Aberdeen: CLICK TO VIEW Questions? peter.black@energysys.com

More Related