FieldManager - Revision history

Clarkj25: /* Inspector's Daily Report (IDR) */

2025-01-22T13:44:25Z

Inspector's Daily Report (IDR)

Clarkj25: /* Inspector's Daily Report (IDR) */

2025-01-22T13:44:08Z

Inspector's Daily Report (IDR)

Clarkj25: /* Inspector's Daily Report (IDR) */

2025-01-22T13:42:11Z

Inspector's Daily Report (IDR)

Clarkj25: /* Mobile Inspector */

2024-09-09T15:34:04Z

Mobile Inspector

Clarkj25: /* Mobile Inspector */

2024-09-09T15:33:30Z

Mobile Inspector

Clarkj25: /* Standard Rounding Convention Guidance */

2024-05-01T16:17:00Z

Standard Rounding Convention Guidance

Clarkj25: /* Revisions to Inspector Daily Reports */

2024-04-29T15:18:19Z

Revisions to Inspector Daily Reports

Clarkj25: /* Inspector's Daily Report (IDR) */

2023-08-22T15:03:07Z

Inspector's Daily Report (IDR)

Clarkj25: /* Documenting Procedures for Live and Shadow Contracts */

2023-07-13T15:07:56Z

Documenting Procedures for Live and Shadow Contracts

Clarkj25: /* FieldManager */

2023-06-01T19:46:38Z

FieldManager

