How Emerging Trends in GIS Technology will Affect Defense Systems

1
How Emerging Trends in GIS Technology will Affect
Defense Systems
David J Swann Defense Market Manager dswann_at_esri.c
om
2
Aims

• Introduction to ESRI
• Identify key technology trends
• Explain NG technology
• Show how NG technology will affect defense systems

3
Why This Briefing?

• Information Technology moves very fast
• Standing still is NOT an option
• New IT / GIS technologies offer significant
  advantages for developers and users.
• This is relevant for ALL players

4
Our Goal

• Support Our Users in Successful GIS
  Implementation

5
Who is ESRI

• Founded in 1969
• Privately owned - zero debt posture
• 2000 people
• World leader in GIS software
• Sustained 20 annual growth
• Have about 75 of Federal GIS business

6
ESRI A Collection of Teams
Administrative Services
Professional Services
Educational Services
Software Products
Sales
Manufacturing/ Distribution
Management
Marketing
Technical Support
Software Development
Business Partners
Customer Service
7
What does ESRI do?

• GIS Software Development - Including training,
  documentation, technical support upgrades.
• GIS Professional Services - Including consulting,
  database design and automation, application
  development implementation support.

ESRI is the world leader in GIS software ESRI is
not a systems integrator
8
ESRI The Company
U.S. Regional Offices
Intl. Offices
Distributors

• ESRIAustralia
• ESRI-Belux
• ESRICanada
• ESRIFrance
• ESRIGermany
• ESRIItaly
• ESRI-India
• ESRIKorea
• ESRINetherlands
• ESRIPoland
• ESRISouth Asia
• ESRISpain
• ESRISweden
• ESRIThailand
• ESRIUK
• ESRI-Venezuela

• Redlands, CA
• Anchorage, AK
• Boston, MA
• Charlotte, NC
• Denver, CO
• Minneapolis, MN
• Olympia, WA
• San Antonio, TX
• St. Louis, MO
• Washington, DC

• Over 65 Countries Worldwide

9
ESRI User Base

• The Largest Installed GIS Base in the World
• City, County, and Regional Governments
• State and Federal Government Agencies
• Private Firms (Oil and Gas, Consulting,
  Mapping, and Sales and Marketing Companies)
• Water, Gas, and Electric Utilities
• Over 2,000 Universities and Nonprofit
  Organizations
• A Diverse, Global User Community

10
ESRI Strategic Relationships

• Industry-Leading Hardware Vendors
• Leading DBMS Companies
• Image Processing, CAD, and GPS Firms
• GIS Service Companies
• Consultants, Developers
• Systems Integrators
• Data Publishers
• Other Software Firms

11
Technology Directions
12
NG Technology
Take the best characteristics of existing products
Reengineer the Codebase
Create New Generation Products
8
Functionality
Functionality Usability Components
Usability
Components
13
NG Technology Investment

• 3 Years
• 120M
• Effort and money that should NOT be re-spent.
• Spread across ALL markets including defense.

14
Architectural Considerations
15
User Needs for GIS - Today
Data Creation
10s
Analysis
100s
Query
1,000s
Browse
10,000s
ArcExplorer
16
User Needs for GIS - NG
Data Creation
10s
Analysis
100s
Query
1,000s
Browse
10,000s
NG Technology
17
Open Approaches
RDBMS
CAD
ESRI
NIMA
18
Emerging Architectures
C4ISR Application
Production Application
Topographic Application
Imagery Exploitation Application
ESRI Components
ERDAS Components
Other vendors Components
19
Data Access
20
User Access to Data - Today
Open API
Producers
Direct Read
Import
Import
Import
DIGEST Data
21
New System Connectivity
Thin Clients
COM Clients
Classic Clients
Producer or Deployed Database
DIGEST Data
22
Appropriate Access to Data
23
ArcInfo 8
24
ArcInfo 8

• The first NG product
• The flagship product
• Many evolutionary elements making a revolutionary
  product
• Functionality roll-out through 8.x
• Classic ArcInfo in the box

