Spatial Data Standard for Facilities, Infrastructure, and Environment (SDSFIE)

1. Spatial Data Standard for Facilities, Infrastructure, and Environment (SDSFIE) Webinar 1300-1500 Eastern 19 SEP 18 (Session 1) 26 SEP 18 (Session 2) Call-in toll-free number: 1-888-557-8511 (US) / Access Code: 903 935 1 / Security Code: 4444 Join Webex meeting: https://usace.webex.com/usace/j.php?MTID=md63dc7e3599d923c73dc9805d9a874c8 Meeting number: 966 475 753 Meeting password: 4444

2. Webinar Considerations Please mute your phone / computer mic, unless asking question. Please wait until the end of the slide to ask questions.

3. SDSFIE Webinar • Section 1: SDSFIE Overview (45 minutes) • Break (5 min) • Section 2: Data Migration (45 minutes) • Questions Section 1 SDSFIE Overview Agenda: • Program History • Governance and Policy • Family of Standards • Vector Data Model Structure • Version History • SDSFIE Online Overview

4. Program History: The CADD/GIS Technology Center - Origins of SDSFIE • Defense Management Review Directive 982 led to 1993 Tri-Service CADD Technologies Center Charter • Part of the USACE ITL and later renamed Tri-Service CADD/GIS Technologies Center • Original developers of Spatial Data Standards for Facilities, Infrastructure, Environment (SDSFIE) • New federal IT legislation and business management transformation mandates prompted a revisiting of CADD/GIS Center responsibilities On 21 Mar 2006, the Center Board of Directors voted to outsource SDSFIE stewardship and future development NLT 30 Sep 2006 given new Service GI&S programs, NGA standards teaming, and DoD IT governance processes.

5. 1992 Milestone TSSDS Release Nov 93 SDSFIE Release Dec 99 SDSFIE Version History 1.20 1.40 1.60 1.70 Aug 95 Nov 93 1992 Nov 96 Aug 97 1.75 Jan 98 “Tri-Service CADD/GIS Technology Center” 1.80 Feb 99 “CADD/GIS Technology Center creates SDSFIE Jul 99 SDSFIE Stewardship by USACE Engineer Research and Development Center (ERDC) Information Technology Laboratory (ITL) – Vicksburg, MS 1.90 Dec 99 1.95 Apr 00 2.00 2011 SDSFIE 3.0 Jan 01 2.1 DoD Service Components Utilize to organize and manage installation geospatial assets and recommend modifications for DoD installation requirements 2017 Jan 02 SDSFIE 4.0 2.20 Aug 02 2.30 2.31 Oct 03 2.40 Apr 04 Oct 04 2.50 Oct 05 “CADD/GIS Technology Center” SDSFIE Stand-down Mar 06

