Migration of Application Portfolio platforms in Statoil

2. Migration of Application Portfolio platforms in Statoil QualiWare Spring Conference 2007 Harald Wesenberg Discipline Adviser Enterprise Architecture Corporate Staff Information Management and Technology

3. Topics • The history of QLM in Statoil • QLM in context • Achievements so far • Application Migration • The road ahead

4. This is Statoil • The world’s 3rd largest net seller of crude oil with 1.2 million bbls o.e. per day • 25,000 employees and 10,000 contractors • Offices in 33 countries • Annual revenue of $61 billion • Scandinavias largest corporation, 70th in Fortune Global 500

5. QLM was chosen as our corporate business modelling tool in May 2003 • In 2002 the needs were specified and pilot tests and customer projects at NTNU were used to investigate different tools • Early 2003 the procurement process started and ended in a contract with Qualisoft • Functional and commercial evaluations • Local support • 2H2003 were used to establish overall processes and IT application portfolio in QLM

6. Major uses of the BPM model today Application portfolio management Internal controls SOX 404 compliance Process and information modelling Publish to DocMap

7. QLM in Context • QLM is important in three major areas • Management System • Application Portfolio Management • (Enterprise Architecture) • The importance of QLM is growing • Management system • ICT investment management • Complience management

8. Achievements with QLM so far • All business processes modeled in QLM and published to BPM • Not all work flows • Including SOX Key Controls • Full control of roles (bla bla bla) • All information systems and ICT technologies registered in QLM and published to BPM • Including life cycle state • Link to processes • Information usage and information flow modeled for some process areas

9. Application Portfolio Migration • Statoil is facing a migration of several large application portfolios over the nest 3-5 years • Natural Gas trading, scheduling and operation • Oil and refinery products trading, scheduling and operation • SAP R/3 migration to ERP 2005 • In total, these are 500.000+ man hour efforts • QLM as our process model repository is used whenever possible • Recognize the need for Enterprise Architecture and EA tool support • Today this is done in Microsoft Office – not good enough

10. Use of QLM EA to support Application Portfolio Migration • QLM is planned used for modeling in several perspectives • Processes, Events, Information, Services, Solution, (Strategy) • QLM is planned used for modeling in several perspectives • Processes, Events, Information, Services, Solution, (Strategy) • We are planning to use the basic QualiSoft EA framework with Statoil extensions • Service perspective must be determined • Current models (information, solution) in MS Office will be transferred and linked to current models in QLM

11. The road ahead with QLM • Current plans • ”Processes to the masses” • Processes made available to all employees and contractors • Roles and relevant competencies matched to positions and organization • Implement QualiWare Enterprise Integrator and EA metamodel • Introduce the discipline of Enterprise Architecture to more business areas in Statoil • Working towards process owners and BA CIOs • From Business Process Modelling to Business Process Management

12. Challenges with our use of QLM • Different target groups requires flexibility and integration • Availability and usability outside desktop environment for multinational blue collar workforce • Online analytics for business and ICT development • Information modelling • One large model or different models for each process domain • Service modelling • How do we represent business and application services and achieve reuse • Make service catalogue available to stakeholders • Business Process Management • How to do this? None of these are unsurmountable, but requires political skill and a good process with business and line management involvement

13. Questions?

15. The targeted software architecture Characteristics: • Service oriented • Loose coupling • Improved interoperability • Improved maintainability • Standardized semantic • Layered • Clear responsibility • Event driven • Addresses the event driven nature of reality • Focus on process execution • Domain centric • Complexity of business in focus

16. Enterprise Architecture and SJEF Concepts Enterprise Architecture • Business process definitions • Information concepts • Business Functions (services) Context Map • A map of modelling contexts and their relationships. • Should reflect the existing situation in the landscape it maps. • A key tool to identify misfits and analyse strategies for dealing with misfits Landscape • A map of information systems and their relationships • Information systems are physical placeholders of modelling contexts, typically aggregated • Should be developed along the principle of evolving order

17. SJEF Architecture – Large Scale Structures Landscape • A set of information systems that supports one of Statoil’s main business processes. I.e. Wet Supply Chain, Gas Sales & Supply. Information System • Autonomous deployable unit that fulfils a role in a landscape. Can be custom made or package. • Supports one or more sub-processes. Subsystem • Cohesive building blocks from which information systems are built. Service • A defined business function exposed by a information system / subsystem for others to use. Module • The smallest building blocks a subsystem is built from, mirrors the package / namespace concepts of programming languages Information Systems, Sub-systems and Services are defined and derived from the Enterprise Architecture