ENTERPRISE ARCHITECTURE

1

• ENTERPRISE ARCHITECTURE

Randeep Sudan, GICT
Hanoi December 14, 2006
2
Winchester Mystery House
3
Winchester Mystery House

• House without an architect
• Located in San Jose, California
• Built by Sarah Winchester between 1884 and 1922
• 160 rooms, 40 bedrooms, 10,000 windows
• Rooms around rooms
• 65 doors to blank walls
• 24 skylights in floors
• 13 staircases go nowhere

4
What is Enterprise Architecture?

• Enterprise Architecture can be thought of as a
  whole of government blueprint and roadmap to
  guide how information systems and technologies
  are able to support the achievement of the
  Governments Outcomes.
  Enterprise Architecture Final Report, June 2004
  Tasmania.

5
Gartner on Enterprise ArchitectureSource
Enterprise Architecture Research Agenda, 2006

• Enterprise architecture is the process of
  describing, and the description of, the desired
  future state of an organizations business
  process, technology and information to best
  support the organizations business strategy.
• Blueprint
• The definition of the steps required, and the
  standards and guidelines to get from the current
  state to the desired future state.
• Roadmap

6
Why Enterprise Architecture?

• investing in IT without defining these
  investments in the context of an architecture
  often results in systems that are duplicative,
  not well integrated, and unnecessarily costly to
  maintain and interface.
• US General Accounting Office
• Information Technology A Framework for
  Assessing and Improving Enterprise Architecture
  Management, (Version 1.1), April 2003.

7
The US Experience

• Clinger-Cohen Act 1996.
• Requires among other things that the CIOs for
  major departments and agencies should develop,
  maintain, and facilitate the implementation of
  architectures as a means of integrating business
  processes and agency goals with IT.
• E-Government Act of 2002
• Established the OMB Office of Electronic
  Government
• The offices responsibilities include overseeing
  the development of EAs within and across federal
  agencies.

8
South Korea

• The eGovernment Act of 2001 prohibits development
  of the same kind of software as developed in
  other government agencies for processing the same
  government business process.
• 234 city/district governments were found to have
  21 common business processes in respect of
  residents, vehicles, land, buildings,
  environment, construction, health, welfare,
  livestock, fisheries, water supply and sewage.
  These processes have been standardized and
  redesigned since 1997.
• 23 existing finance related systems that were
  operating independently in various government
  departments have been interconnected and
  integrated into the National Finance Information
  System (NAFIS)

9
Key Disciplines
Operating model
Enterprise Architecture
Engagement model
10
Key Disciplines
Operating model
Enterprise Architecture
Engagement model
11
Four Operating Models
High
Process integration
Governments
Low
Low
High
Process standardization
12
Four Operating Models
High
Process integration

• Diversification
• Few data standards across business units
• Most IT decisions made within business units
• Makes sense if few if any shared clients, no
  overlapping transactions

Low
Low
High
Process standardization
13
Organizational Change
Coordination
Unification
High
Process integration
Replication
Diversification
Low
Low
High
Process standardization
14
Key Disciplines
Operating model
Enterprise Architecture
Engagement model
15
Inception dates of various EA frameworks

• Zachman Framework, 1987
• The Open Group Architecture Framework (TOGAF),
  1995
• Command, Control, Communications, Computing,
  Intelligence, Surveillance and Reconnaissance
  (C4ISR), 1996
• Treasury information Systems Architecture
  Framework (TISAF), 1997
• Federal Enterprise Architecture Framework (FEAF),
  1999
• Treasury Enterprise Architecture Framework
  (TEAF), 2000
• Department of Defense Architecture Framework
  (DODAF), 2003

• A new framework has been adopted every 15
  months since the
• Clinger-Cohen Act became law in August 1996

16
The Zachman FrameworkCanadian Business
Transformation Enablement Program
17
Federal Enterprise Architecture
Performance Reference Model
Measurement indicators
Business Reference Model
31 lines of business 132 sub-functions
Service Component Reference Model
Business Driven Approach
Data Reference Model
Technical Reference Model
18
Business Value
19
Layers of Enterprise Architecture
Mission, Goals, Objectives, Performance Measures,
Security Objectives, define
Strategic
Business processes and activities use
Business
Data that must be collected, organized,
safeguarded, and distributed using
Information
IT Architecture
Applications such as custom or off-the-shelf
software tools that run on
Solutions
Technology such as computer system and telephone
networks.
Technology
20
Core Diagram Delta AirlinesSource Jeanne
W.Ross et al, Enterprise Architecture as Strategy
Operational pipeline
Prepare for flight departure
Flight arrival and closeout
Clean and service aircraft
Flight Departure and closeout
Monitor flight
Unload aircraft
Allocate resources
Load aircraft
E V E N T S
Gate readers
Pagers
Kiosks
Hand-helds
Voice
Delta nervous system
Video
Location
Flight
Schedule
Maintenance
Employee relationship management
Business reflexes
Equipment
Employee
Aircraft
Customer
Ticket
Nine core databases
PDAs
P R O F I L E
Cell phones
Laptops
Scanners
Reservation systems
Desktops
Skylinks
Skymiles
Reservations
Travel Agent
Skycap
Ticket counter
Crown room
Boarding
Inflight
Baggage
Personalization Digital
relationships
Loyalty programs
Customer experience
21
NCS Singapores eGovernment Framework
Business Service Architecture
Delivery channels
G2C
G2B
G2G
Enterprise IT Architecture
Information Bank
Application Architecture
Security
Education
Health
Taxation
Land Hub
Agency specific applications
eGovernment Framework
Stakeholder Transition Framework
Cross agency applications
Government internal applications
People Hub
Business management
Technical Standards
Business intelligence
Citizen relationship
Infrastructure Architecture
eGovernment Supporting Infrastructure
Enterprise Hub
Nationwide ICT Infrastructure
Information Architecture
Management
Retrieval
Analysis
22
Washington DC Before

