DESIGN AND PLANNING OF A
SOURCE AND PRODUCT
GEODATABASE FOR THE HARRIS
CORPORATION’S GGI PROGRAM
By Andrew Korbel
Capstone Proposal Overview
Introduction
 Overview of the Current Source and
Product Tracking System
 Capstone Project Plan and Design
 Summary

Capstone Project Objective

The objective of this capstone project is to build a
system that can catalog source data and track a
product’s status in a geospatially-enabled database
 Source data can be defined as any geospatial
dataset needed to produce a product
 Examples include various raster and vector
datasets such as: Imagery (Commercial &
National), various scaled CADRGs and ADRGs,
various levels of DTEDs, Geodatabases of Feature
Data, Geo-positioning Support Data, etc.
Harris Corporation Overview





Headquartered in Melbourne, Florida
International communications and information
technology company
Serving government and commercial markets in
more than 150 countries.
Annual revenue of almost $5 billion
16,000 employees — including nearly 7,000
engineers and scientists.
GGI Program Overview



Global Geospatial Intelligence Program is
contracted by the National Geospatial Intelligence
Agency (NGA).
Production of various raster and vector products.
This contract is worth approximately 50 million
dollars in invoices per year for Harris.
GGI Program Overview Cont’d

Within Harris, The GGI Program is split into 2
distinct departments that produce a variety of
classified and unclassified raster and vector
products.
 Global
- Controlled Image Base (CIB 1m & 5m), Digital
Point Positioning Databases (DPPDB), Shuttle Radar
Topography Mission (SRTM) Void Fill
 Vectors - Topographic Line Maps (TLMs)at various
scales, Urban Feature Data (UFD)
Current Source and Product Data
Management
Product Records Created
GovernmentProvided
Spreadsheets
WFMT
ClearQuest
GUI
WFMT
SQL Server
Database
Media and Source Records Created
Check in
physical media
Manual Update of WFMT Records (Media,
Source, Product Records)
Ingest Data
Physical
Media
Containing
Data Items
Data
Items
Source
Evaluation
100%
Visual
Review
Production
Current Source and Product Data
Management Cont’d
PRODUCT
CIB_1m
(quartercell)
MEDIA
TAPE
MEDIA
DVD – AMSD
MEDIA
TAPE
MEDIA
TAPE
MEDIA
DVD – AMSD
SOURCE
National Imagery
SOURCE
National Imagery
PRODUCT
CIB_1m
(quartercell)
PRODUCT
CIB_1m
(quartercell)
PRODUCT
CIB_1m
(quartercell)
MEDIA
Firewire
MEDIA
Firewire
SOURCE
CommerciaI
Imagery
Commercial imagery (CI)
may be spread across
multiple firewire drives.
Creation not
currently
automated
If 5m required:
PRODUCT
CIB_5m
PRODUCT
CIB_5m
PRODUCT
CIB_5m
PRODUCT
CIB_5m
PRODUCT
CIB_5m
PRODUCT
CIB_5m
PRODUCT
CIB_5m_Volume
Current State of Source/Product
Database Cont’d
Media Record Summary
Total # of Records
3900
3000
3000
2150
Media Records
Source Records
1003
33%
Product Records
Source Record Summary
2150
Total Source
Records
494
16%
340
15%
Media Records
Media Records not
connected to Source
Records
Product Record Summary
56
3%
Source Records Source Records Source Records
not connected
not connected
not connected
to Media
to Product
to Product nor
Records
Records
Media Records
3900
Product Records
1195
55%
Source Record not
updated to reflect current
Product Record State
Proposed System
Source’s Geodatabase(s)
CADRGs
Imagery
DTED
AMSDs
Ingestion of
Source Data
DTED GDB
Product’s Geodatabase(s)
UFD
CIB 1m
CIB 5m
DPPDB
Project Setup
Imagery GDB
CADRGs GDB
AMSDs GDB
CIB 1m GDB
DPPDB GDB
UFD GDB CIB 5m GDB
What the System Is Not
A Traditional Geodatabase
 A GIS that produces product deliverables
 An Enterprise GIS

Strategic Purpose of the System



The creation of this system has been mandated
by GGI Program Management.
GGI Program will now be responsible for
acquiring their own source data needed to
produce products.
The importance of quickly and accurately
knowing what source data is in house or needed
to produce a product becomes vitally important
to the success of the program in our resourceand time-constrained environment.
Overview of Project Proposal Plan


I will be developing and managing the
creation of the project proposal and pilot
project
Key contributors to the development of the
system will be the Global and Vector’s System
Engineers
Overview of Project Proposal Plan
Cont’d

The proposal will take an iterative approach that will include
but is not limited too:
 Developing the objective/description of the project
 Creating a needs assessment
 Defining the data and database requirements,
 Defining the system requirements
 Developing a cost-benefit analysis, migration strategy, and
