Geospatial ’09
Kathie Jewell April 29,2009
National Invasive Species Information Management
System NISIMS
National Invasive Species Information Management System
What is NISIMS?
Development Strategy
Deployment Strategy
What is NISIMS?
NISIMS provides tools for data collection and the generation of bureau-wide analysis and statistics for invasive species infestations and treatments through a centralized geodatabase
Geodatabase
ESRI ArcMap Toolbar
Task Assistant – Table of Contents to the Work and Data flow Download data to ArcPad Upload data to local server Data entry Upload data to National Server Generate reports
ESRI ArcPAD Toolbar
Business Processes that NISIMS Addresses
Survey
Infestation
Treatment
Evaluation
Monitoring
How did we get here ?
‘02 IT Investment Board - Weed Business Case CompletedCompleted Inventory of existing data/capabilities
’03 Business Enterprise Architecture/Business Reengineering Charter established – SME. “as is” “to be”
’04 Rapid Application Design Development (RADD) Conceptual data modelLogical Data ModelPhysical Data Model contracted to ESRI
‘05 Database development
How did we get here ?
’08 Completed “pilot” training in Montana, Colorado, Utah and Nevada
Mosaic of all existing data
Developed training material
The final conversion to a national system (personal geodatabase/access, Oracle Sde/replication and ArcGIS 9.3).
Business Reengineering
“As is” Report Regulations Existed
No consistent reporting methods are implementedNo standard business processes are implementedNational reporting necessitated manual data
consolidationNo consistent data collection method with
definitions are implemented
Survey Area Not Tracked
Program lacked the integration of Spatial Analysis and Modeling
NISIMS provides BLM and the Weed Program:
Standard Business Processes - Bureau-wide
Standard National Data Set available for both internal and external customers
Analytical tool
Definitions and Methods
A tool for Field Collection
Tools for Report Generation
Contracts
ESRI – Application development
Northup – Legacy data transition
BLM
Issuing data standards
Data
Geospatial Components
Survey AreaInfestationTreatmentMonitoring – New geometryWeed Management AreaProposal Location
It requires: national administrative boundaries, gcdb, ownership
Legacy Data
Legacy (internal and external) data submitted by states has been entered.
State/Field Office crosswalks have been generated.
System Architecture
System Architecture
Replicated
Existing Infestations/Treatments
National RepositorySDE
State/Project Geodatabase
Handheld Device
Workflow
Proposals
Survey and Identification/InfestationTreatment of an Infestation
Monitoring of an InfestationEvaluation of Treatment
Business Process
Office Proposal WMA
Field Collection Infestation/Monitoring/Treatment/Evaluation/Survey Area
Office Report Generation
Business Rules - Examples
All Weeds surveys include the number of acres systemically checked for the presence or absence of non-native invasive plants and/or noxious weeds
Survey Boundaries will be collected as polygons Acres surveyed are recorded as BS program element code units of
accomplishments Each infestation will have computer generated identification number once uploaded to the National Database
Infestations will be collected as points, lines or polygons Infestation does not represent the acres surveyed Each infestation represents only one species. If multiple species are
identified then multiple infestation records will be generated. Input will use drop down tables for species (NRCS Plant codes) and common names
Infestations can and will overlap. Although collected as point, line and polygon the feature class for infestations will be stored as polygon.
Infestations have to be 40 yards apart to be an infestation unto itself (system will calculate this distance)
NISIMS’s Task Assistant
NISIMS ArcPad Toolbar
Infestations Point, Line, Polygon
Treatments Point, Line, Polygon
Evaluations
Monitoring
Survey Area
NISIMS’s Field Collection
Hardware Trimble HP Ipaq
Software ESRI ArcPAD NISIMS ArcPad Toolbar
Collections Methods Manual Input GPS
Deployment Strategy
Complete the software testingHosted at the Oregon State OfficeCitrix, Oracle, State databases, National instance
ArcGis 9.3Publish National dataset – ExternalExternal partners interfaceField Test ‘09 field season
Deployment Strategy
Issue data standards, Program element
Incorporate ‘09 field season testing results
Transition ‘08 & ‘09 data collection
Transition application to National Operation Center
Deploy application 1/2010
Make it available to all cooperators
Top Related