Development of a Web Based Design, and Construction Bridge Substructure Database Mike McVay, Marc Hoit, Erica Hughes, Thai Nguyen, and Peter Lai.

Development of a Web Based Design, and Construction Bridge

Substructure Database Mike McVay, Marc Hoit,

Erica Hughes, Thai Nguyen, and Peter Lai

Need for Unified Data Access

• Most existing data is in scanned form or paper

• Many states developing Geotechnical Database– Access through internet– Most using XML for outputting data– Some efforts to standardize data representation

• TransXML, agsXML

• No unified schema• No transparent access from applications

Database Standardization Benefits• Savings from unified DB

– single entry of data– reusable data– QA/QC – allows for software verification– More accurate bids (using existing data)

• Time Reduction– Reduce data transfer time and re-keying

• Accessibility– Open standard– Web entry and retrieval (with security)

Current DB System• Data restricted by user security• Upload and retrieve through XML file

– Web App controls conversion to DB format– DB format is not seen by users or applications

• Application centric – general access• Developed to allow multiple XML standards• Browser access to view, update or retrieve in

Excel• Data controlled by designated user

– Add users, create projects and data

XML Data Interchange Process

• Database is application centered

• Repository for project data

• Designed for using data in decision process

• Acts as archive

• Security is table based and hierarchical– Access established by FDOT

• Built in ability for multiple XML standards

Application Centric Architecture• Applications directly

access data• API (DLL) callable

from any language• Security enforced for

all access

Excel File

Website

Database

PDAFB-Deep

User Authenticates

Access Levels for User are identified

View security section for more details

Excel Transfers XML

Data File

XML Example Code:…<Pile ID=“32”> <Driving> <Drv_Date>5/5/1987</Drv_Date> <R_Energy>16.2</R_Energy> </Driving></Pile>…

XML Data is Translated into

Database

•XML Tags are Parsed and the Data is entered into the appropriate tables as long as the User has the appropriate Access Levels to do so. •Any fields the User Does not have Access for will NOT be updated.

Extract or Submit any data fragment

Only data for which the user has security is available

Spreadsheet for Soil Property Access

Scroll between different Lab sets

Select pre-defined description items

Example As-Built Data Plot AsBuilt:

Static LoadTest

FB-Deep Pile Design Using API

API Requires User Login (secure)

Returned Data Tree Based on User Security

123A-45Finiancial_Number

3ProjectID

27BridgeID

Table: Bridges

123A-45Finiancial_Number

3ProjectID

27BridgeID

Table: Bridges

79180-3514Project_Number

Port Orange IntraCoastalProject_Name

3ProjectID

Table: Projects

79180-3514Project_Number

Port Orange IntraCoastalProject_Name

3ProjectID

Table: Projects

192J-21Finiancial_Number

3ProjectID

29BridgeID

Table: Bridges

192J-21Finiancial_Number

3ProjectID

29BridgeID

Table: Bridges

South PointWall_Name

3ProjectID

21Wall_ID

Table: Walls

South PointWall_Name

3ProjectID

21Wall_ID

Table: Walls

78.9DataPoint

21Wall_ID

6WT_ID

Table: Wall_Tests

78.9DataPoint

21Wall_ID

6WT_ID

Table: Wall_Tests

SW 134th St.Roadway_Name

3ProjectID

34RoadWay_ID

Table: Roadway

SW 134th St.Roadway_Name

3ProjectID

34RoadWay_ID

Table: Roadway

43.2DataPoint

34RoadWay_ID

14RT_ID

Table: Roadway_Tests

43.2DataPoint

34RoadWay_ID

14RT_ID

Table: Roadway_Tests

Possible Future Additions• Structure root is project• Currently:

– Bridge

– Subsurface (holes)

• Future possibilities:– Walls

– Roadways

– Site Data

– Schedule

Subsurface High Level Schema• Hole data includes:

– SPT, DMT, PMT, CPT

– Lab test data

1 - Project

2 - Subsurface

3 - Hole

4 - SPT

4 - CPT

4 - DMT

4 - PMT

4 - VST

4 – Lab_Rock

4 – Lab_Soil

Bridge Data High Level Schema• Project has multiple:

– Bridges, Piers, Piles/Shafts

