Difference between revisions of "E-Signature"

From MediaWiki
Jump to navigation Jump to search
 
(58 intermediate revisions by 5 users not shown)
Line 1: Line 1:
−
 
+
<div style="text-align: center;">[mailto:Change?body=http://mdotwiki.state.mi.us/construction/index.php/E-Signature Email this Page]</div>
−
 
 
−
<center><span STYLE="font: 40pt arial;">'''Division 1 Supplemental Information'''</span></center>
 
−
<center><span STYLE="font: 30pt arial;">'''e-Signature'''</span></center>
 
−
 
 
  
 
====[[#General Information|General Information]]====
 
====[[#General Information|General Information]]====
  
−
According to the Code of Federal Regulation, electronic signatures are defined as a computer data compilation of any symbol or series of symbols executed, adopted, or authorized by an individual to be the legally binding equivalent of the individual's handwritten signature.   A specific type of electronic signature is digital signatures.  Digital signatures are defined as an electronic signature based upon cryptographic methods of originator authentication, computed by using a set of rules and a set of parameters such that the identity of the signer and the integrity of the data can be verified.  
+
In 2004 FHWA issued direction that according to the Code of Federal Regulation,[https://www.ecfr.gov/cgi-bin/text-idx?SID=c961274a08c1423164e297c9d95b4e02&node=pt29.1.5&rgn=div5 29 CFR 3.3 Part 5 Federal Contract Law Provisions] electronic signatures are defined as a computer data compilation of any symbol or series of symbols executed, adopted, or authorized by an individual to be the legally binding equivalent of the individual's handwritten signature. [https://www.fhwa.dot.gov/construction/cqit/111204dol.cfm Read FHWA Direction on Electronic Signatures] A specific type of electronic signature is digital signatures.  Digital signatures are defined as an electronic signature based upon cryptographic methods of originator authentication, computed by using a set of rules and a set of parameters such that the identity of the signer and the integrity of the data can be verified.  
  
 
An entity such as a computer user can be assigned a unique digital identification.  This digital identification is composed of a public key, a private key, and a digital certificate.  As their names suggest, the public key should be shared amongst users who wish to carry out transactions amongst themselves, while the private key should be only known by its user.  The digital certificate is used within a public-key infrastructure to allow a third-party certificate authority to verify that the digital certificate is correctly associated with that particular public key.
 
An entity such as a computer user can be assigned a unique digital identification.  This digital identification is composed of a public key, a private key, and a digital certificate.  As their names suggest, the public key should be shared amongst users who wish to carry out transactions amongst themselves, while the private key should be only known by its user.  The digital certificate is used within a public-key infrastructure to allow a third-party certificate authority to verify that the digital certificate is correctly associated with that particular public key.
Line 16: Line 12:
  
 
====[[#Adoption at MDOT and Acceptable Uses|Adoption at MDOT and Acceptable Uses]]====
 
====[[#Adoption at MDOT and Acceptable Uses|Adoption at MDOT and Acceptable Uses]]====
−
The Michigan Attorney General’s office, in concurrence of the Federal Highway Administration, has issued a decision authorizing the Michigan Department of Transportation (MDOT) to use and accept digital signatures (see [http://www.michigan.gov/documents/mdot/MDOT_IM12-02_378056_7.pdf BOH IM 2012-02]).
+
The Michigan Attorney General’s office, in concurrence of the Federal Highway Administration, issued a decision in 2011 authorizing the Michigan Department of Transportation (MDOT) to use and accept digital signatures.
 
    
 
    
−
There are many standards available for digital signatures, but MDOT currently authorizes the use of PKCS#12 files for digital identification.  This cryptographic standard requires the signer to enter their unique password each time they digitally sign a document.  To digitally sign a document, you must first have a digital identification (ID).  This ID can be obtained from various certification authorities, but MDOT will primarily use Adobe as a certification authority.  [http://www.michigan.gov/documents/mdot/Setting_Up_an_Electronic_Signature_422066_7.pdf This PDF file] and [http://www.youtube.com/watch?v=pUIWvJgkw8E this YouTube video, produced by Adobe Acrobat,] shows how to create a digital ID on Adobe Reader.
+
The Department approved process is to use the OneSpan Sign ID Verification & Acceptance Electronic signature Solution (OneSpan), and OneSpan Sign Mobile Applications for document signing processes. More information regarding OneSpan digital signature can be found here: [https://www.michigan.gov/mdot/Business/digital-signature MDOT Digital Signature Program].  
−
 
 
−
Digital signatures created with Adobe Software need to conform to the following style guidelines:
 
−
*Graphic options shall be:
 
−
**“Name” Or “Imported Graphic” (as outlined below)
 
−
 
 
−
*Configure text shall be configured as:
 
−
**Uncheck the adobe “logo”
 
−
**Required to include: (“Name”, “Date”, “Location” and “Reason”)
 
−
**Optional “Distinguished Name” (includes job title)
 
−
**Optional for “labels”
 
−
**“left to right”
 
−
You may have multiple digital signature files configured for different purposes. It is even possible to configure a digital signature with an “Imported Graphic” (refer to this [http://www.michigan.gov/documents/mdot/Applying_an_Image_To_Digital_Signature_422061_7.pdf PDF]) containing an image of your scanned written signature or a scan of a professional license stamp. These are acceptable, but written signature images are not required and non-business related graphics are not acceptable.
 
−
 
 
−
Similar to how handwritten signatures must be verified, it is the responsibility of the recipient of a electronically signed document to confirm the identity of the signer/sender before the electronic signature may be considered valid.  The recipient should consider whether or not that the document was sent from a recognized e-mail account and that the expected signer has been previously validated.  If you are unsure, then you can verify by contacting their place of business.  Adobe Acrobat software has an integrated validation feature that stores validated signatures, meaning that the user does not need to validate those signatures again.  This [http://www.michigan.gov/documents/mdot/Trusting_and_Validating_a_Digital_Signature_422068_7.pdf PDF] shows how to validate a signature.
 
−
 
 
−
MDOT is working on integration of electronic signatures on mobile devices.  There are several mobile applications that allow PDF files to be digitally signed using mobile devices, but as of now none have been authorized for employee use.  Employees are encouraged to submit mobile applications to the E-Sign team of the Construction Field Services Division and to the Department of Technology, Management and Budget.  This  [http://www.michigan.gov/documents/mdot/How_To_Add_A_Digital_Signature_Via_iPhone_422065_7.pdf PDF] shows how to digitally sign a PDF file on an iPhone.
 
−
 
 
−
It is important to note that for records retention and archiving purposes whenever digital signatures are used on documents, the electronic file (usually PDF) is considered the original legal document.  Printouts of the document containing digital signatures are considered copies, so the signed electronic file must be retained and follow the relevant approved records retention procedures.  MDOT will address the records storage issue through the requirement that all electronically signed documents must be placed in the project directory in the ProjectWise document management program.  The E-construction [http://mdotwiki.state.mi.us/construction/index.php/E-Construction wiki page] contains more information regarding ProjectWise.  
 
 
{{top}}
 
{{top}}
  
 
====[[#Guidance for Non-MDOT Users|Guidance for Non-MDOT Users]]====
 
====[[#Guidance for Non-MDOT Users|Guidance for Non-MDOT Users]]====
  
−
An individual’s digital signature must be validated before MDOT can accept the signature.  [http://mdotcf.state.mi.us/public/webforms/public/5600.pdf Form 5600] for contractors and [http://mdotcf.state.mi.us/public/webforms/public/5600A.pdf Form 5600A] for consultants allows an individual to submit their digital signature to MDOT. When you select the signature box when filling out these forms, you can use an existing digital ID or you can create a new ID. There are many ways an individual can obtain a digital ID, but the preferred way is to use Adobe software. These forms will be on file with MDOT until the individual’s digital signature certificate expires or until such time as the individual needs to create a new digital signature.
+
External user guidance can be found in the MDOT special provision for [https://mdotjboss.state.mi.us/SpecProv/getDocumentById.htm?docGuid=c5cf0ff9-f732-4145-97c6-f5f4eef29768&fileName=%2220SP-104C-02.pdf%22 Construction Document Management 20SP-104C-02] and on the MDOT digital signature website: [https://www.michigan.gov/mdot/Business/digital-signature MDOT Digital Signature Program].
 +
 
 +
<div style="text-align: right;">[mailto:Change?body=http://mdotwiki.state.mi.us/construction/index.php/E-Signature Email this Page]</div>
 +
{{top}}
  
−
====[[#What is Digital Signature Validation and why does it matter?|What is digital Signature Validation and why does it matter?]]====
+
====[[#Transition to OneSpan|Transition to OneSpan]]====
 +
Construction Field Services owns over 250 forms, many of which were affected by migrating from DocuSign to OneSpan. Documents signed in OneSpan cannot have text revisions after the first signature is placed unless a created Template or Layout exists to allow for that process. The signature process may not be intuitive for some users and many forms may look different than they have previously. Signature fields have been removed from many MDOT forms as we refocus on areas where signatures are necessary. Signatures are still being placed on multiple party agreements, contract documents and amendments to contracts, and other forms as indicated on the form itself.  Forms will specify what the expectation is for the authorization required.  Forms may specify one of the following:
  
−
All signatures must be authenticated to determine the identity of the document signer(s) and it is the legal requirement that anyone receiving a signature from an external party must authenticate the signature on the document they receive (paper or electronic).  While handwritten signatures have visual indicators that help us determine someone’s real signature, the digital signature process is much faster and more secure.  However, digital signatures can also be falsely created by other parties and made to look very similar to the authentic digital signatures, so care must be taken to determine the true identity of the signers.  The process to determine the authenticity of digital signatures is referred to as signature validation.
+
:* '''Signature'''  If a signature is being requested, that signature must take place in OneSpan.   
  
−
Validation is the process that authenticates the electronic signature on a document and compares it to the known validated signature on file.
+
:* '''Stamp'''  If an approval stamp/dynamic stamp/pdf review stamp is requested, this stamp is built into in all pdf creator applications, and all stamps from all pdf creators are acceptable.  Stamps must include the individual’s name, and the date & time must be embedded within the stamp.  The individual may use pdf stamps, non-OneSpan pdf signatures or even OneSpan signatures as long the minimum components of Name, Date and Time are included in the applied stamp.
  
−
In general, the electronic signature validation process occurs primarily in the background of the software and only requires us to take action the first time a signature is received.  A valid digital signature proves that the message was created by a known sender; such that the sender cannot deny having sent the message (authentication and non-repudiation) and that the message was not altered in transit (integrity).  This is accomplished by the use of an algorithm that creates unique encrypted codes associated with the digital signature for the user.  In general, each digital signature has two main components.  The first is a private key code that is encrypted into the signature which is essentially the user’s password used to affix their signature.  The second component is called the public key code which is a unique complex code embedded into the signature that allows other parties to easily authenticate the true identity of the signer.  Each digital signatures public code is unique to the digital signature, not the person, thus if you have two digital signatures each has its own unique code, they are not the same.  When a sender signs a document their private key remains with them, but the public key is embedded into the signature on the document.  When the document is sent to the recipient, the recipient’s computer compares the unique public code in the signature to the list of known validated signature codes.  If the codes match then the signature is considered valid and proves the signature was made by the sender.  If the codes do not match, the software indicates the signature has not been validated.  If this occurs the recipient is required to perform the validation process as described in the next section of this BOH IM.  (Note the graphic process describing the validation process is presented in Attachment 1; e-Signature Validation Process Overview of this BOH IM.)
+
:* '''Name'''  In some cases, a typed name is acceptable.  A signature or stamp may also be applied, as they meet the minimum requirement of supplying a name in the required field.
  
−
Effective immediately, the process for validating Digital Electronic Signature (DES) received by MDOT from any external party will be as follows:
+
It is prudent that all users are directing themselves to the MDOT forms repository to ensure they are using the most current form in all scenarios.
  
−
:1. External Parties:
+
====[[#Tranistion to OneSpan – Frequently Asked Signature Questions|Tranistion to OneSpan – Frequently Asked Signature Questions]]====
  
−
::a. All external parties (non-MDOT/FHWA), intending to use DES on any documents to be submitted to MDOT, must submit form 5600 Statement of Digital Electronic Signature Validation to the local MDOT office for validation of the DES prior to (or concurrent with) the DES being used on any documents submitted to MDOT.
+
Please see below for instructions on some of MDOT’s forms:
  
−
::b. Form 5600 must be submitted for each individual DES the first time the signature is used on a project.  This can be submitted concurrently with a document; however, the document will not be accepted until the validation process has been completed.
+
* '''Inspectors Daily Report - IDR'''
 +
:Please note guidance listed in Construction Manual Inspector’s Daily Report. Note that the text stating (Signature) is legacy text associated with FieldManager and will not/can not be removed. A pdf review stamp is the mandatory approval action for this document. Transition to AASHTOWare Project will negate the need for this instruction as the Department moves away from FieldManager.  
  
−
::c. Most DES certificates expire after four (4) years from the initial date of the DES creation. It is the responsibility of the signature creator to maintain their DES and create a new DES when their current DES expires.  Form 5600, once validated, will allow the use of the DES on other documents submitted to MDOT until the DES expires (including on other projects or in other offices).
+
* '''Form 1302 FED - Subcontract form'''
 +
:Contractor signatures may be of any legal signature type. Complete and return a copy of the cover page and pay item page(s) to the Engineer prior to any subcontract work beginning.  
  
−
::d. If the DES owner changes employment, position, responsibilities, forgets the DES password, or loses the DES file, this will require that a new form 5600 be submitted for the new signature.
+
* '''Form 0501 – Materials Source List'''
 +
:All signature fields have been removed from this form. Document does not require signature in OneSpan and instead simply requires typed name of Engineering and Contractor staff reviewing and providing information for this form.
  
−
:2. MDOT Office:
+
* '''Pay Estimates
 +
:Previous guidance required electronic signatures on all pay estimates.  Dynamic PDF stamps noting the approver’s name, date and time are now acceptable to be used to document pay estimate approval.  See revised guidance in the Construction Manual for Construction Pay Estimate Approvals.  Transition to AASHTOWare Project will negate the need for this instruction as the Department moves away from FieldManager.
  
−
Any document received by MDOT containing a DES must be checked for proper validation prior to acceptance.  This can be confirmed via the blue signature panel validation process at the top of the document in Adobe Acrobat (Figure 1).
+
* '''Form 1100A – Extension of Contract Time – Request Number'''
 +
:All signature fields have been removed from this form. Document does not require signature in OneSpan and instead simply requires typed name of Engineering staff reviewing and approving the Extension of Time request. Note that Site Supervisor/Foreman/Contractor provided designee must be copied on this final document to ensure mutual understanding of items that will be paid or unpaid as a part of any perspective time extension.
  
−
Figure 1: Screen showing blue signature panel in Adobe Standard XI
+
* '''Form 1165 – Notice of Non-Compliance with Contract Requirements'''
 +
:Form 1165 must be signed as two distinct processes: The Non-Compliance portion, and the Resume Work Portion. Two layouts are necessary in OneSpan to achieve one completed form. The steps necessary for completion of this form can be found here: [https://mdotwiki.state.mi.us/images_construction/c/cc/1165_Signature_Process.pdf 1165 Signature Process]
  
−
[[File:IM14Fig1.png|200px|thumb|center|alt text]]
+
* '''Form 0582B - Moisture and Density Determination'''
 +
:The signature field has been replaced with an “Approval Stamp”.
  
  
−
If the digital electronic signatures on the document have already been authenticated, the software will clearly confirm this with the green checkmark as shown below in Figure 2.
+
<div style="text-align: right;">[mailto:Change?body=http://mdotwiki.state.mi.us/construction/index.php/E-Signature Email this Page]</div>
−
 
+
{{top}}
−
[[File:IM14Fig2.png|200px|thumb|center|alt text]]
 
−
 
 
−
 
 
−
If electronic documents come into the office with a non-validated DES, (figure 3 below),
 
−
 
 
−
[[File:IM14Fig3.png|200px|thumb|center|alt text]]
 
−
 
 
−
then the office must determine the validity of the document signers.  If the signature does not match the previously validated signature codes on file the office must reject the document until a new form 5600 is submitted and the DES can be validated. '''It is the legal responsibility of the first person who receives any signature to verify the validity of the signature before accepting any documents.'''  After the signature has been validated and added to the trusted list of validated signatures, the software will re-validate and display the green check mark.  The completion of the form 5600 is only required when a signature is first used, subsequent documents will be validated automatically for that user.  It may take a while for the central office database updates to be distributed to all other users, so until that occurs a signer can send along a copy of the fully completed form 5600 to the new office where they can manually add the validated signature to their trusted identities.
 
−
 
 
−
In the case of multiple signatures on the same document, the software clearly identifies the signatures that have not been validated as shown in figure 4 below.
 
−
 
 
−
 
 
−
[[File:IM14Fig4.png|200px|thumb|center|alt text]]
 
−
 
 
−
 
 
−
The software also automatically tracks all changes made to the document.  This is important because by the very act of signing a document, the document has changed from the version the first person saw.  Any major changes to the document that affect the integrety of the encrypted digital signatures will invalidate or delete the signatures, but minor changes like multiple signers will just be noted.
 
−
 
 
−
Should an office receive a document or form 5600 that requries them to validate the digital signature the process is simple and straightforeward.
 
−
 
 
−
The validation process is detailed on form 5600 and the receiver must verify at least two (2) of the four (4) federal signature authentication requirements outlined below:
 
−
 
 
−
::a. The name of the sender is the same name expected.
 
−
::b. E-mail from a company domain e-mail address.
 
−
::c. Direct contact with sender verifying they sent the document with signature.
 
−
::d. Verification via another method with provided details.
 
−
 
 
−
The MDOT recipient of the document is then required to indicate which two methods were used to verify the signature is actually from the recipient and then confirm their validation efforts by placing their own digital signature on the form.  This form is then routed to the central office for archiving and a copy of the completed form returned to the sender for their records or for submission to other offices until the central database is updated.
 
−
::a. MDOT office staff that receives form 5600 will go through and complete the validation steps per the form instructions.
 
−
 
 
−
::b. Once the DES is validated, the validating MDOT office staff will countersign form 5600. 
 
−
 
 
−
::c. MDOT office staff will then add the validated signature to their trusted identities.  Instructions for manually adding a validated signature to your trusted identities can be found on the MDOT WIKI Construction Manual in Division 1 Supplemental Information, e-Sign section. 
 
−
[[E-Signature|http://mdotwiki.state.mi.us/construction/index.php/E-Signature]]
 
−
 
 
−
:d. MDOT office staff will then submit the completed form 5600 to
 
−
[mailto:MDOT-eSign@michigan.gov MDOT-eSign@michigan.gov] and also back to the submitting applicant.
 
−
 
 
−
:3. MDOT-Central Office:
 
−
 
 
−
::a. MDOT Central Office staff will receive form 5600 via the
 
−
[mailto:MDOT-eSign@michigan.gov MDOT-eSign@michigan.gov] e-mail address.  MDOT Central Office staff will then maintain these 5600 forms in a centralized server for archiving purposes, update export files of all previously validated DES, and send these validated DES out to MDOT staff periodically.
 
−
 
 
−
If you have any questions, contact[mailto:MDOT-eSign@michigan.gov MDOT-eSign@michigan.gov].  Please share this information with consultants and local agencies within your area.
 
−
 
 
−
====[[#Resources|Resources]]====
 
−
 
 
−
{| class="wikitable"
 
−
|-
 
−
! File Name !! Description
 
−
|-
 
−
| [//{{SERVERNAME}}/images_construction/f/fa/Setting_Up_an_Electronic_Signature.pdf Setting Up an Electronic Signature] || Creating a Digital Identity with Adobe Acrobat||
 
−
|-
 
−
| [//{{SERVERNAME}}/images_construction/5/5d/How_To_Add_A_Digital_Signature_Via_iPhone_422065_7.pdf How To Add A Digital Signature Via iPhone] || Creating a Digital Signature on any iOS smart device
 
−
|-
 
−
| [//{{SERVERNAME}}/images_construction/a/a6/E-sign_brochure.pdf E-sign brochure] || A brief outline concering various facets of E-signatures
 
−
|-
 
−
|[http://www.youtube.com/watch?v=pUIWvJgkw8E How to Digitally Sign a document with Adobe Reader]||A YouTube video published by Adobe about how to digitally sign a PDF file with the free Adobe Reader
 
−
|-
 
−
|[http://www.michigan.gov/documents/mdot/Applying_an_Image_To_Digital_Signature_422061_7.pdf Applying an Image To Digital Signature]|| How to import and insert an image to a digital signature
 
−
|-
 
−
|[http://www.michigan.gov/documents/mdot/Trusting_and_Validating_a_Digital_Signature_422068_7.pdf Trusting and Validating a Digital Siganture]|| How to trust and validate a signature in Adobe Acrobat
 
−
|-
 
−
|}
 
  
  
  
 
[[Category: Construction Manual]]
 
[[Category: Construction Manual]]
 +
[[Category: Division 1]]
 +
[[Category: Division 1 Supplemental]]

Latest revision as of 15:30, 20 September 2023

Email this Page

General Information

In 2004 FHWA issued direction that according to the Code of Federal Regulation,29 CFR 3.3 Part 5 Federal Contract Law Provisions electronic signatures are defined as a computer data compilation of any symbol or series of symbols executed, adopted, or authorized by an individual to be the legally binding equivalent of the individual's handwritten signature. Read FHWA Direction on Electronic Signatures A specific type of electronic signature is digital signatures. Digital signatures are defined as an electronic signature based upon cryptographic methods of originator authentication, computed by using a set of rules and a set of parameters such that the identity of the signer and the integrity of the data can be verified.

An entity such as a computer user can be assigned a unique digital identification. This digital identification is composed of a public key, a private key, and a digital certificate. As their names suggest, the public key should be shared amongst users who wish to carry out transactions amongst themselves, while the private key should be only known by its user. The digital certificate is used within a public-key infrastructure to allow a third-party certificate authority to verify that the digital certificate is correctly associated with that particular public key.

As public keys are shared amongst a group of users, someone’s public key can be used to encrypt a document and their respective private key can be used to decrypt that document. Confidentiality and data integrity of the sent document can be practically guaranteed assuming if the recipient is the only one who knows their private key. Similarly, someone’s private key can be ‘embedded’ into a document to constitute an electronic signature, and the identity of the electronic signature may be verified by using that user’s public key.

[top of page]

Adoption at MDOT and Acceptable Uses

The Michigan Attorney General’s office, in concurrence of the Federal Highway Administration, issued a decision in 2011 authorizing the Michigan Department of Transportation (MDOT) to use and accept digital signatures.

The Department approved process is to use the OneSpan Sign ID Verification & Acceptance Electronic signature Solution (OneSpan), and OneSpan Sign Mobile Applications for document signing processes. More information regarding OneSpan digital signature can be found here: MDOT Digital Signature Program.

[top of page]

Guidance for Non-MDOT Users

External user guidance can be found in the MDOT special provision for Construction Document Management 20SP-104C-02 and on the MDOT digital signature website: MDOT Digital Signature Program.

Email this Page

[top of page]

Transition to OneSpan

Construction Field Services owns over 250 forms, many of which were affected by migrating from DocuSign to OneSpan. Documents signed in OneSpan cannot have text revisions after the first signature is placed unless a created Template or Layout exists to allow for that process. The signature process may not be intuitive for some users and many forms may look different than they have previously. Signature fields have been removed from many MDOT forms as we refocus on areas where signatures are necessary. Signatures are still being placed on multiple party agreements, contract documents and amendments to contracts, and other forms as indicated on the form itself. Forms will specify what the expectation is for the authorization required. Forms may specify one of the following:

  • Signature If a signature is being requested, that signature must take place in OneSpan.
  • Stamp If an approval stamp/dynamic stamp/pdf review stamp is requested, this stamp is built into in all pdf creator applications, and all stamps from all pdf creators are acceptable. Stamps must include the individual’s name, and the date & time must be embedded within the stamp. The individual may use pdf stamps, non-OneSpan pdf signatures or even OneSpan signatures as long the minimum components of Name, Date and Time are included in the applied stamp.
  • Name In some cases, a typed name is acceptable. A signature or stamp may also be applied, as they meet the minimum requirement of supplying a name in the required field.

It is prudent that all users are directing themselves to the MDOT forms repository to ensure they are using the most current form in all scenarios.

Tranistion to OneSpan – Frequently Asked Signature Questions

Please see below for instructions on some of MDOT’s forms:

  • Inspectors Daily Report - IDR
Please note guidance listed in Construction Manual Inspector’s Daily Report. Note that the text stating (Signature) is legacy text associated with FieldManager and will not/can not be removed. A pdf review stamp is the mandatory approval action for this document. Transition to AASHTOWare Project will negate the need for this instruction as the Department moves away from FieldManager.
  • Form 1302 FED - Subcontract form
Contractor signatures may be of any legal signature type. Complete and return a copy of the cover page and pay item page(s) to the Engineer prior to any subcontract work beginning.
  • Form 0501 – Materials Source List
All signature fields have been removed from this form. Document does not require signature in OneSpan and instead simply requires typed name of Engineering and Contractor staff reviewing and providing information for this form.
  • Pay Estimates
Previous guidance required electronic signatures on all pay estimates. Dynamic PDF stamps noting the approver’s name, date and time are now acceptable to be used to document pay estimate approval. See revised guidance in the Construction Manual for Construction Pay Estimate Approvals. Transition to AASHTOWare Project will negate the need for this instruction as the Department moves away from FieldManager.
  • Form 1100A – Extension of Contract Time – Request Number
All signature fields have been removed from this form. Document does not require signature in OneSpan and instead simply requires typed name of Engineering staff reviewing and approving the Extension of Time request. Note that Site Supervisor/Foreman/Contractor provided designee must be copied on this final document to ensure mutual understanding of items that will be paid or unpaid as a part of any perspective time extension.
  • Form 1165 – Notice of Non-Compliance with Contract Requirements
Form 1165 must be signed as two distinct processes: The Non-Compliance portion, and the Resume Work Portion. Two layouts are necessary in OneSpan to achieve one completed form. The steps necessary for completion of this form can be found here: 1165 Signature Process
  • Form 0582B - Moisture and Density Determination
The signature field has been replaced with an “Approval Stamp”.


Email this Page

[top of page]

Retrieved from "https://mdotwiki.state.mi.us/construction/index.php?title=E-Signature&oldid=7629"