70 likes | 424 Views
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
E N D
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 • Applications become “plug n’ play” • “Standards” ease data flows Spaghetti Integration Busters • Point-to-point connections: • Coding = High cost • Inhibit information sharing
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
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
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.