Jump to content

Part F - eConstruction

From Delaware DOT Construction Manual
Revision as of 14:08, 1 April 2026 by Cblowers (talk | contribs) (→Project Vendors: added how-to document)

Back to Top

Section F1.00 - General Information

F1.01 - Introduction

  • The Federal Highway Administration's defines eConstruction as a paperless construction administration delivery process that includes electronic submission of all construction documentation by all stakeholders, electronic document routing/approvals (e-signature), and digital management of all construction documentation in a secure environment allowing distribution to all project stakeholders through mobile devices.
  • The Delaware Department of Transportation is accomplishing this through electronic recording of Inspector Daily Reports, electronic material tickets (hotmix and concrete), electronic submittal of documents, electronic E&S site inspections, electronic correspondence (including Notice to Proceed, First Chargeable Day, time suspension/resumption), and electronic payment tracking using the Primavera Unifier software. Unifier continues to add more Business Processes to incorporate design aspects as well including statements, PS&E, and project estimate information. Unifier will eventually be used to facilitate the electronic administration of all aspects of construction documentation from cradle to grave. In addition, we are moving towards adding 3D Modeling to our design process with more information on that process being added to this webpage as those processes are defined.
  • The information below explains the different software applications that the Department is using to facilitate the eConstruction effort. If users need live training, as opposed to instructional videos and guides, trainings can be scheduled using eContruction Training Request page. These trainings can be requested by any end-user, including the contractor.

Section F2.00 - List and Description of Software

F2.01 - Oracle Primavera Unifier

About Unifier

What is it?

  • Primavera Unifier is a web-based project lifecycle management application owned by Oracle, Inc. Click on this link for more information from Oracle.

How is it used?

  • It began as the framework for our eConstruction efforts.
  • It has now replaced Primavera P6 as the Department's overarching project management platform, retaining the Project Schedule, Support Section Statements, PS&E Documents, and more, in addition to the eConstruction efforts.
  • All capital construction projects administered by the Department of Transportation Solutions will use Unifier for:
    • Entering, tracking, and approving Inspector Daily Reports.
    • Creating and distributing Progress Meeting Minutes
    • Submitting, revising, and approving Source Documents
    • Creating Notice to Proceed documentation
    • Submitting Contractor Evaluations
    • Submitting Change Orders and Estimates for Contractor payments
    • Completing Project Closeout
    • Approving Price Submittals
    • Contractor submittal of documents (including but not limited to Source of Supply, Shop Drawings, Subcontractor Agreements, Requests to Work, Schedule Updates, and Requests for Information)
    • Creating Time Charge Notice documentation (First Chargeable Day, Time Suspension, and Time Resumption)
    • Future phases of the Unifier Implementation to be completed include tracking and approval of Force Account submissions and Subcontractor Agreement and Approvals.
    • Further plans to incorporate the advertising and awarding of contracts, capital budget planning, and additional DBE tracking efforts are all being considered as well.
  • Currently using version 23.12.3.

Unifier Access

How do you access it?

  • Unifier is accessed by going to https://Unifier.DelDOT.gov using any browser on any device with an internet connection.
  • Access to Unifier is currently granted to DelDOT employees, consultants of DelDOT, Prime Contractors, and FHWA with a role in our eConstruction effort, or other partners deemed necessary to the administration of DelDOT projects.
  • Mobile App Instructions
    • Overview: The Oracle Unifier Mobile app is available for free download on most Apple or Android devices from either the Apple App Store or Google Play Store. Simply search for Oracle Unifier and download it. While the mobile app is a more user-friendly interface from a mobile device, there are a few caveats:
      • The mobile app allows Unifier to be accessed while offline for those areas that do not get a cellular signal. Once a signal is received (or the device is connected to WiFi) it can either be forced to sync or will automatically sync the work done while offline.
      • Draft records are stored in the app on the device and not in the cloud or on the server. This means that any draft records made on the app are not accessible from a browser whether on the device, or a laptop/desktop. If you need to access a draft record from something other than the device you created it on, you must submit the record for review and ask that it be returned for revision.
      • Important: This means that if your device is stolen, broken, or wiped due to a forgotten device passcode, those draft records will be lost forever. It is STRONGLY SUGGESTED that users submit the record at the end of the day, even if it is not complete, and ask the person who is reviewing it to send it back to you. This is the only way to ensure that the records will not be lost forever.
      • Any process that has been made available to you can be accessed through the Unifier mobile app. However, reports or custom prints for the processes cannot currently be accessed. Those will still need to be accessed through the Unifier browser interface. However, the documents stored in the Document Manager are accessible through the mobile app, once a record is approved.

Unifier Support

F2.02 - HaulHub Technologies - EDOT

  • What is it?
    • HaulHub EDOT is a Construction Inspection application that collects raw data from from a variety of sources, including construction material suppliers.
    • E-DOT Inspector syncs with Unifier to exchange information relating to projects, staffing, ticketing, and item numbers.
  • Other Benefits
    • EDOT links contractor, inspector, material, and machine activity.
    • EDOT also features digital work zones that communicate with Waze to notify drivers of active work zones and worker presence.
    • The mobile application is able to provide stationing information to users.
    • The system will also be used to harness as-built data from materials and equipment for the Department's asset management uses.
  • How do you access it?
    • EDOT Inspector is accessed by going to https://tickets.deldot.gov using any browser on any device with an internet connection.
    • From Apple IOS devices (iPhone, iPad), download the EDOT Inspector (E-ticketing) app. More information on this app can be accessed by clicking on this link.
    • From Android devices (Samsung, Google), download the EDOT Inspector (E-ticketing) app. More information on this app can be accessed by clicking on this link.
    • Project staffing updates from Unifier nightly. If an inspector needs immediate access to a project, please contact the Project Area Engineer.

