AP State Enterprise Architecture
AP State Enterprise Architecture for a boundary-less information flowThe Vision of the State of Andhra Pradesh is to use e-Governance as a tool to provide integratedservices to its citizens through a free flow of Information, and to usher in an era of GoodGovernance. Designing an Enterprise Architecture is an essential first step in this direction.
AP State Enterprise Architecture V 1.0INTRODUCTION“Enterprise Architecture is a framework for conducting analysis, design, planning andimplementation of the vision, goals, strategies, functions, activities and desired outcomesof an enterprise, using a holistic approach at all times, such that the IT infrastructure and ITservices are always aligned to the business strategies and business services, throughstandardization and integration”The real value of Enterprise Architecture is not in making better architectures it’s inmaking a better enterprise.Enterprise Architecture is quite relevant to Government in so far as Government is an‘Enterprise of Enterprises’. EA enables a systematic and holistic development of a Portfolioof e-Governance Projects to provide integrated services to the stakeholders. Citizencentricity is the essence of Good Governance. It involves building a 360 degree view of acitizen across all his touch-points with the government. Data should be modeled as a sharedlayer across all government departments and a cohesive citizen's profile should help alldepartments target the right citizens for the right services.This document presents a high-level view of the Andhra Pradesh State EnterpriseArchitecture (APSEA).The central theme of the APSEA is to provide “just enough” structure,which can be created “just in time” to meet the transformational requirements of theGovernment. APSEA shall be the Metamodel. The Architectures of various Enterprises(Departments and Agencies) are to be designed or re-designed so as to conform to theMetamodel.In so far as this is a high-level document, it is necessary for an Enterprise Architect (tobe selected), to detail out several of the ideas presented in this document, mostly inconsultation with the departments and agencies of the Government. For instance, the basicobjectives and value proposition of each department, the services it intends to provide to itsstakeholders in the TO BE scenario, the proposed service levels and KPIs, the TO BEdecision-making processes, its position in the capability-maturity model, etc are to bedocumented and incorporated appropriately in the APSEA.APSEA is a journey, not a project. Let us take the first step 1
AP State Enterprise Architecture V 1.01. SCOPE OF APSEAWHY DESIGNBREADTHThe APSEA shall extend to all the departments of GOAP, its publicenterprises and agencies that contribute to 80% of the business ofgovernance, especially in relation to its interface with the citizens,businesses and the internal processes of Government connectedtherewith. An ABC analysis has to be done to identify the entities andthe services and activities of each such entity that shall be included inthe scope of the EA.DEPTHTypically, an architecture is a high-level document that should not loseitself in detail. However, it should not be too abstract to be useful to thedevelopers. The eGov vision of GoAP is quite ambitious both in termsof its breadth and depth as also in terms Time-to-Benefit. Keepingthese in view, the effort in developing APSEA shall lead to a comprehensive conceptualization of the spectrum of possibilitieswithin the scope identified;identification of all the critical building blocks - technical andfunctional - that ensure a Whole-of-Government approach,interoperability, integrated service delivery, flexibility indevelopment,simplicity and securitydesign of all the systems that constitute the critical building blocks.assessment of Capability Maturity Levels of various departmentsand conducting a gap analysisDIMENSIONSEA?The benefits that resultfrom a good enterprisearchitecture include: Efficiency Productivity Interoperability Integration Simplicity Agility Cost-effectiveness Value-for-Money Sustainability Flexibility IndustryfriendlinessTypically, Enterprise Architecture extends to 4 Domains: The Business Architecture, which defines thegovernance goals,organization, and key processes.The Data Architecture, which describes the structure of the logical and physical data assets anddata management resources.The Application Architecture, which provides a blueprint for the individual applications to bedeployed, their interactions, and their relationships to the core government processes.The Technology Architecture, which describes the software and hardware capabilities required torealize the eGov vision, like IT infrastructure, middleware, networks, communications & standards.The present EA effort aims to extend to all the above 4 domains2
AP State Enterprise Architecture V 1.02. VISION OF APSEA“Vision is the art of seeing the invisible”Jonathan SwiftThe Vision of the AP State Enterprise Architecture should truly reflect the Vision to establish SwarnaAndhra Pradesh. While the framework for developing the APSEA should obviously begin with avisioning consultation, involving all major stakeholders within and outside the Government, the visionshould contain the following elements:Aspirational The APSEA shall be an effective tool and one of the important frameworks in the realization ofthe vision of Swarna Andhra Pradesh.The APSEA shall be rated among the best in the world and lead to AP being ranked high onthe e-Government Development Index globally.AP shall be known as an Innovation Society of global repute, with a focus on quality of life ofits citizens, with a special emphasis on quality of education, healthcare, skill development,agricultural practices, infrastructure and services.Developmental e-Governance shall be a catalyst for enhancing the effectiveness of implementation variousdevelopment projects and welfare schemes undertaken by the Government.Planning and/or monitoring of public sector schemes and projects shall be enabled to takeadvantage of the GIS and satellite imaging technologies.Citizen-Centric Citizens and businesses shall have a seamless and smooth interface with the Government.Departments and agencies of the Government shall be able to interoperate with ease andprovide integrated services to the citizens and businesses.The medium of paper for interactions and correspondence should be reduced to the minimumin all the G2C, C2G, G2B, B2G and G2G areas.Inclusive Digital Divide shall be adequately addressed, especially leveraging the mobile technologies.APSEA should enhance the realization of participative and inclusive governance.Citizen Engagement should be accomplished with ease and cost-effectiveness.Technological Government and citizens shall be enabled to take advantage of the cutting-edge technologieslike SMAC currently and those that emerge in future.The principles of open data, open standards and open APIs shall be ingrained in all thesystem development effort.Above all, the framework should ensure the right balance between information security andprivacy of personal data.3
AP State Enterprise Architecture V 1.03. ENTERPRISE ARCHITECTURE PRINCIPLESWHAT AREARCHITECTUREPRINCIPLES?A. ORGANIZATIONAL PRINCIPLESPrinciple #1: Primacy of PrinciplesThese principles of information management apply to allorganizations within the Government.Principle #2: Maximize benefit to the Government as awholeAll decisions relating to information management are made toprovide maximum benefit to the Government as a whole.Someorganizations may have to concede their own preferences forthe greater benefit of the entire Government. Applications andcomponents should be shared across organizationalboundaries.Principle #3: Information Management is Everybody’sBusiness. EA is an Architecture of Architectures.All organizations in the Government participate in informationmanagement decisions needed to accomplish businessobjectives, and implement such decisions with full commitment,devoting the right and adequate resources. APSEA has afederated structure. It will focus on guidelines, mandates,standards, interoperability and integration.Architecture principles area set of guidelines thatreflect consensus acrossthe enterprise.They govern thedevelopment,maintenance, and use ofthe enterprisearchitecture.A good set of ArchitecturePrinciples has thefollowing 5 nsistentStableThe option of designing APSEA as a single, monolithic architecture is infeasible andhence REJECTED. Respective Domain Owners and Managers shall develop their own subarchitectures following these principles, and federate the same to APSEA.Principle #4: Common Use of ApplicationsDevelopment of applications used across the Government is preferred over the development ofsimilar or duplicative applications, which are only specific to a particular department ororganization.Principle #5: Service OrientationThe enterprise architecture is based on a design of services which mirror real-world activitiesrequired to conduct the business of Government. Service orientation places uniquerequirements on the infrastructure, and implementations should use open standards to realizeinteroperability and location transparency.4
AP State Enterprise Architecture V 1.0B. DATA PRINCIPLESPrinciple #6: Data is an Asset.Data is an asset that has a specific and measurable value to the Government and is to bemanaged accordingly.Principle #7: Data is SharedUsers have access to the data necessary to perform their duties; therefore, data is sharedacross enterprise functions and organizations. It is less costly to maintain timely, accurate datain a single application, and then share it, than it is to maintain duplicative data in multipleapplications. Shared data will result in faster and improved decisions since we will rely onfewer sources (ultimately one virtual source, i.e the Single Source of Truth) of more accurateand timely managed data for our decision-making.Principle #8: Data TrusteeEach data element has a trustee accountable for data quality.As the degree of data sharinggrowsand departmentsrely upon common information, it becomes essential that only the datatrustee makes decisions about the content of data, and authorizes its modification. Informationshould be captured electronically once and immediately validated as close to the source aspossible. Quality control measures must be implemented to ensure the integrity of the dataPrinciple #9: Common Vocabulary and Data DefinitionsData is defined consistently throughout Government,and the definitions are understandable andavailable to all users. Defining Metadata and Data Standards (MDDS) within each domainassumes great significance.Principle #10: Data SecurityData is protected from unauthorized use and disclosure.Inaddition to the traditional aspects ofnational security classification, this includes, but is not limited to protection of pre-decisional,sensitive, source selection-sensitive, and proprietary information.Open sharing of information and the publication of information as per extant legislation must bebalanced against the need to restrict the availability of classified, proprietary and sensitiveinformation.“Shared Data leads toFaster Decision-making”5
AP State Enterprise Architecture V 1.0C. APPLICATION PRINCIPLESPrinciple #11: Technology IndependenceApplications are independent of specific technology choices and therefore can operate on avariety of technology platforms.Principle #12: Ease of UseApplications are easy to use.The underlying technology is transparent to users, so they canconcentrate on tasks at hand. Standards on Usability should be adhered to while developingapplications. Conformance to the Guidelines on Universal Electronic Accessibility shall beensured.D. TECHNOLOGY PRINCIPLESPrinciple #12: Requirements-Based ChangeOnly in response to process/service needs are changes to applications and technology made.Principle #13: Control Technical DiversityTechnological diversity is controlled to minimizethe non-trivial cost of maintaining expertise inand connectivity between multiple processing environments. Policies, standards and proceduresthat govern acquisition of technology must be tied directly to this principle.Principle #14: InteroperabilitySoftware and hardware should conform to defined standards that promote interoperability fordata, applications, and technology.Standards help ensure consistency,thus improving the ability to manage systems and improveuser satisfaction, and protect existing IT investments, thus maximizing returnoninvestment andreducing costs.Standards for interoperability additionally help ensure supportfrom multiplevendors for their products,and facilitate supply chain integration.A process for setting standards, reviewing and revising them periodically, and grantingexceptions must be established.“Interoperability is sine qua non for Integrated Services”6
AP State Enterprise Architecture V 1.04. ENTERPRISE BUSINESS ARCHITECTUREBusiness Architecture describes the service strategy, and theorganizational, functional, process, information, and geographicaspects of the business environment. In the context of eGovernance, the term Business Architecture can be interpreted asthe collage of relationships between Government and Citizens(G2C and C2G), Government and Businesses (G2B and B2G),Government and its Employees (G2E and E2G) and the internalprocesses of Government itself (G2G). Given that a Government isan enterprise of enterprises, these relationships and interfacescan number several hundreds.Any Government is characterized by certain quantitative andqualitative parameters that describe the nature and depth of theaforesaid relationships and interfaces. The task of the businessarchitect is, therefore, to assess the current status of suchrelationships (both in quantitative and qualitative measures) anddesign a TO BE Business Architecture that seeks to transformall the relationships/ interfaces or a prioritized subset of the same.GOVERNMENTIS NOT ABUSINESS !!True!However, talking ofBusiness Architecturemakes an eminent sensein the context of designingand developing EA fore-Governance, for thefollowing simple reasons: A. MACRO-LEVEL BUSINESS ARCHITECTUREIn an enterprise of enterprises that a Government is, there areseveral functions, activities, services and applications (togethercalled ‘artifacts’ for this purpose) that are exactly identical or similaror comparable across the various enterprises. Hence a macro-viewof the business architecture of the Government would give us achance to identify such artifacts and to transform them together,deploy them as common applications using the principles of cloudand shared resources, and also to optimize the effort, time and costto develop them. An illustrative list of such common and/or cross-cutting applicationsand artifacts is given below:A1. Applications/Artifacts Common across the Government:1.2.3.4.5.6.7.8.Human Resource Management SystemFinancial Management Systeme-ProcurementManagement of Logistics for governanceAsset ManagementLitigation Managemente-mail, video-conferencing and Calendar servicesElectronic workflow (e-Office)7 Suffice it to say that term‘business’ is not usedhere in a narrowcommercial sense, but ina broader sense toconnote the functions,activities andresponsibilities of theGovernment.Governments had been,and increasingly, willhave to adopt theprinciples of businessmanagement, to be moreeffective.Governments are moreprocess-intensive thanthe corporate sector, andthe methods of processre-engineering, servicetransformation andcustomer(citizen)centricity are, therefore,more applicable togovernments than to thebusiness sector!Above all, citizens wanttheir Government to bemore ‘business-like’indealing with their needs!
AP State Enterprise Architecture V 1.09. State Portal10. Right to Information11. Right to time-bound Services12. Identity Management for Employees13. Access Management Systems14. Attendance Monitoring Systems15. Employee Health Insurance16. Identity of Citizens for Delivery of Services/benefits17. e-Service Delivery Infrastructure18. Payment Gateway19. Mobile Gateway20. Information Security Management System21. Data Centre Services22. Cloud Services23. Wide Area Networks24. LAN & WiFi Services25. Cyber Security26. Knowledge Management (for public sector employees)27. Grievance Management SystemA2. Applications Common across Groups of Departments1. Social Benefits Management System2. Enterprise Project Portfolio Management3. Urban Land Management System4. Agricultural Land Management System5. GIS-based Systems6. Location-Based Services7. Name-based Systems8. Sector Promotion Services9. Educational Institutions Management System10. Content Management SystemA3. Cross-cutting Applications1.2.3.4.5.6.7.8.House Building Permissione-Biz - Single-window clearances for setting up business/industryRegistration of Land-related deedsNutrition Programs for women & childrenAgricultural loans& insuranceIntegrated Criminal Justice SystemDisaster/ Emergency Management SystemsGovernment Land Management SystemPrinciples #2 and #4 (stated in Section 3 on EA Principles) squarely deal with the requirements fordesign and development of the 3 categories of applications/ artifacts specified above. It is8
AP State Enterprise Architecture V 1.0necessary to resist the temptation and / or pressure to continue with the legacy systems in silos orto build ‘pipes’ between them on the plea that they are time-tested applications. Such a view isshort-sighted and takes the steam off the business case for the EA exercise, and therefore,should be resisted.B. MICRO-LEVEL BUSINESS ARCHITECTUREA number of micro-level business decisions or resolutions, illustrated below, play a critical role indeveloping the Business Architecture1. BPR for all the 3 categories of applications listed in the previous section shall be done in ageneric/ cross-cutting manner so as to optimize the benefits to all the targeted stakeholders/users. The BPR teams shall deal with the related departments, forms and processessimultaneously so as to normalize the processes across all the agencies. Elimination,Simplification, Optimization, Workflow Automation, Self-Service and Integration shall bethe thumb rules for such a process transformation.2. The well-established concepts like single-sign-on, digital signatures, and emerging technologieslike SMAC should be taken advantage of in all possible ways, following the practice oftechnology-led innovation.3. The concept of Mobile-First shall be observed religiously while designing any service orredesigning an existing service.4. All processes, and more so the complex processes, shall be broken down to their elementalcomponents. Such Elemental Government Processes (EGPs), which may not number morethan 20 across all the processes of Government, shall be re-engineered and transformed to behighly efficient and transparent, so that transforming the more complex processes becomesautomatic and trivial.5. Customer-centric design, efficiency, convenience and service orientation shall dictate the wayBPR is done. This is more relevant for design of online forms, workflows, service centres,payment systems, customer feedback systems etc. Citizen Services should be customized tosuit the profile of different categories and classes of citizens, like Students, Farmers, BusinessPeople, Self-Helf Groups, Pensioners etc6. Governance should be modeled around the end-to-end holistic lifecycle processes for thegoverned entities i.e. birth to death for citizens encompassing all the services that a citizenavails, initiation to closure for commercial establishments etc7. A quick secondary research on the best practices in the areas identified for BPR, isrecommended.8. Service Levels and Performance Metrics shall be recommended for each service/process,duly benchmarki
AP State Enterprise Architecture V 1.0 1 INTRODUCTION “Enterprise Architecture is a framework for conducting analysis, design, planning and implementation of the vision, goals, strategies, functions, activities and desired outcomes of an enterprise, using a holistic approach at all times, such that the IT infrastructure and IT
FEA Federal Enterprise Architecture FEAF Federal Enterprise Architecture Framework GEA-NZ Government Enterprise Architecture for New Zealand HR Human Resources IaaS Infrastructure as a Service IM/IT Information Management / Information Technology IT Information Technology IFEAD Institute for Enterprise Architecture Development .
VA Enterprise Architecture Per the Clinger-Cohen Act, it is a requirement for federal agencies to maintain an IT architecture (Clinger-Cohen Act of 1996). The government developed the Federal Enterprise Architecture (FEA) specifically for federal agencies, however; The VA uses its own architecture framework called the VA Enterprise Architecture.
According to the Institute for Enterprise Architecture Developments, "Enterprise Architecture is about understanding all of the different elements that make up an enterprise and how those elements inter-relate".6 Gartner Consulting says, "Enterprise architecture provides a decision framework, in the context of the
Architecture Trend 2: Project to Product Trend 3: The Democratization of Enterprise Architecture Trend 4: Continuous Improvement of Way-of-Working Trend 5: Enterprise Architecture as a Digital Twin of the Organization Summary of Enterprise Architecture Trends p. 3 - 6 p. 7 - 12 p. 13 - 21 p. 28 - 34 p. 35 - 41 p. 42 - 46 p. 22 - 27 Reference .
Architecture Frameworks - Architecture Frameworks 20 January, 2020 TOGAF The Open Group Architecture Framework (TOGAF) is one of the most widely accepted methods for developing enterprise architecture. TOGAF is an open framework, providing a practical, definitive and proven step-by-step method for developing and maintaining enterprise architecture.
What is Computer Architecture? “Computer Architecture is the science and art of selecting and interconnecting hardware components to create computers that meet functional, performance and cost goals.” - WWW Computer Architecture Page An analogy to architecture of File Size: 1MBPage Count: 12Explore further(PDF) Lecture Notes on Computer Architecturewww.researchgate.netComputer Architecture - an overview ScienceDirect Topicswww.sciencedirect.comWhat is Computer Architecture? - Definition from Techopediawww.techopedia.com1. An Introduction to Computer Architecture - Designing .www.oreilly.comWhat is Computer Architecture? - University of Washingtoncourses.cs.washington.eduRecommended to you b
oint Enterprise Architecture Department of State and U.S. Agency for International Development . Page 1. APPLIED . JOINT . ENTERPRISE ARCHITECTURE . . Federal Enterprise Architecture (FEA) program, under the auspices of the President's Management Agenda's (PMA) E-Government initiatives, has also played a key role in steering the effort.
Key elements of the Business Architecture may be produced elsewhere The enterprise mission, vision, strategy and goals may be produced as part of a wider business strategy or enterprise planning activity with its own life-cycle in the enterprise. The new architecture work will need to verify and update the currently documented business strategy and plans, and/or to bridge between high-level .
