ODOT Geotechnical Management System: Drilling Request to GIS - August 2010

  • 512 views
Uploaded on

ODOT presentation from the 10th Annual Technical Forum (http://www.marshall.edu/cegas/geohazards/)

ODOT presentation from the 10th Annual Technical Forum (http://www.marshall.edu/cegas/geohazards/)

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
512
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
9
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Ohio DOT's Geotechnical Management System:Drilling Request to GIS
    Columbus, Ohio
    Thursday, August 5, 2010
    Scot D. Weaver, MSCE
    Vice-President and Co-Founder
  • 2.
  • 3. segue…Uses for DIGGS
    • Send data to others (lab, client, consultant, others)
    • 4. Receive data from others
    • 5. Internal for data flow (to different software programs, to different data bases)
    • 6. A key component of a geotechnical management system
  • Brief History of ODOT GeoMS
    • User Needs Interviews by GeoDecisions
    • 7. Centralized data repository
    • 8. Internal/external secure access
    • 9. Borehole logs
    • 10. Laboratory test data
    • 11. Technical application software
    • 12. Search, input, and export data
    • 13. GIS
  • Brief History of ODOT GeoMS
    • Document Management Assessment by tsaAdvet
    • 14. Hundreds of 1000’s of maps, plans, as-builts, …
    • 15. Hundreds of $M in value
  • Brief History of ODOT GeoMS
    • Detailed Assessment by EarthSoft…user survey
    • 16. 2/3 of data is collected on field sheet or notebook
    • 17. 96% of data shared by manual log sheets
    • 18. Almost 2/3 of archived data stored in boxes or warehouse
    • 19. Over 50% of respondents have lost valuable data
    • 20. 97%...important or absolutely necessary to share data
    • 21. 92% prepare, report, archive geotechnical data on paper
    • 22. 96% say it is important or absolutely necessary to store geotechnical data electronically
    • 23. Most commonly used lab data: particle size, moisture content, Atterberg
  • Brief History of ODOT GeoMS
    • Detailed Assessment by EarthSoft…user survey
    • 24. Results of survey allowed prioritization
    • 25. Phased implementation
    Geotechnical Management System
    Borehole
    Logging
    Instrumentation/
    Monitoring
    Geohazards
    Inventory
    Remediation
    Operations
    Pavement
    O&M
    Planning/
    Research
    GeoLIMS
    Structures
    Future…………………
    Geologic Site Mgmt
  • 26. Brief History of ODOT GeoMS
    • Detailed Assessment…user survey
    • 27. Phased implementation
    • 28. Borehole data
    • 29. Drilling data
    • 30. Laboratory test data
    • 31. Integration with Falcon
    • 32. Integration with ESRI GIS
    • 33. EarthSoft contracted to build GeoMS on top of EQuIS
    • 34. A “design/build” approach was adopted, which has proven to be a good thing
  • GeoMS Overview
    EQuIS
    GeoMS
  • 35. Brief History of ODOT GeoMS
  • 36. Brief History of ODOT GeoMS
    • Drilling Request System (DRS)
    • 37. Security: Centralized Authentication
    • 38. Enhanced field data collection with EDGE
    Borehole
    Logging
    Instrumentation/
    Monitoring
    Geohazards
    Inventory
    Remediation
    Operations
    Pavement
    O&M
    Planning/
    Research
    GeoLIMS
    Structures
    Future…………………
    Geologic Site Mgmt
    Login only once to each module
  • 39. GeoMS Overview
    Field Data Collection
    GeoMS
    (EQuIS)
    Monitoring/
    Instrumentation
    Laboratory Data
  • 40. GeoMS Overview
    • GeoMS Components
    • 41. EQuIS Schema (Oracle Database)
    • 42. EQuIS Professional
    • 43. EQuIS Enterprise
    • 44. EQuIS Data Processor (EDP)
    • 45. EQuIS Data Gathering Engine (EDGE)
    • 46. EQuIS Sample Planning Module (SPM)
  • GeoMS Overview
    EQuIS ENTERPRISE
    EQuIS PROFESSIONAL
    GeoMS
    Database
    • Manager, Auditor, Public
    • 47. Web browser (no install req.)
    • 48. Same database, same data
    • 49. Simple, quick, easy to use
    • 50. Automation
    • 51. Data manager, Scientist
    • 52. Windows app (installation)
    • 53. Data importing, editing
    • 54. Advanced analysis, modeling*
    • 55. Ultimate flexibility
    * May require additional third-party software
  • 56. Field Workflow
    • Consultant or ODOT field crew
    EQuIS Data Gathering Engine (EDGE)
    GeoMS
    EDP
    DIGGS EDD
    Emailed
  • 57. EDGE: Field Data Collection
    • What is EDGE?
    A collection of field tools designed to assist field technicians collect accurate and complete field data using the latest mobile computing technologies.
    • Why use EDGE?
    Reduce data entry errors in the field and easily prepare data for submission to the GDMS.
  • 58. EDGE: Field Data Collection
  • 59. EDGE: Field Data Collection
  • 60. EDGE: Field Data Collection
  • 61. EDGE: Field Data Collection
  • 62. EDGE: Field Data Collection
  • 63. EDGE: Field Data Collection
  • 64. EDGE: Field Data Collection
  • 65. EDGE: Field Data Collection
  • 66. EDGE: Field Data Collection
  • 67. Document Submission Workflow
    EDP
    EQuIS Data Gathering Engine (EDGE)
    GeoMS
    EDP
    DIGGS EDD
  • 68. 1. Data Packet Created
    Data submitter selects
    documents
    Data submitter* starts EDP
    *Data submitter may be consultant
    or engineer, typically person or
    company acquiring data
    Documents may include:
  • 2. Submitter Checks EDDs
    Will EDDs
    be included in
    this packet?
    ‘Sign and Submit’ creates Packet* and submits to GeoMS EDP
    NO
    EDDs
    Checked in EDP
    (Standalone)
    EDDs Correct?
    *Data and/or Documents
    YES
    YES
    EDDs are checked in the privacy of submitter’s office using Standalone EDP before creating packet for submission to the GeoMS
    NO
    Data may include:
    • Spreadsheets, text files
    • 76. Access databases
    • 77. DIGGS EDDs (XML)
    Correct, Recheck
  • 78. 3. Packet Submitted
    Email
    GeoMS
    (Enterprise)
    EDP
    EDP submits Packet
    via web service
    (Preferred Method)
    All Files
    Posted to
    Falcon
    Data
    Packet
    EDDs continue on to be checked by GeoMSEDP
    Web Upload
  • 79. 4. GeoMS Checks/Loads EDDs
    GeoMS
    Enterprise EDP
    EDDs Correct?
    GeoMS
    EQuIS
    YES;
    EDDs Accepted
    DIGGS EDDs
    NO;
    EDDs Rejected
    Automatic email notifications
    sent to users by GeoMS
  • 80. ODOT Workflow
    Borehole
    Logs
    Enterprise Drilling
    Request System
    EQuIS Data Gathering Engine (EDGE)
    Reports and
    Documents
    GeoMS
    EDP
    Visualization
    DIGGS EDD
    GIS
    .mdb
  • 81. EDP: Checking Data
    Visual classification does not match laboratory classification.
  • 82. EDP: Checking Data
    MISSING DATA!
  • 83. EDP: Checking Data
    Visual moisture does not match laboratory moisture.
  • 84. EDP: Checking Data
    Plastic limit (PL) should not be greater than 50.
  • 85. EDP: Checking Data
    Liquid limit (LL) should not be less than the plastic limit (PL).
  • 86. EDP: Checking Data
    Liquid limit (LL) should not be greater than 60.
  • 87. EDP: Checking Data
    Plasticity index (PI) should not be greater than 50.
  • 88. ODOT Workflow
    Borehole
    Logs
    Enterprise Drilling
    Request System
    EQuIS Data Gathering Engine (EDGE)
    Reports and
    Documents
    GeoMS
    EDP
    Visualization
    DIGGS EDD
    GIS
    .mdb
  • 89. GeoMS Output
  • 90. GeoMS Output
  • 91. GeoMS Output
  • 92. GeoMS Output
  • 93. Web GeoMS
  • 94. Web GeoMS
  • 95. Web GeoMS
  • 96. Web GeoMS
  • 97. Web GeoMS
  • 98. Web GeoMS
  • 99. Web GeoMS
  • 100. Web GeoMS
  • 101. Web GeoMS
  • 102. In Conclusion…
    Ohio DOT wants to develop a comprehensive geotechnical management system for the state, but does not want to “reinvent the wheel”
    • Ambitious undertaking
    • 103. Needs change, technology changes
    • 104. First phase nearing completion
    • 105. Still a lot of work to be done
    • 106. GeoMS “is envisioned and designed not only to meet the geotechnical needs of all units within ODOT, but to be used by all of the geotechnical community throughout Ohio and the surrounding areas”…becoming a reality.
  • Thank you!
    Questions?
    www.earthsoft.com
    info@earthsoft.com