Using the Spatial Database Engine to develop a FEMA friendly Database and Asset Management Tool José Maria Guzmán, PE February 2009 GAFM 4th Annual Technical Conference Columbus, GA

Outline Typical Datasets involved in Mapping and Stormwater Management Efforts SDE Basics SDE Benefits during the project development Ultimate SDE benefits to the City Integration with common Asset Management Tools Acknowledgments: Erin Hardin, Stan Plante, Joseph Ridge.

FEMA Mapping and Stormwater Master Plans Require a significant ifi amount of data Data is stored and managed in GIS: Terrain Information (LiDAR) Survey Base map (political, transportation, topography, hydrography) Model Data (GEO-RAS, SWMM, Other) DFIRM Databases Data must comply with current FEMA data capture standards

Many Cities are implementing a WEB portal to disseminate information Common data sets include: Parcels, Streets, Aerial Images, Flood zones, zoning, etc. The results of mapping projects and stormwater t master plans can also be served through a web portal Portal is very instrumental in the public outreach portion of the FEMA MapMod program

Why Working on the SDE? Recent project teams faced new challenges: Multiple staff were using the same datasets Staff were creating their own version of the data while working in a particular sub-watershed Work completed in one sub-basin basin affected adjacent areas No consistency among different versions

SDE Basics SDE = Spatial Database Engine Works as an extra level between ee the edataa and ESRI ArcMap One dataset with multiple versions Each user has its own version of the data Data is tracked in all versions, and it is possible to resolve conflicts (by the users or a designated administrator) ArcGIS ArcGIS ArcGIS SDE SQL Database

SDE Basics (2) Single database managed in SQL Each user logs into the SDE The user posts and reconciles his/her version of the dataset t back to the DEFAULT The administrator can track the progress of individual versions Backup performed on all versions

SDE drawbacks Connection speed for staff in remote offices In order to perform basic database management it is necessary to disconnect all the users s Changes to the structure of the database are managed only by the administrator and affect all users License and server cost IT Staff required for initial installation and maintenance

Water Resources Datasets included in our SDE Major basins and sub-basins basins Runoff flow paths Model Nodes, Links, Cross Sections Field Survey Structures (Culverts, bridges, channels) NPDES Survey (inlets, end walls, pipes) Geocoded Flooding Complaints Soils and land use Topographic contours and TINs Roadways (evacuation routes) FEMA flood zones

The SDE allows a Collaborative Watershed Data Management Through the SDE staff can work on simultaneous tasks using the same data An administrator ensures that conflicts are resolved Applications during project development: Hydrology Hydraulics Mapping Capital Improvement Projects Evaluation

Hydrologic Modeling Tributary areas of sub-basins basins are delineated by different modelers Changes in shared boundaries are identified as conflicts By having a single dataset, t the administrator can run topology checks to avoid slivers.

Hydraulic Modeling One database summarizes the ongoing work in multiple sub-basinsbasins Development of an asset management database Data agreement between several departments: planning, engineering, operation and maintenance. Data used for multiple purposes: Modeling FEMA database

Other GIS Tools Are Still Available Because the SDE is not altering the ArcGIS capabilities, other common GIS tools are being used, such as: ArcHydro ArcScene

Flood Mapping Model information used by the mapping professionals is the same one used by the modelers e Many databases requested by FEMA are already in the database: GENSTRUCT, Manning s N, Stream Center lines DFIRM database can be organized and structured on the SDE to ensure access to the information

Evaluation of Capital Improvement Projects Identification of locations with existing survey Access to the planning model schematic Determining tributary areas to capital improvement projects

SDE applications once the project development is complete City staff from multiple departments will access the information: Planning, Engineering, Operation and Maintenance, Public Data Dissemination Identifying discrepancies in model data with respect to actual field measurements Expansion of the current database to create an asset management tool Queries from field staff

Upcoming field applications Handheld computers could be used to access information in the field Other alternative technologies involve a red line program, or the use of digital pens. Wireless Networks can provide instant access to information in the field SDE benefits to the City Accessibility Up to date information Work Order Statistics up-to-date

Integration with Common Asset Management Tools Most utilities are developing asset management tools for their water, sewer and electric networks Stormwater only applications there are off- shelf that can be used, and integrated with other asset management tools The user should consider including important attributes that will become critical at the time of converting the GIS database to an asset management tool: Numeric condition field (1-5) Criticality (1-5) Asset Cost Design life

Summary The SDE has proven to be a great tool in assisting the collaborative use of information. The SDE enabled several staff to work on the same datasets simultaneously. The SDE enables the owner to disseminate data across several department t while maintaining control over its content Efforts conducted in mapping and stormwater projects can work synchronize with asset management tool efforts in other areas such as solid waste, power, water and sewer

Using the Spatial Database Engine to develop a FEMA friendly Database and Asset Management Tool José Maria Guzmán, PE guzmanjm@cdm.com February 2009 GAFM 4th Annual Technical Conference Columbus, GA