@@ Line 107: / Line 107: @@
 ==[[#Inspector's Daily Report (IDR)|Inspector's Daily Report (IDR)]]==
-This information is for FieldManager contracts, for AASHTOWare contracts please see [[Inspector%E2%80%99s_Daily_Work_Report_(DWR)|Inspectors Daily Work Report (DWR) page]].   The Inspector’s Daily Report (IDR) is a significant piece of documentation that is prepared by the inspector with the objective of summarizing the Contractor’s work and progress. It is necessary that the IDR be prepared correctly, legibly, and thoroughly. At a minimum, a completed IDR will include the information listed below:
+This information is for FieldManager contracts, for AASHTOWare contracts please see [[Inspector%E2%80%99s_Daily_Work_Report_(DWR)|Inspectors Daily Work Report (DWR) page]].
 * Header information (Pre-Filled)

@@ Line 107: / Line 107: @@
 ==[[#Inspector's Daily Report (IDR)|Inspector's Daily Report (IDR)]]==
-The Inspector’s Daily Report (IDR) is a significant piece of documentation that is prepared by the inspector with the objective of summarizing the Contractor’s work and progress. It is necessary that the IDR be prepared correctly, legibly, and thoroughly. At a minimum, a completed IDR will include the information listed below:
+This information is for FieldManager contracts, for AASHTOWare contracts please see [[Inspector%E2%80%99s_Daily_Work_Report_(DWR)|Inspectors Daily Work Report (DWR) page]].   The Inspector’s Daily Report (IDR) is a significant piece of documentation that is prepared by the inspector with the objective of summarizing the Contractor’s work and progress. It is necessary that the IDR be prepared correctly, legibly, and thoroughly. At a minimum, a completed IDR will include the information listed below:
 * Header information (Pre-Filled)

@@ Line 127: / Line 127: @@
-OneSpan signatures are not to be used on IDRs.  MDOT has received FHWA approval to use pdf stamps and not signatures.  The FieldManager program coding will not be updated to remove the word “signature”.
+* OneSpan signatures are not to be used on IDRs.  MDOT has received FHWA approval to use pdf stamps and not signatures.  The FieldManager program coding will not be updated to remove the word “signature”.
-The author of the IDR cannot review their own IDR. The person reviewing the IDR does not have to be a certified office technician.
+* The author of the IDR cannot review their own IDR. The person reviewing the IDR does not have to be a certified office technician.
-The actual work performed date will be used when reporting a missed pay item on an IDR.
+* The actual work performed date will be used when reporting a missed pay item on an IDR.
-Following the proper procedures to document the project ensures federal funding participation. The 2019 Federal Highway Administration (FHWA) Compliance Assessment Program (CAP) review noted several findings related to field documentation on construction projects. FHWA and MDOT approved a targeted action plan to address Inspector Daily Reports, calculations, forms, reporting requirements, field documentation, etc.
+* Following the proper procedures to document the project ensures federal funding participation. The 2019 Federal Highway Administration (FHWA) Compliance Assessment Program (CAP) review noted several findings related to field documentation on construction projects. FHWA and MDOT approved a targeted action plan to address Inspector Daily Reports, calculations, forms, reporting requirements, field documentation, etc.
-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 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.
+* 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 including attachments, review them and turn them into the office technician.  Either the senior technician or the office technician checks all computations.  Once the check is complete and verified to be accurate, the office technician or senior technician must stamp their name at the bottom of the IDR.
+* Regardless of the method used, it is always the senior technician’s responsibility to collect all reports daily including attachments, review them and turn them into the office technician.  Either the senior technician or the office technician checks all computations.  Once the check is complete and verified to be accurate, the office technician or senior technician must stamp their name at the bottom of the IDR.
-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.
+* 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). Comments on attitude and quality of Contractor’s work may also be recorded.
+* 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). 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.
+* 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 contacting the Helpdesk email [mailto:MDOT-ConstructionSoftware@michigan.gov MDOT-ConstructionSoftware@michigan.gov].

← Older revision		Revision as of 15:34, 9 September 2024
Line 88:		Line 88:

	Information on [[Mobile_Inspector\|Mobile Inspector can be found here]].		Information on [[Mobile_Inspector\|Mobile Inspector can be found here]].
−
−	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:~~
−
−	~~[http://youtu.be/rDhzXLaIR1E 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:~~
−
−	~~[http://www.michigan.gov/documents/mdot/ugsup_loc_cns_52_516676_7.pdf User's Guide Supplements]~~
−
−	~~[//{{SERVERNAME}}/images_construction/5/5a/Managing_Info_Tech_Mobile_Inspector_within_FieldManager.pdf Mobile Inspector Device Setup Guide]~~

	===[[#FieldManager "Guest" User Account \| FieldManager "Guest" User Account]]===		===[[#FieldManager "Guest" User Account \| FieldManager "Guest" User Account]]===

@@ Line 85: / Line 85: @@
 ===[[#Mobile Inspector|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.
@@ Line 111: / Line 115: @@
 [//{{SERVERNAME}}/images_construction/5/5a/Managing_Info_Tech_Mobile_Inspector_within_FieldManager.pdf Mobile Inspector Device Setup Guide]
 ===[[#FieldManager "Guest" User Account | FieldManager "Guest" User Account]]===

← Older revision		Revision as of 16:17, 1 May 2024
Line 125:		Line 125:

	===[[#Standard Rounding Convention Guidance \| Standard Rounding Convention Guidance]]===		===[[#Standard Rounding Convention Guidance \| Standard Rounding Convention Guidance]]===
−	The Michigan Department of Transportation (MDOT) utilizes the following standard rounding convention for accuracy and consistency for all quantity postings.	+	The Michigan Department of Transportation (MDOT) utilizes the following [[Standard_Rounding_Convention_Guidance\|standard rounding convention]] for accuracy and consistency for all quantity postings.
−
−
−	~~{\| class="wikitable"~~
−	\|-
−	~~!Unit!!Type!!Accuracy~~
−	\|-
−	~~\|Acre\|\|Area\|\|0.000~~
−	\|-
−	~~\|Sft\|\|Area\|\|0.00~~
−	\|-
−	~~\|Sin\|\|Area\|\|0.00~~
−	\|-
−	~~\|Syd\|\|Area\|\|0.00~~
−	\|-
−	~~\|Dlr\|\|Dollar\|\|0.00~~
−	\|-
−	~~\|Ea\|\|Each\|\|0.00~~
−	\|-
−	~~\|Ft\|\|Length\|\|0.00~~
−	\|-
−	~~\|Lnmi\|\|Length\|\|0.000~~
−	\|-
−	~~\|Mile\|\|Length\|\|0.000~~
−	\|-
−	~~\|Rbmi\|\|Length\|\|0.000~~
−	\|-
−	~~\|Sta\|\|Length\|\|0.00~~
−	\|-
−	~~\|Cft\|\|Volume\|\|0.00~~
−	\|-
−	~~\|Cyd\|\|Volume\|\|0.00~~
−	\|-
−	~~\|Gal\|\|Volume\|\|0.00~~
−	\|-
−	~~\|Lb\|\|Weight\|\|0.00~~
−	\|-
−	~~\|Ton\|\|Weight\|\|0.00~~
−	\|}
−
−	~~Calculations should not be rounded until the final quantity value is ready to be posted. The following are some examples of how values should be rounded and posted.~~
−
−	~~<u>'''Syd'''</u>~~
−	~~<br>~~
−	~~12.25 x 55.18 = 675.955 Sft~~
−	~~::+~~
−	~~12.12 x 44.30 = 536.916 Sft~~
−	~~::+~~
−	~~1.81 x 19.54 = 35.367 Sft~~
−
−	~~'''Total:''' 1248.238 Sft / 9 Sft/Syd = 138.693 Syd~~
−
−	~~'''Posting:''' 138.69 Syd~~
−
−
−
−
−	~~<u>'''Cyd'''</u>~~
−	~~<br>~~
−	~~12.25 x 55.18 x 1.12 = 757.070 Cft~~
−	~~::+~~
−	~~12.12 x 44.31 x 1.11 = 596.111 Cft~~
−
−	~~'''Total:''' 1353.181 Cft / 27 Cft/Cyd = 50.118 Cyd~~
−
−	~~'''Posting:''' 50.12 Cyd~~
−
−
−
−
−	~~<u>'''HMA'''</u>~~
−	~~<br>~~
−	~~12 x 231 = 2,772 Sft~~
−	~~::+~~
−	~~2,772 x 1Syd/9Sft = 308 Syd~~
−
−	~~308 x 110 Lbs/Sy-In x 1.5 In = 50,820 Lbs~~
−
−	~~50,820 / 2,000 Lbs/Ton~~
−
−	~~= 25.41 Tons~~
−
−

@@ Line 292: / Line 292: @@
 :::b.  The correction(s) must be adequately documented for audit purposes and correlated on the revised IDR.
 :::c.  Every revised IDR must be a separate document.
-:3.  The document names for original and revised IDRs must follow the current [http://mdotwiki.state.mi.us/construction/index.php/E-Construction#Construction_Documentation_Standard_Naming_Conventions_for_e-Construction|MDOT Standard Naming Convention for e-Construction.]
+:3.  The document names for original and revised IDRs must follow the current [https://mdotwiki.state.mi.us/construction/index.php?title=Standard_Naming_Convention|MDOT Standard Naming Convention for e-Construction.]
 <div style="text-align: right;">[mailto:Change?body=http://mdotwiki.state.mi.us/construction/index.php/FieldManager Email this Page]</div>

← Older revision		Revision as of 15:03, 22 August 2023
Line 234:		Line 234:


−	OneSpan signatures are not to be used on IDRs. MDOT has received FHWA approval to use pdf stamps and not signatures. The ~~Field Manager~~ program coding will not be updated to remove the word “signature”.	+	OneSpan signatures are not to be used on IDRs. MDOT has received FHWA approval to use pdf stamps and not signatures. The FieldManager program coding will not be updated to remove the word “signature”.

	The author of the IDR cannot review their own IDR. The person reviewing the IDR does not have to be a certified office technician.		The author of the IDR cannot review their own IDR. The person reviewing the IDR does not have to be a certified office technician.

@@ Line 76: / Line 76: @@
 # Construction Started Date – Populate the FieldManager Docu &gt; General tab &gt; “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.
 # Contract Files – Include shadow contract documents in the original live contract files.
 # Archiving Shadow Contracts – Archive the contract in FieldManager after completing the final estimate, as is required with the live contract.
 # 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.

@@ Line 26: / Line 26: @@
 * '''FieldBuilder''' - Allows consultants and local 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 contact the FieldManager Help Desk [mailto:FieldManager-Admin@michigan.gov FieldManager-Admin@michigan.gov].
+For information on acquiring the software, self-paced FieldManager and FieldBook Tutorials, FieldManager User’s Guide, Trns*port interface or technical questions, please contact the Help Desk [mailto:MDOT-ConstructionSoftware@michigan.gov MDOT-ConstructionSoftware@michigan.gov].
 Current information on FieldManager system requirements, articles, press releases, events, presentations, license feed, etc., can be found at [http://www.fieldmanager.com www.fieldmanager.com]