National Invasive Species Information Management System NISIMS

1. Geospatial �09 Kathie Jewell April 29,2009 National Invasive Species Information Management System NISIMS

2.  National Invasive Species Information Management System What is NISIMS? Development Strategy Deployment Strategy

3. 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 Had been based on strictly weeds � weed database. It now encompasses all invasive. Task assistant had been developed in support of the Bureau�s NILs. As of 9.3 it is now a component of ArcGIS.Had been based on strictly weeds � weed database. It now encompasses all invasive. Task assistant had been developed in support of the Bureau�s NILs. As of 9.3 it is now a component of ArcGIS.

4. Business Processes that NISIMS Addresses Survey Infestation Treatment Evaluation Monitoring

5. How did we get here ? �02 IT Investment Board - Weed Business Case Completed Completed 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 model Logical Data Model Physical Data Model contracted to ESRI �05 Database development

6. 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).

7. Business Reengineering �As is� Report Regulations Existed No consistent reporting methods are implemented No standard business processes are implemented National reporting necessitated manual data consolidation No consistent data collection method with definitions are implemented Survey Area Not Tracked Program lacked the integration of Spatial Analysis and Modeling

8. 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

9. Contracts ESRI � Application development Northup � Legacy data transition BLM Issuing data standards

10. Data

11. Geospatial Components Survey Area Infestation Treatment Monitoring � New geometry Weed Management Area Proposal Location It requires: national administrative boundaries, gcdb, ownership

12. Legacy Data Legacy (internal and external) data submitted by states has been entered. State/Field Office crosswalks have been generated.

13. System Architecture

14. System Architecture Replicated Existing Infestations/Treatments Data to be maintained in the Corporate SDE instance at the BLM National Operations Center (NOC) Access to NISIMS database available via Citrix for input and analysis Custom ESRI applications used for edit & analysis. System architecture design � arc server and mobile gis National database is stored in ORACLE SDE Each state will have their own state database State databases will be maintained and replicated to the national database The application will be released for 9.3 ArcGIS National dataset will be published through geocommunicator Data to be maintained in the Corporate SDE instance at the BLM National Operations Center (NOC) Access to NISIMS database available via Citrix for input and analysis Custom ESRI applications used for edit & analysis. System architecture design � arc server and mobile gis National database is stored in ORACLE SDE Each state will have their own state database State databases will be maintained and replicated to the national database The application will be released for 9.3 ArcGIS National dataset will be published through geocommunicator

15. Workflow Proposals Survey and Identification/Infestation Treatment of an Infestation Monitoring of an Infestation Evaluation of Treatment

16. Business Process Office Proposal WMA Field Collection Infestation/Monitoring/Treatment/Evaluation/Survey Area Office Report Generation

17. 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)

18. NISIMS�s Task Assistant

19. NISIMS ArcPad Toolbar Infestations Point, Line, Polygon Treatments Point, Line, Polygon Evaluations Monitoring Survey Area

20. NISIMS�s Field Collection Hardware Trimble HP Ipaq Software ESRI ArcPAD NISIMS ArcPad Toolbar Collections Methods Manual Input GPS

21. Deployment Strategy Complete the software testing Hosted at the Oregon State Office Citrix, Oracle, State databases, National instance ArcGis 9.3 Publish National dataset � External External partners interface Field Test �09 field season February Complete software modifications Incorporate cooperators datasets Populate national dataset Application distribution Equipment support Stimulus projects Treatment boundary standard PE definitions Enhancements March Training for State Weed Specialists April Transition FY�08 Field Season Data April Legacy data QC, data entry (domains), install software May Procure additional hardware/software April/May Host virtual training sessions, supply user guide Field Season Field Test Application Generate Datasets for Treatment/Disturbance July Populate geocommunicator Sept/Oct Address software modifications. Obtain CM/Deployment approval. Transition application to NOC February Complete software modifications Incorporate cooperators datasets Populate national dataset Application distribution Equipment support Stimulus projects Treatment boundary standard PE definitions Enhancements March Training for State Weed Specialists April Transition FY�08 Field Season Data April Legacy data QC, data entry (domains), install software May Procure additional hardware/software April/May Host virtual training sessions, supply user guide Field Season Field Test Application Generate Datasets for Treatment/Disturbance July Populate geocommunicator Sept/Oct Address software modifications. Obtain CM/Deployment approval. Transition application to NOC

22. 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