F2.03 - ADA Compliance Inspection Application (ACIA)

  • What is it?
    • ACIA is a web-based application that is used for Compliance Tracking and Inventory of Pedestrian Access Routes (PAR) and facilities within our Public Rights of Way
    • ACIA is used to perform all ADA inspections
    • ACIA is part of the Inspection Framework and necessary for an ADA Acceptance Memo and overall project acceptance
  • Why are we doing this?
    • DelDOT evaluated our ADA infrastructure in 2011-2012 and which included inventorying of facilities within DelDOT’s PAR
    • A Transition Plan was developed with the Federal Government to bring the facilities within our ROW into compliance, and to ensure that all new or reconstructed facilities comply with Federal Law
    • DelDOT is required to report to the FHWA annually our progress in implementing and improving ADA facilities on the Transition Plan
  • Other Benefits
    • In development is an interactive-automatically updating map that will be available to the public to assist the public with pedestrian route planning
    • Having up-to-date and accurate data regarding the status of pedestrian facilities will assist in scoping and development of future projects
  • How do you access it?
    • First, users will be required to create a my.delaware.gov account.
    • Once the my.delaware.gov account is confirmed, the user may request access within ACIA.
    • For further information see the ACIA section of this wiki page

Section F3.00 - Oracle Primavera Unifier

Unifer may be accessed at https://unifier.deldot.gov.

F3.01 General User Documentation

F3.02 Unifier Business Processes

This list is organized in the order that the Business Processes (BPs) are typically used in the course of a project.

Field Requested End Date

  • Location - Found under "General / Project Information" in the BP List.
  • Referenced by - Not referenced by other construction BPs.
  • Uses - As noted in Section C13.15, FRED is used to select the anticipated date that a project is completely closed out. This information is used by Finance to determine when the project Period of Performance must close.
  • Instructions -
    • The initial FRED is auto-created when a project moves from design to construction and will be sent to the Area Engineer that was designated on the project at the time of PS&E. If you do not receive a FRED, or receive a FRED for a project you are not assigned to, please enter a Unifier Support Request.
    • The FRED will automatically update with the approval of any Change Order.
    • After Substantial Completion (and the cessation of time charges) any extensions to the FRED must be manually created by the Area Engineer. Documents substantiating the extension should be attached to the FRED.

Project Vendors

  • Location - Found under the "General" category in the BP list.
  • Referenced by - Contacts-Summary, Contacts, CC List, Notice to Proceed, and IDRs.
  • Uses - This BP is a support BP, used as a reference link for multiple BPs within the project.
  • Instructions - At the start of the Construction Phase of every project the Area Engineer should create two records at minimum: DelDOT - assigned as the owner, and the Prime Contractor. Adding Utilities/Municipalities may be needed to complete the IDRs.

Contracts-Summary

Pay Items

This encompasses both Pay Items and Non-Bid Pay Items

Contacts

Please note that you must ensure Delaware Department of Transportation has been added as a Project Vendor before importing the .xlsx file.
  1. Download and save a copy of DelDOT Contacts to your local drive.
  2. Make any project specific modifications that may be necessary, and save the file.
  3. In Unifier, Select "General", then "Contacts".
  4. Once the Contacts BP Log is open, first select "Actions", then "Import", and then "From Microsoft Excel Template".
  5. Drag and drop your local copy of the .xlsx contacts file into the upload window, and select "Upload".
  • Manually create each record by keying in the required data.
  • To edit an already created contact, open the record, select "Edit", make the required changes, then select "Submit".

CC List

  • Location - Found under the "General" category in the BP List.
  • Referenced by - Subcontractor Approval, Notice to Proceed, Time Charge Notice, General Correspondence, and Price Approval.
  • Uses - This BP is a support BP for the above referenced processes. Because this is a non-workflow BP, records may be edited after creation, assuming the user has appropriate permissions. The CC List BP uses a combination of Unifier Roles and the added Contacts to generate a contact list which can be emailed an attachment of whichever completed record it is assigned to.
    • Unifier Roles, which are assigned within the Unifier system, and are separate from Contacts, are further divided into two categories:
      • Department Roles include positions such as Secretary of Transportation, Assistant Directors, etc. These individuals are pulled from a Master List within Unifier. Staffing changes on this level are handled on by the Unifier team on a global level.
      • Project Roles are defined by the staff assigned to the project within Unifier. These individuals are pulled from their defined project role, such as Area Engineer, Project Resident, Contractor, DBE Specialists, etc. If this staffing changes, it should be adjusted by the Area Engineer in the administration panel for the project and need not be adjusted within this BP.
    • Project Contacts are project specific personnel that typically do not have access to Unifier. Updates to these contacts must be addressed on the Contacts BP, but additions or wholesale replacement of individuals from the cc list must be handled within this BP.
  • Instructions -
  1. In Unifier, Select "General", then "CC List".
  2. Once the CC List BP Log is open, Select "Create". Do not attempt to import without creating a CC List record.
  3. In the new CC List Record, select the "CC List Type", and optionally you may provide a supplemental description.
    • NOTE: You may have more than one cc list of each type. I.E. Price Approvals may have one list for external distribution, and one for 401699 - QA/QC which only requires internal distribution.
  4. Under the "Contact Details" tab you have two options to add individuals:
    • Manually add individuals from Contacts, Department Roles, or Project Roles.
    • Bulk add individuals, using the below .xslx templates.
      1. Download the appropriate .xlsx file (below) to your local drive.
      2. Make any project specific modifications that may be necessary, and save the file.
        • Ensure you have uploaded Contacts, as found in the Contacts BP above, as the templates rely on Contacts already being loaded. Failure to do so will result in an error.
      3. Next on the details tab titled "Contact Details" go to "Actions", then "Import", then "Data From Microsoft Excel File", and then drag and drop the template file you modified for the project.
        • These templates also assume that various project roles, like Contractor and Project Resident have been assigned a user within Unifier.
        • Occasionally, these uploads will appear to hang or be stuck in the upload phase. You may disregard such notices or warnings and proceed with the upload. The file is not large enough to generate an error of that nature.
  5. Once created, users may edit the CC List by opening the record, selecting "Edit", selecting the "Contact Details tab", modifying the cc's as needed, selecting "Save" on the detail line, and "Submit" for the overall record.


  • TEMPLATE FILES
