FieldManager

From MDOT Wiki
Revision as of 20:49, 29 March 2016 by McGowanR (Talk | contribs)

Jump to: navigation, search
Division 1 Supplemental Information
FieldManager


Contents

FieldManager

FieldManager is a construction management system employed by over 1000 users to manage and track road and bridge construction projects in Michigan. It will be used by MDOT’s Region, TSC and construction field offices, local government agencies and construction consultants. Business functions automated by FieldManager include the following.

  • Contractor payments
  • Inspector’s Daily Reports (IDR)
  • Daily Diaries
  • Work item progress
  • Contract Modifications
  • Material usage
  • Stockpile management
  • Estimates
  • Project finalizations

Construction projects are initialized in FieldManager from files that have been created in Lansing using AASHTO’s Trns*port software. Once construction begins, FieldManager stringently monitors and reviews the work activities that occur throughout the life of each project. IDR information is captured on notebook computers directly at the construction sites and later transferred to a network, or desktop computer, located in the field office responsible for managing the project. More than 50 inquires are available to provide information when and where it is needed. FieldManager also sends pertinent data to Trns*port software on a daily basis.

The FieldManager suite of products consists of four components:

  • FieldManager - The main component, which usually runs at the field office and manages product data by processing IDR’s, Contract Modifications and Estimates.
  • FieldBook - Used to gather IDR information directly at the construction site and sends the IDR’s electronically to FieldManager.
  • FieldPad - A subcomponent of FieldBook that runs on a hand held device.
  • FieldBuilder - Allows local government and consulting agencies to establish their own respective FieldManager projects on contracts that will not be processed through the Trns*port system.

For information on acquiring the software, self-paced FieldManager and FieldBook Tutorials, FieldManager User’s Guide, Trns*port interface or technical questions, please call the FieldManager Help Line at 517-322-1556.

Current information on FieldManager system requirements, articles, press releases, events, presentations, license feed, etc., can be found at www.fieldmanager.com

[top of page]


Using FieldManager to Track Design-Build Contracts

The purpose of this section is to provide instructions on how to utilize FieldManager to track design-build contracts. When design-build contracts are awarded, the managing office will receive the FieldManager initialization file (live contract) through FieldNet, which contains three-to-five pay items used to pay the contractor. However, design-build contracts do not use typical construction work items; therefore, FieldManager will utilize two contracts. In addition to the “live contract,” the managing office will also use a “shadow contract”, which will be used to:


  1. Document construction activities
  2. Document work items
  3. Track material usage and approvals


In short, continue using MDOT procedures when documenting the above items in the shadow contracts.


It is critical to track and document material usage on design-build contracts. Book 2 section 2 of

design-build contracts require the design-build team to provide MDOT with the estimated quantities for all items that require inspection or testing in accordance with MDOT’s Material Source Guide. The team must submit this information with or before the “released for construction” documents. The managing office will manually enter this information into the shadow contract.


FieldNet will be used for the live contract pay estimates, contract modifications, and contractor performance evaluations; however, FieldNet will not be used to process these electronic files for shadow contracts.

[top of page]


Documenting Procedures for Live and Shadow Contracts

  1. When the initialization file is received through FieldNet, contact the FieldManager Help Desk to acquire a shadow contract initialization file.
  2. Use the following contract ID naming convention:
    • Live contract: 38103-105785
    • Shadow contract: _38103-105785X
  3. Use the following project number naming convention:
    • Live contract: 105785A
    • Shadow contract: _105785AX
  4. Adding shadow contract items and materials:

a. Add items through:

  • Contract modifications, or
  • Tracked as unattached items

b. Add materials associated with items as needed.

  1. Subcontracts – Enter subcontracts into the live contract and the shadow contract; this includes the design subcontract.
  2. Construction Started Date – Populate the FieldManager Docu > General tab > “Construction started date” is to be populated when the design starts (just after award) on the live and shadow contracts, as the designer is a subcontractor.
  3. Contract Files – Include shadow contract documents in the original live contract files.
  4. Contractor Performance Evaluations (CPE) – Shadow contract CPEs will not be used for official contract documentation, but they must be generated before FieldManager will allow a final estimate to be completed. Use N/A to fill out the ratings tab for shadow contract CPEs.
  5. Archiving Shadow Contracts – Archive the contract in FieldManager after completing the final estimate, as is required with the live contract.
  6. FieldNet – You can use FieldNet to transfer shadow contract files between FieldManager and FieldBook, as can be done with any live contract. Contact the FieldManager Help Desk should you wish to use this feature.
  7. Contractor Read-Only (CRO) Files – In most cases, managing offices will not be creating biweekly shadow contract estimates. Therefore, contractors will not automatically receive CRO files as estimate creation is the auto-send CRO trigger. Users can still send CRO files to contractors via FieldNet by using FieldManager’s File > Export > Transfer contracts functionality.
  8. Stockpiles – This feature can be used on shadow contracts depending on how the managing office chooses to track contractor progress within the shadow contract.