6. SDSFIE Governance and Structure Services Mission Areas Resources, Tools, & Support Policy & Governance • Real Property • Public Works • Transportation & Infrastructure • Test & Training Ranges • Environment • Natural & Cultural • Recreation • Civil Works • Governance • Adaptations • Implementation • Reporting & Data Submittal • DODI 8130.01, Installation Geospatial Information & Services: • (ASD(EI&E) GIO/IGI&S Governance Group (IGG) • SDSFIE Standards: DISDI Portal • Policies & Guidance • Atlas • Data & Metadata Search Vector Raster Metadata Portrayal Quality Services Endorsed DISDI Atlas Pro • Map Viewers • Army Mapper • CorpsMap • GeoFidelis (USMC) Map Viewer • GeoReadiness Explorer • Program Websites/Portals • Army IGI&S (USA) • GeoBase (USAF)(limited access) • GeoFidelis (USMC) • GeoReadiness (USN) • Sustainable Range Program (SRP) • USACE Geospatial Platform • Authoritative Data Sources • Evaluate Investments • Common Installation Picture (CIP) • IGG Structure and Functions • Army Support Responsibilities SDSFIE Online • Models & Workflow Tools • Training Videos • Standards Documents • Component Pages SDSFIE is a standards framework governed by the IGG, supported with online tools, technical support, and training, to meet the DODI goal of making Installation and Civil Works geospatial data and services visible, accessible, understandable, trusted, and interoperable across the DoD

7. Installation Geospatial Information and Services (IGI&S) SDSFIE Policy - DODI 8130.01 6. DoD COMPONENT HEADS. The DoD Component heads: a. Assign responsibilities and establish procedures within their Component to implement the data collection, guidelines, and procedures specified by this instruction. b. Ensure that all business systems, geospatial data assets, information, and IT services pertaining to installations and environment in the Active, Guard, and Reserve Components are in compliance with relevant standards, the interoperability guidance established by the ASD(EI&E), and this instruction. 7. SECRETARIES OF THE MILITARY DEPARTMENTS AND DIRECTOR, WHS. In addition to the responsibilities in section 6 of this enclosure, the Secretaries of the Military Departments and the Director, WHS: a. Designate IGI&S elements within their respective organizations to coordinate IGI&S capabilities and facilitate integration of IGI&S activities and organizational functions across the DoD business enterprise. 8. SECRETARY OF THE ARMY. In addition to the responsibilities in sections 6 and 7 of this enclosure, the Secretary of the Army: a. Provides technical development, change management, general support, and implementation support for IGI&S standards, which will be a function supporting the IGG. b. Ensures that the IGI&S requirements of the United States Army Corps of Engineers civil works program are met, and that these requirements are fully represented in the IGG.

8. AR 115-13 2–4. Chief of Engineers The COE, as the Commanding General (CG), U.S. Army Corps of Engineers (USACE)— a. Appoints a USACE IGI&S program lead. b. Enforces USACE compliance of geospatially referenced installation information to Federal and DOD standards related to IT, IA, IS, CAD, Building Information and Modeling, and GIS. c. Directs the IGI&S program lead, USACE to— (1) Represent USACE on the IGI&S FCC. (2) Execute IGI&S support to installations in accordance with the OACSIM IGI&S policy and guidance. (3) Develop and execute the USACE IGI&S POM. (4) Develop training programs and SOP documentation for geospatial data collection and map production. (5) Recommend policy and standards to the OACSIM IGI&S program manager. (6) Serve as command proponent for USACE geospatial data. (7) Serve as data layer proponent lead for applicable geospatial data layers or delegate to an appropriate program manager to identify program execution priorities, program, validate, and defend resources in the planning, programming, budgeting, and execution process in support of applicable geospatial data layers. (8) Deliver data for all geospatial data layers of USACE proponency. (9) Procure imagery, GIS support, and other activities in accordance with IGI&S program strategy. (10) Support OACSIM IGI&S program remote sensing and imagery requests for installations through USACE’s Army Geospatial Center Imagery Office. (11) Ensure USACE IGI&S systems and applications are compliant with OACSIM IGI&S program policy.

9. ER 1110-1-8156 2. Applicability. a. ER 1110-1-8156 applies to all USACE Commands having Civil Works, Military, or Environmental responsibilities. USACE Commands who support Civil, Military and Environmental missions have the responsibility to collect, manage and report their geospatial data as outlined here and in EM 1110-1-2909. It specifically applies to functional areas that involve geospatial technologies and services for Computer Aided Design and Building Information Modeling (CAD/BIM), Survey and Mapping (S&M), Site Information Modeling (SIM), Computer Aided Facility Management (CAFM), Geographic Information Systems (GIS), remote sensing, database development, and modeling. (4) GIS functional areas generally encompass regulatory investigations and studies, planning, real estate, emergency operations, and engineering functions. b. This regulation also applies to a variety of geospatial products, including river and harbor maps; navigation charts; inundation mapping; vulnerability and risk analysis; recreation and lake management activities; dredge site placement; real estate project maps; engineering and construction drawings; survey reports; reconstruction, restoration, and rehabilitation efforts; environmental stewardship; environmental studies; Hazardous, Toxic, and Radioactive Waste (HTRW) studies; shoreline studies; and channel condition reports. 5. Policy. e. All non-raster data developed for, by, or in partnership with USACE must comply with the Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE). Metadata are required for all geospatial data developed for, by, or in partnership with USACE.

