Innovation… Leadership… Performance 2007 JSEM Josh Fortenberry (805) 982-4990 Naval Facilities Engineering Command Engineering Service Center aval aval nstallation nstallation estoration estoration nformation nformation olution olution N N I I R R I I S S Navy's Solution for Navy's Solution for Environmental Restoration Environmental Restoration Data Management Data Management
32
Embed
Navy's Solution for Environmental Restoration Innovation Data
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Documents– GIS Facility Maps and IR Site Boundaries– Land Use Control Data
7
Environmental Restoration Program- Need for NIRIS
•Part of DoD ERP (DERP)–About 4500 active sites in Navy–About $300 million per year
•Terra Bytes of data, 100s of users!!–6 regional NAVFAC offices with multiple
contractors working on multipleinstallations that have multiple ER sites with multiplesample locations that can be sampled multiple times, and analyzed various ways with hundreds of analytes reported, and validated...
•How can we manage this???Solution: NIRIS
8
NIRIS Concept
•Central, web based database
•Tools to ensure only quality data gets loaded
•Tools to visualize and analyze data, including GIS
•Interoprable with other enterprise systems
CONTR C
CONTR A
NIRIS
8 regional offices
CONTR B
CONTR D
NAVFAC
Tools
9
NIRIS Vision• Non-proprietary• Navy Marine Corps Intranet (NMCI)
–compliant with DoD Information Technology Security Certification (DITSCAP)
–web-based (Citrix)–no desktop install–Some restrictions on server side
10
NIRIS Database
NIRIS Database
11
5 Components of NIRIS
1)NIRIS database structure• Database for tabular data
–e.g., sample location and type (x, y, z, matrix type )
• Spatial data–e.g., site boundary, survey grid –Automatically updated based on triggers
• Environmental Data Management System for Admin Record, Post Decision, and Site File documents–e.g., PA/SI report, SOW
NIRIS Overview and Update
12
Components continued
2) NIRIS Electronic Data Deliverable (NEDD) tables- 50 Standard data submittal forms e.g., analytical,
pump test, lithology. 3) Administrative tools, instructions and training
- SOPs- RPM Handbook,- NEDD Data Checker/Data Loader
4) End user data analysis and GIS-based visualization tools
- ArcIMS- ArcGIS via Citrix (runs on server, no desktop
installation)
13
Spatial
•Spatial data is managed using:– Oracle 10G Enterprise (10.1.2)
Geodatabase– ESRI ArcSDE (Spatial Database
Engine) V9.1 – Separate schema for each regional
State Plane Coordinate System– All schema use NAD 83
•Identified standard layers for ER
14
15
Components of NIRIS
Tabular SpatialNIRIS Spatial DBNIRIS Database
Audit SchemaX – Y CoordinatesProjectionM&A Schema RefLocation Type
Location_CoordinatesLocation_Alias
NIRIS
Changes Database Link
NW Schema- ER Points
SW Schema- ER Points
NE Schema- ER Points
South Schema- ER Points
LANT Schema- ER Points
PAC Schema- ER Points
Admin Schema SDE SchemaJava & PL/SQL
Procedure: Update, Insert, Delete ER
PointsInfrastructure
Job Scheduler
Doc. Mgmt EDMS
16
Schedule
• Deployment in process•Training planned•Most FECs have legacy data staged•Historic data loading ongoing•Continue to add end user tools
17
Since Last JSEMS
•Migrated Servers to NMCI–Made changes to meet DoD IT security rules
•Central servers tested and ready•Just cleaned out beta test data
•Set up Geospatial components•Geodatabases
•Started work on Environmental Document Management System
18
Interoperability
19
Interoperability
•Key ID fields from other enterprise databases
•Centralized, Uniform database•SDS compliance
–Federal CADD/GIS Center’s Spatial Data Standard
–Not an easy decision: Big commitment, big investment!
• SDS is not normalized (duplication)• Legacy database mapping issues
20
SDS
•SDS compliant at “Experienced” level•Added fields to SDS structures (to make legacy data fit)
•Maximized database query efficiency by minimizing table ‘joins’
•Was partnering with CADD/GIS Center and provided data model to them, continue to work with DISDI
21
Interoperability
Interoperability allows:• Sharing, leveraging of data
– Regional Shore Installation Management System (RSIMS)
– NIRIS provides ER data e.g., IR site boundaries, Land Use Controls
– RSIMS provides base boundaries, buildings– NIRIS does not duplicate data in RSIMS
•Roll up of ER program data– GeoReadiness Repository