1 / 19

Business Transformation and Technology Evolution: Lessons Learned and Future Strategies

Explore the business cases, architecture, technology, and valuable lessons learned from Ordina's implementations, alongside insights for today and tomorrow in this engaging session. Learn more at the Ordina Gastcollege in Nijmegen on June 8, 2005.

justine-chen
Download Presentation

Business Transformation and Technology Evolution: Lessons Learned and Future Strategies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ORDINA Gastcollege Nijmegen 8 juni 2005

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

  3. Introduction • Aarnoud HoekstraOrdina SI&D Technology Consulting • Background:Computer Science TwenteApplied Physics Delft • EAI main interest area

  4. 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

  5. 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

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

  7. 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

  8. 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

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

  10. 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

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

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

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

  14. 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

  15. 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

  16. Lessons learnt (V)

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

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

  19. Conclusions • VRAGEN ?

More Related