Enterprise Architecture provides a framework to guide the development of complex systems and services. The document discusses the need for enterprise architecture when building large organizations and systems, as without a guiding plan it can result in disconnected and inefficient solutions. It introduces several common enterprise architecture frameworks, including TOGAF, Zachman Framework, and FEA, which provide standardized processes and models to define the key components of an enterprise. The document argues that adopting an enterprise architecture approach helps ensure strategic alignment, increase innovation, improve efficiency, and maximize return on investment from new technologies.

1. Introduction to
Enterprise Architecture
Seemantinee Sengupta
Enetrprise Architecture Resource Division
National Informatics Centre
20 February 2019

2. Context and Need for Architecture
When do we need an
architecture?

3. Context and Need for Architecture
Do we need an
Architecture?
In simple endeavors, for example
construction of a mud hut, a
formal architecture blueprint may
not be needed to ensure
successful construction and
subsequent maintenance

4. Context and Need for Architecture
Do we need an
Architecture?
In simple endeavors, for example
a wood cabin, a formal
architecture blueprint may not be
needed to ensure successful
construction and subsequent
maintenance

5. Context and Need for Architecture
Greater the complexity of the
endeavor, greater is the necessity
of a guiding blueprint.
Blueprint is also essential to
undertake further development or
make modifications.
For significantly large endeavors,
not only is a blueprint essential, a
phased plan/roadmap is a must.

6. Context and Need for Architecture
Building large, complex,
enterprise-wide information
systems without an
enterprise architecture is
like trying to build a city
without a city plan.
Can you build a city without
a city plan? Probably Yes.
Would you want to live in
such a city? Probably not.

7. Architecture
for Construction
Architecture for
Service Delivery
in State
Architecture for
Information Systems
of Enterprise
Context and Need for Architecture
Hut
Wood Cabin
Urban House
Residential Tower
Gated Community
Township
Request
Service
Agency
Department
Sector
State
Program
Module
Package
(HRMS)
ERP (FMIS, HRMS,
….)
ERP, CRM, SCM, …
Enterprise and Partner Systems

8. Architecture
for Construction
Architecture for
Service Delivery
in State
Architecture for
Information Systems
of Enterprise
Context and Need for Architecture
Hut
Wood Cabin
Urban House
Residential Tower
Gated Community
Township
Request
Service
Agency
Department
Sector
State
Program
Module
Package
(HRMS)
ERP (FMIS, HRMS,
….)
ERP, CRM, SCM, …
Enterprise and Partner Systems
Complexity due to Size & Scale

9. Architecture
for Construction
Architecture for
Service Delivery
in State
Architecture for
Information Systems
of Enterprise
Enterprise Architecture – A Recap
Context and Need for Enterprise Architecture
Hut
Wood Cabin
Urban House
Residential Tower
Gated Community
Township
Request
Service
Agency
Department
Sector
State
Program
Module
Package
(HRMS)
ERP (FMIS, HRMS,
….)
ERP, CRM, SCM, …
Enterprise and Partner Systems
Dynamics of Change

10. Defining Enterprise Architecture
24-01-2023 National Informatics Centre 10

11. Defining Enterprise Architecture
11
• Enterprise: Any collection of organizations that have common goals
• Union Government or State Government at broader level
• Individual Ministry or Department at narrower level
• Enterprise Architecture: Description of
the current and future services, processes
and information systems of the enterprise
aligned with its vision.

12. How to define Enterprise Architecture
• There is a process of architecting which is prescribed by the discipline
of EA.
• It produces outputs that describe the architecture of an enterprise.
• The process of architecting involves, taking stock of the relevant
components or building blocks that make up an enterprise.
• An architect then needs to examine how these components enable or
constrain the enterprise in fulfilling the goals of the enterprise.
• This is done by looking at how the components are organized or
configured, how they are used or how they behave or perform
together
24-01-2023 National Informatics Centre 12

