1. ORDINA NV Ringwade 1 3439 LM Nieuwegein Tel: 030 6637000 Fax: 030 6637099 www.ordina.nl e-mail: info@ordina.nl e y on d B t h e o rd ina r y Gastcollege Nijmegen 8 juni 2005 ORDINA

2. eyondBtheordinary 2 Introduction Ordina Business case Architecture Technology Lessons learnt Today / Tomorrow Conclusions AGENDA

3. eyondBtheordinary 3 Aarnoud Hoekstra Ordina SI&D Technology Consulting Background: Computer Science Twente Applied Physics Delft EAI main interest area Introduction

4. eyondBtheordinary 4 Approx. 3600 employees Annual turnover EUR 383 million Known recently due to Pink Roccade bid Consultancy, project management, design, implementation and run&maintain http://www.ordina.nl http://www.mijnnaamisjob.nl Ordina

5. eyondBtheordinary 5 European implementation of SAP (mid 1990’s) Centralisation of systems Standardization of procedures (ways of working) Best in class Cost reduction due to efficient management of assets Business case (I)

6. eyondBtheordinary 6 Requirement to be able to manage documentation due to: –Size of projects, amount of documentation –Legal requirements –Harmonization –Maintenance –Electronic documentation Business case (II)

7. eyondBtheordinary 7 Asset Information Management: –Controlled update of asset information –Controlled update of document information –Exchange of information with 3rd parties –Easy access (Navigator) –Document management facilities –Generic document viewing Business case (III)

8. eyondBtheordinary 8 Classical hub and spoke architecture Tailor made software (those were the days) Client – server approach Scalable (processes and/or servers) Secure (encryption used where needed) Single logon Architecture (I)

9. eyondBtheordinary 9 Architecture (II) Navigator SAP GUI Viewer WEB Server CORBA interface Integration Layer Oracle DMS SAP

10. eyondBtheordinary 10 Technology used: –HTTP plain text with webservices –CORBA interfaces –Native application interfaces (SP, RFC, DMS) –HTML / SGML –Plug ins for desktop applications –Tailor made workflow mechanism Technology (I)

11. eyondBtheordinary 11 Technology used (cont’d): –C(++) code –VB code –ABAP / SAP RFC –Stored procedures –Workflow (Staffware) procedures Technology (II)

12. eyondBtheordinary 12 Current status: –4000 registered users –200 concurrent users per country –4 countries, 9 sites –1 server per country (12 integration layers) Lessons learnt (I)

13. eyondBtheordinary 13 Business perspective: –Hard to define clear requirements –Scope mangling –Acceptance is difficult –Business is not IT oriented Lessons learnt (II)

14. eyondBtheordinary 14 IT (development) perspective: –Large teams are hard to manage –“Island” thinking –Not enough business knowledge –State-of-the art is nice but …. –Tailor made software is a great challenge Lessons learnt (III)

15. eyondBtheordinary 15 Delivery of the system is just a start Takes a few years to get a stable system –System was rolled out in 1999 and is stable since 2002 Business finds it hard to accept new systems and new procedures –Awareness –Training –Governing expectations Lessons learnt (IV)

16. eyondBtheordinary 16 Lessons learnt (V)

17. eyondBtheordinary 17 Hype or not? Service Oriented Architectures SOAP Enterprise Service Bus Business Activity Monitoring Today / Tomorrow (I)

18. eyondBtheordinary 18 Definitely a paradigm shift No longer data orientation No IT push Business drives IT Process orientation Optimizing the business processes Today / Tomorrow (II)

19. eyondBtheordinary 19 VRAGEN ? Conclusions