risk analysis
 Developing a small pilot project over a study area for
proof of concept throughout the entire project planning
that will continue after final project plan
Needs Assessment
Identify the potential users of the system
 Identify the mission/goal of the system
 Identify how we track our source data currently
and define what the problems are currently
with the existing system.
 Define users requirements for the system being
built
 Produce a Needs Assessment document

Data and Database Requirements






Define the data required for the system
Define the required characteristics needed for the data
that will be inputted in the system
Identify data conversion requirements needed to
produce an integrated and seamless system
Define the structure of the required data
Define how each source/product will be represented
and design the database
Produce Data and Database Design document
System Requirements






System Requirements driven from needs
assessment and data and database
requirements
Define the scope of the system
Identify required hardware needed
Identify required software needed
Identify required networking needed
Produce a System Architectural Design
Document
Cost-Benefit Analysis




Identify and calculate costs by year
Identify and calculate benefits by year
Identify and calculate cost-benefit ratios
Produce a Cost-Benefit Analysis
document
Migration Strategy




Identify a strategy
Plan sequence of events for migration
process
Define migration timeline
Produce a Migration Strategy document
Risk Analysis




Identify and define the risks involved in
the Implementation of the system
Identify how to mitigate the risk
Score and summarize the identified risks
Produce a Risk Analysis document
Pilot Project/Proof of Concept




Build feasible pilot project throughout the
entire project planning stages – Iterative
Approach
Identify or create a geographic area that
encompasses all source datasets
Incorporate product bounding rectangles and
how they relate to there source data
Perform all use cases for each identified user
of the system
Project Milestones
Complete Needs Assessment and Formal Document – July 20th
Complete Data and Database Requirements and Formal Document
– August 3rd
Complete System Requirements and Formal Document – August
17th
Complete Cost-Benefit Analysis and Formal Document – August
24th
Complete Migration Strategy and Formal Document – August 31st
Complete Risk Analysis and Formal Document – September 7th
Complete Formal Design and Project Plan Presentation and
Program Management Approval – September 30th
Complete Pilot Project/Proof of Concept – November 30th









Milestones within the Pilot Project will be developed after the formal design
and plan is established
Possible Roadblocks/Shortfalls




Availability of Resources
Getting Program Management/Stakeholders to
agree on the proposed project plan due to
differing requirements from the different
departments
Unwillingness to adopt new architecture
(hardware/software)
Cost associated with new system
Capstone Presentation Deliverables



Presentation of the project lifecycle - design and planning
phases
Demo the pilot project which would include how the following
teams utilize the system to retrieve required information in
order to accomplish their everyday tasks
 Program Management Team
 Data Management Team
 Production Management Team
Other Deliverables (Harris Corp.)
 Formal Design and Project Planning Documents
 Fully Functional Pilot Project
Research Performed/References
Design/Planning References for a Traditional
GIS/Geodatabase
“Thinking About GIS” by Roger Tomlinson
“System Design Strategies: An ESRI ® Technical Reference Document • July 2007 Revision 1” by
Dave Peters
https://tsc.wes.army.mil/contacts/groups/FWG/Environmental/env/frameimplement.htm Implementing A GIS – Describes the different phases of implementation from a needs
assessment to systems analysis and maintenance to cost benefit strategies.
http://www.worldbank.org/html/fpd/urban/upgrading/docs/esri/idb-presentations/04-implementingsuccessful-gis.pdf - Implementing Successful GIS Projects in Developing Countries – Describes planning and
implementing strategies.
http://americancityandcounty.com/mag/government_building_gis_ground/ - Planning and Implementing a GIS
– Local Government – This paper talks about the implementation process and implementation and
management issues encountered through various real life examples.
http://www.gisdevelopment.net/technology/gis/techgi0012pf.htm - This paper outlines an approach to
successfully implementing a GIS.
http://lagic.lsu.edu/gisprimer/strategies.asp - GIS Strategies & Issues – Strategies for managing and Utilizing
GIS in Your Organization--- This is a website that describes strategies for planning and implementing a GIS
which includes topics such as application development to funding strategies.
Research Performed/References
Data Management References for a Traditional GIS/Geodatabase
http://gis.esri.com/library/userconf/proc01/professional/papers/pap742/p
742.htm - Spatial Data Management in an Enterprise GIS – This paper
describe the experience of the St. George Consulting Group and the Maine
Department of Environmental Protection in creating a spatial data
management infrastructure for an Enterprise GIS.
http://dusk2.geo.orst.edu/djl/arcgis/docs/hydro-datamgmt.pdf Hydrographic Data Management Using GIS Technologies - This paper
describes the use of Geographic Information System (GIS) technology to
provide effective and efficient data management for processed
hydrographic data.
Note: References and research performed could not uncover a direct solution
to the customized system that needs to be built.