EA Resource Group NIC

1. India Enterprise Architecture Framework An enterprise architecture (EA) is a conceptual blueprint that defines the structure and operation of an organization. The intent of an Enterprise architecture is to determine how an organization can most effectively achieve its current and future objectives. Need for IndEA • Holistic approach in the context of e-Governance in India EA Resource Group NIC P.Gayatri Sr.Technical Director NIC, Andhra Pradesh

2. SDG 9: Industry Innovation and Infrastructure Key initiatives under Digital India • The aim is to simplify government business processes by • Introduction of IT • Online interface and tracking across departments • Integration of services and platforms (UIDAI, Payment Gateway, Mobile Platform) • Public grievance redressal through IT so on Broadband highways Universal access to mobile connectivity National Rural Internet mission E-Kranti E-Governance Informationfor All Electronic Manufacturing Training and Jobs creation Early Harvest Program … paved way to develop a ONE GOVERNMENT Framework – IndEA

3. IndEA Vision 'To establish best-in-class architectural governance, processes and practices with optimal utilization of ICTinfrastructure and applications to offer ONE Government experience to the citizens and businesses' Methodology: Adopted TOGAF ADM to develop Reference Models

4. Primary Objectives of IndEA • Capture and codify current knowledge and experience in a consolidated form for ready referenceto anyone who is interested to understand this subject • Kick start enterprise architecture initiatives across India, covering entire state governments and other government / public sector entities; • Enrich the procurement process and provide greater leverage to government enterprises in managingtheirvendors; • Spell issues and concerns contextualtoIndia, in a manner such that the finer nuances of governance are captured and factored in;  • Support India’s transition towards digital governance and knowledge economy as envisaged in the Digital India initiative.

5. As-Is To-Be Architect

6. IndEA Reference Models – Overview

7. A Reference Model is an abstract representation of the entities relevant to a domain of the Enterprise Architecture, the inter-relationships among those and the standards to be followed.

8. IndEA - Reference Models Defines KPIs for outcome assessment PRM Guides Design & Implementation of EA GRM Provides Portfolio of Services BRM IndEA Specifies Standards and Best Practices for Security Assets SRM Provides Application Portfolio and SW Development Methods ARM Interoperability & Integration AIRM Life cycle management of Enterprise Data DRM Specifies Technology Landscape & Standards TRM

9. IndEA Reference Models – Overview

10. IndEA Reference Models – Overview

11. Performance Reference Model – PRM PRM Provides framework to measure Effectiveness and Efficiency of Business Processes

12. Performance Layer

13. PRM provides framework to measure effectiveness and Efficiency of Business Processes

14. Relationship of PRM and BRM

15. Defining KPIs for a service – PRM (Illustrative)

16. Business Reference Model – BRM BRM is a mechanism to describe the administrative structure of the State’s Departments, its Functions and Services. It articulates Business Structure and Prioritizes Business Services.

17. Business Reference Model Schematic BRM is a mechanism to describe the administrative structure of the State’s Departments, its Functions and Services. It articulates Business Structure and Prioritizes Business Services.

18. Get Department Approval Study Acts / Gos / Circulars / Registers Examine Filled-in Questionnaire Prepare/Communicate Questionnaire from the basic understanding View Demonstrations of Existing legacy systems Interact with Nodal Officer Prepare a Skeleton Document Interact with Users and Citizens Gap Analysis with BPR Recommendations Prepare As-Is Document in a structured format Visit Field offices As-Is Study Methodology - Illustrative

19. Gap Analysis through Heat-map preparation -Illustrative

20. Service deliverance through BhuSeva Identification of Key Performance Indicators Get Department Approval Prepare To-Be Document in a structured format Scope and Vision of the Service High-Level diagram for the To-Be system List of Comprehensive Use Cases Becomes input to SRS To-Be Modelling - Illustrative

21. Stakeholders Matrix– Illustrative

22. Relationship Between BRM and ARM

23. Data Reference Model – DRM It provides a standard framework for describing the data identified by the department, its context, mode of sharing and data modeling so that a meaningful and usable Data Architecture can be derived by the consuming departments.

24. Data Reference Model

25. IndEA Reference Model - DRM It provides a standard framework for describing the data identified by the department, its context, mode of sharing and data modeling so that a meaningful and usable Data Architecture can be derived by the consuming departments.

26. Data Context - Data Steward, Data Source, Data Assets - Illustrative

27. Data Description- Data Entities, Relations - Illustrative

28. Application Reference Model – ARM It provides structure to automate Business Services identified in BRM. It defines the building blocks required to develop high-level Application Architecture. ARM identifies various Application Capabilities and facilitates sharing & re-use of application capabilities. It also provides building blocks to group similar applications and describes guidelines for integrating the applications.

29. Application Reference Model • Provides structure to automate Business Services identified in BRM. • Defines the building blocks required to develop high-level Application Architecture. • Identifies various Application Capabilities and facilitates sharing & re-use of application capabilities. • Provides building blocks to group similar applications and describes guidelines for integrating the applications.

30. ARM – Indicative Portfolio

31. Application Reference Model - Illustrative Core, Common & Group Applications Departmental Applications Third Party Developers Community Development API Facade Information Services Master Data Management Transactional Services CRUD Services Service N Service F Service C Service D Service E Service B Service A

32. Technology Reference Model - TRM TRM applies the Common Technology Standards to Infrastructure Service Components for ensuring interoperability between Applications and Technology Platforms for multi-channel delivery of Stakeholder Services.

33. Technology Reference Model TRM provides a holistic view of the e-Governance technology landscape The Technology Reference Model (TRM) t aims to develop an interoperable and cost effective framework which could be referenced and used by Central government, States and agencies for inter-departmental discovery and digital collaboration

34. Technology Reference Model

35. Technology Layer Stack – Illustrative

36. Security Reference Model – SRM Provides security and privacy requirements and standards that secure Applications and Services supported. It provides guidelines to define security controls at various levels including business, network, infrastructure, application and data.

37. Security Reference Model

38. Layers of Security Reference Model

39. Controls at Business Layer - Illustrative

40. Controls at Business Layer - Illustrative

41. Application Integration Reference Model – AIRM Provides guidelines for interoperability of Applications

42. Application Integration Reference Model

43. IndEA Reference Model – AIRM

44. AIRM – Guidelines and integration methods

45. AIRM – Guidelines and integration methods

46. Architecture Governance Reference Model – GRM Provides guidelines for maintaining and enhancing Enterprise Architecture

47. Governance Reference Model

48. Critical Success Factors – GRM • Engagement of senior management • Continuous EA program as against a one-time project • Involvement of Different important Government Agencies • Skillful EA team • Good knowledge management practices • Staff and other stakeholder support • Clear definition of roles, responsibilities, and procedure in the governance team. • Use automation tools to control governance and architecture board Work flow

49. EA Communication Plan Matrix– GRM

50. Governance Model – Illustrative Architecture Governance Board • Structure, Roles & Responsibilities IT Governance Board Architecture Contract PMU Set up