The order of individuals on the cc list is determined by their sequence number, with the lowest number being the first listed.
  • Due to this, it is recommended that the initial sequence numbering for individuals be entered in multiples of five (i.e. 5, 10, 15, etc.) to allow for the addition of individuals to the cc list without having to resequence the entire list.
Note - Individuals who are assigned under the Area Engineer role, who are not licensed PE's, must be added as Project Contact to ensure documentation is in compliance with Delaware Code.
  • Projects WITH a Professional Engineer assigned as the Area Engineer
last updated or reviewed on 2025.12.22 (All links for Internal Use Only)
  • Projects WITHOUT a Professional Engineer assigned as the Area Engineer
last updated or reviewed on 2025.12.22 (All links for Internal Use Only)


Submittals

  • Location - Found under "Construction Phase / Contract Administration".
  • Referenced by - Not referenced by other construction BPs.
  • Uses - Used by the Prime Contractor to send the different submittal types to the Department for review. It facilitates the review by the Area Engineer and Subject Matter Experts (SME) and is used to provide a response back to the Contractor. All information uploaded to this BP is saved in the Unifier Document Manager as well.
  • Instructions -
On larger projects it may be necessary to implement a naming convention for submittals to aid in quick identification. Below is a suggested naming convention. While some projects may need to alter this convention to fit the project type and needs, it is important to maintain the integrity of the naming convention within the project.
Suggested Submittals Naming Convention
Submittal Type Type-Number Suffix Description
Certified Payroll PR-001 A-Del Payroll Submittal 001 for A-Del
Certified Payroll PR-001 Kriss Payroll Submittal 001 for Kriss
Shop Drawing RW-001 RW 001
Shop Drawing BR-001 Bridge 001
Shop Drawing BR-001 A Bridge 001, resubmittal
Shop Drawing UT-001 Utility Shop Drawing 001
Project Schedule CPM-001 CPM submittal 001
Material SOS-001 A-Del Source of Supply 001 for A-Del
Material SOS-001 Kriss Source of Supply 001 for Kriss
MOT MOT-002 MOT Submittal 002
Other MISC-001 Miscellaneous Submittal 001
Contractor 2 Week TW-018 Two Week Schedule Submittal 018

Request for Information

  • Location - Found under "Construction Phase / Contract Administration".
  • Referenced by - Not referenced by other construction BPs.
  • Uses - Used by the Prime Contractor's Project Manager to submit Requests for Information to the Department for review. It facilitates the review by the Area Engineer and Subject Matter Experts (SME) and is used to provide a response back to the contractor. All information uploaded to this BP is saved in the Unifier Document Manager as well.
  • Instructions -

Subcontractor Approval

  • Location - Found under "Construction Phase / Contract Administration".
  • Referenced by - adds approved Subcontractors to Project Vendors.
  • Uses - Used to identify and approve Subcontractors to be added to the project. This BP is initiated by the Contractor before it is sent to its subsequent review steps.
  • Instructions -
    • Initiation - This step is completed by the Contractor for all subcontractors, regardless of their status (DBE, third-tier subcontractor).
Subcontractor Approval - Record Initiation
  • Note: Race Conscious is a Federal term that identifies if a DBE Subcontractor is participating towards the Contract's DBE goal attainment.
  • Note: FHWA Form 1273 is only required if the Contract is receiving Federal Funding. Unifier identifies the FHWA Participation for the user in this step.
  • Note: When adding subcontracted items to the record, the contract can identify if the item should be included towards the 50% subcontracting limit or not. Items that should be excluded may include, but are not limited to, specialty items, services, and work performed by third tier subcontractors.
  • Note: The Agreement UOM does not need to match the Pay Item UOM.
Example: Subcontracts on fuel servicing may be placed under 763000 - Initial Expense, with a Gallon UOM. Subcontracts on trucking may be placed under 202000 - Excavation and Embankment, with a Lump Sum, UOM. Remarks should be added in either circumstance. Remarks may include "See attached Subcontractor Agreement for further details."
  • Review - Depending upon the record, the Unifier Administrator and DBE Specialist may review the record for accuracy. The Area Engineer, Estimator, and Group Engineer will review the record.
Subcontractor Approval - DBE Review
Subcontractor Approval - AE & DBE Review
Subcontractor Approval - Estimator Review
  • Revision - The record may be sent back to the Contractor at any point during its review. The Contractor must address any issues and resubmit the record.