To request a shadow contract or FieldManager support for design-build contracts, please contact the FieldManager Help Desk at 517-322-1556.


Mobile Inspector

Mobile Inspector is an app designed to run on tablets and smart phones. The purpose of the app is to allow inspectors in the field to create Inspector Daily Reports (IDRs) using a mobile device. Mobile Inspector runs on any device running Apple’s iOS or Android. It is designed to be as simple to use as possible.


Key features of the Mobile Inspector app include:

  • Intuitive user interface.
  • Easy IDR instruction for co-ops.
  • Can create IDRs while walking around at job site.
  • Voice recognition can be used instead of typing.
  • IDRs completed in Mobile Inspector are automatically sent to FieldManager.
  • Contract refreshes are automatically sent from FieldManager to Mobile Inspector.
  • Does not require connectivity to enter IDRs.
  • Runs on iPads, iPhones, and Android devices.
  • Can be used by MDOT and consultant staff for any project where an MDOT facility is the managing office.
  • Inspectors will not need training when MDOT implements AASHTOWare Project Construction & Materials as the app works with both FieldManager and the AASHTOWare software.


For more information on Mobile Inspector click on the link below:

Mobile Inspector


Reference the links below for FieldManager User’s Guide Supplements along with information related to installing and using Mobile Inspector devices with FieldManager:

User's Guide Supplements

Mobile Inspector Device Setup Guide


[top of page]


Inspector's Daily Report (IDR)

Perhaps the single most important type of project documentation is the Inspector’s Daily Report (IDR) and its variations. Because of the IDR’s importance, it is imperative that it be prepared correctly, legibly and thoroughly. At the very minimum, a completed IDR must include all report header information, a statement in the body of the report and a signature of the person who reviewed the IDR. The person reviewing the IDR should not be the author of the IDR.

The exact nomenclature and pay item code number shown in the proposal must be used when turning in a pay item. Any inaccuracy in nomenclature or code can be misleading, as many contracts contain pay items with similar nomenclature.

The recommended work flow method for submitting automated or manual IDR’s to the office for processing is to have each individual inspector complete the IDR and submit it to the office for processing.

Regardless of the method used, it is always the senior technician’s responsibility to collect all reports daily, review them and turn them into the office technician. Either the senior technician or the office technician checks and initials all computations.

Inspectors should complete and submit reports no later than the first work day after the work was performed. The sooner information is put in writing, the more accurate it will be.

In addition to the pay items, other details to be documented in the body of the report include Subcontractor information, final pay item quantities, final pay item field measurement (these items should be clearly labeled as final measured), associated pay item test material usage and comments, comments on maintaining traffic and maintenance of traffic devices (traffic device checks must be recorded daily). Anytime a material is posted to a pay item on an IDR, the inspector on site needs to visually inspect, verify the source/product name of the material, and document the information on the IDR. If the material source is unavailable, indicate that on the material posting. Comments on attitude and quality of Contractor’s work may also be recorded.

Other details that should be recorded include complaints from the public, along with inspector responses to these complaints, unusual events, daily weather conditions and accidents. Exceptionally good or bad work may also be cited.

Questions regarding this process can be answered by calling the FieldManager Help Line at 517-322-1556.

A sample IDR is shown in Figure 101-1.

Figure 101-1 - Sample IDR
Figure 101-1(Cont.) - Sample IDR

[top of page]


Documentation of Inspector Daily Reports

The purpose of this construction advisory is to remind construction staff of documentation requirements related to the retention of Inspector Daily Reports (IDRs) and any revisions made to the IDR. A 2013 Federal Highway Administration (FHWA) billing review noted deficiencies with retention of IDR documentation.

The 2013 FHWA billing review discovered that in some cases original IDRs are not being retained in the project files. Construction staff is to retain all original IDRs and any revisions to the IDR. These documents must be placed in the paper or electronic project files. This requirement applies to all federal aid projects regardless of construction oversight by MDOT, consultant, or local agency.

The requirement to maintain these documents has been previously referenced for local agency projects on page 3 of Bureau of Highway Instructional Memorandum (BOHIM) 2009-06, Region Oversight of Local Agency Construction Projects under the heading of Project Administration: MDOT-Let Local Agency Projects (Road/Bridge/Enhancement), which states in part the following:

In addition, when Inspector’s Daily Reports (IDRs) are modified or changed, the original and all revisions are to be kept in the project files as a permanent part of the project records.

This information and requirement must be reinforced to all construction staff at MDOT, consultant offices and local agencies. These documents are considered source documentation and must be maintained in the project files. The documentation requirements are applicable to all federally funded projects.

[top of page]


Personal tools
Namespaces

Variants
Actions
Navigation
Division 2 - Earthwork
Division 3 - Base Courses
Division 4 - Drainage Features
Division 5 - HMA Pavements and Surface Treatments
Division 6 - PCC Pavement Mixtures
Division 7 - Structures
Division 8 - Incidental Construction
Toolbox