61G15-23.005 Procedures for Electronically Signing and Sealing Electronically Transmitted Plans, Specifications, Reports or Other Documents.
(1) Engineering plans, specifications, reports or other documents which must be signed, dated and sealed in accordance with the provisions of Section 471.025, F.S., and Rule 61G15-23.001, F.A.C. may be signed electronically as provided herein by the professional engineer in responsible charge. As used herein, the term “electronic signature” shall have the meanings ascribed to them in Sections 668.003(2), (3) and (4), F.S.
(2) A professional engineer utilizing an electronic signature to electronically sign and seal engineering plans, specifications, reports or other documents using the Florida Department of Transportation (FDOT) Professionals’ Electronic Data Delivery System (PEDDS) software shall:
(a) Create a “signature” file that contains the licensee’s given name, the licensee’s license number, a brief overall description of the engineering documents to be signed and sealed, a list of the electronic files to be signed and sealed, and the SHA-1 authentication code or Secure Hash Standard for each electronic file to be signed and sealed. The SHA-1 authentication code is described in Federal Information Processing Standard Publication 180-4 “Secure Hash Standard,” August 2015, which is hereby adopted and incorporated by reference by the Board and can be obtained from the Internet Website:
http://www.flrules.org/Gateway/reference.asp?No=Ref-05976.
(b) Create a “signature” report that contains the licensee’s given name, the licensee’s license number, a brief overall description of the engineering documents to be signed and sealed and the SHA-1 authentication code of the signature file;
(c) Print and manually sign, date and seal the signature report in compliance with Rule 61G15-23.003, F.A.C.;
(d) Transmit the signed, dated and sealed signature report to the receiving party along with the signed, dated and sealed signature file, either by hardcopy or electronic scan, if scanned and sent electronically. The hardcopy signed and sealed report shall be retained by the licensee in accordance with Rule 61G15-30.009; and,
(e) The signature file is considered to be signed and sealed if the signature file’s authentication code matches the authentication code on the manually signed, dated and sealed signature report. Each electronic file listed within the signed and sealed signature file is considered to be signed and sealed if the listed SHA-1 authentication code in the signature file matches the electronic file’s SHA-1 authentication code.
(3) A professional engineer utilizing an electronic signature to electronically sign and seal engineering plans, specifications, reports or other documents other than through the FDOT PEDDS system shall:
(a) Create a static electronic version, such as PDF, of the engineering document(s) that is to be signed and sealed;
(b) Compute an SHA-1 authentication code for each electronic engineering document;
(c) Create a printable “signature report” that contains the licensee’s given name, the licensee’s license number, and a list of the electronic files to be signed and sealed that includes a brief description of each engineering document and the SHA-1 authentication code of each engineering document;
(d) Print and manually sign, date and seal the “signature report” in compliance with Rule 61G15-23.003, F.A.C.; and,
(e) Transmit the signed, dated and sealed “signature report” to the receiving party along with each electronically signed, dated and sealed engineering document either by hardcopy or electronic scan, if scanned and sent electronically. The hardcopy signed and sealed report shall be retained by the licensee in accordance with Rule 61G15-30.009, F.A.C. Each engineering document is considered to be electronically signed and sealed if the document’s SHA-1 authentication code matches the SHA-1 authentication code on the physically signed, dated and sealed “signature report.”
(4) The affixing of an electronic signature to engineering plans, specifications, reports or other documents as provided herein shall constitute the signing and sealing of such items.
(a) A digitally created seal as set forth in Rule 61G15-23.002, F.A.C. may be placed where it would appear if the item were being physically signed, dated and sealed.
(b) The date that the electronic signature is to be placed into the document must appear on the document in accordance with subsection 61G15-23.001(5), F.A.C. and where it would appear if the item were being physically signed, dated and sealed.
(c) A scanned, facsimile, digitally created or copied image of the licensee’s signature shall not be used on electronically signed and sealed engineering plans, specifications, reports or other documents.
(d) The engineering plans, specifications, reports or other documents being electronically signed and sealed shall include text to indicate the following and place it where an original signature would appear if the item were being physically signed, dated and sealed:
1. The same information required by subsection 61G15-23.002(2), F.A.C. if a digitally created seal is not used,
2. The item has been electronically signed and sealed using a SHA-1 authentication codes; and,
3. Printed copies of the document are not considered signed and sealed and all SHA-1 authentication code must be verified on any electronic copies.
(e) Formatting of seals and text similar to that depicted below may be used.
1. When a digitally created seal is used:
seal here | This item has been electronically signed and sealed by C. S. Hammatt, PE. On [DATE] using a SHA-1 authentication code.
Printed copies of this document are not considered signed and sealed and the SHA-1 authentication code must be verified on any electronic copies. |
2. When a digitally created seal is not used:
C. S. Hammatt, State of Florida, Professional Engineer, License No. X
This item has been electronically signed and sealed by C. S. Hammatt, PE. On [DATE] using a SHA-1 authentication code.
Printed copies of this document are not considered signed and sealed and the SHA-1 authentication code must be verified on any electronic copies.
|
Rulemaking Authority 471.025(1), 471.033(2), 471.008 FS. Law Implemented 471.025, 668.006 FS. History–New 11-3-15, Amended 2-3-16, 10-26-16.