Subcontractor Approval - Revision
  • Approval - Upon approval of the record, the Subcontractor will be automatically added to the project's Vendor List for use within the IDR BP. If a Subcontractor does not appear as a Vendor, then they are not approved.

Project Locations

  • Location - Found under the "General" category in the BP List.
  • Referenced by - Inspector Daily Reports
  • Uses - This is a support BP used to track on multi-location projects. This allows inspectors to document work, quantities, and other important information based on a specific location.
    • Benefits of this BP include the ability to search by location within the Inspector Daily Reports BP and simplifying tracking of quantities and costs associated with a location.
  • Instructions - Project Locations can be generated in Unifier by the Project Resident or Area Engineer.

Notice to Proceed

  • Location - Found under "Construction Phase / Contract Administration".
  • Referenced by - Not referenced by other construction BPs.
  • Uses - Used to autogenerate the required NTP letter as noted in Section 108.2 of the Standard Specifications and C9.00 - Notice to Proceed of this manual.
  • Instructions - This record is created by submitted by the Area Engineer and approved/signed by the Group Engineer.
    • The NTP options include Full or Partial. Each letter has language specific to the type.
      • Partial NTP, for off-site fabrication: "The work is limited to off-site fabrication for approved submittals by the Department."
      • Partial NTP, not all ROW acquired: "The work is limited to areas with acquired Right of Way as noted in the executed Contract and subsequent communications."
      • Partial NTP, schedule not yet approved: "Work may proceed but all estimates will be held until your work schedule is approved."
      • Partial NTP, other: This does not include standard language, but can be modified under the letter details section to include any details that apply.
      • Full NTP with no exceptions: "Work may being on 'DATE', time charges will begin no later than 'DATE'."
      • Full NTP with work schedule not approved: "Work may proceed but all estimates will be held until your work schedule is approved."


Time Charge Notices

  • Location - Found under "Construction Phase / Contract Administration".
  • Referenced by - Contracts-Summary and Progress Estimate.
  • Uses -
    • Used to generate First Chargeable Day letters, as noted in Section 108.3 of the Standard Specifications and Part C13.06 of this manual.
    • Used to generate Suspension and Resumption letters, as noted in Section 104.2.D of the Standard Specifications and Parts C13.07 and 13.08 of this manual.
    • Currently, this BP is only creating the memos. However, there is an intention to use this BP to not only create the memos, but it will also help us generate the exact time used during an estimate period and help with calculating the number of days passed in the Inspector Daily Report PDF.
  • Instructions -
    • First Chargeable Day -
      1. Open the BP log.
      2. Select "Create", then "First Chargeable Day"
      3. Fill out the following fields:
        • Title (optional)
        • Contract Reference (from Contracts-Summary)
        • The actual First Chargeable Day
        • The date the notice is issued
        • The District Engineer for the Maintenance District the project is in (from Contacts)
        • The CC List
        • Any additional details or wording needed in body of the letter.
    • Time Suspension and Time Resumption - Note: This is a two-step process. While interim steps will issue a suspension letter to the Contractor, the record is not closed until the Resumption letter has been issued.
      • SUSPENSION
      1. Open the BP log.
      2. Select "Create", then "Suspension & Resumption"
      3. Fill out the following fields:
        • Title (recommended)
        • Contract Reference (from Contracts-Summary)
        • Whom requested the suspension
        • Select the reason for suspension (this will change the default wording in the form letter)
        • The date the notice is issued (this is the GE Approval date)
        • The start date of the suspension
        • The anticipated end date of the suspension
        • The CC List
        • Any additional details or wording needed in body of the letter.
        • The Contractor's Project Manager (from Contacts)
  • Standard language in the letter includes:
       "Unless otherwise noted or discussed, the Contractor will remain responsible for a limited scope of work including, but not limited to, the following: Maintenance of Traffic. Environmental and stormwater controls. All other requirements of Standard Specification 104.13, Contractor's Responsibility for the Work."
  • RESUMPTION
  1. Open the BP log.
  2. Select the previously created suspension record.
  3. Fill out the following fields:
    • The date time charges will resume
    • The date the notice is being sent (this is the GE Approval Date)
    • Any additional details or wording needed in body of the letter.
  • Standard language in the letter includes:
       "As soon as possible, the Contractor is requested to submit a two-week activity schedule with a start date on or before (DATE) so the department can secure staffing. Whether or not work begins, time charges will resume on the aforementioned date."

E&S Site Inspection

  • Location - Found under "Construction Phase / Field"
  • Referenced by - Not referenced by other construction BPs
  • Uses - The E&S Site Inspection BP is used for Minor Projects and when required, must be completely weekly by an inspector with at least a current Contractor Training Program Certificate "Blue Card" holder. It is preferred that this be completed by an inspector with a current Certified Construction Reviewer "Gold Card" issued after February 2019.
  • Instructions - This inspection includes questions and documentation for the following categories: Sediment & Stormwater Management Plan (SSMP), Erosion & Sediment Controls, Pollution Prevention Practices, and Deficiencies (specific to BMP Control Devices). The workflow for this Business Process includes creation by any inspector assigned to the project that meets the requirements and approval by the Project Resident.