13. How to define Enterprise Architecture
• Study the enterprise in its current state and how it should be in the
future.
• Work out the alternatives for moving from the current state to the
future target state.
• Create frameworks to manage the architecture, spell out descriptions
of the architecture and its components and road maps to show the
best way to change or improve the architecture.
• Assess the constraints and opportunities, costs, benefits, risks and
value in each option to help decision makers to select the best
alternative.
24-01-2023 National Informatics Centre 13

14. Do we need enterprise architects?
• No there are many enterprises that exist without the intervention of a
enterprise architect. However, there are many situations when it is
better to architect an enterprise than to leave the creation and
evolution of its architecture to chance.
• Every enterprise will always have an architecture, its not optional. But
we do have a choice ..whether we manage its evolution or not and
how well we manage it.
24-01-2023 National Informatics Centre 14

15. 15
• Public transit, schools and parks are
afterthoughts
• No common services
• Inefficient and fragmented processes
• Aesthetically unpleasing
• Limited scope for growth
• Future-oriented, planned and sustainable
• Common services
• Principles and standards (fire, safety,
master plan)
• Higher productivity and effectiveness
• Aesthetically pleasing
Value of Architectural Thinking

16. 16
Enterprise-wide
focus
Project
focus
IT Solutions
IT Solutions
Governance
Strategy
IT Strategy
Enterprise Architecture
Governance
Architecture
• Service
• Process
• People
IS/IT
Architecture
• Information
• Application
• Technology
Transition Planning
Government Processes & IT Systems
Enterprise Architecture: “the city plan”
Solution: “the building design”
Aligning
Change
to
Business
Need
Enterprise Architecture is Analogous to City
Planning for an Enterprise

17. EA – The Building Blocks
17
Strategy & Performance Architecture
Business
IT
Service & Process Architecture
IT
Change
Driven
by
Business
Understanding

18. Leveraging Enterprise Architecture
Throughout the globe many countries have utilized Enterprise Architecture
approach to successfully undertake transformation journeys
24-01-2023 National Informatics Centre 18
EA mandated by
act of Parliament
Malaysia
Bhutan
Bangladesh
The United States
of America
South Korea Australia
Singapore
Germany
United Kingdom New Zealand Finland
Estonia

19. EA Leveraged to Plan and Manage
Transformations
24-01-2023 National Informatics Centre 19
Target State
Transition State 2
Transition State 1

20. Benefits of Enterprise Architecture
Increased efficiency of
service delivery
Increased innovation
enabled by a defined
architecture and its
governance
Improved effectiveness of
scheme implementation
Increased agility through
quicker technology
changes in response
dynamic business changes
Higher RoI from
investments in
technology, through
common, re-usable
components
Seamless interoperability
between systems
20

21. Decisions in Enterprise Architecture
• Should we use a common set of applications across different
programs / services OR develop independent applications?
• Which systems must we develop / enhance / retire?
• Which data area / elements must we standardize across the
enterprise?
• What enterprise-wide interfaces should our systems provide?
• Should we standardize the technology we use?
• What kind and which current or upcoming technologies should we
invest in?
24-01-2023 National Informatics Centre 21

22. Key Takeaways
22
• Enterprise architecture:
• is to understand the enterprise on a holistic basis (business, technology and
operating environment)
• helps effectively direct the enterprise to deliver strategic goals by aligning
business and technology operations to strategic intent
• We need enterprise architecture to:
• improve service delivery efficiency and scheme implementation effectiveness
by improving alignment of business & technology to strategic intent
• increase agility by making faster changes in response to dynamic business
• increase RoI from technology investments through optimized landscape
enabled by common & re-usable components

23. Thank you

24. Enterprise Architecture
Frameworks
24-01-2023 National Informatics Centre 24

25. EA Frameworks Overview
24-01-2023 National Informatics Centre 25
Enterprise Architecture
Frameworks
FEA
Gartner
Zachman
TOGAF
EA Frameworks typically include:
• Processes & methods
• Catalog of architecture deliverables
and artifacts
• Content model and repository
structure
• Reference models
• Best practices, guidelines &
techniques
• Architecture capability
development
• Architecture governance &
compliance
Each of the frameworks follows different philosophies, and any implementing enterprise may choose bits and
pieces from each of the methodologies, modify and merge them as per their unique set of requirements

