WEBVTT 00:00.189 --> 00:03.990 Welcome . This is the 2nd of our 4-part 00:03.990 --> 00:07.170 SDSFIE and UAce webinar series . 00:07.980 --> 00:09.980 This presentation is focused on the 00:09.980 --> 00:12.659 UAce Enterprise Geospatial Information 00:12.659 --> 00:15.939 and Services , or EGINS program and 00:15.939 --> 00:19.629 strategy . This 00:19.629 --> 00:21.740 training resource is designed for the 00:21.740 --> 00:25.399 UAce geospatial community . We have 00:25.399 --> 00:27.566 produced a suite of training resources 00:27.566 --> 00:30.100 on SDSFIE and its implementation . 00:31.180 --> 00:33.720 These resources , which to date include 00:33.720 --> 00:37.180 19 videos and several recorded webinars , 00:37.340 --> 00:39.459 are aimed at the broader IGINS 00:39.459 --> 00:43.139 community . To create this presentation , 00:43.580 --> 00:46.259 content was curated from the SDSFIE use 00:46.259 --> 00:49.619 and governance video . For users 00:49.619 --> 00:51.900 wanting more context or greater depth , 00:52.060 --> 00:53.939 we can recommend that video as a 00:53.939 --> 00:56.380 prerequisite or follow-up to reinforce 00:56.380 --> 00:58.840 the concepts presented in this video . 01:00.310 --> 01:03.069 In addition , the first overview video 01:03.069 --> 01:06.750 in this four-part SDSFIE and UA series 01:06.750 --> 01:08.972 should be viewed prior to watching this 01:08.972 --> 01:11.739 video . All of these videos are 01:11.739 --> 01:13.906 accessible from the support section of 01:13.906 --> 01:16.360 the SDSFIE portal at the URL shown . 01:18.489 --> 01:20.500 The overall goal for this training 01:20.500 --> 01:22.389 resource is for you to understand 01:22.389 --> 01:25.940 SDSFIE and particularly the vector or V 01:25.940 --> 01:28.019 standard , which when implemented in 01:28.019 --> 01:30.879 conjunction with USA geospatial policy , 01:30.980 --> 01:33.099 is the best way to meet requirements 01:33.099 --> 01:35.540 and provide value to your project and 01:35.540 --> 01:37.900 move us towards enterprise level goals . 01:39.110 --> 01:41.166 The specific objectives are that the 01:41.166 --> 01:43.332 audience gains an understanding of the 01:43.332 --> 01:46.309 following . How the SDSFIE family of 01:46.309 --> 01:48.750 standards helps improve geospatial data 01:48.750 --> 01:51.099 and services for your project and the 01:51.099 --> 01:53.910 USA enterprise . What the 01:53.910 --> 01:56.889 UAEGINS program and strategy is . 01:57.879 --> 02:00.046 And what the relationships are between 02:00.046 --> 02:03.349 SDSFIE and UAC EGINS strategy , 02:03.599 --> 02:05.500 policy and implementation . 02:08.250 --> 02:10.779 UAS has directly developed , managed , 02:11.100 --> 02:13.509 supported , and implemented SDSFIE 02:13.509 --> 02:15.842 throughout the history of the standards , 02:15.842 --> 02:18.619 which to date exceeds 33 years . 02:20.059 --> 02:23.289 For its 1st 21 years , SDSFIE was just 02:23.289 --> 02:25.779 a vector GIS data model with 02:25.779 --> 02:28.779 development starting in 1993 by USA 02:28.779 --> 02:30.723 staff in Vicksburg , Mississippi , 02:31.020 --> 02:33.179 using military installation and civil 02:33.179 --> 02:36.929 works requirements . In 1999 , the 02:36.929 --> 02:39.669 standard was rebranded as SDSFIE . 02:40.690 --> 02:42.970 It remained in Usace management and 02:42.970 --> 02:45.210 with UAce development support , and in 02:45.210 --> 02:48.369 2006 was relocated to the UAC's 02:48.369 --> 02:51.630 Topographic Engineering Center , or TEC 02:51.630 --> 02:55.300 in Alexandria . From 2001 to 02:55.300 --> 02:58.660 2010 , all components and UAce itself 02:58.660 --> 03:01.479 were using the SDSFIE version two model . 03:02.309 --> 03:05.449 In 2011 , the more streamlined version 03:05.449 --> 03:08.860 3 model was published . Usace was an 03:08.860 --> 03:10.839 early adopter , using the new 03:10.839 --> 03:12.929 adaptation approach to creating a 03:12.929 --> 03:15.660 customized 3.0 model that better 03:15.660 --> 03:17.771 supported Usace requirements than the 03:17.771 --> 03:20.979 shared gold 3.0 model . In 03:20.979 --> 03:24.399 2014 , SDSFIE added the quality , 03:24.619 --> 03:27.220 metadata , and raster standards to the 03:27.220 --> 03:29.820 existing single vector standard , thus 03:29.820 --> 03:32.419 encompassing a family of interrelated 03:32.419 --> 03:36.320 standards . In 2022 , the 03:36.320 --> 03:40.139 AR 525-95 formalizes 03:40.139 --> 03:43.770 Uace's historic SDSFIE support role to 03:43.770 --> 03:45.326 provide technical support , 03:45.326 --> 03:47.589 configuration management , and general 03:47.589 --> 03:50.429 support to implement IGINS standards as 03:50.429 --> 03:52.630 a function supporting the IGINS 03:52.630 --> 03:54.960 governance group in accordance with DD 03:54.960 --> 03:58.820 8130.01 . At the end of 03:58.820 --> 04:02.179 2024 , the IG chair approved the most 04:02.179 --> 04:06.160 recent Uace adaptation , version 4.0.6 . 04:07.039 --> 04:10.050 Through 2025 , the standardization of 04:10.050 --> 04:13.649 GIS data to SDSFIE within UAce is 04:13.649 --> 04:15.949 limited to that of its enterprise level 04:15.949 --> 04:18.089 programs , such as National Levy 04:18.089 --> 04:21.089 Database , E-Hydro , and Remus . 04:22.088 --> 04:23.921 Looking towards the future , the 04:23.921 --> 04:26.699 implementation action from the EGINS 04:26.699 --> 04:28.643 program will increase the level of 04:28.643 --> 04:30.868 SDSFIE standardization throughout UA . 04:33.730 --> 04:36.570 The definition of the SDSFIE family of 04:36.570 --> 04:38.126 standards and the roles and 04:38.126 --> 04:40.890 responsibilities of the DOW components 04:40.890 --> 04:44.000 as presented in the 2014 SDSFIE 04:44.000 --> 04:46.290 governance plan were clarified and 04:46.290 --> 04:49.130 given weight by the 2015 publication of 04:49.130 --> 04:51.241 the Department of Defense instruction 04:51.241 --> 04:54.730 8130.01 entitled Installation 04:54.730 --> 04:57.170 Geospatial Information and Services . 04:58.290 --> 05:01.209 The IGINS Ddi mandated the use and 05:01.209 --> 05:04.010 management of the SDSFIE standards by 05:04.010 --> 05:06.730 DOW components by providing governance 05:06.730 --> 05:09.450 procedures , establishing policy , and 05:09.450 --> 05:11.440 assigning responsibilities to the 05:11.440 --> 05:13.450 components and other SDSFIE 05:13.450 --> 05:16.880 stakeholders . The Dodi is 05:16.880 --> 05:19.160 relevant to usa for two additional 05:19.160 --> 05:21.104 reasons that I want to highlight . 05:21.859 --> 05:24.299 First , it establishes the IGINS 05:24.299 --> 05:27.540 governance group , or IG , in which UAS 05:27.540 --> 05:29.207 participates equally with the 05:29.207 --> 05:32.970 components . Second , it specifies 05:32.970 --> 05:35.390 that Big Army ensures the UA 05:35.390 --> 05:37.230 requirements are met and fully 05:37.230 --> 05:40.100 represented in the egg . AR 05:40.100 --> 05:43.899 115-13 is also noteworthy as it 05:43.899 --> 05:45.899 calls out the mandate for using the 05:45.899 --> 05:49.600 SDSFIE family of standards . ER 05:49.600 --> 05:53.559 1110-1-8156 05:53.559 --> 05:56.239 restates this mandate , specifying both 05:56.239 --> 06:00.119 vector data and metadata . EGINS is 06:00.119 --> 06:02.239 aligned to these three key policy 06:02.239 --> 06:05.000 documents and to the Engineer Manual on 06:05.000 --> 06:07.839 geospatial Data and Systems , EM 06:07.839 --> 06:11.760 1110-1-2909 , as 06:11.760 --> 06:14.750 well . The 06:14.750 --> 06:17.510 EGINS program has been mentioned twice 06:17.510 --> 06:21.429 now , but what is it exactly ? It is 06:21.429 --> 06:24.850 first described in detail in the 2024 06:24.850 --> 06:28.269 to 2029 strategy document that lays out 06:28.269 --> 06:31.309 the framework and vision for the EGINS 06:31.309 --> 06:33.820 program . The vision statement 06:33.820 --> 06:36.859 emphasizes quality geospatial products 06:36.859 --> 06:39.081 supporting all pertinent aspects of the 06:39.081 --> 06:42.190 enterprise . As shown on the previous 06:42.190 --> 06:45.570 slide , the EGINS strategy ensures that 06:45.570 --> 06:48.390 UAC geospatial policies are aligned to 06:48.390 --> 06:50.589 those of the Department of War , US 06:50.589 --> 06:53.619 Army , and USAce policies , as well as 06:53.619 --> 06:56.339 other federal policies such as OMB 06:56.339 --> 06:59.500 Circular A-16 and the Geospatial Data 06:59.500 --> 07:01.989 Act , and UAce policies such as the 07:01.989 --> 07:05.869 2025 data strategy . In doing 07:05.869 --> 07:07.730 so , the strategy is careful to 07:07.730 --> 07:10.609 prioritize UA's program and project 07:10.609 --> 07:13.859 delivery . Again , this program is 07:13.859 --> 07:16.019 designed to add value to both your 07:16.019 --> 07:19.089 project and our shared enterprise . The 07:19.089 --> 07:21.170 document moves forward the goals and 07:21.170 --> 07:23.250 objectives of the UAC engineering 07:23.250 --> 07:25.609 report and manual previously mentioned 07:25.609 --> 07:27.839 by laying out the ends , ways , 07:28.010 --> 07:30.450 enablers , and resources that are 07:30.450 --> 07:32.950 required to achieve the EGINS program 07:32.950 --> 07:36.440 vision . As with any good strategy , it 07:36.440 --> 07:38.649 also enumerates and analyzes the 07:38.649 --> 07:41.250 challenges , risks , and opportunity 07:41.250 --> 07:44.859 for program success . As expressed in 07:44.859 --> 07:46.970 the program vision , which is enabled 07:46.970 --> 07:48.803 by following and fulfilling this 07:48.803 --> 07:51.820 strategy , EGINS is broadly applicable 07:51.820 --> 07:53.380 across the enterprise , and 07:53.380 --> 07:55.380 specifically so to those functional 07:55.380 --> 07:57.260 areas that involve geospatial 07:57.260 --> 08:00.690 technologies and services . Soon we'll 08:00.690 --> 08:02.634 look at a list of those functional 08:02.634 --> 08:05.589 areas for which the standard has 08:05.589 --> 08:09.510 already been developed . This is 08:09.510 --> 08:12.179 the 1st of 3 slides that show the close 08:12.179 --> 08:15.690 relationship between EGINS and SDSFIE . 08:16.619 --> 08:19.380 This slide focuses on how the SDSFIE 08:19.380 --> 08:21.779 capabilities can be leveraged to meet a 08:21.779 --> 08:23.779 substantial set of the strategy's 08:23.779 --> 08:27.549 objectives and fulfill its goals . Goal 08:27.549 --> 08:30.149 one is all about making UAce geospatial 08:30.149 --> 08:32.539 data an enterprise asset and ensuring 08:32.539 --> 08:34.706 that it meets the Volttis principles . 08:35.400 --> 08:38.359 Objective A focuses on interoperability 08:38.359 --> 08:40.440 through data standards and a unified 08:40.440 --> 08:43.190 framework . This is where the SDSFIE 08:43.190 --> 08:45.479 family of standards really shines . 08:46.619 --> 08:49.580 SDSFIE gives us a common consistent 08:49.580 --> 08:51.413 structure that covers the entire 08:51.413 --> 08:54.049 geospatial data life cycle . Because 08:54.559 --> 08:56.615 the standards are unified across the 08:56.615 --> 08:58.726 enterprise , they let us connect data 08:58.726 --> 09:02.369 sets and systems more easily . In short , 09:02.570 --> 09:05.010 STSFIE is a fundamental part of what 09:05.010 --> 09:07.229 makes true interoperability possible . 09:08.049 --> 09:10.090 Objective B is to be able to use 09:10.090 --> 09:12.409 geospatial resources across all 09:12.409 --> 09:14.353 business lines and mission areas . 09:15.559 --> 09:17.900 SDSFIE is built through consensus , 09:18.200 --> 09:20.033 which means every mission area , 09:20.320 --> 09:22.487 including all the diverse areas inside 09:22.487 --> 09:26.239 UA , has a voice in the model . That 09:26.239 --> 09:28.350 makes the standard flexible enough to 09:28.350 --> 09:30.295 support everyone's needs but still 09:30.295 --> 09:32.350 consistent at the enterprise level . 09:32.849 --> 09:35.250 The data is then built to work across 09:35.250 --> 09:37.250 programs , not just within one . 09:38.179 --> 09:40.659 Objective C is about delivering quality 09:40.659 --> 09:43.369 geospatial products to enable programs . 09:43.780 --> 09:45.891 Here , the different standards of the 09:45.891 --> 09:48.500 SDSFIE family come together , as we saw 09:48.500 --> 09:50.500 in the slide with the image of Fort 09:50.500 --> 09:52.760 Buchanan in the video 1 overview . 09:53.780 --> 09:56.780 SDSFIER provides guidance and best 09:56.780 --> 09:58.780 practices for acquiring and using 09:58.780 --> 10:01.080 raster data , which can in turn be used 10:01.080 --> 10:04.820 in the production of vector data . SDSF 10:04.820 --> 10:07.380 IEV standards give us the consistent 10:07.380 --> 10:09.602 structures for the geometry and feature 10:09.602 --> 10:12.929 data tables . SDSFIEQ , 10:13.479 --> 10:15.535 including the feature class specific 10:15.535 --> 10:18.219 data content specifications or DCS , 10:18.559 --> 10:20.349 provide details on the creation 10:20.349 --> 10:22.489 specifications , structure of the 10:22.489 --> 10:24.656 content , and metrics and processes to 10:24.656 --> 10:26.711 measure and report on data quality . 10:27.679 --> 10:31.039 SDSFIEM ensures metadata captures the 10:31.039 --> 10:33.659 details needed to understand , trust , 10:33.760 --> 10:37.080 and reuse the data . Together , the 10:37.080 --> 10:39.799 SDSFIE standards make sure our data is 10:39.799 --> 10:41.919 reliable , well documented , and 10:41.919 --> 10:45.200 mission ready . And then when we talk 10:45.200 --> 10:47.359 about the broader target of making UA 10:47.359 --> 10:50.919 data Voltis , SDSFIE aligns directly to 10:50.919 --> 10:54.260 that DOW requirement . The standards 10:54.260 --> 10:56.371 are intentionally designed to support 10:56.371 --> 10:58.859 the Volttis principles , so SDSFIE 10:58.859 --> 11:00.803 becomes the backbone of enterprise 11:00.803 --> 11:03.640 quality data . Although the closest 11:03.640 --> 11:05.751 alignment is for goal number 1 of the 11:05.751 --> 11:07.973 strategy , as evident by the portion of 11:07.973 --> 11:10.520 the table dedicated to it , SDSFIE 11:10.520 --> 11:12.187 supports the other 4 goals in 11:12.187 --> 11:15.280 meaningful ways . Goal 2 is for a 11:15.280 --> 11:18.119 geospatial IT architecture and the 11:18.119 --> 11:20.008 processes to deliver systems that 11:20.008 --> 11:22.230 readily connect all stakeholders to the 11:22.230 --> 11:24.400 data and applications required to meet 11:24.400 --> 11:27.440 the mission objectives . One important 11:27.440 --> 11:29.218 component of these systems is a 11:29.218 --> 11:32.659 geospatial data catalog . This is 11:32.659 --> 11:34.826 exactly the type of key infrastructure 11:34.826 --> 11:37.780 element for which the SDSFIEV Q and M 11:37.780 --> 11:41.479 standards were designed . Goal 3 is to 11:41.479 --> 11:43.840 establish a leadership level culture of 11:43.840 --> 11:46.840 support for the UAC EGINS program by 11:46.840 --> 11:49.159 proactively demonstrating a positive 11:49.159 --> 11:51.080 return on investment and enhanced 11:51.080 --> 11:52.858 capabilities in meeting mission 11:52.858 --> 11:56.330 requirements . Goal 4 is to cultivate a 11:56.330 --> 11:58.609 technically exceptional , connected , 11:59.210 --> 12:00.932 situationally aware geospatial 12:00.932 --> 12:04.299 workforce and organization . And goal 5 12:04.299 --> 12:06.099 is to prioritize consolidated 12:06.099 --> 12:08.650 geospatial capabilities at UA's 12:08.650 --> 12:10.706 districts through a standardized ENC 12:10.706 --> 12:12.780 division-driven organizational 12:12.780 --> 12:14.700 structure and promote geospatial 12:14.700 --> 12:17.679 centers of expertise . The common 12:17.679 --> 12:19.846 objective of these goals is to promote 12:19.846 --> 12:22.559 uptake of policy guidance , standards , 12:23.080 --> 12:24.960 processes , and best practices . 12:26.500 --> 12:28.940 SDSFIE supports these by providing 12:28.940 --> 12:31.330 extensive documentation , training 12:31.330 --> 12:32.997 materials , and collaboration 12:32.997 --> 12:36.400 opportunities . So as leaders promote 12:36.400 --> 12:38.640 geospatial alignment and as the 12:38.640 --> 12:41.719 workforce grows in capability , SDSFIE 12:41.719 --> 12:43.608 is a core component of the common 12:43.608 --> 12:45.663 foundation that everyone can learn , 12:45.799 --> 12:49.429 use , and rely on . It makes the EGINS 12:49.429 --> 12:52.750 strategy achievable . It aligns our 12:52.750 --> 12:55.270 data , connects our mission areas , and 12:55.270 --> 12:57.729 sets us up for enterprise level success . 13:00.349 --> 13:02.405 On this slide , we're looking at how 13:02.405 --> 13:05.030 SDSFIE directly supports each of the 13:05.030 --> 13:07.609 EGINS goal one opportunities . 13:08.929 --> 13:11.289 And as we saw in the previous slide , 13:11.489 --> 13:13.267 while all of the objectives and 13:13.267 --> 13:15.729 opportunities are important , SDSFIE 13:15.729 --> 13:18.489 most clearly addresses , supports , and 13:18.489 --> 13:20.489 in several cases is crucial in 13:20.489 --> 13:22.650 realizing those of goal 1 . 13:24.169 --> 13:26.280 First , when we talk about developing 13:26.280 --> 13:28.002 life cycle data production and 13:28.002 --> 13:30.500 management guidance , the STSFIE family 13:30.500 --> 13:32.840 of standards covers every phase of the 13:32.840 --> 13:35.770 geospatial data life cycle , so Uace 13:35.770 --> 13:37.826 doesn't have to invent that guidance 13:37.826 --> 13:41.299 from scratch . Next , for creating 13:41.299 --> 13:43.159 usa-specific data content 13:43.159 --> 13:46.520 specifications , SDSFIEQ and the IgG 13:46.520 --> 13:49.080 level DCS guidance give us a solid 13:49.080 --> 13:52.080 foundation , templates , rules , and 13:52.080 --> 13:54.359 examples that we can adapt for our own 13:54.359 --> 13:58.270 mission needs . For institutionalizing 13:58.270 --> 14:01.750 quality metadata , SDSFIEM delivers the 14:01.750 --> 14:03.989 standards and tools that make metadata 14:03.989 --> 14:07.150 consistent across the enterprise . This 14:07.150 --> 14:08.817 is what allows our data to be 14:08.817 --> 14:12.039 discoverable and trusted . When it 14:12.039 --> 14:14.270 comes to prioritizing investment in 14:14.270 --> 14:18.179 quality data , SDSFIER , VQ , 14:18.320 --> 14:21.109 and M give us a framework to assess , 14:21.320 --> 14:23.659 document , and track data quality . 14:24.419 --> 14:26.669 That makes it easier to justify where 14:26.669 --> 14:28.940 data improvements are needed and why it 14:28.940 --> 14:32.909 matters . To leverage existing DOW 14:32.909 --> 14:36.909 investments , SDSFIEV and SDSFIEM make 14:36.909 --> 14:38.950 shared data sets easier to find and 14:38.950 --> 14:41.349 reuse by giving them a common structure 14:41.349 --> 14:44.799 and consistent metadata . That reduces 14:44.799 --> 14:47.580 duplicated effort and maximizes value . 14:49.010 --> 14:52.890 Per EM 1110-1-2909 , 14:53.049 --> 14:56.250 a UAce national data set is an ADS and 14:56.250 --> 14:58.210 it must have its data and metadata 14:58.210 --> 15:02.109 schemas coordinated with SDSFIE . In 15:02.109 --> 15:04.479 addition , regions and districts must 15:04.479 --> 15:06.280 adhere to these standards when 15:06.280 --> 15:08.391 submitting to an authoritative source 15:08.391 --> 15:12.200 repository , or ASR . Note that the 15:12.200 --> 15:15.090 UAC ASR medallion accreditation process 15:15.090 --> 15:18.210 validates SDSFIE compliance in order to 15:18.210 --> 15:22.049 achieve silver medallion status . These 15:22.049 --> 15:24.271 last two opportunities hit at the heart 15:24.271 --> 15:25.993 of the drivers to implement an 15:25.993 --> 15:28.859 enterprise strategy such as this cost . 15:29.289 --> 15:31.729 Consider this introduction to Annex 1 15:31.729 --> 15:34.250 of the strategy document . Developing 15:34.250 --> 15:36.650 and maintaining geospatial data are the 15:36.650 --> 15:38.840 most expensive and crucial parts of 15:38.840 --> 15:41.039 implementing geospatial strategies . 15:41.239 --> 15:43.169 Standardization enables the data 15:43.169 --> 15:45.690 collected by districts or field offices 15:45.690 --> 15:47.857 to be used throughout the organization 15:47.857 --> 15:49.746 in an enterprise implementation . 15:50.789 --> 15:53.190 Compliance with data standards also 15:53.190 --> 15:55.309 ensures that the data other agencies 15:55.309 --> 15:57.031 collect will be compatible and 15:57.031 --> 15:59.270 interchangeable with UAce data sets . 16:00.650 --> 16:04.020 Thus , each SDSFIE product or activity 16:04.020 --> 16:06.500 directly enables the matching goal one 16:06.500 --> 16:08.556 opportunity , helping us move toward 16:08.556 --> 16:11.000 truly enterprise ready geospatial data 16:11.000 --> 16:12.940 in the most economical manner . 16:15.270 --> 16:17.500 This slide looks at how SDSFIE 16:17.500 --> 16:19.820 activities fit with new and ongoing 16:19.820 --> 16:21.890 EGINS efforts across UA . 16:23.700 --> 16:26.179 First , several national level program 16:26.179 --> 16:28.340 SMEs have already collaborated with 16:28.340 --> 16:31.140 SDSFIE program staff to align their 16:31.140 --> 16:34.390 schema requirements . This work laid 16:34.390 --> 16:36.223 the foundation for ensuring that 16:36.223 --> 16:39.429 SDSFIEV supports real mission-driven 16:39.429 --> 16:42.849 data needs . In 2023 , 16:43.090 --> 16:45.169 districts also contributed by 16:45.169 --> 16:47.489 responding to a feature usage survey . 16:48.580 --> 16:50.802 Their input is helping refine and clean 16:50.802 --> 16:54.150 up the Usace HQ 4.0.6 adaptation of 16:54.150 --> 16:57.150 SDSFIEV Gold , so it better reflects 16:57.150 --> 16:59.789 what Usace programs actually use in 16:59.789 --> 17:03.780 practice . As EGINS continues to mature , 17:03.940 --> 17:06.051 we'll begin enabling interoperability 17:06.051 --> 17:08.180 and reusability of data beyond the 17:08.180 --> 17:11.718 national data sets . District level ASR 17:11.718 --> 17:13.662 requirements will be the next step 17:13.662 --> 17:15.818 toward expanding SDSFIE alignment 17:15.818 --> 17:18.779 across the enterprise . You say 17:18.779 --> 17:20.779 specific DCSs are planned to be 17:20.779 --> 17:22.899 developed for all layers , with those 17:22.899 --> 17:25.010 supporting the MAPland Act identified 17:25.010 --> 17:28.189 as the initial priority . These DCS 17:28.189 --> 17:30.078 documents will give districts the 17:30.078 --> 17:32.133 guidance they need when collecting , 17:32.133 --> 17:34.930 editing , or interpreting data . In 17:34.930 --> 17:37.420 addition , geospatial data management 17:37.420 --> 17:39.579 plans will play an important role by 17:39.579 --> 17:42.640 expanding on SDSFIE schemas whenever 17:42.640 --> 17:44.979 project-specific requirements go beyond 17:44.979 --> 17:48.709 what SDSFIE currently provides . Taken 17:48.709 --> 17:50.989 together , these efforts , national 17:50.989 --> 17:53.045 program alignment , district feature 17:53.045 --> 17:55.829 usage input , DCS development , and 17:55.829 --> 17:58.239 project level DMPs illustrate how 17:58.239 --> 18:01.550 SDSFIE and EGINS activities are being 18:01.550 --> 18:03.709 coordinated to help UAC achieve its 18:03.709 --> 18:06.390 five enterprise level geospatial goals . 18:07.229 --> 18:09.819 We're modernizing , standardizing , and 18:09.819 --> 18:12.030 aligning our practices so that our 18:12.030 --> 18:14.180 geospatial data becomes a truly 18:14.180 --> 18:17.900 enterprise asset . The 18:17.900 --> 18:20.540 message here is clear . Usace data 18:20.540 --> 18:22.429 stewards should ensure that their 18:22.429 --> 18:24.939 geospatial data adheres to the schema 18:24.939 --> 18:28.619 documented in the SDSFIEV Usace HQ 18:28.619 --> 18:32.510 4.0.6 adaptation . But in 18:32.510 --> 18:35.010 what specific cases is this true ? 18:36.420 --> 18:38.099 Compliance to the current UAS 18:38.099 --> 18:40.689 adaptation is required for databases of 18:40.689 --> 18:42.849 record , data that is shared , 18:43.219 --> 18:45.441 particularly with organizations outside 18:45.441 --> 18:47.689 of UAS , and data that is fully 18:47.689 --> 18:49.745 processed and has a production level 18:49.745 --> 18:51.640 quality or enduring nature . 18:52.949 --> 18:56.060 Conversely , raw or unprocessed data , 18:56.390 --> 18:58.910 interim data in some stage working 18:58.910 --> 19:01.229 toward production , and data that is 19:01.229 --> 19:03.118 required to adhere to a different 19:03.118 --> 19:05.340 standard , does not need to comply with 19:05.340 --> 19:08.069 the UAce HQ 4.0.6 adaptation of 19:08.069 --> 19:11.890 STSFIEV . Note that this last 19:11.890 --> 19:14.112 category of exemption could simply mean 19:14.112 --> 19:17.349 applying a different SDSFIEV adaptation . 19:18.260 --> 19:20.579 For example , geospatial data 19:20.579 --> 19:23.099 deliverables for big army would in most 19:23.099 --> 19:25.780 cases require adherence to the SDSFIE 19:25.780 --> 19:29.050 4.0.2 Gold Army adaptation , or 19:29.050 --> 19:30.780 alternatively , the Air Force 19:30.780 --> 19:34.219 adaptation 4.0.3 for projects with 19:34.219 --> 19:37.410 products going to the Air Force . As 19:37.410 --> 19:40.109 articulated in the EGINS strategy , 19:40.359 --> 19:42.920 there are important reasons integral to 19:42.920 --> 19:45.140 USA's functions for the harmonization 19:45.140 --> 19:48.689 of models that is being promoted . In 19:48.689 --> 19:50.800 order to enable better coordination , 19:51.020 --> 19:53.260 cost efficiencies , and improved 19:53.260 --> 19:55.149 decision making , we need to work 19:55.149 --> 19:57.239 together in accord as a larger 19:57.239 --> 20:00.099 organization . Modernization is an 20:00.099 --> 20:02.819 opportunity to update our data . The 20:02.819 --> 20:05.459 best time to plant a tree is 10 years 20:05.459 --> 20:08.619 ago . The second best time is now . 20:09.770 --> 20:12.089 The same is true for the timing of data 20:12.089 --> 20:15.050 compliancy to SDSFIE and the benefits 20:15.050 --> 20:18.520 to the enterprise . We know that 20:18.520 --> 20:20.742 education will be key , and we are glad 20:20.742 --> 20:22.298 you are taking part in this 20:22.298 --> 20:24.959 presentation . One thing the geospatial 20:24.959 --> 20:27.750 COP members can do moving forward is 20:27.750 --> 20:30.609 learn from each other . If any 20:30.609 --> 20:33.060 districts have updated or are in the 20:33.060 --> 20:35.300 process of updating databases to be in 20:35.300 --> 20:37.780 accordance with the SDSFIE schema , 20:38.010 --> 20:40.177 would they be willing to share lessons 20:40.177 --> 20:42.343 learned or best practices with a group 20:42.343 --> 20:46.239 at a geotech exchange ? Today , 20:46.250 --> 20:48.869 we explained why implementing STSFIE 20:48.869 --> 20:51.030 standards provides value to you and 20:51.030 --> 20:52.863 your project , as well as to the 20:52.863 --> 20:55.750 enterprise by meeting EGINS goals . 20:57.060 --> 20:59.819 The requirement to use SDSFIE is meant 20:59.819 --> 21:02.219 to support you , it is not meant to get 21:02.219 --> 21:04.900 in your way or to be an onerous burden . 21:05.380 --> 21:07.339 When done properly and with just a 21:07.339 --> 21:09.450 little practice , these standards and 21:09.450 --> 21:11.561 technologies should save you time and 21:11.561 --> 21:15.449 money . Thus , using SDSFIE standards 21:15.449 --> 21:17.969 is and will increasingly be vital to 21:17.969 --> 21:20.880 the success of UAS at all levels of the 21:20.880 --> 21:24.540 organization . The SDSFIE support staff 21:24.540 --> 21:27.359 and the UAce SDSFIE leads are here to 21:27.359 --> 21:30.079 help you achieve that success . Don't 21:30.079 --> 21:31.619 hesitate to call on us . 21:34.189 --> 21:37.689 This concludes the SDSFIE and UAce Part 21:37.689 --> 21:41.150 2 , EGINS training . The next 21:41.150 --> 21:43.369 training resources in this series are 21:43.839 --> 21:47.709 SDSFIE and UAce Part 3 , adaptations , 21:47.989 --> 21:51.390 and STSFIE and UAce Part 4 , Portal and 21:51.390 --> 21:53.869 tools . If you want to learn more about 21:53.869 --> 21:56.819 other detailed SDSFIE topics , visit 21:56.819 --> 21:59.270 our training resources page at the URL 21:59.270 --> 22:01.469 listed here . Thank you for your 22:01.469 --> 22:03.069 interest in SDSFIE .