metrics for simplifying and standardizing an enterprise
play

Metrics for Simplifying and Standardizing an Enterprise Architecture: - PowerPoint PPT Presentation

Metrics for Simplifying and Standardizing an Enterprise Architecture: An Experience Report from an Oil and Gas Organization Alexis Ocampo (Ecopetrol) Jens Heidrich (Fraunhofer IESE), Constanza Lampasona (Fraunhofer IESE), Victor Basili (University


  1. Metrics for Simplifying and Standardizing an Enterprise Architecture: An Experience Report from an Oil and Gas Organization Alexis Ocampo (Ecopetrol) Jens Heidrich (Fraunhofer IESE), Constanza Lampasona (Fraunhofer IESE), Victor Basili (University of Maryland, Fraunhofer CESE) SATURN 2014, Portland, USA May 7, 2014

  2. ECOPETROL S.A. – Oil and Gas Company 1st 1M Colombian Barrels 2015 Company Top 4th 40 Latin American Top World Oil and Gas Company Oil and Gas Companies How can IT contribute?

  3. Reliable and Secure Information in Real Time 1. Standardization and simplification of enterprise platforms 2. Consistent and complete information 24 hours 3. Timely information for taking business decisions 4. Confidential information treated like an asset 5. Information security and quality practices

  4. GQM+Strategies in Practice: Ecopetrol excerpt G1: Be positioned among the first XX companies by 20XX S1: Increase oil and gas reserves C1: In 20XX: Z A1: There are MMBOE reserves sufficient funds to and increase by Y do the exploration G2: Increase the oil and gas Business Level reserves by X MMBOE p.a. A5: Balanced portfolio leads to increased reserves S2: Achieve an effectively balanced exploration portfolio A2: If portfolio is A3: If portfolio is of good quality, of good quality, faster decisions decisions less risky G3: Decrease analysis time for finding reserves A4: Getting good data faster leads to better decisions S3: Improve information quality G4: Improve and maintain information quality IT Level S4.2: Develop / maintain / S4.3: Improve business S4.1: Improve internal data integrate applications that process definition and management for faster … provide high quality inf. information processing decision making G5: Improve and GQM maintain quality of applications (Quality Model) Source: Basili, Lampasona, Ocampo: Aligning Corporate and IT Goals and Strategies in the Oil and Gas Industry. PROFES 2013

  5. Quality Model Development Process • Survey • ISO25010 quality characteristics • Type of software • Programming languages • Areas addressed • On ‐ site workshop • GQM workshops • Final comprehensive quality model

  6. Survey Results Portability Performance Efficiency Security Usability Maintainability Reliability Functional Suitability Compatibility 0.00 1.00 2.00 3.00 4.00 5.00 6.00 7.00 8.00 9.00 less relevant more relevant

  7. Survey Results Which type of What are the primary Which areas are software do you programming addressed by your develop? languages? products? ABAP Embedded C++ systems Cobol ASP .Net 13% 12% 6% Business 20% 25% 4% information 8% C+# Upstream sys. 45% 7% Visual Basic Downstream 13% 21% Development Java Corporative tools 67% 30% 17% 8% Java Script 4% Platforms Oracle PHP Delphi

  8. On ‐ site Workshop • Survey provided little differentiation among quality attributes • Informally applied UMD approach and asked: What do you think it should not happen? What do you think it should not happen? What causes you the most problem? What causes you the most problem? • Result: list of issues that should be mitigated • From major issues quality goals were derived

  9. Quality Model Mapping to ISO 25010

  10. G7: Enterprise Architecture Coupling Provision and Consumption of Application Interfaces

  11. G7: Enterprise Architecture Coupling X • Base area equals # related information units Height equals the sum of used and • X provided interfaces, • Color equals status field of application X X X X

  12. G4: Design External Dependencies Application Coupling 16 14 12 10 8 6 4 2 0 APP 1 APP 2 APP 3 APP 4 APP 5 APP 6 APP 7 APP 8 APP 9 APP 10 APP 11 APP 12 APP 13 APP 14 APP 15 APP 16 APP 17 APP 18 Number of afferent applications (which deliver input through used interfaces) Number of efferent applications (which use output through provided interfaces)

  13. G4: Design External Dependencies Provided Interfaces not used by other Applications 35 30 25 20 15 10 5 0 APP 1 APP 2 APP 3 APP 4 APP 5 APP 6 APP 7 APP 8 APP 9 APP 10 APP 11 APP 12 APP 13 APP 14 APP 15 APP 16 APP 17 APP 18

  14. G3: Design Internal Dependencies Coupling Between Objects 160 140 120 100 80 60 40 20 0 APP 1 APP 2 APP 3 APP 4 APP 5 APP 6 APP 7 APP 8 APP 9 APP 10 APP 11 APP 12 APP 13 APP 14 APP 15 APP 16 APP 17 APP 18 1st Quartile 16.5 5 0 9 2 4 9 Min 3 0 0 2 1 2 5 Max 52 126 35 90 49 129 27 3rd Quartile 30 19 8 10 10 18 13.75 Median 23 9 2 9 5 7 12.5

  15. Deployment at ECP – Implications Lanscape view 2012 Logistics and Production Refining Transportation Chain Integrated Platform Management Exploration Marketing Industry Platforms Supply Finance Mixed Platforms (Third parties/ In ‐ house) Human Asset Resources Management Applications Redundancy Project Procurement HSE Management *** Información Restringida *** Comité Auditoria Junta Directiva, Marzo de 2013

  16. Deployment at ECP – Implications Lanscape view 2017 Logistics and Production Refining Transportation Chain Integrated Platform Management Exploration Marketing Supply Industry Platforms Finance Mixed Platforms (Third parties/ In ‐ house) Human Asset Resources Management Applications Redundancy Project Procurement HSE Management *** Información Restringida *** Comité Auditoria Junta Directiva, Marzo de 2013

  17. Deployment at ECP – Decreasing Interfaces 100% 92% 100% 98% 90% 77% 80% 88% 85% 70% 74% 60% 50% 40% 30% 20% 10% 0% 2012 2013 2014 2015 Baseline Real Plan *** Información Restringida *** Comité Auditoria Junta Directiva, Marzo de 2013

  18. Summary Standardization by identifying the major platforms and moving towards them (G7: EA coupling) Mesuring G4: Aplication coupling contributes to Simplification The Quality Model Provided the baseline for simplification and standardization goals Traditional models are not close to Real Issues therefore a different approach was used for generating the Quality Model Providers have to apply the model and comply with the baseline in order to be accepted

  19. Para uso restringido en Ecopetrol S.A. Todos los derechos reservados. Ninguna parte de esta presentación puede ser reproducida o utilizada en ninguna forma o por ningún medio sin permiso explícito de Ecopetrol S.A.

Recommend


More recommend