E&S Control Revision Form

  • Location - Found in "Construction Phase / Field"
  • Referenced by - Not referenced by other construction BPs.
  • Uses - This BP is used to update or the current Plan related to the erosion and sediment controls of a construction site.
  • Instructions - This record can be created by the Contractor, the Area Engineer, or the E&S liaison (ESL). ESL will have first review of all records. Depending on the category of the revision, the workflow will then direct the record to the appropriate Subject Matter Experts (SMEs). SMEs may include a representative from Environmental Studies, the E&S Engineer, and/or the Stormwater Engineer. The final steps of every record will be Area Engineer review and Contractor approval.
    • Revision categories include:
      • Placeholders and Substitutions
      • LOC (Major)
      • Permanent Modification
      • Sequencing/Phasing (Major)
      • Wetlands/Environmental Impacts
      • LOC (Minor)
      • Sequencing/Phase (Minor)
      • Alternate BMP/E&S Device
      • BMP/E&S Device Modification
    • Redline plan sheets and any other required documentation will be attached for review and approval.

eTicketing

Two associated Business Processes fall under the eTicketing categories.

eTickets

  • Location - Found under "Construction Phase / Field / eTicketing".
  • Referenced by - Ticket Packages
  • Uses - The eTicket BP is where eTickets are stored in Unifier. ETickets are imported into Unifier from HaulHub on an hourly basis. However, only tickets that have been marked delivered will be imported. Refer to Part F4.01 for more information on marking tickets delivered.
  • Instructions - This BP does not modify the ticket information. In this BP users can view the raw tickets and their status (Used/Unused).
    • Once eTickets are assigned and approved on a Ticket Package and IDR the status under the "Used?" category will change to "Yes". Tickets marked used in the system cannot be added to another ticket package in order to prevent double payments.

Ticket Packages

  • Location - Found under "Construction Phase / Field / eTicketing".
  • Referenced by - Inspector Daily Report
  • Uses - The Ticket Package BP is used to compile eTickets together. Once compiled, the packages can be imported into the IDR for tracking and payment.
  • Instructions -
    1. eTicket Selection Filters - Open a new Ticket Package record and select the eTicket filters to build the package. This includes material type, date & time range of ticket creation at the supplier, and (optionally) the inspector who marked the ticket delivered within EDOT. This optional category can be used as an additional filter to gather eTickets when multiple operations using the same material are underway on-site.
    2. eTicket Package Defaults - The user must identify if the eTickets in the Package are Pay or Source Tickets, and the Item Number they fall under. These fields must be filled even if the items had already been assigned in EDOT. This will only add information to the ticket if an item was not assigned in EDOT.
      • Note - "Override EDOT Value" will overwrite any item information that was entered in EDOT. This may be necessary in circumstances such as Flowable Fill tickets, where the item is imported as a Source Ticket, but it will be used as a Pay Ticket.
    3. Once the upper form is complete, the Ticket Package can be sent to Auto-Generate Ticket Package. In this step, eTickets meeting the filter requirements will be automatically gathered and if, needed, reassigned the Pay Item and Pay/Source designation as identified in step 2.
    4. Ticket Package Review - Once populated, the creator of the ticket package can modify the eTickets and package as needed. This includes, adding or removing individual tickets, correcting quantities due to overweights or underpayment, splitting tickets, modifying pay items, and/or adding payment for surcharge.
    5. Once the eTickets are confirmed, the Re-calculate eTickets Total on the upper form will need to be completed.
      • The difference should be 0. If there is a positive or negative value, this indicates a missing or duplicated payment and must be corrected.
      • To confirm pay items, use the Summary Pay Items tab.
      • If you are having issues identifying which ticket is causing the difference, use the Custom Print of the Ticket Package to help determine the error.
      • Please note, waste identified in the EDOT app is automatically deducted
    6. After reviewing the totals and all eTickets, the Ticket Package is sent to Calculate Summary Lines to prepare it for import into the IDR. The Ticket Package will remain in the Project Resident's review until it is added to an IDR.
      • REMINDER - Project Residents must never send a ticket package to the end step. They will review and approve within the IDR. The Ticket Packages will be automatically approved/completed when the IDR is approved.
      • If a revision to a Ticket Package is needed, the Project Resident can return for revision from the Ticket Package BP. If the inspector is missing tickets, the Ticket Package can be returned again to change eTickets selection which will allow new dates/times to be selected.

Inspector Daily Report

  • Location - Found under "Construction Phase / Field".
  • Referenced by - Pay Items, Source Documents, and Estimates indirectly.
  • Uses - The Inspector Daily Report (IDR) BP is primarily used by Inspectors to track activities and detail the work operations on a Project. Information includes date, weather, personnel, equipment, pay items/ticket packages, materials, visitors, potential risks/issues, photos, and a detailed description of the work on site (started, ongoing, completed). While Area Engineers, Project Residents, and Office Managers may also create records, the latter two are required to approve the records.
  • Instructions - Staff is to complete all applicable parts of the record for each day they are assigned in the field to the project.
Guides:
  • For projects requiring Blue Check, please select Source Document Review required for all applicable pay items. This will automatically generate a Source Document BP record and send for review. See Source Document BP section for more information.
  • Inspection staff must coordinate/communicate with each other on the project. It is recommended to only track weather and personnel/equipment on one IDR. For personnel and equipment, you may have duplicates if there are multiple crews.
  • The project type will determine the workflow on a given project. Workflow options include:
    • Project Resident Review
    • Office Manager and Project Resident Review
    • Lead Inspector, Office Manager, and Project Resident Review
    • Once the workflow is selected (during the creation of the Contracts-Summary record), changes to the workflow must be requested by the Area Engineer using a Support Request.

