<?xml version='1.0' encoding='utf-8'?>
<regulation prefix="Regulation" num=".05" citation="COMAR 11.07.06.05" title_num="11" subtitle_num="07" chapter_num="06" heading="Identification Process.">
  <paragraph num="A.">
    <text>Public-private partnership concepts and opportunities will be identified within the Authority and through other State, regional, local, and municipal processes.</text>
    <paragraph num="(1)">
      <text>Potential public-private partnership concepts and opportunities may be identified through periodic transportation planning, communication, and evaluation processes that are carried out within the Authority, the Department, and through other State, regional, local, and municipal processes, including but not limited to:</text>
      <paragraph num="(a)">
        <text>The Consolidated Transportation Program;</text>
      </paragraph>
      <paragraph num="(b)">
        <text>The Statewide Transportation Improvement Program;</text>
      </paragraph>
      <paragraph num="(c)">
        <text>Long-range transportation plans developed by metropolitan planning organizations; and</text>
      </paragraph>
      <paragraph num="(d)">
        <text>County Priority Letters.</text>
      </paragraph>
    </paragraph>
    <paragraph num="(2)">
      <text>Public-Private Partnership Candidate Concept Application.</text>
      <paragraph num="(a)">
        <text>To initiate a high-level review, screening, and policy analysis of a proposed public-private partnership concept or opportunity, a Public-Private Partnership Candidate Concept Application shall be submitted to the Steering Committee chair by an internal sponsor.</text>
      </paragraph>
      <paragraph num="(b)">
        <text>A Public-Private Partnership Candidate Concept Application may be submitted at any time, and may be supplemented with additional information as needed.</text>
      </paragraph>
      <paragraph num="(c)">
        <text>Relevant supporting information or documentation shall be included in the submission of the Public-Private Partnership Candidate Concept Application, to the extent such information is available, including but not limited to:</text>
        <paragraph num="(i)">
          <text>Preliminary ideas of public-private partnership scope, schedule, and project lifecycle considerations;</text>
        </paragraph>
        <paragraph num="(ii)">
          <text>Preliminary qualitative evaluation of relevant benefits and cost;</text>
        </paragraph>
        <paragraph num="(iii)">
          <text>Preliminary description of financial concepts;</text>
        </paragraph>
        <paragraph num="(iv)">
          <text>Rationale for a public-private partnership delivery method relative to a conventional project delivery approach; and</text>
        </paragraph>
        <paragraph num="(v)">
          <text>Additional information, as necessary, to support a high-level screening process, as outlined in Regulation .06C(1) of this chapter.</text>
        </paragraph>
      </paragraph>
      <paragraph num="(d)">
        <text>The format and required contents of the Public-Private Partnership Candidate Concept Application will be:</text>
        <paragraph num="(i)">
          <text>Developed and updated as needed by the Steering Committee; and</text>
        </paragraph>
        <paragraph num="(ii)">
          <text>Approved by the Executive Director, Chairman, and members of the Authority.</text>
        </paragraph>
      </paragraph>
    </paragraph>
  </paragraph>
  <paragraph num="B.">
    <text>Unsolicited Proposals to the Authority.</text>
    <paragraph num="(1)">
      <text>In accordance with State Finance and Procurement Article, §10A-301, Annotated Code of Maryland, the Authority is permitted to accept, reject, or evaluate unsolicited proposals for public-private partnerships that will assist the Authority in implementing its functions in a manner consistent with State policy.</text>
    </paragraph>
    <paragraph num="(2)">
      <text>Assets not defined as a transportation facilities project under Transportation Article, §4-101(h), Annotated Code of Maryland, are not covered by the Authority’s Program and should be submitted to the appropriate State agency.</text>
    </paragraph>
    <paragraph num="(3)">
      <text>An unsolicited proposal may be submitted at any time.</text>
    </paragraph>
    <paragraph num="(4)">
      <text>An unsolicited proposal shall:</text>
      <paragraph num="(a)">
        <text>Be sealed and delivered to the Authority’s Headquarters to the attention of the Executive Director, bearing the private entity’s name, address, and the words “Public-Private Partnership Unsolicited Proposal” clearly on the outside; and</text>
      </paragraph>
      <paragraph num="(b)">
        <text>Consist of 15 hardcopies and 1 electronic copy.</text>
      </paragraph>
    </paragraph>
    <paragraph num="(5)">
      <text>Unsolicited Informational Meetings.</text>
      <paragraph num="(a)">
        <text>Private entities may request meetings with the Steering Committee to discuss potential unsolicited proposals prior to submission.</text>
      </paragraph>
      <paragraph num="(b)">
        <text>Requests for unsolicited informational meetings shall be submitted to the Steering Committee chair.</text>
      </paragraph>
      <paragraph num="(c)">
        <text>The Steering Committee is not required to grant meetings in response to a request.</text>
      </paragraph>
      <paragraph num="(d)">
        <text>During unsolicited informational meetings, the Steering Committee may provide informal feedback and comments to the private entity.</text>
      </paragraph>
      <paragraph num="(e)">
        <text>The primary purpose of unsolicited informational meetings is to avoid private entities spending unnecessary time and resources on the development of unsolicited proposals that do not directly meet the State’s transportation needs.</text>
      </paragraph>
      <paragraph num="(f)">
        <text>A formal review and screening of an unsolicited proposal will be undertaken only after a private entity completes the formal submission process.</text>
      </paragraph>
    </paragraph>
    <paragraph num="(6)">
      <text>An unsolicited proposal shall be conceptual, containing only the information required for the Steering Committee to conduct a high-level review and screening of the proposed public-private partnership concept.</text>
    </paragraph>
    <paragraph num="(7)">
      <text>An unsolicited proposal shall include, at a minimum, the following:</text>
      <paragraph num="(a)">
        <text>An executive summary of the major elements of the unsolicited proposal, including:</text>
        <paragraph num="(i)">
          <text>The title of the proposed concept;</text>
        </paragraph>
        <paragraph num="(ii)">
          <text>A brief description and justification of the proposed concept;</text>
        </paragraph>
        <paragraph num="(iii)">
          <text>The name and address of the public-private partnership private entity; and</text>
        </paragraph>
        <paragraph num="(iv)">
          <text>A signature of an individual authorized to act on behalf of and bind the private entity, along with the individual’s telephone number and email address;</text>
        </paragraph>
      </paragraph>
      <paragraph num="(b)">
        <text>Summary of the experience, expertise, technical and financial competence, and professional qualifications of the private entity;</text>
      </paragraph>
      <paragraph num="(c)">
        <text>A summary narrative that describes:</text>
        <paragraph num="(i)">
          <text>The key components of the proposed public-private partnership concept;</text>
        </paragraph>
        <paragraph num="(ii)">
          <text>Preliminary ideas of public-private partnership scope, schedule, and project lifecycle considerations;</text>
        </paragraph>
        <paragraph num="(iii)">
          <text>Preliminary qualitative evaluation of relevant benefits and costs;</text>
        </paragraph>
        <paragraph num="(iv)">
          <text>Preliminary description of financial concepts;</text>
        </paragraph>
        <paragraph num="(v)">
          <text>The relevance of the public-private concept to other transportation facilities or other public infrastructure assets for which the Authority is responsible; and</text>
        </paragraph>
        <paragraph num="(vi)">
          <text>A statement of the public-private partnership concept’s consistency with existing governmental transportation planning or project documents and governing law;</text>
        </paragraph>
      </paragraph>
      <paragraph num="(d)">
        <text>A high-level description of financial feasibility that includes:</text>
        <paragraph num="(i)">
          <text>Amounts and sources of any public funding that may be required;</text>
        </paragraph>
        <paragraph num="(ii)">
          <text>How estimated funding from all relevant sources would be sufficient to support all asset delivery activities, including design, property and equipment acquisition, construction, long-term capital replacement activities, financing, operations, and maintenance; and</text>
        </paragraph>
        <paragraph num="(iii)">
          <text>How estimated funding from all relevant sources would be sufficient to provide for contingencies to meet the terms and conditions under which the public infrastructure asset shall be handed back to the Authority at the expiration or termination of the public-private partnership agreement;</text>
        </paragraph>
      </paragraph>
      <paragraph num="(e)">
        <text>Rationale for a public-private partnership delivery method relative to a conventional project delivery approach;</text>
      </paragraph>
      <paragraph num="(f)">
        <text>A clear indication of any proprietary information that should be protected in accordance with State Finance and Procurement Article, §10A-301(d)(2), Annotated Code of Maryland; and</text>
      </paragraph>
      <paragraph num="(g)">
        <text>Additional information, as necessary, to support a high-level screening process, as outlined in Regulation .06C(1) of this chapter.</text>
      </paragraph>
    </paragraph>
    <paragraph num="(8)">
      <text>Unsolicited Proposal Fee.</text>
      <paragraph num="(a)">
        <text>Each unsolicited proposal that addresses a project already in the Consolidated Transportation Program for which the Authority is responsible shall be accompanied by a check in the amount of $10,000 made payable to the Maryland Transportation Authority.</text>
      </paragraph>
      <paragraph num="(b)">
        <text>Each unsolicited proposal that does not address a project already in the Consolidated Transportation Program and concerns a public infrastructure asset for which the Authority is responsible shall be accompanied by a check in the amount of $25,000 made payable to the Maryland Transportation Authority.</text>
      </paragraph>
      <paragraph num="(c)">
        <text>The Authority reserves the right, in its sole discretion, to determine whether submitted alternates and variations of proposals will be considered separate proposals that require separate proposal fees.</text>
      </paragraph>
      <paragraph num="(d)">
        <text>Unsolicited proposal fees are nonrefundable.</text>
      </paragraph>
    </paragraph>
  </paragraph>
</regulation>