1. FDOT Database Training #2 May 3, 2010 Presented by Erica Hughes & Michael Faraone Bridge Software Institute University of Florida

2. Overview Part 1 – Initial Setup of Machines Part 1 – Initial Setup of Machines Part 2 – Database Hierarchy & Overview Part 2 – Database Hierarchy & Overview Part 3 – Uploading Data to Database from Excel Applications Part 3 – Uploading Data to Database from Excel Applications Lunch Lunch Part 4 – Review of Uploaded Data w/ CADD Drawing Part 4 – Review of Uploaded Data w/ CADD Drawing Part 5 – Locking Data by Submitter After Review Part 5 – Locking Data by Submitter After Review Part 6 – Application of FB-Deep Analysis Part 6 – Application of FB-Deep Analysis

3. Part 1: Initial Setup of Machines Training Requirements Training Requirements –Latest version of FB-Deep with 3.8 Database DLL –Excel Applications 2.02 for LabTest and Insitu Required Files & Presentation Handouts are available: Required Files & Presentation Handouts are available: –Located in the ‘Other Training’ section for 5/3/10 http://fdot.ce.ufl.edu/tutorials.html http://fdot.ce.ufl.edu/tutorials.html –CADD User Tutorial presentation by Michael Robertson is also on the tutorials page.

4. Part 2: Database Hierarchy & Overview Presented by Erica Hughes Why a Database? Why a Database? About Projects About Projects GeoTech Security Hierarchy GeoTech Security Hierarchy DGE Interface – creating projects, users, assigning security settings for user DGE Interface – creating projects, users, assigning security settings for user Security Access for Excel Applications Security Access for Excel Applications Project Hierarchy in Database Project Hierarchy in Database Naming Conventions Naming Conventions Protecting Your Data Protecting Your Data DGE Delegates DGE Delegates

5. Why a Database? A database provides the means to digitally store, read and write the geotechnical data. A database provides the means to digitally store, read and write the geotechnical data. One Time Entry of Data One Time Entry of Data –Allows quick access for an array of software applications. –Reduces chances for input errors. Promotes reuse of historical Insitu and Lab data on future projects. Promotes reuse of historical Insitu and Lab data on future projects. Monitor project progress. Monitor project progress.

6. About Projects Everything starts with a Project Everything starts with a Project Project’s unique identifier is called ‘Project Number’ Project’s unique identifier is called ‘Project Number’ Project Number generally coincides with FDOT’s Financial Project Number Project Number generally coincides with FDOT’s Financial Project Number

7. About Projects cntd. Project Administrators like District Geotech Engineers (DGEs) create the Project in the database system and create/assign user accounts Project Administrators like District Geotech Engineers (DGEs) create the Project in the database system and create/assign user accounts

8. GeoTech Security Hierarchy

9. How To: DGE Create Projects Log into DGE account (DGE accounts have Project creator permissions) http://fdot.ce.ufl.edu – Admin Interface Log into DGE account (DGE accounts have Project creator permissions) http://fdot.ce.ufl.edu – Admin Interface http://fdot.ce.ufl.edu Click the ‘Create Project’ button Click the ‘Create Project’ button Fill in required field, ‘Project Number’ which should coincide with the FDOT Financial Project Number Fill in required field, ‘Project Number’ which should coincide with the FDOT Financial Project Number Project Number must be unique and only used for 1 Project in the database Project Number must be unique and only used for 1 Project in the database

10. Main Interface for DGE Create New Projects Create New Users

11. Create Project Interface Corresponds to FDOT’s Financial Project Number Unique Identifier for the Project Will be used for all database submissions for the Project

12. Create New User Interface Unique Identifier for User Account Geotechs should use geo- prefix for new user accounts or an agreed upon prefix for your district to easily locate users.

13. New User Notified by Email The User will receive a notification of their new user account and their auto- generated password. The User will receive a notification of their new user account and their auto- generated password.

14. Assign User to Project After User is created, you can assign the New User to the Project you created earlier. After User is created, you can assign the New User to the Project you created earlier.