10. SDSFIE Family of Standards • SDSFIE Vector: “Gold ” Logical Data Model and all Component HQ-level Adaptation LDMs. • SDSFIE Metadata: V 1.0.2 is Class-2 profile of ISO 19115 and ISO 19115-2. V.2 will be Class 2 profile of NSG Application Schema 8.0 (includes ISO 19115-1, 19115-2, 19110, and 19157). • Can download Esri SDSFIE Metadata Style from USACE App Portal • SDSFIE Raster: Preferred and recommended raster standards. Raster Standards Compendium - comprehensive summary of raster and related standards adopted, endorsed, recommended or referenced by the Department of Defense (DoD). • SDSFIE Data Quality: Over-arching guidance for a tiered quality approach; includes data quality processes, measures, and metrics for vector, raster, and geospatial services. • SDSFIE Portrayal: Presentation of geospatial information; may include map portrayal, symbology, or related encoding specifications. • SDSFIE Services: Functionality provided through information technology-based interfaces (e.g., web service interfaces). • SDSFIE Endorsed Standards: Consensus specifications, standards, models, and publications developed and managed by organizations other than DISDI, but which are vetted and endorsed and recommended for IGI&S use by DISDI.

11. USACE APP Portal – SDSFIE M Style Sets

12. SDSFIE-V “Models” • In SDSFIE-Vector, or “SDSFIE-V”, a “Model” consists of an organized set of “elements”: • A set of Entities(Feature Types and/or non-spatial Object Tables) • with Attributes, or characteristics, for each feature • Attributes may be constrained by Enumerations • Enumerations (“picklists”) have a set of Enumerants • and, potentially, participate in Associations • In each Version of SDSFIE-V (e.g., 3.1 or 4.0), there is a Gold version that is the root of all other versions • Each Service develops their own Headquarters Adaptation of the Gold version • Services can allow lower echelons to develop their own adaptations • All adaptations must adhere to SDSFIE-V Implementation Guidance (SVIG) SDSFIE-V 4.0 Gold Army4.0 … Air Force 4.0 Navy Data Model 4.0 GEOFidelis 4.0 USACE HQ 4.0 …

13. SDSFIE Data Model Terminology Logical, and Physical (Implementations) 2 Primary Business Missions: USACE Civil Works DoD Installations (IGI&S) • Business Subject Matter Area Model = IGI&S and Civil Works Missions • Entities from the SDSFIE Gold LDMs is grouped into 15 Application Subject Matter Areas • “Gold 4.0” - 281 Entities • Component-specific LDMs, e.g., “USACE HQ 4.0.1” • PDM is schema expression of LDM in format that can be implemented in a GIS • Implementation of PDM at Military Installations, and at USACE HQ, Divisions, and Districts Civil Works Cultural Resources Airfields Recreation Natural Resources Planning 14 Business Lines: Boundaries Buildings & Structures Utilities Transportation Military Range Training Pavement Environmental Reference, Elevation, & Survey USACE HQ 3.1 Gold 3.1 Gold 4.0.1 USACE HQ 4.0.1 SDSFIE Online Models Gold & Service Adaptations: Workspace XMLs Physical Data Models Installation and District Implementations and National Datasets Geodatabases IENC Seattle District Fort Riley • For SDSFIE-V, the Logical Data Models can be created, edited, reviewed, approved, and downloaded (Excel format), and used to create a Physical Data Model to be downloaded (ESRI Workspace XML schema) and implemented as a geodatabase

14. Logical Data Model (LDM) “elements” include any of the following model components: Folder – a set of feature types Feature type – a set of thematically equivalent features Attribute – a characteristic of the features Enumeration – constraint on an attribute Enumerant – permissible values within an enumeration Association – describes relationships between two tables SDSFIE Logical Data Model “Elements”

15. Folder~ Feature Dataset (“CCF”) SDSFIE LDM Elements in ArcGIS PDM Feature Type ~ Feature Class (“Bridge_A”) Attribute ~ Field (“operationalStatus”) Enumerant ~ Value (“abandoned”) Enumeration ~ Domain (“OperationalStatus”)

16. SDSFIE-V History:2.6 to 3.0 Transition • Issues with 2.6: • Lack of managed change process • Lack of inter-service coordination • Business data stored in attribute tables • Resulted in: • Duplicated entity concepts • Bloated model • Service-specific elements in general model • "Primary Modernization“ Actions: • Merged many 2.6.1 FTs, and removed most non-spatial business tables • Cut entities by ~order of magnitude • Removed many business attributes • on average, 31 attributes per entity in v2.6 • average of 9 in v3.0 • One location for each entity concept!

