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

(1)

Software Logistics at ABN AMRO Bank

Application CCM: A Customer Experience

Session 8407

Software Logistics Approach at ABN AMRO

Jan Boef

Wednesday, July 25 2001 @ 4:30pm

(2)

ABN AMRO Bank

• Ranked as Europe’s 5 large bank and 16 largest of the world

• Total assets Euro 533 bn • approx. 3500 branches • 110.000 employees

• Headoffice in Amsterdam, the Netherlands • over 10.000 people in ICT

(3)

Speaker info

• Jan Boef

• 29 years in ICT

• Experience in Development and Operations

• Solution Integrator with ICT as business • Area’s: Software Logistics

(4)

Software Logistics at ABN AMRO Bank Concept of software logistics

ST Acc PR DWH Req Design Coding UT/UIT Information Warehouse

(5)

Software Logistics at ABN AMRO Bank Delivery C u s to m e r Assembly A B C Design Product Warehouse Purchasing Specifications D Construction Order Internal Part Stock The CHIPS-model

(6)

Software Logistics at ABN AMRO Bank development maintentance part checking Release assembly Release checking Configuration checking Distribution Installation Software Parts Warehouse Software Products Repository Support & monitoring dev el opm ent m anagem ent rel eas e m anagem ent Conf igur at io n m anagem ent Problem reports Product &-part -design Product & part definitions Productwishes Market trends System configurations prod uc t m anagem ent purchase

(7)

Migration plan Start situation

A D D S Tools OVS HOS ???

(8)

Software Logistics at ABN AMRO Bank Migration plan A D D S Tools OVS HOS ??? Audit _Repository ARTIS 1

(9)

Software Logistics at ABN AMRO Bank Migration plan A D D S Tools OVS HOS ??? Repository ARTIS ISPW 2 1

(10)

Software Logistics at ABN AMRO Bank Migration plan A D D S _HOS Repository ARTIS ISPW 2 1 3

(11)

Software Logistics at ABN AMRO Bank Migration plan A D D S _HOS Repository ARTIS ISPW 2 1 3 Dev. Tools 4 ₄ 3

(12)

Software Logistics at ABN AMRO Bank Migration plan A D D S _HOS Repository ARTIS ISPW 2 1 3 Dev. Tools 4 ₄ 3 5

(13)

Status today

• ISPW fully implemented for MVS • Migration in 5 weekends

• 750 developers and supporters use ISPW • 400.000 components in ISPW, with

versions in 30 lpars

• 80 componenttypes defined • 390 applications

(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

(16)

Benefits of ISPW

3 SPEED

• Distribution 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 • ……...

(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 end-of-life

• Hyperlinks and data warehousing

(18)

Next steps

• Extending release management • Impact analysis

• Integrated systems documentation • Automated transformations

(19)

Release management

• Distribution 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

(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

(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

(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

(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

(25)