Integrated Geotechnical Data Management for Working Engineers and

Geologists

Geospatial Technology Symposium & Exhibition

17-19 August 2004

San Antonio, Texas

Scot D. Weaver

EarthSoft, Inc.

Paul D. Madison

St. Paul District, USACE

Agenda

• Geotechnical Data Management • U.S. Army Corps of Engineers Approach• Example Implementation• Benefits• Conclusion

Geotechnical Data Management

• Volume of Data• Inability/Difficulty in Accessing Data• Incompatibility of Existing Systems• Impact on Geotechnical Design

Geotechnical Data ManagementVolume of Data

“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….”

Quote from state agency:

Geotechnical Data ManagementVolume of Data

“…Without the ability to manage data electronically, the quality of work suffered and hundreds of millions of data were lost forever.”

Quote from state agency:

Geotechnical Data Management Inability/Difficulty in Accessing Data

District only uses hard copies of log and testing data.  The information is stored in warehouses at different places throughout Omaha.”

“The department is truly archaic when dealing with records.  It is my understanding that the

Quote from an engineer in the US Army Corps of Engineers:

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.

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)

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.

• 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

U.S. Army Corps of Engineers Approach

• 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…

U.S. Army Corps of Engineers Approach

Tasks

• 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

U.S. Army Corps of Engineers Approach

Data Structure

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

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

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

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• type• length (if applicable)• required • key field

• validation• description• aliases, abbreviations• example

U.S. Army Corps of Engineers Approach

Geotechnical Database Schema

Geotechnical Tables Defined by EarthSoftStatic 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 EarthSoftLithology, stratigraphy, sample, sample parameter, drill activity, drill parameter, …

Non-Geotechnical Tables Defined by EarthSoftProject, location, location parameter, coordinate, well, well construction, water level, water table, company, …

U.S. Army Corps of Engineers Approach

Geotechnical Database Schema

Geotechnical Tables Defined by EarthSoftStatic 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 EarthSoftLithology, stratigraphy, sample, sample parameter, drill activity, drill parameter, …

Non-Geotechnical Tables Defined by EarthSoftProject, location, location parameter, coordinate, well, well construction, water level, water table, company, …

U.S. Army Corps of Engineers Approach

Geotechnical Database Schema

Geotechnical Tables Defined by EarthSoftStatic 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 EarthSoftLithology, stratigraphy, sample, sample parameter, drill activity, drill parameter, …

Non-Geotechnical Tables Defined by EarthSoftProject, location, location parameter, coordinate, well, well construction, water level, water table, company, …

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

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

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

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…

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…

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.

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.

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

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

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

Example Implementation Scope

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

Example Implementation Potential Data Output/Exports

• Borehole Logs

• Lab Data (grain size dist., ternary diagrams)

• Design

• Predictive Models/Simulation

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)

Example Implementation Data Entry and Importing

The EQuIS Data Processor (EDP) enforces EDD formats, rules

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’

Example Implementation Data Entry and Importing

Standalone Windows application ensures privacy of data submitter

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

Example Implementation Data Entry and Importing

Intelligent Forms:

• Data checked on entry

• Can be reproduced upon paper

• Automatically creates EDDs

Example Implementation Data Entry and Importing

Integration/Import from gINT Databases

EQuISGeotechnical

DataManagement

System

Example Implementation Data Entry and Importing

ArcPad integration with handheld device for incorporation of GPS data

Example Implementation Document Management

Integration with Falcon/DMS

EQuISGeotechnical

DataManagement

System

Example Implementation Document Management

Manages versions of all INCOMING DATA

Manages versions of all OUTGOING DATA

FALCON/DMS

FALCON/DMS

Example Implementation Geotechnical Reports/Graphics

Integration with gINT:Borehole Log

EQuISGeotechnical

DataManagement

System

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

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”

Example Implementation EQuIS Information Agent (“Push” Reporting)

1. Report scheduled

2. Report generated when condition is met

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

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.

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

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

Thank You!