17. SDSFIE-V History:3.0 to 4 • 3.1 to 4.0 was “Secondary Modernization” • Implemented SOPs for • Change Management Process (CMP) • Initiated SDSFIE-V Working Group • Instituted change interoperabiliity • categories, and versioning rules • Added Description, Note, Justification, • and Business Req/Doc properties • 4.0.1 was First Corrigendum Release, basis for USACE HQ Adaptation • Utilized new A/P/P tool for CMP • 4.0.2 is Second Corrigendum Release, basis for Army HQ Adaptation *IENC = Inland Electronic Navigation Chart

18. SDSFIE-V “Change” and “Release” Types Change Category / Release Type Release Name Examples of Changes • Definition changes (without affecting relationship to other elements) • Note additions or modifications • Alias Name changes • Enumerant extensions • Attribute length increases 4.0.1 4.0.2… 4.0.n Corrigendum Low 6 months • Removing permissible geometry • Definition changes (change in scope, or relationship to other elements) • Model Name changes • Adding a constraining enumeration to an attribute; changing data type • Attribute length decreases 4.0 4.1 … 4.n Minor Level of Negative Impact On Interoperability Release Frequency 4 5 … n Major • Entity Splits • Entity Merges High Decade

19. SDSFIE Online – Website Walkthrough[DEMO] • Homepage – 3 primary sections • Menu Strip [guide for walkthrough] • SDSFIE Online • Standards • Vector, Metadata, etc. • Change Management Process (CMP) • Models and Workflows • Browse Generate • Data Dictionary • Migration • Model Builder • Validate • Component Page • Support

20. SDSFIE Online – Homepage https://www.sdsfieonline.org After consenting, you have access to the SDSFIE Online Homepage – Provides a brief overview of SDSFIE, with links to the all parts of SDSFIE Online, with 4 main sections Consent Banner – An initial pop-up to give consent Menu Strip section – Access to all tools and pages Welcome section – A brief explanation of SDSFIE along with a “Learn More” link that will direct you to a page that explains the SDSFIE Family of Standards. What’s New? section – Highlights new developments or updated tools / documents Stakeholders section – provides links to each Component page

21. SDSFIE Online – The Menu Strip Home – will always take you to the Welcome (Home) page SDSFIE Online – provides links to general information and how to get started Standards – provides details on each of the SDSFIE Standards Models & Workflows – provides links to each of the SDSFIE Tools, and the means to interact with the models Components - provides links to each component page (identical to the links on the Home page) Support – provides links to a FAQ page, SDSFIE User Guides and additional training • The Menu Strip: • Top of almost all SDSFIE Online pages (not Tools) • Versatile • Hover/click accesses different SDSFIE Online topics and functions

22. SDSFIE Online – “SDSFIE Online” • What is SDSFIE Online? – Provides an overview of SDSFIE Online and the SDSFIE family of standards. • Getting Started – Three step process: • Step 1) Register • Step 2) Learn More • Step 3) Get to Work • Website Changelog • Register User – first, create User Account • Specify a Sponsor or Manager • Takes 24-48 hrs, normally less • Log In As User – must log in to obtain access to models and tools • Standard password reset and username recovery functions • Learn More – See “Support” menu item.

23. SDSFIE Online – “Standards”

24. SDSFIE Online – “Models & Workflows” Browse Generate – allows examination of a single model at a time and/or publishes a physical or logical data representation of that model Data Dictionary – provides multi-faceted search interface and reports across all logical data models, with saved search function Migration – supports moving data repositories to new (target) models, with capabilities for managing and registering custom data and sub-adaptations Model Builder - provides for creation and editing of logical data models, with options for interactive GUI or workbook upload for large/complex models Validate – facilitates comparison between any two models, including source to parent mode, with workbook output; shows adherence to SDSFIE rules

25. SDSFIE Online – “Components”US Army Page • To be Updated Soon! • US Army HQ 4.0.2 – model details • Implementation Plan • Migration Guidance and Support

