190 likes | 259 Views
ORDINA. Gastcollege Nijmegen. 8 juni 2005. AGENDA. Introduction Ordina Business case Architecture Technology Lessons learnt Today / Tomorrow Conclusions. Introduction. Aarnoud Hoekstra Ordina SI&D Technology Consulting Background: Computer Science Twente Applied Physics Delft
E N D
ORDINA Gastcollege Nijmegen 8 juni 2005
AGENDA • Introduction • Ordina • Business case • Architecture • Technology • Lessons learnt • Today / Tomorrow • Conclusions
Introduction • Aarnoud HoekstraOrdina SI&D Technology Consulting • Background:Computer Science TwenteApplied Physics Delft • EAI main interest area
Ordina • 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
Business case (I) • 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 (II) • Requirement to be able to manage documentation due to: • Size of projects, amount of documentation • Legal requirements • Harmonization • Maintenance • Electronic documentation
Business case (III) • 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
Architecture (I) • 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 (II) SAP GUI Navigator Viewer WEB Server CORBA interface Integration Layer SAP Oracle DMS
Technology (I) • 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 (II) • Technology used (cont’d): • C(++) code • VB code • ABAP / SAP RFC • Stored procedures • Workflow (Staffware) procedures
Lessons learnt (I) • Current status: • 4000 registered users • 200 concurrent users per country • 4 countries, 9 sites • 1 server per country (12 integration layers)
Lessons learnt (II) • Business perspective: • Hard to define clear requirements • Scope mangling • Acceptance is difficult • Business is not IT oriented
Lessons learnt (III) • 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 (IV) • 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
Today / Tomorrow (I) • Hype or not? • Service Oriented Architectures • SOAP • Enterprise Service Bus • Business Activity Monitoring
Today / Tomorrow (II) • Definitely a paradigm shift • No longer data orientation • No IT push • Business drives IT • Process orientation • Optimizing the business processes
Conclusions • VRAGEN ?