 How would you approach the same, trying to achieve the same outcomes in a state that has existing silos, existing infrastructure and set up there? What would the differences in approach be, if any? Yeah, though technically Andhra Pradesh is a new state, but it is a state which was in existence and it was part of the composite state. So it's not as if we are starting with a clean slate here in Andhra Pradesh. Out of the 72, just to give an idea of the magnitude of what is new and what is old, out of 72, the portfolio of 72 applications which I showed and others also talked about it, 27 of them are already existing legacy systems, which we call it as brownfield and remaining 45 are greenfield applications like the CLGS we have seen or the data analytics that Srinivas spoke about. So it is roughly, you know, 2745 is the ratio of, so you need to customize the enterprise architecture in such a manner that, you know, you are getting into a running train or a moving train at this point of time as far as he Prakriti is concerned. That's how you need to, you can't brush aside the existing systems overnight and then go for a new one. So that is a constraint, that is also a plus, that is also, you can build upon what is existing is a plus point so that you can show quicker results, the positive side. On the other side, you know, you have to live with certain compromises in terms of the overall architecture. That's how I see that. Anyone, anything to add? So this is one of the questions that I typically get asked when I, you know, present to other states because they keep saying, oh, AP is a new state, they are doing everything greenfield, that's not true, right? As he said, the services are existing, yes, some of the systems are new, the policies are there, the practices are there, the legacy and the heritage, whatever you might call are there. So it's not as if it's a new, new state in that sense, it's not a new country, you know, that the constitution has to be defined and all that. So, yeah, so I really don't buy that as an excuse for, by any state for not doing enterprise architecture, saying that AP is a unique situation and, you know, it's a new state, that's why they could do it. Other states can also try, I think it's the lack of conviction rather than anything, just looking for, you know, reasons not to do it. Right, okay. So we've got, yes, multiple hours worth of questions if we allowed them to be that way, but we are standing between people and lunch, so let me start with this one. How are requirements being maintained and classified? Are there any specific tools and strategies used for requirements management? So the high-level requirements are being captured in what, you know, Gopal was saying the EPRS, right? So those are the basic, I would say, broad high-level requirements because the whole idea here is that once the EPRS is made available. EPRS is E-Pragati requirements specific specifications. We have SRS, we have FRS, we have something in between these two, which is called the EPRS. So it's a publicly available document, it's going to be, I think one of them have already been released, so the idea is we have a broad high-level requirements there. And then all of the respondents who are going to be, you know, let's say bidding for those projects, so to speak, will have to detail out the requirements. So that is the approach, because remember that we are doing the architecture, we are not doing the low-level design, so please understand that. So don't start the SDLC here. The SDLC will kick in later on, right? So that's important. All those factors, apart from this, we also try to, you know, leverage some of the functionalities which helps like game changers and, you know, BPR and all those things have been covered in the EPRS document in detail. Okay, thank you. Another question. How do you overcome the hurdles around sharing data internally between departments and, more importantly, concerns around data security and privacy for data that, how to go beyond the government boundaries, or data that has to go beyond the government boundaries? So there were various mentions, I think probably from all of you, about the importance of data and how there may be a reluctance to share data between departments. How do you overcome those obstacles in practice? So as Dr. Pallava was mentioning about, you know, enterprise architecture is less about technology and more about, you know, handling the political scenario. So, yeah, it's very, very challenging to interact with various departmental stakeholders and extract the information. Yes, we try to publicize and then explain them about the nature of this particular huge initiative and the pros and cons of, you know, the, or what are the pros of these enterprise architecture definition, having connected government in place has been explained to the stakeholders. And then one asset for this particular project, you know, not to exaggerate, we are working with advisor CM. So whenever, whatever meeting we go, trust me, JSAT has sent to us, JSAT asked us to collect this data. So every department, they used to give this information to us. Trust me, these are the trick we are following it. So we never faced, I mean, definitely there are the challenges, but we convinced them, explained them, and we showed them the roadmap. We showed them the importance of having a 2B architecture in place, what benefits the department gets out of it, what benefits the government is going to get, what benefits the citizen is going to get. So, and we are able to extract the information from various departments. That is how the service filtration has been done. So today, 1030 has come to 645. If I may add to that, in fact, as Mr. Satyanarayan was mentioning during his session, over the period of April to June, we are planning workshop sessions for district officers. And one of the key thing is for them to understand the value of data sharing in collaborative. So that is part of the overall change management process. So that's one aspect of it. That is one aspect of it. And the second thing is about data security and privacy. I was talking to Bala from, you know, my friend Bala there from DCS. I was telling, how much of data do you share without any concern to Facebook and Twitter? It's all there, right? They are monetizing the data. So if you don't worry about that, why are you worrying too much? I mean, I'm sure the government will take care of this. Just one, adding a couple of bits of information. One is on the, you know, the possessiveness about data that the government departments typically have, agencies have. How do we handle, fortunately for us, you know, the technology is such today that we have the SOA, we have the web services. They don't have to part with their database in any manner physically. There is a service request that goes and comes back with only the specific bits and bytes of information that is needed for rendering the service. So, gone are the days where you have to take a replica of the whole database and keep party to another department. That situation is no longer there. So, that is a plus point for us in terms of technology which enables. You are giving the information but you are not parting with the whole database as such. So, that is one way. You know, departments are increasingly convinced that, you know, they are safe with their own information. They are the owners and they are the, you know, data controllers, right? So that's, I just wanted to add the technological dimension to it. On the privacy issue also, while web services will also address that to some extent, but we have also brought in a policy on security and privacy in the context of ePragati, which is available on the web website of Andhra Pradesh government, you can see. And as I mentioned in my earlier talk, initial talk, that we have taken the best principles from the European Commission, principles on data privacy and built into our policy. And that is going to give the measure of confidence that is required both to departments and more importantly to the citizens whose data we are handling. Thank you. How does ePragati enable price reduction of agricultural products such as rice and dal? Does it help in reducing middlemen in the supply chain from the farm to the retail store? Yeah, in fact, is price reduction good or bad from the point of the farmer? So we have to balance it also, ultimately. But all the same, you know, the disintermediation is also one of the outcomes that is expected in the primary sector. We have got one of the modules there, which is part of that big picture you have seen, which deals with the eMarkets or eMundi, it is called our eMarket. So it is directly addressing the issue of disintermediation. How do you achieve the disintermediation is addressed squarely in ePragati. Just adding to that. So we could also look at using, again, data analytics to predict and then give the best price to the farmers, right. So if, let us say, there is going to be a shortfall in dal, then we can tell the farmers, okay, this is going to be the scenario, this is what you need to do so that he is prepared, right. So then rather than saying price reduction, you know, you could say the farmer, the benefits can reach the farmer, right. So you will have a farmer who knows what the price is going to be and you would have seen, I would have heard about a lot of news for farmers to say happening because they really did not know, you know, for example, the sugarcane farmers, right. So they did not know that they should not grow sugarcane this season. Nobody told them about that. So they went ahead, they grew sugarcane and then they found out that there was no demand, right. So we could prevent those situations. You know, we could give them good knowledge, insights and analytics, right. So leveraging analytics. Okay, thank you. I love this question. In Dr. Palab's presentation, knowledge and skill development was highlighted. Is anything being done to leverage Togaf certified individuals in building more architects for the country? I think the open group should be taking that question, but yes, I can tell you as a professional enterprise architect, there is a lot of, you know, one of the benefits, one of the advantages of E-Pragati has been the general awareness, the general knowledge about enterprise architecture has gone up. People have realized that this is an important, you know, profession, so to speak. And when you have a successful example like E-Pragati, it lends credibility to the entire story. Otherwise people are just thinking this is just 622 pages as he was mentioning or 700 odd pages of a book, but then how do you actually, you know, realize it in practice. So I am seeing a lot of demand coming in, you know, to me for instance, saying that can we become a professional enterprise architect, even people speaking to me during the break, I says, where the person actually says I have 12 years of this experience, that's my, you know, thing, can I become an architect? So yes, there is a lot of, there's a lot of awareness being created just by having this project as a showcase, you know, from a professional architect perspective. And I am sure the open group would be very interested in increasing the number of people who are certified. In fact, if my statistic is right, at this point, if I am not wrong, Bangalore has the highest number of TOGAP certifications, certified professionals in the world. It is number one in the world. India is number three. Number three in the world as a country, Bangalore is number one. So I am saying, let Hyderabad be there. Yeah. Right? So that is actually a challenge to all of you. And also, further information on this is we are planning to establish an E-Pragati Academy, which is one of the, which is for capacity building in and around E-governance and around E-Pragati. But one of the courses that it's, we envisage it to run is on enterprise architecture exclusively because going forward, there's more and more people are required in this domain, both within government and outside. So E-Pragati Academy, our Honorable Chief Minister suggested that it should come up in the new capital city of Amarauti. So we have requested for land for this E-Pragati complex. One of it will be E-Pragati Academy there. Good to hear. Thank you. Yes, a round of applause for that one. Next question. It's good that we have a kind of system that provides citizen-related information getting closer to real-time. What about citizen data upgrades? How easy is it for a citizen to upgrade his or her data with respect to security and authenticity? How does the government handle that? We have one of the system called People Hub, which actually a repository of the citizen. Almost, I can say, 95% of Andhra citizen information is available on a People Hub. Earlier it is called SRDH, State Residential Data Hub. So today we named it as People Hub and that is getting further enhanced by collecting the show-show economic data of every individual, every citizen of Andhra in terms of gathering the further information in terms of family and respect to family tree and the residential information, other credentials which are getting added to the citizen repository. Coming to the security aspect of it, it is a highly secured system trying to provide the standard security features like the authentication, authorization and then the cybersecurity is the major component which we are trying to build as a part of ePrakati initiative. So those things have been implemented as a part of taking the security aspects of the citizen information and also some of the security standards have been adopted to implement ePrakati initiative. Just adding to that, so if I understood the question, it's also about how you're going to keep the data, citizen data synchronized and up-to-date and secure. Security aspect of course was addressed already but it is important to keep the data synchronized and current and up-to-date in all the systems and we have so many departments maintaining their own databases and you cannot get rid of them in one shot. So that's also, we have a solution for that. We have a solution to ensure that wherever people data get updated, whichever system it is, it is propagated to the other systems in a near real-time basis. Of course, but you also have to understand that there will be some workflows, some approvals, etc. So considering that it will not be near real-time always but where possible it could be near real-time but if it requires approvals, etc. then that workflow will be defined. So at least with the latency of let us say 24 or 48 hours you should have the data synchronized across most of the systems. Great, thank you. We don't have time for too many more questions but here's one. How do you see Ipragadi transforming to a state where we could monetize the data and make the initiative self-funding in the long run? What is your overall view on data monetization using Ipragadi? I think it's a very interesting point. It's not about monetizing the data which takes us on a wrong connotation or a purely commercial connotation which as a government we do not want to do that at all. In a commercial sense you understand what I mean a commercial concern how it monetizes such huge data which is not at all the intention in fact it is expressly prohibited as an activity by the government. On the other hand how do you make the Ipragadi program self-sustainable to a large extent is through levying some user charges wherever some value addition is provided to the value added services are provided to the citizen or to any department you know a charge back mechanism so that you know at least O&M costs are recovered if not the capital costs. So that is the philosophy with which we are going and if you see overall out of 2,000 crores about 1100 crores will be the capex and rest is the recovered through a charge back mechanism or user charge mechanism. So that is how we'll see but not we can't exactly compare it with monetizing the data which is a different aspect altogether. In fact this kind of leads me to a larger issue where many countries are grappling with if all of this data is available can you make it available as in open data and many countries have tried doing that and monetization is one of the issues they have to deal with because in Singapore for instance I have seen where the government is making available all of the data in analyzable format now I as a SME I can take that data and provide a new service for instance if I want to know where are the let's say location of the public toilets in the radius of one kilometer right from here I mean I could provide that service as an app now so the issue that will come is if I as a private provider and providing that service and making money out of it do I have to pay back to the government because the source data is coming from the government so it gets into a lot of issues because there are legal implications and all of this so I would say we have not gone to that level of discussion yet open data is one of the topics that is a big topic for digital India but eventually we will have to grapple with that and monetization will be one of the factors as he said while that is not the intent I think the use of government data by private providers to provide new services co-create new services is definitely one of the things that the state wants to do because it contributes to this whole digital ecosystem because see this is not about building 72 applications and releasing them it's also about encouraging small and medium enterprises to be part of the ecosystem and they can actually build applications and things like that absolutely so you must understand that this is much bigger than just doing an architecture there is a lot of ecosystem thing going around here and the vision is definitely very grand and this is how digital government should work a component called App Store in that big picture that I had shown which is where we are exposing the APIs and the data that is shareable to the public to the developer community to the startup community so that they can come up with apps which are more useful to the citizens and then they can in turn monetize that there is no problem in that so government by itself would not like to monetize but indirectly will expose the APIs wherever the situation to you know permits that and the data make it as open data so that the developers can really develop apps and host it on our App Store platform and then derive benefit out of that Thank you Time for two more questions I think this one is a sort of multi-part one but you've all mentioned in some way the e-highway as a service bus that connects different layers how is it realized how much of it will eventually be automated and do you envision it at a state level or at a national level ultimately so again e-highway is one of the core component which actually acts like an integration channel to connect the various departmental applications not only the departmental applications but also it should also helps us to connect to the third-party systems like you know banks, insurance companies and other things using various gateway technologies so definitely yes you should be able to connect as long as the integration channel is in place which helps you in mediation, routing, transformation and you know fellow station and workflow centric approach not just a state level but you should also be able to connect to the central government departments and also based on the requirement you can connect to any third-party system based on within the security scope implementation however this e-highway is in addition to an integration channel it also acts like a registry and repository for the software service components which you build so it should be able to have a registry of services such that when you implement this huge e-pragathy system the SIS need to look at the registry and the repository and try to reuse those software components which have been built and the repository will be continuously incrementing based on the implementation of each block what we have shown you earlier and it eliminates the redundancy of the service development and reusable components and a shareable component will be available and we can also bring in the chargeback model across the departments who are consuming these services so that can be done so just to come back to the question so it is basically predominantly an integration channel which helps you to connect to the departments government departments, state, central or any third-party systems Thank you Last question before we let you all go for lunch then it's a bit of a mean one Do you think e-pragathy is doable in two years? Yes, yes and yes We wouldn't know if we don't try, right? I mean trying doesn't guarantee success but not trying guarantees failure so you have to work with that So it is driven by at the highest level and there are actually as I mentioned a number of challenges to overcome procurement itself is a big barrier to implementation rather while it's a facilitation but it takes time that way time barrier is there We are already six months into the implementation Our Chief Minister has given the deadline also 16th September 2017 It should be completed So we are working against that tight time schedule I think if it doesn't work it doesn't work anywhere else in India definitely if not in the world it needs to work doesn't it? That's what I've heard, yeah Just to add a point here we already started floating RFPs in the market so almost a couple of them are I mean one already floated and the response is also coming and the three or four are in line so the essays are also lined up for it so it is definitely achievable it can be done Great, thank you Apologies to those of you who asked questions I didn't get to I think I got to at least one of each of your questions at least I tried to but in order to make sure that you had oh James has a ton more but in order to make sure that we do have some time to eat lunch today we'll call it a day there but a big thank you to our speakers and our panelists this morning and to you for your attention and we'll be back here for the tracks this afternoon but a big thank you to the panel May I just add one sentence I think really I must admire the patience of all the participants I'm not participated in any conference where no member of the audience has opened his or her mouth so it's really they've written it down and it's really a different feeling altogether Thanks, I think all the same it has been participated