26. SDSFIE Online – “Support” • SDSFIE FAQ – commonly asked questions and general information about SDSFIE and the website; accessible from the “Get Help” link at the bottom of any page • User Guides and Training Videos – 4 Tool/Workflow downloadable user guides and 26 training videos (watch through YouTube, or download) • Direct Contact “Help Desk” – response within 24 hrs (8:00AM-4:30PM EST Mon-Fri) • Webform email submission • Email: support@sdsfieonline.org • Phone: (571) 403-0238

27. End Section 1 • 5 minute break (if time allows) --- DON’T HANG UP OR LOG OUT!

28. Section 2: Data Migration Agenda: • Adaptation Development • HQ USACE Adaptation • USACE Migration • Migration Overview • Migration Process • Migration Preparation

29. USACE Adaptations: Rules & Guidance • SDSFIE Vector Implementation Guidance (SVIG) - Sets up rules for Gold, for adapting Gold, so as to maintain interoperability • Provides rules under which all Components develop their HQ-level Adaptation • Provides rules for under which a Components may develop “subordinate” adaptations, based on the HQ Adaptation • Mandates Component Implementation Plan • Mandates Component Data Migration Plan • USACE Implementation Plan • Allows for adaptations within USACE, based on HQ-level Adaptation (USACE HQ 4.0.x) • Provides governance (roles and process) for the sub-adaptations • References the detailed rules found in SVIG

30. Adaptation Approach - Basics • “SDSFIE Adaptation” defined: A formalized alteration of a model which results in another model tailored to the particular business requirements of an implementing organization. An Adaptation consists of a specific Profile and/or all the Extensions that are required to meet specific business requirements. • SDSFIE Adaptation consists of three primary steps: • “profiling” – removing non-mandatory elements that the implementing organization does not require • Any entity other than those used in Installation COP • Any non-foundational attribute • “extending” – adding required elements not found in the parent model (e.g., needed by USACE but not in Gold) • “changing” – altering model, without affecting interoperability

31. SDSFIE Adaptation Concept Add attributes and/or domains Parent Adaptation Add entire Feature Types, and/or Tables PROFILE (Profiled Parent) EXTEND Child Adaptation Remove attributes and domains Remove entire Feature Types, and/or Tables

32. Benefits of SDSFIE adaptations • Keeps the “base” Gold model “clean” • Allows Services to add in data that is specific to their mission only • Shared data schema • All adaptations utilize an approved starting point, the “parent” model • Consistent data definitions • Definitions cannot be changed outside of CMP • Conceptual uniqueness is fundamental • Easily share and/or roll-up data • Interoperability is promoted through standardization • Potential to reuse or adapt common mission schemas • Provides definitions for several offices to leverage in enterprise GIS initiatives

33. USACE Adaptation Scope Executed in 9 Major Subordinate Commands (MSCs) or Regional Business Centers, 44 Districts (38 of which contribute to the Civil Works mission), and 6 specialized centers supporting the entire organization

34. USACE 4.0 Adaptation Overview • USACE HQ Adaptation of SDSFIE-V 4.0 Gold • Conducted 3 draft versions/reviews • SDSFIE-V 4.0 Gold • 287 entities • based on 4.0.1 Gold “Corrigendum Release” • “USACE HQ 4.0.1” • Removed 42 Military-specific entities • Added 223 new entities for USACE functional areas • 468 total entities

35. Corrigendum Releases and the4.0 USACE Adaptations • Every Component’s 4.0 Adaptation has a “Corrigendum” release of 4.0 Gold as a parent: • Gold 4.0.1 Corrigendum is the parent of the USACE HQ 4.0.1 model • Gold 4.0.2 Corrigendum is the parent of the Army Adaptation 4.0.2 model • Gold 4.0.3 Corrigendum will be the parent of the Navy 4.0.3 model (both TBD) • USACE can “update” their 4.0.1 HQ Adaptation to version 4.0.2 • add in all Gold Changes (from formal CRs) approved after 4.0.1 release and by 4.0.2 “cutoff date”

36. USACE Migration • HQ USACE 4.0.1 – Approved March 2018 • In SDSFIEOnline Registry • HQ USACE 4.0.2 – Modified from Army Corrigendum release • September 2018: WE WILL USE THIS VERSION • Must complete migration of USACE data to 4.0.X NLT 30 DEC 2020 • Method: • National data sets within 3 mission areas (starting with Navigation mission area) • Central pre-migration analysis/support • Mission area migration workshops (Navigation Nov/Dec 2018) • Push migrations to implementing Districts (e.g., Navigation subadaptationschemas)

