1 / 23

SDSFIE 3.0: From Pilot Studies to Official Release

SDSFIE 3.0: From Pilot Studies to Official Release. ESRI IUC 14 Jul 10. Marc Beckel 703.227.8535. Marc.beckel@ngc.com. Agenda. Current status of SDSFIE 3.0 (Beta and Gold) SDSFIE 3.0 Web-based tools SDSFIE Pilot Project Review Questions. Current Status of SDSFIE 3.0.

mada
Download Presentation

SDSFIE 3.0: From Pilot Studies to Official Release

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SDSFIE 3.0: From Pilot Studies to Official Release ESRI IUC 14 Jul 10 Marc Beckel 703.227.8535 Marc.beckel@ngc.com

  2. Agenda • Current status of SDSFIE 3.0 (Beta and Gold) • SDSFIE 3.0 Web-based tools • SDSFIE Pilot Project Review • Questions ESRI IUC 14 Jul 10

  3. Current Status of SDSFIE 3.0 • Beta Version (Not Official Release) • Released in Jan 2010 • Training development is being finalized • INTRO Course on website with Official Release • Public Works Model Modifications • SDSFIE 3.0 Gold to include a “Generalized” PW Model • PW “Detailed” model will be a Special Adaptation on the Website • SDSFIE 3.0 Gold set for Official Release in early Sep 2010!!! The End Is Near! ESRI IUC 14 Jul 10

  4. SDSFIE Logical Data Modeling Military Operations Range, Training & Testing Waterways Civil Works Flood Control & Water Supply Cultural Resources ESOH Natural Resources SDSFIE Restoration, Management, & OEHazards Final Modeling Activity Public Works Installations Real Property Planning Common/Cross- Function Features Foundation 4 ESRI IUC 14 Jul 10

  5. Public Works SemanticsFor Linear Utilities in “Generalized” Model • Node – a point that is a subdivision of a utility network. • For example, Electrical generator or fuse, Wastewater pump or meter point, or Communications amplifier • Segment – a line that is a subdivision of a utility network • For example, Electrical line, Wastewater pipe, Communications cable. • UtilityFeature – a feature that logically belongs to a utility but does not participate in the network itself • For example, SCADA sensors, underground enclosures, utility markers, etc. • A “network” is defined as all features (nodes and segments) of a particular type (e.g., WaterUtilityNode and WaterUtilitySegment) that have the same Real Property Network Unique Identifier (RPNUID) • No explicit topology, no explicit linking of features to form a network graph ESRI IUC 14 Jul 10

  6. Public Works SemanticsAdditional Elements • Pavement and Rail differ from Node-Segment. • Pavement: • Rail: Network Branch Section Network Track Segment • NOTE: Roads are a Common Model Element ESRI IUC 14 Jul 10

  7. SDSFIENamedFeature CommunicationsUtilityNode CommunicationsUtilitySegment ElectricalUtilityNode AbstractUtilityClass ElectricalUtilitySegment GasUtilityNode GasUtilitySegment UtilityFeature RailTrack PavementBranch PavementSection RailSegment POLUtilityNode POLUtilitySegment ThermalUtilityNode WastewaterUtilityNode WastewaterUtilitySegment ThermalUtilitySegment WaterUtilityNode WaterUtilitySegment ESRI IUC 14 Jul 10

  8. SDSFIE 3.0 Web-based Tools

  9. Services’ Pilot Projects 9 ESRI IUC 14 Jul 10 • USACE • Work with Four Full DB teams looking across the CW missions • Army • Work with Three Installations and the Army Mapper team • Navy • Work with Four Installation Databases • Air Force • Work with One USAF Installation per MAJCOM – Focus on CIP Data • USMC • Inventory of all current database schemas • Looking at USMC Data Model (modified version of SDSFIE 2.6) • Develop USMC Adaptation for SDSFIE 3.0

  10. SDSFIE Pilot Projects Findings • Two Big Items Impacting Auto-Migration • Data that is Required for Specific Operations, but NOT Compliant with a Prior Release Model • Data that is Compliant with Prior Release Model, but has been “Removed/Deleted” from SDSFIE 3.0 Gold • Adaptation can resolve these issues, but with impact to Auto-Migration of Data • Need to Focus on Prior Release Compliancy • Auto-migration for SDSFIE 3.0 is based on Prior Release ESRI IUC 14 Jul 10

  11. SDSFIE Pilot Projects Findings:Tools Related • Building an Adaptation takes TIME! • The process of Extending the SDSFIE 3.0 requires careful consideration • The tools require a detailed oriented process • REMEMBER: ALL extensions must have proper written justification (See DISDIG Implementation Strategy Guidance) • Trial Migrations vs. Adaptation Builds • Currently tools don’t allow a user to “test” their Adaptation against their Data Schemas before its finalized • Migrations can be time consuming! • Factors: OS, Personal GeoDatabase vs Oracle SDE, Machine Speed, Version of ArcGIS, size of DB, and Number of Feature Types • Migration can take anywhere from 5 mins to 7 hours! ESRI IUC 14 Jul 10

  12. SDSFIE Pilot Projects Findings:Tools Related • Feature Types Requiring Multiple Geometries • ESRI SW does not allow for the same instance of a feature type with Multiple Geometries Option #1: Separate the Geomteries, BUT retain link to the Parent Feature Type in Gold • Pro: Retains the link for Auto-Migration • Con: All attributes, regardless of geometry, are retained (extended or otherwise Option #2: Extend with new feature types to represent each Geomtery • Pro: Maintains true separation of the feature types • Con: No Auto-Migration occurs for Extended Features ESRI IUC 14 Jul 10

  13. SDSFIE Pilot Projects Findings:Data Related • Extensions to SDSFIE 3.0 DO NOT support Auto-Migrations • Adaptations with ANY Extension will result in some manual migration • CADD Data • CADD attributes retained in GIS data – Non-Compliance • Specialized (Regional or Site Unique) requirements • Example: Red Cockaded Woodpecker Fed Data Reporting Requirements in SE US ESRI IUC 14 Jul 10

  14. Summary • SDSFIE 3.0 Official Release in Fall 2010 (TBD) • LOTS of changes from Prior Release (2.6 and earlier) to 3.0 • Begin to Review your Data Early! • Understand your non-compliance areas • Begin to Understand the Cross-walk for Migration to 3.0 • Consider Moving Business Data out of your GIS Databases • The SDSFIE 3.0 Gold Beta is on the Website Now for Review • Complete with Release Notes, Tool Documents, and Help Files ESRI IUC 14 Jul 10

  15. SDSFIE SIG • SDSFIE Special Interest Group (SIG) Meeting • Tonight: 5:30 - 7 pm • Where: Room 29B • Open Forum with focus on the details of the SDSFIE 3.0 model, the SDSFIE 3.0 tools, and audience questions/participation ESRI IUC 14 Jul 10

  16. Questions? ESRI IUC 14 Jul 10

  17. Back-up Slides ESRI IUC 14 Jul 10

  18. The Generic ProcessPhase I Prior ReleaseFeature Types Complete List ofFeature TypeNames andDefinitions CurrentDatasetContents NewFeature Types Service Supplied DefinitionsandGeometry 18 ESRI IUC 14 Jul 10

  19. The Generic ProcessPhase II HasCorresponding3.0 Feature FinalAdaptationCandidateList Complete List ofFeature TypeNames andDefinitions Has noCorresponding3.0 Feature STARSServiceCollaboration ESRI IUC 14 Jul 10

  20. SDSFIE 3.0 Training Development • Current Activity underway to design and develop a Training Curriculum for SDSFIE 3.0 prior to or with the Official Release • Will replace current SDSFIE 2.6x online and classroom training modules • Additional Advanced Courses and Leadership Workshop Material to be designed and built in 2010 • One Classroom Training per service has been established, but not scheduled at this time (2010) • See Service Lead for Details or Requirements • USACE as part of GIS/GPS Training – Huntsville, AL, Mar 10 • Additional classroom training to be as requested / funded ESRI IUC 14 Jul 10

  21. start SDSFIE Version ? Export 2.x Schema Backup Existing Data Determine Data Needs Fix Data as Required Run SDSFIE Validation Tool SDSFIE Browser Tool Older than 2.4 Backup Existing Data YES Can get Compliant? SDSFIE 2.x Compliant ? NO Determine Service Policy NO Use Non-Migration Data Load YES Mostly Upgrade to good Release Select Service Adaptation Migrating Prior Release Data using SDSFIE tools into a User Adaptation SDSFIE Browser Tool Run Trial Migration Needs met by Adaptation? NO Document Adaptation Shortfalls / Create User Adaptation and Customize YES Run Final Migration SDSFIE 3 Compliant ? Script Results as Expected ? YES Run SDSFIE Validation Tool end Run Scripts on Source Data NO NO SDSFIE Toolset ESRI IUC 14 Jul 10

  22. Backup Existing Data Determine Data Needs Determine Service Policy start Loading Non-Compliant User Data (not supported by Migration tool) SDSFIE Browser Tool Select Service Adaptation Document Data to Adaptation Correlation Needs met by Adaptation? YES Document Adaptation Shortfalls / Create User Adaptation and Customize NO SDSFIE Browser Tool Run Generator Tool NO SDSFIE 3 Compliant ? Export 3.0 Schema Run SDSFIE Validation Tool Perform Manual Data Load YES end SDSFIE Toolset ESRI IUC 14 Jul 10

  23. start SDSFIE Version ? Document Adaptation Shortfalls / Propose Adaptation changes or Interim Solution Provide Adaptation feedback through SDSFIE governance Backup Existing Data Assess Data Migration Needs Evaluate approved SDSFIE Adaptation SDSFIE Model Browser Older than 2.5 Backup Existing Data Needs met by Adaptation? Run migration scripts NO Evaluate migration results Upgrade to SDSFIE 2.61 YES Run SDSFIE Checker Script Results as Expected ? NO SDSFIE 2.x Compliant ? Fix issues NO YES Run SDSFIE Checker SDSFIE 3 Compliant ? Upload Schema to SDSFIE website NO Generate 2.x Schema Generate 2.x to 3.0 migration scripts Collect Platform Information Re-evaluate scripts Make adjustments SDSFIE Toolset end ESRI IUC 14 Jul 10

More Related