To review the rule’s requirement that all codes and standards be listed and identified in the engineering documents.  

  •  

    DEPARTMENT OF BUSINESS AND PROFESSIONAL REGULATION

    Board of Professional Engineers

    RULE NO.:RULE TITLE:

    61G15-30.003Minimum Requirements for Engineering Documents

    PURPOSE AND EFFECT: To review the rule’s requirement that all codes and standards be listed and identified in the engineering documents.

    SUMMARY: Requirements for engineering documents.

    SUMMARY OF STATEMENT OF ESTIMATED REGULATORY COSTS AND LEGISLATIVE RATIFICATION: The Agency has determined that this will not have an adverse impact on small business or likely increase directly or indirectly regulatory costs in excess of $200,000 in the aggregate within one year after the implementation of the rule. A SERC has not been prepared by the Agency.

    The Agency has determined that the proposed rule is not expected to require legislative ratification based on the statement of estimated regulatory costs or if no SERC is required, the information expressly relied upon and described herein: During discussion of the economic impact of this rule at its Board meeting, the Board, based upon the expertise and experience of its members, determined that a Statement of Estimated Regulatory Costs (SERC) was not necessary and that the rule will not require ratification by the Legislature. No person or interested party submitted additional information regarding the economic impact at that time.

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

    RULEMAKING AUTHORITY: 471.033(2), 471.008 FS.

    LAW IMPLEMENTED: 471.033(1)(g), 471.025(3) FS.

    IF REQUESTED WITHIN 21 DAYS OF THE DATE OF THIS NOTICE, A HEARING WILL BE SCHEDULED AND ANNOUNCED IN THE FAR.

    THE PERSON TO BE CONTACTED REGARDING THE PROPOSED RULE IS: Zana Raybon, Executive Director, Board of Professional Engineers, 2639 North Monroe Street, Suite B-112, Tallahassee, FL 32303, (850)521-0500

     

    THE FULL TEXT OF THE PROPOSED RULE IS:

     

    61G15-30.003 Minimum Requirements for Engineering Documents.

    (1) Engineering Documents are prepared in the course of performing engineering services. When prepared for inclusion with an application for a general building permit, the Documents shall meet all Engineer’s Responsibility Rules, set forth in Chapters 61G15-31, 61G15-32, 61G15-33, and 61G15-34, F.A.C., and be of sufficient clarity to indicate the location, nature and extent of the work proposed and show in detail that the proposed work it will conform to all the provisions of the Florida Building Code, adopted in Section 553.73, F.S., and applicable standards, codes, laws, ordinances, rules and regulations in effect at the time the Documents are sealed, signed and dated, as determined by the AHJ. The Documents shall include:

    (a)  No change.

    (b) If the Engineering Documents are intended to comply with requirements of any edition of List Federal, State, Municipal, or and County standards, codes, ordinances, laws, or and rules, other than those currently in effect, with their effective dates, that the Engineering Documents must clearly state the edition and effective dates the Documents are intended to conform to.

    (c)  through (e)  No change.

    (2) Engineers shall legibly indicate their name and business address, on Eengineering Ddocuments. Engineering Ddocuments which are issued for preliminary or conceptual use, shall clearly note the intended purpose of such Ddocuments.

    (3) When elements of the project are shown on an Eengineering Ddocument only for information or clarification and the Engineer does not intend to accept responsibility for the elements, the engineer shall clearly note on the Ddocuments the extent of his responsibility.

    (4) Engineering Documents drawings shall be legible and clearly define and delineate the work in the project. They must also comply with the requirements of Chapter 61G15-23, F.A.C., Seals.

    (5) Engineers shall clearly note on any preliminary Eengineering Ddocuments that such Ddocuments are not in final form, but are being transmitted to the AHJ public agency to receive agency reviews, comments and interpretations. The Ddocuments may subsequently be revised by the engineer to reflect resolution of issues with the AHJ public agency prior to final action by the AHJ agency. Changes, revisions and modifications to a project may prompt additional document submittal for AHJ agency approval action on the same project.

    RulemakingSpecific Authority 471.033(2), 471.008 FS. Law Implemented 471.033(1)(g), 471.025(3) FS. History–New 1-26-93, Formerly 21H-30.003, Amended 11-13-08,_________.

     

    NAME OF PERSON ORIGINATING PROPOSED RULE: Board of Professional Engineers

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

    DATE PROPOSED RULE APPROVED BY AGENCY HEAD: August 17, 2016

    DATE NOTICE OF PROPOSED RULE DEVELOPMENT PUBLISHED IN FAR: September 9, 2016

Document Information

Comments Open:
9/27/2016
Summary:
Requirements for engineering documents.
Purpose:
To review the rule’s requirement that all codes and standards be listed and identified in the engineering documents.
Rulemaking Authority:
471.033(2), 471.008 FS
Law:
471.033(1)(g), 471.025(3) FS
Contact:
Zana Raybon, Executive Director, Board of Professional Engineers, 2639 North Monroe Street, Suite B-112, Tallahassee, FL 32303; 850-521-0500.
Related Rules: (1)
61G15-30.003. Engineering Document Classification