1 / 7

PRODML – A Vendor Viewpoint

PRODML – A Vendor Viewpoint. Patricia Yeska – TIBCO Software 6 November 2007. Agenda. Who we are Why is PRODML of interest to us What we did in the PRODML WorkGroup What have we learned. Integration requires a platform Rapid and Reliable Information Sharing

cargan
Télécharger la présentation

PRODML – A Vendor Viewpoint

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. PRODML – A Vendor Viewpoint Patricia Yeska – TIBCO Software 6 November 2007

  2. Agenda • Who we are • Why is PRODML of interest to us • What we did in the PRODML WorkGroup • What have we learned

  3. Integration requires a platform • Rapid and Reliable Information Sharing • Applications become “plug n’ play” • “Standards” ease data flows Spaghetti Integration Busters • Point-to-point connections: • Coding = High cost • Inhibit information sharing

  4. Why are we interested in PRODML • Upstream environments has been off limits to technology companies with a “standards” ethos • PRODML presents an opportunity to open the field to more technology choices Integration platform J2EE Ecosystem SAP Ecosystem .NET Ecosystem Web services Application 1 Application n Application 2

  5. Our Role in the PRODML WG07 React to Tank Level Change Based on Recommendation Filter active well list by Status And Block Valve Status Based on Recommendation Sort by BOPD (open) or WOR (SI) Solve for >= Recommendation (maximize oil producing) Orchestration 5 7 Notify InFusion 8 1 4 3 6 2 List of wells to open or close Well test Recommendation Active Well List Tank Level & Qout Status On/off Data Integration InFusion Wonder Ware LOWIS WPH Catalyst RMIS

  6. What have we learned? • Orchestration of Upstream processes can be configuration not code. • More efficient in high throughput environments • The PRODML is flexible • Allows adaptations for specific needs • We learned a lot about Upstream environments • Deployment is the “proof” • Though further enhancements are being planned, the schema can be deployed in it’s “as is” state.

  7. THANK YOU for your Attention

More Related