<a id="pl.1.3"></a><var>1.3</var>design-build contracting process for certain highway construction projects.<br/>
<a id="pl.1.4"></a><var>1.4</var>BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF MINNESOTA:<br/>
<br/>
<a id="bill.0.1.0"></a><a id="pl.1.5"></a><var>1.5</var>    Section 1. <b>DESIGN-BUILD PILOT PROGRAM.</b><br/>
<a id="pl.1.6"></a><var>1.6</var>    Subdivision 1. <b>Definitions.</b> The following terms have the meanings given:<br/>
<a id="pl.1.7"></a><var>1.7</var>(1) "commissioner" means the commissioner of transportation;<br/>
<a id="pl.1.8"></a><var>1.8</var>(2) "municipality" means the board of commissioners of Anoka or Dakota County;<br/>
<a id="pl.1.9"></a><var>1.9</var>(3) "design-build contract" means a single contract between a municipality and a <br/>
<a id="pl.1.10"></a><var>1.10</var>design-build company or firm to furnish the architectural or engineering and related design <br/>
<a id="pl.1.11"></a><var>1.11</var>services as well as the labor, material, supplies, equipment, and construction services <br/>
<a id="pl.1.12"></a><var>1.12</var>for a pilot project;<br/>
<a id="pl.1.13"></a><var>1.13</var>(4) "design-build firm" means a proprietorship, partnership, limited liability <br/>
<a id="pl.1.14"></a><var>1.14</var>partnership, joint venture, corporation, any type of limited liability company, professional <br/>
<a id="pl.1.15"></a><var>1.15</var>corporation, or any legal entity;<br/>
<a id="pl.1.16"></a><var>1.16</var>(5) "design professional" means a person who holds a license under Minnesota <br/>
<a id="pl.1.17"></a><var>1.17</var>Statutes, chapter 326B, that is required to be registered under Minnesota law;<br/>
<a id="pl.1.18"></a><var>1.18</var>(6) "design-build transportation project" means the procurement of both the design <br/>
<a id="pl.1.19"></a><var>1.19</var>and construction of a pilot project in a single contract with a company or companies <br/>
<a id="pl.1.20"></a><var>1.20</var>capable of providing the necessary engineering services and construction;<br/>
<a id="pl.1.21"></a><var>1.21</var>(7) "design-builder" means the design-build firm that proposes to design and build a <br/>
<a id="pl.1.22"></a><var>1.22</var>pilot project governed by the procedures of this section;<br/>
<a id="pl.1.23"></a><var>1.23</var>(8) "pilot project" means (1) the reconstruction of the intersection at marked <br/>
<a id="pl.1.24"></a><var>1.24</var>Trunk Highway 10 and Anoka County State-Aid Highway 83, or (2) construction of <br/>
<a id="pl.2.1"></a><var>2.1</var>an interchange at marked Trunk Highway 13 and Dakota County State-Aid Highway 5 <br/>
<a id="pl.2.2"></a><var>2.2</var>in Burnsville;<br/>
<a id="pl.2.3"></a><var>2.3</var>(9) "request for proposals" or "RFP" means the document by which the municipality <br/>
<a id="pl.2.4"></a><var>2.4</var>solicits proposals from qualified design-build firms to design and construct a pilot project;<br/>
<a id="pl.2.5"></a><var>2.5</var>(10) "request for qualifications" or "RFQ" means a document to qualify potential <br/>
<a id="pl.2.6"></a><var>2.6</var>design-build firms; and<br/>
<a id="pl.2.7"></a><var>2.7</var>(11) "responsive proposal" means a technical proposal of which no major component <br/>
<a id="pl.2.8"></a><var>2.8</var>contradicts the goals of the project, significantly violates an RFP requirement, or places <br/>
<a id="pl.2.9"></a><var>2.9</var>conditions on a proposal.<br/>
<a id="pl.2.10"></a><var>2.10</var>    Subd. 2. <b>Pilot program established.</b> (a) Each municipality may participate in a <br/>
<a id="pl.2.11"></a><var>2.11</var>design-build contracting pilot program as provided in this section. If either municipality <br/>
<a id="pl.2.12"></a><var>2.12</var>determines to participate, the commissioner and each participating municipality shall <br/>
<a id="pl.2.13"></a><var>2.13</var>conduct a design-build contracting pilot program to support and evaluate the use of the <br/>
<a id="pl.2.14"></a><var>2.14</var>design-build method of contracting by counties and statutory and home rule charter cities <br/>
<a id="pl.2.15"></a><var>2.15</var>in constructing, improving, and maintaining streets and highways on the state-aid system.<br/>
<a id="pl.2.16"></a><var>2.16</var>(b) Subject to the requirements of this section and as appropriate under that <br/>
<a id="pl.2.17"></a><var>2.17</var>municipality's jurisdiction, a municipality may use the design-build method of contracting <br/>
<a id="pl.2.18"></a><var>2.18</var>for (1) reconstruction of the intersection at marked Trunk Highway 10 and Anoka County <br/>
<a id="pl.2.19"></a><var>2.19</var>State-Aid Highway 83, and (2) construction of an interchange at marked Trunk Highway <br/>
<a id="pl.2.20"></a><var>2.20</var>13 and Dakota County State-Aid Highway 5 in Burnsville.<br/>
<a id="pl.2.21"></a><var>2.21</var>    Subd. 3. <b>Licensing requirements.</b>  (a) Each design-builder shall employ, or have <br/>
<a id="pl.2.22"></a><var>2.22</var>as a partner, member, officer, coventurer, or subcontractor, a person duly licensed and <br/>
<a id="pl.2.23"></a><var>2.23</var>registered to provide the design services required to complete the project and do business <br/>
<a id="pl.2.24"></a><var>2.24</var>in the state.<br/>
<a id="pl.2.25"></a><var>2.25</var> (b) A design-builder may enter into a contract to provide professional or construction <br/>
<a id="pl.2.26"></a><var>2.26</var>services for a project that the design-builder is not licensed, registered, or qualified to <br/>
<a id="pl.2.27"></a><var>2.27</var>perform, so long as the design-builder provides those services through subcontractors with <br/>
<a id="pl.2.28"></a><var>2.28</var>duly licensed, registered, or otherwise qualified individuals in accordance with Minnesota <br/>
<a id="pl.2.29"></a><var>2.29</var>Statutes, sections 
<statute_ref>161.3410</statute_ref> to 
<statute_ref>161.3428</statute_ref>.<br/>
<a id="pl.2.30"></a><var>2.30</var>(c) Nothing in this section authorizing design-build contracts is intended to limit or <br/>
<a id="pl.2.31"></a><var>2.31</var>eliminate the responsibility or liability owed by a professional on a design-build project to <br/>
<a id="pl.2.32"></a><var>2.32</var>the state, municipality, or other third party under existing law.<br/>
<a id="pl.2.33"></a><var>2.33</var>(d) The design service portion of a design-build contract must be considered a <br/>
<a id="pl.2.34"></a><var>2.34</var>service and not a product.<br/>
<a id="pl.2.35"></a><var>2.35</var>    Subd. 4. <b>Information session for municipal engineer.</b> The commissioner or the <br/>
<a id="pl.2.36"></a><var>2.36</var>commissioner's designee with design-build experience shall conduct an information <br/>
<a id="pl.3.1"></a><var>3.1</var>session for the municipality's engineer for each pilot project, in which issues unique to <br/>
<a id="pl.3.2"></a><var>3.2</var>design-build must be discussed, including, but not limited to, writing an RFP, project <br/>
<a id="pl.3.3"></a><var>3.3</var>oversight requirements, assessing risk, and communication with the design-build firm. <br/>
<a id="pl.3.4"></a><var>3.4</var>After participation in the information session, the municipality's engineer may solicit <br/>
<a id="pl.3.5"></a><var>3.5</var>proposals under subdivision 6 for the pilot project.<br/>
<a id="pl.3.6"></a><var>3.6</var>    Subd. 5. <b>Technical Review Committee.</b> During the phase one RFQ and before <br/>
<a id="pl.3.7"></a><var>3.7</var>solicitation, the municipality shall appoint a Technical Review Committee of at least <br/>
<a id="pl.3.8"></a><var>3.8</var>five individuals. The Technical Review Committee must include an individual whose <br/>
<a id="pl.3.9"></a><var>3.9</var>name and qualifications are submitted to the municipality by the Minnesota chapter of <br/>
<a id="pl.3.10"></a><var>3.10</var>the Associated General Contractors, after consultation with other commercial contractor <br/>
<a id="pl.3.11"></a><var>3.11</var>associations in the state. Members of the Technical Review Committee who are not state <br/>
<a id="pl.3.12"></a><var>3.12</var>employees are subject to the Minnesota Government Data Practices Act and Minnesota <br/>
<a id="pl.3.13"></a><var>3.13</var>Statutes, section 
<statute_ref>16C.06,</statute_ref> to the same extent that state agencies are subject to those <br/>
<a id="pl.3.14"></a><var>3.14</var>provisions. A Technical Review Committee member may not participate in the review or <br/>
<a id="pl.3.15"></a><var>3.15</var>discussion of responses to the RFQ or RFP when a design-build firm in which the member <br/>
<a id="pl.3.16"></a><var>3.16</var>has a financial interest has responded to the RFQ or RFP. "Financial interest" includes, <br/>
<a id="pl.3.17"></a><var>3.17</var>but is not limited to, being or serving as an owner, employee, partner, limited liability <br/>
<a id="pl.3.18"></a><var>3.18</var>partner, shareholder, joint venturer, family member, officer, or director of a design-build <br/>
<a id="pl.3.19"></a><var>3.19</var>firm responding to an RFQ or RFP for a specific project, or having any other economic <br/>
<a id="pl.3.20"></a><var>3.20</var>interest in that design-build firm. The members of the Technical Review Committee must <br/>
<a id="pl.3.21"></a><var>3.21</var>be treated as municipal employees in the event of litigation resulting from any action <br/>
<a id="pl.3.22"></a><var>3.22</var>arising out of their service on the committee.<br/>
<a id="pl.3.23"></a><var>3.23</var>    Subd. 6. <b>Phase one; design-build RFQ.</b> The municipality shall prepare an RFQ, <br/>
<a id="pl.3.24"></a><var>3.24</var>which must include the following:<br/>
<a id="pl.3.25"></a><var>3.25</var>(1) the minimum qualifications of design-builders necessary to meet the requirements <br/>
<a id="pl.3.26"></a><var>3.26</var>for acceptance;<br/>
<a id="pl.3.27"></a><var>3.27</var>(2) a scope of work statement and schedule;<br/>
<a id="pl.3.28"></a><var>3.28</var>(3) documents defining the project requirements;<br/>
<a id="pl.3.29"></a><var>3.29</var>(4) the form of contract to be awarded;<br/>
<a id="pl.3.30"></a><var>3.30</var>(5) the weighted selection criteria for compiling a short list and the number of firms <br/>
<a id="pl.3.31"></a><var>3.31</var>to be included in the short list, which must be at least two but not more than five;<br/>
<a id="pl.3.32"></a><var>3.32</var>(6) a description of the request for proposals (RFP) requirements;<br/>
<a id="pl.3.33"></a><var>3.33</var>(7) the maximum time allowed for design and construction;<br/>
<a id="pl.3.34"></a><var>3.34</var>(8) the municipality's estimated cost of design and construction;<br/>
<a id="pl.3.35"></a><var>3.35</var>(9) requirements for construction experience, design experience, financial, personnel, <br/>
<a id="pl.3.36"></a><var>3.36</var>and equipment resources available from potential design-builders for the project and <br/>
<a id="pl.4.1"></a><var>4.1</var>experience in other design-build transportation projects or similar projects, provided that <br/>
<a id="pl.4.2"></a><var>4.2</var>these requirements may not unduly restrict competition; and<br/>
<a id="pl.4.3"></a><var>4.3</var>(10) a statement that "past performance" or "experience" or other criteria used in the <br/>
<a id="pl.4.4"></a><var>4.4</var>RFQ evaluation process does not include the exercise or assertion of a person's legal rights.<br/>
<a id="pl.4.5"></a><var>4.5</var>    Subd. 7. <b>Information session for prospective design-build firms.</b> After an RFQ <br/>
<a id="pl.4.6"></a><var>4.6</var>solicitation for a pilot project is made, any prospective design-build firm shall attend a <br/>
<a id="pl.4.7"></a><var>4.7</var>design-build information session conducted by the commissioner or the commissioner's <br/>
<a id="pl.4.8"></a><var>4.8</var>designee with design-build experience. The information must include information about <br/>
<a id="pl.4.9"></a><var>4.9</var>design-build contracts, including, but not limited to, communication with partner firms, <br/>
<a id="pl.4.10"></a><var>4.10</var>project oversight requirements, assessing risk, and communication with the municipality's <br/>
<a id="pl.4.11"></a><var>4.11</var>engineer. After participation in the information session, the design-build firm is eligible <br/>
<a id="pl.4.12"></a><var>4.12</var>to bid on the pilot project and any future design-build pilot program projects under this <br/>
<a id="pl.4.13"></a><var>4.13</var>section.<br/>
<a id="pl.4.14"></a><var>4.14</var>    Subd. 8. <b>Evaluation; short list.</b> The selection team shall evaluate the design-build <br/>
<a id="pl.4.15"></a><var>4.15</var>qualifications of responding firms and shall compile a short list of no more than five <br/>
<a id="pl.4.16"></a><var>4.16</var>most highly qualified firms in accordance with qualifications criteria described in the <br/>
<a id="pl.4.17"></a><var>4.17</var>RFQ. If only one design-build firm responds to the RFQ or remains on the short list, the <br/>
<a id="pl.4.18"></a><var>4.18</var>municipality may readvertise or cancel the project as the municipality deems necessary.<br/>
<a id="pl.4.19"></a><var>4.19</var>    Subd. 9. <b>Phase two; design-build RFP.</b> The municipality shall prepare an RFP, <br/>
<a id="pl.4.20"></a><var>4.20</var>which must include:<br/>
<a id="pl.4.21"></a><var>4.21</var>(1) the scope of work, including (i) performance and technical requirements, (ii) <br/>
<a id="pl.4.22"></a><var>4.22</var>conceptual design, (iii) specifications, and (iv) functional and operational elements for <br/>
<a id="pl.4.23"></a><var>4.23</var>the delivery of the completed project, all of which must be prepared by a registered or <br/>
<a id="pl.4.24"></a><var>4.24</var>licensed professional engineer;<br/>
<a id="pl.4.25"></a><var>4.25</var>(2) copies of the contract documents that the successful proposer will be expected to <br/>
<a id="pl.4.26"></a><var>4.26</var>sign;<br/>
<a id="pl.4.27"></a><var>4.27</var>(3) the maximum time allowable for design and construction;<br/>
<a id="pl.4.28"></a><var>4.28</var>(4) the road authority's estimated cost of design and construction;<br/>
<a id="pl.4.29"></a><var>4.29</var>(5) the requirement that a submitted proposal be segmented into two parts, a <br/>
<a id="pl.4.30"></a><var>4.30</var>technical proposal and a price proposal;<br/>
<a id="pl.4.31"></a><var>4.31</var>(6) the requirement that each proposal be in a separately sealed, clearly identified <br/>
<a id="pl.4.32"></a><var>4.32</var>package and include the date and time of the submittal deadline;<br/>
<a id="pl.4.33"></a><var>4.33</var>(7) the requirement that the technical proposal include a critical path method, <br/>
<a id="pl.4.34"></a><var>4.34</var>bar schedule of the work to be performed, or similar schematic; preliminary design <br/>
<a id="pl.4.35"></a><var>4.35</var>plans and specifications; technical reports; calculations; permit requirements; applicable <br/>
<a id="pl.4.36"></a><var>4.36</var>development fees; and other data requested in the RFP;<br/>
<a id="pl.5.1"></a><var>5.1</var>(8) the requirement that the price proposal contain all design, construction, <br/>
<a id="pl.5.2"></a><var>5.2</var>engineering, inspection, and construction costs of the proposed project;<br/>
<a id="pl.5.3"></a><var>5.3</var>(9) the date, time, and location of the public opening of the sealed price proposals; <br/>
<a id="pl.5.4"></a><var>5.4</var>(10) the amount of, and eligibility for, a stipulated fee;<br/>
<a id="pl.5.5"></a><var>5.5</var>(11) other information relevant to the project; and<br/>
<a id="pl.5.6"></a><var>5.6</var>(12) a statement that "past performance," "experience," or other criteria used in the <br/>
<a id="pl.5.7"></a><var>5.7</var>RFP evaluation process does not include the exercise or assertion of a person's legal rights.<br/>
<a id="pl.5.8"></a><var>5.8</var>    Subd. 10. <b>Design-build award; computation; announcement.</b> (a) A design-build <br/>
<a id="pl.5.9"></a><var>5.9</var>contract must be awarded as follows.<br/>
<a id="pl.5.10"></a><var>5.10</var>(b) The Technical Review Committee shall score the technical proposals of the <br/>
<a id="pl.5.11"></a><var>5.11</var>proposers selected under subdivision 8 using the selection criteria in the RFP. The <br/>
<a id="pl.5.12"></a><var>5.12</var>Technical Review Committee shall then submit a technical proposal score for each <br/>
<a id="pl.5.13"></a><var>5.13</var>design-builder to the municipality. The Technical Review Committee shall reject any <br/>
<a id="pl.5.14"></a><var>5.14</var>nonresponsive proposal. The municipality shall review the technical proposal scores.<br/>
<a id="pl.5.15"></a><var>5.15</var>(c) The commissioner or the commissioner's designee shall review the technical <br/>
<a id="pl.5.16"></a><var>5.16</var>proposal scores. The commissioner shall submit the final technical proposal scores to the <br/>
<a id="pl.5.17"></a><var>5.17</var>municipality.<br/>
<a id="pl.5.18"></a><var>5.18</var>(d) The municipality shall announce the technical proposal score for each <br/>
<a id="pl.5.19"></a><var>5.19</var>design-builder and shall publicly open the sealed price proposals and shall divide each <br/>
<a id="pl.5.20"></a><var>5.20</var>design-builder's price by the technical score that the commissioner has given to it to obtain <br/>
<a id="pl.5.21"></a><var>5.21</var>an adjusted score. The design-builder selected must be that responsive and responsible <br/>
<a id="pl.5.22"></a><var>5.22</var>design-builder whose adjusted score is the lowest.<br/>
<a id="pl.5.23"></a><var>5.23</var>(e) If a time factor is included with the selection criteria in the RFP package, the <br/>
<a id="pl.5.24"></a><var>5.24</var>municipality may use a value of the time factor established by the municipality as a <br/>
<a id="pl.5.25"></a><var>5.25</var>criterion in the RFP.<br/>
<a id="pl.5.26"></a><var>5.26</var>(f) Unless all proposals are rejected, the municipality shall award the contract <br/>
<a id="pl.5.27"></a><var>5.27</var>to the responsive and responsible design-builder with the lowest adjusted score. The <br/>
<a id="pl.5.28"></a><var>5.28</var>municipality shall reserve the right to reject all proposals.<br/>
<a id="pl.5.29"></a><var>5.29</var>(g) The municipality shall award a stipulated fee not less than two-tenths of <br/>
<a id="pl.5.30"></a><var>5.30</var>one percent of the municipality's estimated cost of design and construction to each <br/>
<a id="pl.5.31"></a><var>5.31</var>short-listed, responsible proposer who provides a responsive but unsuccessful proposal. <br/>
<a id="pl.5.32"></a><var>5.32</var>If the municipality does not award a contract, all short-listed proposers must receive the <br/>
<a id="pl.5.33"></a><var>5.33</var>stipulated fee. If the municipality cancels the contract before reviewing the technical <br/>
<a id="pl.5.34"></a><var>5.34</var>proposals, the municipality shall award each design-builder on the short list a stipulated <br/>
<a id="pl.5.35"></a><var>5.35</var>fee of not less than two-tenths of one percent of the municipality's estimated cost of <br/>
<a id="pl.5.36"></a><var>5.36</var>design and construction. The municipality shall pay the stipulated fee to each proposer <br/>
<a id="pl.6.1"></a><var>6.1</var>within 90 days after the award of the contract or the decision not to award a contract. <br/>
<a id="pl.6.2"></a><var>6.2</var>In consideration for paying the stipulated fee, the municipality may use any ideas or <br/>
<a id="pl.6.3"></a><var>6.3</var>information contained in the proposals in connection with any contract awarded for the <br/>
<a id="pl.6.4"></a><var>6.4</var>project or in connection with a subsequent procurement, without any obligation to pay <br/>
<a id="pl.6.5"></a><var>6.5</var>any additional compensation to the unsuccessful proposers. Notwithstanding the other <br/>
<a id="pl.6.6"></a><var>6.6</var>provisions of this subdivision, an unsuccessful short-list proposer may elect to waive <br/>
<a id="pl.6.7"></a><var>6.7</var>the stipulated fee. If an unsuccessful short-list proposer elects to waive the stipulated <br/>
<a id="pl.6.8"></a><var>6.8</var>fee, the municipality may not use ideas and information contained in that proposer's <br/>
<a id="pl.6.9"></a><var>6.9</var>proposal. Upon the request of the municipality, a proposer who waived a stipulated fee <br/>
<a id="pl.6.10"></a><var>6.10</var>may withdraw the waiver, in which case the municipality shall pay the stipulated fee to the <br/>
<a id="pl.6.11"></a><var>6.11</var>proposer and thereafter may use ideas and information in the proposer's proposal.<br/>
<a id="pl.6.12"></a><var>6.12</var>    Subd. 11. <b>Low-bid design-build process.</b> (a) The municipality may also use <br/>
<a id="pl.6.13"></a><var>6.13</var>low-bid, design-build procedures to award a design-build contract where the scope of <br/>
<a id="pl.6.14"></a><var>6.14</var>the work can be clearly defined.<br/>
<a id="pl.6.15"></a><var>6.15</var>(b) Low-bid design-build projects may require an RFQ and short-listing, and must <br/>
<a id="pl.6.16"></a><var>6.16</var>require an RFP.<br/>
<a id="pl.6.17"></a><var>6.17</var>(c) Submitted proposals under this subdivision must include separately a technical <br/>
<a id="pl.6.18"></a><var>6.18</var>proposal and a price proposal. The low-bid, design-build procedures must follow a <br/>
<a id="pl.6.19"></a><var>6.19</var>two-step process for review of the responses to the RFP as follows:<br/>
<a id="pl.6.20"></a><var>6.20</var>(1) the first step is the review of the technical proposal by the Technical Review <br/>
<a id="pl.6.21"></a><var>6.21</var>Committee as provided in subdivision 5. The Technical Review Committee must open <br/>
<a id="pl.6.22"></a><var>6.22</var>the technical proposal first and must determine if it complies with the requirements of the <br/>
<a id="pl.6.23"></a><var>6.23</var>RFP and is responsive. The Technical Review Committee may not perform any ranking <br/>
<a id="pl.6.24"></a><var>6.24</var>or scoring of the technical proposals; and<br/>
<a id="pl.6.25"></a><var>6.25</var>(2) the second step is the determination of the low bidder based on the price <br/>
<a id="pl.6.26"></a><var>6.26</var>proposal. The municipality may not open the price proposal until the review of the <br/>
<a id="pl.6.27"></a><var>6.27</var>technical proposal is complete.<br/>
<a id="pl.6.28"></a><var>6.28</var>(d) The contract award under low-bid, design-build procedures must be made to the <br/>
<a id="pl.6.29"></a><var>6.29</var>proposer whose sealed bid is responsive to the technical requirements as determined by <br/>
<a id="pl.6.30"></a><var>6.30</var>the Technical Review Committee and that is also the lowest bid.<br/>
<a id="pl.6.31"></a><var>6.31</var>(e) A stipulated fee may be paid for unsuccessful bids on low-bid, design-build <br/>
<a id="pl.6.32"></a><var>6.32</var>projects only when the municipality has required an RFQ and short-listed the most highly <br/>
<a id="pl.6.33"></a><var>6.33</var>qualified responsive bidders.<br/>
<a id="pl.6.34"></a><var>6.34</var>    Subd. 12. <b>Legislative report.</b> By December 15, 2011, the commissioner shall <br/>
<a id="pl.6.35"></a><var>6.35</var>submit a report on the pilot program to the chairs and ranking minority members of the <br/>
<a id="pl.7.1"></a><var>7.1</var>house of representatives and senate committees with jurisdiction over transportation <br/>
<a id="pl.7.2"></a><var>7.2</var>policy and finance. The report must, at a minimum:<br/>
<a id="pl.7.3"></a><var>7.3</var>(1) summarize each pilot project, including the contracting process and project costs;<br/>
<a id="pl.7.4"></a><var>7.4</var>(2) evaluate the process and results applying the performance-based measures with <br/>
<a id="pl.7.5"></a><var>7.5</var>which the commissioner evaluates trunk highway design-build projects; and<br/>
<a id="pl.7.6"></a><var>7.6</var>(3) identify any recommendations for future legislation.<br/>
<a id="pl.7.7"></a><var>7.7</var><b>EFFECTIVE DATE.</b>This section is effective the day following final enactment.<br/>