For those of us involved in the SUE (Subsurface Utility Engineering) profession… Illinois DOT has included the following contract language in their Scope of Work: “Subsurface Utility Engineering (SUE) standards referred to within this scope of work are in accordance with the ASCE/UESI/CI 38-22 Standard Guideline for Investigating and Documenting Existing Utilities.” What does the Utility Report to IDOT include? Refer to ASCE/UESI/CI 38-22 Chapter C4 Engineer and Owner Tasks. C4.1.16 Preparing the Utility Report. The Utility Report should include the following, but not necessarily all, inclusive information: • Project description (e.g., project limits, type of work, existing utilities); • Contract requirements relative to utilities; • Metadata; • Methods used to collect and depict subsurface Utility information; • List of Utility Owners or other entities that have information on utilities within the project limits that were contacted and results of the contact; • Description of the types and thoroughness of research applied to obtain information from the Utility Owners and other entities; • Types of equipment selected and used to collect information; • Types of software used to depict information; • Areas swept, areas, not swept, and suspect areas; • Utilities found and documented (type, attributes, etc.); • Linear feet designated, number of Test Holes excavated, and other pertinent results; • Problems encountered and unresolved issues (such as unidentified utilities, inconclusive information, or conflicting information); • Detailed efforts and actions taken to identify ownership and type of designated unknown utilities; • Conflict analysis setup (e.g., Utility conflict matrix, potential conflicts, resolved conflicts, or remaining conflicts to be addressed during design) if part of the Scope of Work; • Recommended additional or future work; and • Pictures, images, and lidar data that may convey information more accurately than graphical deliverables. Tell us which other State DOTs have this contract language. #asce/uesi/ci 38-22
Aaron Etzkorn
2mo
Impressive commitment to quality and safety. How has this impacted project outcomes and client satisfaction, Steven M. Rienks, P.E., PMP?
Rich Ferguson
3mo
Thank you Steve for posting this on LinkedIn. Hopefully, you receive input from professionals from other States.
Husband | Dad | Servant Leadership | Drone Ninja | SUE | Survey | Utility Mapping | Damage Prevention | FAA Certified UAS Pilot
3moKey verbiage is, "but not necessarily all". We all know the data you are delivering, format of delivery, schedule and everything else that is scoped has got to be negotiated and clearly defined in writing upon execution of the contract. That's just PM 101. This will prevent scope creep, and mitigate any, "Uh...where is this...I thought you were giving us this? But what about...?" It takes the guess work of project deliverables out of the equation. Here's what we've agreed to. Which should be exactly what's being delivered. Nothing more, nothing less. As for the language in this particular scope of work, I haven't seen a request like this. I can understand wanting to get the best bang for your buck...but, there's several "extras" on this list that's going to cost you.