26. EA Frameworks Evolution
24-01-2023 National Informatics Centre 26
Year 1987 1994 1996 2002 2003 2006 2009 2017 2018
Activity
Zachman’s
Enterprise
Architecture
TAFIM
released
Clinger –
Cohen Bill
passed
FEA replaces
FEAF
TOGAF 8.0
Enterprise
Edition
released
FEA
completed
(~)
TOGAF 9
released
IndEA
created
TOGAF 9.2
released
The Zachman Framework is
an Enterprise Ontology
which provides a formal and
structured way of viewing
and defining an enterprise.
The Open Group
Architecture Framework
(TOGAF) is a framework for
enterprise architecture
which provides an approach
for designing, planning,
implementing, and
governing an enterprise’s
architecture
Gartner Methodology is
based on the amalgamation
of Gartner framework and
Meta architecture
development process.
A federal enterprise
architecture (FEA) provides
a common approach for the
integration of strategic,
business and technology
management as part of
organization design and
performance improvement
The Zachman Framework
The Open Group
Architectural Framework
The Gartner Methodology
The Federal Enterprise
Architecture
The development of the above frameworks has paved the way for multiple Nations (Korea, Singapore, UAE, UK and USA) and Industry
(Microsoft and Oracle) to develop their own tailored enterprise architecture frameworks which are being consumed by enterprises.

27. Zachman Framework (1/2)
• Schema - the intersection between two classifications:
• First: Primitive interrogatives – What, How, When, Who,
Where, and Why.
• Second: Derived from the transformation of an abstract
idea into an instantiation – Identification, Definition,
Representation, Specification, Configuration and
Instantiation
27

28. Zachman Framework (2/2)
28

29. The Open Group Architecture Framework (TOGAF) (1/2)
• Detailed method and a set of supporting tools for
developing an enterprise architecture.
• Based on an iterative process model called
Architecture Development Method (ADM)
• TOGAF is developed and maintained by members of
The Open Group
29

30. The Open Group Architecture Framework (TOGAF) (2/2)
30

31. Federal Enterprise Architecture (FEA) (1/2)
• Supports planning and decision-making in US Federal Govt. through
documentation and information providing an abstracted view of
enterprise at various levels of scope and detail.
• Core is Consolidated Reference Model (CRM) – set of 5 interrelated
reference models
• Also provides Collaborative Planning Methodology – a simple,
repeatable process to aid planning
31

32. Federal Enterprise Architecture (FEA) (2/2)
Consolidated Reference Model Collaborative Planning Methodology
32

33. Gartner Methodology (1/2)
• Gartner methodology believes that EA is about bringing together
three constituents:
• Business owners
• Information specialists
• Technology implementers
• According to Gartner, EA project must be started with understanding
enterprise direction on business, not with finding its current position.
33

34. • The sequence of future-state EA
development activities include
• Develop requirements - identification of the
business-driven requirements
• Develop principles - qualities that must be
exhibited by an enterprise to realize its goals
• Develop models - detailed drilling down of
architecture content
• These activities are meant to convey a
logical sequence of development-based on
relationships and dependencies, rather
than a rigidly linear sequence of events.
Gartner Methodology (2/2)
34

35. IndEA as National Standard
Candida Shadap
National Informatics Centre
Meghalaya State Unit
20 February 2019

36. India Enterprise Architecture (IndEA)
Framework
Notified as national standard on October 9, 2018
Published Documents:
• IndEA Framework
• IndEA Adoption Guide
• IndEA Primer
24-01-2023 National Informatics Centre 36
IndEA
Business Reference Model
(BRM)
Data Reference Model
(DRM)
Application Reference
Model (ARM)
Technology
Reference Model (TRM)
Architecture Governance
Reference Model (GRM)
Integration Reference
Model (IRM)
Performance Reference
Model (PRM)
Security Reference
Model (SRM)
Provides Portfolio
of Services to
Guides Design &
Implementation of
Life-cycle Mgt of
Enterprise Data of
Specifies Technology
Landscape &
Standards of
Provides Application
Portfolio & S/w
Development methods to
Interoperability
& Integration of
Specifies Standards &
Best Practices for
Security of assets of
Defines methods for
Outcome
Assessment to