37. USACE Migration • USACE Spatial Data Standards PDT • Review Gold model change requests resulting from migration • Review sub-adaptations • USACE Geospatial COP Lead approves sub-adaptations • Navigation: • Business line leaders meetings 19 Jun, 27 Jun • Navigation feature proponency by business line • Determine feature generation vs. “consumer” by business area • Next: obtain xml schemas to evaluate compliance • Conduct migration workshop(s) (Nov 2018) • Push results to “consuming” and “feeder” offices

38. Migration Overview As – Is (Parent/Source Model) Element A Element B Element C Element D Element E To-Be (Target) Element A-1 (split) Element A-2 (split) Element B/C (merged) Element D^ (changed) + Element N (new)

39. SDSFIE Migration Overview Physical Model Logical Models & Online Workflows Other Other 3.1 4.0 4.0 2.6 3.1 4.0 4.0 3.1 4.0 4.0 3.1

40. Migration Terminology • Model • a logical data model in the SDSFIE Online Registry • Schema • a physical data model, typically a representation of a geodatabase structure in Esri XML Workspace format • may include metadata, but not data records • Geodatabase • a database or file structure used primarily to store, query, and manipulate spatial data used by ArcGIS • the typical format for interactions (I/O) with the SDSFIE Online Registry, e.g., the expected starting input and output format for a migration • Source and Target • the input and output of a migration, respectively • Standard Data • data elements which are compliant to a Model in the SDSFIE Online Registry • context matters (e.g., attributes are considered in relation to a particular entity) • Non-Standard Data (aka Non-Compliant Data) • data elements which are not compliant to a Model in the SDSFIE Online Registry

41. SDSFIE Online – User WorkflowsMigration (Overview) • Model - a logical data model in the SDSFIE Online Registry. Ex: USACE HQ 4.0 Ex: USACE HQ 3.1 • Schema - an XML Workspace representation of a geodatabase structure including the metadata, but not the data. • Geodatabase - a database or file structure used primarily to store, query, and manipulate spatial data used by ArcGIS. This is the expected starting input and output format for a migration. • SDSFIE Migration is the process moving data from within one SDSFIE geodatabase, to another SDSFIE geodatabase where the two have differing schemas • The source schema must be associated with a Source Parent model in SDSFIE (for example USACE HQ 3.1) • A Target Parent model is identified (for example USACE HQ 4.0.2) • The result is a target geodatabase, with schema compliant to a registered SDSFIE model!

42. A bit more on Source and Target Models

43. Migration – System Requirements To fully utilize the SDSFIE Migration Workflow, you must have the following software on your computer: • ArcGIS for Desktop Standard or Advanced, 10.3.1 or above • Esri Defense Mapping or Esri Production Mapping (corresponding to your version of ArcGIS for Desktop) • Microsoft Office 2010 or above You will also need: • SDSFIEOnline user account • Ability / permission to download zip files and Excel workbooks • Ability / permission to install ArcGIS toolboxes

44. Migration – User Experience Level? • There are no specific requirements for the level of GIS training or experience that you need to perform a migration. • We do recommend: • Familiarity with the data that you are migrating, documentation of that data, and/or reach back to data originator / maintainer • Some familiarity with ArcGIS for Desktop – advanced user not necessary • Ability to follow instructions, persistence, willingness to ask for help!

45. Migration – About Data Compliancy… • SDSFIE-V was established to maintain IGI&S and CW geospatial data interoperability among and within DoD • The SVIG defines rules for the Gold model (e.g., 4.0.1 Gold), and for HQ-Level Adaptations of Gold (e.g., USACE HQ 4.0.1) • The USACE Implementation Plan defines rules for sub-adaptations (e.g., “USACE Baltimore District 4.0.1”, or “USACE Navigation 4.0.2”) to preserve flexibility and interoperability within USACE, and with DoD • What is “non-compliant” data? • Generally speaking, non-compliant data refers to all GIS vector database elements that do not adhere to the standards specified in the SVIG. • Non-compliance can occur anywhere within the feature classes, fields, domains, domain values, and relationships of your geodatabase.

