Application CCM: A Customer Experience Session Software Logistics Approach at ABN AMRO

Transcription

1 Application CCM: A Customer Experience Session 8407 Software Logistics Approach at ABN AMRO Jan Boef Wednesday, July 25 4:30pm Minneapolis Convention Center Second Level Room 211B SHARE Session 8407 July 25, 2001

2 ABN AMRO Bank Ranked as Europe s 5 large bank and 16 largest of the world Total assets Euro 533 bn approx branches employees Headoffice in Amsterdam, the Netherlands over people in ICT SHARE Session 8407 July 25, 2001

3 Speaker info Jan Boef 29 years in ICT Experience in evelopment and Operations Solution Integrator with ICT as business Area s: Software Logistics Migration and maintenance SHARE Session 8407 July 25, 2001

4 Concept of software logistics Information Warehouse Req esign Coding UT/UIT ST Acc PR WH

5 The CHIPS-model Order A B C Customer elivery Assembly Construction esign Purchasing Product Warehouse Internal Part Stock Specifications

6 product management Product &- part - design Product & part definitions Productwishes Market trends development management development purchase part checking maintentance Problem reports Software Parts Warehouse release management Release assembly Release checking Software Products Repository System configurations Configuration management Configuration checking istribution SHARE Session 8407 July 25, 2001 Installation Support & monitoring

7 Migration plan Start situation A S Tools OVS HOS???

8 Migration plan A S Tools OVS HOS 1 ARTIS Audit??? Repository

9 Migration plan A S Tools OVS ISPW 2 HOS 1 ARTIS??? Repository

10 Migration plan A S ISPW 2 HOS 3 1 ARTIS Repository

11 Migration plan ev. Tools 4 4 A S ISPW 2 HOS ARTIS Repository

12 Migration plan ev. Tools 4 4 A S 5 ISPW 2 HOS ARTIS Repository

13 Status today ISPW fully implemented for MVS Migration in 5 weekends 750 developers and supporters use ISPW components in ISPW, with versions in 30 lpars 80 componenttypes defined 390 applications SHARE Session 8407 July 25, 2001

14 Benefits of ISPW 1 OVERVIEW Which components belong to an application Which ones are in development/test Which versions exist and what is their status Who did what with a component What is the content of a release Which components of an assignment are completed Which troubleshootversions are in production...

15 Benefits of ISPW 2 SURENESS Feedback on distribution of a component Only one active version on a level Parallel development/implementation supported Formal process for troubleshoot QA processes standardized Controlled generation Negative handover with consistency Clean up of components that do not reach production istribution per release SHARE Session 8407 July 25, 2001

16 Benefits of ISPW 3 SPEE istribution per release/set Administration is always reflecting reality Realtime processing in distribution Scheduling for implementation in production Easy to learn Easy to take over activities... Logistics delay reduced from weeks to days

17 The way forward Evaluation of the migration plan: ISPW BenchMark is developing functionality for multi-platform release management Our repository solution appears to be endof-life Hyperlinks and data warehousing techniques are available for our Information Warehouse SHARE Session 8407 July 25, 2001

18 Next steps Extending release management Impact analysis Integrated systems documentation Automated transformations

19 Release management istribution under control of ISPW Activation under control of ISPW Enhanced fallback possibilities Also for non-mvs target platforms 7x24 hours support Integration with non-mvs development Enhanced audit possibilities SHARE Session 8407 July 25, 2001

20 Impact analysis Which information is needed for which ICT activity and why Which approval procedures are necessary and why How to cope with changes in services that are used in many applications Leads to requirements for systems documentation SHARE Session 8407 July 25, 2001

21 Systems documentation Which documentation is really needed When is it needed Which documentation can be generated Integrated QA for documentation in the logistics process Status of documentation connected to status of application Presentation through intranet SHARE Session 8407 July 25, 2001

22 Automated transformation Programming languages are formal languages For JCL we are doing this already for many years Y2K was very expensive A lot of testing is wasted time We can do far better SHARE Session 8407 July 25, 2001

23 We are just at the beginning of our job. The current implementation of ISPW is a solid basis

24 We want to compete in etime with business strength solutions

25 The end