37. Indian eGovernance Context
24-01-2023 National Informatics Centre 37

38. Indian eGovernance Evolution
From Digitization to Digitalization
24-01-2023 National Informatics Centre 38
Pre 1995
• Networks - State HQs
• Computerization (Banks,
Railway Reservations)
1995 - 2005
• Localized champion driven
department / state initiatives
• Networks - District HQ
• Emails, Basic Websites
• Emphasis on local
automation & efficiency
2006 - 2013
• NeGP – institutional
initiatives & MMPs
• SWAN - Blocks
• eServices with basic
workflows
• Focus on standardisation –
Infra, Policies, Tools,
2014 onwards
• Digital India & eKranti –
Transformational initiatives
• BharatNet - Villages
• Platform based, integrated,
transformative services
• Citizen engagement and
experience centric

39. Initiatives & Enablers
24-01-2023 National Informatics Centre 39
Digital
Locker
Aadhaar
(Digital ID)
PFMS
ServicePlus
eSign
• Central Excise and Customs
• e-Office
• Income Tax
• IVFRT: Immigration, Visa Foreigner’s
Registration & Tracking
• MCA21
• Passport Seva Project
• Banking MMP
• Insurance MMP
• Pensions
• e-Sansad
• e-Vidhaan
• NMEICT (National Mission in Education
through ICT)
• Urban Governance
• Employment Exchange (National
Career Service Project)
• Crime and Criminal Tracking Networks
and Systems (CCTNS)
• e-District
• Commercial Taxes
• e-Municipality
• e-Panchayat
• National Land Records Modernization
Programme (NLRMP)
• Public Distribution System (PDS)
• Education
• e-Health
• Agriculture 2.0
• Rural Development
• Women and Child Development
• e-Courts
• e-Biz
• e-Procurement
• e-Trade (EDI)
• India Portal
• e-Sangam (formerly National Services
Delivery Gateway)
• Common Services Centers (CSC)
• Financial Inclusion
• Roads and Highways Information
System (RAHI)
• National Geospatial Information System
(NGIS)
• Social Benefits
Central Initiatives (17) State Initiatives (16) Integrated Initiatives (11)
Vibrant
Private
Sector
MyGov.in
& UMANG
BharatNet IndEA
& DSS
eTaal Unified
Payments
Interface
Partial List
Digital India

40. UN eService Maturity Model: Connected Services
is the Next Stage of Progression for India
24-01-2023 National Informatics Centre 40
Present
Future

41. Current Landscape
While we have developed several systems to automate key government
processes, resulting landscape is far from optimal
24-01-2023 National Informatics Centre 41
Holistic Enterprise Architecture Led Transformation is an Approach for Future
Senior Leadership has to often put significant efforts
to further gather and organize information for making decisions!
Siloed Systems
Low
interoperability
Little system
flexibility for
quick change …
One Citizen –
Multiple
Government
Experience

42. Current Landscape
While we have developed several systems to automate key government
processes, resulting landscape is far from optimal
24-01-2023 National Informatics Centre 42
Holistic Enterprise Architecture Led Transformation is an Approach for Future
Senior Leadership has to often put significant efforts
to further gather and organize information for making decisions!
Siloed Systems
Low
interoperability
Little system
flexibility for
quick change …
One Citizen –
Multiple
Government
Experience

43. IndEA Framework
24-01-2023 National Informatics Centre 43

44. A 2-Speed Model for
Digital Governance
Architecture at Macro-level
Service Standards at Micro-level
+
IndEA
for ONE Government
DSS
for a rich UX
44

