2. Information Technology Applications Architecture
kpmg 15/05/2002
Introduction
This document sets out the application architecture for the Bank resulting from the review of the IT Research
project. It covers the following two main systems:
Continued implementation of the CCBS system as a multi province and potential multi currency system. The
system is currently a single province application,
Implementation of a multi layered data warehousing solution to meet the Bank’s management information needs
Other systems have not been assessed alongside these because these represent the significant areas for change
in the Bank’s main application architecture. The architecture is represented as is today followed by an interim
development with the new core systems configuration and an initial implementation of the data warehousing
solution. The full architecture is represented by the core system supported by a full data warehousing
implementation. On each slide the light coloured systems are those that have been newly implemented at that
stage of development
In addition, a section ahs been included showing the main areas of an applications architecture which KPMG
would expect to see as a multi layered solution as is being proposed for the core banking reengineering. As part of
this we have included the main business rules around the interaction between such layers.
Preliminary Draft 2 China Construction Bank
3. Information Technology Applications Architecture
kpmg 15/05/2002
CCB’s Applications Architecture Transition
Preliminary Draft 3 China Construction Bank
4. Information Technology Applications Architecture
kpmg Current Architecture (Shanghai Province) 15/05/2002
Processing Management
Systems Information
External gateways and front ends Systems
Call centres
Centre Card organisations
Front end
Web Server database
Local Settlement
Local External gateways
systems Securities transfer
Province
information
Payments
Accounts
Customer
Security
Savings
Loans
Card organisations
Point Web Server
of sale
Automated
Local Settlement
teller machine
Local Point of sale Automated Counter Top
terminal teller machine Terminals
Preliminary Draft 4 China Construction Bank
5. Information Technology Applications Architecture
kpmg Interim Architecture 15/05/2002
Processing Management
Systems Information
External gateways and front ends Systems
On line
Analytical
Call centres Processing
information
Centre
Payments
Accounts
Customer
Security
Savings
Loans
Card organisations Head Office
CCBS Front end line of
database Web Server database
business
Local Settlement data mart
On line On line
Big Front End Analytical Analytical
Processing Processing
Local SNA Communications External gateways
systems Securities transfer
Province Data formatting Line of Line of
Card organisations business business
Point Transaction transfer Web Server data data
of sale marts marts
Automated
Local Settlement
teller machine
Province Front end
based
data database
extraction
Local Point of sale Automated Small Front In the interim management information is provided
Province
terminal teller machine End based either within a province or at province and Head
data
extraction Office for one line of business
Counter Top
Terminals
Preliminary Draft 5 China Construction Bank
6. Information Technology Applications Architecture
kpmg Full Architecture 15/05/2002
Processing Management
Systems Information
External gateways and front ends Systems
On line On line
Analytical Analytical
Centre Call centres Processing Processing
information
Payments
Accounts
Customer
Security
Savings
Loans
Card organisations Summary Head Office
CCBS Front end Head Office line of
database Web Server database
data mart business
Local Settlement data mart
On line On line
Big Front End Analytical Analytical
Processing Processing
Local SNA Communications External gateways
Province systems Securities transfer
Data formatting Line of Line of
Card organisations business business
Point Transaction transfer Web Server data data
of sale marts marts
Automated
Local Settlement
teller machine
Province Front end
based
data database
extraction
Local Management information is either grouped by
Point of sale Automated Small Front
terminal teller machine End Province province and then consolidated into one head office
based
data system or by line of business and consolidated by
extraction
line of business at Head Office. Both options are
Counter Top
Terminals shown here
Preliminary Draft 6 China Construction Bank
7. Information Technology Applications Architecture
kpmg 15/05/2002
Applications architecture
-
Locations
Preliminary Draft 7 China Construction Bank
8. Information Technology Applications Architecture
kpmg 15/05/2002
The best practice applications architecture will have the layers located as
follows
Channel Layer
(central or distributed)
Channel Management Layer
(central or distributed)
Operational Partner
Customer Management
Management Systems
(central) (central)
Business Integration Layer (central)
Customer Production Engine Layer (central)
Enterprise
Analytics Management
Marketing & MIS Systems (central)
(central)
Mailing & Payment Gateways (central)
Preliminary Draft 8 China Construction Bank
9. Information Technology Applications Architecture
kpmg 15/05/2002
CCB’s current practice applications architecture has the layers located as
follows
Channel Layer
(distributed)
Channel Management Layer
(distributed at province level)
Operational Partner
Customer Management
Management Systems
(distributed (does not exist)
where it exists) Business Integration Layer
(does not exist)
Customer Production Engine Layer
(distributed at province and City level) Enterprise
Analytics Management
Marketing & MIS Systems
(does not exist)
(distributed
Mailing & Payment Gateways (distributed) and central)
Preliminary Draft 9 China Construction Bank
10. Information Technology Applications Architecture
kpmg 15/05/2002
CCB’s likley applications architecture will have the layers located as follows
Channel Layer
(central or distributed)
Channel Management Layer
(distributed at province level)
Operational Partner
Customer Management
Management Systems
(central) (not needed in
Business Integration Layer the short to
(distributed at province level) medium term)
Customer Production Engine Layer
(central and distributed) Enterprise
Analytics Management
Marketing & MIS Systems (central)
(central)
Mailing & Payment Gateways (central)
Preliminary Draft 10 China Construction Bank
11. Information Technology Applications Architecture
kpmg 15/05/2002
Applications architecture
-
Rules for managing the application layers
Preliminary Draft 11 China Construction Bank
12. Information Technology Applications Architecture
kpmg 15/05/2002
From an applications architecture perspective the architecture is
divided into layers ….
Channel Layer
Channel Management Layer
Operational Partner
Customer Management
Management Systems
Business Integration Layer
Customer Production Engine Layer
Enterprise
Analytics Management
Marketing & MIS Systems
Mailing & Payment Gateways
Preliminary Draft 12 China Construction Bank
13. Information Technology Applications Architecture
kpmg 15/05/2002
The application layers can then be exploded to show application components...
Channels
(- eg, PDA, Kiosk)
ACD
PC Propriety
WAP Phone
Trad ATM
PC OFX
Postal
Internet
E-mail
Outlet
Retail
Branch
Other
Fax
I-TV
Script
Video
AVR
IVR
CTI
e - channels Call Centre Supporting Channels High Street
High Street
Channel Management Partner Management Systems
Operational Customer
Management
Presentation Distribution Channel Integration
Content
Repository Admin.
Contact Customer Web Page Design Personalisation Content Management
Management Authentication
Finance.
Customer Interaction Layer
Risk Relationship Relation.
Workflow
Management Management Partner
Service Management Fulfilment Management Complaints Management Sales Support
Data
Customer Treatment Brand
Applications Capture Quotations Recommendations M.I. & B.I.S.
Profile Strategies
Common Processes
Business
Business Integration Layer Risk
Operational
Customer Database Rules Data Data Data
Messaging Security FTP Workflow Transformation Directory Services
Engine Aggregation Splitting
Message Audit Invocation of Look-up Directory
Flow Queuing Directory Services
Prioritisation
RT/batch functs.
Repair Trail Control Tables Services
Enterprise Management Risk
Customer Analytics Systems Management
Marketing & MIS
Product Bundling and Branding
Regulatory
Campaign Personalisation Banking Engines Reporting
Management Development Other FS Engines
Treasury
Current General Life
Credit Ref./ Loans
Accounts Insurance Insurance Transaction
Scorecard GL
Householding Cross-Selling Account Reconciliation
Data Credit Wealth Retail
Deposits Collections
Cards Management Brokerage Corporate
Arrears Mgt.
Customer Data
Behavioural Applications HR/Payroll Accounts
Value Fraud Mortgages FX/Travel
Analysis Leasing Payable
Analysis Detection Cheques
Suppliers
Analytic Databases
Credit Reference Card Mailing & Payment Gateways HPI 3rd party
Commission Purchase
Bureau Production debt collection
Management Ordering Fixed
Finance Customer Product Channel Assets
CHAPS euro Cheque
BACS SET Switch Swift
EBA Clearing
CHAPS Stock
Detail e-purchasing Internet
Control
Data Remittance AUDDIS/ Cheque Mailing Fulfilment Statementing
Processing ADDACS Production
Other
Banks
Preliminary Draft 13 China Construction Bank
14. Information Technology Applications Architecture
kpmg 15/05/2002
Channel to Channel Management layer
Interaction Rules
• Channel systems send enquiries and
transactions only to specified systems in
Channel Layer the channel management layer
• Channel systems have a valid subset of
business transaction types which they can
deal with e.g. internet channels cannot deal
with notes and coins
• A subset of customer and account
Channel Management Layer enquiries are valid for each channel layer
Operational Partner system e.g. ATMs cannot enquire directly
Customer Management on customer records
Management Systems
Business Integration Layer
Customer Production Engine Layer
Enterprise
Analytics Management
Marketing & MIS Systems
Mailing & Payment Gateways
Preliminary Draft 14 China Construction Bank
15. Information Technology Applications Architecture
kpmg 15/05/2002
Channel Management to Business Integration Layer
Interaction rules
• All transactions pass through a switch between
the layers
Channel Layer • All transactions have the following stamped on
them:
•Time
•Date
•Source system
•Target system
Channel Management Layer •Processing priority, e.g. interactive,
Operational Partner
request, memo posting, batch
Customer Management •Valid security access to create, read,
Management Systems update and delete
• All transactions have business rules applied in
Business Integration Layer this layer for the following:
•Categorisation for information retrieval
e.g. customer type, product type, channel
type, time period,geographical source
•Supplementary data to be added to the
transaction depending on the transaction
Customer Production Engine Layer type
Enterprise •Rules to be applied to the transaction to
Analytics Management create aggregated totals for further
Marketing & MIS analysis
Systems • Transaction record is complete with the
following action:
Mailing & Payment Gateways •If yes which system to pass it to
•If no which system to pass it back to or
what repair algorithms to apply
Preliminary Draft 15 China Construction Bank
16. Information Technology Applications Architecture
kpmg 15/05/2002
Operational Customer Management to Business Integration Layer
Interaction rules:
• All customer related transactions passed to
Operational Customer Management
Channel Layer • Customer authentication requested directed to
Customer Authentication
• All customer transactions update Operational
Customer Database
• Operational Customer Database (OCD))
updates other systems in Operational
Channel Management Layer Customer Management depending on
Operational Partner predefined rules held in the OCD
Customer Management
Management Systems
Business Integration Layer
Customer Production Engine Layer
Enterprise
Analytics Management
Marketing & MIS Systems
Mailing & Payment Gateways
Preliminary Draft 16 China Construction Bank
17. Information Technology Applications Architecture
kpmg 15/05/2002
Business Integration to Customer Analytics Marketing & MIS layer
Interaction rules:
• All customer related transactions
passed to Detail Database
• All customer transactions update
Channel Layer Detail Database in
•summary customer record or
•individual customer record
•both
• Customer Analytics Marketing & MIS
sends outbound transaction to
Channel Management Layer Business Integration Layer driven by
Operational Partner predefined prompts held in each
Customer Management system in that area. Target system
details for that type of transaction are
Management Systems held in the Business Integration layer
Business Integration Layer
Customer
Analytics Production Engine Layer
Marketing & MIS Enterprise
Management
Systems
Mailing & Payment Gateways
Preliminary Draft 17 China Construction Bank
18. Information Technology Applications Architecture
kpmg 15/05/2002
Business Integration to Production Engine layer
Interaction rules:
• Business Integration Layer directs
inbound transaction to relevant
product system in the Production
Channel Layer Engine Layer driven by predefined
look up table. The rules for this will
be driven by:
•Valid transaction type
•Time of day, (production
Channel Management Layer engine systems may be
Operational Partner running batch updates and the
Management rule will switch to a shadow
Customer data file not the main
Management Systems transactional file
• Business Integration layer will store
Business Integration Layer a record of the transaction to match
to the response transaction to
ensure that a reply is received and
processed
• changes to customer records held
in the Production Engine Layer can
Customer Production Engine Layer only be done via the Business
Enterprise Integration Layer thus maintaining
Analytics Management a record of inbound transaction
Marketing & MIS Systems
updates only, no direct update of
accounts is valid
Mailing & Payment Gateways
Preliminary Draft 18 China Construction Bank
19. Information Technology Applications Architecture
kpmg 15/05/2002
Production Engine Layer to Mailing & Payments Gateways
Interaction rule:
• Valid transaction types generate a subset of
payment types or other types of transaction
Channel Layer driven by a look up table e. g. a domestic
payment will not be valid for a SWIFT
transaction or a payment below a specified
amount will not be valid for a real time gross
settlement system
• Payment messages will require and
Channel Management Layer authentication message before Production
Operational Partner Engine Layer systems are updated with the
Customer Management transaction
• Payment messages will update different
Management Systems balances e. g. cleared or uncleared
depending on the payment type
Business Integration Layer • Incomplete inbound payment messages held
in suspense accounts in the Mailing &
Payment Gateway before manual
intervention
• changes to customer or third party payment
records held in the Mailing & Payments
Customer Production Engine Layer Gateway can only be done via the
Enterprise Production Engine ion Layer thus
Analytics Management maintaining a record of inbound transaction
Marketing & MIS Systems updates only, no direct update of records is
valid
Mailing & Payment Gateways
Preliminary Draft 19 China Construction Bank
20. Information Technology Applications Architecture
kpmg 15/05/2002
Business Integration Layer to Partner Management Systems
Interaction rules:
• Certain transaction will known to be
third party sourced system transactions
Channel Layer from transaction tables held in the
Business Integration Layer
• In and outbound transactions between
layers will generate or receive receipt
messages depending on
•the transaction value or
Channel Management Layer •The transaction amount
Operational Partner In either
Customer Management •In real time
Management Systems •As part of a periodic batch
update
Business Integration Layer • Firewall principles apply for invalid or
incomplete messages
• changes to customer or third party
records held in the Partner
Management Systems can only be
done via the Business Integration
Customer Production Engine Layer Layer thus maintaining a record of
Enterprise inbound transaction updates only, no
Analytics Management direct update of accounts is valid
Marketing & MIS Systems
Mailing & Payment Gateways
Preliminary Draft 20 China Construction Bank
21. Information Technology Applications Architecture
kpmg 15/05/2002
Business Integration layer to Enterprise Management Systems
Interaction rules:
• A subset of transaction (i.e. financial
transactions and transactions which update
Channel Layer management reports) will be passed from the
Business Integration Layer to the Enterprise
Management layer
• Control totals will be created for sent and
received transactions to valid receipt.
• Transaction flow is one way i.e to Enterprise
Channel Management Layer Management only except for payroll which roots
Operational Partner via the Production Engine to the Payment
Customer Management Gateway or updates Production Engine
customer accounts
Management Systems • changes to account records held in the
Business Integration Layer Enterprise Management Systems can only be
done via the Business Integration Layer thus
maintaining a record of inbound transaction
updates only, no direct update of accounts is
valid
Customer Production Engine Layer
Enterprise
Analytics Management
Marketing & MIS Systems
Mailing & Payment Gateways
Preliminary Draft 21 China Construction Bank
