all right thank you very much uh for everyone coming by here last session before uh we adjourn for food happy hour and uh traffic home uh this session is survivability in the Gap planning for when not if we thought it was very important to um take a DOD view of what we're doing with SAS here's our Safe Harbor notice so everything we say may or may not be held against us later on okay and our agenda and we're going to kick right into it so I'm going to give you a quick Cliff Notes from kind of our position the way that uh we we see this unfolding uh our adversaries have gone to school on the American way of War they understand our Reliance on various networks both in cyber in space and in in the information domain they've also spent hundreds of billions of dollars to try and hold those networks at risk and the attack surface is too wide to defend every point of it so you have to make sure your networks are resilient so that you can fight through the inevitable uh disruptions that are coming now on the national strategy front really our our goal is to uh have integrated deterrents uh in a domain of competition fighting through those planed disruptions in a distributed Manner and where are we at today this is my opinion uh we have just a little bit of catching up to do so uh as we think about where we start as far as disruptions and how we should think about this I think a very uh straightforward Common Sense approach in uh the Pacific region is this map right here so right here this this is fiber optic cabl running through the Pacific they connect the US and some of our other friendly Nations just imagine if someone just were to cut those lines of communication us as a SAS company you as a paying customer how do we continue the fight so the adversary knows that whomever shoots faster and hits better will win that fight and faster more accurate is based on having information superiority decision superiority which then gives us back b space superiority now I might be the last Marine to have used one of these books in combat sadly right this right here is a memo uh uh message book so when I was dug into uh defensive positions in Afghanistan well away from friendly resupply we had to conserve batteries and fuel so we only had a 5minute calm window every hour and that's where we pass information back and forth but other than those those 5 minutes unless we were in contact so you know in a gunfight or something we used Runners to pass messages all the way through the uh the company level and now I I'll say this was a much made fun of practice that we would rehearse in the United States you know people were like oh what are you on gu Canal like what what are you trying to do uh but when we were in Afghanistan and we had to go to being uh conserving everything because every time you send resupply they would get attacked right so we wanted to conserve that uh we were able to still continue to operate I would argue that today teaching people that skill so that that shorthand message writing that I had to learn I'm sorry uh is the equivalent of showing someone today this uh this this uh phone booth and I'm not talking about the telephone itself but I'm talking about the book that you see in that picture trying to explain to someone how to use a phone book to look up a name a number an address or a location and better yet uh this thing right here right I was at a basketball game a couple weeks ago and they had these college basketball stars that are probably going to go to the NBA um they they gave them this phone and they and they said okay uh do you know what this is most of them did not know what it was which surprised me but even more impressive uh none of them knew how to actually make a phone call on this thing so teaching someone how to use a rotary phone uh is uh you know a little scary now take a look at this this is not a Navy ship but this is is a Canadian commercial vessel this diagram shows all information piping within a ship that's connecting all the systems that tells you how that ship performs I would say that if you tried to switch from systems running this telling you and giving you informations to make decision uh and you switch to the grease board you would probably have a very ineffective vessel not able to perform its job we think the same holds true today uh with the types of systems and platforms you have in place today you need a digital system to be maintained uh as a grease board so this is our view our view today is that you have connectivity we have what you would call a kill chain in order to affect your operations but in that domain of competition which exists today and and will become starkly aware for all when this thing kicks off we have to assume that at some point that communication is going to cut when that happens what do systems do especially if it's a SAS based product right we have to be able to operate lights on lights out without hindering you so for us we want to have our instances still be able to operate locally capture information as best as possible and you have in effect a digital grease board that still captures all that information because all this data that's coming through the human mind can't handle that problem set and still make effective decisions you need this in order to maintain uh your awareness and make those decisions and then as you reconnect that data gets uploaded back to you know your larger command element or whatever so that you can continue to make decisions we want that transition to be something that is seamless that is practiced and that's the capability that we're working on delivering which you're going to hear today now how do we get there we get there by uh finding a small use case that matches that problem set and try to help solve for that and that's where I'm proud to say that with the chaplain Corps we're able to actually take that and exercise that on ships today and with that I'll pass it to Chaplan Quinn from the Navy yeah thank you so good afternoon everyone uh I'm chaplain Jeff Quinn with submarine Force Atlantic I've been working on our data analytics project for the last couple of years a quick uh uh history real quick the chapl corps actually got interested in data about 12 years ago when we finally realized that if we all started recording you know with the same definition uh and the same business rules our activities we could actually use that for one of our core functions which is advising our commanding officers on the morale and religious needs of the Personnel um so we started and we put together um what was a typically amateurish effort was a Excel spreadsheet Laden with a bunch of macros that we tried to use to aggregate data it didn't work very well at all and so we went um to a solution that was uh hosted by G2 on the G2 server at cnic and it was called the command religious program Analytics tool uh which if you imagine was number CRP a quickly became known as the crap app in the in the chapl Corp and it was a fitting uh moniker because what ended up happening is we had a tool that was really designed as a as a longitudinal study tool it was it was trying to suck up every possible bit of data you could imagine and it was on a platform that required you know a Tac to log into and it had to refresh every time you you uh went to a new screen there were something like 800 total Fields you could possibly F fill out and half the time G2 itself wasn't working so you couldn't get to the app uh and the other half of the time our connectivity where we were was such that we really couldn't use it with any kind of alacrity so I I as just an example I was underway on Abraham Lincoln and tried to use the app to to just record one day's activities and it took about two hours uh to do that and I stuck with it because I was I was bound and determined to to finish but two hours out of every day obviously is untenable uh for us to be able to feed that information up and and beyond that it was available real time to a few users but not to me as the as the actual chapl entering it I couldn't download my own data to share with my chain of command and um and it was very partial because a lot of people just stopped using it so the data we got was had a lot of holes in it it was just not as useful as it could be so when we started talking with service now we all got together did a little uh hackathon we got a bunch of Chaplin in a room and believe it or not we were able to take the the crap app and just duplicate it on the on the service now platform with with a lot of help uh but Chaplin and RPS did RPS are religious program Specialists the our enlisted assistants we did this together in one week we got something up and and running that actually worked where we are now is we've had enough time with uh the system as we built it to understand that we still had too many fields we were still asking some of the wrong questions and when we started working with the digital transformation office to get aligned with the efforts um in uh Jupiter and the the destructive behaviors dashboard that's being built there uh then everything started to to flow together we we've since simplified our fields and we are about to launch uh part two uh which will actually get us to u to where we want to be and one other quick aside that's interesting from from a community perspective if you can think if any if there's any community that needs to be dragged into the 21st century Kicking and Screaming it's probably chaplain right we're still operating out of a 16th century mindset in some cases so but here we are and in the last two years we've actually had uh half a dozen chaplain go to the Naval Postgraduate School to do systems analysis degrees we've got uh religious program Specialists who are enrolling in data analytics courses and really uh starting to embrace the project management aspect of their of their role so this project is having a transformational impact on us as a Chaplain Corps uh and and oh by the way we will have the opportunity to to use this on canes on the ships on iPads in the field and Via URL or via app app there a bunch of different ways to use it so that everybody can get their data up and we can actually do our job of informing people without worrying about um the technicalities awesome I'll turn it over uh to Adam and Eric and uh they'll walk you through kind of where we're taking it from here yeah thank you yeah as the chaplain mentioned um you know the way that we came about with the the solution that you're going to see a little bit later today what we've been deploying um across the we're starting to employ across the fleet has really been a marriage of capability that we've been trying to address for many many years but also that simplistic use case that could get us actually on there provide value for uh for for chaplains in the fleet but just a refresher about Dil right in case anyone um doesn't hasn't heard the term um this stands for disconnected intermittently connected or lone bandwidth Communications um this is a very regular thing that we see in the dod particularly in the Navy because as you can imagine right I'm a ship I'm in the Indian Ocean I have no connectivity to the sh sure I'm largely doing everything I need to on that ship and of course I will have some bandwidth to do certain things but certainly not enough to do everything and we'll have a little discussion about that in a minute but Dil in the Navy um stands for you know this idea that sometimes it's intentional and sometimes it's unintentional um an intentional use case would be we're going out to do an exercise so we've got to pull our Cals down um we call that River City you might hear someone saying the Navy say we're going River City that means no coms anywhere um everything stays in the ship so uh that might be like an exercise that you're doing but if you're um unintentional might be you know a Cyber attack it could be something where it's weather related right and I just simply don't have a line of sight bandwidth or anything that I can connect to a Shore um and so Dil environments happen all the time um and we just wanted to address it um and you know I I use this slide a lot I my background is p4i so I came from the the PMW 150 side of the house where we build manage deploy applications that ride on the Navy Network on uh over the last 15 years those Navy networks have been Consolidated into something called canes uh it used to be isns adns and Cane so now they're they're Shoring up to provide a standardized Network across all different ship classes um to save money and and everything else uh but if you look at this and you think of like that Cane's network is a very valuable asset it's used for a lot of different things and although it does have a bandwidth right what is it really being used for um so if you're looking at the at the boat here uh you've got intelligence users you've got War fighting users you've even got some business users that are Al creating and also consuming data on that ship when they need to send anything to the shore um usually that bandwidth is going to be scoped down to something very small when it comes to workflow and tasks right it's usually being used for intelligence and War fighting information and position and navigation and timing and things like that that's really where the uh the priority chain exists so from a service now perspective it's important that we operate on a ship with very very limited bandwidth because that's what we're expecting when we get on there um I know the Navy is is coming to address some of those bandwidth concerns but uh that's kind of where we're at today so from a service now at C architecture perspective uh we've been using this uh quite a bit so just to kind of look at this I'll start in the dead center uh as your your service now authorative data source right for workflows and data would be something in the GC Sur of the NSE our Isle for Isle 5 cloud or potentially even an Isle six Cloud that we're going to address in the Navy but certainly exists in the other DOD agencies today um and on the right hand side you've got your connected dedicated um you know connections you're looking at you know nav navc uh the shipyards the airfields these are shore-based commands that will need constant connectivity to that Isle four is 5 instance but on the left hand side this is what Dil is right I've got all these ships um in this case it's very Navy branded but again this is addesses needs across all the dod but I've got my ships um each one of these ships has been deployed a service now self-hosted platform there's been discussions about hey how thin can we make this how can we just do a mid server we just decided it's probably best just to deploy the whole platform because as you can imagine we started with the chaplain a very awesome simplistic workflow um but imagine the possibilities of being able to do discovery on a ship understanding what that ship cmdb looks like and then being able to transport that uh in a in a low pack way to a cloud where it can be deconstructed and understood and worked on by agents on the shore uh we used to address a lot of CAS reps casualty reports in PMW 150 and it took months uh to get them addressed and I think a concept like this makes it a lot easier um just really quickly on the cloud on the left deployed on the ship uh this slide is actually a couple years old but we have been tested on a snowball Edge um we've been tested on Azure stacks for the Navy for our purposes today it was just way easier just go on the infrastructure that's already there and that's can's so just a bit of advancing my slide there we go I just didn't push hard enough uh how did we get here um and so as I mentioned we've been trying to address disconnected operations since I joined the company in 2016 it wasn't until 2018 that I worked with one of Eric's counterparts to deploy a very very simple way of of addressing this idea of can I have a self-hosted instance and turn any communication off and then have it sync a couple records just to show it off because this is I think what the Navy needs uh and so we built that in 2018 it was in 2020 when we met the Chaplin and said wow we've got a use case where people actually need this on ships and we've got this prototype that we built so let's let's merge these two and go out together and make it happen so in 2022 we um we we've got some Partners at CDW that have a can's accredited lab this is exists in San Diego where everything is completely fine-tuned exactly as you would expect on a Navy ship so they can do really interesting tests with regards to um watching data synchronization and being able to throttle bandwidth Up and Down based on hey you know we're going down to a fix 56k link can records still get off the ship and it was very successful and it was very eye opening we were able to test the chaplain application there for that um and then came the next big step is addressing with PMW 160 so PMW 160 is the program management Warfare office that manages canes so to do anything on canes if you want to ride on canes you want to install on canes you have to go through a very rigorous testing process uh to do that so uh in 2013 we wrapped up that test it was very successful couple snafus here and there with regards to security and our our our thing getting wiped out and having to go back and retest it um but that happens um but happy to announce that a couple weeks ago we got to an L RP state where we installed on the eima uh we had gone through a couple different platforms based on availability when they were important which ones were the best ones to install on but that happened a couple weeks go that was in the uima so exciting that's in norfol uh we intend to go full rate production we're working with the Navy right now on fleet forces command to identify what ships and when um to to not only get the disconnected operations piece on but of course deploy also the chaplain application uh so that that's there and then we expect the omm funny story about this when we were leaving the uima um the EXO and the co heard what we were doing and immediately just jumped into this conversation about we should talk about sailor onboarding like we didn't position that we didn't throw that in their faces they actually came and said you're doing workflow on our ship like think of the use cases so that was something that we're going to address uh here very shortly and get back to the EO and and talk to them so this is me and Eric in Norfolk this is uh there's the the EOS right over my head um but it was a it was a great it was a great day it was a great couple days we had a lot of ups and downs um it's also a picture we weren't supposed to take I think I was almost outside the gate at that point but yeah so it was it was good day it was a good little little way to celebrate our uh our Victory there all right so we're going to switch over to the uh the desktop see if I can see and we're g to give you a quick demonstration now this is um this is not specific to the chaplain application this is more uh disc connected operations as a whole so you're going to see a lot of um uh more kind of uh itm information okay um I'm going to pause this as we go through uh just to make sure we're on time we got 15 minutes we look like we're on a good uh Glide right here okay oops make sure this is functional is this showing okay great y okay um two things real quick we're going to be showing two different instances and this can get a little confusing I couldn't do one on each screen so um if you're looking at the hovering right now I'm showing a Shore based instance a cloud-based instance I'm flipping over to the next browser here and we're showing the Eisenhower CVN 69 this is online if you ever get lost in this demo just take a look at the upper left hand screen and you'll know what instance you're looking at but this is a ship based application on this one so what we're looking at here is a global map of our entire operation this is showing us our conus fixed bases as Adam alluded to earlier um you know Shor side and then if we look across the globe we have um ships that are out Force we have forward operating bases so this isn't just a Navy thing it's for everything at the edge um so the the general idea behind all of this is that at at everywhere at the edge they are running service now for them they are doing their mission facing work for them where they need it to be on the off chance we hit a dil environment they can still operate as if nothing has changed everything continues status quo for them and we'll see as we go through this in a in a green scenario like this we have real-time synchronization happening between the forward the edge and home when we go dark for whatever that reason is we'll see that's going to happen here today as we go through this but again the point is we operate as we always have nothing changes but when we come back online now HQ starts to get all the data back we get our Enterprise view back into our Global operations and also comes to the Forefront is what the edge needs us to do now that they can tell us they have stuff going on exactly so we're going to start off again we're at the the shore based instance we can call this HQ or Fleet forces command as you're seeing it so this is would be almost an aggregation of all the data coming off the ships or bases or whatever else um we can see that this one's online and just kind of scrolling across the top we're looking at very high level metrics uh around tasking so critical tasks open tasks anything that's on hold um these are again aggregated numbers coming from the ships and we're also seeing some announcements on the right hand side of the screen as as pertains to what the ships are doing what are the announcements that are happening there this is where Fleet forces might want to look at this and say great it's good to know the canes is upgrading we've got some Rust issues impacting the fleet we understand that as we scroll down I used to work on a program called maintenance figure of Merit it's a it's an mom program that was basically designed to um create a score per ship based on its Readiness level across the the Warfare so is it cyber ready is it maintenance ready what how are we doing and if do we need to address it so now we're moving over to the map here and uh we're going to do a couple things we've we've got some Dynamic filters in the upper left hand as far as show me just the ships or show me just the bases uh this is just something that's quickly flipping back and forth to show I the data that I want to see um we're going to leave it on ship and station here just to get the whole Spectrum those icons by the way those little pyramid icons those are ships driving toward you so that's it didn't resonate when I first looked at it either but it's it looks good but online and offline these are all online if it's got a green pin on it that means it's active we're actively receiving information later in the demo you're going to see pins go red uh and and that's the way that you'll know that we have a disconnected uh state so we're going to do a lot of our demonst ation out of the Persian Gulf and so this is where and this is all fictitious by the way none of this is real real data but I don't think the Eisenhower is in the Persian Gulf but if it is uh CBN 69 right uh we can see that it's a ship we can see that it's online um and we can understand what they're doing on that leftand column talking about link 16 network is down or compost 5.0 these are navy applications um you know that a sailor would probably report and it's something that needs sure visibility and we can short sort things and show things um by severity State whatever it may be so I think at this point we're going to switch over to the ship instance okay so now we're going to look at again the upper right left hand corner or right left hand corner you're seeing the the little graphic of the ship we are an online capability right now so everything that we're doing on the ship is being synchronized over there's a long discussion about Do We sync everything do we need to sync everything we'll leave that for another time in this case we're just assuming that we're going to sync all the tasks based information so as you can see there's some important actions going on on the on the the Eisenhower we've got the can's upgrade we're doing a a deck sweep here in a little bit now again I talked about the synchronization dashboard don't worry so much about incident problem change we just did this for the demonstration but also think of this as like HR cases and payroll discrepancies and whatever else security issues but the idea of these three columns is if it's in the created update column that means that data has been synced with the shore if it's in pending create or pending update that means I've been in a disconnected State and all that stuff lives locally on my uh my shipboard instance but it has not completed a synchronization so just a quick way of of demonstrating hey when was the last time we've had a chance to sync up so this is where it gets fun we're going to take this ship offline we're going to do it by clicking that now I'm going to turn it over real quick yeah so just this is for a demo right um we would not expect in real life for someone have to click a button to take something offline um so just wanted to make that clear in in a real in real life scenar right this is designed in such a way that whenever the edge goes dark for whatever that reason is everything Adam just talked about and we're going to talk about here in a second will automatically happen the service now instance at the edge is designed to handle running offline and not synchronizing back um so again just caveat no expectation someone in the middle of some exercise has to go hit a button to turn this thing off uh it's just going to do its job that's right all right so we are going to take that offline and what it's going to do right now is it's going to do a um a quick refresh of the screen to show you that the ship is Now offline as as far as Fleet forces are concerned I can't communicate with that ship anymore um it is offline and like Eric said I mean we almost kind of expect the ship to know when it's offline like they're going to be the ones that are going to be telling hey I can't receive information I can't send information so a quick visual indicator saying I'm offline on my banner there it's turned from green to Red if you remember a couple moments ago it was Green um and what we're going to do now is we're just going to simulate the idea of a sailor on the ship creating an incident you guys have been probably if if You' service out customers you've seen multiple portals hopefully you've seen the employee service center um but this is the way that we're going to have a sailor create an incident once again it could be an incident it could be an HR case for this presentation we're just doing sort of the itsm route but we're going to create an incident and this is the out of the box right it's very simple but I'm going to give this an urgency of medium and as a sailor it's actually actually High because uh as a sailor I work with a an application called DS n right it's kind of a battle space awareness critical application that they use um and it has gone down or I'm seeing issues with it so I got to log this so while I'm typing this in you'll see the search results underneath and this speaks a bit to the AI capabilities of incident deflection or self-help right the idea of I'm going to do a quick search across knowledge bases service cataloges make sure there's nothing in here that the Sailor could use now before or you know submitting an incident and so here's our resulting record we've got an incident record we've got the description uh probably the most important thing is the message that's going to be highlighted in a second here it's going to tell we talk about a lot about the user visibility and and the user understanding where we are in the workflow this is saying hey look we understand we've got this this has been recorded but we're in a disconnected state right now so you're not going to get Fleet visib or uh Shore base visibility and right now going back to the SN table you'll see that this is in a pending create state so again it lives on the ship and it is not synchronized as of yet so we're going to do some magic here um it it's for me to send one record over is woo but like you know in reality it's probably going to be 30 40 50 100 200 records so you notice that we filled up the boxes here um and as we turn this instance back on you're going to see the records flow out so we're back at the uh you know the button the main button that will probably never happen happen but uh for for demonstration purposes we're bringing the ship back online we're going to start synchronizing we're going to go back to the uh the sync dashboard and again you're going to see records just sort of flow out so just to remember 854 it's going to start with the pending creates and it just you know we've while this runs you know we get a lot of questions about what about file sizes and attachments we actually did test quite a bit of this at the CDW lab um and the records flew out I talked about the way that they could throttle bandwidth um and you know and in really low band with situations the records would slowly go out probably you know slower than this but uh they do go out uh and it syncs up flawlessly so that number right there that's 78 above the ship has been updated based on the uh the numbers that have been um sort of carried out so I'm almost done we're wrapping up this is back at the the base level Fleet forces instance at this point I want to go in and make sure that that D Record came in because I've got fulfillers or agents or specific Mission owners that are going to help me uh with that actual uh bringing that system back online and so there it is it's been synchronized and you know I'll I'll pause it here because there is a and we've got time I probably could show it um but I do want to leave time for questions and answers maybe I'll just talk over it while it's finishing up here there is a bidirectionality to this it works both ways we we talked to the Navy a lot about it's great from ship to shore but from a training perspective it's one of the use cases the Navy said we want want to take training content and push it to the ships can we do that and that's what we're kind of showing right here we're doing a quick update on the incident description um and we're going to push that back over to the ship and the and the uh the the user that created that incident record will see that um it uses the exact same technology in both directions we're not doing anything special in in either One Direction so it's just a matter of looking for a system property that says am I online or I'm I not online and and do what I you know continue my workflows that way so I will pause it there um I think we've got if you want to kick it back over to the slide there's one last slide oh yeah thank you that's wrong computer yeah I worked really hard on this slide okay guys I mean this is where we expect an encore there it is uh no in a minute we'll um we're doing a know if you're seeing the same there it is okay we're not see in here but it's there uh a QR code if you interested in this want to learn more I mean we can do we'll do live demonstrations outside if you need to um we'd be more than happy to to talk to about this again that was a very uh Navy flavored demo but I think this is applicable across um all DOD and we're also talking to even um uh the commercial um Cruise Lines about this as well so it's getting a lot of visibility um but if you scan that you'll be in touch with someone that can help uh triage to the right people so I think with that I mean any question questions two questions how do you handle the uh avoiding unique number collisions between these various enties that are creating records offline and I've got incident 1101 So to that one um the way we're handling it today is when the when the record whatever type it is comes over from the edge in we basically it's it's appended so to speak with the source so if you're looking at a master ceue of incidents it could be you know it could be whatever number is- Eisenhower or you know whatever it is Das forward operating base so that's how we're handling that part does that get sent back to the remote instance or do they still just work with their local number yeah so they're going to work with their local number and for those that are familiar with how service now works behind the scenes what has happened is we have sent the parent CIS ID to the ship to the edge so that when updates are happening back and forth we we know we're talking to the same records both sides and then we don't have that Collision that could potentially happen um the selfhosted environment that you're putting on there does that is that in an appliance form or have you considered that to where it could be used for other entities of us that yeah so deal with infrastructure yeah 100% so today um like Adam said we deploy directly on canes which is basically a virtualized environments um appliances are definitely something we've discussed on the table um and it it's it's still just going to be be sell posted pre-built ready to ship um at the end of the day um so yes it it has been discussed yeah think of this is V1 right uh we're iterating on this uh we want to you know this is the first time we're sharing this uh with customers uh what we want to do is is come visit folks invite us out show us what you want to do and let's talk about what makes sense uh we want to start with the greatest breath to be able to address anywhere you want to put this right uh and then from there we we feel like we're going to hone down to kind of what works best for everyone yes can ships task other ships without going through the so I'm saying rather yeah I mean I we haven't addressed that that's a great that's a great there's no reason you couldn't um you know all we're really looking for or is um probably an IP address of the of the surfice now instance so we got to have it a give it a Target to point at but that's interesting yeah any other questions awesome all well thank you for coming out and like I said um invite us out ask us questions uh we want to come to where you are to see how this can best fit in uh for what you know I see as the coming fight uh and there is no no excuse for a company that supports our customers in DOD to not think about this stuff not have an answer for something like this we want to be held accountable when the time comes and that's why we want to Lean Forward on this so thanks for coming enjoy the happy hours and uh and the food and thank you so much [Applause]