45. Why IndEA ?
• India is below global average on UN e-Government Index
• We need to take large strides to make up !!
• Enterprise Architecture approach is a good way.
• India has to leverage its current strengths – widely, rapidly!
• Aadhaar, Mobile, Digital India…
• Adoption of IndEA enables a planned development
• Through ‘Architectural Thinking’
45

46. The IndEA Vision (WoG)
IndEA Vision
ONE Government
IndEA Principles
IndEA Reference Models
States & UTs
GoI Ministries PSUs
• Unified & Uniform Interfaces
• Citizen/ Business-centric Services
• Guaranteed Service Levels
• Effective Program Management
• Less Government, More Governance
• Security & Privacy
Interoperability
Shared
Infra
Common
Applications
Open
Standards
SDG
Approach
Prioritization
Process
Re-engineering
Change
Mgt
TECHNOLOGY STAKEHOLDER BENEFITS PROCESS / PEOPLE 46

47. The 8 Reference Models of IndEA
IndEA
Business Reference Model
(BRM)
Data Reference Model
(DRM)
Application Reference
Model (ARM)
Technology
Reference Model (TRM)
Architecture Governance
Reference Model (GRM)
Integration Reference
Model (IRM)
Performance Reference
Model (PRM)
Security Reference
Model (SRM)
Provides Portfolio
of Services to
Guides Design &
Implementation of
Life-cycle Mgt of
Enterprise Data of
Specifies Technology
Landscape &
Standards of
Provides Application
Portfolio & S/w
Development methods to
Interoperability
& Integration of
Specifies Standards &
Best Practices for
Security of assets of
Defines methods for
Outcome
Assessment to
47
36 Principles
of IndEA

48. The IndEA Business Landscape
IndEA Core
Financial Management
HR Management
Performance Management
Procurement
Litigation Management
Land &Resources Management
Grievance Management
Unified Contact Center
Data Analytics
Service Delivery Management
Right To Information
Primary
Sector
Health
Education
Skill
Development
Urban
Development
&
Housing
Rural
Development
Social
Justice
Energy
Infrastructure
Industry,
Labour
&
Employment
Natural
Resources
&
Environment
Transportation
Tourism
Public
Safety
Disaster
Management
Public
Distribution
System
16 Verticals
12 Horizontals
Standardize
Integrate
Virtualize
48

49. Thank you
XXX
National Informatics Centre
Ministry of Electronics and Information Technology
Government of India

50. 50

51. Value of an Architectural Reference Model
• An Architectural Reference Model
• Depicts the Components of each Domain (Business, Application, Data etc)
• Identifies the relationships between the Components
• Defines the Standards applicable to the Domain
• Adoption of Reference Model
• Enables fast-tracking Architecture Development (cuts 70% of effort)
• Ensures compliance with relevant Standards
• Enables compliance with Architectural Principles
51

52. IndEA RM to Implementation
IndEA
Reference
Model(s)
Reference
Architectures for
the Domain
Arch Dev
• Problem Space
• Stakeholder Needs
• Business Reqts
Solution
Architecture
Solution Design
• Constraints
• Opportunities
Implementations
52

53. 53

54. 54
v
Goal Defines
Objectives Programs, Projects, Schemes
Govern
Sectors
Departments
Consist of
SERVICES
Provide
Relate to
Service Definition
Are Specified by
Service Transformation
Are Enhanced by
Service Delivery
Are Realized thru
Measurement
Are Assessed by
Objective
Type
Category
Priority
Service Level
Specifies
BPR Change Management
Is Achieved by
Channels
Service Provider
Beneficiary
Comprises
of
Output
Outcome
Economy
Analyses
GOAL
ORGANIZATION
BENEFITS
&
RESULTS
BUSINESS
REFERENCE
MODEL

55. 55
PERFORMANCE
REFERENCE MODEL

56. 56
DATA
REFERENCE MODEL

