Overview:Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE) Services Support

Overview:Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE) Services Support

Joint Services Environmental Management Conference 23 May 2007

Tim Maidl(301)-862-2762

tmaidl@upper-90.com

JSEM 20072

OverviewOverview

• Introduction

• The Transition

• Communication

• Training

• Wrap up

Introduction – JSEM 20073

The SDSFIE VisionThe SDSFIE Vision

• The SDSFIE Five-Year Vision Statement

4

SDSFIE’s 7 Guiding PrinciplesSDSFIE’s 7 Guiding Principles1. SDSFIE will focus on the geospatial representation of

features and maintain a minimum number of attributes. It will link to our business databases for attribute data and not duplicate attributes found in business databases.

2. SDSFIE will provide a data model that is scalable from installation mapping up to Service level and DoD; from local to global

3. If a relevant data content standard already exists, SDSFIE must incorporate it into the model rather than develop new content.

4. SDSFIE standard development will follow a nationally recognized development process

5. SDSFIE will reside in the public domain and is vendor neutral6. The standard will be responsive and built to support the

business needs of data creators and end users7. SDSFIE is governed and managed by the DISDI Group.

Introduction – JSEM 2007

5

The STARS TeamThe STARS Team

• USACE – ERDC TEC– COR: Mr. William (Bill) Ryder

William.H.Ryder@erdc.usace.army.mil (703.428.6767)

• Northrop Grumman / TASC’s SDSFIE Team– Deputy Program Manager: Mr. Marc Beckel

Marc.Beckel@ngc.com (703.227.8535)

• Team Goals– Adhere to the new SDSFIE Vision– Establish strategies for DoD standards alignment

Recognize as a DISR mandated Standard– Evolve the SDSFIE

Facilitate HarmonizationThrough UML ModelingCoordination with various standards bodies

– Compliant with DoD Policies and Requirements

Introduction – JSEM 2007

6

Organizational Relationship ChartOrganizational Relationship Chart

Supporting

Legend

Reporting

Installation

User

SDSFIE Consumers

MajorCommand

Installation

User Non-DoD User

RegionalCommand

Installation

User

RegionalCenter

Installation

User

SDSFIE Working Group

Division

District

User

IMCOMRegion

InstallationManagement

Command(IMCOM)

DISDI Group (Chaired by DISDI Executive Manager)

Introduction – JSEM 2007

7

What should the DoD user expect?What should the DoD user expect?• Release 2.600 (Jan 07)

– Physical Data Model UpdateReal Property Inventory (RPI) ModelLevee Database ModelArcGIS 9.2 compatibility modification Same Tool Set as 2.500NO incorporation of content requests since 2.500 release

• Release 3.0 (Fall 08)– Logical Data Model (Revolutionary Change)

Model compliant with standards improved interoperabilityMuch the same content; some additions no capability loss“One feature, one definition” easier to use/applyNew toolset that will enforce compliance while enabling “adaptation” to specific needs improved interoperability / usefulness

The Transition – JSEM 2007

8

SDSFIE Release 2.600SDSFIE Release 2.600• Content

– Release 2.500 Entity Types/Tables– Real Property Inventory from DISDI– Levee Database Model (Version 1.8+)

• Statistics (RPI / Levee)

– 1135 Features (13 New Features 5/8)– 1234 Tables (5 New Tables 0/5)– 33,433 Attributes (384 New Attributes)

The Transition – JSEM 2007

9

SDSFIE Release 2.600SDSFIE Release 2.600

• Based on Release 2.500 Final Software

• Modified hyperlink to new http://www.sdsfie.org/

• No significant enhancements except:– Geodatabase Builder

Adjustments to accommodate ArcGIS 9.2Added additional Domain limitations for RPI/LeveeNew ArcGIS Expanded Text Field capability

– Geodatabase LoaderAdjustments to accommodate ArcGIS 9.2

– Compliance CheckerAdaptation to handle ArcGIS Expanded Text Field capability

The Transition – JSEM 2007

Software ModificationsSoftware Modifications

10

Transition Plan OverviewTransition Plan Overview• What is it?

– The steps required to transition from the baseline (As-Is) architecture to the target (To-Be) architecture

• For SDSFIE, there are two Revolutionary transitions followed by three Evolutionary transitions – Revolutionary (to 3.0)

Logical data model revisionTool development

– Evolutionary (post 3.0)Logical data model maintenanceTool maintenance and improvementAbility to support facilitating and migrating business applications

The Transition – JSEM 2007

11

The (Near) FutureThe (Near) Future

• UML modeling

• Definitions will be clarified and improved

• Eliminate redundancy

• Integrate additional DoD models

• Create implementations via tools• Model Registry/Repository• Database Creation

• Database Migration & Sharing• Database Validation• Release 3.0 Fall 2008

GOAL: One Feature, One Definition

The Transition – JSEM 2007

12

Business DriversBusiness Drivers• Strategic requirements such as DISR, BEA, DDMS,

ISO, FGDC, and other DoD standards and models

• Upon completion of the SDSFIE LDM (Release 3.0), future releases of the SDSFIE will be driven by DoD Business Mission Area Requirements

• Individual content requests and change recommendations will drive local adaptations and not the LDM – Individual changes may result in LDM changes if they are

approved by the respective DoD data owner and/or the DISDI Group

The Transition – JSEM 2007

13

• Objectives– Coordinated Efforts – Proactive Involvement – Deliver Concise Necessary

Information– Promote Community Involvement– Interface with Standards Bodies

• Delivery Mechanisms– New Website– On-Line, e-Mail, and Phone Help

Desk– Conferences and Events– Training

Key to the New SDSFIE

CommunicationCommunication

Communication – JSEM 2007

14

The New SDSFIE WebsiteThe New SDSFIE Websitehttp://www.sdsfie.org

Communication – JSEM 2007

15

• As the STARS Team performs the transition, the intermediate model components will be made available via the SDSFIE website

• Forums will be available and specific comment periods will be announced that will allow for feedback on the “state of the SDSFIE”

• In this way, the transition will be visible to those who have an interest

The “Glass Box”The “Glass Box”

Communication – JSEM 2007

16

• Operating Hours - 6:00AM through 6:00PM (EST) Mon - Fri• Response within 24 hours (1 business day) to phone,

e-mail, or web submission • SDSFIE Releases

– Supporting User Operating Systems (except Vista and Linux)– Content Clarification– Receipt and queue of Modification Recommendations– Tool Support (Question/Answers, Bugs & Fixes)

• Web Site Support– Knowledge Base (White Papers and FAQ)– Monitored User Forums – Papers on new SDSFIE Strategies and Training– “Chat Assistance” monitor during Help Desk Hours - Envisioned

• Tool Upgrades/Enhancements for new Vendor Versions

1.866.9SDSFIE or helpme@sdsfie.orgThe Help DeskThe Help Desk

Communication – JSEM 2007

17

Overview of Training MethodologyOverview of Training MethodologyTraining is classified into two types: instructor-led &

self-directed

• Instructor-led Training– Distance learning (instructor-led)– On the job training– Synchronous (Online/Offline)– Asynchronous (Online/Offline)– Blended e-learning

• Self-Directed Training– Self-paced manuals, “how-to” books, individual workbooks– Cassettes / videotapes– Web-based training (WBT)– Computer-based training (CBT)– Distance learning (self-paced)

Training – JSEM 2007

Questions & AnswersQuestions & Answers