Source Documents

  • Location - Found under "Construction Phase / Field"
  • Referenced by - Not referenced by other construction BPs.
  • Uses - Source Document records, as noted in Part D6.04, are required for any items that require a calculation to determine the quantity. Records for this BP are automatically generated from the IDR BP to facilitate the required Blue Check.
  • Instructions - To create the record, when completing the IDR Construction Inspection staff will be prompted to select if Source Document Review is Required. If yes, the Source Document record is created once the IDR is fully approved.
    • Once created, the assigned Blue Checker will review the document for accuracy and either approve the record or send for revision. If the record is sent for revision, the Office Manager or Project Resident can either update and return the record or return to Inspector for revision. The Source Document could require new calculations that results in a quantity change. If there is a quantity change, the Construction staff must attach or link the revised Source Document and link proof of the submitted pay adjustment (through a Quantity Adjustment or Inspector Daily Report).
    • REMINDERS:
      • All Source Documents are required to be a PDF.
      • All work/calculations must be written out.
      • All payments must be rounded to two (2) decimal places.
      • QAQC, AC Cost Adjustment, and Traffic Officer items will require Source Documents to be Blue Checked. Please discuss the process with your Blue Checker prior to submitting the first Source Document. The price must be approved prior to creating a Source Document record.
      • Do not create a new Source Document record for quantity changes. Return the corrections through the existing Source Document Record.
    • Some Area Engineers may require Source Documents for all items, but this does not mean that all items need to be Blue Checked. Please discuss with your Area Engineer at the start of each project.

General Correspondence

  • Location - Found under "Construction Phase / Contract Administration"
  • Referenced by - Not referenced by other construction BPs
  • Uses - This BP is used for miscellaneous documentation. Letters can be generated for any correspondence type by using the Body of Correspondence Details box. The letters can be generated as in progress (for review) and correspondence sent (approved/completed). This BP uses the Contacts BP and the CC List BP to distribute letters, even to users without Unifier access.
  • Instructions - Please see the Whatfix guides and videos within Unifier.

Price Approval

Change Orders

  • Location - Found under "Construction Phase / Contract Administation"
  • Referenced by - Pay Items and Estimates
  • Uses - Used to modify approved quantity of original bid items, add new bid items that were created under the Price Approval BP, and adjust the duration of Contract Time. This BP also tracks the reason and justification for those quantity changes, for retrospective reviews. Reason codes are lised below:
Change Order Reason Codes

Quantity Adjustment

  • Location - Found under "Construction Phase / Field"
  • Referenced by - Pay Items and Estimates
  • Uses - Used to complete pay item quantity adjustments to prior estimate periods (usually due to a review or Blue Check), or if multiple adjustments are needed in the current period. This BP is also used to deactivate items that are no longer needed on a project, such as an old item that has been replaced with a new item.
    • NOTE: While this BP functions like a quantity only IDR, please be mindful that this BP does not generate it's own Source Document. Therefore, it will need to be linked to the record it is correcting.
  • Instructions - Please refer to IDR for instructions.

Estimates

  • OVERVIEW: In Unifier, the Estimate process is a two BP process. Pencil Estimate and Progress Estimate. First, a Pencil Estimate record must be initiated, reviewed, and acknowledged by the following roles: Project Resident, Contractor Project Manager, and Area Engineer. After the Pencil Estimate record is complete. The Area Engineer will continue the process by starting a "Progress Estimate" record. The Progress Estimate record must then be reviewed and acknowledged by the following roles: Estimator, Contractor Project Manager, Group Engineer, and Chief of Construction (only if it is a Final Estimate). It is important that the Estimate Worksheet is accurate, as this is the best opportunity to correct errors. The items and quantities on this report are an exact representation of what will be used in the Progress Estimate BP.

Pencil Estimate

  • Location - Found under "Construction Phase / Contract Administration.
  • Referenced by - Progress Estimate
  • Uses - Intended as a "rough draft" of the estimate, to catch any missing quantities, or quantity overruns that require a Change Order.
  • Instructions -
    1. Creating a Pencil Estimate Record (.pdf)
    2. Project Resident Pre-Review (2:17)
      • Ensure the "Days Charged" field, which is auto-filled by Unifier based upon the cutoff dates, is accurate. Note that this auto-filled field does not account for any suspension, or the Substantial Completion of the project.
    3. Contractor Review (2:04)
    4. Area Engineer Review (2:06)
    • ADDITIONAL INFORMATION: If it is determined that the records needs to be corrected, the record should be sent to the revision step. This will send the record back to the responsibility of the Project Resident. At that point, based on the type of change that is required, a Price Approval, Change Order, and/or Quantity Adjustment can be completed and approved by the appropriate people. Keep in mind that if a new item is needed, all 3 processes must be completed (Price Approval to add the item to the list of items, Quantity Adjustment or corrective IDR to record the quantity to be paid for that period, and Change Order to officially add the item to the Contract so that it can be paid on a Progress Estimate). Once that is done, there are 2 options:
      • If you are sure that the appropriate adjustments were made, simply move the record to the Contractor Review step
      • However, it is recommended that the Estimate Worksheet be verified first. Follow this video to manually run the Estimate Worksheet from the record: (Run Estimate Worksheet)
    • REMINDER: Non-Bid Pay Items will not appear on the Pencil Estimate or Estimate Worksheet until the Change Order adding that item is fully approved.