57. 57
Enterprise Portal Enterprise App Store
API Gateway / ESB India Stack
IndEA CORE PLATFORM
SMS Gateway
IAM
Finance Mgt HR Mgt
Scheme Mgt Performance Mgt
COMMON APPLICATIONS
e-Procurement
Grievance Mgt
Unified Call Centre
E-Office
Content Mgt
License Mgt Litigation Mgt Data Analytics RTI GIS
e-Cabinet
Primary Sector Education
Benefits/ DBT Skill Development
GROUP APPLICATIONS
Health
Infrastructure
Works
Disaster Mgt
Land Mgt
Public Safety Urban Devpt
Dept-SPECIFIC APPLICATIONS
Rural Devpt Public Distribution System Energy
Social Justice Industry Transportation Labour Tourism Natural Resource
11
9
14
6
SYSTEMS
EXTERNAL
TO
IndEA
Concentric
4-Layered
Meta-model
of
ARM

58. 58
Technology Reference Model (TRM)
Access Devices,
Network Components,
Delivery Platforms and
Cloud
Open Standards
Apps, App Stores,
Application Platform,
Mobile Device Mgmt,
Big Data/IoT
Network Infrastructure
IT Infrastructure
SLAs / OLAs
PRM
Applications Reference Model (ARM)
Comprises Of
Subject To
Consists
Of
Input
To
Communication
Infrastructure Interface
Connects To
Interface for Intra/
Internet Objects
Subject To
Open Source Products
Grouped By
Connects To
Service Outlets,
Devices & Applications
Connects To
Subject To
Dept. Permises /
State Data Center
NIC Cloud Data Center
(MeghRaj)
Proprietary Products
PRM and BRM Provides Input To
Open Formats
TRM Service Standards
Specifications for eGovernance in India
TRM Components
Comprises of
Open API Gateway
ROA/SOA on Cloud
Architected as
Microservices
and SOA based
Web Services
Third Party Ecosystem
Consists
Of
Integration
Reference
Model
(IRM)
Security
Reference
Model
(SRM)
Provides Input To
Provides Input To
Provides Input To
Provides
Input
To
Provides
Input
To
Provides
Input
To
Provides Input To
Connects To
Data Reference Model (DRM)
Performance Reference Model (PRM)
Provides Input To
Governance
Reference
Model
(GRM)
Hosted
At
Business Reference Model (BRM)
TECHNOLOGY REFERENCE MODEL

59. 59
INTEGRATION REFERENCE MODEL

60. 60
IndEA Security Reference Model
BRM
Business Vision
Strategies
Requirements
Services
Risks
Threats
Information
Assets
Assessment
Security Policy Risk Management
Data Layer
Application Layer
Perimeter Layer
Network Layer
Endpoint Layer
Controls
Additional
Controls
Security Architecture
Protection Detection Response Recovery
Tools Procedures Capabilities Governance
Enables Design of
Supports
Through
Provides
Provide inputs for of to
Supports DESIGN of
Red dotted line delineates
the scope of SRM
Reference Model Level
Architecture Level
Solution Level
Implementation Level
Indicates
Business Priorities of
Guides choice of Guides choice of
Are
applied
at
Are
applied
at

61. 61
IndEA Governance Reference Model
Government
Architecture
Governance Board
IT
Governance Board
A Structure
Roles &
Responsibilities
Has
Participates in
Reports
Architecture
Compliance to
Architecture
Capabilities
Builds
Architecture
Compliance
Reviews
A Structure
Roles &
Responsibilities
Has
Architecture
Development
Architecture
Contract
Architecture
Developer
Manages
Architecture
Repository
Provides Architecture Vision to Provides Approvals & Resources to
Migration of Legacy
Applications to
Target Architecture
Manages
Green Field Projects
to fulfil Architecture
Vision
Implements
Reports
Performance
to
Reports
Progress
of
Architecture
Development
to
Incumbent
System Integrators
New
System Integrators
Through Through
GRC
Is Responsible for

62. Prime Principles of IndEA (9 of 36)
SDG Linkage
Data Sharing
Reusable
Applications
Technology
Independence
Federated Orchestration
Cloud First
Integrated Services
Mobile First
Primacy
of
Principles
62

63. 63
PRINCIPLES OF
IndEA (36 OF 36)