WEBVTT 00:00:00.000 --> 00:00:06.000 Thanks for hanging in there till the end. 00:00:06.000 --> 00:00:12.000 Today I've really enjoyed all the talks it's been really exciting to be a part of this. 00:00:12.000 --> 00:00:12.000 I'm gonna be presenting today on web application-based, digital conceptual site models. 00:00:12.000 --> 00:00:22.000 It's a tool and a technology that we've been developing for a little while. 00:00:22.000 --> 00:00:37.000 Now at Burns, Mcdonald really excited about it, and my name is Colin Planck. 00:00:37.000 --> 00:00:46.000 20 years, a little over 20 years of experience in the environmental industry, and spent the last 50 or so of that developing site. 00:00:46.000 --> 00:00:55.000 Conceptual models, employing environmental sequencing, artigraphy, co-authors with Mike and Rick on that 2,017 EPA. 00:00:55.000 --> 00:01:02.000 Best practices document and a lot of what I'm going to talk about today comes from that. 00:01:02.000 --> 00:01:07.000 It's sort of the next step in taking those Csm elements. 00:01:07.000 --> 00:01:12.000 And really making them more widely available to the team and streamlining. 00:01:12.000 --> 00:01:17.000 Some of the workflows that we've used in that Ess Csm development process. 00:01:17.000 --> 00:01:20.000 And I said all that here because I didn't want to dwell on this slide, because it's really scary to see your face. 00:01:20.000 --> 00:01:32.000 This big, but it does demonstrate that if supplied with one, I'm able to tie and wear a necktie. 00:01:32.000 --> 00:01:44.000 So presentation goals today demonstrated technology that I think has changed the way that we'll use and deliver Csms. 00:01:44.000 --> 00:01:47.000 And I want to give kind of a hands-on. 00:01:47.000 --> 00:01:50.000 Demo Kent is doing away with his good. 00:01:50.000 --> 00:01:54.000 Oh, you're gonna see me tired later at the end. 00:01:54.000 --> 00:01:55.000 Give you a hands-on or a sort of a live action. 00:01:55.000 --> 00:02:06.000 Demo of the standard web application that we're using internally and with our clients called the digital site management tool at the very end of the day to day, we're gonna go out on a limb and try to do a live technology demo here. 00:02:06.000 --> 00:02:21.000 So that could be exciting. So this is something that we received an environmental business journal, technical merit award for this last year, sort of that. 00:02:21.000 --> 00:02:27.000 And just something about the timing of all this. 00:02:27.000 --> 00:02:33.000 It's long been sort of held in best management, practice or guidance. 00:02:30.000 --> 00:02:40.000 That life cycle, conceptual site models are a big goal. 00:02:40.000 --> 00:02:52.000 Right, so not just producing summaries of sight, understanding, and then putting it on a shelf. 00:02:52.000 --> 00:02:58.000 But you know initiating a Csm. At the beginning stages of the Project life Cycle building on that Csm. 00:02:58.000 --> 00:03:13.000 As Ri data comes in the door. Continuing to flesh that out as you test the hypotheses built in your in your in your baseline Csm, and onward and onward through the project lifecycle. 00:03:13.000 --> 00:03:24.000 And so this is always been the goal. But really making that practice has been a challenge, because we're, you know, multiple consultants coming in through multiple contracts, passing on. 00:03:24.000 --> 00:03:30.000 Ri. Reports that have a Csm element of them passing on. 00:03:30.000 --> 00:03:51.000 Maybe even a specific Csm document. But they're kind of locked up as a Pdf, and so I think the timing for this technology is really at a fortunate point here, because we've all seen dashboards they're becoming more and more 00:03:51.000 --> 00:04:01.000 ubiquitous right? Everyone's project meetings include some infographics in a dashboard or the use of different state websites. 00:03:59.000 --> 00:04:18.000 And so we're all really familiar with this technology and it's a great time to apply that to the delivery and the use of conceptual site models so that's where the innovation in this stands. 00:04:18.000 --> 00:04:23.000 Right is not in. Oh, hey! We've learned how to use power bi or web app builder. 00:04:22.000 --> 00:04:25.000 Csm elements to our team. And I think that's really powerful right now. 00:04:25.000 --> 00:04:37.000 So this is a. This is a figure that was put out a couple years ago, horsed it all, and groundwater monitoring and remediation and kind of summarizes again. 00:04:37.000 --> 00:04:43.000 You know where we're where we're at as an industry. 00:04:43.000 --> 00:04:53.000 And so this concept of, you know as Csm maturity grows, you know, it becomes more important to move it past a simple file cabinet Csm, kind of the semi derogatory term for having your Csm. 00:04:53.000 --> 00:05:12.000 And a Pdf. And instead start to integrate your Csm elements with a data structure and a database that allows you to bring legacy and new data together. 00:05:12.000 --> 00:05:19.000 In a, in a queryable database that gives your gives your Csm some sort of rapid update ability all the way to. 00:05:18.000 --> 00:05:36.000 Er technologies to where you're instrumenting points on your Csm with live data streams and sort of creating that kind of glamorous term of a digital desktop twin. 00:05:36.000 --> 00:05:42.000 And so a challenge with this and the digital Csm has always been sort of fragmentation. 00:05:42.000 --> 00:05:45.000 So we use lots of different data types across lots of different platforms. 00:05:45.000 --> 00:05:55.000 And I think you know this web app. Csm gets us past a little of that, or a good chunk of that. 00:05:55.000 --> 00:06:00.000 It's still early times. With some of this you'll see that there are some things that were great about it, and some things that don't. 00:05:59.000 --> 00:06:14.000 So here's some. Here's here's a summary diagram from Wright, Patterson, Air Force base that we put together a while ago in a pfas, related Ri. Right? 00:06:14.000 --> 00:06:16.000 And so these would be some common static Csm elements that would be combined together. 00:06:16.000 --> 00:06:31.000 Your potentiometric contours, your pfast data, spatially shown as points it's sort of a heat map type diagram, maybe a cross-section network. 00:06:31.000 --> 00:06:37.000 Some flow errors on here, portraying sort of process based understanding groundwater flow right? 00:06:37.000 --> 00:06:46.000 And so if you look at the platforms used to put this together, and then, additionally, time series of contaminant data. 00:06:46.000 --> 00:06:50.000 So, if you consider the platforms to put this hodgepodge of information together, you're calling up. 00:06:50.000 --> 00:06:51.000 Excel on your screen. We've all been there pulling up you know the Pdf of the site map. 00:06:51.000 --> 00:07:13.000 Maybe looking at the access database to understand what the data is that you're plotting on your excel plots here, and which point it corresponds with bringing in another cadm for your potentiometric map looking at how those overlay may be complaining to some 00:07:13.000 --> 00:07:20.000 junior member of your staff that you can't read any of the damn labels, cause it's zoom so far out. 00:07:20.000 --> 00:07:20.000 Bringing up your cross section as another Pdf. 00:07:20.000 --> 00:07:30.000 And trying to relate that to your cross sectionsection location on the map. 00:07:30.000 --> 00:07:34.000 And that's another application. And to create that application you're using yet another tool. 00:07:34.000 --> 00:07:39.000 And so aye, aye, right like, next thing you know you've got, even though you've got 2 screens. 00:07:39.000 --> 00:07:47.000 You've got 30 applications open and just when you get them all open and you're about to reach that point where you understand something, it frees up. 00:07:47.000 --> 00:07:53.000 And and it's time for a Martini. 00:07:53.000 --> 00:07:59.000 So, then, so I think these web applications provide an off-the-shelf solution they're not perfect at this stage, but this is really exciting thing is that you can get all these materials together. 00:07:59.000 --> 00:08:12.000 Do some of the groundwork, and you can supply this basic capability to all your team members, and all they need is access to a web browser right? 00:08:12.000 --> 00:08:16.000 So that's the other really key thing, right? There's a little bit of. 00:08:16.000 --> 00:08:19.000 So the goal with designing these is to make them all the same right. 00:08:19.000 --> 00:08:28.000 We try to make ours pretty similar, so that once you've trained up on one of these web applications, you're familiar with this toggle switch sort of technology. 00:08:28.000 --> 00:08:32.000 And you know, sort of format. So you don't have to relearn this tool every time. 00:08:32.000 --> 00:08:37.000 But there's pretty limited learning timeframe, and it's pretty friendly. 00:08:37.000 --> 00:08:43.000 Your team members are just driving something via their web browser. 00:08:43.000 --> 00:08:47.000 Okay. So I think I've already explained this. You know. 00:08:47.000 --> 00:08:51.000 What does the web application be? Csm. All web application is a program that utilizes web browsers. 00:08:51.000 --> 00:08:58.000 There's a lot of web apps already in use in the Federal space, and the goal of a web app based. 00:08:58.000 --> 00:09:05.000 Csm is to make your current Csm. Available to all team members via, simply there, there! 00:09:05.000 --> 00:09:14.000 But web tool, so so I think we're missing a couple slides here. 00:09:14.000 --> 00:09:23.000 Actually, but so this may not be my most recent version that we loaded up this morning, but no, I guess it is, anyway. 00:09:23.000 --> 00:09:23.000 So think about this. Right? So that we're going to look at an example here. 00:09:23.000 --> 00:09:36.000 Shortly. We've developed these for a lot of sites, and the idea is to take this through from a preliminary Csm, provide a tool that's available to the project team throughout the lifespan. 00:09:36.000 --> 00:09:59.000 We've developed these at over over 15 locations nationwide so far, using them to guide remedial investations, remedial alternatives, analysis and provide support to risk assessors and and provide support to risk assessors and so just a smattering of different looks at these you know, we we try 00:09:59.000 --> 00:10:08.000 to keep them in a similar dashboard sort of format, with maybe some different infographics or color schemes depending on the goal of the site. 00:10:08.000 --> 00:10:32.000 Some of these are designed for for managing excavations, and providing sort of summary statistics on excavation, completion, others are designed more like what I'm going to pride the example of today with an active webmap panel that displays iso concentration data cross-section location data allows you to on 00:10:32.000 --> 00:10:40.000 a per well or boring basis. Plot, time, series of product, thickness or analytical results or water levels. 00:10:40.000 --> 00:10:41.000 Etc., and we're using these all over. 00:10:41.000 --> 00:10:49.000 We're again. This is an example from Shepherd Air Force Base, where we're combining basic Gis layers, utility corridors and things to better understand sampling strategies. 00:10:49.000 --> 00:11:00.000 Related to. You know pfastelineation and Ri. 00:11:00.000 --> 00:11:08.000 Investigation, and lastly, we've developed this and used it at Wordswept Air Force Base recently. 00:11:08.000 --> 00:11:15.000 So with this, I'm gonna skip past. These are these are the baked, the the backup slides, in case everything goes to hell. And I have to go back to something. 00:11:15.000 --> 00:11:26.000 Static, so I'm going to skip now to in theory. 00:11:26.000 --> 00:11:34.000 Skip now to the web browser that I have queued up here in the background. 00:11:34.000 --> 00:11:49.000 And so, if you were provided a link to your web app. And incidentally, I went back and forth about sharing the wordsmith example and sharing this. 00:11:49.000 --> 00:11:55.000 And sharing this demo that we developed, using the urbum's data schema. 00:11:55.000 --> 00:12:01.000 And I'm sharing this one because this is available to all of you as a link in the in the electronic file. 00:12:01.000 --> 00:12:01.000 You can go to this kind of silly looking island of Pfoa. 00:12:01.000 --> 00:12:13.000 Oh, slide, and you can click on. Go to the island and you can go to this dashboard and try it out on your own but this is a fictitious site again. 00:12:13.000 --> 00:12:21.000 We called it the Island of Pfo. Oh, and I want to just sort of go through some of the basics of the web application based. 00:12:21.000 --> 00:12:24.000 Csm, here to introduce you to it. So you see, there's a central map. 00:12:24.000 --> 00:12:24.000 Pane here, right? So this is like looking at Google Earth. 00:12:24.000 --> 00:12:39.000 And we've got some points queued up here, and and then there are 3 other data panes here on the on the left, or control panels. 00:12:39.000 --> 00:12:50.000 I should refer them. There's a basic layers control panel here with multiple tabs for geology contamination areas, historical imagery. 00:12:50.000 --> 00:12:54.000 And then, like a pfizer, compound information. 00:12:54.000 --> 00:12:56.000 Widget, and so you can get around here. 00:12:56.000 --> 00:13:04.000 I'm gonna just scooch this over a little bit between all these different data layers. 00:13:04.000 --> 00:13:15.000 That are served up via gis. Right? So this is basic basically sharing some of those static map elements in a layers file here. 00:13:15.000 --> 00:13:18.000 And so let's see here, let's go to geology. 00:13:18.000 --> 00:13:23.000 So I'm gonna start adding some things to this map here, and I'm gonna zoom in. 00:13:23.000 --> 00:13:25.000 This is A, we're gonna make a really busy map here. 00:13:25.000 --> 00:13:25.000 And then we're going to pair it down to something that's manageable. 00:13:25.000 --> 00:13:34.000 So from a geologist perspective. The first thing I want to see is, where do I have? 00:13:34.000 --> 00:13:37.000 Csm cross section. So I'm going to put those on here. 00:13:37.000 --> 00:13:44.000 And these are some basic Csm elements. Now, I'm going to add to this a shallow potentiometric contour map. 00:13:44.000 --> 00:13:50.000 Start to kind of build up the site picture, in theory, looks like these layers. 00:13:50.000 --> 00:13:58.000 Yeah, there they are, in theory and out. Now, indeed, in practice, I'm going to add Pfos contours right? 00:13:58.000 --> 00:14:05.000 So here's sort of say you have some existing iso concentration contours that had been generated by your team in Gis. 00:14:05.000 --> 00:14:07.000 You're sharing those up to the to the webmap. 00:14:07.000 --> 00:14:22.000 You got sort of a busy picture developing here. Maybe we want to add to this and go back here some site labels right so now you're quickly getting into this map. 00:14:22.000 --> 00:14:32.000 That would, if this was a static figure, you would just be going nuts trying to portray this and it's going to take a 1 million different map panels to get around the aisle of Pfa. 00:14:32.000 --> 00:14:38.000 So. One thing is, of course you can zoom in and try to alleviate some of that. 00:14:38.000 --> 00:14:38.000 The scales. The labels all scale dynamically, and so on. 00:14:38.000 --> 00:14:43.000 The next thing you can do is try to pair down through this data with some of these data queries here. 00:14:43.000 --> 00:14:48.000 And that's what these toggle switches are about. 00:14:48.000 --> 00:15:04.000 Is this is produced. So, instead of having to know some Gis sort of basic commands we've set those up already so that you can pair down in here and just say, Show me only the locations with Pfos results. 00:15:04.000 --> 00:15:13.000 And I can turn that toggle switch on, and it'll get rid of a small subset of these I can then say, you know, show me only location. 00:15:13.000 --> 00:15:24.000 Results from, say, you know, monitoring wells and boring locations. 00:15:23.000 --> 00:15:28.000 Health data sets. You toggle on that switch and you can see a good number of our points have gone away. 00:15:28.000 --> 00:15:38.000 So we're starting to simplify that simplify that map a little bit. 00:15:36.000 --> 00:15:51.000 I also like to have things like, show me where the high-quality boring logs are, and apparently most of the points go away on this map at this moment. 00:15:51.000 --> 00:16:01.000 That's typical of our of our sites, you know, or you might go through here and start to talkgle down by. 00:16:01.000 --> 00:16:14.000 Say, I want to understand wells by depth. So here we have a screen interval switch setup here, so we'll say, minimum screen, a top of 10 feet and then 20 feet. 00:16:14.000 --> 00:16:14.000 So just the wells that are screened within a certain interval. 00:16:14.000 --> 00:16:26.000 You can sort of start to slice down through the data, begin to understand where your data lies. 00:16:26.000 --> 00:16:31.000 With respect to the currently mapped, currently mapped plume, geometry and so on. 00:16:31.000 --> 00:16:42.000 Right basic ability to kind of get into and interrogate the data. 00:16:42.000 --> 00:16:47.000 So I'm gonna zoom in now on this central area here. 00:16:47.000 --> 00:16:50.000 And you know, start thinking about other Csm elements. Right? 00:16:50.000 --> 00:16:57.000 So now you've kind of populated this map with some plumes that are of some sort of somewhat in agreement with the potentiometric contours. 00:16:57.000 --> 00:17:10.000 Maybe not a little bit. So maybe you want to start talking about this with the Remedial Action Board or the Regulators, and so on, and start thinking through some of these problems with your project team in terms of data gaps, analysis and so on. 00:17:10.000 --> 00:17:22.000 So you can start to interact with the map now clicking on these points produces a produces a little information window on the wells. 00:17:22.000 --> 00:17:37.000 And all this is is, it's an intersection of that data point with a bunch of underlying Gis layers that we've set up some code to produce a live English sort of summary. 00:17:37.000 --> 00:17:41.000 So it says, here you know, gives you the well. Id total depth screen interval tells you the soil location, etc., etc. 00:17:41.000 --> 00:17:59.000 What crash sites it's associated with, if you scroll down further, you can set up information widgets that provide for you some summary statistics or summary diagrams of, say, Pfos, concentrations and so on. 00:17:59.000 --> 00:18:13.000 So you can start to sort of access data interactively with the map, we can click here on a cross section, pull up the cross section. 00:18:13.000 --> 00:18:20.000 So here we have an Ess Cross section that pops up in theory. 00:18:20.000 --> 00:18:24.000 Serves to you in the, in the web browser. 00:18:24.000 --> 00:18:32.000 You can pull that down simultaneously. Look at that with your with the rest of your map, start to relate. 00:18:32.000 --> 00:18:38.000 Well positioned, spatially on the map to well positioned on a cross section. 00:18:38.000 --> 00:18:41.000 We're going to come back to that here, but you can look at. 00:18:41.000 --> 00:18:50.000 Say, your well screens versus the interpreted hydrostratographic units that your geologist may have set up in in their ess analysis. 00:18:50.000 --> 00:18:55.000 I'm gonna drag this back up here now to the top. 00:18:55.000 --> 00:19:12.000 So you can really start to tear around in the Csm and the nice thing is that, you know. Say, if I'm a geologist working on cross-sections, and I've got some ideas some new ideas that I want to share with the team, I output a new cross-section location. 00:19:12.000 --> 00:19:26.000 to the Webmap, it appears in the webmap, it appears in the web application simultaneously I connect my recent Pdfs to that, and I can share with you my draft and my cross section at the end of the day. 00:19:26.000 --> 00:19:29.000 And you can be seeing that, and in near real time, etc. 00:19:29.000 --> 00:19:39.000 There's also some other tools here that are useful in these web applications, like the historical imagery, swiper, tool. 00:19:39.000 --> 00:19:50.000 You can. If you have a bank of of historic imagery, you can cue that up in here and begin to try to understand changes at your site. 00:19:50.000 --> 00:19:57.000 Potential locations of legacy or historic sources relative to your current plumes, and so on. 00:19:57.000 --> 00:20:10.000 And this again just is an out-of-the-box widget that is available to incorporate into your into your webcsms. 00:20:10.000 --> 00:20:15.000 And let's see here. So let's say we were interested in. 00:20:15.000 --> 00:20:19.000 I'm going to turn off this. 00:20:19.000 --> 00:20:24.000 Turn off this historic image here. 00:20:24.000 --> 00:20:34.000 So kind of whipping through a lot of this, but you can see there's a lot of functionality in here you're able to start kind of building your maps as you need to. 00:20:32.000 --> 00:20:42.000 Widget, so you can annotate the map and capture that. 00:20:42.000 --> 00:20:52.000 I'll show you that shortly. There's also some nice interactive tools that can be developed to allow you to look at. 00:20:52.000 --> 00:21:01.000 Say forensics, data related to Pfos on the fly related to these little interactive lassoing tools. Here. 00:21:01.000 --> 00:21:16.000 So we're gonna go here and look at smattering of pfas ratios across the plume here, and sort of look at for coherent changes in compounds just qualitatively. 00:21:16.000 --> 00:21:25.000 So you can do that on an individual by individual basis, or you can do that in aggregate. 00:21:25.000 --> 00:21:30.000 You can also output. If I zoom in here. 00:21:30.000 --> 00:21:47.000 This is fairly useful. If you want to get some of your data into other software, you can go to another query, Widget here and select certain points on the map to. 00:21:47.000 --> 00:21:57.000 Capture Tabular Output. 00:21:57.000 --> 00:22:03.000 Maybe there we go. So it's going to zoom in on that, and then you can go and export that data. 00:22:03.000 --> 00:22:09.000 Provides a little summary here to you as well, but I'm gonna try save it. 00:22:09.000 --> 00:22:17.000 So here goes. So it pops up here, produces a a. 00:22:17.000 --> 00:22:19.000 I don't know if it's opening it or not. 00:22:19.000 --> 00:22:29.000 But yeah, there it goes, produces a tabular data set for the for the area that you're that you're looking at. 00:22:29.000 --> 00:22:36.000 So you can capture information in that way as well. So we find it really useful, for you know this is all hooked up to via Fme. 00:22:36.000 --> 00:22:45.000 To a an equis or an accuracy database. 00:22:45.000 --> 00:22:52.000 We just use cuts of data from urbums, bring them in and internalize them, and then access them. 00:22:52.000 --> 00:23:06.000 In that way, but once that hookup is created, new data coming into erpums becomes available to the web application as soon as we as soon as we as soon as your project team gets it. 00:23:06.000 --> 00:23:10.000 So now we might sort of look at these and kind of consider, you know. 00:23:10.000 --> 00:23:19.000 Maybe some of the processes at the site. So let me clear this here and let's go back to point locations. 00:23:19.000 --> 00:23:25.000 And so now the last little bit of functionality here that is useful. 00:23:25.000 --> 00:23:30.000 I guess I'm not obscuring anything with this little menu here is to look at. 00:23:30.000 --> 00:23:35.000 Say, you know, we had this cross section up. Say, we're looking at. 00:23:35.000 --> 00:23:43.000 Well, 2767, and well, 2,808, and they appear to be on the same flow path, but with slightly different concentrations. 00:23:43.000 --> 00:23:54.000 If we go and we look at that well pair here on our cross section, you know, and you're starting to think through the geology of your site. 00:23:54.000 --> 00:24:04.000 You know. Here we see well, 27, 6, 7 is screened it's got some pretty high concentrations. It's partly across the little Aquitard into this little incision here. 00:24:04.000 --> 00:24:05.000 Well, 2804 is screened more deeply, but is out of this channel. 00:24:05.000 --> 00:24:21.000 So now, is there anything else in the is there anything else in the in the analytical data that suggests that perhaps they're in differing hydrostratigraphic units right? 00:24:21.000 --> 00:24:29.000 So maybe we see different. 00:24:29.000 --> 00:24:34.000 Analytical behavior. So we're going to go down here to our chart selection here we're going to select. 00:24:34.000 --> 00:24:36.000 Well, 2767. We're gonna look at Pfos. 00:24:36.000 --> 00:24:54.000 Let me turn that on, and we'll see. You know, the time series of data the point gets highlighted on the map and now let's compare it to say, well, 2,804, which was screened in a slightly different zone. 00:24:54.000 --> 00:24:59.000 So let's see, let me go in here and type and right now this is set up to be well pairs that we're comparing. 00:24:59.000 --> 00:25:04.000 You can put as many of these infographic widgets in here as you like. 00:25:04.000 --> 00:25:26.000 Those other projects with high-resight characterization data, we put in like a panel of 6 to display multiple ech, hpt data sets side by side and sort of a virtual cross section. 00:25:26.000 --> 00:25:31.000 So here we'll turn on the info widget here for this one, and so you can see, you know, differing behavior. 00:25:31.000 --> 00:25:53.000 There. And if we consider water levels, this is with respect to depth in the well, just to make the scale easy to look at you know, differing water, level behavior, you can start to try to use your basic time series and your basic understanding of the geology to investigate problems spatially and then capture some of 00:25:53.000 --> 00:26:02.000 that you know, as you work through problem areas, you can start to capture some of that with annotations on the map, you know. Perhaps. 00:26:02.000 --> 00:26:18.000 And this is a pretty effective use of the tool. I've used this with Regulators to come to consensus on investigation points and their collection in working meetings. 00:26:18.000 --> 00:26:25.000 So you can go on here. Add points. Say, you know, add a little annotation that you know. 00:26:25.000 --> 00:26:33.000 Vap 20 to, you know. 20 to 40 feet. Whatever the group had kind of agreed upon. 00:26:33.000 --> 00:26:37.000 Maybe annotate. Add some extra flow arrows, or whatever the group. 00:26:37.000 --> 00:26:53.000 Why the group was thinking this, you know, was an appropriate location to cite additional points of investigation, and then you can capture that as a georeferenced hard copy map or a Pdf. 00:26:53.000 --> 00:27:00.000 And this is gonna cook for a minute while it does that. 00:27:00.000 --> 00:27:04.000 So, yeah, so let's see here. 00:27:04.000 --> 00:27:10.000 So let's do a a 4 landscape different sometimes. 00:27:10.000 --> 00:27:15.000 This takes little time when it's sharing over the over the web. 00:27:15.000 --> 00:27:31.000 Yeah, so these things are very open-ended. There's another example I have of a site here that sort of demonstrates some of the use of this in a high-res site. 00:27:31.000 --> 00:27:37.000 Characterization campaign, and these were mip hpt points. 00:27:37.000 --> 00:27:59.000 Here also, you know. So we use this to track progress in the field, so as the because the field teams were equipped with webmap linked tablets, they were able to update a sampling plan from status of incomplete complete complete complete as they completed sampling at 00:27:59.000 --> 00:28:05.000 these individual points, they're able to upload you know, field photos to these points. 00:28:05.000 --> 00:28:15.000 And the cool thing about all that is that you have all this data coming in, and you would be looking at it in the context of your existing site. 00:28:15.000 --> 00:28:27.000 Data. Pretty exciting tool, the, you know, if I typed in here, this is kind of the utility for some of that. 00:28:27.000 --> 00:28:41.000 9, 1, 1, 87. You know an example of some of these using these with high-risk characterization data that comes in. 00:28:41.000 --> 00:28:45.000 Let's do another one. They were. 00:28:45.000 --> 00:28:53.000 It's useful for making on the fly. 00:28:53.000 --> 00:28:59.000 Bluebine. Load line one. 00:28:59.000 --> 00:29:03.000 On the fly decisions based on the data that's coming in the door. 00:29:03.000 --> 00:29:10.000 Here. You can toggle these on. See where they're located on the map. 00:29:10.000 --> 00:29:15.000 If I stretch this out a little bit. 00:29:15.000 --> 00:29:23.000 If we look at. So here we can display Ec curves for these 3 wells. 00:29:23.000 --> 00:29:46.000 Look at the hpt pressure, etc., and then relate that to, you know, Xsd results, and so on, and start to help guide real-time decisions using the web application and you know the cross-sections, etc., that are here at your fingertips to help you know the field team decide where to 00:29:46.000 --> 00:29:52.000 go next with their sampling aside, so. 00:29:52.000 --> 00:29:56.000 Let me go back to. 00:29:56.000 --> 00:30:04.000 The presentation here when you go, and you're looking at your. 00:30:04.000 --> 00:30:08.000 When you're looking at your electronic slide deck. 00:30:08.000 --> 00:30:12.000 If I start from this slide. 00:30:12.000 --> 00:30:14.000 This is the this is the link to that web application, demo. 00:30:14.000 --> 00:30:21.000 This is a publicly-facing demo that you can access. 00:30:21.000 --> 00:30:22.000 It's a you kind of have to acknowledge when you click on it. 00:30:22.000 --> 00:30:29.000 That it's a fictitious site, and and then go from there. 00:30:29.000 --> 00:30:34.000 So just a couple words about the use of the or the design, or the how this thing comes about right? 00:30:34.000 --> 00:30:47.000 So this is a sort of farmed table analogy, for you know everybody likes the idea of a technology like this, but it takes some discipline in the background, right? 00:30:47.000 --> 00:31:09.000 And the and the heavy lifting associated with this, particularly with respect to a legacy site, is in wrestling with your getting your arms around all your legacy data and getting all of that into a standardized database structure or data schema and this is where air force programs like the erpms 00:31:09.000 --> 00:31:26.000 program really give them a leg up. Nyrus, with the Navy is close behind on that Fudgcam is good for some of the analytical data, but those efforts that have kind of been stewing now for some time in the background as as a necessary evil as some of us geologists might perceive 00:31:26.000 --> 00:31:31.000 it are really what are going to allow us to really start integrating stuff quickly, right? 00:31:31.000 --> 00:31:37.000 And if you have a new project, the key thing is just to get religion about that right off the bat. 00:31:36.000 --> 00:31:44.000 Colin, one as the name for their monitoring wells. 00:31:44.000 --> 00:31:50.000 Stick on your labs for using the standard Edd type, deliverables, etc. 00:31:50.000 --> 00:31:50.000 So the idea is that you take your raw project data. 00:31:50.000 --> 00:32:12.000 You do some data governance and data management to get it into a database or sort of this marketplace structure, you may have some specialized software like we like to use leapfrog or rockware to create our cross sections and manage lithologic data and geophysical data and 00:32:12.000 --> 00:32:19.000 it might access that database back and forth the whole key to this is that it's served up through Asri Arcm. 00:32:19.000 --> 00:32:25.000 Right. So this is all. All your data has to come through some sort of hub and Ezri is about as ubiquitous a software package as we have in our industry. 00:32:25.000 --> 00:32:42.000 You if you don't have it. A client, a consultant, that you have access to does, I mean, it's nearly as available as something like Omega Microsoft word in our world. 00:32:42.000 --> 00:32:47.000 So data is accessed and displayed in our jazz pro. 00:32:47.000 --> 00:33:00.000 And that's really where the leg work is done, and then it's pushed out with some Fme technology and other data massaging pushed out to Artgis online and fed to a web application based. 00:33:00.000 --> 00:33:00.000 Csm that's created in that web. Application or experience. 00:33:00.000 --> 00:33:14.000 Builder, and there's a range of other potential software types you could use to to do this. 00:33:14.000 --> 00:33:29.000 What we have found to be the most flexible to date has been the web experience builder with with Esri's tools, as far as the data deliverable goes, associated with this, you know, so right now, we're this is where we're kind of a little bit in the wild West. 00:33:29.000 --> 00:33:37.000 Right for private clients. It's far easier than it is with Department of Defense. 00:33:37.000 --> 00:33:43.000 Because we don't we're not dealing with quite the level of data security and sort of firewall issues. 00:33:43.000 --> 00:34:05.000 But at the very least you can get your data structure together, get everything put together, get Frankenstein built on your end, get all that coding together, and then, when it comes time to deliver, provide the pieces and step away right I'm not going to or you all with 00:34:05.000 --> 00:34:15.000 too many flow charts here, at the end of a long day, I get you all worked up with data visualization only to cool you down with flowcharts. 00:34:15.000 --> 00:34:26.000 But this is currently kind of a visualization. This is where you also have to be brave enough to start dealing with data governance types who love this kind of thing. 00:34:26.000 --> 00:34:34.000 But the it's kind of a visualization of how this works for us right now is within, within, with a lot of our clients. 00:34:34.000 --> 00:34:41.000 We're hosting and creating the Rjis group and developing the web app. 00:34:41.000 --> 00:34:49.000 Here creating a viewer only web application, and then inviting users to this, and preferably the clients already have an Agl account right? 00:34:49.000 --> 00:34:54.000 And then there's no cost to them to access this they don't have an agl account. You can. 00:34:54.000 --> 00:34:59.000 They can be provided one at a rate of $150 a year for access. Right? 00:34:59.000 --> 00:35:09.000 So it's pretty minimal. Given that there are other boutique solutions out there that are, you know, twelvek a year, for, you know, solution, or whatever. 00:35:09.000 --> 00:35:20.000 So there is a data hosting fee. If you're purchasing shared organizational space on Agol, and there's a licensing fee if you don't have access to Esri tools yourself right? 00:35:20.000 --> 00:35:28.000 So it's at least a a technology fee with the consultant or a $600 data hosting fee on Agol, and then $100. 00:35:28.000 --> 00:35:30.000 It's at least $700 a year for 1 one user outside of your project team. 00:35:30.000 --> 00:35:41.000 To, or it can be made available to you just for the project duration under a technical service fee and etc., with the Dod. 00:35:41.000 --> 00:35:45.000 This is kind of currently like I was saying, this is kind of currently how it goes. 00:35:45.000 --> 00:36:00.000 We develop it here on our end, and then, when it comes time to hand off, there has to be sort of a one-time data and coding share where this goes up and over the firewall to the to the Geo base team or Afghans team and they put it back together, on their end, or you know 00:36:00.000 --> 00:36:05.000 dealing with the Nyrus folks on their Js contractors, etc. 00:36:05.000 --> 00:36:19.000 Something that we've developed internally and as we've seen it as like a real viable future for Csms, we've put it out there for Csm delivery and now it's time to, you know, work out the handoffs. 00:36:19.000 --> 00:36:23.000 And so on, right. The idea isn't that we've inserted ourselves as a consultant in here forever to maintain or serve your data. 00:36:23.000 --> 00:36:28.000 No one. None of us wants to be a software developer or data server. 00:36:28.000 --> 00:36:34.000 We want to provide a viable platform for Csm Development. 00:36:34.000 --> 00:36:40.000 And this is something all of us can be chasing after. 00:36:40.000 --> 00:36:45.000 So some other options here you can look at in the in the slide deck. 00:36:45.000 --> 00:37:09.000 But basically it's all kind of hinges around where the project data resides, where the web application is placed for perpetuity, and whether or not the client has has every licenses to begin with, or not and so again, it's just sort of moving that project location around 00:37:09.000 --> 00:37:23.000 here, etc. So I think I'm pretty close to the end of my time again, so I hope you saw that this is, you know, it's using technology. 00:37:23.000 --> 00:37:28.000 That's quote unquote, freely available to all of us. Right? 00:37:28.000 --> 00:37:28.000 We're all using Ezri technologies. We're all familiar with these dashboard approaches. 00:37:28.000 --> 00:37:38.000 If you're going to national Geologic Map database for the Usgs, you're accessing a web app. 00:37:38.000 --> 00:37:44.000 If you're going to Michigan's, deqeues, Geo. Webface, you're accessing a web app. 00:37:44.000 --> 00:37:51.000 These are all using this same technology. And so it's time to start incorporating it into our workflows and giving our team all their materials. 00:37:51.000 --> 00:37:56.000 In one place, and I think, really the sky is the limit. 00:37:56.000 --> 00:38:08.000 With these development is open-ended. There's, you know, you're seeing newer and newer stuff all the time with it. 00:38:08.000 --> 00:38:16.000 So thank you. What's that? 00:38:16.000 --> 00:38:19.000 All right. Any questions in the room. 00:38:19.000 --> 00:38:24.000 Because I have questions online. 00:38:24.000 --> 00:38:28.000 Alright! Kyle, I'll lead in with some of the ones that are here online. 00:38:28.000 --> 00:38:28.000 Someone wanted to talk about managing these from a record-keeping perspective. 00:38:28.000 --> 00:38:40.000 They note that they need to keep files stored in a special system for legal purposes. 00:38:40.000 --> 00:38:44.000 And it's unclear how such a dynamic web page would be saved. 00:38:44.000 --> 00:38:54.000 So, yeah, so if they're if they are saving the materials, we document everything in our own file structure. To begin with, right? 00:38:54.000 --> 00:38:57.000 So it is still elements of the static Pdm. 00:38:57.000 --> 00:39:01.000 Of the static Pdf type report that is saved and available, and or data tables that are saved and available. 00:39:01.000 --> 00:39:06.000 But it's not a 1 million excel files. 00:39:06.000 --> 00:39:11.000 It's a single singular equis or access database. 00:39:11.000 --> 00:39:18.000 It's a rigorous file structure where you're putting all of your visual files cross-sections, etc. 00:39:18.000 --> 00:39:24.000 So you're archiving all of that material. And then accessing it with the tool. 00:39:24.000 --> 00:39:33.000 So you could have a file structure that reflects your need for archival history and have the tool be accessing those elements. 00:39:33.000 --> 00:39:44.000 Ok. One of the attendees wanted to confirm. Would all data entered into the web interface need to be in an access or equis friendly format? 00:39:44.000 --> 00:39:48.000 How would Boris log data be entered? So that it's in a format that could be queried in. 00:39:48.000 --> 00:39:54.000 Joined. Yeah. So the answer is, it doesn't have to be. 00:39:54.000 --> 00:39:57.000 You can slam these together with a 1 million different excel formats. 00:39:57.000 --> 00:40:05.000 But that's highly unrecommended, because it's a lot of work so you want to get it into one access or one equis data structure, it's up to you to kind of decide on your data schema. 00:40:05.000 --> 00:40:27.000 And there are some out there templates out there that you can use, and then lithology data is that's partly why things like the Uscs code, I think, came into use was that it gave an easy way to capture lithologic information but we'd like to move past that 00:40:27.000 --> 00:40:39.000 to things like our graphic green size. Log coding where we're capturing more than just silts, silt clay, etc. 00:40:39.000 --> 00:40:43.000 Capturing visual estimates of percentages, things like that. 00:40:43.000 --> 00:40:51.000 And that actually is also a big motivator behind some collaborative work we're doing with Jesse Meyer and a sort of Estp. 00:40:51.000 --> 00:41:09.000 And Estcp program here this year, where we're talking about graphical logging schemes and the whole goal on that is to move past paragraphs that are hard to archive in databases and move to alpha-numeric sort of AR archiving of that information 00:41:09.000 --> 00:41:17.000 next. Excellent. I see a question in the room, Jim, go ahead. 00:41:17.000 --> 00:41:20.000 Jim, could you turn the mic on? Thank you. Alright. 00:41:20.000 --> 00:41:24.000 Let! 00:41:24.000 --> 00:41:31.000 We will get you a microphone, sir. There we go. 00:41:31.000 --> 00:41:37.000 Bye, I still have a microphone. I always have a microphone. 00:41:37.000 --> 00:41:42.000 Can't let you go like this. Come on, let's get that question in. 00:41:42.000 --> 00:41:50.000 So when you got a whole team of people, can they upload information to this thing all independently? 00:41:50.000 --> 00:42:01.000 Or is it a practical question? Do they have to submit the data to a central repository where someone would perform some quality control checks? 00:42:01.000 --> 00:42:10.000 And also, if you've got a team out in the field, do you have a, for example, a minimum time frame that they're required to update? 00:42:07.000 --> 00:42:20.000 So how do you, as a practical matter? How do you input data so you can have a dynamic? Csm, yeah. 00:42:20.000 --> 00:42:27.000 So so we're exiting the Wild West, where everyone on your team who could get anything on to Agl could update the map. 00:42:27.000 --> 00:42:44.000 And that's the bad and the good of it. We're entering the world of data governance personally, at Berns and Mac. Right now we're experiencing it where we're implementing a lot of stards on making sure everything that goes into Agol has the same data schema and all that and 00:42:44.000 --> 00:42:53.000 it's incredibly cumbersome at the moment to do that, but I think by going through that phase you will ensure higher data quality and so on. 00:42:53.000 --> 00:42:57.000 And so the idea isn't to have a singular staff member. 00:42:56.000 --> 00:43:08.000 But it will be it will. That gateway will narrow to a core group that has to be responsive on that. 00:43:08.000 --> 00:43:31.000 So yes, and but I think that's ultimately a good idea, for from a quality standpoint, and then with project teams, if your team is equipped with field data collector, which is a Gis component that can be or application that can be placed on their tablets, they can be updating points, and you 00:43:31.000 --> 00:43:40.000 will see those changes if that map is fed to your Agl space, you'll see that instantly on the web application map, because it's accesses that same data. 00:43:40.000 --> 00:43:46.000 So that's like 0 timeframe. And they can be connecting photos to those points, etc. 00:43:46.000 --> 00:43:53.000 From uploading of things like those Ec. Hbt curves that's usually an overnight process. 00:43:53.000 --> 00:44:10.000 At this point, because how we've done that is just we put a link to a sharepoint at the top of the web application, and every morning we had someone looking at what Dakota had uploaded to the sharepoint, and then they were you know, our person was then taking that tabular data and 00:44:10.000 --> 00:44:13.000 uploading it into the into the database that the widget was accessing. 00:44:13.000 --> 00:44:19.000 So so 24 h turnaround kind of thing, you know. 00:44:19.000 --> 00:44:25.000 You have to have your ducks in a row for that kind of data. 00:44:25.000 --> 00:44:25.000 All right. I just wanted you to know lots of people online for playing along with the demo maps. 00:44:25.000 --> 00:44:37.000 And we're very excited. Oh, cool. Good. Yeah. Any other questions in the room? 00:44:37.000 --> 00:44:42.000 Oh, there we go! 00:44:42.000 --> 00:44:58.000 Okay. I'm not sure if this is only a question for you, Colin, or everyone that's been in the back of my mind, because my navy command is very interested in how we can use artificial intelligence in the future, and with all of this data that's been presented. 00:44:58.000 --> 00:45:00.000 Today, I and my very limited understanding about AI, I I mean, really, I'm a ground 0. 00:45:00.000 --> 00:45:13.000 But I do think it's staged of it is the modeling. 00:45:13.000 --> 00:45:15.000 Go! Ahead! What? What could be the future? 00:45:15.000 --> 00:45:23.000 With AI, yeah, I am. I am not an AI. I have no real. 00:45:23.000 --> 00:45:30.000 I'd open that up to the floor struggle with AI, because, as I've yet to find our eye, you know, real intelligence. 00:45:30.000 --> 00:45:36.000 But yeah. 00:45:36.000 --> 00:45:41.000 Any response? 00:45:41.000 --> 00:45:56.000 My question regarding using new technology for digital twins. And if you can combine digital twins, I understand you tell when you could use 3D, but still you are developing 3D. 00:45:56.000 --> 00:46:05.000 So the question or do you have any plans to consider, adding these 12 points to developing of the conceptual conceptual side model? 00:46:05.000 --> 00:46:14.000 Or you are already applying that. Thank you. So so currently, as far as like data streaming and so on. 00:46:14.000 --> 00:46:17.000 Just an example of that kind of thing, you know. 00:46:17.000 --> 00:46:23.000 There's a little. This is actually sort of the fun part of this map is the, you know. 00:46:23.000 --> 00:46:31.000 So here's an example of a of a webcam that's hooked up and is streaming streaming data to the. 00:46:31.000 --> 00:46:34.000 To this, so you can go to the aisle of before. 00:46:34.000 --> 00:46:44.000 -oh, and see it, but you know anything that can be served up through a web-based like data, logger, or whatever could be streamed. 00:46:44.000 --> 00:46:54.000 These things far as the 3D. Goes, we've yet to really push through that I mean, I think there's some options with our Arcene and others. 00:46:54.000 --> 00:46:55.000 Currently we use Evs and leapfrog for our visualizations, and the best we can do is kind of like. 00:46:55.000 --> 00:47:04.000 Add a tab to these, so you can access the threed visualization with it. 00:47:04.000 --> 00:47:07.000 But it's not truly interactive with the web app, but it will. 00:47:07.000 --> 00:47:18.000 It will get there. And in other applications like in on the engineering side, where some of these tools have been developed in, are further along than on our side. 00:47:18.000 --> 00:47:29.000 You know, they typically link. They can link map points to sort of preset fl throughs of Arcene, you know, 3 dimensional depictions, and so on. 00:47:29.000 --> 00:47:34.000 So still early times. But yeah. 00:47:34.000 --> 00:47:42.000 Yeah, mark. 00:47:42.000 --> 00:47:48.000 No, it is not a real place. This is. This is a webcam that's hooked up to Hawaii. 00:47:48.000 --> 00:47:51.000 So we're we're. This is what is it? 00:47:51.000 --> 00:48:01.000 All this is a oh, yes, just an example of how you can stream data off the web. 00:48:01.000 --> 00:48:05.000 Alright. We got another question. 00:48:05.000 --> 00:48:12.000 The only thing I would say with regard to AI is that it's going to be the same garbage in garbage out. 00:48:12.000 --> 00:48:19.000 So what's going in on the front end, you know, is super important. 00:48:19.000 --> 00:48:26.000 Be diligent about your database management, because turn it loose on, you know, on poor data. 00:48:26.000 --> 00:48:38.000 Then you're gonna get a more resolved.