Progress Estimate

  • Location - Found under "Construction Phase / Contract Administration.
  • Referenced by - Change Order
  • Uses - This BP, initiated by the Area Engineer, uses the Pencil Estimate to set the parameters and then import quantities from the IDR and Quantity Adjustments based on those quantities before review and approval to subsequently generate a payment voucher in FACTS, as noted in Part D8.01.
  • Instructions -
    1. This process is started by the Area Engineer, who selects a Pencil Estimate to associate with the record, verifies the information in the record, and then sends it to the next step.
    2. At the Estimator Review steps, the Estimator decides whether they want to automatically pull item quantities from the Approved Inspector Daily Reports (IDR) or manually enter the quantity of each item. In the case where the Estimator decides to pull from the Approved IDRs, the Estimator does get a chance to review the estimate, comparing the totals to the information in the Pencil Estimate, before sending the record to the next step.
    3. At the Contractor Review step, the Contractor is able to review the record and either send it for approval or revision.
    4. If the record is an Interim or Semi-Final Estimate, the Group Engineer has the final review of the record before either requesting a revision, or completing a final approval. If the record is identified as a Final Estimate, it will go to the Chief of Construction & Materials for final acknowledgment.
    • Viewing/Printing the Progress Estimate PDF (1:37)
    • MISCELLANEOUS ADJUSTMENTS: At the Semi-Final or Final Estimate stage, it should be determined whether there was a rounding error on a change order by using the Adjust Balance to Current Payment Due? selector. This will enable the Miscellaneous Adjustment field and allow the Estimator to modify the current payment due field by that amount. The File:Misc Adjustments.pdf will explain in more detail how to find and use this function in Unifier.
    • ADDITIONAL INFORMATION: If it is determined that the Progress Estimate needs to be corrected, the record should be sent to the revision step. This will send the record back to the responsibility of the Estimators. At that point, based on the type of change that is required, a Price Approval, Change Order, and/or Quantity adjustment can be completed. Keep in mind that if a new item is needed, all 3 processes must be completed to add the item to the list of items, Quantity Adjustment to record the quantity to be paid for that period and Change Order to officially add the item to the Contract so that it can be paid on a Progress Estimate. Once that is done, there are 2 options:
    • If you are sure that the appropriate adjustments were made, simply move the record to the Contractor Review step
    • However, it is recommended that the Estimate Worksheet be verified first. Follow the Run Estimate Worksheet video to manually run the Estimate Worksheet from the record.
    • Note about Change Orders: Currently, Unifier does not allow a Change Order with a negative quantity to be processed while a Progress Estimate is in flight. If this is needed, please submit a Unifier Support Request to have the Progress Estimate record terminated so that the Change Order can be processed.

Progress Meeting

  • Location - Found in "Construction Phase / Field"
  • Referenced by - Not referenced by other construction BP's.
  • Uses - The Progress Meeting BP is used to generate a Progress Meeting agenda for distribution and the final meeting minutes.
  • Instructions -
    1. Fill out the requisite fields in the upper form:
      • Meeting Date, Meeting No., Meeting Time, Meeting Location
      • % Time Elapsed, % Work Complete
      • RFI Log (pending items)
      • Shop Drawings
      • Source of Supply Submittals/Material Certification
      • Sub-contractor Approvals (To Date)
      • Trainees
      • Change Order Update
      • Certified Payrolls
      • Additional Comments
    2. Under the Business Items Details tab the creator to assign a type, title, date, and if further action is required. In addition, there is a section to describe the issue and progress throughout additional meetings.
    3. The record can then be sent to "Distribute Agenda" to be printed and distributed to the attendees.
    4. The minutes can then be sent to recording to be updated with the occurrences of the meeting, and add the list of attendees.
      • The attendees can be selected from those previously entered in the Contacts BP
    5. The meeting minutes can then be sent for "Review" by the Area Engineer before being downloaded and sent via email.
      • At this time, the minutes do not self-distribute in Unifier.
    • NOTE: After the record is closed, the next meeting can be started by copying the previous record to reduce the burden of creating the record.

Contractor Evaluations

  • Location - Found under "Construction Phase / Contract Administration".
  • Referenced by - not referenced by other construction BPs.
  • Uses - Used to fulfill the regulatory requirements noted in Part C16.07.
  • Instructions -
    1. Either the Project Resident or Area Engineer must create the record.
    2. The creator then completes the record, noting if the Contractor has met the requirements for each item in the current reporting period.
    3. The record is then sent to the Area Engineer for review.
      • REMINDERS
        • If an item is left blank, it will result in a deduction of their score. If an item does not apply to the Contract, please mark "N/A".
        • Any items left blank must have backup documentation attached to the record. For example, if the Contractor did not maintain signage/MOT, please include photos of the work zone and/or email correspondence asking for it to be addressed.
    4. After review, the record is sent to the Group Engineer. The Group Engineer may send it to the Contractor, or request a revision.
    5. The Contractor may either accept the score or request a meeting with the Chief of Construction and Materials.

