Integrated Financial Management System IFMS Architecture Overview

1
Integrated Financial Management System
(IFMS)Architecture Overview

• Nagalin Tuganadar
• 17th June 2008

2
Agenda

• Objectives of the Architecture
• IFMS Architecture Framework
• IFMS Conceptual Solution Architecture
• IFMS Functional Scope
• Technology Architecture
• Integration Architecture
• Security Architecture
• Data Architecture
• Software Engineering Landscape
• Challenges

3
Objectives of the Architecture

• Provide the principles that guide the governance
  and design of the Architecture
• Provide the city planning scope of the
  Functional architecture with reference to the
  URS, best practice and legacy systems
• Provide the IFMS Conceptual Solution
  Architecture
• Produce Architecture Framework for evolving from
  concept to physical
• Produce a Service Reference Model (SRM) that
  clearly indicates and classifies the different
  services domains and types according to their
  support of IFMS business, functional and
  performance objectives
• Provide a Roadmap and Release Plan
• Provide a Architectural Governance Model and
• Provide a Implementation Model.

4
Collaborative IFMS Architecture Framework
5
Line of Sight Reference Models
6
IFMS Conceptual Solution Architecture
7
(No Transcript)
8
TECHNOLOGY ARCHITECTURE
SECURITY
HOSTING
NETWORKS
INTERNAL EMPLOYEE
INTERNET USER
EXTERNAL SYSTEM
IDENTIFI- CATION
CONNEC- TIVITY SERVERS
LAN
USER
AUTHENTI- CATION
APPLICATION SERVERS
NGN/ GCCN
PC
MOBILE
TELEPHONE
PIT (kiosk)
OTHER BCR HHDs
DEVICES
AUTHORI- ZATION
DATABASE SERVERS
VPN
INTRANET
INTERNET
MESSAGING

• OTHER
• SMS
• FAX
• E MAIL

CHANNEL
AUDIT
SECURITY SERVERS
GLOBAL DMZ
PORTAL
GATEWAY
INTEGRITY
STORAGE MAN.
NETWORK MAN.
APPLICATION PRESENTATION
APPLICATION CLIENT
WEB PAGE
SECURITY MAN.
ARCHIVING
DISASTER RECOVERY
INTEGRATION SERVICES
SOA APPLICATION DELIVERY
DISASTER RECOVERY
BESPOKE IFMS
COTS
BI
MASTER DATA
UTILITY APPS
ADMIN MAN.
OLTP
ODS
WAREHOUSE
EXTERNAL INTERFACE STAGING
OTHER - META - DIR
DATA MANAGEMENT
DATA MANAGEMENT
9
Expanding into e-Government
Application service
10
(No Transcript)
11
Integration with other Environments
Service Discovery
Request / Response
Request / Response
Service Discovery
12
SOA Security
13
IFMS Data Architecture
14
Software Engineering Landscape
15
Challenges

• Managing the phasing out of a 25 Year Legacy
  within 140 departments in 10 years
• Governance
• Ensuring that the minimum of all current common
  IFMS government transversal systems business
  rules are included with IFMS
• Managing different multi-department
  implementation variants
• Defining multiple system user interfaces
• Performance Management
• Master Data Management
• Skills Shortage

THANK YOU