 So please a warm welcome for Dr. Pallab Sahar. Welcome Pallab. It's great to be here today, presenting after Mr. Esatanarayana, who gave a very quick overview of what E. Praditi is. In fact, it is a privilege and honour for me to be presenting this because this happens to be the first statewide enterprise architect for India, anywhere in India. And the interesting thing is you've seen the scope of what is being thought of in the number of services, the number of systems that we're talking about, and the fact that it kind of impacts 50 million people, which is, as you were saying earlier, it's like the size of a country in many situations, right? And I've deliberately titled my presentation from aspiration to inspiration because obviously you've heard about the aspiration part of it and how Chief Minister Naju and Mr. Esatanarayana actually came up with the initial roadmap of what was done before we came in. And now what has happened is I've been speaking to various state governments even at the central level. So there is some traction coming along as part of the overall initial India initiative that the Honourable Prime Minister has picked off, so to speak, in this country. So the whole thing is E. Praditi has become an inspiration for hundred states. But obviously it is important that beyond all the rhetoric that we talked about, we need to understand that it is not easy to do enterprise architecture in the public sector, in the government sector. And I'll kind of highlight some of the key points. And as Steve was introducing me, I have had the privilege of working with many governments around the world. And some of them are actually taken as, I would say, benchmarks in terms of their e-governance maturity, e-governance capability through various surveys and rankings that institutions, very respectable institutions like United Nations and the World Health Organization does. So what I'll do here is obviously all of you are very curious to know what E. Praditi is all about. And you have been given kind of a small booklet and CD. Something that really stands out here is what I'd like to highlight right up front is the Honourable Chief Minister when he launched the E. Praditi in Vishakapatnam a few months back. That was in October. He's on record to say that the state, the AP state, is very, very willing to share all the experience with other states, which is very, very unique because it's important that as part of the open group, we also... So what I've seen here is as a result of E. Praditi, the entire profession of enterprise architecture, some of you probably are in that in your respective organizations, has been elevated. People now know what enterprise architects do because one of the questions I'm sure many of you have faced that people ask, what do enterprise architects actually do? I mean, it's okay to have certification and all that stuff, right? So this is what they do. What you're seeing here and me and my two couple of team members are going to take you through some deep dive sessions later on and we have a panel discussion. So all the questions will be free to ask some questions. And as I said, E. Praditi is an example for digital government. It has to succeed. It's important because other states are watching. The center is watching. It's absolutely essential. And as Mr. Satyanarana was saying, this is not about information technology alone. It's important. Information technology is important. We know that today every organization effectively is a technology organization. Everybody uses technology and you will see some data later on. But as to his credit, I mean to Mr. Satyanarana's credit, you have to understand that a lot of people think that when you talk of enterprise architecture, it has to be quote-unquote only limited to the IT department. He has actually been speaking to the Planning Commission. That is where it needs to go in because people have to understand enterprise architecture is the big picture planning methodology which can help you execute your strategy. So if you're speaking to the Planning Commission as an example, you're talking to the right people. That's the message which is very important and I think the credit definite goes to him. So let me set the context. I think some of these areas have been covered but I'll kind of formalize it in terms of how governments across the world are thinking and what you see is how governments are now at this point they tend to be very hierarchical. Nothing specific to any state or any country because given my experience in other countries, I've kind of summarized and synthesized some of the findings. They tend to be very rigid. Typically the government services are offered through single channels or few channels and then there is always an issue of which channel is better in terms of providing certain services because you always have the rural urban divide where the rural area and maybe some of the senior citizens have probably never used technology. So some of those issues come up. Most citizens tend to view government as input oriented, very closed and typically as a citizen you end up becoming a spectator. You really don't contribute much to the process of governance. Versus the next generation government, I'm not going to provide a version number or so but the next generation government as has been spoken about earlier tends to be more network, more collaborative, more flexible. It's important because citizens are demanding it. I'll show you some data later on. It is definitely providing, trying to provide certain services using multiple channels, becoming more transparent, more outcome driven and also because people are trying to, wanting to participate in the process of governance itself. You will see that some of the issues that have come up in terms of co-creating certain services along with the people. So the government and people actually are partnering, providing some of the services because it's what people are demanding. And the good thing is because of the technology maturity, some of this is being enabled and facilitated by technology. And that's where enterprise architecture plays a big role in making that transition from current way of governance to the future government and he was talking about future proofing. So it kind of sets the context. However, to make this happen there are few things that governments around the world have to bring in. Number one is they have to move from departmental stuff pipes to becoming more citizen-centric. Now this is easier said than done. We know that when you want to, because it kind of entails some level of restructuring in the government and when you know that when you're talking of restructuring let alone in the corporate sector, in the government sector, it's all, so the political aspect becomes the overbearing matter within the, in terms of how the restructuring is going to happen. It's not as if in terms of administrative restructuring but even if you're looking at a service which is, let's say, cross-departmental it is not easy for departments to collaborate and share data because there are many issues that come into play. And you'll realize that enterprise architecture is, I would say, a lot about understanding the political dynamics and a little bit about technology. So it's something that enterprise architects have to remember. This therefore requires transformation and integration of the back office operations. Very important and that has been highlighted in the previous presentation already. It requires, therefore, collaborative working and information sharing. It is, again, easier said than done. It is not easy for government ministries to share data because for various historical reasons and obviously a lot of people actually think and we know that in the corporate sector also. Information sharing, once you start sharing your data and information, you use your power. So that mental model exists in people. This is a human behavior. Nothing specific to India. It's very common in any other country. People do not want to share information and that's the reason I'm sure many organizations have tried implementing knowledge management systems and I failed miserably because it is not about having a system it's about the mental model of why people do not want to share information because it gives them power. And that's very, very true in many kinds of organization. Citizen engagement and inclusion is absolutely essential and in many cases what is happening is I'll show you some countries later on list down some countries. Many countries have succeeded in doing a good enterprise architecture because citizens were part of the overall equation. They are not part of the problem they are part of the solution. It's extremely important to involve the citizens. And enterprise architecture as a whole is one way of providing that whole philosophy of one government, connected government. Connected government is a term that has been introduced by the United Nations in the 2008 survey and now they actually rank countries in terms of how integrated governments around the world are. So they have a kind of two-year survey and I'll show you some of the results later on. You know that governments are complex ecosystems so this is the kind of structure that we typically have very typical, again nothing specific to India but you can obviously relate it to India. We have a government at the central level, national level you have a state provincial level government you could also have a district rural, urban kind of government and you also tend to have a city government. So if you want to do enterprise architecture at the city level it could be positioned under the smart city initiative whereas if you want to do it at the state level which is what we are presenting today it's a statewide enterprise architecture. At the national level as of now there is no initiative there is no traction going on there is some talk going on and he was talking about the need for a federated architecture so we are trying to figure out how that federated architecture should look like because it is as he has already been telling about it is not about eliminating any all types of diversity it is about ensuring that you kind of support the diversity you support reusability but in a stacked manner in a manner which is increasing with the example later on alright so there was a survey done by UN in terms of various countries as to what citizens expect from their government probably the font is little small for the people behind but I will just highlight on India here so you can see the number one issue that Indian citizens are looking from the government is planned for the long term not just for the next few years so this is what we as people as citizens are expecting from the Indian government national government or state government besides the matter but this is the basic philosophy number two is understanding the priorities understand what people want so when you provide a service it is not as if this is what I can provide take it or leave it that kind of mental model does not work so you have to provide a service in terms of fulfilling citizen requirements, citizen aspirations and of course third one is involve citizens in the decision making process in the thinking process and he was talking about change management and the kind of awareness and advocacy sessions that we are for instance planning in the state of AP that is one aspect of creating and involving people government officials at the lower level and also people to understand what all this is about you know I always come back there is a reason why we labelled it because it kind of gels well with the people people remember it imagine if I were to go talk to a district officer or a farmer or a fish farmer in the rural area and say you know what we are doing Andhra Pradesh state enterprise architecture nobody will remember that right it's important right you have to have the right label because that's important from a communication perspective so these are the you know so obviously there are other countries mentioned here I'm not highlighting on the other countries but this deal the kind of priorities so to speak citizen expectations and aspirations from the government side so you can quickly understand that there is a need for a holistic approach and now that approach happens to be enterprise architecture so I don't belabor too much on the the label of enterprise architecture in terms of you know what it is and whether you should be debating on you know what you call it but rather what it can do for the people what it can do for the governance in fact as he was saying the the famous code by honorable prime minister is actually minimum government maximum governance and that is very important see the whole idea is doing more with less in fact this was I've been involved with as Steve was introducing I've been involved with the Singapore government journey and in 1999 when they started out the enterprise architecture activity the the vision was doing more with less because 1999 if you remember was immediately after the Asian financial crisis and many countries had issues pertaining to you know budget cuts for instance and you must be wondering right if in a in an era of budget cuts how do governments think about enterprise architecture but that is the very reason why it got started because once you have budget cuts you have to think holistically you know it's no more free lunch and I'm starting to see that in Middle East because you can imagine the way oil prices are going down many countries many governments in the Middle East actually don't have budget deficit and they're using enterprise architecture as a way to reduce the overall size of the government but still providing all the services that the citizens need alright so here is a survey done by the World Bank and this shows you the adoption of digital technologies by businesses so corporate businesses by people, citizens and by government so you can see in the graph in the center the adoption of digital technologies is actually higher by the people so businesses, corporates and the government sector actually has to catch up in some sense that is the message from this slide so there is already some level of catching up required so think of it as a citizen not as an employee or an officer think of it how much of technology do we use quite a lot right each of us probably has three or four mobile devices now right on you right now you're probably online you're probably googling already and looking at some of the tweets maybe around this conference so we do use technology digital technology at an individual level but at the government level and at the government level the adoption is much lower so you can see the comparison here so that's where the overall use of information technology to consume use of enterprise architecture to consume information technology becomes more and more important this is the journey of e-governance in India so it kind of gives you the highlight so as you see it started sometime in the mid 70s and all the way up to 2014 which is currently the whole idea is it has been going on computerization and adoption of information technology for government services has been going on there have been lots of successful projects adhar is a great successful project the railway reservation system is a great project passport is a great project however it could be better because technically you do know that I'm not sure how many of you know but I'll tell you you could actually get a passport in 20 minutes if two ministries had collaborating data it is not a technology issue it's just two ministries not sharing data so he was talking about the you know sharing of data right otherwise you could actually get passport the only time it requires is the amount of time it takes to print that passport right today you would there is an improvement and you remember that sometime even 10 years back we used it is to probably take a month probably two months to get a passport today you can get it maybe in one one to three days you know if you go for a third call kind of situation so there is scope for improvement but yeah things things are there and things have been there so there is some level of heritage and some level of legacy so it provides the basis for us to look at enterprise architecture okay I think most of you know what are the blocks of enterprise architecture so I'm not going to the details I'll just play out all of the key elements so to speak one thing you would typically see missing in many of the frameworks is the need for a policy and strategy architecture personally I see that as an absolute essential imperative element for you know enterprise architecture because this is where you get the overall vision the overall direction and the guidance for doing the rest of the stuff so business architecture here is the more operational aspect of the business so that's where you provide the services and the processes so on and so forth enabled by the three layers of technology however as you see this looks like a house which means a house will only be strong if it has a strong you know foundation of governance and management so I'm not going to the details of each of this but you will see the definition of each of these layers is in a very non-technical term for instance business architecture it's the reason we do what we do the people we serve and the outcomes we see you know you may have seen very you know very flowery English language definition of each of these areas but I prefer to use a very simple definition because this is something that you know stays with the people that you're communicating with remember that in most cases when you're talking about enterprise architecture your audience may be tech savvy but they may not belong to the IT department right so it's important as as an architect as a profession as a profession you need to be understanding that you have to communicate to people who do not belong to IT department but maybe tech savvy in terms of using technology to solve business problems okay so this is important from a professional point of view and I've done that and I can tell you people understand if you use the right language right you know labels people do understand the value of information technology in fact at this point we are talking to a couple of business schools to introduce enterprise architecture as a subject in their curriculum it's very interesting that the consulting companies all consulting companies are not focusing on Wipro or any other specific organization have a very strong enterprise architecture practice but at the education level formal education level there is nothing you will have certifications like togaaf and a few other certifications but there is no formal education going on in India at this point so it is definitely a big gap right so this is something that we are also trying to address so government enterprise architecture which is the focus of the session this morning is a mission focused approach and a framework to galvanize span government ecosystem so this is government as a single entity which has already been highlighted in the previous presentation by transcending the boundaries for designing and delivering services important this is not about building systems it is about delivering services in a coordinated and efficient way that citizens and businesses demand and deserve right with the overall goal of achieving one government digital government connected government so this is the definition that we work with and we have used this to also kind of define what e-pragati is all about and you will see some of that definition coming on later so there are certain things that you have to keep in view in terms of what government enterprise architecture is the important point which I'd like to highlight on this slide here are the capabilities and again the point is repeated need for leadership both at the political level and at the administrative service level bureaucratic level is essential right I mean I speak to other states and people ask me what are the key factors, key success factors you know in fact one of the two key success factors for e-p would be the vision and the acceptance by the chief minister, honorable chief minister and having a person like Mr. Jay Satyanarayana without that it wouldn't have happened okay all credit to both of them because that leadership is extremely important the chief minister provides the vision and it is being executed by the advisor and few other things that are absolutely important, funding is important, nothing happens free right, you saw the funding and some numbers are given to you on the booklet there, so this is absolutely essential from a success point of view and many states have to get this right the combination of these things right before you jump on to enterprise architecture okay so this is it and this is the framework I'm not going to the framework so let's see what Ibrahiti is all about you've seen this definition earlier so Ibrahiti is a new paradigm in governance based on governance framework so it has already been highlighted previously transcending departmental boundaries so when you see those packages and services what you implicitly don't see as which department it belongs to and that is deliberate because we want to get away from this whole idea of you belong to this department and you belong to so that departmental structure still exists but when a citizen comes to the government the policy the single most important principle and policy for the government is that there is no wrong door a department cannot say Mr. citizen you have come to the wrong department because the citizen is approaching the government period what you do internally is your problem how you integrate the services is your problem obviously lot of governments have tried doing this by providing a portal but the portal is almost like putting a lipstick on a pig right if nothing has changed behind just providing a portal by itself doesn't make it one government right many things have to have to be put in place he spoke about the applications many things have to be put in place before you get the entire vision of connected one government okay and the pillars of e-prague it's important and of course you know that AP has a has a overall vision called Sunrise AP and as you were saying there's nothing to do with technology here technology is an enabler in doing all of these things for instance engage citizenry citizen centric services so on and so forth all right so it started with the mission again seven missions as part of the vision that was in the previous slide okay and each mission has a mission priority there are four mission priorities identified each mission priority is measured by something called a key performance indicator or e-prague the indicator so that is important that's the reason why I was saying when you do enterprise architecture in the government sector you need to have the strategy and policy in place extremely important because this was already in place so this was our starting point and you'll see that this is not about technology this is not about building systems right if it is all about building systems I would call it systems architecture I would call it it architecture the reason there is a reason why the term is called enterprise architecture and the word enterprise is the first one in the phrase okay never never forget that as as an enterprise architecture professional right there is a small sliver in the entire equation principles already been highlighted so I'll highlight a few ones one government we have already spoken about that single entry multiple use so that's about reusability disintermediation what happens when you have a structure like this it is deliberate that none of the departments are named because for a citizen the only thing that matters is are you going to provide my service or not that's all which department provides it the back office operation which application is automating who cares it's not important from a citizen-centric perspective right so that's important so you see that disintermediation and this is actually scary to many government because it suddenly what happens is the departments are no longer you know I would say highest priority in the entire architecture and some people do see that as loss of power as loss of authority suddenly you are presenting the entire government and there is no department there is no ministry there is just what is your priority and what is the service that you want to provide to the citizens so these are some of the key principles from the mission we then identified the key business area so all of these missions are mentioned that you can see the big package their primary industry so those are the seven missions and each of the missions have different functions and different departments to deliver that mission it is extremely structured it is because it's a collection a group of departments who come together to fulfill a specific mission all of the seven missions on your left you see the different stakeholders so you have Farmer Fish from a senior citizen woman so on and so forth and on your right you have the business you know structure that we have identified as part of the business architecture so what are we doing with this business architecture we are operationalizing the strategy and vision of the government that was presented to you in the previous slide now to automate these business functions to automate these business processes you definitely need technology I'm not saying technology is not important position it as an enabler and therefore starts the data aspect right all of these are data services I'm probably you know all of these are clear you know probably the projector is not very sharp here but the thing that I'd like to highlight already it has been presented earlier is the need for single source of truth that comes on your left so we are planning different data hubs metadata master data in fact that's how it is structured if you want a data driven government you do need to provide that data structure around all of the government data so you need to understand what the metadata structure is you need to create a framework for master data you need to create certain data hubs because they become your archive for the entire government the important thing is if you don't have this in place none of those business services that we identified in the business architecture will be automated how do you collaborate when there is no single source of truth right so that is extremely important and one of the showstoppers in fact you know Srinni is going to present on the data litics one of the key showstoppers for many state governments in fact probably all of the state governments is non availability of data in a format that can be used by multiple departments something that many states have to think about in terms of how to migrate to what they have now to something that is usable in this structure okay obviously you need applications he has already highlighted so you can see there are certain applications which are departmental certain applications which are cross-cutting because they need orchestration across multiple departments for instance procurement right many departments are involved many departments are stakeholders certain departments certain applications which are specific to a group of cluster group of organizations so for instance there could be a set of applications which are specific to the healthcare you know group because their nature of business is very different set of applications which could be relevant to transportation department such applications which could be relevant to the industries department so that group application and there are certain common applications which are common across the entire government so this is a very large part of the departmentality but stacked in an increasing order right we are not mandating centralization this is the core this is the essence of federated approach you do provide for autonomy to departments because each department if you need to understand that has a different type of set of services so the nature of operation could be different you have to provide that autonomy one of the things that I have is that people start thinking if you are doing a statewide or a national wide enterprise architecture does it mean that you are going to standardize everything centralize everything and just say that it is required no not at all you have to provide as an architect you have to provide scope for individual autonomy because it gives them the flexibility to ensure that they can be more responsive to specific citizen requirements obviously the last layer is the last layer so I will not go into the details of that so there is a presentation later on on this but this is where most of the standardization can happen right because technology is one area where so if you see the layers of architectures of starting from technology application, data, business and strategy as you move up the level of standardization and the scope for standardization becomes less right I don't care whether this laptop is a Lenovo or HP shares as long as it works I don't care whether my email is exchange or lotus notes right so there are no debates you know people are not going to be burning buses because we chose one vendor over another vendor but if you want to touch at the strategy in the business level definitely people get affected right so you understand how the entire layering happens and that has been implicitly built into ePragati putting it all together so you can see the seven missions there right and this is the whole perspective so you can see the different types of applications some of these are common applications some of these are group applications so all of these things have been put together one thing that is important that is putting that is keeping all of these things together is the layer on your left that is eHighway basically it's a service bus which connects all the applications okay now there are certain components which are going to be elaborated in the subsequent two presentations so as deep dive sessions so I'm not going into the details of that but I'd like to highlight one thing some of these things are pretty game changers right so for instance the need for certificates completely eliminate the need for certificates think about it right if you want to apply for a passport or you know some kind of an admission to a university how many documents you have to carry as your as your supporting documents all of that information is also given by another department in the government right you could actually completely eliminate the need to carry any document just give your other idea and say figure out whether I've you know passed my tenth standard exam it's already with the department of education why do I have to carry my tenth standard certificate to the passport office they don't want to know how much I scored in mathematics they just want to know what my date of birth is right so what is happening is with all these certificates I as a citizen I become the courier I'm taking it from one department to another department it's not required alright so that's going to be you know elaborated later on okay so you've already gone through this so these are the waves again not very department specific but the whole intent was to group certain you know applications and certain capabilities into logical packages and the waving is also extremely important because it is kind of you know reflecting the priorities of the government a wave one is a wave one because it is the core package without that nothing else will work that's why it's called wave one right so on and so forth so there is a thinking behind it in terms of how things should be prioritized and what are the quick wins it's extremely important to identify certain quick wins because you cannot go back and say I'm going to do enterprise architecture for the government so next five years don't disturb me that's not going to happen from a practical perspective you have to provide that initial low-hanging fruit figure out what will give you more credential more credibility within the organization and then build you know you know support for the rest of the activities in the in the organization whether it's a government or the corporate sector doesn't matter the story is same all right okay I think benefits are by now fairly clear to all of you okay in terms of that all right so benefits are there both for citizens and businesses and also for government departments extremely important because you know a lot of countries I'll show you the list of the countries a lot of countries use the maturity and capability of their government as a way to attract investors people don't realize this right one mental model that exists in the government sector across the world is that we are a monopoly you are not a monopoly countries are competing cities are competing right you saw the smart city challenge that is currently going on in India 20 cities were selected that is a great thing because people are now realizing the importance of cities in the overall contribution to the economy however there are challenges because think about it Indian cities do not have leaders we are not structured like that but I hope over the next three to five years that's going to happen right you do have municipal commissioner you may have mayors but they're not city leaders in that sense because it was not thought cities were not thought as important okay but that conversation is now changing the mental model is now cities are important they can contribute to the overall growth of the country okay so there are lots of benefits that we see and that will be true for all states that you know who are eventually going to adopt enterprise architecture so why did it work right obviously there's a lot more work to do but I'll just kind of highlight the few things so this is the overall approach or the methodology why did it work number one it has already been highlighted by Mr. Satya Narayana earlier the vision and purpose was absolutely clear leadership very important mission I've shown you the mission they are I would say inspired by the sustainable development goals some of the KPIs are actually aligning to the SDG of the United Nations remember one of the vision statement was AP will be a developed state by 2029 that is the kind of vision you need I would expect digital India to say we should be in the top 10 if you can send a mission to Mars why can't you be in the top 10 in the ranking so we need to aspire better as a country as a state as a country okay third obviously there is a thinking process so architecture is executing that vision and mission so which is what we are going through fourth you need funding and resources 350 million dollars you just heard about it and obviously now it is a you know legend that how much money was sanctioned so to speak and finally you need leadership in the center these are the five critical success factors without which no government should if you are not confident of this you should not do enterprise architecture it will be hard for you to sustain it it will end up becoming an academic exercise which will come up with a big report or a blueprint and beyond that nothing will happen architecture is done because you want to implement it think about it you are building a house the architect has given you a blueprint but then you don't actually build a house what's the value of that blueprint nothing and the other thing that the open group is trying to do is make enterprise architecture a profession it should be a profession in my view like any other profession you know medicine law what does that mean it gives us authority but it comes with accountability if you sign on that architecture you are accountable for if anything goes wrong that's what civil engineers do right if you sign on a blueprint of a building or a bridge or a flyover you are accountable for that right I have I have known architects who are scared to play that role and you want to play the role of an advisor which is good but you need to go beyond advisor you have to get to the implementation and operationalizing aspect as a professional all right what does this truly mean in a picture this is what it means the departments are not going to go away anywhere it's the way it has been positioned the services cross cutting services you have common services you have group services you have departmental services some observations which I have actually gathered this is not specific to AP or any state I have gathered from many states very interesting which in our analysis we also see the you know the whole idea of conflicting KPIs so there is one department which will be saying that it's not good to smoke and drink right whereas the revenue department will be looking for revenue from tobacco and liquor so you can see that there is already a dichotomy in terms of how the KPIs are conflicting so when we did the analysis all of these things actually came out so when he was talking about the 745 services and the KPIs for that all of these things were interesting findings in my view okay so EA is a strategy and what this slide shows you is how governments around the world have used enterprise architecture to improve their e-government maturity so those maturity levels are actually defined by united nations this is not our invention right so if countries have moved from let's say web presence to connected government they have used enterprise architecture to make that transition because at this level government operates and appears as one so the whole idea of one government and you cannot have that if you don't have the holistic planning approach which happens to be enterprise architecture okay one thing I'd like to highlight is the need for integration and one thing obviously all of these things are related to the layers the thing that I'd like to highlight is the need for political and legal integration if you don't have political support if some of these procedures and processes don't have legal support it will not survive for instance I gave you the example of elimination of certificates what happens if the judiciary decides providing certificate is a legal requirement then you cannot eliminate certificates even though at the operational level you can do that but sometimes you cannot do that because it's not a legal requirement for instance digital signature is not accepted in India so you do need that process because that is a critical success factor for any of the interoperability and the integration that you're looking for across the different layers of the enterprise in this case it happens to be government okay so what are the imperatives for other states so this is the overall model so this is make in India in terms of digital government so this is where the architecture comes in and again leadership is in the center methodology structures policies supporting policies but states also have to get many other things right like here for instance it needs to you know get the it assurance important security that has already been spoken about earlier service delivery governance of information technology managing it as a as an investment right so all of these things have to come together to support the architecture and many states don't have that internal okay and we have spoken about procurement already quality management project management change management extremely essential so all of this picture all of the elements components of this picture have to come together to provide that vision of digital government so architecture here becomes the driver supported by the amplifiers the reason I call them amplifiers because it amplifies the value of architecture supported by the enablers right so if you're a state government you should be analyzing which of these components are your weak points you know do a some kind of a heat map and figure out what your priority should be at the digital government level not just at the architecture level there's nothing called digital government strategy it is basically government strategy for adoption of digital technologies okay so that's important that differentiation is extremely critical I told you about the country so these are in the latest UN survey okay in terms of e-government maturity and adoption of digital technologies for citizen services okay a lot of you people probably don't know six out of these ten countries have enterprise architecture as a legal mandate which means for instance US is an example which means a federal agency has to have its agency enterprise architecture as a legal document just like companies need to have a quarterly and an annual report right if you're a public company it is a legal requirement it's a mandated requirement it's a legislation this is the kind of seriousness they provide to enterprise architecture and to repeat and reemphasize my point we have to be aspire in the top league this is what I would like to see digital India say we need to be in the top 50 maybe over the next three years and maybe over the next you know five to seven or ten years you have to be in the top ten so that that goal is extremely important otherwise you know there's a lot of rhetoric going on vendors coming and talking about beautiful slides and nothing going around that and you need to have that and this needs to transcend political parties because this is in national interest I'll highlight this and this will also give you a lot of food for thought for the panel discussion having said all this government enterprise architecture in the in in in many countries it's hard okay let me highlight some points in the government departments you have to find who the champion is going to be I've given you some examples right leadership is extremely important for any country any type of government you know government enterprise architecture I've spoken about lack of you know education formal education that is highlighted so what will happen is when you go and talk about government enterprise architecture to any audience outside of the kind of the audience that we have here they don't know what it is right so don't assume that they know what enterprise architecture is and everybody knows about the certification they don't know you have to tell them what it can do for them why don't ministries and departments collaborate because that's how the budgeting processes there is no specific incentive to collaborate okay so the silo thinking is institutionalized in the way government structure so that's something that you have to keep in mind number four the difference between enterprise architecture and any other kind of architecture is that you do any other kind of architecture before the structure is started for construction in enterprise architecture you don't have that luxury you don't do enterprise architecture in a green field environment the enterprise already exists you are architecting it you have to spend let's say 6 months 9 months 12 months to do the architecting the enterprise continues to function you cannot go back to your organization and say I have learned this wonderful thing called ePragati let's stop working for the next 6 months we will do architecture civil engineers have that luxury the building doesn't exist it's just a flat plain land right you do the architecture it's signed off and then you start construction that is not the case in enterprise architecture that means it is a far more complex undertaking you are architecting even as you are operating any government any organization keep that as something in your mind as professional enterprise architects right now true enterprise architecture leads to some level of redistribution of authority and some level of restructuring something that you have to keep in mind that's why I said the need for political and legal integration interoperability is an absolute showstopper if you do not have political support legal support legal mandate it's very difficult to succeed in EA I have spoken about IT activity IT is important but if you kind of limit this to as an IT activities all you will get is new systems and probably a few legacy systems you have to talk at the right level and I've already given you the example of the conversation that is happening with the planning commission I've seen that in Singapore 70 ministries everybody had a ERP instance of ERP standardized they set up a center for shared services all of the 70 licenses consolidated to one license so imagine that license owner that vendor he doesn't like enterprise architecture obviously right because governments use enterprise architecture to manage vendors that's one of the benefit when you put out an RFP your architecture must be a public document where you can say all of the vendors therefore have to comply this becomes part of your procurement process part of your decision making process right so keep that in mind and this is also this will also play out as you're doing enterprise architecture in the government well we are a multi-layered government we have a national government you have a state government and you have a local government something that you have to keep in mind is that they could belong to different political parties who don't like to talk to each other in most cases they will not talk to each other we know that right so something that you have to factor in as you're coming up with a federated architecture so you have to get that whole you know the whole the idea of providing autonomy at the department level at the ministry level and still have that holistic thinking that balancing is extremely important for a multi-level government yeah and I've seen that in many states they're waiting for somebody else to take the lead I'm really glad that AP did not do that it wanted to be the first because I interact with the states and saying oh let's see what AP does and let's figure out why I mean you don't look for examples you become one right so this is something that you have to keep in mind many times you will not have that leadership you will not have that vision people who understand who really believe that this can do wonders to the entire functioning of the government so to speak okay I think that's the last one and that gives you some kind of summary of Iprakati we have two more deep dive sessions so specific areas that we'll focus on and I think we'll do the question answer during the panel discussion so thank you very much