WEBVTT 00:02.993 --> 00:04.578 - Ms. Gaspar it's good to have you back. 00:04.578 --> 00:07.673 We appreciate what you've done so far. 00:07.673 --> 00:10.756 We're looking forward to this update. 00:13.326 --> 00:17.493 - So I have asked, and this committee has been engaged in, 00:17.668 --> 00:21.085 learning on how we've made ourselves more 00:23.815 --> 00:25.565 I guess, IT friendly. 00:25.757 --> 00:29.568 Our information technology tools for the public. 00:29.568 --> 00:31.099 And we've got the explorer app. 00:31.099 --> 00:34.294 Everybody's using it and downloading it. 00:34.294 --> 00:35.383 But Jill's gonna talk today 00:35.383 --> 00:38.244 about what's exciting for the cemetery, 00:38.244 --> 00:39.955 the personnel that actually manage 00:39.955 --> 00:43.372 and conduct the business of the cemetery. 00:43.550 --> 00:45.336 So I'm gonna let her-- 00:45.336 --> 00:46.169 I'm gonna turn it over to her. 00:46.169 --> 00:47.333 She's got some fun tools, 00:47.333 --> 00:49.899 she's gonna let you guys play with some things, 00:49.899 --> 00:54.066 to see our next generation of management of the cemetery. 00:55.596 --> 00:56.614 - Okay, thank you. 00:56.614 --> 00:57.818 Sorry, everyone. 00:57.818 --> 01:01.985 As Ms. Yates was saying, we are making great strides 01:02.030 --> 01:05.757 to modernize our IT efforts here at the cemeteries. 01:05.757 --> 01:09.424 So one of the pieces that we have considered 01:10.834 --> 01:12.191 are mobile tablets. 01:12.191 --> 01:15.375 Particularly when we consider our field ops staff 01:15.375 --> 01:17.041 who are out in the field, 01:17.041 --> 01:17.952 out in the cemetery rather 01:17.952 --> 01:20.626 who are supporting burial services. 01:20.626 --> 01:22.774 Going back and clearing the desk top 01:22.774 --> 01:23.738 is not always convenient. 01:23.738 --> 01:25.810 So implementing tablets in the field 01:25.810 --> 01:29.977 is a great way for them to continue their workload, 01:31.020 --> 01:33.586 their administrative tasks while, 01:33.586 --> 01:36.996 perhaps they're waiting for a funeral service to pass. 01:36.996 --> 01:39.226 So these are ruggedized Dell tablets, 01:39.226 --> 01:40.628 I'm gonna pass them around. 01:40.628 --> 01:42.865 I do have the website loaded. 01:42.865 --> 01:46.018 This has a stylus that you can tap to explore. 01:46.018 --> 01:46.935 It rotates. 01:47.451 --> 01:49.284 Feel free to break it. 01:50.888 --> 01:52.983 I like breaking things, so-- 01:52.983 --> 01:54.191 - [Ms. Yates] I was gonna say, 01:54.191 --> 01:56.597 that is the phase of development we're in 01:56.597 --> 02:00.764 so I will count this as one of our tests of the device. 02:01.319 --> 02:04.405 So if you break it, then Jill's more excited 02:04.405 --> 02:05.905 than if you don't. 02:06.838 --> 02:08.225 - [Jill] So we have a couple-- 02:08.225 --> 02:09.335 - [Male Panelist] Marine proof? 02:09.335 --> 02:10.184 - [Second Panelist] I don't know, sir, 02:10.184 --> 02:12.291 if it's marine proof or not. 02:12.291 --> 02:14.883 - [Jill] So the one that's going down the left side 02:14.883 --> 02:18.050 it has the keyboard attachments on it. 02:18.699 --> 02:19.861 - [Second Panelist] No touch screen. 02:19.861 --> 02:20.977 - It does have a touch screen. 02:20.977 --> 02:23.533 So it is meant to function as a tablet 02:23.533 --> 02:26.533 or like a desktop with the keyboard. 02:29.274 --> 02:30.759 As I mentioned, the field ops, 02:30.759 --> 02:33.420 because they may be in their trucks or in backhoes, 02:33.420 --> 02:34.615 we do have vehicle mounts. 02:34.615 --> 02:35.452 I didn't bring those 02:35.452 --> 02:38.882 but essentially they suction cup to the windshield. 02:38.882 --> 02:41.632 We considered these Dell tablets, 02:43.519 --> 02:45.291 mostly because they are ruggedized, 02:45.291 --> 02:48.947 so when you're in the cemetery and you're dealing with dirt 02:48.947 --> 02:50.269 they might fall, 02:50.269 --> 02:54.436 they should handle the shock of the drop and dust. 02:55.490 --> 02:56.734 The other pieces, 02:56.734 --> 02:59.506 the longterm implementation of these tablets 02:59.506 --> 03:02.756 is to accommodate our business systems, 03:04.052 --> 03:06.802 for example the EISS, ANC Mapper, 03:07.137 --> 03:08.855 and those are packeting systems. 03:08.855 --> 03:11.061 So these tablets meet the requirements 03:11.061 --> 03:14.144 of our information assurance policies 03:14.393 --> 03:16.726 that we need to comply with. 03:17.487 --> 03:21.487 They will be run off of army-accredited network. 03:21.591 --> 03:25.559 Essentially allowing for any intrusion detection monitoring, 03:25.559 --> 03:27.976 so we believe that these were 03:28.745 --> 03:31.020 probably the most locked down systems 03:31.020 --> 03:32.812 that we could implement in the cemetery. 03:32.812 --> 03:33.946 - Pretty good. - Yeah. 03:33.946 --> 03:37.556 - We do currently have 10 of them that have been distributed 03:37.556 --> 03:40.193 for testing, for our quality assurance folks, 03:40.193 --> 03:42.812 who have been taking headstone photos with them. 03:42.812 --> 03:46.340 We do have the one in our possession now with OCIO, 03:46.340 --> 03:50.507 ANMC has also used it to support their mission for testing. 03:52.956 --> 03:56.039 And we do have some feedback on that, 03:57.000 --> 04:01.167 some comments of I guess the ease of use in the field. 04:02.199 --> 04:03.738 Our current faux-op right now, 04:03.738 --> 04:07.905 we use iPhones but the tablets depending on the user, 04:09.662 --> 04:10.865 some are more comfortable with the phone, 04:10.865 --> 04:12.865 some do like the tablet. 04:13.550 --> 04:16.709 Particularly when you're considering data entry 04:16.709 --> 04:18.977 on the tablet you've got a larger screen and the keyboard. 04:18.977 --> 04:21.894 So that was some positive feedback. 04:22.214 --> 04:23.266 - [Ahbi] Jill, do you want to mention anything 04:23.266 --> 04:26.599 about the screen resolution in sunlight? 04:28.854 --> 04:30.531 - The other benefit too with the screens 04:30.531 --> 04:32.409 is that when you are out in the field 04:32.409 --> 04:35.372 resolution does allow for daytime view 04:35.372 --> 04:37.208 making it more readable 04:37.208 --> 04:39.791 and a bit more clear for users. 04:42.032 --> 04:43.806 - [Female Panelist] What is EISS? 04:43.806 --> 04:46.254 - It is the Enterprise Interment Service System, 04:46.254 --> 04:48.141 so that is the system we use to manage 04:48.141 --> 04:50.391 all of our decedent records 04:50.644 --> 04:53.811 and any aspects of the burial service. 04:57.078 --> 04:59.956 So to follow along, like I said there, 04:59.956 --> 05:03.289 ANC explorer website is loaded on there. 05:04.994 --> 05:06.290 At this point I do want to update, 05:06.290 --> 05:10.457 that since our last meeting we have restored our CMS, 05:11.114 --> 05:13.318 which is our Content Management System, 05:13.318 --> 05:16.342 and one of the comments that we had was talking about 05:16.342 --> 05:17.925 enabling sub-pages. 05:18.828 --> 05:22.238 We talked about the World War I anniversaries. 05:22.238 --> 05:26.152 So we are in development for building that piece out. 05:26.152 --> 05:28.450 And again the Content Management System was designed 05:28.450 --> 05:31.700 to be less dependent on our contractors 05:32.292 --> 05:35.764 for managing any of the information that's displayed 05:35.764 --> 05:39.931 in the mobile and web apps that we have for explorer. 05:40.716 --> 05:44.466 We did update the user interface for the CMS, 05:47.041 --> 05:49.008 so I was gonna say we can pull it up. 05:49.008 --> 05:51.425 - Essentially it says, - Okay. 05:52.641 --> 05:53.971 - We've modernized it. 05:53.971 --> 05:57.138 It is much easier to use for our staff 05:57.922 --> 05:59.339 who may, I think, 06:01.531 --> 06:04.860 our previous version was less user friendly. 06:04.860 --> 06:06.693 I struggled sometimes. 06:08.671 --> 06:12.504 Also we did update our URLs from HTTP to HTPS, 06:14.743 --> 06:15.759 making it more secure. 06:15.759 --> 06:19.176 So we are continually progressing to make 06:19.339 --> 06:20.915 our systems and lock downs 06:20.915 --> 06:23.998 comply with army and DOD regulations. 06:25.543 --> 06:29.710 We've also created individual URLs for our kiosks. 06:30.142 --> 06:31.809 I think one of our-- 06:32.029 --> 06:33.660 one of the things we're always curious 06:33.660 --> 06:36.226 is to know how they're being used, who's using it? 06:36.226 --> 06:38.592 So by creating these individual URLs 06:38.592 --> 06:42.175 we are able to track some of those metrics. 06:42.603 --> 06:45.428 So we did have a busy Memorial Day weekend, 06:45.428 --> 06:47.005 I did pull a couple of stats, 06:47.005 --> 06:49.172 I kind of consolidated it, 06:51.108 --> 06:52.401 we had up-use for the website. 06:52.401 --> 06:54.818 We had about 125,000 sessions 06:56.768 --> 07:00.185 and with the mobile app, on Memorial Day, 07:00.413 --> 07:04.580 so you had about 15,000 downloads over the weekend, 07:08.188 --> 07:09.237 of new users. 07:09.237 --> 07:11.320 So it was a busy weekend. 07:12.281 --> 07:14.198 We did talk about the-- 07:14.457 --> 07:18.374 in our last meeting, how we switch data centers 07:19.217 --> 07:21.775 and by doing that we did notice significant improvement 07:21.775 --> 07:25.775 in our performance and development that weekend. 07:26.116 --> 07:28.949 So we also in our last forty days, 07:31.849 --> 07:33.991 we restored our push notification 07:33.991 --> 07:36.096 and added some new social media links. 07:36.096 --> 07:39.096 So we are slowly but surely evolving 07:41.244 --> 07:43.017 and we've gotten better. 07:43.017 --> 07:44.267 All the layers. 07:44.656 --> 07:45.961 - So one of the things that we're-- 07:45.961 --> 07:47.869 I know, we're excited about, 07:47.869 --> 07:49.596 did you mention, I apologize, 07:49.596 --> 07:51.766 did you mention the outside kiosks? 07:51.766 --> 07:53.516 - No, so we do have-- 07:54.378 --> 07:57.378 we did purchase those outdoor kiosks 07:57.449 --> 08:00.469 to be placed at columbarium and at the millennium sections. 08:00.469 --> 08:01.900 So the millennium kiosks, 08:01.900 --> 08:05.983 we do have to reconfigure the power outlet, but-- 08:06.422 --> 08:10.123 - The intent would be that the same experience 08:10.123 --> 08:13.373 a user gets on explorer on their iPhone 08:13.624 --> 08:17.791 would be what they're seeing on the mobile, the kiosks. 08:18.033 --> 08:21.533 And then our staff will use these devices. 08:21.748 --> 08:24.451 They'd have access to explorer as well, 08:24.451 --> 08:28.430 but more importantly our internal mapping systems. 08:28.430 --> 08:31.175 And can you bring that up on that? 08:31.175 --> 08:32.579 - [Jill] Yes, the two tabs-- 08:32.579 --> 08:33.741 One of the tabs at the top? 08:33.741 --> 08:34.824 - Yep. - Okay. 08:37.331 --> 08:39.586 - Why are these so much heavier than a normal tablet? 08:39.586 --> 08:41.375 - They are and it's because they are ruggedized. 08:41.375 --> 08:44.103 That was one of the comments that we've had 08:44.103 --> 08:45.603 is they are heavy. 08:46.415 --> 08:49.998 But for particularly with field operations, 08:51.311 --> 08:54.728 they're gonna be mounted in their trucks. 08:55.703 --> 08:57.141 They're not going to be carrying them around. 08:57.141 --> 08:59.580 - [Ms. Yates] So, can I show them why they're ruggedized? 08:59.580 --> 09:00.913 - Please. Do it. 09:01.073 --> 09:03.000 - Because, this is what we want to be able to do. 09:03.000 --> 09:05.312 (loud clatter) 09:05.312 --> 09:07.896 And not have to replace it. - Right. 09:07.896 --> 09:09.840 - My daughter drops her mobile device, 09:09.840 --> 09:10.785 her mobile-- 09:10.785 --> 09:14.035 she has a tablet that is Windows based, 09:15.482 --> 09:17.165 which is what we need for security. 09:17.165 --> 09:20.645 Jill wanted me probably to drop it to the actual floor, 09:20.645 --> 09:21.478 I can do that. 09:21.478 --> 09:24.221 But this is what we want them to be able to withstand. 09:24.221 --> 09:26.054 And when that happens, 09:26.518 --> 09:27.351 the screen is still up, 09:27.351 --> 09:29.254 Jill, can you get it and show it to everybody? 09:29.254 --> 09:30.962 The screen is actually still up. 09:30.962 --> 09:32.438 - Can I buy two of those for my sons? 09:32.438 --> 09:34.428 (laughter) 09:34.428 --> 09:35.401 - That did not break the screen. 09:35.401 --> 09:37.298 Now granted it is a carpeted floor, 09:37.298 --> 09:38.548 but it is not-- 09:38.974 --> 09:40.395 that is why it's heavier. 09:40.395 --> 09:41.228 - [Mr. Edwards] That is great. 09:41.228 --> 09:42.725 - And our field ops, 09:42.725 --> 09:46.124 most of what they're gonna do is have it in their truck. 09:46.124 --> 09:48.124 But it's not their desk. 09:48.226 --> 09:49.059 - They won't be carrying it around. 09:49.059 --> 09:50.079 - No. - Five hours a day. 09:50.079 --> 09:52.664 - My cem rep, if my goal or our goal-- 09:52.664 --> 09:53.581 - [Jill] Our cem reps are out-- 09:53.581 --> 09:56.038 - At the grave site, they're only gonna carry it 09:56.038 --> 09:57.200 for 15, 20 minutes. 09:57.200 --> 09:58.467 - Yeah, that's not bad. 09:58.467 --> 09:59.458 - And it's not, it's got this-- 09:59.458 --> 10:01.618 if I can put it on my hand correctly, 10:01.618 --> 10:04.535 this ability to ask someone to sign 10:05.379 --> 10:07.212 is our long-term goal. 10:07.431 --> 10:08.942 So that a family doesn't have to-- 10:08.942 --> 10:11.221 you know, we can do things, make an edit, 10:11.221 --> 10:13.932 fix something, and ask them to sign the form 10:13.932 --> 10:14.833 right then and there. 10:14.833 --> 10:16.287 And I'll data capture it. 10:16.287 --> 10:18.620 So the weight of the device, 10:19.698 --> 10:21.662 it's not designed to be something I carry around 10:21.662 --> 10:22.620 like this all day long. 10:22.620 --> 10:23.453 - Right. 10:23.830 --> 10:26.330 - So we believe the trade off, 10:27.215 --> 10:29.548 for that ability to drop it, 10:29.793 --> 10:33.210 bump it, smack it, spill something on it, 10:34.441 --> 10:35.855 - Spill something so there-- - get water-- 10:35.855 --> 10:37.655 if you notice there's a lot, 10:37.655 --> 10:39.714 I can do a lot of things to this thing. 10:39.714 --> 10:40.680 And that's why Jill said break it, 10:40.680 --> 10:43.415 I didn't see any of you guys trying to break if for me. 10:43.415 --> 10:46.082 That's because people are people 10:46.394 --> 10:47.958 and accidents will happen. 10:47.958 --> 10:48.995 - Thought you were interviewing 10:48.995 --> 10:50.478 for QVC network or something. 10:50.478 --> 10:51.311 - No. 10:51.311 --> 10:54.144 (hearty laughter) 10:54.350 --> 10:56.427 But that's why they're heavy. 10:56.427 --> 10:57.472 - And another reason why they're heavy, 10:57.472 --> 10:59.956 is also that they have two batteries. 10:59.956 --> 11:01.394 So like Ms. Yates said, 11:01.394 --> 11:03.144 the field ops members 11:03.376 --> 11:05.923 will be carrying around in their trucks, 11:05.923 --> 11:07.660 they don't have the luxury of going back and recharging. 11:07.660 --> 11:09.578 So we have two batteries to keep them 11:09.578 --> 11:12.161 operational for the entire day. 11:12.844 --> 11:15.249 - [Male Panelist] About like 12 hours, something? 11:15.249 --> 11:18.388 - It depends on the use and how much brightness, of course, 11:18.388 --> 11:19.767 and how much you're utilizing it 11:19.767 --> 11:22.434 but at least six to eight hours. 11:22.525 --> 11:24.883 - [Male Panelist] For a battery or with both together. 11:24.883 --> 11:25.721 - I think for both together. 11:25.721 --> 11:27.881 - Together, but if one of the batteries, 11:27.881 --> 11:30.843 you can do a hot spot with one of the batteries 11:30.843 --> 11:31.959 and it will still stay up and running 11:31.959 --> 11:33.762 which is a benefit too. 11:33.762 --> 11:35.568 You're not yanking out a battery 11:35.568 --> 11:36.582 and the system is shutting down. 11:36.582 --> 11:38.332 So it will maintain-- 11:39.535 --> 11:40.483 - [Male Panelist] And you get an indicator 11:40.483 --> 11:42.461 for low battery as well, pretty sure, okay. 11:42.461 --> 11:44.467 - Yeah it functions just like your regular 11:44.467 --> 11:46.384 desktop or laptop, so-- 11:46.691 --> 11:47.790 and that's basically what that is. 11:47.790 --> 11:50.707 It's as powerful as a normal laptop 11:51.354 --> 11:54.206 it's just probably weighs less and more light 11:54.206 --> 11:55.681 you know, than google desk towers. 11:55.681 --> 11:57.590 - [Male Panelist] It seems like a smart phone on steroids. 11:57.590 --> 11:59.051 (laughter) 11:59.051 --> 12:00.968 - It's like that more-- 12:01.384 --> 12:02.217 Yes sir? 12:02.627 --> 12:04.338 - I'm not sure the period of time 12:04.338 --> 12:07.626 between you do a burial and you get the headstone in. 12:07.626 --> 12:08.489 I'm not sure. 12:08.489 --> 12:09.829 - So we're averaging, 12:09.829 --> 12:11.505 and Jill probably can tell me if I'm accurate, 12:11.505 --> 12:14.796 but it's somewhere between 45 and 60 days depending on. 12:14.796 --> 12:17.296 - So then, what I visualize is 12:17.893 --> 12:19.703 the family comes out because they want to see 12:19.703 --> 12:20.927 the new headstone 12:20.927 --> 12:25.094 and they see maybe, a misspelling of a name or something. 12:25.173 --> 12:27.873 So your field man right out there 12:27.873 --> 12:29.610 can say oh, here is the form 12:29.610 --> 12:32.805 to adjust the spelling on your loved one's grave 12:32.805 --> 12:33.803 and do it right there 12:33.803 --> 12:36.997 instead of sending them to the office or something. 12:36.997 --> 12:39.625 - That could potentially be an option. 12:39.625 --> 12:43.125 I won't brag that we've all but eliminated 12:43.584 --> 12:44.629 those types of errors. 12:44.629 --> 12:47.574 Because that signature I was speaking about 12:47.574 --> 12:50.085 is actually done in the family room 12:50.085 --> 12:52.110 or immediately following the service, 12:52.110 --> 12:54.882 and the family approves a pre-template 12:54.882 --> 12:56.215 of the headstone 12:57.167 --> 13:00.124 so that those kind of mistakes are not-- 13:00.124 --> 13:02.874 and then we're quality assurance checking the stone 13:02.874 --> 13:04.907 when it arrives to the cemetery, 13:04.907 --> 13:08.202 a quality assurance specialist will have one of these. 13:08.202 --> 13:10.361 And every stone that comes into the cemetery 13:10.361 --> 13:11.315 will be able to be checked 13:11.315 --> 13:13.398 against the ordered stone 13:13.590 --> 13:16.066 to make sure that what came from the contractor 13:16.066 --> 13:17.922 is actually what we received. 13:17.922 --> 13:20.989 - Well, my experience is we still got errors. 13:20.989 --> 13:22.680 - We still get people that want to-- 13:22.680 --> 13:23.513 Yep. 13:24.180 --> 13:25.206 - And a family member, 13:25.206 --> 13:27.006 whether they're here or at home 13:27.006 --> 13:28.734 if they're searching on explorer 13:28.734 --> 13:31.686 and they find any information on the marker 13:31.686 --> 13:32.641 to be incorrect, 13:32.641 --> 13:35.548 they can submit feedback directly from that record. 13:35.548 --> 13:37.624 It will tie in to the location. 13:37.624 --> 13:39.813 So that we're not searching, 13:39.813 --> 13:42.505 if it's Joe Smith and which Joe Smith. 13:42.505 --> 13:46.384 So it will say, it's Joe Smith is section 60 grave 1220. 13:46.384 --> 13:49.931 Or whatever the burial or memorial should be. 13:49.931 --> 13:51.145 - Well for the maintenance people in the field 13:51.145 --> 13:54.637 that's a great accelerated way to get something done. 13:54.637 --> 13:55.470 - That's correct, sir. 13:55.470 --> 13:57.616 And once they do something 13:57.616 --> 14:00.616 because the tools we have in Mapper, 14:01.471 --> 14:02.703 tamping the grave. 14:02.703 --> 14:04.370 The grave is tamped. 14:04.377 --> 14:08.544 We're verifying the work leader or the supervisor, 14:08.789 --> 14:10.131 and you make checks. 14:10.131 --> 14:11.643 Marking it right away and done 14:11.643 --> 14:13.534 so that it's not this making a paper list, 14:13.534 --> 14:15.730 carrying it back, tagging it, 14:15.730 --> 14:17.571 it's actually doing it real time. 14:17.571 --> 14:18.404 - And it's also, 14:18.404 --> 14:21.526 the other intent that we planned for this 14:21.526 --> 14:24.009 is whether it's our quality assurance staff, 14:24.009 --> 14:25.765 whether it's field operations, or it's cem reps, 14:25.765 --> 14:28.238 that if they walk passed a marker, 14:28.238 --> 14:30.042 if it's illegible for whatever reason 14:30.042 --> 14:31.873 due to natural causes, 14:31.873 --> 14:33.546 they can pull up the grave, flag it, 14:33.546 --> 14:35.463 and then depending on-- 14:36.894 --> 14:38.496 either flagged for a reorder, 14:38.496 --> 14:41.311 or if you've got a series of headstones that need cleaning 14:41.311 --> 14:42.445 they can flag those, too, 14:42.445 --> 14:46.068 and then we mark those sections for headstone cleaning. 14:46.068 --> 14:48.104 And same thing with turf. 14:48.104 --> 14:50.506 Those are the longterm plans is that 14:50.506 --> 14:53.961 it really is to provide greater situational awareness 14:53.961 --> 14:55.645 of what our cemetery looks like 14:55.645 --> 14:58.462 and how to maintain that pristine look. 14:58.462 --> 14:59.559 - [Female Panelist] Can you take pictures? 14:59.559 --> 15:00.867 You can take a picture, right, and then send it to somebody? 15:00.867 --> 15:02.970 - Yes there is front and rear facing camera. 15:02.970 --> 15:05.018 - [Ms. Yates] Yep, front and rear facing camera on it. 15:05.018 --> 15:06.116 - [Female Panelist] But if they see something 15:06.116 --> 15:08.206 that's amiss they can send it in. 15:08.206 --> 15:10.006 - Snap a picture, yep. 15:10.006 --> 15:12.398 Email, be able to email it or save it. 15:12.398 --> 15:15.890 - So right now these tablets have cellular service on it. 15:15.890 --> 15:18.003 We are in the process of expanding our WiFi 15:18.003 --> 15:19.320 throughout the cemetery. 15:19.320 --> 15:21.254 So once that's complete, we'll switch off the cellular 15:21.254 --> 15:23.004 and stay on the WiFi, 15:23.162 --> 15:26.329 so that will also help with our costs. 15:26.854 --> 15:29.254 We do know that ANMC will be following on 15:29.254 --> 15:33.337 after ANC deploys their business systems to this. 15:33.744 --> 15:37.716 They're also maintaining their business outreach. 15:37.716 --> 15:39.466 - You anticipate that 15:39.804 --> 15:43.008 if you're not a technical expert like myself, 15:43.008 --> 15:45.734 I still have a flip phone I think, 15:45.734 --> 15:47.858 what about the maintenance crew? 15:47.858 --> 15:49.355 Are they going to be trained 15:49.355 --> 15:51.482 on how to get up to speed on this? 15:51.482 --> 15:55.462 - So the initial is we'll have the field supervisors. 15:55.462 --> 15:59.629 They'll be using it and we'll have their staff also. 15:59.733 --> 16:03.900 - We have found that the average age of our field crew 16:05.273 --> 16:06.377 is much younger. 16:06.377 --> 16:09.267 And every one of them has an iPhone in their pocket. 16:09.267 --> 16:11.188 - Not a flip phone. - They're the ones showing 16:11.188 --> 16:13.938 the families how to use explorer, 16:13.940 --> 16:15.615 that they run into in the cemetery. 16:15.615 --> 16:19.780 So there's a lot of them that are very excited about this. 16:19.780 --> 16:21.519 - And also the way our business is structured, 16:21.519 --> 16:22.736 they are permission based, 16:22.736 --> 16:26.272 so depending on he level of access you have, 16:26.272 --> 16:28.355 there's only one limited, 16:28.991 --> 16:30.996 or maybe you have certain capabilities 16:30.996 --> 16:34.228 of what functionalities you can execute. 16:34.228 --> 16:36.469 So you may not be able to delete a record, 16:36.469 --> 16:38.027 but you can edit certain pieces. 16:38.027 --> 16:41.121 And we do have auditing allowance within that, 16:41.121 --> 16:43.698 so if we do find something askew, 16:43.698 --> 16:46.176 we can always go back and dig a little, 16:46.176 --> 16:47.705 see what may have changed. 16:47.705 --> 16:51.788 We are definitely doing out best to keep that up. 16:52.148 --> 16:55.065 (muffled speaking) 16:55.100 --> 16:56.273 - First of all let me 16:56.273 --> 16:58.249 compliment you and your team. 16:58.249 --> 17:01.666 What this has done as brought Arlington-- 17:02.216 --> 17:03.484 I'm talking about the ANC app, 17:03.484 --> 17:05.869 has brought Arlington to the world. 17:05.869 --> 17:09.361 - To the 21st century. - It's just outstanding. 17:09.361 --> 17:12.111 Several of us had asked last year 17:12.342 --> 17:15.481 about looking at, under notable graves, 17:15.481 --> 17:18.937 adding a category of Civil Rights leaders. 17:18.937 --> 17:21.924 And I think we were told that y'all would look at that. 17:21.924 --> 17:24.292 Can you tell me the status to that 17:24.292 --> 17:27.236 and if for any reason you honestly believe 17:27.236 --> 17:28.819 we shouldn't do it, tell us. 17:28.819 --> 17:32.499 But I would think it would be a nice addition to have 17:32.499 --> 17:34.916 to notable graves categories. 17:35.368 --> 17:39.451 - So we, as part of our online version last year, 17:40.923 --> 17:42.411 we did have some little areas 17:42.411 --> 17:44.962 with updated content management system. 17:44.962 --> 17:48.721 As a part of that, it did break, we've restored it. 17:48.721 --> 17:50.472 And as I mentioned earlier, we are in development 17:50.472 --> 17:53.991 of adding that functionality of creating sub-pages, 17:53.991 --> 17:57.453 so that way if we wanted to add Civil War leaders, 17:57.453 --> 17:58.453 or you know, 17:58.841 --> 18:02.314 notable service members who served in World War I 18:02.314 --> 18:04.147 or any other conflict, 18:04.220 --> 18:06.553 we do want that flexibility. 18:06.617 --> 18:09.170 So we do hope in the next couple months, 18:09.170 --> 18:11.667 couple months meaning this summer, 18:11.667 --> 18:14.917 but we hope to release that capability. 18:16.310 --> 18:17.645 One of the things that we've done so far, 18:17.645 --> 18:20.040 because I think our previous was the 18:20.040 --> 18:21.903 reporting lost items, we added that. 18:21.903 --> 18:25.486 So that's another model in the application. 18:25.806 --> 18:29.473 So we are slowly taking some of the feedback 18:29.885 --> 18:32.635 that the committee has presented. 18:33.460 --> 18:36.730 - Could you report to us at our next full committee meeting, 18:36.730 --> 18:39.797 the status of the Civil Rights sub-category? 18:39.797 --> 18:41.280 - So I think with that-- - And the historians-- 18:41.280 --> 18:43.557 we have to meet with an historian, to identify-- 18:43.557 --> 18:45.142 - [Male Panelist] Civil Rights or Civil War? 18:45.142 --> 18:47.642 - Civil Rights. - Civil Rights. 18:47.974 --> 18:50.977 Like, Medgar Evers is listed under political figure. 18:50.977 --> 18:52.436 I think Civil Rights would be-- 18:52.436 --> 18:53.326 - [Male Panelist] She said Civil War 18:53.326 --> 18:54.159 and you said Civil Rights. 18:54.159 --> 18:54.992 - [Jill] I'm sorry. 18:54.992 --> 18:56.889 - She's just referring to 18:56.889 --> 18:59.639 the greater project that she has, 18:59.653 --> 19:02.153 Jill gives it access on there. 19:03.666 --> 19:06.476 But the content management piece of it 19:06.476 --> 19:08.410 belongs to the historians. 19:08.410 --> 19:09.243 And has to. - Right. 19:09.243 --> 19:11.022 And the executive directors 19:11.022 --> 19:13.234 looking at all of those categories. 19:13.234 --> 19:15.067 So if you recall, sir, 19:16.150 --> 19:19.067 much of what you see was inherited. 19:19.590 --> 19:22.905 And so instead of removing it completely, we've left it 19:22.905 --> 19:25.346 and it's going through a complete vetting process. 19:25.346 --> 19:26.730 - How much longer will that take? 19:26.730 --> 19:27.563 Do you think? 19:27.563 --> 19:29.528 That's what will be concluded this summer, perhaps? 19:29.528 --> 19:30.361 - Exactly. 19:30.361 --> 19:31.194 - Okay. 19:32.244 --> 19:33.650 And just a senior citizen question. 19:33.650 --> 19:35.483 I was looking at this. 19:36.487 --> 19:40.404 On one of the main pages, instead of going back 19:40.921 --> 19:42.671 to the previous page, 19:43.175 --> 19:46.008 it has the three horizontal lines. 19:46.971 --> 19:48.851 To most people, is that automatically, 19:48.851 --> 19:51.824 do they read that as being that's how you go back? 19:51.824 --> 19:52.657 - I didn't-- 19:52.657 --> 19:53.759 My children had to-- - because some of the others 19:53.759 --> 19:55.477 have an arrow to go back, 19:55.477 --> 19:58.455 but this one, this page, has the horizontal lines. 19:58.455 --> 19:59.744 - Well, the horizontal lines is a menu. 19:59.744 --> 20:00.577 - Right. 20:01.885 --> 20:02.718 Right. 20:02.775 --> 20:03.783 - [Jill] So if you swipe right or left, 20:03.783 --> 20:05.866 it'll take you all over-- 20:06.948 --> 20:09.365 - He's referring to the menu. 20:09.372 --> 20:13.539 - That is the convention used around all applications, 20:15.001 --> 20:17.526 mobile, and even websites these days, 20:17.526 --> 20:20.055 for the three stacked lines to indicated a menu. 20:20.055 --> 20:21.716 So, if we have some kind of navigation-- 20:21.716 --> 20:22.818 - Right, if I don't want to go to the menu, 20:22.818 --> 20:24.942 I want to go to my previous page, 20:24.942 --> 20:27.947 I want to go to my second previous page, 20:27.947 --> 20:31.259 is that self-explanatory to most people. 20:31.259 --> 20:32.092 That you you hit, 20:32.092 --> 20:33.663 if I want to go to the previous page, 20:33.663 --> 20:35.751 I hit the three horizontal lines. 20:35.751 --> 20:37.907 - The three horizontal lines 20:37.907 --> 20:40.331 just happens to be your previous page in this case. 20:40.331 --> 20:41.863 - [Male Panelist] You should have a device on your phone. 20:41.863 --> 20:43.631 - [Ahbi] Yeah, it should have a little back arrow. 20:43.631 --> 20:45.376 - Because you were at the menu to start with. 20:45.376 --> 20:46.209 - Right, okay. 20:46.209 --> 20:47.394 - So that's what that means, that's menu. 20:47.394 --> 20:50.644 - So, sir. I'm on Explore the Cemetery. 20:51.919 --> 20:52.752 - Right. 20:52.752 --> 20:55.043 - So that takes me back to my main menu, 20:55.043 --> 20:56.860 when I got to Explore the Cemetery. 20:56.860 --> 20:59.640 If I want to go back and I'm on a sub-page, 20:59.640 --> 21:00.473 it takes me-- 21:00.473 --> 21:01.793 - So then it does have the arrow on it? 21:01.793 --> 21:04.726 - You just happened to be only on one advancement. 21:04.726 --> 21:05.559 If you go one more-- 21:05.559 --> 21:07.110 - Okay so yeah, if I advanced one more 21:07.110 --> 21:08.430 then it does have it. 21:08.430 --> 21:09.263 Perfect. 21:09.450 --> 21:10.283 Thank you. 21:11.116 --> 21:13.366 Great work on this, really. 21:13.492 --> 21:14.395 Outstanding. 21:14.395 --> 21:17.395 - [Jill] Any other questions for us? 21:18.250 --> 21:20.750 - Alright, we'll move to EISS. 21:21.259 --> 21:25.426 - So the next presentation will be by Ahbi Kalavapudi, 21:26.887 --> 21:28.590 and he's gonna introduce himself 21:28.590 --> 21:30.578 'cause he'll do a better job than I will. 21:30.578 --> 21:33.969 But he is part of our internal contract team 21:33.969 --> 21:35.052 that works on 21:38.309 --> 21:39.142 now we're talking, 21:39.142 --> 21:43.309 we just talked a lot of external and internal tools. 21:43.716 --> 21:44.993 He is going to talk a little bit 21:44.993 --> 21:47.449 about the things we're doing to improve 21:47.449 --> 21:51.282 how we manage the auditable records of burial, 21:51.617 --> 21:53.758 and how we manage the cemetery 21:53.758 --> 21:56.225 and our operations through that system. 21:56.225 --> 21:57.791 Ahbi, I'm gonna let you do a better job 21:57.791 --> 21:59.124 than I just did. 21:59.130 --> 22:01.444 - Okay, no problem, thank you. 22:01.444 --> 22:03.030 I appreciate your time today 22:03.030 --> 22:05.110 and allowing me to speak about 22:05.110 --> 22:07.292 the Enterprise Interment Services System. 22:07.292 --> 22:08.716 - [Male Panelist] Would you use the microphone, please? 22:08.716 --> 22:09.731 - Oh yeah. Could you hear me now? 22:09.731 --> 22:11.323 - [Ms. Yates] Union projective services is recording it. 22:11.323 --> 22:12.345 Ahbi if you could speak a little louder. 22:12.345 --> 22:13.413 - Oh I'm sorry. 22:13.413 --> 22:16.961 Yes so the Enterprise Interment Services System 22:16.961 --> 22:18.228 is what I'll be talking about today. 22:18.228 --> 22:20.299 My name is Ahbi Kalavapudi. 22:20.299 --> 22:21.178 I am a contractor, 22:21.178 --> 22:24.401 so feel free to have no hold barred against me, 22:24.401 --> 22:27.131 I know that's depending on how you feel. 22:27.131 --> 22:28.497 Yes, as Ms. Yates said, 22:28.497 --> 22:30.861 I've been here for about four years with ANC 22:30.861 --> 22:33.901 and have been working on the current system, 22:33.901 --> 22:35.289 interment services system, 22:35.289 --> 22:37.372 which we refer to as ISS, 22:37.809 --> 22:39.660 but we are now trying to scale that 22:39.660 --> 22:43.425 across all the cemeteries that are on the army portfolio. 22:43.425 --> 22:44.259 So that's why we call it 22:44.259 --> 22:47.342 Enterprise Interment Services System. 22:49.524 --> 22:52.774 So let's establish what EISS really is. 22:53.737 --> 22:56.385 What it does and what Ms. Yates eluded to, 22:56.385 --> 22:57.976 if I can dovetail off of that, 22:57.976 --> 23:00.489 is it's really an auditable system of record 23:00.489 --> 23:02.008 for all administration, 23:02.008 --> 23:05.425 or administrative and operational aspects 23:05.977 --> 23:07.840 of the entire funeral service. 23:07.840 --> 23:09.854 But it is a decedent based system. 23:09.854 --> 23:12.493 It works in conjunction with other internal systems 23:12.493 --> 23:13.608 such as Mapper, that Jill, 23:13.608 --> 23:17.775 Ms. Gaspar has oversaw for the last several years. 23:18.613 --> 23:21.395 And it does supply data to the applications 23:21.395 --> 23:24.112 that you were using, Mr. Edwards, earlier. 23:24.112 --> 23:27.460 So Explorer, all its data that it's fetching, 23:27.460 --> 23:28.293 well not all of it, 23:28.293 --> 23:31.737 but all the descendant based data regarding 23:31.737 --> 23:34.261 if you were doing a Find a Grave Site 23:34.261 --> 23:36.397 aspect of that application, 23:36.397 --> 23:39.147 that is retrieving data from ISS. 23:40.521 --> 23:44.438 So it is imperative that we record data cleanly 23:46.359 --> 23:50.073 for operational purposes as well as for posterity 23:50.073 --> 23:52.633 to present to other public applications, 23:52.633 --> 23:54.300 such as our website. 23:54.532 --> 23:58.420 If the family members who are attending a service 23:58.420 --> 24:00.184 have questions about where to attend 24:00.184 --> 24:01.617 or how to attend, what time, 24:01.617 --> 24:03.918 that is all being coordinated today 24:03.918 --> 24:07.335 though Interment Services System, or ISS. 24:07.671 --> 24:10.175 The goal here is to make those capabilities 24:10.175 --> 24:12.341 and functionality expanded 24:12.341 --> 24:14.174 to the post cemeteries 24:15.080 --> 24:15.913 as well as combining 24:15.913 --> 24:19.352 with Soldier and Airmen's home data records. 24:19.352 --> 24:22.519 And make it a more comprehensive tool. 24:22.825 --> 24:25.542 In order to do that, we found opportunities 24:25.542 --> 24:28.655 to improve the existing legacy system. 24:28.655 --> 24:31.249 To modernize it with functionality 24:31.249 --> 24:33.999 like Ms. Gaspar eluded to earlier 24:34.231 --> 24:38.398 for compliance reasons with the DOD for role based access, 24:38.535 --> 24:40.302 so supervisors have a different perspective 24:40.302 --> 24:43.052 on how to maintain and edit data, 24:43.326 --> 24:45.332 versus the cemetery representatives 24:45.332 --> 24:48.220 or field operation maintenance crew. 24:48.220 --> 24:52.387 So that is essentially what we intend to build out 24:52.459 --> 24:55.744 with Enterprise Interment Services System. 24:55.744 --> 24:57.006 - So what is this based on? 24:57.006 --> 25:00.089 Is this a commercial off the shelves? 25:01.855 --> 25:04.844 - No it is an entirely custom application. 25:04.844 --> 25:07.815 As you know, Arlington is a very unique environment. 25:07.815 --> 25:09.740 It has many complex business rules 25:09.740 --> 25:11.487 that kind of overlap each other. 25:11.487 --> 25:13.042 So there's a lot of different circumstances 25:13.042 --> 25:16.542 as to why we'd need to customize certain-- 25:16.606 --> 25:18.678 all our data is customized in it, of course. 25:18.678 --> 25:20.252 But to make that data available 25:20.252 --> 25:24.283 and interact with each other has to be customized. 25:24.283 --> 25:26.753 So they chose it to be based out of 25:26.753 --> 25:29.336 microsoft.net C-sharp platform, 25:31.139 --> 25:33.750 but we are essentially modernizing it 25:33.750 --> 25:35.629 for the web 2.0 standards, 25:35.629 --> 25:38.074 so that it can be viewed on a tablet, 25:38.074 --> 25:42.162 like Ms. Gaspar said, for the field crew or anybody-- 25:42.162 --> 25:43.475 - [Mr. Peake] Who's IP is this? 25:43.475 --> 25:44.308 - I'm sorry? 25:44.308 --> 25:45.743 - This is government IP? 25:45.743 --> 25:47.284 - [Ahbi] Yes that's correct. 25:47.284 --> 25:48.951 - Is it monetizable? 25:52.799 --> 25:54.059 - [Jill] How do you answer? 25:54.059 --> 25:56.255 - [Ms. Yates] Sir, can you define that for those of us-- 25:56.255 --> 25:57.088 - Could you, 25:57.088 --> 26:01.050 is this something that would have applicability, 26:01.050 --> 26:01.883 I know you're unique, 26:01.883 --> 26:03.467 but go to a VA cemetery 26:03.467 --> 26:04.585 and I don't know, - Yes, sir. Yes, sir. 26:04.585 --> 26:05.418 - Gene, what would they say? 26:05.418 --> 26:06.709 How unique is it, you know? 26:06.709 --> 26:08.698 - So is there -- - Yes, sir. 26:08.698 --> 26:10.013 - Is this something that could be-- 26:10.013 --> 26:12.767 - There are aspects of it that are definitely reusable, 26:12.767 --> 26:13.631 and in fact-- 26:13.631 --> 26:16.340 - Which is true of most big ERP kinds of systems, right? 26:16.340 --> 26:17.173 - Right. 26:17.173 --> 26:20.923 And particularly, to shed an example on that, 26:21.613 --> 26:25.280 the DOD has requested to utilize our system, 26:26.070 --> 26:28.751 and our database, and the way we conduct our processes 26:28.751 --> 26:31.084 for capturing the life cycle 26:31.424 --> 26:33.306 of that decedent record-- 26:33.306 --> 26:34.439 - My next question was gonna be about 26:34.439 --> 26:36.724 out of the purview of this committee, 26:36.724 --> 26:39.057 but the 40 army cemeteries-- 26:39.822 --> 26:42.925 - [Jill] That's the next step is to expand 26:42.925 --> 26:46.398 for ANMC and then, as Mr. Kalavapudi was saying, 26:46.398 --> 26:49.065 DOD has also expressed interest. 26:50.442 --> 26:51.914 - And I've been working with 26:51.914 --> 26:54.032 the National Cemeteries Administration and their team, 26:54.032 --> 26:55.115 'cause as they're, 26:55.115 --> 26:56.604 they're looking for the next generation 26:56.604 --> 26:57.699 of what boss will be there, 26:57.699 --> 27:00.024 their operating system, yes sir. 27:00.024 --> 27:01.330 We're all working together. 27:01.330 --> 27:03.997 'Cause, to back up, we took ISS, 27:05.763 --> 27:06.846 the interment-- 27:06.846 --> 27:09.846 what was a scheduling system in 2010 27:09.905 --> 27:11.238 turned into ISS, 27:11.921 --> 27:13.242 interment services system, that-- 27:13.242 --> 27:14.825 - I remember the briefings. 27:14.825 --> 27:17.838 - And we changed it to model it after 27:17.838 --> 27:20.005 the decedent based process 27:20.132 --> 27:22.011 that the barrel operating system uses. 27:22.011 --> 27:25.678 So we already kind of came in line with NCA, 27:25.712 --> 27:28.323 and now we've gone beyond that with this system, 27:28.323 --> 27:29.934 will be multiple cemeteries, 27:29.934 --> 27:32.651 and he's got some demos he'll run you through. 27:32.651 --> 27:35.251 And it shows where, I think we've already got it mocked up, 27:35.251 --> 27:36.980 Soldier and Airmen's home. 27:36.980 --> 27:40.832 So he'll be able to show you where that's headed to, sir. 27:40.832 --> 27:42.119 - It'll be more of a notional example, 27:42.119 --> 27:43.767 but it'll still illustrate 27:43.767 --> 27:46.684 the points that Ms. Yates has made. 27:46.827 --> 27:47.727 But going back, as I said, 27:47.727 --> 27:50.507 there's slew of applications that we use 27:50.507 --> 27:51.615 for daily operations. 27:51.615 --> 27:54.090 You know, we have Mapper, we have the photo application 27:54.090 --> 27:58.257 for taking photographs of markers for accountability effort 27:59.408 --> 28:02.089 to maintain that we've ordered the marker 28:02.089 --> 28:04.223 as prescribed by the family 28:04.223 --> 28:07.986 and according to the rules that the VA, NCA imposes. 28:07.986 --> 28:09.586 So we have to make sure that we're very delicate 28:09.586 --> 28:12.503 about how we process those markers. 28:12.738 --> 28:15.123 And then we also use something called the research tool 28:15.123 --> 28:17.751 which was the original accountability tool, 28:17.751 --> 28:20.323 that was meant for vetting records, 28:20.323 --> 28:22.724 all the historical records here at ANC. 28:22.724 --> 28:26.249 And then it essentially moved those records 28:26.249 --> 28:30.389 into the current state where they currently reside in ISS. 28:30.389 --> 28:32.071 But that just illustrates to you 28:32.071 --> 28:34.349 with the number or applications that I listed, 28:34.349 --> 28:36.103 that it's very decentralized. 28:36.103 --> 28:38.004 The goal is to centralize it a little bit more. 28:38.004 --> 28:40.200 To have the photo app and research tool 28:40.200 --> 28:42.747 work in conjunction with this EISS 28:42.747 --> 28:44.232 so that it's comprehensive. 28:44.232 --> 28:47.176 And I can go into a little bit more in the next slide 28:47.176 --> 28:48.589 which talks about all its features 28:48.589 --> 28:50.922 that we intend to integrate. 28:51.120 --> 28:53.120 So many of these bullets 28:53.989 --> 28:56.268 are either aspects of the application 28:56.268 --> 28:59.931 or aspects of our operations on the administration side, 28:59.931 --> 29:04.098 that will be integrated in some fashion and backed by IT 29:05.206 --> 29:08.379 and that's essentially what EISS will accomplish for us. 29:08.379 --> 29:09.629 So off the bat, 29:10.056 --> 29:12.495 multiple sites and roles and permissions 29:12.495 --> 29:15.591 are the key fundamental aspects as to why we invested 29:15.591 --> 29:19.258 in expanding an existing legacy application. 29:19.479 --> 29:21.812 But we took this opportunity to make it better, 29:21.812 --> 29:24.189 improve it from the ground up. 29:24.189 --> 29:26.978 So when you're asking questions about cots or gots 29:26.978 --> 29:29.272 there's really nothing that's out there to purchase 29:29.272 --> 29:31.772 that conforms to what we need. 29:31.972 --> 29:34.993 So we essentially had to develop this 29:34.993 --> 29:37.076 from the ground up again. 29:38.623 --> 29:40.928 The funeral service resource management 29:40.928 --> 29:41.767 is what we do today, 29:41.767 --> 29:43.999 but we need to make that customizable 29:43.999 --> 29:48.166 for each of the post-cemeteries as well as DOD cemeteries, 29:48.410 --> 29:50.630 depending on how they conduct their operation. 29:50.630 --> 29:53.380 What ANC uses as far as case ons, 29:54.236 --> 29:56.516 things that are unique to ANC 29:56.516 --> 30:00.016 may not be available at the next cemetery. 30:02.276 --> 30:03.491 Chain of custody, 30:03.491 --> 30:06.721 we need to be able to automate that process, 30:06.721 --> 30:08.684 currently it's very manual and a lot of paperwork 30:08.684 --> 30:09.517 involved with that. 30:09.517 --> 30:12.635 We do have the ability to take photographs 30:12.635 --> 30:14.588 with the government issued iPhones, 30:14.588 --> 30:17.449 but it doesn't directly go into our system 30:17.449 --> 30:20.343 so that is something that we intend to integrate. 30:20.343 --> 30:23.327 So that it is a more streamlined process 30:23.327 --> 30:25.182 for our cemetery representatives. 30:25.182 --> 30:26.015 - Quick question - Yes, sir? 30:26.015 --> 30:27.198 - On the chain of custody, 30:27.198 --> 30:29.949 I know how important that is and if I'm not mistaken, 30:29.949 --> 30:32.660 the funeral home sends the body to probably here. 30:32.660 --> 30:33.657 So having said that, 30:33.657 --> 30:36.794 the family members, do you see putting in a system 30:36.794 --> 30:40.377 where each time the merchant, the product-- 30:43.552 --> 30:45.417 not the product, but the body 30:45.417 --> 30:47.323 gets moved from one point to the other, 30:47.323 --> 30:49.869 you get an email the person that initiated it? 30:49.869 --> 30:50.902 Like the family member 30:50.902 --> 30:52.592 or the funeral home get like an email? 30:52.592 --> 30:55.509 And I say that because it remind me 30:55.509 --> 30:57.156 when I purchased a car, 30:57.156 --> 30:59.280 and it let you know where it's at. 30:59.280 --> 31:00.631 We just put it on the truck, 31:00.631 --> 31:02.791 expect three days to the location. 31:02.791 --> 31:05.336 So when it get to the location, you get an email. 31:05.336 --> 31:06.814 So I was just throwing that out there, 31:06.814 --> 31:08.964 do you see something like that happening? 31:08.964 --> 31:12.295 - So chain of custody for us is positive control 31:12.295 --> 31:15.212 so it's person to person conducted. 31:15.634 --> 31:18.051 We have talked about at times 31:18.546 --> 31:22.713 the implementation of some sort of RFID tracking process. 31:25.020 --> 31:26.353 Not necessarily, 31:27.410 --> 31:28.243 for the amount of time, 31:28.243 --> 31:30.438 we do not accept remains but three days before 31:30.438 --> 31:32.382 and those are cremated and they're hand carried, 31:32.382 --> 31:36.549 signed over from the funeral home to the cemetery rep. 31:37.376 --> 31:39.438 The cemetery rep then signs it over to the field crew 31:39.438 --> 31:41.533 and they put it, interment in the ground. 31:41.533 --> 31:44.756 So, you know, it's something we've talked about. 31:44.756 --> 31:46.278 - I guess the question the store manager's asking is 31:46.278 --> 31:47.599 okay where's the family member in this, right? 31:47.599 --> 31:50.281 - Along the way, so they'll know, you know? 31:50.281 --> 31:51.948 - Do they know that? 31:51.960 --> 31:54.214 - The majority of our remains come carried by the-- 31:54.214 --> 31:57.881 70% are cremated, and of those 70% 31:58.517 --> 32:02.044 only about a third come before the services, 32:02.044 --> 32:03.673 the family doesn't carry it themselves. 32:03.673 --> 32:05.867 - So now what about the body? - The casket? 32:05.867 --> 32:07.544 - The casket is with the funeral director, 32:07.544 --> 32:09.171 and then it's transferred to us. 32:09.171 --> 32:11.623 - See, that's what I was thinking about. 32:11.623 --> 32:15.790 I want to believe all funeral homes are top notch, 32:16.612 --> 32:18.824 and got the best people handling this, 32:18.824 --> 32:22.074 but we know the world is round as well. 32:23.442 --> 32:26.673 - To answer his question, the funeral home, 32:26.673 --> 32:29.246 say we had a death in Hawaii, okay? 32:29.246 --> 32:33.145 And they want, they're eligible for Arlington, okay? 32:33.145 --> 32:34.528 That funeral home in Hawaii 32:34.528 --> 32:37.742 has to coordinate with the funeral home here. 32:37.742 --> 32:39.377 And the remains are transferred, 32:39.377 --> 32:40.567 and the chain of custody, 32:40.567 --> 32:44.734 is up to that funeral home until it reaches a cemetery. 32:45.302 --> 32:46.135 - The service for a casket 32:46.135 --> 32:47.390 is that it remains with the family. 32:47.390 --> 32:49.699 - And you project this may be six months 32:49.699 --> 32:52.449 when they make their application. 32:53.085 --> 32:55.201 - Right, so if we would just visualize 32:55.201 --> 32:57.722 a cemetery representative is coordinating all these details 32:57.722 --> 33:00.305 through a system called Remedy, 33:00.305 --> 33:02.587 we have a customized instance of Remedy, 33:02.587 --> 33:05.282 which is a case tracking or case management tool, 33:05.282 --> 33:07.514 and they're reaching out to the family members 33:07.514 --> 33:10.365 who are also in contact with the funeral home 33:10.365 --> 33:12.410 and sometimes our cemetery representatives 33:12.410 --> 33:14.570 are talking directly with the funeral homes. 33:14.570 --> 33:15.775 So we do take information 33:15.775 --> 33:17.702 and plop it into the record. 33:17.702 --> 33:21.535 We do the sending and receiving funeral homes, 33:22.677 --> 33:24.110 we populate that information. 33:24.110 --> 33:26.054 But these are also opportunities to improve 33:26.054 --> 33:28.421 how that data entry is put in. 33:28.421 --> 33:30.836 Right now a lot of it is free form. 33:30.836 --> 33:34.072 So that results in a lot of variability with the data. 33:34.072 --> 33:36.405 And if we were to run metrics 33:36.405 --> 33:39.655 as to how to say, this particular state 33:40.269 --> 33:42.761 or this particular funeral home in general 33:42.761 --> 33:46.428 gets a lot of, they do a lot of the shipping 33:47.145 --> 33:48.593 or they do a lot of the receiving, 33:48.593 --> 33:51.465 and maybe we can target how we communicate with them 33:51.465 --> 33:53.632 to improve our messaging-- 33:53.652 --> 33:56.061 - [Male Panelist] A tracking device, more. 33:56.061 --> 33:59.914 - So essentially EISS will have cleaner inputs, 33:59.914 --> 34:02.174 essentially on the form and how the data 34:02.174 --> 34:04.424 is entered into the system. 34:05.882 --> 34:07.421 Did I answer your question, sir? 34:07.421 --> 34:08.925 - Yeah, I just wanted to throw 34:08.925 --> 34:09.758 some modern technology, 34:09.758 --> 34:12.473 'cause I do have a smart phone, not a flip phone, 34:12.473 --> 34:14.930 so I'm aware of how that stuff operates. 34:14.930 --> 34:17.142 (laughing) 34:17.142 --> 34:18.975 - [Ahbi] I understand. 34:19.026 --> 34:20.109 - Had to hit you on that. 34:20.109 --> 34:20.942 - Touche. 34:21.174 --> 34:23.395 (panelists laughing) 34:23.395 --> 34:24.426 - The case management tool 34:24.426 --> 34:26.851 that I eluded to a little bit ago 34:26.851 --> 34:27.833 will still be intact, 34:27.833 --> 34:30.470 but there's an aspect of it that coordinates the service. 34:30.470 --> 34:32.009 Usually about, I don't know, 34:32.009 --> 34:33.161 Ms. Yates off the top of your head, 34:33.161 --> 34:35.049 do you know the percentage of callers 34:35.049 --> 34:38.743 that call to schedule a loved one for a service? 34:38.743 --> 34:42.076 - I know the number total exceeds 7,000. 34:43.734 --> 34:45.984 It's closer to 7,500 a year 34:47.273 --> 34:48.902 calls just to schedule service. 34:48.902 --> 34:51.122 And then on top of that, every call, 34:51.122 --> 34:55.289 every one of those has probably got at least 25 calls 34:55.363 --> 34:56.810 associated with it. 34:56.810 --> 35:00.977 - Right, so when that process is essentially initiated 35:01.517 --> 35:04.991 they record information in to this case tracking tool. 35:04.991 --> 35:07.279 What we refer to as ANC case management, 35:07.279 --> 35:11.362 it's a customized cost product off of BMC remedy. 35:12.489 --> 35:15.656 We want to decouple that and centralize it into EISS 35:15.656 --> 35:17.889 because what we are essentially find out is 35:17.889 --> 35:19.569 our same cemetery representatives 35:19.569 --> 35:21.129 have to access two systems, 35:21.129 --> 35:22.533 they have to take data out of one 35:22.533 --> 35:24.900 and rerecord it manually into the other. 35:24.900 --> 35:28.212 We could invest in integrating the applications 35:28.212 --> 35:30.603 but then that is also more footprint 35:30.603 --> 35:31.722 from an IT standpoint 35:31.722 --> 35:34.225 and more maintenance from the IT standpoint. 35:34.225 --> 35:35.488 It's best to integrate it into 35:35.488 --> 35:37.253 something where we can determine eligibility 35:37.253 --> 35:38.585 within one system 35:38.585 --> 35:40.342 and then have that record continue on 35:40.342 --> 35:42.169 for the rest of the scheduling process 35:42.169 --> 35:44.380 and then ultimately ordering a marker, 35:44.380 --> 35:47.463 and then having that QA'ed and so on. 35:47.945 --> 35:49.117 And then that takes me to the next point. 35:49.117 --> 35:51.185 Marker order system will allow us to expand 35:51.185 --> 35:53.453 the current capabilities that we do today. 35:53.453 --> 35:55.190 Several years ago we had, 35:55.190 --> 35:57.735 when we implemented this marker order system 35:57.735 --> 36:01.366 it was the ability to work in conjunction with the VA 36:01.366 --> 36:02.509 because they're the ones 36:02.509 --> 36:03.548 who actually produce the markers 36:03.548 --> 36:05.500 and their contract teams. 36:05.500 --> 36:06.922 And then they send it to us. 36:06.922 --> 36:10.424 This will allow us to actually order in bulk. 36:10.424 --> 36:13.330 As you know, we do 30 services a day 36:13.330 --> 36:14.163 here at this cemetery. 36:14.163 --> 36:16.913 So in a weeks time, 150 services, 36:18.318 --> 36:20.228 there's a lot of markers to order. 36:20.228 --> 36:23.312 So if somebody were to go into the VA system 36:23.312 --> 36:24.895 and hand-type it in 36:25.148 --> 36:26.353 it could take a whole day 36:26.353 --> 36:28.587 or a couple of days to actually process. 36:28.587 --> 36:31.697 And the backlog would be growing faster than 36:31.697 --> 36:33.264 what they can actually output. 36:33.264 --> 36:35.065 So that's why the marker order system 36:35.065 --> 36:38.448 is actually very vital for our operations. 36:38.448 --> 36:40.363 And then the last module would be the quality assurance 36:40.363 --> 36:42.676 is to the constant, comprehensive check 36:42.676 --> 36:45.206 on our own data and how it's being recorded 36:45.206 --> 36:48.539 existing and to be prescribed processes. 36:50.198 --> 36:52.117 Arlington's processes are very, very tight 36:52.117 --> 36:54.214 in terms of what we've learned over 36:54.214 --> 36:56.881 many, many decades of operating. 36:58.414 --> 37:00.440 So the QA team is an independent team 37:00.440 --> 37:03.401 that is meant for assessing our process 37:03.401 --> 37:06.363 and making sure that we're adhering to our own 37:06.363 --> 37:08.107 prescribed processes, so that our data 37:08.107 --> 37:10.857 is flowing in and out cohesively. 37:13.220 --> 37:15.553 Any questions on this slide? 37:15.769 --> 37:18.019 Anything to add, Ms. Yates? 37:18.397 --> 37:20.051 - [Ms. Yates] Great job. 37:20.051 --> 37:20.914 - Alright, this next slide 37:20.914 --> 37:23.247 I'm gonna give a brief demo, 37:23.264 --> 37:25.561 I believe everyone has a copy of this slides 37:25.561 --> 37:28.647 so I'm just gonna break away from the presentation here. 37:28.647 --> 37:30.745 And give you a quick demonstration 37:30.745 --> 37:33.662 of what EISS is meant to look like. 37:34.875 --> 37:36.594 It's currently still in development, 37:36.594 --> 37:40.103 but we were given this demonstration back in March, 37:40.103 --> 37:43.424 so in that time they're made significant progress as well, 37:43.424 --> 37:46.755 but what I have is still the build copy from March 37:46.755 --> 37:47.755 to show you. 37:50.994 --> 37:52.956 Would it be sufficient to show ISS as well? 37:52.956 --> 37:53.789 - [Ms. Yates] I was gonna say, well, 37:53.789 --> 37:57.956 so essentially from, and somebody mentioned about training 37:59.478 --> 38:02.415 the field crew and the use of the tools, 38:02.415 --> 38:04.962 my biggest concern was changing a system 38:04.962 --> 38:08.212 that has better data integrity with it, 38:09.416 --> 38:12.512 but now I put myself behind the power curve 38:12.512 --> 38:14.682 of teaching them a whole new interface. 38:14.682 --> 38:17.765 So the system itself reflects greatly 38:18.362 --> 38:20.100 on how we operate today. 38:20.100 --> 38:23.250 The look and feel of this page is much like 38:23.250 --> 38:26.833 what my interment services team would see-- 38:27.172 --> 38:29.063 he's gonna bring it up real quick. 38:29.063 --> 38:31.813 For our burial system today, ISS. 38:34.429 --> 38:37.496 It's gonna have the same functionality 38:37.496 --> 38:41.663 but it will talk to itself and inside itself much better. 38:50.162 --> 38:51.043 So as you can see, - So this is what-- 38:51.043 --> 38:53.126 - It's very similar look. 38:53.304 --> 38:55.219 - You have your navigation pane on the left, 38:55.219 --> 38:56.812 you have a summary of the information 38:56.812 --> 38:58.190 on the schedule screen on the top. 38:58.190 --> 39:00.690 All of the services for today, 39:01.348 --> 39:04.098 with an notable active duty here, 39:05.425 --> 39:06.425 and another, 39:07.272 --> 39:08.729 with all the data kind of populating 39:08.729 --> 39:10.166 for everyone, situational awareness, 39:10.166 --> 39:11.916 for today's services. 39:12.366 --> 39:14.250 Similarly, we wanted to maintain that 39:14.250 --> 39:15.171 like Ms. Yates said, 39:15.171 --> 39:18.476 we want to make it easier to adapt to a new system 39:18.476 --> 39:21.401 without it feeling completely like a fish out of water 39:21.401 --> 39:24.734 when you're trying to maintain the rate. 39:26.441 --> 39:27.299 - Pace of-- - And pace 39:27.299 --> 39:28.400 of operations, too. 39:28.400 --> 39:29.384 - [Ms. Yates] Operational tempo of 39:29.384 --> 39:31.005 scheduling services each day 39:31.005 --> 39:33.922 for conducting 150 services a week. 39:34.213 --> 39:35.296 - Right, so-- 39:36.315 --> 39:38.902 earlier I mentioned, and we talked about 39:38.902 --> 39:40.262 one of the themes for today, 39:40.262 --> 39:43.332 was about mobility and being able to access this data 39:43.332 --> 39:44.673 while you're out in the field. 39:44.673 --> 39:47.760 I mean we know that the cemetery's not run entirely 39:47.760 --> 39:49.276 from behind a desk, 39:49.276 --> 39:52.030 so it makes it all the more imperative 39:52.030 --> 39:55.333 to be able to access these systems from a tablet 39:55.333 --> 39:58.481 and to see what it would look like on a tablet. 39:58.481 --> 40:01.624 So that is why, even though this is what's considered 40:01.624 --> 40:04.486 a web application, not a native application, 40:04.486 --> 40:07.153 it's accessed through a website, 40:07.720 --> 40:10.769 that this site be what's called responsive 40:10.769 --> 40:13.186 or responsive user interface. 40:13.190 --> 40:16.942 It's an industry term that's meant to show flexibility 40:16.942 --> 40:18.253 on multiple screens, 40:18.253 --> 40:20.419 so if you're on a mobile or a tablet, 40:20.419 --> 40:22.023 or behind a projector or something like that 40:22.023 --> 40:23.038 where it expands 40:23.038 --> 40:25.621 and allows for viewing the data 40:26.206 --> 40:27.675 and the information a little bit better. 40:27.675 --> 40:30.507 So I'm just gonna show that as an example here. 40:30.507 --> 40:34.340 And how the table, if you look at the summary, 40:34.865 --> 40:37.493 and know that this is just a test site, 40:37.493 --> 40:39.914 so there's gonna be some misspellings and stuff. 40:39.914 --> 40:44.081 But we just wanted to show you the functionality here. 40:45.070 --> 40:47.637 And how the table is shrinking, 40:47.637 --> 40:48.865 as I drag my screens. 40:48.865 --> 40:50.757 And the menu is also changing. 40:50.757 --> 40:52.340 It's just adapting. 40:53.387 --> 40:56.129 So that is the goal of responsive UI, 40:56.129 --> 40:58.747 and they did a good job with that. 40:58.747 --> 41:01.427 It's backed by a technology called Bootstrap 41:01.427 --> 41:04.143 which allows you to rapidly build 41:04.143 --> 41:06.978 these responsive frameworks very quickly 41:06.978 --> 41:09.811 so it's an open source technology. 41:10.630 --> 41:13.880 And here like we saw in the ISS screen, 41:15.365 --> 41:19.032 EISS will be fitted with all the information 41:19.862 --> 41:23.616 and on the left we have to modules or components 41:23.616 --> 41:26.033 that we will extend this base 41:26.045 --> 41:29.545 Enterprise Interment Services System with. 41:30.587 --> 41:33.670 So the burial requests will supersede 41:34.285 --> 41:37.325 the need for using the case management tool for scheduling. 41:37.325 --> 41:38.926 So a process will be, 41:38.926 --> 41:41.387 when somebody calls, they'll open up EISS, 41:41.387 --> 41:43.925 and be in that process for creating a record. 41:43.925 --> 41:47.957 And we have, I think, the ability to kind of show 41:47.957 --> 41:49.329 at a high level-- 41:49.329 --> 41:51.205 - One of the points I want to make here 41:51.205 --> 41:53.372 is highlight to this body, 41:53.376 --> 41:54.754 that if you'll recall, 41:54.754 --> 41:58.165 one of the department of defense IG deficiencies 41:58.165 --> 41:59.832 was this duel entry. 42:00.883 --> 42:02.667 This data integrity, duel entry to system. 42:02.667 --> 42:04.347 And this implementation of this 42:04.347 --> 42:06.954 and the, from the initial barrel request forward, 42:06.954 --> 42:08.787 it'll be in one system 42:10.226 --> 42:11.125 and that data will be able to be maintained 42:11.125 --> 42:14.125 and quality checked in one location. 42:14.395 --> 42:15.228 - Right. 42:17.706 --> 42:19.067 And this is, again, very notional. 42:19.067 --> 42:21.136 There's a lot of work to be done 42:21.136 --> 42:23.993 in terms of actually building this functionality out, 42:23.993 --> 42:25.645 which they're currently doing. 42:25.645 --> 42:26.478 - [Male Panelist] Who's doing? 42:26.478 --> 42:27.656 You said they're doing, who's doing? 42:27.656 --> 42:29.256 - It's a contract team. 42:29.256 --> 42:32.506 Ms. Yates, if we're permitted to say--? 42:32.888 --> 42:33.888 - I'm just-- 42:35.107 --> 42:37.102 so this is not DOD that's doing this? 42:37.102 --> 42:41.202 - No this is an ANC funded project within the OCIO. 42:41.202 --> 42:44.924 So the chief of information officer is overseeing this. 42:44.924 --> 42:47.730 And Ms. Gaspar and I are part of that organization. 42:47.730 --> 42:49.572 - So this is exactly what I'm looking at right here. 42:49.572 --> 42:52.942 You mentioned something earlier about burial requests 42:52.942 --> 42:54.364 but this is the person that initiated? 42:54.364 --> 42:55.197 - [Ahbi] That's correct. 42:55.197 --> 42:56.170 - That's what I was talking about, 42:56.170 --> 42:57.003 so if they initiate, 42:57.003 --> 42:59.564 now see the email address out there, 42:59.564 --> 43:01.091 so as it goes through the channels, 43:01.091 --> 43:02.052 the check and balance-- 43:02.052 --> 43:05.370 the next level it could be notified or whatever. 43:05.370 --> 43:06.970 That's why I asked that question. 43:06.970 --> 43:09.443 - There are definitely areas in the process 43:09.443 --> 43:11.793 where we could send a notification message, 43:11.793 --> 43:13.662 and we currently do that today. 43:13.662 --> 43:14.873 - We currently use that today - Okay. 43:14.873 --> 43:18.012 - For some things. Not necessarily remains related. 43:18.012 --> 43:19.512 - But yeah, right. 43:20.802 --> 43:24.372 So we will continue to maintain existing functionality 43:24.372 --> 43:27.524 but improve it in terms of how it's organized 43:27.524 --> 43:28.357 in the actual system. 43:28.357 --> 43:29.564 So if we have to modify it, 43:29.564 --> 43:33.731 it wouldn't invest a whole lot of IT development time. 43:35.371 --> 43:37.560 (man clears throat) 43:37.560 --> 43:39.137 So don't want to spend a whole lot of time 43:39.137 --> 43:40.047 going over the key aspects 43:40.047 --> 43:41.600 as I have done in the previous slide, 43:41.600 --> 43:43.861 but I mentioned one of the key facets 43:43.861 --> 43:46.361 of EISS and what makes it EISS 43:46.470 --> 43:49.970 is the scalability to multiple cemeteries, 43:50.147 --> 43:51.647 or multiple sites. 43:52.460 --> 43:56.293 This would be the intended navigability aspect 43:56.588 --> 43:59.610 of changing your perspective of what data 43:59.610 --> 44:01.901 or what cemetery you're currently operating within 44:01.901 --> 44:03.061 the application. 44:03.061 --> 44:05.032 Now it is going to be a role based system. 44:05.032 --> 44:08.115 Currently for demonstration purposes, 44:08.822 --> 44:10.800 I have access to all these cemeteries 44:10.800 --> 44:13.500 and, you know, some don't really have an image yet, 44:13.500 --> 44:15.400 we're still working on gathering all the images 44:15.400 --> 44:16.900 for each cemetery. 44:18.301 --> 44:22.468 But the intention is to be able to switch and toggle 44:23.832 --> 44:25.971 which cemetery you're currently operating in. 44:25.971 --> 44:27.342 Now there's no real data behind this. 44:27.342 --> 44:30.422 This is just for demonstration purposes only. 44:30.422 --> 44:33.172 But that is the intended way to-- 44:33.432 --> 44:35.765 or the proposed way that way 44:35.945 --> 44:38.232 that we intend to adhere to that requirement 44:38.232 --> 44:40.262 of managing multiple sites. 44:40.262 --> 44:41.432 - So, for instance, 44:41.432 --> 44:43.120 he switched to Soldiers and Airmen's Home. 44:43.120 --> 44:46.037 Those services are scheduled by ANC 44:47.261 --> 44:49.537 'cause ANC manages that cemetery. 44:49.537 --> 44:52.617 So the cemetery representatives would be able 44:52.617 --> 44:55.450 just to switch right to that page. 44:56.967 --> 44:58.756 I guess that's the right word for it. 44:58.756 --> 44:59.589 - [Ahbi] Right. 44:59.589 --> 45:01.105 - What's the right word for it, Ahbi? 45:01.105 --> 45:01.938 - [Ahbi] It's just a multiple-- 45:01.938 --> 45:02.796 it's another site. 45:02.796 --> 45:03.927 - Right, like that site. 45:03.927 --> 45:05.985 And be able to manage data 45:05.985 --> 45:08.527 for the Soldiers and Airmen's home that simply. 45:08.527 --> 45:11.047 Right now, today, it's not that simple. 45:11.047 --> 45:12.465 I have to open up a different interface, 45:12.465 --> 45:14.116 I have to use a diff-- 45:14.116 --> 45:16.377 have to have different permissions, different-- 45:16.377 --> 45:19.185 It's just another management process we have to go through. 45:19.185 --> 45:20.196 This simplifies it. 45:20.196 --> 45:22.696 And for all of the ANMC staff, 45:23.276 --> 45:24.305 who's responsible for, 45:24.305 --> 45:26.817 you know has that broader over sight, 45:26.817 --> 45:30.984 they would have access to looking down into all of them. 45:32.196 --> 45:36.057 And I dare to say, potentially dashboard ability 45:36.057 --> 45:39.564 for all the data, for all the army cemeteries. 45:39.564 --> 45:41.791 - Because we're dealing with multiple sets of data, 45:41.791 --> 45:42.684 we have to decide, 45:42.684 --> 45:44.912 and there's gotta be a governance effort 45:44.912 --> 45:47.394 behind this internally within the army, 45:47.394 --> 45:50.015 that decides who gets to see what data 45:50.015 --> 45:53.182 and who is the audience for that data. 45:53.254 --> 45:55.254 - [Male Panelist] Input. 45:55.604 --> 45:56.437 - Not only just inputting 45:56.437 --> 45:57.834 but also the outputs as well, right? 45:57.834 --> 45:59.935 So we want to see the aggregates 45:59.935 --> 46:01.866 and who should have access. 46:01.866 --> 46:05.234 I would think that the people who are stewards of the data, 46:05.234 --> 46:07.484 who are maintaining the data, 46:07.484 --> 46:09.984 should be able to have access. 46:10.044 --> 46:13.195 So those are generally called super users, 46:13.195 --> 46:16.153 people who have kind of like almost God privileges 46:16.153 --> 46:17.235 on an application, 46:17.235 --> 46:18.491 where they can see everything. 46:18.491 --> 46:22.658 That's why we have to build in this role based system, 46:22.882 --> 46:25.402 or role based access control so that 46:25.402 --> 46:27.762 if you do not have that access 46:27.762 --> 46:29.629 you shouldn't be able to see that data. 46:29.629 --> 46:32.202 So it's just that whole need to know aspect of 46:32.202 --> 46:35.535 and compliance of information assurance. 46:35.540 --> 46:37.820 And to show and example of that 46:37.820 --> 46:39.052 we have users and roles. 46:39.052 --> 46:41.385 And we should be able to see 46:41.751 --> 46:45.168 that I should be able to look for a user. 46:47.459 --> 46:48.292 Let's see. 46:48.292 --> 46:52.375 There's only one user in this demonstration, so-- 46:53.126 --> 46:56.665 I should be able to edit this person's information 46:56.665 --> 46:59.248 and give and assign permissions 46:59.396 --> 47:02.313 as I see fit for this person's role 47:03.055 --> 47:06.888 as they play in Arlington or whatever cemetery 47:07.477 --> 47:11.144 across the army portfolio and DOD portfolio. 47:11.544 --> 47:14.348 - And this is, I know, this is important to us 47:14.348 --> 47:16.615 because right now this system we have 47:16.615 --> 47:19.532 doesn't have this level of control. 47:23.959 --> 47:26.140 It's an all or nothing system. 47:26.140 --> 47:26.973 - That's correct. 47:26.973 --> 47:30.890 We have very broad stroke roles and permissions 47:31.330 --> 47:34.407 and it's not granular to the point where 47:34.407 --> 47:35.620 if you didn't want somebody 47:35.620 --> 47:37.519 to meddle with a particular aspect, 47:37.519 --> 47:41.610 and you wanted to kind of cut off that functionality 47:41.610 --> 47:44.860 so that you could retrain for instance, 47:44.959 --> 47:46.768 stop the bleeding so to speak, 47:46.768 --> 47:50.226 so that you don't have to invest more resources internally 47:50.226 --> 47:51.809 to fix the records. 47:51.876 --> 47:54.876 You can manage more discretely here, 47:54.959 --> 47:56.126 which is nice. 47:57.239 --> 47:58.988 And you can also create custom roles. 47:58.988 --> 48:01.820 And this helps with our in-processing and out-processing 48:01.820 --> 48:04.070 aspects of our organization 48:04.542 --> 48:06.039 and training as well. 48:06.039 --> 48:07.420 If you want to pick a canned role 48:07.420 --> 48:08.700 that they're filling in, 48:08.700 --> 48:11.519 if interment services hires a new cem rep, 48:11.519 --> 48:12.860 then we can just say 48:12.860 --> 48:15.828 assign these permissions and they're ready to go. 48:15.828 --> 48:19.159 And, you know, there's different stakeholders 48:19.159 --> 48:20.178 that use this system. 48:20.178 --> 48:23.761 We have chaplains that offer their services 48:24.638 --> 48:26.290 for the actual funeral services, 48:26.290 --> 48:27.757 and they need to see that data too, 48:27.757 --> 48:29.840 but maybe not everything. 48:29.877 --> 48:32.745 They need to see just kind of the areas they touch. 48:32.745 --> 48:36.306 So that's another area where we will flush out, 48:36.306 --> 48:38.473 in terms of functionality. 48:39.105 --> 48:40.510 Any questions about roles? 48:40.510 --> 48:43.377 - How hardwired versus configurable is this? 48:43.377 --> 48:44.497 - Because it's custom, 48:44.497 --> 48:46.080 it'll allow us to-- 48:46.597 --> 48:48.097 we have a lot of-- 48:48.559 --> 48:49.479 well let me just back up. 48:49.479 --> 48:51.812 We've, particularly my team, 48:52.159 --> 48:54.748 has prescribed a change management process 48:54.748 --> 48:57.331 for vetting IT change requests, 48:59.908 --> 49:02.439 particularly around EISS and ISS 49:02.439 --> 49:04.939 and we do also consider Mapper 49:05.067 --> 49:07.167 and all the integrated systems as well. 49:07.167 --> 49:10.598 But we have a significant backlog of ideas 49:10.598 --> 49:13.559 that have flowed through our system for the last four years, 49:13.559 --> 49:15.047 through that process. 49:15.047 --> 49:16.967 And what that'll allow us to do 49:16.967 --> 49:20.588 is comprehensively continue to push to improve this. 49:20.588 --> 49:22.528 Now technologically speaking, 49:22.528 --> 49:23.719 because it is custom, 49:23.719 --> 49:26.047 we have this entire backlog in mind, 49:26.047 --> 49:28.177 and we will be scaling this system, 49:28.177 --> 49:30.079 so that with the ideas in mind-- 49:30.079 --> 49:31.537 - Just a little different, 49:31.537 --> 49:33.177 I mean I appreciate the importance of 49:33.177 --> 49:36.266 configuration management and governance and all that. 49:36.266 --> 49:40.433 What I'm asking is what are your design principles 49:40.646 --> 49:42.118 about configurability 49:42.118 --> 49:46.118 as opposed to having to have another project yet 49:46.977 --> 49:49.977 to add a line or a role or whatever. 49:51.247 --> 49:54.247 So that goes a little bit back to what I am saying 49:54.247 --> 49:57.664 about more universal applicability of it. 49:57.777 --> 49:58.988 When you get different users that say, 49:58.988 --> 50:01.319 I don't have that role, I have this role, 50:01.319 --> 50:02.748 or I want to add a-- 50:02.748 --> 50:03.998 - [Ahbi] Right. 50:04.206 --> 50:06.169 - A muslim chaplain or something. 50:06.169 --> 50:07.419 - Right, right. 50:08.342 --> 50:09.259 So in that, 50:09.983 --> 50:12.244 I don't have a way to show or demonstrate that. 50:12.244 --> 50:14.314 - The answer is yes, sir. 50:14.314 --> 50:16.874 That is the one thing that frustrates me 50:16.874 --> 50:17.964 more than anything else right now 50:17.964 --> 50:19.433 about my current system 50:19.433 --> 50:21.766 is when, I'll say the truth, 50:22.032 --> 50:24.282 or when the reality changes 50:24.502 --> 50:27.141 and we want to add something that I believe 50:27.141 --> 50:28.579 is a very simple add, 50:28.579 --> 50:31.329 type of chaplain, add a new role. 50:32.164 --> 50:34.044 We will have a management- 50:34.044 --> 50:35.474 you have the, we have it up there right? 50:35.474 --> 50:36.307 What's the-- 50:36.307 --> 50:38.484 - [Ahbi] Yeah, managing roles-- 50:38.484 --> 50:40.317 - No, the CMS of this. 50:41.883 --> 50:43.216 - [Ahbi] As far as the -- 50:43.216 --> 50:45.644 - The content management edit-ability, 50:45.644 --> 50:47.394 the super user admin. 50:47.484 --> 50:50.204 - Yeah, so if I show an example of ISS 50:50.204 --> 50:51.572 I can show the resources 50:51.572 --> 50:55.739 and to illustrate Ms. Yates' frustration is that... 51:05.562 --> 51:08.002 You can see that ANC is customized 51:08.002 --> 51:09.612 with all the types of resources. 51:09.612 --> 51:11.591 So to your point, Mr. Peake, you mentioned 51:11.591 --> 51:14.758 if I wanted to add a Imam for instance 51:16.871 --> 51:20.380 if that were something that we were to add. 51:20.380 --> 51:23.231 Right now, we don't have that capability. 51:23.231 --> 51:25.452 We have to issue a change request 51:25.452 --> 51:28.702 and have it accommodated by a developer 51:29.508 --> 51:31.341 or a development team. 51:31.461 --> 51:35.313 - That's different than saying it's configurable. 51:35.313 --> 51:38.392 What you're saying is you gotta re-hardwire-- 51:38.392 --> 51:39.883 - Currently. - Currently. 51:39.883 --> 51:40.917 - What we intend to go to 51:40.917 --> 51:42.656 is a system that will be configurable. 51:42.656 --> 51:43.755 - [Mr. Peake] That was my question. 51:43.755 --> 51:46.016 - I wasn't sure if you were asking technically, 51:46.016 --> 51:49.026 in the weeds, about the architecture, or-- 51:49.026 --> 51:52.307 - Yeah it is, the architecture has to support that 51:52.307 --> 51:53.645 if you're gonna go that way. 51:53.645 --> 51:54.962 I'm not hearing. 51:54.962 --> 51:56.945 I'm just trying to understand. 51:56.945 --> 51:57.778 - No problem, sir. 51:57.778 --> 52:01.945 So essentially that entry is just another row in a table. 52:02.803 --> 52:04.471 Right now we have no way to insert 52:04.471 --> 52:05.780 a row in a table. 52:05.780 --> 52:06.613 - [Ms. Yates] But you will have it. 52:06.613 --> 52:07.692 - But we will have it. 52:07.692 --> 52:10.412 That's how they intend to customize the needs 52:10.412 --> 52:13.532 of every cemetery that's under this portfolio 52:13.532 --> 52:15.199 of those using EISS. 52:15.549 --> 52:17.303 - [Male Panelist] So that's saying a resource list 52:17.303 --> 52:18.136 would be available, 52:18.136 --> 52:19.113 would be used for every cemetery? 52:19.113 --> 52:20.113 - It would be-- - Not necessarily. 52:20.113 --> 52:23.863 - It would be customizable based upon what they need. 52:23.863 --> 52:27.394 The differences and so it's the administration tab, 52:27.394 --> 52:28.914 the administrative-- - Right. 52:28.914 --> 52:33.081 - There's a whole new process that we don't currently have. 52:33.362 --> 52:34.234 There he goes. 52:34.234 --> 52:36.172 And that is where we'll be able, 52:36.172 --> 52:39.434 the super user is the term I'm gonna use, 52:39.434 --> 52:41.132 will be able to configure the site 52:41.132 --> 52:44.382 or a particular cemeteries information. 52:46.114 --> 52:47.663 So it's customizable to them. 52:47.663 --> 52:49.343 The answer's yes, sir. 52:49.343 --> 52:51.092 - So like an ANC supervisor 52:51.092 --> 52:55.175 wouldn't want to necessarily manage West Point's. 52:56.620 --> 52:58.703 (faint speaking) 52:58.703 --> 53:01.286 Appreciate the question, sorry. 53:01.322 --> 53:04.322 Anything else you'd like to go over? 53:08.082 --> 53:08.915 Okay. 53:10.892 --> 53:14.809 To Ms. Gaspar's earlier point about the tablets 53:16.463 --> 53:18.903 and why we selected that particular hardware, 53:18.903 --> 53:20.403 was to enable CAC, 53:21.582 --> 53:23.633 you know the Common Access Card, 53:23.633 --> 53:24.884 two factor authentication. 53:24.884 --> 53:28.134 It's a requirement for all DOD systems. 53:28.250 --> 53:29.583 And the hardware 53:29.932 --> 53:33.953 will allow us to access this web application, as well. 53:33.953 --> 53:36.692 So this will be a CAC enabled application 53:36.692 --> 53:40.033 and particularly why we couldn't use Apple products. 53:40.033 --> 53:41.923 - I was gonna say, that's another reason 53:41.923 --> 53:43.590 why we went to this. 53:44.203 --> 53:45.182 Where's the CAC? 53:45.182 --> 53:46.015 - [Ahbi] It's on the back, 53:46.015 --> 53:47.202 it's a little sleeve. 53:47.202 --> 53:50.535 It's being covered up right now by the-- 53:51.372 --> 53:52.205 - So these will be, 53:52.205 --> 53:53.205 there it is. 53:53.901 --> 53:55.604 - So, I can take this apart. 53:55.604 --> 53:58.291 But the other requirement with your card reader 53:58.291 --> 54:00.458 is that when you insert it 54:00.742 --> 54:01.659 it has to-- 54:02.764 --> 54:05.672 your photo should not be facing forward, 54:05.672 --> 54:08.505 and of course now I can't do this. 54:09.942 --> 54:13.609 So it tucks in and now your photos obscured. 54:13.964 --> 54:16.631 So little, tiny, nitpicky things 54:16.741 --> 54:20.164 but this is one of the reasons why it was selected. 54:20.164 --> 54:23.142 Again meeting those IA requirements. 54:23.142 --> 54:24.732 - [Male Panelist] Now the CAC reader, 54:24.732 --> 54:27.892 so you have to have the CAC card from this-- 54:27.892 --> 54:28.812 so like, I would at the Pentagon. 54:28.812 --> 54:30.632 So I couldn't use my CAC in that? 54:30.632 --> 54:33.204 - You could be what you could do would be different. 54:33.204 --> 54:34.037 - [Male Panelist] Okay. 54:34.037 --> 54:35.141 - Correct. - Okay. 54:35.141 --> 54:36.873 - And that's the beauty of these, 54:36.873 --> 54:40.623 they won't have to be configured to the user. 54:41.712 --> 54:42.772 We're all a team, 54:42.772 --> 54:43.605 and I can-- 54:43.605 --> 54:45.862 today I'm working on a certain thing and I'm using it. 54:45.862 --> 54:49.779 And tomorrow Mr. Edwards slips his CAC card in. 54:49.831 --> 54:50.850 So it doesn't have to be assigned 54:50.850 --> 54:52.101 to an individual user. 54:52.101 --> 54:54.202 - [Jill] So Ms. Yates drops hers and breaks it, 54:54.202 --> 54:56.932 she'll say, "Jill, give me your tablet." 54:56.932 --> 54:59.062 And she'll be able to continue. 54:59.062 --> 55:01.593 - But I'm not gonna break it when I drop it! 55:01.593 --> 55:02.702 (laughter) 55:02.702 --> 55:03.822 - True, you can dump coffee on it. 55:03.822 --> 55:04.655 - That's right. 55:04.655 --> 55:06.905 (laughing) 55:09.484 --> 55:12.364 - Alright, these four main lines of effort 55:12.364 --> 55:13.782 that's continually ongoing, 55:13.782 --> 55:17.949 Ms. Yates, just at a high level, I'll just touch base. 55:18.667 --> 55:19.710 We mentioned last year 55:19.710 --> 55:23.210 that we're focusing on a migration effort. 55:24.240 --> 55:26.571 Some pieces of that are still ongoing. 55:26.571 --> 55:29.051 Partially because of the sheer amount of data 55:29.051 --> 55:31.261 and the size that we have to transfer. 55:31.261 --> 55:33.171 It is an inter-agency effort. 55:33.171 --> 55:34.754 So we have to work, 55:36.221 --> 55:39.502 when I say agency, I'm talking Arlington Cemetery 55:39.502 --> 55:42.432 and a sister agency within the army portfolio, 55:42.432 --> 55:44.182 Army Analytics Group. 55:45.243 --> 55:46.862 So, in coordination with that 55:46.862 --> 55:50.403 there's different contracting rules and regulations 55:50.403 --> 55:52.571 that allow when people can work, 55:52.571 --> 55:54.163 and how to get the data over, 55:54.163 --> 55:57.043 and what method we can actually transfer the data. 55:57.043 --> 55:58.038 So that's still ongoing 55:58.038 --> 56:00.331 and our target for completion is, I believe, 56:00.331 --> 56:01.852 at the end of this month. 56:01.852 --> 56:03.185 - Which will be, 56:03.887 --> 56:05.867 call it the first domino that will fall 56:05.867 --> 56:09.784 that will get us down the road a little faster. 56:10.825 --> 56:12.614 - And what this slide is meant to illustrate 56:12.614 --> 56:16.123 is that these lines of effort are being done in parallel. 56:16.123 --> 56:19.123 The second line of effort is the ISS 56:19.153 --> 56:22.692 current operations and maintenance enhancements 56:22.692 --> 56:26.609 that we've selected about 12-14 change requests 56:27.250 --> 56:30.917 to scale to the immediate needs of Ms. Yates 56:31.345 --> 56:33.262 and the ANC leadership, 56:33.643 --> 56:37.810 of what they've decided to improve 'til we get EISS. 56:38.083 --> 56:40.553 We're also consolidated our iOS, 56:40.553 --> 56:43.854 our Apple based photo applications that currently 56:43.854 --> 56:46.854 enable our QA team members to go out 56:48.553 --> 56:50.123 and take photographs of these markers 56:50.123 --> 56:52.843 after they've been ordered and set. 56:52.843 --> 56:55.305 We are consolidating that so it can be used 56:55.305 --> 56:56.574 exclusively on the tablets, 56:56.574 --> 56:59.611 so that you have one device to do everything, 56:59.611 --> 57:03.028 Mapper, website, EISS, photo application. 57:05.043 --> 57:08.742 So we actually just completed the alpha testing, 57:08.742 --> 57:11.113 we're heading towards beta testing, 57:11.113 --> 57:13.771 where we're gonna be testing more functionality 57:13.771 --> 57:15.854 such as saving the record 57:16.193 --> 57:19.693 and how to post that record to a database. 57:21.073 --> 57:22.883 And then eventually the EISS build out 57:22.883 --> 57:24.514 which is targeted currently 57:24.514 --> 57:27.681 at the current op tempo of early 2018. 57:30.686 --> 57:34.853 And the bright box to the right of that blue arrow, 57:35.158 --> 57:38.138 we have all the priorities of modules 57:38.138 --> 57:39.694 that we will be focusing on. 57:39.694 --> 57:41.249 So in an iterative method, 57:41.249 --> 57:43.337 we will be focusing on multiple sites, 57:43.337 --> 57:45.068 roles and permissions, 57:45.068 --> 57:46.866 the resource management, like we talked up, 57:46.866 --> 57:50.033 configurability, the chain of custody. 57:50.369 --> 57:52.729 And then barrel requests, marker system, and QA 57:52.729 --> 57:55.867 to round out the big pieces or the pillars 57:55.867 --> 58:00.034 of maintaining the op-tempo of ANC administration. 58:04.769 --> 58:07.609 And that, I basically summarized that in the previous slide. 58:07.609 --> 58:10.253 - [Ms. Yates] Hey, you basically went through most of this. 58:10.253 --> 58:13.198 - This is just to kind of illustrate 58:13.198 --> 58:15.278 the development teams progress 58:15.278 --> 58:17.346 and what they've been setting up, 58:17.346 --> 58:18.998 the application framework, 58:18.998 --> 58:22.748 how effectively they've been with several CRs 58:23.306 --> 58:25.417 and how close we are to an actual deployment 58:25.417 --> 58:27.250 of a software release. 58:28.737 --> 58:31.398 And what we'll be focusing on next, 58:31.398 --> 58:32.617 this coming Monday, 58:32.617 --> 58:36.078 my team and several other folks within the OCIO 58:36.078 --> 58:38.617 will be working in conjunction with that development team 58:38.617 --> 58:40.617 to map out other functionality 58:40.617 --> 58:44.198 that we intend to release in the next build. 58:44.198 --> 58:47.031 We are working constantly on this. 58:48.063 --> 58:50.230 Any feedback or questions? 58:51.377 --> 58:52.210 - [Male Panelist] Just a comment. 58:52.210 --> 58:53.049 - Yes, sir. 58:53.049 --> 58:55.969 - The days of the smoke signal, pony express, 58:55.969 --> 58:58.102 telegram, we've come a long way. 58:58.102 --> 59:00.121 I like the direction we're going. 59:00.121 --> 59:01.198 I like the product. 59:01.198 --> 59:04.615 I know it'll probably get better in time. 59:05.108 --> 59:06.108 I like that. 59:06.344 --> 59:07.177 - [Ahbi] Thank you, sir. 59:07.177 --> 59:08.435 - [Male Panelist] I could see it's user friendly. 59:08.435 --> 59:09.595 - Did you save the old file cards 59:09.595 --> 59:11.542 that they used to use when you guys came in? 59:11.542 --> 59:14.709 - Those went to the national archives. 59:15.336 --> 59:17.503 - Along with the dinosaur. 59:17.906 --> 59:21.573 - We did save a couple just for memory sake. 59:22.003 --> 59:23.453 - And I'm sure everyone knows 59:23.453 --> 59:26.984 those records have been scanned into PDF form, 59:26.984 --> 59:28.343 so we do have access to them, 59:28.343 --> 59:30.223 and it does help today's operations. 59:30.223 --> 59:31.056 - We use them every-- 59:31.056 --> 59:32.144 and this system will allow me 59:32.144 --> 59:34.727 to see them quicker and easier. 59:35.240 --> 59:36.073 - [Female Panelist] Is there a problem 59:36.073 --> 59:37.513 with upload or download time? 59:37.513 --> 59:38.974 Like if you're trying to get a photo 59:38.974 --> 59:42.391 and it's taking you a day to do that or-- 59:42.994 --> 59:44.464 - [Ahbi] With respect to the marker photos? 59:44.464 --> 59:45.755 - The photos on the-- 59:45.755 --> 59:46.588 just getting that information. 59:46.588 --> 59:49.943 - So it depends on which application you're referring to. 59:49.943 --> 59:52.798 If I take it today and then it sends it, 59:52.798 --> 59:55.166 it goes and then it takes a period of time 59:55.166 --> 59:58.499 to get to our system for quality review. 59:59.044 --> 01:00:01.526 But then posting it is relatively quickly. 01:00:01.526 --> 01:00:05.693 And retrieving, once it's been posted, is very quick. 01:00:08.558 --> 01:00:10.975 - [Ahbi] Any other questions? 01:00:12.136 --> 01:00:15.136 - Is this being hosted by DISA then? 01:00:15.447 --> 01:00:18.530 - All DOD systems are hosted by DISA. 01:00:19.118 --> 01:00:20.238 - [Mr. Peake] Talked about server set up, 01:00:20.238 --> 01:00:21.196 and I was just curious. 01:00:21.196 --> 01:00:24.446 - Right, so because we are transferring 01:00:25.778 --> 01:00:28.111 one system from the Pentagon 01:00:28.484 --> 01:00:32.066 to the Army Analytics Group out in Fairfield, California. 01:00:32.066 --> 01:00:34.176 We are maintaining an existing system, 01:00:34.176 --> 01:00:36.166 and all the while, at the same time, 01:00:36.166 --> 01:00:37.336 building up an new system. 01:00:37.336 --> 01:00:39.246 So we had to set up a new set of servers 01:00:39.246 --> 01:00:40.566 for that new system. 01:00:40.566 --> 01:00:43.149 - The Army Analytics Group is-- 01:00:45.696 --> 01:00:47.425 and all of our systems will be out there 01:00:47.425 --> 01:00:49.425 so when we moved Mapper, 01:00:52.265 --> 01:00:55.432 our response times went significantly, 01:00:56.913 --> 01:00:58.183 four times faster. 01:00:58.183 --> 01:00:59.753 - That was one of the initial feedbacks 01:00:59.753 --> 01:01:02.255 we got from staff was once we migrated 01:01:02.255 --> 01:01:05.735 to Army Analytics one of the first calls I got 01:01:05.735 --> 01:01:07.592 was from one of the cemetery reps 01:01:07.592 --> 01:01:09.620 saying this loaded significantly faster 01:01:09.620 --> 01:01:11.537 than they've ever seen. 01:01:11.615 --> 01:01:14.982 So just getting a couple extra minutes a day, 01:01:14.982 --> 01:01:16.065 click though. 01:01:16.922 --> 01:01:18.565 Definitely improves the efficiency 01:01:18.565 --> 01:01:19.903 of our operations. 01:01:19.903 --> 01:01:22.863 - Because there are a mostly virtualized environment, 01:01:22.863 --> 01:01:26.495 we can add computing resources pretty quickly. 01:01:26.495 --> 01:01:28.162 So in Mapper's case, 01:01:29.245 --> 01:01:30.797 prior to the migration we felt 01:01:30.797 --> 01:01:33.697 we could increase the number of computing resources 01:01:33.697 --> 01:01:35.749 in advance of Memorial Day 01:01:35.749 --> 01:01:37.138 and some of these peak traffic weekends, 01:01:37.138 --> 01:01:41.138 so I think that really helped out with explorer. 01:01:44.109 --> 01:01:47.609 - Are there any other questions, comments? 01:01:47.956 --> 01:01:49.639 - I certainly agree-- 01:01:49.639 --> 01:01:53.806 this is a step forward in your digital transformation. 01:01:53.975 --> 01:01:54.997 - Yes, sir. - Thanks. 01:01:54.997 --> 01:01:55.830 - [Ahbi] Thank you. 01:01:55.830 --> 01:01:57.747 I appreciate your time. 01:01:58.071 --> 01:02:00.904 (muffled talking) 01:02:05.668 --> 01:02:07.168 - We're about to-- 01:02:08.796 --> 01:02:10.046 what is it now? 01:02:10.156 --> 01:02:14.323 We're gonna adjourn for executive time for our lunch 01:02:15.804 --> 01:02:18.304 for just the committee members 01:02:18.555 --> 01:02:20.638 and we will then at 12:45 01:02:22.245 --> 01:02:26.412 reconvene in here for the rest of our open agenda. 01:02:27.617 --> 01:02:29.116 - Chairman, could I ask, 01:02:29.116 --> 01:02:32.033 do we need 'til 12:45 or could we-- 01:02:32.356 --> 01:02:33.996 based on the public announcement 01:02:33.996 --> 01:02:35.166 of this being a public meeting, 01:02:35.166 --> 01:02:38.905 can we, I don't know if we all need nearly an hour. 01:02:38.905 --> 01:02:40.583 Unless there are members who need make-- 01:02:40.583 --> 01:02:41.996 - 12:30 if that's-- - 12:30 01:02:41.996 --> 01:02:43.996 Anybody object to 12:30? 01:02:45.955 --> 01:02:48.086 - That'll give us 15 more minutes to talk. 01:02:48.086 --> 01:02:48.919 - Sure. 01:02:48.919 --> 01:02:49.752 - Great. 01:02:49.752 --> 01:02:50.585 - Thanks. 01:02:50.585 --> 01:02:51.418 - [Male Panelist] As we say in the Marine Corps, 01:02:51.418 --> 01:02:52.497 the private pair is correct. 01:02:52.497 --> 01:02:54.747 (laughing) 01:02:55.566 --> 01:02:57.584 - So 12:30 if everyone could be back in their seats please. 01:02:57.584 --> 01:02:58.417 Thank you.