SDSFIE 3.0: From Pilot Studies to Official Release

SDSFIE 3.0: From Pilot Studies to Official Release

SDSFIE 3.0: From Pilot Studies to Official Release

ESRI IUC

14 Jul 10

Marc Beckel703.227.8535

[email protected]

ESRI IUC 14 Jul 10

AgendaAgenda

Current status of SDSFIE 3.0 (Beta and Gold) SDSFIE 3.0 Web-based tools SDSFIE Pilot Project Review Questions

2

ESRI IUC 14 Jul 10

Current Status of SDSFIE 3.0Current 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 EndThe EndIs Near!Is Near!

3

ESRI IUC 14 Jul 10

SDSFIESDSFIE

Military Operations

Civil Works

ESOH

Installations

Common/Cross-Function Features

Foundation

Range, Training & Testing

Waterways

Flood Control & Water Supply

Cultural Resources

Restoration, Management, & OE Hazards

Real Property

Planning

Public Works

4

SDSFIE Logical Data ModelingSDSFIE Logical Data Modeling

Final Modeling Activity

Natural Resources

4

Public Works SemanticsFor Linear Utilities in “Generalized” ModelPublic 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 105

Public Works SemanticsAdditional Elements

Public Works SemanticsAdditional Elements

• Pavement and Rail differ from Node-Segment.– Pavement:

– Rail:

Network

Branch

Section

Network

Track

Segment

ESRI IUC 14 Jul 106

NOTE: Roads are a Common Model Element

SDSFIENamedFeature

AbstractUtilityClass

UtilityFeature

CommunicationsUtilityNode

CommunicationsUtilitySegmentElectricalUtilityNode

ElectricalUtilitySegmentGasUtilityNode

GasUtilitySegmentPavementBranch

PavementSectionPOLUtilityNode

POLUtilitySegment

ThermalUtilityNode

ThermalUtilitySegmentWaterUtilityNode

WaterUtilitySegmentWastewaterUtilityNode

WastewaterUtilitySegment

RailTrack

RailSegment

ESRI IUC 14 Jul 107

SDSFIE 3.0 Web-based ToolsSDSFIE 3.0 Web-based Tools

ESRI IUC 14 Jul 10

Services’ Pilot ProjectsServices’ Pilot Projects

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

99

SDSFIE Pilot Projects FindingsSDSFIE 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 1010

• 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

SDSFIE Pilot Projects Findings:Tools Related


11

• 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



12

• 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

SDSFIE Pilot Projects Findings:Data Related

SDSFIE Pilot Projects Findings:Data Related

13

SummarySummary

• 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


SDSFIE SIGSDSFIE 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

Questions?

16

ESRI IUC 14 Jul 10

Back-up Slides

17

ESRI IUC 14 Jul 10

The Generic ProcessPhase I

The Generic ProcessPhase I

18

CurrentDataset

Contents

Prior ReleaseFeature Types

NewFeature Types

CompleteList of

Feature TypeNames andDefinitions

Service Supplied

Definitionsand

Geometry

18

ESRI IUC 14 Jul 10

The Generic ProcessPhase II

The Generic ProcessPhase II

HasCorresponding

3.0 Feature

Has noCorresponding

3.0 Feature

CompleteList of

Feature TypeNames andDefinitions

FinalAdaptationCandidate

List

STARSService

Collaboration

19

ESRI IUC 14 Jul 10

SDSFIE 3.0 Training DevelopmentSDSFIE 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

20

Run Trial Migration

Run SDSFIE Validation

Tool

end

startSDSFIE

Version ?

SDSFIE 2.xCompliant ?

Export 2.x Schema

NOYES Document Adaptation Shortfalls / Create User

Adaptation and Customize

Determine Data Needs

Determine Service Policy

Needs metby Adaptation?

NOYES Mostly Use Non-Migration Data Load

SDSFIE Toolset

Run Final Migration

Run Scripts on Source Data

Run SDSFIE Validation Tool

Backup Existing

Data

Script Results asExpected ?

SDSFIE 3Compliant ?

YES

Backup Existing

Data

Upgrade to good Release

Older than 2.4

Select Service Adaptation

Can get Compliant?

Fix Data as Required

YES

NO

NO

SDSFIE Browser Tool

SDSFIE Browser Tool

NO

Migrating Prior Release Data using SDSFIE tools

into a User Adaptation


Run Generator Tool

end

start

NOYES Document Adaptation Shortfalls / Create User

Adaptation and Customize

Determine Data Needs

Determine Service Policy


SDSFIE Toolset

Perform Manual Data Load

Run SDSFIE Validation Tool

Backup Existing

Data

SDSFIE 3Compliant ?

YES

Select Service Adaptation

SDSFIE Browser Tool

SDSFIE Browser Tool

NO

Loading Non-Compliant User Data (not supported

by Migration tool)

Document Data to Adaptation Correlation

Export 3.0 Schema


Run SDSFIE Checker

end

startSDSFIE

Version ?

SDSFIE 2.xCompliant ?

Generate 2.x Schema

Fix issuesNO

Upload Schema to SDSFIE website

YES

Provide Adaptation feedback through SDSFIE

governance

Document Adaptation Shortfalls / Propose

Adaptation changes or Interim Solution

Assess Data Migration

Needs

Evaluate approved SDSFIE Adaptation


NO

YES

Collect Platform Information

SDSFIE Model Browser

SDSFIE Toolset

Generate 2.x to 3.0 migration scripts

Run migration scripts

Evaluate migration results

Run SDSFIE Checker

Backup Existing

Data

Script Results asExpected ?

Re-evaluate scriptsMake adjustments

SDSFIE 3Compliant ?

NO

NO

Backup Existing

Data

Upgrade to SDSFIE

2.61

Older than 2.5
