 The challenge really is, it makes it was a big country, it's a very complex country, and it also operates fairly state-level, municipal level in a very independent way. So, we have sectorial differences. So to be able to establish a policy that will talk to not only healthcare or oil and gas or energy or the economy and so on, really was to start thinking more horizontally. So how can we provide an ICT policy that talks to all these sectors and brings value to them, so that they could actually even open the door for us, because as we operate independently and as we build these walls, we're also open for a conversation that's based on best practices and efficiencies. President Peña set out very early on in the administration to create a unit inside the office of the president called the National Digital Strategy Coordination Unit. What it does is coordinate any digital efforts across the federal government. So the budgets and initiatives are held inside the ministries, but then if there are efficiencies that could be built, sectorial ones or horizontal ones, then we could actually provide that value to different agencies. So part of it was an ongoing concern that we couldn't interoperate in the best way possible. And this happens across the board in many applications, in many infrastructure builds, not only in the healthcare sector and so on and so forth, but it was happening all across. We were duplicating investments or expenditures and we were duplicating the applications that were buying with that budget. So the first stake or the first interest that we took with open source was to be able to establish a practice more than selecting a technology, a practice that will be open, a practice that it doesn't matter what type of technology you're using, it's going to be there to be open, to be interconnected, to be more valuable than only its sole starting purpose. We have a very segregated ecosystem, IT ecosystem within the federal government in Mexico. That means of course we made our own choices inside each of the ministries to which technology could serve us best and I think that's the right approach to do so. Now when we're drawing a federal policy and we want to interconnect better and we're pushing or positioning a hub so that a citizen can actually consume or exploit or enjoy digital services via a single portal, then we need to have a proper mechanism to be able to connect to the different agencies. So what OpenStack is giving us is an open standard to connect to different technologies so that we can actually bring that value back to the citizen. So as I said, we're not really selecting technology per se, we're not selecting a vendor. What we're doing is taking advantage of the decisions that we're taking at the ministry level and then being able to interconnect amongst themselves. The effort there is massive and the results that we already have within a couple of years are actually proving themselves out. On the location front, on the healthcare sector, on the telecom sector as well via the reforms that were drafted, signed and now we're actually executing. There are 6500 online services that will be deployed towards the end of this administration. Now the first thing we'd set out to do was to actually know what the services were, to inventory it and then to actually draft some practices, manuals or to collaborate with the different ministries because they are very different amongst themselves. So healthcare services to Ministry of the Economy services, for example, to set out a new company or to exercise or to report taxes, declare taxes or to... They're very different services, but each of the agencies actually knows them very well. And they'll be able to put them through an API, through a consolidation standpoint or to Interoperative Hub. So we mapped those services out. So me as a citizen, me Victor Laguna as a citizen could actually log into a portal and if I'm just booking an appointment to get my passport or setting up a new company, I will be able to do so through a single portal. The reality is also on the communication standpoint. So websites, government websites, very segregated. We had around 4,000 federal government websites that we consolidated that into one. So we can only have a search engine type website in which we actually find what we're looking for. Everything from really booking an appointment to get your passport all the way into understanding where your closest hospital is or setting up a new company, you'll be able to do so in there. The value behind it is that we're not consolidating all the information in one single point. And that's very valuable, but it's also very scary if we were to do so. Because we don't only become a single point of contact to the citizen, but we would be aggregating all the information, the thing that we're not doing. So we're taking into account Privacy Act, we're taking into account the Transparency Act, and we're only exposing those services in the most secure way possible to the citizen. So they avoid making the same line in different agencies and going there and back and having an agency asking for the same information. So the philosophy behind it is we already know as government your birth certificate because you already gave it once. So do not ask it twice. And via the technology behind it, we would be able to provide that and instead of you or a citizen going into an office eight times, then cutting down into two times and there's a huge value in that. So we set out a year and a half ago with the whole process and it sounds a lot of time, but really the effort has never been done. And also you said the perception or reality around how we move as government, it's true. But it also makes some sense in the cyclicality of contracts and the complexity of applications and the complexity inside many of these ministries. So now we're at a point and we should be at a point because by presidential decree, August 3rd, we're launching GOP.MX, which is our single window for online services. And then from there, we're going to be ramping up more and more services. It doesn't mean that we're going to have everything on August 3rd. It just means that we'll have the first online service really available to citizens. We understood priorities based on a couple of consulting engagements that we actually got help with. We didn't want to make decisions just based on GOP, but on information. And really the single most sought after service is bird certificate inside and out the country. So Mexico, it's a very interesting ecosystem because outside the country there are around 30 million compatriots or Mexican people living in the U.S. alone. And they do need services without having to go back to the country. What I intend to say is we go through the same challenges and we need to find solutions for them. Government being very complex and having very limited budgets towards ICT needs to be very creative and innovative in the solutions that we deploy. So we get help with the whole sector, the industry, the academy and so on. One thing that we were not doing correctly and now it's actually proving very successful is running public challenges. So we understand the situation, we understand the problematic around it and we just share it through an ecosystem. We're not prescribing the type of solution. We're not saying we want this technology to help us deliver this solution. We just inform the ecosystem to bring that value to us. So what it was, for example, a tender for either a million dollar solution and we got five people interested or five parties interested. Now we're getting 150 companies interested in bidding for that contract and we're getting massive value out of it because you get everything from the students that are coding in open source all the way into your regular channels bidding for the same contract and you're getting more or less the same value. So it's kind of equalizing the play field if I can call it like that. And also it's making us understand in reality that we can solution a lot with not a lot of budget allocated to it. And in these macroeconomic situations is what Mexico needs. We first sought out OpenStack around six months ago and we're really in touch with many of the cloud orchestration players. We do have installations of other mechanisms and other orchestration services. OpenStack for us at that time and while this assessment process is going, it's proving that the decision is heading in the right direction. So the only thing I can share with you at this point is we're trusting that OpenStack is the orchestration mechanism and we need right now to deploy online services cloud and hopefully what could become the cloud ecosystem of the Mexican government. So private hybrid and public cloud interaction. The Walmart team was kind enough to share with me that in their high transaction, high secure environment, how they actually deal with these complex environments. And the reality is sometimes you build a big cloud, host everything there. Sometimes you separate clouds to avoid disruption or bigger outages than you could actually afford. It is ambitious but it's also a part of a bigger ecosystem. So we've been working together with all the federal agencies so that they are up to date in the way that they build their own processes and the way that they will be exposing their own services to this hub. So it's not building a massive infrastructure that will host everything. So we believe that's the right approach and we're putting our effort into that with the support of the industry. The second one and what keeps me awake is information security. So part of it is maintaining infrastructure up, that you build redundancies and you replicate services, you expose those to citizens. But in our journey we need to talk about information security and we deploy it in the right way. So security is a philosophy and security driving many of these installations so that at the end the service gets consumed and joy by the citizen in the most secure way possible. The private laws in Mexico are very strong, they're actually quite cutting-edge. So we have the Privacy Act that operates in very similar way to the one on the U.S. And then we have the Transparency Act. So the Transparency Act actually dictates the way that we manage our operations and our information, government information. And then of course the Privacy Act dictates how we should manage citizens' data. And everything from top secret all the way down to financial information, healthcare information and so on and so forth. So the law is there. We're just using the law to drive behavior or drive the guidelines to ensure that we set up the right level of criticality and sensitivity to the data so we know where to put it. We're actually building incentives around going to Google Apps and ensuring that you're not managing 180 on-premise email servers because we believe our skills and our talent should be used for mission-critical apps and for citizen-oriented services and not to manage certain infrastructure that's not giving us the value that it should have. We're ramping up. We're building small, we're testing the case and then we're building up. So that's one of the things that I like about OpenStack, that it let us build and then escalate. It let us build tests and then via agile deployment being able to grow fast. The other part of that is that we don't have a lot of budgets to these type of solutions. So we need to test the case on production and then ramp it up. We know the ecosystem in Mexico. It's the first time that we've been in this event and we're getting a lot of support from the ecosystem. We don't solution ourselves, everything. We do get the help from the industry in ensuring that what we're thinking or doing, it's done in a collaborative approach. So really taking the philosophy of OpenStack into kind of the human interaction and it's working well. As I said, we're building capacity as we build skills, but we're also bringing the skills from the industry to be able to shield ourselves better and build a better solution wholly in a collaborative approach. Most of my life I've been in the private enterprise sector for a couple of years in government and the current feedback that we get is that budgets are not being allocated in the best way possible. Not only that, but they're not being used rightfully. So the answer is we duplicate a lot. We multiply application development, et cetera, et cetera. So what keeps me really excited and really passionate about this project is that we didn't want to build a massive solution with a massive budget. We actually set out to do a small piece in which all the agencies can interconnect that drives citizen value. And if we can do so by demonstrating the business case, return X, return investment of the budget, then we can actually get more budgets towards mission-critical citizen-centric applications. And that's what really the core of our day-to-day lies.