25
ArcInfo 8Desktop Architecture
ArcInfo 8 Applications
GeoData Object Model
Personal ArcSDE
Files
ArcSDE
26
Compelling ArcInfo 8

• Add object behavior to VPF
• Create self-validating geoobjects
• Metadata
• Embeddability
• Customizability (Drag Drop, VBA, OCX Core)
• Open (COM), Open (Programming), Open (Data)

27
Technology HeadlinesProcess Implications
28
All Relational Data Model

• Fast, Multi-User access to huge, seamless spatial
  data
• Faster processes,
• distributed processes,
• Less data management overhead
• Easier integration with other battlefield systems
• More accurate tasking
• Faster distribution of products
• Uses RDBMS data security mechanisms
• Better Data Security

29
Object Oriented GIS

• Behavior Modeling
• Faster, more controlled feature extraction
• Terrain-specific feature extraction
• Self-validating feature extraction
• Inheritance
• Easier modeling of complex features
• Extending the relational model
• Strengthen existing data standards

30
Production Objects
31
Battlefield Objects...
This isnt a point ...its an OBJECT - A
Divisional Headquarters responsible for an AOR
that comprises exactly 3 brigade AORs
This isnt a Polygon this is an OBJECT An
armored battlegroup AOR that has advanced
10 miles today, lengthening its logistic tail
This isnt a network its an OBJECT A logistic
tail that links fighting units via convoy routes
to the BAA, back to the DAA...
32
Geodatabase ConversionESRI Core Behaviors
Convert to Geodatabase
Geodatabase
Coverage / Shape
Object Class Table skdjfhkfjsdjjfj jfksjhdfj
kjhfkjfh ddkgfo0pb knerr lskdffe djf
You dont need to do anything!
Registry
ESRI DLLs are Registered During ArcInfo
Installation
33
Geodatabase ConversionCustom Behavior Creation
Convert to Geodatabase
Geodatabase
Coverage / Shape
Object Class Table skdjfhkfjsdjjfj jfksjhdfj
kjhfkjfh ddkgfo0pb knerr lskdffe djf
Stub Code
C
Registry
34
Geodatabase ConversionSubsequent Conversion
Convert to Geodatabase
Geodatabase
Coverage / Shape
Object Class Table skdjfhkfjsdjjfj jfksjhdfj
kjhfkjfh ddkgfo0pb knerr lskdffe djf
This has already been done it doesnt need to
be done again!
Stub Code
C
Registry
35
Feature Creation
Create Feature
Geodatabase
Object Class Table skdjfhkfjsdjjfj jfksjhdfj
kjhfkjfh ddkgfo0pb knerr lskdffe djf
This has already been done it doesnt need to
be done again!
Stub Code
C
Registry
36
Metadata Handling

• Metadata maintenance
• Quality understood in processes
• Provider information maintained
• Validated Processes

37
Analysis - Feature Extraction Cycle
Terrain-specific
Time Estimate
Source Validation
Feature Extraction GeoObject
No
Terrain-specific
Analysis GeoObject
Data Validation
Answer will have quality x - OK?
Conduct Analysis
Yes
Quality
38
Versions(Only for Server SDE!)

• GeoDatabases may have multiple versions
• Optimistic concurrency (i.e., not locking)
• Directly supports long transactions
• Versions have names
• All have same schema
• Each may have different content
• Always a Default version (e.g., AsBuilt)
• Most users work with it
• Easy to make versions (ArcMap)

39
Versioning
Default Common Operating Picture
Engr
VersionOPPLAN A
Arty
Battle Data
Log
Ops
VersionOPPLAN B
Engr
VersionOp Update
Arty
40
Conflicts and versions
Remember these are all the same database just
recorded deltas from the definitive battle
picture.
41
Resolving edit conflicts

• Triggered by Save, Reconcile or Post

Conflicting FeatureClass
Your options to resolve conflict
Conflicting feature(s)
Versions
Conflicting field
42
How to get there?

• Migrate from file - SDE
• Invest in RDBMS technology
• Start VB training
• Think about data modeling object modeling
  process modeling
• ArcInfo 8 evaluation
• Connect with other users
• Compete and commit!
• Virtual Campus

43
Demos Questions?