15. Assign User to Project You may locate the Project by ‘Project Number’ (top) or by ‘Project Name’ (bottom) You may locate the Project by ‘Project Number’ (top) or by ‘Project Name’ (bottom)

16. Assign User to Project Confirm the User Account you want to Assign to the Project. Existing users for the Project are listed in the top, new users are listed in the bottom section (the new account is auto-selected). Confirm the User Account you want to Assign to the Project. Existing users for the Project are listed in the top, new users are listed in the bottom section (the new account is auto-selected).

17. Assign User to Project Check each type of job role the user should be granted for the Project. Do not give a user access to Lab data if they will only be submitting Insitu (SPT/CPT/etc.) data. Check each type of job role the user should be granted for the Project. Do not give a user access to Lab data if they will only be submitting Insitu (SPT/CPT/etc.) data.

18. User Notified by Email User will be notified of their user account’s new security settings for the Project Number. User will be notified of their user account’s new security settings for the Project Number. The Admin will also receive a copy of the user’s email message as confirmation. The Admin will also receive a copy of the user’s email message as confirmation.

19. Security Access for Excel In order for Users to submit data using the Insitu Excel application, they will need to be assigned as ‘Insitu Poster’. In order for Users to submit data using the Insitu Excel application, they will need to be assigned as ‘Insitu Poster’. In order for Users to submit data using the Lab Test Excel application, they will need to be assigned as ‘Lab Rock Poster’ and ‘Lab Soil Poster’. In order for Users to submit data using the Lab Test Excel application, they will need to be assigned as ‘Lab Rock Poster’ and ‘Lab Soil Poster’.

20. Project Hierarchy

21. Naming Conventions Hole Name is the unique identifier for Borings/Holes. Hole Name is the unique identifier for Borings/Holes. Hole Name: B1   B-1 they would be submitted as different Holes in the database. Hole Name: B1   B-1 they would be submitted as different Holes in the database. Make sure to know your Project’s naming conventions in order for boring information to be submitted correctly. Make sure to know your Project’s naming conventions in order for boring information to be submitted correctly.

22. Protect Your Data Multiple users can submit to the same Hole if they have the appropriate permissions. Multiple users can submit to the same Hole if they have the appropriate permissions. Once the Boring data is complete, the Hole should be locked by one of the submitters to prevent changes. The last person to submit a portion of the data (ex: SPT) will be recorded as the Submitter for the data. Once the Boring data is complete, the Hole should be locked by one of the submitters to prevent changes. The last person to submit a portion of the data (ex: SPT) will be recorded as the Submitter for the data. If the Hole is locked, no submissions can be made to any of the Hole’s nodes (ex: Lab Rock). If the Hole is locked, no submissions can be made to any of the Hole’s nodes (ex: Lab Rock).

23. DGE Delegates DGEs also have the ability to assign a user account to the DGE Delegate security role. DGEs also have the ability to assign a user account to the DGE Delegate security role. DGE Delegates act as backup for the DGE when the DGE is not available. DGE Delegates act as backup for the DGE when the DGE is not available. DGE Delegates have the same ability to assign/create user accounts and approve data as the DGE but do not have access to create new Projects. DGE Delegates have the same ability to assign/create user accounts and approve data as the DGE but do not have access to create new Projects.

24. Questions?

25. Part 3: Uploading Data to Database from Excel Applications Overview of Excel Application Overview of Excel Application –Entering data into application –Uploading to Database using DLL & Review of Log –Downloading from Database using DLL for Review Credentials to Use for Test Submission Credentials to Use for Test Submission –User: test-user1 –Password: geotech –Project-Number: 000000-0-00-00 –Hole Name: First Initial and Last Name (ex: jdoe) Review of Data Types Review of Data Types –Insitu Data – SPT & CPT –Lab Data – Rock & Soil Presented by Mike Faraone

26. Lunch Break Next session starts 1:10pm. Next session starts 1:10pm.

