The Board proposes the rule amendment to delete unnecessary language and to modify language to update the Federal Information Processing Standard Publication and to provide the website address where the standards can be downloaded.

 

DEPARTMENT OF BUSINESS AND PROFESSIONAL REGULATION
Board of Professional Engineers

RULE NO.: RULE TITLE:
61G15-23.003: Procedures for Signing and Sealing Electronically Transmitted Plans, Specifications, Reports or Other Documents

PURPOSE AND EFFECT: The Board proposes the rule amendment to delete unnecessary language and to modify language to update the Federal Information Processing Standard Publication and to provide the website address where the standards can be downloaded.

SUMMARY: The rule amendment will delete unnecessary language and to modify language to update the Federal Information Processing Standard Publication and to provide the website address where the standards can be downloaded.

SUMMARY OF STATEMENT OF ESTIMATED REGULATORY COST:

The Board determined that a Statement of Estimated Regulatory Cost (SERC) was not necessary. The Board has determined that this will not have an adverse impact on small business, or likely increase regulatory costs in excess of $200,000 in the aggregate within 1 year after implementation of the rule. These rule amendments will not require ratification by the Legislature.

Any person who wishes to provide information regarding the statement of estimated costs, or to provide a proposal for a lower regulatory cost alternative must do so in writing within 21 days of this notice.

RULEMAKING AUTHORITY: 471.025(1), 668.006 FS.
LAW IMPLEMENTED: 471.025 FS.

IF REQUESTED WITHIN 21 DAYS OF THE DATE OF THIS NOTICE, A HEARING WILL BE ANNOUNCED IN THE NEXT AVAILABLE FLORIDA ADMINISTRATIVE WEEKLY.

THE PERSON TO BE CONTACTED REGARDING THE PROPOSED RULE IS: Carrie Flynn, Executive Director, Board of Professional Engineers, 2507 Callaway Road, Suite 200, Tallahassee, Florida 32303-5268

 

THE FULL TEXT OF THE PROPOSED RULE IS:

61G15-23.003 Procedures for Signing and Sealing Electronically Transmitted Plans, Specifications, Reports or Other Documents.

(1) through (2) No change.

(3) A professional engineer utilizing an electronic signature to seal engineering work shall create a “signature” file that contains the engineer’s name and PE number, a brief overall description of the engineering documents, and a list of the electronic files to be sealed. Each file in the list shall be identified by its file name utilizing relative Uniform Resource Locators (URL) syntax described in the Internet Architecture Board’s Request for Comments (RFC) 1738, December 1994, which is hereby adopted and incorporated by reference by the Board and can be obtained from the Internet Website: http://ftp.isi.edu/in-notes/rfc1738.txt. Each file shall have an authentication code defined as an SHA-1 message digest described in Federal Information Processing Standard Publication 180-31 “Secure Hash Standard,” October 2008 1995 April 17, which is hereby adopted and incorporated by reference by the Board and can be obtained from the Internet Website: http://csrc.nist.gove/publications/fips/fips180-3/fips180-3final.pdf http://www.itl.nist.gov/div897/pubs/ fip180-1.htm. The licenses shall then create a report that contains the engineer’s name and PE number, a brief overall description of the engineering documents in question and the authentication code of the signature file. This report shall be printed and manually signed, dated, and sealed by the professional engineer in responsible charge. The signature file is defined as sealed if the signature file’s authentication code matches the authentication code on the printed, manually signed, dated and sealed report. Each electronic file listed in a sealed signature file is defined as sealed if the listed authentication code in the signature file matches the electronic file’s computed authentication code.

Rulemaking Authority 471.025(1), 668.006 FS. Law Implemented 471.025 FS. History–New 8-18-98, Amended 9-4-05, 5-6-09,________.

 

NAME OF PERSON ORIGINATING PROPOSED RULE: Board of Professional Engineers

NAME AGENCY HEAD WHO APPROVED THE PROPOSED RULE: Board of Professional Engineers

DATE PROPOSED RULE APPROVED BY AGENCY HEAD: July 19, 2011

DATE NOTICE OF PROPOSED RULE DEVELOPMENT PUBLISHED IN FAW: September 30, 2011