Project Closeout

  • Location - Found under "Construction Phase / Contract Administration".
  • Referenced by - Not referenced by other construction BPs.
  • Uses - This BP is not used by construction. This BP is used to generate a notification for Audit and Finance that the Construction Phase of the project is complete, and provide the supporting documents in one record. While this does require some re-entry on the part of construction staff, this serves as verification to Audit that they may begin their work.
  • Instructions - The Project Closeout BP is autogenerated once the Final Estimate is approved. This BP requires the Area Engineer and Estimator to confirm receipt and attach the following items:
    • Punchlist Complete? Yes/No and attach annotated Primary Inspection Punchlist
    • Final Acceptance Letter Signed by M&O? Yes/No and attach signed Acceptance Letter
    • Final Change Order Complete? Yes/No and attach/link final Change Order
    • Confirm all Signed Change Orders on File: Yes/No
    • Confirm all Change Orders Signed Off by FHWA: Yes/No/NA
    • Final Estiamte Signed/All Items Paid: Yes/No and attach/link Final Estimate
    • CN-102 General Contractor Release: Yes/No and attach copy of release
    • Bond Company Release: Yes/No and attach copy of bond release
    • CN-103 Sub-Contractor Release (each subcontractor): Yes/No and attach all required releases
    • Archive: Yes/No and attach any required paperwork for the archiving process
    • Attachments can be added under the Closeout Documents tab.
      • NOTE: The BP is designed to only allow internal attachments from the Unifier Document Manager, as these records should already exist in the project file. External attachments are not permitted.
    • Under the Phase Closeout tab, select the appropriate phases and select the date it was closed.

Section F4.00 - HaulHub EDOT

Updated workflows within Unifier will now create the project within EDOT, assign the staff, and sync item numbers available to be assigned to tickets.

F4.01 Tickets

HaulHub has generated purpose built training videos for all of their DOT customers. These videos are identified below and serve as an excellent guide, but they do not discuss the nuances of DelDOT's particular processes. If individual training is required, please reach out to schedule an eConstruction Training Session.

Requirements

  • In accordance with the 763520 Electronic Ticketing Special Provision, calibration tickets are required for each supplier and each hot-mix item at least 14 days prior to shipping material unless otherwise approved by the Engineer.
  • Beginning in 2026, ready-mix concrete will be added as a material which requires eTickets, in addition to the standing hot-mix requirements.
    • Included with this change will be the ability to mark pay items on tickets as they are marked delivered. The user is able to assign up to three pay items on each ticket within the EDOT Mobile Application. Tickets can then be added to a Ticket Package within Unifier. If a ticket must be split between more than three pay items, then it must be done within Unifier.

F4.02 Digital Stationing

Digital stationing may be added to projects to aid in identifying their location in the field. This information may be used in the mobile application based upon a dropped point or cell phone location data (accurate to within 30'). Currently, stationing can only be added by the Construction Resource Engineer, but in the future users will be able to do so as well.

To facilitate the creation of the stationing, any alignment files should be requested from the Engineer of Record. These files can be exported as shown in the DelDOT CADD wiki.

Stations are then generated in one of two ways.

  • Import: The alignment export can be added to EDOT to create alignments that precisely match the plans. These imported alignments can be turned on and off, or designated to different components, based upon the needs in the field and the phase of the project. The currently accepted alignment files for import are LandXML files. Future updates may allow for the use of .dgn files and .ifc files.
  • Manual Creation: The start and end points on the project can be selected and assign a station to the start point. This system uses Delaware's publicly available Linear Reference System, and will match the alignment to existing roads. This may lead to some issues & artifacts when used on divided highways and crossing bridges.


In general, it is expected that manual creation will be utilized for Pavement and Rehabilitation Projects, whereas import will be utilized for Capital Projects.

The creation of stationing within EDOT allows for the same alignments to be made into work zones automatically after verification, so the addition of stationing to a project should be the rule, not the exception.

F4.03 Work Zones

The creation of a work zone within EDOT is required for all construction projects. This work zone will automatically be identified as Active when either a ticket is marked delivered within the work zone, or when connected equipment is is detected to be running within the work zone. Upon the work zone being identified as Active, a notification is displayed within Waze for the traveling public. Future integrations include DelDOT's Transportation Management Center and other consumer navigation programs.

The work zone should be automatically created from a stationing alignment, but if it does not match an alignment the user must create the work zone by matching a poly line to the road, the user will be prompted to enter information as identified below. This information should be filled out as follows:

  • Road Name: The Road Name must accurately reflect the road that they are working on. For divided highways and ramps this should be more specific, i.e. "SR 896 NB to I-95 NB". For two lane, two directional roads, it should simply be the road name, i.e. "Sunnyside Road". This is because impacts on two lane, two directional roads may be experienced in both directions.
  • Kind of Road Event: The user should always select "A Work zone area".
  • In which direction: The user should only select a direction if it is a divided highway or ramp. For undivided roads, the user should select "No signed direction" for the same reason identified above.
  • Motorist Notification: The user should enter "Workers Present - Slow Down".
  • Reduced Speed: Enter the regulatory speed limit. You may only enter a reduced speed limit if it is noted in the plans for the current phase of work. Please check with your immediate supervisor and/or the Traffic Safety Section if you have any questions.
  • Method to indicate: The user should select "Unknown" as this field is currently not being used.
  • Impact to vehicular lanes The user should select "Unknown" as this field requires daily modification. Future improvements will make use of this section in a manner that is not an additional burden on the project staff.
    • Some users may be willing to update this section daily. If this is done, the user must return the setting to "Unknown" once the daily impact has ended. This is to ensure any notification has the highest degree of accuracy.
Image of Work Zone Creation within the EDOT Application
Image of Work Zone Creation within the EDOT Application

Section F5.00 - ADA Compliance Inspection Application (ACIA) Documentation

F5.01 ACIA Procedures

Retrieved from "https://constructionmanual.deldot.gov/index.php?title=Part_F_-_eConstruction&oldid=1550"