46. Migration – Assessing Data Compliancy SDSFIE-V Compliancy has two parts – conceptual and property-level • Semantic or “conceptual” compliancy • Does your element concept match a concept in an SDSFIE-V LDM? • Matching is hierarchical: • Entities first, then attributes within each entity • Enumerations, then enumerants within each enumeration • If the concept matches, then all element properties / syntax must match • Syntactic or “property-level” compliancy • Does your data element exactly match all of the properties in the matched SDSFIE-V element? (e.g., Model Name, Definition, Description, Note, …) • The Model Name property is critical for automated matching: • Matches are made on basis of Model Names in Validation and Migration tools • Need to either (1) use the correct Model Name for an SDSFIE element concept, or (2) know the correct Model Name so the match can be established • Model Names changes between SDSFIE-V LDM versions are known & leveraged

47. Migration – Options for Non-Compliant Data There are 4 options for your data elements that are non-compliant: • Match your data element properties to that of the SDSFIE-V element • Change your Model Name, Definition, etc. to that of the SDSFIE-V element • In Migration, this is done automatically once you establish the match • Adapt or change the model to fit your data element(s) • Extend the SDSFIE-V LDM to add new (conceptually-unique) element(s) • You will need to provide a Definition and other properties • Your model might be an improvement, so request to change the LDM (CR) • Carry your non-compliant data through the Migration Workflow • As mentioned, non-compliant data is OK under certain conditions, and you may want to preserve the structure / keep all of your data together • The Migration Workflow supports moving non-compliant data from the source geodatabase to the target geodatabase • Delete, ignore, or otherwise do not include non-compliant data in the Migration Workflow

48. Migration Preparation – Checks • All elements in your data to be registered must have a Definition • The Definition (and Description and Note) is known for compliant or matched data • Definitions are obtained automatically from metadata • Definitions may be provided manually, using the Gathering Sheet, after locating in Data Dictionary, other documentation, or from an SME • Any match that exists between a non-standard data element and an SDSFIE element must be established manually in the Gathering Sheet • If you have renamed a standard element in your geodatabase and do not have the standard Model Name documented in your metadata, then you need to manually match that element to the correct element in the Source Parent (via the Gathering Sheet) • If your geodatabase is “mixed”, containing some data that is compliant to one SDSFIE model (e.g., Army HQ 3.1) and some data that is compliant to another, you will need to split the data up into two groups, run the Migration Workflow for each group, and then merge it afterwards • You need to identify the correct Source Parent for each entity in your data • Given: Every element in a registered SDSFIE model must have a Definition (and optionally a Description and Note)

49. Migration Preparation – Overview of Best Practices • Create Inventory • Start with your data dictionary, otherwise use Validation Tool to get full lists of elements quickly in spreadsheet format • Work at entity level first, then at attribute level • Characterize (add column for) each element, and populate as you: • Decide what can be discarded • Access and specify compliance to a model (e.g., 2.6 Gold, or USACE 3.1 HQ, and identify all non-standard elements • Identify any splits and merges involving non-compliant data • Identify data owner or functional area SME for every non-standard element (if not you!) – Definition generation is a critical step • Identify path forward for non-standard elements – to register or not to register… (“not” is acceptable for local data not to be shared) • Check 4.0.2 – Army HQ, and other Component’s models, before extending a “new” entity into your adaptation

50. Migration Workflow – Detailed Steps Updated SourceModel & Import DB SourceParent Model SourceModel & Import DB Target Parent Model Target Model 4 5 7 8 SDSFIE Online Import Source Schema Generate Gathering Spreadsheet Generate Crosswalk Spreadsheet Generate Target Model and Schema 6 C G S Edit, Import, Generate (Iterative) Gathering Spreadsheet SourceSchema Crosswalk Spreadsheet ArcCatalog / ArcMap Pre-Migration Tools Migration Tools S 9 1 Target Schema 10 Create Cross Reference Database (X-Ref GDB) and Target GDB Pre-migration Planning 2 3 Migrate Data Pre-migration Preparation Export Source Schema Post-Migration Actions TargetGDB SourceGDB X-Ref GDB