• 21,000 employees (excluding public school system)
• 5.4 billion budget
• Services provided through 74 operating agencies
• 10 centralized e.g. purchasing, HR, IT, legal
  services
• 64 customer facing e.g. law enforcement,
  transportation
• January 1999 DC was half a billion dollars in
  debt
• Public services ranked at bottom of big city
  ratings

23
Operating Tenets

• Single point of entry
• All citizen requests to be routed to a central
  point of entry
• Guaranteed closure
• Citizen requests once submitted will be
  fulfilled, no matter which agency or how many
  agencies are involved
• Benign service delivery
• Make it easy for citizens to deal with the
  government

24
Operating model

• Standardization of common processes
• End to end integration of processes
• Data sharing
• Nine service modernization programs launched in
  2001
• Nine functional clusters administrative,
  customer, educational, enforcement, financial,
  human, motorist, property, transportation
  services
• Consolidation of servers, storage and software

25
Washington DC After

• DC government improved from worst to first
• Government Technology magazine named DC portal as
  the number one Web portal in government
• Cost of modernization program 71 million
• Measurable cost savings 150 million

26
Summary of Enterprise Architecture Management
Maturity Framework Version 1.1 (GAO)
Maturation
27
The Importance of Standards Baltimore Fire 1904

• Major fire in downtown Baltimore
• More than 1,200 firefighters, 57 engines and 9
  trucks arrive from 5 states and the District of
  Columbia
• Fire crews unable to assist, because
  out-of-town hose couplings would not fit
  Baltimore fire hydrants
• Within 30 hours
• 70 city blocks devastated
• 1,526 buildings destroyed

28
UKs e-Government Interoperability Framework
(e-GIF)
e-GIF
e-Gov Metadata Standard
Government Data Standards Catalogue
XML Schemas
Technical Standards Catalogue
Government Category List
29
Examples of Standards

• Two letter country codes eg. VN for Vietnam
  defined by ISO 3166-1
• ISO 8601 defines numeric representation of dates
  in the form YYYY-MM-DD
• TCP/IP standard developed and endorsed by the
  Internet Engineering Task Force (IETF) through
  RFC 2246. Part of the protocol relates to IP
  addresses in the form nnn.nnn.nnn.nnn where nnn
  is a number between 0 and 255
• W3C standards include HTML, XML, XSLT, XML
  Schema, RDF, Web services, XQuery and XPath

30
Key Disciplines
Operating model
Enterprise Architecture
Engagement model
31
Enterprise Architecture Reporting Structure
CIO
IT Strategy Architecture and Planning
Chief Architect
Information Architect(s)
Business Architect(s)
Technical Architect(s)
Solution Architect(s)
Gartner (April 2006)
32
Project Architects
CIO
Chief Architect
PMO
Support Staff
Project Manager
Information Architect(s)
Business Architect(s)
Technical Architect(s)
Solution Architect(s)
Project Architect(s)
Gartner (April 2006)
33
The Engagement Model
ALIGNMENT
Business
IT
National Strategy and goals
Enterprise architecture
National level
Nationwide IT governance
Municipal unit strategy and goals
COORDINATION
Municipal unit architecture
Municipal level
Linking mechanisms
Project plan
Project IT architecture
Project team level
Project management
Adapted from Jeanne W.Ross et al. Enterprise
Architecture as Strategy
34
More visionary role
Chief Architect
Enterprise Architect
Enterprise Architect
Enterprise Architect
Enterprise Architect
EA Modeling Team (Virtual)
EA Modeling Team (Virtual)
EA Modeling Team (Virtual)
EA Modeling Team (Virtual)
Application Architect
Application Architect
Application Architect
Application Architect
Gartner (April 2006)
35
Plan
Initial Research
Project Initiation
Technical Teams
Workshops
GEAF
Best practices
Draft Plan Workshops
3 ministries
Implementation Plan
Engagement Model
Project finalization
Training
Assessment Methodology
Final Report
Draft Plan Workshop
Final Workshop
36
Conclusion

• Focus on defining the right EA process, and spend
  less time debating and choosing an EA framework.
• Start the EA effort by devising a future-state
  architecture.
• The secret of defining a great enterprise
  architecture is knowing when to stop.
• Large organizations are simply too complex to be
  designed by a small group of enterprise
  architects, no matter how smart they are.

Source Gartner
37
Thank You