27. Part 4: Review of Uploaded Data with CADD Drawing Downloading XML using Web Interface Downloading XML using Web Interface Generating boring log with Microstation Generating boring log with Microstation View Michael Robertson’s presentation online: http://fdot.ce.ufl.edu/tutorials.html View Michael Robertson’s presentation online: http://fdot.ce.ufl.edu/tutorials.htmlhttp://fdot.ce.ufl.edu/tutorials.html Compare Excel Data to Drawing Compare Excel Data to Drawing Two Scenarios for Drawing Two Scenarios for Drawing –top of boring elev. = ground surface elev. –top of boring elev.  ground surface elev. Presented by Mike Faraone

28. Part 5: Locking Data by Submitter After Review Importance of Locking Your Data Importance of Locking Your Data Reviewing XML Online Reviewing XML Online Accessing Locking Interface Accessing Locking Interface Levels of Locking Levels of Locking Locking Database Hierarchy Locking Database Hierarchy Notifications of Locking Notifications of Locking Presented by Erica Hughes

29. Why You NEED to Lock Prevent your data from being overwritten by others Prevent your data from being overwritten by others Allows the data to be reviewed and verified at different levels Allows the data to be reviewed and verified at different levels

30. Reviewing Data Using Web Interface Begin by viewing your XML Tree

31. Your XML Tree Shows the XML for the projects you are authorized to view. Shows the XML for the projects you are authorized to view. Only a skeleton version of your data will be available until you select a node. Only a skeleton version of your data will be available until you select a node.

32. Selecting Data to Lock Select Table Results First select ‘Table Results’ First select ‘Table Results’ Then select a node to lock from XML Then select a node to lock from XML Below we are choosing to Lock Hole B-3 Below we are choosing to Lock Hole B-3

33. Accessing Locking Interface View Your Table File A table file is generated to lock the data. A table file is generated to lock the data. Open the link to review and lock data node. Open the link to review and lock data node.

34. The Table File View Enables you to edit values for unlocked data Enables you to edit values for unlocked data All locks are applied using this view only All locks are applied using this view only

35. Levels of Locking Two levels of locking used currently for boring information: Two levels of locking used currently for boring information: –Submitter –District/DGE Once submitter locks the data it cannot be overwritten. Once submitter locks the data it cannot be overwritten. Only the Submitter that Locked the data can Un-Lock the data. Only the Submitter that Locked the data can Un-Lock the data. After District locks are placed, no submitter can update the data. After District locks are placed, no submitter can update the data.

36. Locking Hierarchy When you lock a node, all subsequent children nodes will automatically be locked from editing. When you lock a node, all subsequent children nodes will automatically be locked from editing. User Locks Hole SPT Locked Automatically and not able to be updated by any submitter

37. Locking Interface Submitter chooses ‘Lock Data’ after review DGE Approval

38. Confirm Locking/Changes Provides additional security Provides additional security Review Updates Review Updates Enter your password and confirm. Enter your password and confirm.

39. Email Notifications The DGE will be notified when the data is locked by the submitter. The DGE will be notified when the data is locked by the submitter.

40. Log Results After Locking You will see confirmation that your lock was successful in the Log Results You will see confirmation that your lock was successful in the Log Results You will also see which users (DGEs) were sent notification of your lock. You will also see which users (DGEs) were sent notification of your lock.

41. Questions?

42. Part 6: Application of FB-Deep Analysis Driven Pile Analysis Driven Pile Analysis Downloading SPT Boring Data into FB- Deep Downloading SPT Boring Data into FB- Deep Modifying Downloaded Data to Create Proper FB-Deep Input File Modifying Downloaded Data to Create Proper FB-Deep Input File Uploading FB-Deep Boring Logs Uploading FB-Deep Boring Logs Presented by Mike Faraone

43. Bridge Software Institute Additional Training Materials: http://fdot.ce.ufl.edu/tutorials.html Technical Support: techsupport@fdot.ce.ufl.edu techsupport@fdot.ce.ufl.edu Bridge Software Institute