Geotechnical Data Management in the Army Corps

2,638 views

Published on

The described collaborative approach, innovative, market-leading, proven base technology and combined experience will provide the foundation for effective geotechnical decision support, leading to improved geotechnical design.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,638
On SlideShare
0
From Embeds
0
Number of Embeds
72
Actions
Shares
0
Downloads
97
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Geotechnical Data Management in the Army Corps

  1. 1. Integrated Geotechnical Data Management for Working Engineers and Geologists Scot D. Weaver Geospatial Technology Symposium & Exhibition EarthSoft, Inc. 17-19 August 2004 Paul D. Madison San Antonio, Texas St. Paul District, USACE
  2. 2. Agenda • Geotechnical Data Management • U.S. Army Corps of Engineers Approach • Example Implementation • Benefits • Conclusion
  3. 3. Geotechnical Data Management • Volume of Data • Inability/Difficulty in Accessing Data • Incompatibility of Existing Systems • Impact on Geotechnical Design
  4. 4. Geotechnical Data Management Volume of Data Quote from state agency: “Some project datasets filled thirty or more boxes.…When the case was closed, as there was no practical way to archive the data, it was all thrown away….”
  5. 5. Geotechnical Data Management Volume of Data Quote from state agency: “…Without the ability to manage data electronically, the quality of work suffered and hundreds of millions of data were lost forever.”
  6. 6. Geotechnical Data Management Inability/Difficulty in Accessing Data Quote from an engineer in the US Army Corps of Engineers: “The department is truly archaic when dealing with records. It is my understanding that the District only uses hard copies of log and testing data. The information is stored in warehouses at different places throughout Omaha.”
  7. 7. Geotechnical Data Management Inability/Difficulty in Accessing Data What can this result in? In one Army Corps District, tens of thousands of dollars were spent unnecessarily on drilling new boreholes within meters of previous drilling sites, simply because they didn‟t know that the data existed.
  8. 8. Geotechnical Data Management Incompatibility of Existing Systems • Legacy Systems • New data acquisition systems • Observation/field notebook • Real-time monitoring • Tabular field data entry (EDDs) • Electronic field data entry forms • Instrumentation/telemetry • New data transfer protocols (and old devices) • Data “hostage” scenarios (proprietary formats)
  9. 9. Geotechnical Data Management Impact on Geotechnical Design Geotechnical data that is not easily accessible impedes the design process, increases overall costs and may reduce the overall quality of products. If approached correctly, geotechnical data management can be the cornerstone and foundation for effective decision support and risk management.
  10. 10. U.S. Army Corps of Engineers Approach • Data management is done in varies ways throughout the Geotechnical Community – Some Good, Some Bad! • The Corps Geotechnical Community is very similar to their peers in other agencies. • There is not a data management process that is accepted by everyone and It is difficult to use geotechnical data with both CADD and GIS software. • GTFAC initiated a Geotech Dbase Project
  11. 11. U.S. Army Corps of Engineers Approach Tasks • Identify Geotechnical Data Structures and Usage • Define Geotechnical Database Schema • Identify Data Input Streams and Output (Reports/Logs) • Define Electronic Data Deliverable (EDD) Formats • Develop Intelligent Data Entry Forms • Develop Application Software…
  12. 12. U.S. Army Corps of Engineers Approach Data Structure • In 2003, the Geotechnical Field Action CADD group funded EarthSoft for Phase 1 of the Project • Objective: “Develop an enterprise-wide geotechnical database” • EarthSoft surveyed 17 US Army Corps of Engineer District to determine • the type and extent of geotechnical data of concern • existing tools utilized for geotechnical data management and analysis
  13. 13. U.S. Army Corps of Engineers Approach Data Structure • In 2003, the Geotechnical Field Action CADD group funded EarthSoft for Phase 1 of the Project • Objective: “Develop an enterprise-wide geotechnical database” • EarthSoft surveyed 17 US Army Corps of Engineer Districts to determine • the type and extent of geotechnical data of concern • existing tools utilized for geotechnical data management and analysis
  14. 14. U.S. Army Corps of Engineers Approach Data Structure • In 2003, the Geotechnical Field Action CADD group funded EarthSoft for Phase 1 of the Project • Objective: “Develop an enterprise-wide geotechnical database” • EarthSoft surveyed 17 US Army Corps of Engineer Districts to determine • the type and extent of geotechnical data of concern • existing tools utilized for geotechnical data management and analysis
  15. 15. U.S. Army Corps of Engineers Approach Geotechnical Database Schema As a result of the survey an expanded data structure has been proposed that encompasses most geotechnical data elements currently used within the Corps. • Geotechnical, Geologic, Non-Geotechnical Tables • 53 tables, over 600 fields • Relational structure
  16. 16. U.S. Army Corps of Engineers Approach Geotechnical Database Schema As a result of the survey an expanded data structure has been proposed that encompasses most geotechnical data elements currently used within the Corps. • Definition includes field • name • validation • type • description • length (if applicable) • aliases, abbreviations • required • example • key field
  17. 17. U.S. Army Corps of Engineers Approach Geotechnical Database Schema Geotechnical Tables Defined by EarthSoft Static material properties, water content, density, Atterberg, sieve, hydrometer, specific gravity, compaction, UU/CU, compression, direct shear, permeability, sedimentation, elastic modulus, downhole point (CPT), … Geologic Tables Defined by EarthSoft Lithology, stratigraphy, sample, sample parameter, drill activity, drill parameter, … Non-Geotechnical Tables Defined by EarthSoft Project, location, location parameter, coordinate, well, well construction, water level, water table, company, …
  18. 18. U.S. Army Corps of Engineers Approach Geotechnical Database Schema Geotechnical Tables Defined by EarthSoft Static material properties, water content, density, Atterberg, sieve, hydrometer, specific gravity, compaction, UU/CU, compression, direct shear, permeability, sedimentation, elastic modulus, downhole point (CPT), … Geologic Tables Defined by EarthSoft Lithology, stratigraphy, sample, sample parameter, drill activity, drill parameter, … Non-Geotechnical Tables Defined by EarthSoft Project, location, location parameter, coordinate, well, well construction, water level, water table, company, …
  19. 19. U.S. Army Corps of Engineers Approach Geotechnical Database Schema Geotechnical Tables Defined by EarthSoft Static material properties, water content, density, Atterberg, sieve, hydrometer, specific gravity, compaction, UU/CU, compression, direct shear, permeability, sedimentation, elastic modulus, downhole point (CPT), … Geologic Tables Defined by EarthSoft Lithology, stratigraphy, sample, sample parameter, drill activity, drill parameter, … Non-Geotechnical Tables Defined by EarthSoft Project, location, location parameter, coordinate, well, well construction, water level, water table, company, …
  20. 20. U.S. Army Corps of Engineers Approach Geotechnical Database Schema—SDSFIE Database Schema must be compatible with SDSFIE. What is SDSFIE? Spatial Data Standard for Facilities, Infrastructure, and Environment (SDSFIE) • Set of graphic and non-graphic standards for GIS implementation • The only non-proprietary data content standard designed for use with predominant commercial GIS, CADD, and database software
  21. 21. U.S. Army Corps of Engineers Approach Geotechnical Database Schema—SDSFIE Database Schema must be compatible with SDSFIE. What is SDSFIE? Spatial Data Standard for Facilities, Infrastructure, and Environment (SDSFIE) • Set of graphic and non-graphic standards for GIS implementation • The only non-proprietary data content standard designed for use with predominant commercial GIS, CADD, and database software
  22. 22. U.S. Army Corps of Engineers Approach Geotechnical Database Schema—SDSFIE Database Schema must be compatible with SDSFIE. What is SDSFIE? Spatial Data Standard for Facilities, Infrastructure, and Environment (SDSFIE) • Set of graphic and non-graphic standards for GIS implementation • The only non-proprietary data content standard designed for use with predominant commercial GIS, CADD, and database software
  23. 23. U.S. Army Corps of Engineers Approach Geotechnical Database Schema—SDSFIE Spatial Data Standard for Facilities, Infrastructure, and Environment (SDSFIE) • Standard for GIS implementation throughout the Department of Defense • de facto standard for GIS implementation in many federal, state, and local agencies; public utilities; and private industry However…
  24. 24. U.S. Army Corps of Engineers Approach Geotechnical Database Schema—SDSFIE Spatial Data Standard for Facilities, Infrastructure, and Environment (SDSFIE) • Standard for GIS implementation throughout the Department of Defense • de facto standard for GIS implementation in many federal, state, and local agencies; public utilities; and private industry However…
  25. 25. U.S. Army Corps of Engineers Approach Geotechnical Database Schema—SDSFIE Spatial Data Standard for Facilities, Infrastructure, and Environment (SDSFIE) …while the SDSFIE is great with 2D features like buildings, roads, types vegetation, it is lacking in support of subsurface features like … … consolidation tests.
  26. 26. U.S. Army Corps of Engineers Approach Geotechnical Database Schema—SDSFIE Spatial Data Standard for Facilities, Infrastructure, and Environment (SDSFIE) The geotechnical attributes and domain tables defined in the data structure will be added to the next version of SDSFIE.
  27. 27. U.S. Army Corps of Engineers Approach Geotechnical Database Schema Ultimate goal of the Project is to produce an enterprise Geotechnical Data Management System that is … • Easy to enter, edit, retrieve subsurface/laboratory data • Interface with GIS, engineering design applications • Support production of boring logs for contract documents
  28. 28. U.S. Army Corps of Engineers Approach Geotechnical Database Schema Ultimate goal of the Project is to produce an enterprise Geotechnical Data Management System • Anticipated implementation: • Army 80 installations • Army Corps 41 District offices • Navy 110 installations • Air Force 110 installations • Other Federal agencies 29
  29. 29. Example Implementation Scope The proposed system includes not only support for field and laboratory rock and soils data, but also: • Geohazard Inventories • Document Management • Research & Planning • Instrumentation & Monitoring • Archived Data and Documents • Emergency Response • Construction • Structures • Highway Maintenance
  30. 30. Example Implementation Potential Data Input Streams • Import from existing databases, such as gINT • Intelligent Forms • Electronic Data Deliverables (EDDs) • Field data entry/ collection • Manual data entry
  31. 31. Example Implementation Potential Data Output/Exports • Borehole Logs • Lab Data (grain size dist., ternary diagrams) • Design • Predictive Models/Simulation
  32. 32. Example Implementation Define Electronic Data Deliverable (EDD) Formats • Establish formats for loading laboratory and field data • Define checking constraints (vocabulary, limits, etc.) • EDD formats are free, removing barriers to their use • EDD formats can be enforced by agencies with the freely- distributed EQuIS Data Processor (EDP)
  33. 33. Example Implementation Data Entry and Importing The EQuIS Data Processor (EDP) enforces EDD formats, rules
  34. 34. Example Implementation Data Entry and Importing • EDP is available as standalone, Windows application or Enterprise web application • Both versions use the same code • „Closed Loop‟
  35. 35. Example Implementation Data Entry and Importing Standalone Windows application ensures privacy of data submitter
  36. 36. Example Implementation Data Entry and Importing • Enterprise EDP for high-volume data submission programs Supports: • Automated Workflow • Checking, Processing • Rejection Notices • Acceptance Notices • Data Screening
  37. 37. Example Implementation Data Entry and Importing Intelligent Forms: • Data checked on entry • Can be reproduced upon paper • Automatically creates EDDs
  38. 38. Example Implementation Data Entry and Importing Integration/Import from gINT Databases EQuIS Geotechnical Data Management System
  39. 39. Example Implementation Data Entry and Importing ArcPad integration with handheld device for incorporation of GPS data
  40. 40. Example Implementation Document Management Integration with Falcon/DMS
  41. 41. Example Implementation Document Management F F A A L L EQuIS C C Geotechnical O O Data N N / Management / System D D M M S S Manages versions of all Manages versions of all INCOMING DATA OUTGOING DATA
  42. 42. Example Implementation Geotechnical Reports/Graphics Integration with gINT: Borehole Log EQuIS Geotechnical Data Management System
  43. 43. Example Implementation EQuIS for ArcGIS/ArcIMS • Open GIS Consortium (OGC) Compliant • Support Dynamic Linear Segmentation • Both thin-client (i.e. ArcIMS) and thick-client (i.e. ArcGIS) solutions • Conventionally, GIS is used as an analysis tool. EQuIS also uses GIS as a user interface: • data selection • posting • viewing • integration with other modeling and analysis tools
  44. 44. Example Implementation EQuIS Information Agent (“Push” Reporting) • Reports (or graphs, or logs) delivered automatically via email or web portal (dashboard) • May be event-driven, i.e. “a new borehole has been entered into the database so send me a gINT log” Or • May be scheduled, i.e. “every Friday at 1 p.m. give me a report of all drilling activity for that week”
  45. 45. Example Implementation EQuIS Information Agent (“Push” Reporting) 1. Report scheduled 2. Report generated when condition is met
  46. 46. Benefits of System Implementation • Reduces costs associated with project design • Requires the establishment of electronic standards for geotechnical data (soil, rock, water, …) • Provides the foundation for data sharing
  47. 47. Benefits of Commercial-Off-the-Shelf (COTS) Software • Built on commercial EQuIS system: an expansion of existing tools and technologies, not an invention • Open System…easily expanded, easily accessed. • Supportable inexpensively.
  48. 48. Benefits of Collaboration • Lessens the significance of political boundaries • Improves cooperation between state agencies and between state agencies and federal oversight agencies • Consistent with national initiative to support information and technology transfer
  49. 49. Conclusion The described collaborative approach, innovative, market- leading, proven base technology and combined experience will provide the foundation for effective geotechnical decision support, leading to improved geotechnical design. The EQuIS Geotechnical Data Management System described is the anticipated course of action for the Ohio Department of Transportation (ODOT).
  50. 50. Thank You!

×