 Thanks, everybody, for coming. I'm Karanjit Singh from Kelton Tech. And I'll be talking to you about digital transformation using IoT and Drupal. So let's just dive right away. So what exactly is digital transformation? I want to start off with a little bit about the digital transformation, the IoT, and then kind of build it out to the work that we have done there. So what exactly is digital transformation? Of course, there's a lot of interest. There's a lot of talk of digital. You have Dries, you have Janet, everybody talking about digital. Essentially, it's about applying all these new technologies, the digital technologies, to create personalized experiences for your users and trying to reach all your customers. So it's essentially about personalizing the experience. If we were to just break it down into the point technologies that are being used in here, so obviously, we have had the social media. So all of these have existed for some time now and been used individually as point solutions, sometimes in combination. So basically, the social media is essentially about customer engagement, building brand value. Then it's about mobility. So everybody has to have a mobile app nowadays. But then again, mobility, you have a lot of things that have come along with it, like location-based services. Essentially, going from the desktop to essentially having a mobile storefront, personalizing things for your users. Then again, the whole analytics and big data and analytics that can go along with it. So you can essentially derive a lot of insights into your customers, do everything from predictive, prescriptive analytics. Most of these things nowadays, this is a game changer, and everybody talks about cloud. But one big thing that it does is it socializes or democratizes the use of computing power for people, for startups, who just with a credit card today can get up computing power, which is available to any large enterprise today, and then put together all the solutions and essentially create experiences, unique experiences for their customers. Now these things, these four have essentially been out there for a while, mostly being used as point ways. And the latest that's being talked about is IoT, something which is still a little way out, but already interesting things that are happening around there, which will essentially kind of have all sorts of sensors out there talking to each other and with people. And what essentially the digital transformation piece kind of does today, or this something happened, let's say the inflection point was last year, when it's not really about that one point solution, like just mobility or just analytics, but about a combination of these whole things, the whole thing coming together and basically providing a complete seamless experience, which is what essentially is the digital transformation. And we'll get into a little bit detail into what we're doing there. And in a sense, people are calling whatever is happening now in the whole digital space, which is the whole social, mobile, analytics, cloud, and the IoT, has pretty much the fourth revolution. So of course, the first one, every industrial revolution causes a lot of social changes, a lot of changes on the ground in terms of the way we live and work. So the first one, of course, was the water and steam, power. Then we had electricity. In a sense, the IoT system or computers in 1960s, 70s, is where it all started. It kind of looks the same. Everybody says, hey, it's the same thing. But what is changing this time around is basically the way everything is coming together and you are able to address and talk to a customer in a very unique personalized conversation that you can have with your customers. So essentially, previously, it was about simple digitization. And basically, that was the third industrial revolution. I was automating things. Most of the things that were happening, if you went to any enterprise or any business, was something which was behind its firewall, behind its premise. But what is going to happen now is basically a combination of these technologies, the innovation that can happen by combining this technology, is basically forcing companies to reexamine the way they do business because they're able to uniquely, in a very individualistic way, personalized way, able to talk to their customers, one on one. So just the internet of things, this is just a slide which talks about IoT. So IoT is basically linking the physical and digital worlds. Essentially, any part of our environment are natural systems, human systems, physical objects. They're soon, they're already. And soon, they're going to connect and start interacting with things, just some graphics around things. So essentially, your refrigerator will start asking you to get milk when the way back home. And if you sort of forget, then it will kind of replace your spouse for you and kind of complain to you. It's going to be who controls whom. So you could have things like these. You could have, hey, we just got to go out because my refrigerator and my stove have stopped speaking to each other. Or you could have cases where the machines will take over and basically threaten to cut off access to your refrigerator just because you're overweight. And of course, the worst of it all, you could just get unfollowed by your coffee machine. So these can have very personal impacts on you. But that's just the lighter side of things. Essentially, the future of IoT, essentially, these are the numbers that we're talking about. We already have about 10 billion connected devices. But increasingly, what's going to happen in the future is, till now, we have not really concerned ourselves so much about, hey, is the thing talking to me? Is a sensor or a machine talking to me? But in the future, about pretty much 99% of everything will be interconnected and talk to each other. That's going to be the natural design principle. So everything from your street lights to your heart monitors to your dog callers, everything pretty much will become enabled with these kind of enabled and talk to each other. That's all. This is just the potential. I mean, just the raw numbers you're talking about. You'll have four billion connected people, four trillion revenue opportunity, millions of apps, and of course, billions of embedded and integrated systems. Of course, all of them are going to produce huge amount of data. So, you know, this is the huge potential that we're talking about. Now, as a company, Kelton Tech, we have been working in the whole newer technologies that we talked about, the whole SMAC space, for a few years now. And one of our kind of areas of interest always has been location-based services, especially in the mobility space. And one of the interesting things that's happening there was basically the whole indoor proximity technology, so essentially the beacons, which essentially enable devices to perform defined actions when you get into close proximity. So, one of the things is today, if you look at LBS, essentially what you have is a lat-long, but when you are in a building like this, you really do not know whether you are on which floor you are. So essentially, the whole proximity-based technology, we kind of Kelton Tech has married his expertise in IoT and LBS to essentially create, you know, digital experiences in the indoor navigation space. That's kind of essentially what we have done. So, you know, what does indoor proximity technology enable? So, these are some of the use cases that you can, you know, obviously envision. Some of them are already happening. We have been part of some solutions that are already out there. So, things like omnichannel shopping experience, you know, you're in a mall on which floor. Are you close to a particular shop? You can get some things. You have location-based promotions. You could have product display information. You could know what are the heat maps, where are your customers are. You could gamify their behaviors after you get some insights. You know, continuing on, you could have things like navigation assistance, you know, at large spaces like these or at airports. You could also do queue busting, you know, a session is running full. You could actually gamify the behavior and say something interesting is happening somewhere else or something is running empty. You could gamify things by giving out a little deal or information or pushing a notification. You could do crowd flow management. Of course, you can do a whole lot of monitoring at the back end as you are collecting a lot of this information. And obviously, you know, there's the whole security angle to it. So, you know, essentially what's happening is, you know, this is a period of great change in terms of the whole digital transformation space. And essentially, a whole lot of business models are getting disrupted, changed, a lot of startups by using the whole smack thing or disrupting large businesses. And of course, it's going to change and have very deep and meaningful changes into the way we kind of live and work. So some of our customers are basically using this whole indoor proximity technology that are helping them to, you know, define actions using iBeacons. And, you know, some of the reasons why people choose iBeacons over, say, GPS or RFID. Of course, you know, I already talked about GPS. You know, GPS just gives you a lat-long location. You really still do not know where exactly you are vertically. So you have accuracy. Obviously, these devices are low energy. Only they work on proximity. So you can set the proximity, it's five meters, it's 20 meters, whatever it is. So there's a whole lot of privacy. It's not like they're beaming your information all over the place. Obviously, there's the integration and usability. So what we have as Kelton Tech is basically, we work with a lot of customers and build a generic sort of platform, which we call the Kelton Tech location-based gamification analytics and rich messaging engine. That's kind of what we have built. Essentially, it's a framework or accelerator that we have developed that helps basically has features like rich push notification. Can provide you navigation assistance. Let's say you're in an airport. It can pretty much take you to your gate. It can do real-time analytics. You arrive for your flight just half an hour. It can pretty much give you navigation assistance and give you notification to say, hey, rush to your gate. And you arrive three hours early and it can pretty much give you deals and gamify the behavior to get you to your favorite restaurant, your favorite shopping spot in the airport. Obviously, since it's a framework or accelerator and the use cases are that I could take it to a lot of, and I'll talk about the use cases. We needed capability at the backend where I could quickly configure the locations, what sort of messages need to go out, what sort of behaviors need to happen. So we have basically a CMS-enabled backend. Essentially, it has to be scalable, customizable, and it is IoT ready because we have basically used the whole proximity and interior navigation. Kind of a couple of use cases. I already talked about using it in travel and hospitality. You can use it in retail and e-commerce. So essentially, at your malls, you can use it at entertainment centers. You can use it at events and amusement parks. So you can help to modernize all these things, like just to give you a little example. One of the things that we've actually gone and done some work with are museums. So today, if you go to a museum, it's pretty much a paper-based system or you have fixed tours. Now, once you have beacons there as IoT devices, which tell you what the exact location is, using our platform, you can pretty much configure, let's say you're at a museum. You pretty much know that I have only got about an hour to see whatever I want to see. You can pretty much go to the application, tell it that I'm only interested in two exhibits. It can create a dynamic navigation for you, help you with the timings. It can also do some little deals and stuff for you. So that's the kind of application. You go near and exhibit pretty much as you approach it because it's a proximity technology. I can set the proximity when you're near this painting by like only about two meters from there, pretty much on your mobile, it'll pop up all the information about that particular exhibit for you. So those are the kind of use cases that we've worked on. This is essentially kind of the architecture. So if you see on the right side, as I said, we have a CMS as a back end, obviously that's Drupal today. So that's Drupal. Of course, we have the gamification engine, the analytics engine, of course, a location engine and a messaging engine. Of course, all of this is exposed. It's headless, so it's all exposed via web services, which are working with a mobile device. So that's the device that a customer is actually using. Let's say you're in a museum or you're in an airport or you're in a shopping mall. That's the device that you're using. And that's the one that interacts now with the IoT devices, which are iBeacons today, but our platform can support all sorts of newer technologies that will come up there. So this is something that we have actually done for a customer called VenuIQ. So essentially, they wanted to do the same thing, but a specific use case was about a conference like this. They want to do attendee check-ins. They want to provide navigation assistance. You can do networking, so you know who's attending. You can network with them, locate them. You can actually send out promotions and advertisements, so you can kind of gamify some of that. And you can do a lot of other gamification. Some sessions are running full. You can pretty much inform people about, hey, there's another interesting session happening or the other way around. You can have, so this was the client requirements. And essentially, their use case itself, we have something, we've built it as a platform. So essentially, they can actually use this for the kind of applications that we've talked about there, which is conferences and exhibitions, museums and galleries, parks, retail stores, hotels, restaurants. So that's the kind of use case they are building out. So there are a couple of them that are already working on or have done POCs. Now coming back to the question of, hey, so we're providing a digital experience using IoT, but why Drupal? Of course, apart from the fact that we love Drupal, Drupal has some advantages. So of course, if you see the evolution of Drupal, Drupal was basically built to essentially build websites. But then slowly, integrations were built into it, and Drupal can interact very well with third party applications. There afterwards then there was the whole thing about Drupal became responsive and essentially it's today ready, mobile ready. And then now the next approach that has opened up is essentially, which is what we are actually using, which is Drupal as a service platform using headless Drupal. That's kind of what we are doing. So if you go back to the slide that I had here, essentially we're using headless Drupal, exposing things by web services and then having the mobile device which are actually talking to our IoT devices, which are iBeacons in this case. Pretty much that's the whole solution that we put together. And of course, all the strengths that come with having a CMS, we are able to easily configure it for different conferences. In fact, this application was at Tycon last week. So we were doing the complete, the whole KLGAM platform was deployed there. It was the mobile, I mean, people know it as the mobile application for the conference, but it was pretty much doing everything that we talked about. We were actually at the NASCOM leadership forum, which is NASCOM is the industry body for Indian software industry. We pretty much did it there. And we were at the IIT global leadership conference as well, where it was deployed pretty successfully and we got some great feedback. So coming towards the end, essentially why were we using Drupal for IoT? So essentially it's a strong CMS, allows us all the flexibility that we need in terms of configuring. It's a stable and mature system. It's scalable. And of course, has a very active community. The other thing is, of course, it provides seamless integration. We are able to easily integrate and collect data from multiple IoT devices. We are able to expose data has flexible APIs. We were able to easily integrate with third party tools. And the other thing that we're not getting there is as we kind of put this kind of platforms out there, essentially starts getting used in malls or starts getting used by enterprises at their stores, obviously you're going to have a huge amount of data that is going to get collected. So we can integrate this very easily with MongoDB at a later date or technologies like that, which will allow us to handle the big data and the complex data challenges that will arise with it. And of course, apart from all the other functionalities that we have written there. So that's kind of our rationale for using Drupal as the backend system for the KL game platform. So my session was half an hour, so I had to really rush through since we were a little late. Thank you. That's cool. So if you have any questions, I can answer them. Mahesh is my colleague, so you can both address any questions. Just a question, is this your current platform is on Drupal 7 or 8? Right now it's on Drupal 7. Is there any reason why you didn't use it since it is on there? That's because we were working on this for almost the last one and a half, two years now. So Drupal 7 was the only one at that time. But yeah, we'll migrate it with Drupal 8 very soon. Yeah, but we've been building this for almost close to one and a half, two years now. What protocols are these IoT devices using to communicate? What protocols are the IoT devices using? Well, I do not have that information handy, but they come with some authoring tools along with the sensors and things, and then those are used to integrate with the mobile. And the mobile application is the one that actually talks to Drupal. So REST APIs, yes. So because it's not just about mobile, we've also done an integration with Google Glass on the front end, but Google decided to shelf the project for some time, and we are in future whatever kind of new variables come up since it's on headless, it can seamlessly integrate. Were you familiar with Drupal before using it for IoT stuff? Because I wanna know if there's any other things that you could recommend or that you would recommend to Drupal instead for the IoT. Yeah, so we have been working in Drupal for more than close to 10 years now. We started using Drupal 4.3 or 4.7, so those were the kind of versions. So that's how old we were in the Drupal, yeah. So Drupal is one of our core expertise areas, but other than it, we do work in very large spectrum of things like web, social, mobile analytics, cloud and internet of things. So all the spectrum of digital technologies that Karanjit showed, we work across all of those. Again, on the web itself, apart from Drupal, we work with WordPress, lot many flavors of PHP, Java, .NET and everything. But Drupal was a kind of a natural choice because most of the times when you're building a platform, what happens is you need to deploy the platform and create the solution for the client very quickly. So Drupal gives some nice out-of-the-box flexibility like user management, permissions or roles and handling of the content, et cetera. So Drupal was a kind of a natural choice. Two different questions. Do you have API call management? And that's the first question. Can you just be a little louder? Yeah, do you have API call management? Like for example, Apigee or any other like third party, Apigee management interface? And second one is, is there any use case in terms of healthcare industry using IoT? Yeah, so I'd like to take the first question. Second question, I'll leave it to Karanjit because we have done one of the largest M governance rollouts in India in healthcare sector. So Karanjit can give some nice examples of how IoT can benefit. The first question in terms of the API management, we currently are not using any third party tool or anything. We have basically using what Drupal provides and extended the APIs a bit to make it more friendly for the mobile devices in faster responses. But eventually, yeah, we may explore in future, like if any third party or a specific API management is required. Yeah, Karanjit, do you want to take the next question? Yeah, so actually, yeah, healthcare is another, so yeah, I'd listed all that and one of the things that we've been thinking for a while now is essentially healthcare because again, the whole indoor proximity location is an interesting use case. Just as Mahesh mentioned, we've actually done one of the largest mobile-based public health, ego governance initiatives in India about 10 million people already on the platform. And one of the things that we are talking to the public health officials in India is about, today they do a lot of things in terms of measurement of your blood pressure and things like that. So those are interesting use cases and there is interesting work happening in that space. There are startups which are building sort of IoT, maybe the more advanced Fitbits, which are more specialized. So we are working with them and that's something which is an interest area. That's something that we can easily plug into the platform because essentially it's standard based and the whole backend is all there. All we have to do is essentially enable it, just enable it and connect it to the platform. So yeah, all right, thanks for your time. Yeah. And we are at booth six to four. If any of you have any follow-up questions or anything that comes to your mind, we are at six to four, so glad to discuss with you anytime. Thank you. I'm crazy enough to run around here and jack it in this awesome, yeah I know people shaking their heads. This awesome heat, looking pretty good. If it's okay with everybody, I'll keep it in this mode because I have some tabs on the top and I want to jump over to it. It's gonna be a lot easier than the escape kit. So it'll be at least a little bit more simplistic as it were. So I'm here to talk to you guys today about Drupal as a platform for the U.S. government. My name, about me, I'm Dave Gallaruzzo, the CEO of Figleaf Software. These are just some shameless pics from some years ago. But I'm the CEO of Figleaf Software, classically educated in computer science, math, and economics. I'm an old style desktop developer. I moved to the web like everybody else did back in the 90s. I got my start in whole fusion. I actually still work it, believe it or not. Very, very old, 20-some years. You know, ago I started playing with it on diskettes and now I'm doing Drupal. Added it on as part of our business back in 2010. Primarily because of the government, government started to look at open source about five, six years ago, really seriously. And at that point we were working for clients on platforms that they were purchasing for lots and lots of money, right? The government said, well, let's look at this open source thing. And what was kind of interesting was luckily for everybody, they got confused between open source and open data and so they started doing open source platforms when open data was really the initiative. But that's okay, we'll do both, right? It's no big deal. I'm someone that stays close to the code and the infrastructure, just because I put a code on and a nice little fig leaf shirt. This whole computer science thing right here, I did that because I love it. So I actually teach our module to have a course at fig leaf and, you know, I'd stay real close to what we do on the Drupal platform. Probably a little more than I should and to the detriment of my employees, I really hate the fact that I stick my nose in probably a little bit too much. Will here works for me, he'll tell you that, so. So why am I here, right? What am I here to talk to you guys about today? I'm here to talk to you guys about Drupal as a platform at the Department of the Interior. It's really a business case study for what we're doing out at DOI right now and the work that we're doing for these guys. And it's really digital transformation in the public arena. It's the whole idea behind why we're chatting today. Department of the Interior, as you may or may not know, is one of the largest government agencies out there. It's very, very big. They have a very large number of bureaus that are under them. One of our marquee clients is the National Park Service, which is a bureau within DOI. And we've been working in that environment since 2004. Park Service is a gigantic animal, billion-page views a year, lots and lots of traffic, 99.999% up time, et cetera, et cetera. But the Department of the Interior themselves, because of all the bureaus that they have, we've managed and built DOI.gov back in 2009. They actually had what we called in the beginning, right? What there was at the Department of the Interior was a lot of chaos, right? And what do we mean by chaos? And frankly, there still is a lot of chaos there. But it's much less than this gigantic black screen with the red writing and everything that I've got up here today. The Interior Bureau's, in 2009, had a lot of different things. This is Bureau of Reclamation, Fish and Wildlife Service, Parks, OSM, USGS, Geological Survey. They're still kind of out there on their own. Park of the Interior, all of these guys, Bureau of BIA, Bureau of Indian Affairs, Bureau of Land Management, et cetera. These guys are on pay software, which is, you know, CQ. But Adobe call CQ, then I'll call Adobe Experience Manager. And what I call a gigantic thing to implement, right? It's a big, big, big lift. I don't know why the government would spend half a million to outrify a software package just to manage it. Not saying BLM did, but they paid a lot of money for it. And then Minerals Management Service, which is now called BESI, the Bureau of Safety and Environmental Enforcement, they're on ECTRONIC. Now, luckily for us as a contractor, CommonSpot and ECTRON are things that we work, right? We've got a dot net business and a whole fusion business. And we're still running Parks on CommonSpot. DOI was on this CommonSpot platform. The problem is there's a lot of stuff here, right? Not only is there a lot of stuff, they had to stand up and keep the Denver Data Center going just for these guys out of place to host. It's a lot of money to keep the data center going. Tons of money. Not only that, they were responsible for everything. Parks is still running in that data center right now. It's going to move to AWS eventually. If contractor that they're using can figure out how to just get everything up into the platform, right? Hey, us. But that whole Denver Data Center thing was a gigantic, and has to be gigantic, costs up for the government, right? Lots and lots of money to put stuff out in that data center. Lots and lots of people to support it. So what they decided to do was they decided that they wanted to move forward. They wanted to go from this, which is what the website looked like in 2009. About a year right after the inauguration of President Obama here, you can see the screen. What they did is they went from that to this, which we built for them in 2009 in six weeks, unfortunately, because the big boss wanted to win for the first stage of the union. It had to have a brand new website up there for the Department of the Interior. So we had six weeks, a really crappy Christmas, and I spent all night on my birthday pushing this thing into the Denver Data Center while my wife had a great, nice, home-made, open-up green highway for me at the house. Great. Didn't get beat down for another day. Well, we went from this to where they are today, which is this. This is their new site in, I'm actually gonna kick over to it. It's in Drupal. It's fully responsive. It's really a very, very nice launch for these guys. It's too bad we didn't do this in 2009, and we didn't build this in six weeks. We'll talk about that. It took a little bit longer to launch the new DOI.gov website. But what did we do? And how did we actually make all of this work? What did we do to sort of bring it all together? So, DOI moved forward with this idea, and this is something we actually had influenced. The first pictures I showed you, I don't know jargon, right? 25 years in the Marine Corps. So, I'm a firm believer, and I'm not saying that other people aren't, but for me, the government dollar and how it's spent, it's a big, big deal. We supported DOI.gov with one developer for six years. One guy, the main DOI.gov website. He was a full-time dude. He's the guy that actually moved from Cold Fusion and CommonSpot over to Drupal, and he now supports DOI.gov on the Drupal platform, which is actually a pretty cool story, right? But, for a very long time, we supported them with one person, why? Because it was economical for the government. A lot of other large integrators, they have a whole team, right? Seven people, et cetera. DOI, when they decided they were gonna do a platform, one thing that we talked to them about, this is what I call a lesson learned, is we said, look, decouple your platform choice and your vendor that brings your platform in and implements it for you, from the people that are gonna build your ultimate site, okay? Because if you don't, what's gonna happen is you're gonna get locked in. You're gonna be locked into the people that do your platform, and then they're gonna be locked into doing the sites, and at the end of the day, there's gonna be no economy of scale for the government, and there's gonna be no way for you to do anything other than say, how much money is this gonna cost, and then they're gonna tell you it's gonna cost X, and X is all the money that you're gonna have to spend, okay? So we said, take that platform and separate it. Do a procurement, just to figure that out. Focus on your platform, and then after that you can issue procurement to build out your websites, right? To do the sites within bureaus. But start with a platform. So DOI decided to move forward. Now they thought about a lot of different things. They looked at Adobe, I don't know why they did, right? Because that's a big spec. For Adobe, they spent millions of dollars on the software alone, just to get it actually out there, and they really don't need what comes in that package, okay? For them, the ability to track what people are doing is not nearly as important as just having a nice experience actually come in and get data from the department of the interior. Now for our friends at Park Service, maybe a little different, because Parks does make money off of us. Even though we pay taxes, people come to Parks and they pay money to get in, and it goes into the budget, right? But that's okay. They provide a great service to the American people, and to the people that come from other countries to visit and go to our parks, okay? So, VOI decided to actually put a platform together, and they made some choices. They put a procurement out. And in the procurement, what they decided was that every one of these agencies, when they wanted to, right? VOI can't force them. And if you work with government agencies that have software, you'll figure that out. So most of these guys, especially these guys, right? And these guys, and by the way, these guys, right? To them, they aren't even part of Interior. It's, you know, hey, we just kind of exist and Interior is on top of us, but they're not the boss of things, right? I see, that's the thing. However, when they started looking at a platform, if they said we're gonna push something like a Gobi, forget it, right? All these guys over here were like, you know, excuse my language, Mike, right? I'm not gonna play that game. But when they said, hey, let's talk about Drupal, then everybody just stood up and took notes, right? It was only a few years ago that the platforms put together. It's Drupal, it's government, right? And all these agencies doing it, it's been proven, et cetera, et cetera. So what they did was they put a procurement out and they just bought a platform and they just bought what their host did. So they put Drupal Platform as a service together. It's running on IBM software. So IBM is their vendor that manages the actual platform. Phase two went in with IBM and took the open public distribution and they made it into something called open DOI. So they customized it, right? So we now have a distribution running within that environment and that built off of the public, proven distribution, et cetera, et cetera, that we can use, right, customized, right? So they have this environment running. IBM manages that environment, much like, you know, OQI does their environment or a plaque measure, anybody else can host with it. But it's dedicated to the Department of Interior, right? So they stood it up and dedicated it. They ran it compliant, all the good stuff that you want to actually have, all those buzzwords that we need to have. What's all buzzwords compliant, right? It's just a big thing. We gotta have that, we gotta have buzzwords. Phase two spent the time working with IBM to get everything stood up, went through a series of workshops with the Department of Interior to put some levels of functionality into the platform. And luckily for us, we partner with them very, very closely to work on the site buildouts, right? So when we went down at the site buildout, we became best friends with them, said, hey, let's work together, and it's been really wildly fantastic. One of the lucky times when we actually worked with other companies seamlessly worked together, all right? So first they built this platform. Now, the way that they did it was very agile, all right? It's cloud hosting, which is out of DOI's hands. It's extremely agile. So DOI's like, I'm done. I'm not worried about this. I don't have to worry about the disk array going down, like they did in Denver, at least once a month because it was an old array and somebody needed to move into a new array. You wouldn't believe the chicanery that would go on. It's, you know, if I can package the email and actually sort of share it, it was always very funny. Drupal is open source, right? Which is a big deal for the Fed community. People love it. It works. And it's got a good reputation, we know that. The SLA for uptime was only 9.9% where they get the month for free. And that was a big deal for the government clients specifically was the ability to say, if I'm not up to my SLA, I don't pay for the month for host, right? So that's, you know, that's also a way to make it a lot cheaper for them. And that easy creation of Fed websites for Drupal. I'm a little disingenuous. I don't know that it's all easy, but it's efficient. How about that, right? We have a place to go, and a place to stand up, new sites when we want to, right? And when we can't. The cost. You don't usually see this in talks, but I'll throw it out there for you. For the feds, they were able to, their past setup was a quarter of a million bucks right there. Their DOI.gov migration, that was about $330,000, right? With content. With content. I'm gonna talk about content a little bit. The VESCE migration is 210 grand. However, VESCE has a big content issue that we're dealing with as a separate contract. I'll talk to you guys about content in a minute. Just frankly, of all the things we talk about here today, that's probably the most important thing. And then Bureau of Land Management, so DOI and VESCE and BLM, and DOI, OIG, are all in the mix, right? Either in-depth or they're live. They're only paying about $11,000 a month, okay? For these four sites, and then when they add a fifth and a sixth and a seventh, they're still paying $11,000 a month. And they add a eighth site, they're still paying 11 grand a month. Think about that for a minute, all right? That's not a whole heck of a lot of money for the department and the interior to host. Pretty much every bureau except Park Service, right? If Parks wanted to go on the platform and move over to Drupal, then they would have to see an increase because they'd just take too much traffic, right? If Parks is spending not awful amount of money on Akamai anyway, just to front their service. DOI's actually got Akamai in front. We don't take the traffic, but it's really there for an integration point for that. And by the way, we've actually integrated Akamai into the platform. So for every one of these sites, any time you make a content change, call the Akamai API directly, right? It's part of the push and it invalidates the content so it makes its way for Akamai as quickly as it's gonna make its way to Akamai, right? That's another great thing in the Fed. You know, when they're working with CD-Ed, every time we've worked with LineWide, level three, Akamai, CloudFront, they expect the evaluation to be automatic. I'm like, there's this whole point of presence sitting around the planet where it's got a proper game. It's not gonna be automatic. We're gonna wait a few minutes, right? At least a few minutes. We'll have real-time content, then we'll pass it away. So, and then the developer support, we have a full-time dev. He's really only supporting DOI.gov, I should put that, DOI-OIG is the office of the Inspector General for the Department of the Interior. They have their own separate website they didn't use to, but they do now. Lots of infighting over there, so to say. A lot on their own, right? So, Miller and Oliver, it's actually dedicated to just being there to support these guys. Same guy supported the old site. So, they invested about a million and a half so far, right, to go through this. Now, we'll talk a little bit more about that, a little bit later on, because we can actually take all of this and site-builds, you're gonna pay that with ours. You're migrating, you're gonna pay that money. But it's really the past setup and then the build, it's really the hosting where they've taken a gigantic return on investment. The build-out stuff, we put it in there to say, hey, this is how much it'll cost you. If you're working with an agency and you wanna do something similar, these costs are in line, right? So, the way they set this up, which was really good, is they set up what's called a blank list. They set this up, which was really good, is they set up what's called a blank and purchase agreement with five companies, about 40 companies competed to get on the BPA. This is a separate contract from the platform contract, right? We're not crossing the streams, right? There's a new Ghostbusters movie coming out. We're not crossing the streams, right? I don't date myself on this one. You should have seen my original picture of why are we here. It was Admiral Stockdale and like nobody's been in over that. So, I'll be a certified Drupalist. This is the biggest rub for the companies that competed on it. Why do they have to go through certified, et cetera, et cetera, right? We can talk about that all day. My people have gone through the certification. Why? Because for the department of interior, it's the only measure they have, right? Yes, I know, you guys work with great companies, you've built 50 sites and you've done everything under the sun and you've got things that are really fast and tens of clients and everything, that's also fantastic. But when the government's procuring, there's no, they can't accept it, okay? The only thing they can do is take a measure. They said, the measure for us is obviously certification. That's the problem. And when I told you guys, when they all pitched you loans, to use my language about having to go through certification, I said, you're all gonna pass. They all did, they just didn't want to take this, right? So, at the end of the day, that was your requirement to be on the BPA. And it shut down a lot of organizations that were out there. And there was a lot of having involved. But it is what it is. That was not something that I suggested. By the way, they picked it up on their own. Everybody had that government experience. We had a lot, not only we worked with the L.I. We were actually in the Fort Bank, B.G., West of America. Of course, we worked with Parks. Large-scale projects, right? You have to at least have some experience playing around in the field. I'll talk a little bit about some of the particulars for each of these sites in a minute. And then we just compete with each other for the business. Some compete better than others. That's a separate issue. But everybody goes in, puts task orders in to do the sites, right? So, that way the government gets their best talks. And what they do is they'll come to us and say, we want to move Bureau of Land Management. How much money do you think that would be? And then we'll tell them what we think, and they go to all the other people, all the other BPA holders, and they tell them what they're going to think. And then they'll fund enough money to cover the site, right? So, they know they can get their site, and it's predictable. That's a big return on investment for the government because a lot of times, they'll go in, it'll be a T&M, and all this extra money gets added on, et cetera, et cetera. They just do it with this Plattey contract. Some of the particulars. So, how did we make it happen? So, how long did it take? The platform was less than six months. Facebook and IBM built that out. They did a great job. Worked together very closely. I should have put this in the bag, but I didn't, which is, when IBM, because IBM didn't have this background, right, of doing this, they didn't think that, you know, the old spaghetti sauce was pretty good, it's in there, right? Pretty good, it's in there. Well, when it came to the platform, solar, it's not in there. So, they launched you to the platform out and they didn't really have a search. They said, we'll just use USAI.gov for every single bureau. And, somebody along the way didn't think to say, excuse me, right? I need something a little bit better. You just use USAI.gov, which is not very good, right? It's okay, but it's not very good. But, they did build it in less than six months. DIY.gov, we did that in about six months. We started it last January. We were done for the 4th of July, which was pretty cool, we're gonna launch it. But then, the secretary of the interior that was worried about security held the site for two months, right? Because they just got in trouble with the OPM breach. Because OPMs were running their data out of the Denver data center, and it was breached. So, the secretary of the interior was like, you know what, I don't want anything out of the public eye right now. So, it's just kind of a little bit bad. That scene, we started earlier this year. It's supposed to launch at the end of June, probably next launch. So, we'll launch whatever it is and then sort of move it forward. The only thing about DIY, 15,000 distinct pieces of content, that was an automated migration. But the content management system they were in were an expert in. So, we easily sucked that data out and pushed it in. It was, you know, we did that completely automated. The only problem with that is a little garbage in, garbage out, right? They didn't add it all in their contents and some of the stuff they had ended up getting moved over. Sort of an important thing to know. But the design was done ahead of time. So, it's not a six month project, right? I think they spent eight months doing this design. And that's a nice design that any of you that actually know Drupal and have actually themed in Drupal and worked with Drupal know that theming this was not easy for my people, okay? And it's got all this collapsible menu thing. I mean, it's... And at the time, nobody was thinking of building them ahead of the site. So, theming this was actually a bit of a challenge. The site is very deep. So, because it's very deep, you have a bit of a challenge with how we're doing. Not only menuing, right? It's a lot of stuff. But we have to have the obligatory picture of the secretary there. I had to come here. So, we've got the venues with the pictures and, you know, that, and I'll tell you another thing. We had to have Agnes in the platform but customizing taxonomy to drive breadcrumbs. They still have breadcrumbs in their site and to actually have breadcrumbs and to have proper URLs, right? We had to do that through taxonomy customization, which is probably the best way to do it anyway. But they go into their taxonomy. They actually place, you know, what they want the URL to be for anybody that chooses that taxonomy value. And then when that person adds content to that taxonomy, they automatically get a URL and it's just taken care of for them. So, different types of content can be in different parts of the site. For anybody who's played with Drupal before and done any Drupal Dev, you know, that's actually a bit of a challenge in the platform, right? So, creating content on the back end, right? It's all dynamic. Making those URLs actually work where you've got the same content site in two different places. It could be a challenge. But you don't want people hard coding their URLs otherwise you can't go in and just make a global update, right? Seeing that thing, right? It's 7,000 pages in, they've all hard coded to go. I'd like to make a change. It's not gonna happen, all right? So, DOI, again, this design took them a while to go through it, but they were not, we weren't contracted at that point, they were still building the platform. So, it's a little bit of a, but we did our part in six months, right? But they only gave us PSDs. So, we really had to do the majority of the work. Photoshop costs. Bestie, Bestie will launch in June, but it won't have everything they need. And we'll talk about that in a second here. There's over 19,000 to 50,000 content, which strategy was done by SRA, the government contractor ahead of time. And they gave us 120 PowerPoint slides and said, here's your strategy. Thank you very much. We've been waiting seven months for this, but that's all right. It's true, they were supposed to be done last July, they didn't hand it over to us until January of this year. And when they handed it over, Bestie still said, we want our site by June. But wait a minute, because time and space is in tune. That's one of the lessons learned. And then BLM's gonna go live at the end of July, but we'll probably still have functionality. So, we'll launch them and then there's gonna be some things missing. And then, OIG. We did this in eight weeks, all right? Now, this is one, but you can tell why, watch. So, that's an eight week website, right? But it was right off of open public, we're open DOI. And it was when we walked in, they had a very limited budget, they only had 70 grand, 500 pieces of content. They had a customized reporting system. And this part right here is the piece that on the contracting side, when you're playing with the Feds, make sure everything's included. This required solar, but because solar didn't make it in, there was this, I don't even think, it's a matter of fact, I get it back and check, I don't think, this was a year ago, okay? And I'm pretty sure this still doesn't run off solar and I didn't have to add solar to the platform because of contract problems. So, if you're playing this game, you need to make sure that platform has all the little bits and pieces, or you have something in the contract to make sure you can add to it, all right? Probably would've been easier if they were set on something like OIG, right? Number one solar would've been there. Hey, would've been a problem, but it would've been more expensive, all right? Anybody that's interested in that, we did actually try to pitch a platform ourselves with Aquia, and I can tell you what that cost was, and I'll tell you offline, all right? It was definitely more than $11,000 a month, though. That's for sure, believe it or not. But anyway, so this part right here is the customized piece, but the rest of it's very straightforward. Actually, I was the tech leader on it, right? I dragged my Team Food and Agile framework, we launched from start to finish in eight weeks. 700 hours estimated, 705, took 715, all right? But we built it, all right? We got it running, so it was a good deal. So how do we do it? Things that actually work well. We did Agile framework mostly, see the air quotes mostly, right? The government wants Agile, there's more air quotes out here, but they don't always actually understand what that really means, all right? Still some aspects of waterfall, they always want you to build a spec, and they're waiting to Agile for that, let's move forward. Short pops, we just said, hey, we're only gonna have six months, that's it, you get what you get, forces the time, time, timeline, contractually have to get it done, we say, hey, we only have this much time, too bad you can't have that, deal with it. Our friends at OIG said to me, I was in the meeting, they said, when are we gonna talk about making this look like Whitehouse.gov? I said, when you triple your budget, you're talking about it, right? And you go, Whitehouse.gov, today, you can get this, all right? So that forces the client to continue to be realistic. You might not think that actually works, but it does, right? But it puts a lot of pressure on everyone. Rapid prototype, all the iterative development, hey, every week you see something, right? Or every two weeks, here's something, here's a little something. Short wins, we show something, they're happy and they're not complaining. Not like the old days where you wait till the end, you go, hey, look at this, it's great. And they go, no, it's not real great. And then the platform, we have a good starting point. We have the platform. So again, what worked, the agile framework, mostly fixed-speed contracts, you gotta do this. The platform is up all the time, it does not crash. The client's pretty easy to work with for lucky, that's what worked. But the ability to calculate ROI, previously they were in the Denver data center, they have to employ staff to manage the center, now we're kind of wondering that's if they walk away. And one more thing that worked really well was this, security, right? Good ol' OWAPZ attack proxy. They hammered the living daylights out of DOI. They found nothing in the red range, bunch of orange, bunch of yellow stuff that we just went in and fixed. But not a single flaw on the security side. And it hasn't been hacked, right, so there we go. Now be mad, I might as well just shut up, I'll just go ahead and close the front of the business and kind of move on if it got hacked. The pain points, there's no drushing the platform. If you're a developer, you know these pain points. It's not automated, it's not like doctrine, where I can drag and drop from dev to staging to prod, and that is a problem, right? So IBM's screwed it up, this platform. And there's a rudimentary reporting. It's not sitting out there where you've got 5,000 clients, like one of these other guys where you just drop things in. So it's been costing, again, I went to my house and I felt for 70K, I'm sorry, right? We had just enough time to get you up and running, get your stuff new, make it work, make the changes that you want, right? So we did run into a lot of that. They would just say, I want everything and you can't have it, there's a little bit of a problem. This is the biggest part. I should have just done 30 minutes on contact preparation, right? PDFs have to be five-way compliant for the Feds. It's a requirement, okay? It's a lot of work, time and money. DOIs are not, so they're in trouble but they don't have the budget. They went to the budget, the budget says, hey, we don't have the budget for it, so you can't sue us, right? No problems. But unfortunately, Vessie, we have a migration contract that's more than the actual development of the site. There are 11,000 PDFs that my team is working on, 15 people right now going in and fixing PDFs and tagging content for migration. Unfortunately, we'll still do automated migration so we can't and PDFs have to be fixed by the end. I'm not talking about migrating it in. Everybody forgets this, it's a big deal, right? The Bureau of Indian Affairs right now has 12,000 pieces of content and 9,000 PDFs to make things. They're gonna fix all their PDFs and make them five-way compliant by themselves. 8,000 of them are not compliant. It's at least 30 minutes of PDF, right? That is really important, especially if you're dealing with a federal client. I can't overstress it. Usually I'm right on time and I'm right at 30. Any quick questions about what we just talked about? Anybody have anything? It's a very basic showcase, right? We're just talking business, but. Yeah, so who owns the platform now that's gonna be shopped around outside DOI? Okay, question, who owns the platform that's gonna be shopped around outside DOI? DOI owns the platform. So technically it wouldn't be shopped around, but other agencies can come to them and say, can I host with you guys? And they'll actually let them host at FJC, the Federal Judicial Center. They'll let them host with them and they'll just charge it with a thing. It's like they've stood up their own government office, as it were. So I've been using IBM Soundslayer and I do everything myself. How do I get IBM to set up a platform for all of you guys? I have 11,000 dollars for them. I'm serious. That is the only way you have to pay them. All right, in DOI's case, they wanted that business. So they said, they'll do what they bought. 11 grand is, they bought the business. That's fine, buy lots of things, right? I'm sure it was choose and things like that. They bought the business. So the only way to get them to do that, that's a bad answer, unfortunately. No, it's honest. Yeah. Question? Thank you all very much for your time. I really appreciate it.