1 / 70

FDOT’s Web Interface

FDOT’s Web Interface. Presented by: Paul Herring Florida DOT, Estimates Office paul.herring@dot.state.fl.us. Outline. What is FDOT’s Web Interface? Why did we need an Interface? Benefits of the Interface Steps in loading data User Roles Demonstration. What is FDOT’s Web Interface?.

bowie
Télécharger la présentation

FDOT’s Web Interface

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. FDOT’sWeb Interface Presented by: Paul Herring Florida DOT, Estimates Office paul.herring@dot.state.fl.us

  2. Outline • What is FDOT’s Web Interface? • Why did we need an Interface? • Benefits of the Interface • Steps in loading data • User Roles • Demonstration

  3. What is FDOT’sWeb Interface? • A simple application that allows designers to: • easily input pay items and quantities into the PES Oracle database • generate a variety of reports…without using TRNS*PORT PES software!!!

  4. Why did FDOT needan Interface? • Accessibility • Confidentiality • Large number of users • Training

  5. Why did FDOT needan Interface? • Accessibilityfor external users had to be considered. • Web Interface is an internet application, accessed through FDOT website. • Accessible to users with proper authority and adequate roles.

  6. Why did FDOT needan Interface? • Confidentiality • For legal reasons, only Estimates staff are allowed access to estimates. • PES/CES software would not provide this security.

  7. Why did FDOT needan Interface? • Large Number of Users– • Approximately 800 consultant designers working outside FDOT. • High turnover rate for external users. • Training would be an ongoing issue.

  8. Why did FDOT needan Interface? • Training • PES would have required an estimated12 – 16 hours of hands-on training: • Most of FDOT’s training facilities accommodate a maximum of 12-14 students. • For 800 students, approx. 125 days of training would be required statewide.

  9. Benefits ofFDOT Web Interface • Training time reduced: • Auditorium-style training was accomplished in2 hour sessions, with up to 150 students each; • Estimated $68,000 savings; • Material cost was reduced considerably. • Security • Intuitive, user-friendly • Windows features – buttons, check boxes, drop-down lists, etc.

  10. Benefits ofFDOT Web Interface • Our users LIKE IT !!!! • User problems are virtually non-existent!!

  11. 7 Simple Steps in Loading Data: • Step 1 - Transfer Project Data from FM (Financial Management System) to TP PES. • Step 2 - Set Control/Pass control to Designer. • Step 3 - Designer locates project in project menu in Designer Interface.

  12. 7 Simple Steps in Loading Data: • Step 4 – Customizes categories to project. • Step 5 – Loads limited category header information.*

  13. 7 Simple Steps in Loading Data: • Step 6 – Load Items & Quantities: • Validation is made with Master Pay Item List on items the designer is attempting to load. • Comparison is made with the Letting Date and the date an item is to be valid or obsolete. • Immediate feedback if problem with item above.

  14. 7 Simple Steps in Loading Data: • Step 7 – Summary of Items & Quantities, 1 step process, then options to: • View on Screen • Save to File • Transfer to CADD File

  15. Access toWeb Interface • Controlled by District and Central Coordinators • Options available are directly related to a user’s function or role.

  16. User Roles • Florida has approx. 65 roles for PES and CES • For today’s demo, we will look at – Designer, Public and Estimator roles

  17. User Roles • Designer • Designer Interface • Project Edit Report • Master Pay Item List • Summary of Pay Items • Project • Proposal • Pay Item Average Unit Cost • Bridge History Report

  18. User Roles • Public • Same access as Designer, but READ ONLY • Essentially a Reviewer role • Estimator • Same access as Designer and Public, AND reports to assist in the preparation of estimates • Reports to aid in post-bid evaluations (customized for FDOT)

  19. Let’s Get Started!!

  20. Web Address: http://www3.dot.state.fl.us/trnsport2/

  21. Enter User ID Enter Password Login Screen

  22. Web Interface Menu

  23. Control Group Select View/Update

  24. Select Process Deletes Check Unwanted Categories

  25. Select Update

  26. Select Update Category Code Length Code Width Select Bridge Type 010175

  27. Pay Item Coding

  28. Click Process Items

  29. Resubmit Items Update Items and Quantities

  30. Select Return To Category

  31. Click Add Category Click Copy Selected Category

  32. Select Update ?

  33. Enter Bridge ID Select Update Category

  34. Select Process Updates/Deletes Check UPD/DEL Items 700

  35. Click Return To Project

  36. Select Update

  37. Update Stations Click Update Category

  38. Click Add New Items

  39. Enter Item #’s Enter Quantity Select Process Items

  40. Select Return to Category

  41. Select Items

  42. Enter Item #’s Enter Quantity Select Process Items

  43. Select Return To Category

  44. Click To Minimize

  45. Enter Project Number

  46. Summary

More Related