– Test results

1 - Project

2 - Bridge

3 - Pier

4 - Pile

5 – Pile_Capacity

5 – Static_LT

5 - Osterberg

5 - Statnamic

5 – Driving_Info

5 – Driving_Analysis

4 - Shaft

5 – Section

5 – Shaft_Capacity

5 – Static_LT

5 - Osterberg

5 - Statnamic

5 – Hole_Info

Detailed High Level Schema

1 - Project

Name Project_Number Financial_Number Comment Base_Latitude Base_Longitude Base_Station Base_Offset

2 - Subsurface

3 - Hole

SI_Unit Hole_Name Latitude Longitude Station Offset GWT Ground_Elev x_Coordinate y_Coordinate

4 - SPT

Company SI_Unit Test_Date Report_Date SPT_Type Eft_Energy_Ratio Spoon_Inside Spoon_Outside Hammer_drop Hammer_weight Comment

5 - SPT_Data

Elev Depth Sample N Interval Color Soil USCS AASHTO Core_Length Note

4 - CPT

Company SI_Unit Test_Date Report_Date Ratio_a Ratio_b Cone_angle Rod_dia Cone_dia Comment

5 - CPT_Data

Elev Depth qc q2 fs u2 u0 Note

4 - DMT

Company SI_Unit Test_Date Report_Date Comment

5 - Zero_Reading

6 - Zero_Data

Depth DA DB Zm

5 - DMT_Data

Elev Depth Thrust A B C Note

4 - PMT

Company SI_Unit Test_Date Report_Date PMT_Type Test_Depth Comment Description Modulus At_Rest_po Limit_p1 Net_Limit_p1

5 - PMT_Data

Volume Pressure Note

4 - VST

Company SI_Unit Test_Date Report_Date VST_Type Comment

5 - VST_Data

Elev Depth Su Sr Muy Note

Table: Projects

ProjectID 3

Project_Name Port Orange IntraCoastal

Project_Number 79180-3514

Client FDOT

Consultant Sverdrup Corporation

Contractor Danis Industries Corporation

Comments There are no comments

Table: Bridges

BridgeID 27

Bridge_Name Port Orange Bridge

ProjectID 3

Finiancial_Number 123A-45

Latitude 135

Longitude 20

Station 221+10

Offset -11

State FL

County 50

Zipcode  

Client FDOT

Consultant Sverdrup Corporation

Contractor Danis Industries Corporation

PileShaft_Company Industrial Contracting Company (ICC)

PileTest_Company Schmertmann_Crapps, Inc.

Comments There are no comments

AsBuilt 1

AsBuiltID  

1 Project can have many Bridges

Data Structure - Example

Security Structure ExampleMultiple levels of approval and locking

Data Originator (Technician) Original data entry – Locks data as a sign off that data is complete

Sub-Contractor (Geotech Firm) Original data entry – Locks data as a sign off that data is complete

Contractor (Bridge Contractor) Original data entry – Locks data as a sign off that data is complete

Owner (FDOT Approver) Original data entry – Locks data as a sign off that data is complete

Level 0

Level 1

Level 2

Level 3

Construction Example

Data Originator (Driller, Lab Tech) Original data entry – Locks data as a sign off that data is complete

Sub-Contractor (Geotech Consultant) Original data entry – Locks data as a sign off that data is complete

Designer (Bridge Design Firm) Original data entry – Locks data as a sign off that data is complete

Owner (FDOT Approver) Original data entry – Locks data as a sign off that data is complete

Design Example

Data Security – Role BasedCan restrict access to table and/or individual data

•A User Account can have Access to Mutiple Projects, Bridges, Piles, etc.

•User can be assigned different Access Levels (AccessID) per Project/Bridge/Pile/etc.

This example shows UserID 34 has different Access Levels (AccessID) for 2 different Bridges of the same Project

Data SecurityUsers can have different security for each project

This example shows UserID 34 has different Access Levels (AccessID) for 2 different Bridges of the same Project

Summary

• Schema developed for Geotechnical Data• Database has security built into the design• Database can be expanded to add unlimited types

of projects (roadway, walls, slopes …)• XML interaction allows applications upload and

download• Scalability is handled through standard database

and web growth options