BBMB Kewangan Berhad

Performance, Availability/Recovery and Support Recommendations

Presentation to EXCO 16 July 1997

BBMB KEWANGAN Bh

Agenda

• Performance Management Strategy • Availability/Recovery Strategy

— Interruption/Disaster Architecture — Contingency Planning Program — Emergency Operations Teams — Application Release Procedure — Other Availability Elements

• Help Desk Approach • Recommendations

Recommended Performance Management Strategy

Measure UNIX Host Production System Performance ON-LiNE PERFORMANCE - 95% in 3 seconds committed (Method: Insert time stamp into test transactions)

- Need 8 Transactions per Second -Committed 10 transactions per Second

BATCH PERFORMANCE (Method: Development System Drives Data into the Production System)

- Need & Committed End-of-Day in 5 Hours - Need & Committed End-of-Month in 7 Hours

Recommended Performance Management Strategy (Continued)

Measure Branch System Response Time- 95% in 2 seconds committed

(Method Insert time stamp into test transactions) Workstations will create transactions at maximum teller input rate

Measure Network Response Time - 95% in 2 seconds expected(Method: Insert time stamp into test transactions) High volume branches will create transactions at maximum branch system throughput

Responsibility for Performance Testing

• UNIX Host Production System - Executing - Monitoring and review

• Branch Systems

- Executing - Monitoring and review

• Network

- Executing - Monitoring and review

Sanchez & DECBBMBK

DECBBMBK

DEC & TelékomBBMBK

Recommended Availability/Recovery Strategy • Interruption/Disaster Recovery Program

- Architecture - Contingency Plunning Program (Disaster) - Restart Training (Interruptions)

• Hardware/Systems Software Program- Data Center Maintenance & Escalation - Branch Systems Maintenance & Escalation

• Application Architecture Program

- Application Release Procedure - Restart Training (Interruptions) - Application Architecture Review

Interruption/Disaster Architecture

ProductionSystem

D eve lopm en tand

M IS/D SS

H ot S iteBackupSystem

C old S iteEm ptySpace

In te rrup tionBackup

D isaste rBackup

R ecoverySpace

ProductionD ata Send to o ffs ite s to rage

O n line Log to Backup System

C om m erc ia l Backup C en te rBBM BK D a ta C en te r

Contingency Planning Program

• Backup Site Contract • Decision & Notification Procedure • Team Structure & Membership • Operational Testing • Management Simulation Exercises

T Y P IC A L IT C O N T IN G E N C Y P L A N N IN G T E A M S T R U C T U R E

C om m and C en te r Vendor H o t/C o ld S ite

PolicyTeam

BR PM anager

Adm in is tra tionTeam

D ata D is tribu tionTeam

Supp liesTeam

D am ageAssessm en t& R ecovery

Team

Log is ticsTeam

U serSupport

BR PO pera tions

M anager

App lica tionsTeam

O pera tionsTeam

D ata C ontro lTeam

N etw orkO pera tions

Team

SecurityTeam

System sTeam

O utpu tTeam

A pplica tion Change Contro l: Release M anagem ent

U sers P lann ing D eve lopm entQ ua lity

Assu ranceO pera tions

AccumulateRequirements

Define aRelease

Plan theRelease

Implement theRelease

CoordinateTesting of

Release

Source Code

Sourceand O bject

Code

Sourceand O bject

Code

AcceptanceTesting

O bjectCode

O bject Code

AcceptRelease

ProductionProcessing

Recommended Availability/Recovery Strategy (Continued)

Interruption/Disaster Recovery Program -Architecture - Contingency Planning Program (Disaster) - Restart Training

• Hardware/Systems Software Program-Data Center Maintenance & Escalation - Brunch Systems Maintenance & Escalation

• Application Architecture Program- Application Release System - Restart Training (Interruptions) - Application Architecture Review

Recommended Actions

1. Conduct Performance Testing

2. 2. Upgrade Development System

(needed for Phase 2 interruptions)

3 .Create Architecture Review Team

4. Implement Application Architecture Review

5. Implement Disaster Plan

6. Contract with Disaster Backup Center

7. Implement Application Change/Release Procedure

8. Implement Help Desk

WHEN

Phase 2 Rollout

Phase 2 Rollout

Phase 2 Design

Phase 2 Design

Phase 1 Rollout

Phase 1 Rollout

NOW

NOW