<?xml version='1.0' encoding='utf-8'?>
<baltimore-city-law heading="Title 14 – Department of Transportation">
  <container prefix="Subtitle" num="01" heading="Alley Gating">
    <container prefix="Chapter" num="01" heading="Documents Incorporated by Reference">
      <section prefix="Regulation" num=".01" heading="Documents Incorporated by Reference.">
        <text>All provisions of the Baltimore City Department of Transportation Book of Standards (2025) are incorporated by reference to &lt;cite data-path="14"&gt;this Title&lt;/cite&gt;.</text>
      </section>
    </container>
  </container>
  <container prefix="Subtitle" num="02" heading="Dockless Vehicles">
    <container prefix="Chapter" num="01" heading="General Provisions">
      <section prefix="Regulation" num=".01" heading="Scope.">
        <text>&lt;cite data-path="14.02.01"&gt;This chapter&lt;/cite&gt; establishes rules and regulations for the operation of dockless vehicles in Baltimore City.</text>
      </section>
      <section prefix="Regulation" num=".02" heading="Definitions.">
        <para num="A.">In &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;, the following terms have the meanings indicated.</para>
        <para num="B.">Terms Defined.<para num="(1)">Adaptive Dockless Vehicle.<para num="(a)">“Adaptive dockless vehicle” means a dockless vehicle that is accessible to people with a physical disability.</para>
            <para num="(b)">“Adaptive dockless vehicle” includes a motorized or non-motorized:<para num="(a)">Recumbent bicycle;</para>
              <para num="(b)">Tricycle; and</para>
              <para num="(c)">Hand cycle.</para>
            </para>
          </para>
          <para num="(2)">Alternative Deployment Location.<para num="(a)">“Alternative deployment location” means an area other than a public street.</para>
            <para num="(b)">“Alternative deployment location” includes:<para num="(i)">A park;</para>
              <para num="(ii)">A plaza;</para>
              <para num="(iii)">A parking lot;</para>
              <para num="(iv)">Private property; or</para>
              <para num="(v)">A transit station.</para>
            </para>
          </para>
          <para num="(3)">Applicant.<para num="(a)">“Applicant” means a person applying for an initial dockless vehicle permit.</para>
            <para num="(b)">“Applicant” does not include a permit holder applying for the renewal of a dockless vehicle permit.</para>
          </para>
          <para num="(4)">“Application Programming Interface endpoint (API)” means a protocol that enables a software application to:<para num="(a)">Communicate with another platform; or</para>
            <para num="(b)">Exchange data.</para>
          </para>
          <para num="(5)">“Beta endpoint” means an API endpoint that has been officially released in a testing mode by its regulatory authority but not formally adopted.</para>
          <para num="(6)">“Block face” means one side of a street between the intersection of two other streets, excluding an alleyway.</para>
          <para num="(7)">“Community event” means an event held by:<para num="(a)">A community organization as recognized by the City’s Online Community Association Directory; or</para>
            <para num="(b)">Another organization as deemed appropriate by the Director.</para>
          </para>
          <para num="(8)">“Compliance score” means a calculation of a permit holder’s compliance with the provisions of &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;.</para>
          <para num="(9)">“CPSC” means the U.S. Consumer Product Safety Commission.</para>
          <para num="(10)">“Department” means the Baltimore City Department of Transportation.</para>
          <para num="(11)">“Deployment” means the location where a dockless vehicle is placed by a permit holder when it is made available for rent.</para>
          <para num="(12)">“Deployment district” means a geographic area designated in the Department’s MDS Policy API for tracking the distribution of dockless vehicles.</para>
          <para num="(13)">“Director” means the Director of the Department of Transportation.</para>
          <para num="(14)">“Dockless corral” means a geographic location designated by the Department where a dockless vehicle may be parked.</para>
          <para num="(15)">“Dockless vehicle” has the meaning stated in &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-1|(b)"&gt;City Code Article 31, § 38-1(b)&lt;/cite&gt;.</para>
          <para num="(16)">“E-bike” has the meaning stated in &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-1|(d)"&gt;City Code Article 31, § 38-1(d)&lt;/cite&gt;.</para>
          <para num="(17)">"E-scooter" has the meaning stated in &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-1|(e)"&gt;City Code Article 31, § 38-1(e)&lt;/cite&gt;.</para>
          <para num="(18)">“Equitable access” means a process of making dockless vehicles available to the public by removing barriers to use including:<para num="(a)">Geography;</para>
            <para num="(b)">Income;</para>
            <para num="(c)">Banking status; or</para>
            <para num="(d)">Inclusion in a federally protected class.</para>
          </para>
          <para num="(19)">“Equity zone” means a geographic location where a dockless vehicle is deployed for equitable access as designated in the official document provided by the Department to a permit holder.</para>
          <para num="(20)">“Fleet” means the total number of dockless vehicles operated by a permit holder in Baltimore City, regardless of whether they are available for rent.</para>
          <para num="(21)">“Genetic information” means genetic markers related to a person’s medical history, including the manifestation of a:<para num="(a)">Disease; or</para>
            <para num="(b)">Disorder.</para>
          </para>
          <para num="(22)">“Geo-fencing” means a location-based service that uses GPS or cellular data to identify when a mobile device or dockless vehicle enters or exits a virtual geographic boundary.</para>
          <para num="(23)">“GitHub” means a code hosting platform.</para>
          <para num="(24)">“Low-income population” means a person whose family income is at or below 150 percent of the poverty line</para>
          <para num="(25)">“MDS” means Mobility Data Specification.</para>
          <para num="(26)">“MDS Policy API” means the Open Mobility Foundation standards and code available on GitHub for secure mobility data exchange.</para>
          <para num="(27)">“New permit holder” means a provider of dockless vehicles who has:<para num="(a)">Not previously been issued a permit to operate on a public street by the Department; or</para>
            <para num="(b)">Not held a permit in the previous year.</para>
          </para>
          <para num="(28)">Non-deployment Request.<para num="(a)">“Non-deployment request” means a request from a member of the public to prevent the deployment of a dockless vehicle in front of their property.</para>
            <para num="(b)">“Non-deployment request” includes a vehicle deployed by a dockless vehicle permit holder.</para>
            <para num="(c)">“Non-deployment request” does not include a vehicle parked by a user.</para>
          </para>
          <para num="(29)">“OMF” means Open Mobility Foundation.</para>
          <para num="(30)">“Overconcentration” means the deployment of more than 25 percent of a permit holder’s fleet in a single deployment district.</para>
          <para num="(31)">“Payment Card Industry Data Security Standards” means the set of guidelines designed to ensure companies that process credit card information maintain a secure environment.</para>
          <para num="(32)">“Parking corral” means an area designated by the Department where a dockless vehicle may be parked.</para>
          <para num="(33)">“Permit” means a dockless vehicle permit as provided in &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-8"&gt;City Code Article 31, § 38-8&lt;/cite&gt;.</para>
          <para num="(34)">“Permit agreement” means a document that is entered into between the City and a permit holder that:<para num="(a)">Stipulates required insurance coverage for a permit holder to operate in Baltimore City;</para>
            <para num="(b)">Stipulates that the permit holder is obligated to adhere to applicable laws and regulations to operate in Baltimore City; and</para>
            <para num="(c)">Outlines procedures for the cessation of operations prior to the end of a permit.</para>
          </para>
          <para num="(35)">“Permit holder” means a provider of dockless vehicles who has been issued a permit by the Department to operate on a public street.</para>
          <para num="(36)">“Permit year” means the period from July 1 to June 30 annually.</para>
          <para num="(37)">“Person” has the meaning stated in &lt;cite data-doc="Md. Code" data-path="ggp|1-107"&gt;General Provisions Article § 1-107, &lt;/cite&gt;City Code.</para>
          <para num="(38)">“Referral agency” means a government assistance program that provides services to individuals who qualify as low-income.</para>
          <para num="(39)">&lt;em&gt;“&lt;/em&gt;Remote shut down notice” means a written communication from the Department sent via e-mail to a permit holder instructing the permit holder to shut down the entirety or a portion of their fleet in Baltimore City.</para>
          <para num="(40)">Seizure.<para num="(a)">“Seizure” means the act of removing a dockless vehicle in violation of &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt; from:<para num="(i)">City property; or</para>
              <para num="(ii)">An area inaccessible to a permit holder.</para>
            </para>
            <para num="(b)">“Seizure” includes the act of:<para num="(i)">Towing;</para>
              <para num="(ii)">Impoundment; and</para>
              <para num="(iii)">Retrieval from a body of water.</para>
            </para>
          </para>
          <para num="(41)">“Speed governor” means a device that ensures the motor of a dockless vehicle is incapable of traveling at a speed in excess of a mandated speed limit on level ground.</para>
          <para num="(42)">“Street” has the meaning stated in &lt;cite data-doc="Md. Code" data-path="ggp|1-109"&gt;General Provisions Article § 1-109, &lt;/cite&gt;City Code.</para>
          <para num="(43)">“Third-party” means a person that is not the permit holder that may access data related to the operation of dockless vehicles.</para>
          <para num="(44)">“Third-party aggregator” means an organization that processes data from one or more sources for use by the City.</para>
          <para num="(45)">“Towing Division” means the Baltimore City Department of Transportation’s Towing Division.</para>
          <para num="(46)">“Tree pit” means an area of the street where a tree is planted.</para>
          <para num="(47)">“Underserved population” means a group of people that:<para num="(a)">Has limited or no access to resources; or</para>
            <para num="(b)">Is otherwise disenfranchised.</para>
          </para>
          <para num="(48)">“Vehicle model” means a vehicle of the certain type, but with different features or appearance.</para>
          <para num="(49)">“Vehicle type” means a vehicle that meets specifications in the City’s vehicle code for that vehicle.</para>
          <para num="(50)">“Web Content Accessibility Guidelines (WCAG)” means guidelines published by the World Wide Web Consortium's Web Accessibility Initiative to make web content accessible.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".03" heading="Permits - Applications.">
        <para num="A.">An applicant shall submit an application for a dockless vehicle permit in accordance with the information published on the Department’s website regarding submission processes.</para>
        <para num="B.">At the time of submission, an applicant shall ensure their application contains:<para num="(1)">An operations plan that includes:<para num="(a)">Hours and days of operation, including relevant limitations;</para>
            <para num="(b)">Procedures for responding to extreme weather events;</para>
            <para num="(c)">Procedures for responding to special events;</para>
            <para num="(d)">Procedures for responding to complaints;</para>
            <para num="(e)">Procedures for ensuring availability of dockless vehicles in each deployment district; and</para>
            <para num="(f)">Procedures and avoiding overconcentration of the applicant’s fleet in a single deployment district; and</para>
          </para>
          <para num="(2)">A maintenance plan that includes:<para num="(a)">Procedures for ensuring that the applicant’s fleet is:<para num="(i)">Safe for public use; and</para>
              <para num="(ii)">Well-maintained;</para>
            </para>
            <para num="(b)">A schedule for inspection of the applicant’s fleet;</para>
            <para num="(c)">A description of the training method used for the applicant’s mechanics;</para>
            <para num="(d)">A description of the life expectancy for each component of a dockless vehicle; and</para>
            <para num="(e)">A method of long-term monitoring to ensure the condition of vehicles in the applicant’s fleet.</para>
          </para>
        </para>
        <para num="C.">An applicant shall notify the Department of a change to the noted requirements in &lt;cite data-path="14.02.01.03|B."&gt;§B of this regulation&lt;/cite&gt;.</para>
      </section>
      <section prefix="Regulation" num=".04" heading="Permits - Fees.">
        <para num="A.">A permit holder shall remit a fee for the issuance of a revocable dockless vehicle permit within 30 days of being awarded the permit.</para>
        <para num="B.">The Board of Estimates shall:<para num="(1)">Approve the cost of the fee, which will include the cost of:<para num="(a)">Issuing the permit;</para>
            <para num="(b)">Program administration;</para>
            <para num="(c)">Associated infrastructure;</para>
            <para num="(d)">Education;</para>
            <para num="(e)">Enforcement; and</para>
            <para num="(f)">Program evaluation; and</para>
          </para>
          <para num="(2)">Disclose the cost of the fee to a permit applicant before the application deadline.</para>
        </para>
        <para num="C.">If a permit holder’s permit is revoked, the Department may not refund a permitting fee paid by the permit holder for the current permit cycle.</para>
      </section>
      <section prefix="Regulation" num=".05" heading="Permits - Issuance.">
        <para num="A.">The Department may issue up to three dockless vehicle permits annually through:<para num="(1)">A renewal of an existing permit; or</para>
          <para num="(2)">A competitive application process.</para>
        </para>
        <para num="B.">Except as provided in &lt;cite data-path="14.02.01.05|C."&gt;§C of this regulation&lt;/cite&gt;, a permit holder shall maintain a daily fleet of two or more vehicle types.</para>
        <para num="C.">If a permit holder administers an adaptive vehicle program, the permit holder may maintain a fleet of a single vehicle type.</para>
        <para num="D.">If a permit holder fails to meet one or more of the standards in &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;, the Department shall:<para num="(1)">Review the performance of the permit holder under the permit issued; and</para>
          <para num="(2)">Assess the violation for a citation in accordance with &lt;cite data-path="14.02.01.26"&gt;regulation .26 of this chapter&lt;/cite&gt;.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".06" heading="Permits - Renewal.">
        <para num="A.">Eligibility Requirements.
A permit holder shall be eligible to renew a permit if the permit holder:<para num="(1)">Has not had a violation in the permit year prior; and</para>
          <para num="(2)">Is in good standing to conduct business in the State of Maryland.</para>
        </para>
        <para num="B.">Renewal Process.
A permit holder may renew a permit by:<para num="(1)">Signing a renewal agreement that includes current rules and regulations; and</para>
          <para num="(2)">Remitting an annual fee in accordance with &lt;cite data-path="14.02.01.04"&gt;regulation .04 of this chapter&lt;/cite&gt;.</para>
        </para>
        <para num="C.">The Department may renew a permit if a permit holder meets the eligibility requirements in &lt;cite data-path="14.02.01.06|A."&gt;§A of this regulation&lt;/cite&gt;.</para>
      </section>
      <section prefix="Regulation" num=".07" heading="Permits - Revocation.">
        <para num="A.">The Department may revoke a permit in accordance with &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-13"&gt;City Code Article 31, § 38-13&lt;/cite&gt;.</para>
        <para num="B.">Revocation Hearing Procedures.<para num="(1)">A permit holder may request a hearing to determine whether sufficient facts exist to revoke a permit.</para>
          <para num="(2)">The Department shall:<para num="(a)">Designate a time and place for a revocation hearing;</para>
            <para num="(b)">Provide the permit holder with notice of the hearing at least ten business days before the scheduled date; and</para>
            <para num="(c)">Provide an opportunity for the permit holder to be heard at the hearing.</para>
          </para>
          <para num="(3)">A permit holder may:<para num="(a)">Waive the right to an in-person hearing for the revocation of a permit; and</para>
            <para num="(b)">Submit a written opposition to the revocation before the scheduled hearing date in accordance with &lt;cite data-path="14.02.01.07|B.|(4)"&gt;§B(4) of this regulation&lt;/cite&gt;.</para>
          </para>
          <para num="(4)">A permit holder shall submit written opposition to:</para>
          <para num="(5)">Following the hearing or the review of a written opposition, the Department shall record its findings of fact in writing.</para>
          <para num="(6)">The Director may revoke a permit if:<para num="(a)">The Department finds that sufficient grounds exist to revoke a permit; and</para>
            <para num="(b)">The Department provides at least five days’ written notice to the permit holder in advance of the revocation.</para>
          </para>
        </para>
        <para num="C.">A permit holder may appeal the revocation of a dockless vehicle permit to the Director.</para>
      </section>
      <section prefix="Regulation" num=".08" heading="Deployment.">
        <para num="A.">In General.<para num="(1)">A permit holder shall ensure that a dockless vehicle is deployed in compliance with City Code Article 31, § 38-19, Unlawful Parking.</para>
          <para num="(2)">A permit holder shall provide an account for its mobile application to the Department so that Department employees can access a dockless vehicle for free for the purposes of:<para num="(a)">Education;</para>
            <para num="(b)">A routine vehicle inspection; or</para>
            <para num="(c)">Vehicle repositioning.</para>
          </para>
          <para num="(3)">A permit holder shall apply speed geo-fencing to a dockless vehicle by using a speed governor to establish a City-wide speed limit of 15 mph except for:<para num="(a)">In a reduced speed zone as defined in the Department’s MDS Policy API where speeds are limited to eight mph; and</para>
            <para num="(b)">In a no ride zone as defined in the Department’s MDS Policy API where a dockless vehicle is limited to a speed of no more than three mph.</para>
          </para>
        </para>
        <para num="B.">Deployment District Requirements.<para num="(1)">On each day of service, a permit holder shall deploy to each deployment district:<para num="(a)">A minimum of 5 percent of their fleet; and</para>
            <para num="(b)">A maximum of 25 percent of their fleet.</para>
          </para>
          <para num="(2)">Compliance.
The Department shall:<para num="(a)">Evaluate daily compliance with the requirements in &lt;cite data-path="14.02.01.08|B.|(1)"&gt;§B(1) of this regulation&lt;/cite&gt; based on at least one hour of compliance between 5:00 a.m. and 9:0 a.m.; and</para>
            <para num="(b)">Notify a permit holder in violation of the requirements in &lt;cite data-path="14.02.01.08|B.|(1)"&gt;§B(1) of this regulation&lt;/cite&gt; via a compliance score notification.</para>
          </para>
          <para num="(3)">A permit holder shall redistribute their fleet within three hours of receipt of a compliance score notification from the Department.</para>
        </para>
        <para num="C.">Equitable Deployment Requirements.<para num="(1)">A permit holder shall deploy a minimum of three dockless vehicles per day to each equity zone.</para>
          <para num="(2)">Compliance.
The Department shall:<para num="(a)">Evaluate daily compliance based on at least one hour of compliance between 5:00 a.m. and 9:00 a.m; and</para>
            <para num="(b)">Notify a permit holder of in violation of &lt;cite data-path="14.02.01.08|C.|(1)"&gt;§C(1)&lt;/cite&gt;&lt;cite data-path="14.02.01.08|C.|(2)"&gt;-(2)&lt;/cite&gt; of &lt;cite data-path="14.02.01.08"&gt;this regulation&lt;/cite&gt; via a compliance score notification.</para>
          </para>
        </para>
        <para num="D.">Prohibitions.<para num="(1)">A permit holder may not deploy a dockless vehicle:<para num="(a)">Outside of a parking corral on a block face that contains an official parking corral designated by the Department, except as provided in &lt;cite data-path="14.02.01.08|D.|(2)"&gt;§D(2) of this regulation&lt;/cite&gt;;</para>
            <para num="(b)">In a quantity greater than ten per block face, except as allowed by the Department to accommodate a special event;</para>
            <para num="(c)">On a block face which contains the front entrance to a K-8 school;</para>
            <para num="(d)">In a tree pit or otherwise landscaped area;</para>
            <para num="(e)">In front of a property with an approved non-deployment request in accordance with &lt;cite data-path="14.02.01.08|E."&gt;§E of this regulation&lt;/cite&gt;; or</para>
            <para num="(f)">In a location the Department has notified the permit holder that they may not deploy to, beginning 48 hours after the notification.</para>
          </para>
          <para num="(2)">If a parking corral is full, a permit holder may deploy a dockless vehicle on a block face outside of the parking corral.</para>
          <para num="(3)">Unless a permit holder receives approval from the Department, a permit holder may not designate a public street in Baltimore City as a:<para num="(a)">No parking zone;</para>
            <para num="(b)">Reduced speed zone; or</para>
            <para num="(c)">No ride zone.</para>
          </para>
        </para>
        <para num="E.">Non-Deployment Requests.<para num="(1)">A property owner or manager may submit a non-deployment request in writing to the Department for an area adjacent to their property.</para>
          <para num="(2)">The Department shall notify a permit holder:<para num="(a)">Of an approved non-deployment request; and</para>
            <para num="(b)">That an approved non-deployment request will begin 48-hours after notification.</para>
          </para>
        </para>
        <para num="F.">Severe Weather and Emergencies.<para num="(1)">If 24-hour advanced notice is provided, the Department may:<para num="(a)">Suspend the requirements of &lt;cite data-path="14.02.01.08"&gt;this regulation&lt;/cite&gt;; or</para>
            <para num="(b)">Require the removal of:<para num="(i)">An entire fleet; or</para>
              <para num="(ii)">A portion of a fleet in a defined geographic location.</para>
            </para>
          </para>
          <para num="(2)">The Department may require a permit holder to remove a dockless vehicle from:<para num="(a)">An evacuation route prior to an emergency snow event; and</para>
            <para num="(b)">A low-lying area prior to an emergency flooding event.</para>
          </para>
        </para>
        <para num="G.">Special Events.
The Department may suspend the requirements of &lt;cite data-path="14.02.01.08"&gt;this regulation&lt;/cite&gt; during a special event.</para>
        <para num="H.">Temporary Exemptions from Deployment Regulations.<para num="(1)">A permit holder may apply for a temporary exemption from the deployment requirements in &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;.</para>
          <para num="(2)">A permit holder shall include a plan for communicating operational changes to affected users and the public within the application for temporary exemption.</para>
          <para num="(3)">The Department shall review applications for temporary exemption:<para num="(a)">Within 24 hours for an application based on an immediate safety concern; and</para>
            <para num="(b)">Within five business days for other exemption requests.</para>
          </para>
        </para>
        <para num="I.">Alternative Deployment Locations.<para num="(1)">A permit holder shall obtain permission to deploy a dockless vehicle to an alternative deployment location from:<para num="(a)">The Department;</para>
            <para num="(b)">A private property owner; or</para>
            <para num="(c)">Another City agency.</para>
          </para>
          <para num="(2)">A permit holder shall communicate the permission to deploy a dockless vehicle in an alternative deployment location via:<para num="(a)">Signage approved by the entity granting permission; or</para>
            <para num="(b)">A mobile or web application.</para>
          </para>
        </para>
      </section>
      <section prefix="Regulation" num=".09" heading="Equitable Dockless Vehicle Access.">
        <para num="A.">Cash Payment Plans.<para num="(1)">A permit holder shall:<para num="(a)">Provide the option to rent a dockless vehicle using a cash payment;</para>
            <para num="(b)">Offer at least one cash payment location in each deployment district;</para>
            <para num="(c)">Identify the following on its website and mobile application:<para num="(i)">The process for making a cash payment; and</para>
              <para num="(ii)">The locations where a cash payment option is available;</para>
            </para>
            <para num="(d)">Provide an instruction document to the Department that summarizes the process to sign up for a cash-payment plan; and</para>
            <para num="(e)">Inform a user of the availability of cash payment option:<para num="(i)">During initial sign-up; and</para>
              <para num="(ii)">Via email at least twice annually.</para>
            </para>
          </para>
          <para num="(2)">The Department shall post the instruction document provided for in &lt;cite data-path="14.02.01.09|A.|(1)|(d)"&gt;§A(1)(d) of this regulation&lt;/cite&gt; to the Department website.</para>
        </para>
        <para num="B.">Non-Smartphone Plans.<para num="(1)">A permit holder shall:<para num="(a)">Offer the option to rent a dockless vehicle without the use of a smartphone;</para>
            <para num="(b)">Identify the process to rent a dockless vehicle without using a smartphone on its website and mobile application;</para>
            <para num="(c)">Provide an instruction document to the Department that summarizes the process to sign up for a cash-payment plan; and</para>
            <para num="(d)">Inform a user of the availability of cash payment option:<para num="(i)">During initial sign-up; and</para>
              <para num="(ii)">Via email at least twice annually.</para>
            </para>
          </para>
          <para num="(2)">The Department shall post the instruction document provided for in &lt;cite data-path="14.02.01.09|B.|(1)|(c)"&gt;§B(1)(c) of this regulation&lt;/cite&gt; to the Department website.</para>
        </para>
        <para num="C.">Low-Income Plans.<para num="(1)">A permit holder shall offer a low-income plan to users with an income level at or below 200 percent of the federal poverty guideline.</para>
          <para num="(2)">A permit holder shall approve a low-income user by obtaining:<para num="(a)">Preapproval from a referral agency; or</para>
            <para num="(b)">Proof of assistance, including:<para num="(i)">Local assistance;</para>
              <para num="(ii)">State assistance; or</para>
              <para num="(iii)">Federal assistance.</para>
            </para>
          </para>
          <para num="(3)">A permit holder shall ensure a low-income plan:<para num="(a)">Waives an unlock fee for at least four rides per day; and</para>
            <para num="(b)">Offers a minimum 80 percent discount on rental fees for at least four rides per day.</para>
          </para>
          <para num="(4)">A permit holder shall:<para num="(a)">Describe the process to sign up for a low-income plan on the dockless vehicle:<para num="(i)">Website; and</para>
              <para num="(ii)">Mobile application;</para>
            </para>
            <para num="(b)">Notify the Department of a change to verification methods for low-income customer plans;</para>
            <para num="(c)">Provide an instruction document to the Department that summarizes the process to sign up for a low-income plan;</para>
            <para num="(d)">Inform a user of the availability of cash payment option:<para num="(i)">During initial sign-up; and</para>
              <para num="(ii)">Via email at least twice annually.</para>
            </para>
          </para>
          <para num="(5)">The Department shall post the instruction document provided for in &lt;cite data-path="14.02.01.09|C.|(4)|(c)"&gt;§C(4)(c) of this regulation&lt;/cite&gt; to the Department website.</para>
        </para>
        <para num="D.">Customer Service Phone Lines.<para num="(1)">A permit holder shall maintain a live, multilingual 24-hour customer service phone line.</para>
          <para num="(2)">If a caller is required to leave a voicemail when calling the customer service phone line, a permit holder shall respond with a call back within two hours.</para>
          <para num="(3)">A permit holder shall provide a translation or call back within four hours when a message is left by a customer in:<para num="(a)">Spanish;</para>
            <para num="(b)">French;</para>
            <para num="(c)">Mandarin Chinese; or</para>
            <para num="(d)">Korean.</para>
          </para>
        </para>
        <para num="E.">Web Accessibility.
Within 120 days of receiving a permit, a permit holder shall ensure that its software application used for vehicle rental and website are accessible to visually impaired individuals consistent with the latest WCAG standards.</para>
      </section>
      <section prefix="Regulation" num=".10" heading="Compliance.">
        <para num="A.">Compliance Scores – Calculation and Reporting.
The Department shall:<para num="(1)">Calculate a compliance score to determine compliance for:<para num="(a)">Equitable distribution of a dockless vehicle fleet; and</para>
            <para num="(b)">Parking of a dockless vehicle fleet; and</para>
          </para>
          <para num="(2)">Report compliance scores to a permit holder twice per calendar month.</para>
        </para>
        <para num="B.">Compliance Requirements – Distribution.<para num="(1)">To remain compliant with the distribution requirements of &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;, a permit holder shall ensure a minimum compliance score of 85 percent for each reporting period in:<para num="(a)">A deployment district; and</para>
            <para num="(b)">An equity zone.</para>
          </para>
        </para>
        <para num="C.">Compliance Requirements – Fleet Parking.
To remain compliant with fleet parking requirements, a permit holder shall ensure:<para num="(1)">No more than 5 percent of a dockless vehicle fleet remains parked for longer than 5 days for the period from April 1 through November 30; and</para>
          <para num="(2)">No more than 10 percent of a dockless vehicle fleet remains parked for longer than 5 days for the period from December 1 through March 31.</para>
        </para>
        <para num="D.">Eligibility for Fleet Cap Increase.
To be eligible for a fleet cap increase, a permit holder shall score a minimum of 90 percent compliance for each reporting period in<para num="(1)">A deployment district; and</para>
          <para num="(2)">An equity zone.</para>
        </para>
        <para num="E.">Winter Weather Compliance Exemptions.
On days for which the Baltimore City Public School System implements a modified schedule due to inclement weather, the Department shall grant compliance exemptions for violations of:<para num="(1)">Distribution;</para>
          <para num="(2)">Equity; and</para>
          <para num="(3)">Five-day parking.</para>
        </para>
        <para num="F.">Remote Shut Down Notice Exemptions.
When the Department has issued a remote shutdown notice to a permit holder, the Department shall grant compliance exemptions for violations of:<para num="(1)">Distribution;</para>
          <para num="(2)">Equity; and</para>
          <para num="(3)">Five-day parking.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".11" heading="Vehicle Standards.">
        <para num="A.">Vehicle Approval.<para num="(1)">A permit holder shall ensure a dockless vehicle model intended for deployment on a public street has been approved by the Director prior to its deployment on the public street.</para>
          <para num="(2)">To deploy a new vehicle model or vehicle type, a permit holder shall submit the following to the Department at least two weeks prior to intended deployment:<para num="(a)">Vehicle specifications;</para>
            <para num="(b)">A safety certificate;</para>
            <para num="(c)">A deployment plan;</para>
            <para num="(d)">A change to an operations plan, if any; and</para>
            <para num="(e)">A change to a maintenance plan, if any.</para>
          </para>
          <para num="(3)">A permit holder may not deploy a new vehicle model or type until receiving written approval from the Department.</para>
        </para>
        <para num="B.">Required Features – In General.
A permit holder shall ensure a dockless vehicle deployed on a public street:<para num="(1)">Weighs no more than 100 pounds;</para>
          <para num="(2)">Is equipped with an operational structural feature that allows the vehicle to be stably parked upright without needing to lean on another object;</para>
          <para num="(3)">Is equipped with built-in front and back lights that:<para num="(a)">Illuminate while the dockless vehicle is in use; and</para>
            <para num="(b)">Are visible from a distance of at least 500 feet under normal atmospheric conditions at night;</para>
          </para>
          <para num="(4)">Is equipped with a bell or noise emitting device;</para>
          <para num="(5)">Has tires with a diameter of at least nine inches;</para>
          <para num="(6)">Has tactile identification which:<para num="(a)">Meets State requirements; and</para>
            <para num="(b)">Is located on the stem near the handlebars if handlebars are present; and</para>
          </para>
          <para num="(7)">Has legible decals listing:<para num="(a)">The name of the permit holder displayed in a minimum of 16-point font;</para>
            <para num="(b)">The following contact information for a permit holder displayed in a minimum of 16-point font:<para num="(i)">A toll-free telephone number;</para>
              <para num="(ii)">An e-mail address; and</para>
              <para num="(iii)">A website address; and</para>
            </para>
            <para num="(c)">A unique identification number displayed in:<para num="(i)">A minimum of 48-point font; or</para>
              <para num="(ii)">Font that is at least 1 inch in height.</para>
            </para>
          </para>
        </para>
        <para num="C.">Required Features – E-scooters.
A permit holder shall ensure that an e-scooter deployed on a public street:<para num="(1)">Has a speedometer that is legible; and</para>
          <para num="(2)">Is equipped with a speed governor capable of throttling speeds to specific speed limits in geographical areas designated in the MDS Policy API.</para>
        </para>
        <para num="D.">Data and Information.
A permit holder shall ensure a dockless vehicle and its associated apps do not provide false information, including:<para num="(1)">An inaccurate speedometer reading; and</para>
          <para num="(2)">An alarm that announces that a vehicle can notify the police.</para>
        </para>
        <para num="E.">Additional Requirements.<para num="(1)">A permit holder shall certify that its deployed vehicles meet:<para num="(a)">Applicable federal laws;</para>
            <para num="(b)">Applicable State laws;</para>
            <para num="(c)">Applicable provisions of City Code;</para>
            <para num="(d)">CPSC Safety Standards: ISO 43.150 for Pedal Bicycles; and</para>
            <para num="(e)">CPSC Public Law 107-319 for E-Scooters and E-Bicycles.</para>
          </para>
          <para num="(2)">A permit holder shall certify that each dockless vehicle they deploy in the City are:<para num="(a)">Free of defects in materials;</para>
            <para num="(b)">Free of defects in construction; and</para>
            <para num="(c)">Safe for members of the public to use in the ordinary course of usage.</para>
          </para>
        </para>
      </section>
      <section prefix="Regulation" num=".12" heading="Vehicle Standards - Inspections and Notification.">
        <para num="A.">The Department shall:<para num="(1)">Perform regular vehicle inspections to ensure that a rentable dockless vehicle deployed on a public street is:<para num="(a)">Functioning safely; and</para>
            <para num="(b)">Properly equipped; and</para>
          </para>
          <para num="(2)">Provide advance notice to a permit holder about the details of an inspection to be performed.</para>
        </para>
        <para num="B.">For vehicles found to be in violation of &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;, the Department shall notify a permit holder within 24 hours of inspection.</para>
      </section>
      <section prefix="Regulation" num=".13" heading="Vehicle Standards – Timeline for Compliance.">
        <text>Upon notification of a violation in accordance with &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;, the Department shall calculate a timeline for compliance that is:</text>
        <para num="A.">Based on the extent of changes required to a permit holder’s fleet;</para>
        <para num="B.">No fewer than 60 days; and</para>
        <para num="C.">No more than 6 months.</para>
      </section>
      <section prefix="Regulation" num=".14" heading="Remote Shutdown.">
        <para num="A.">User Reported Safety Issue.<para num="(1)">Upon the first report of a safety issue by a user, a permit holder shall remotely shut down the dockless vehicle so that it cannot be operated until repaired.</para>
          <para num="(2)">If a reported safety issue is due to an equipment malfunction which could be present in additional dockless vehicles, the permit holder shall:<para num="(a)">Remove their entire fleet of vehicles from the street within 24 hours; and</para>
            <para num="(b)">Ensure the fleet remains off the street until:<para num="(i)">Further investigation is completed; and</para>
              <para num="(ii)">Relaunch is approved by the City.</para>
            </para>
          </para>
        </para>
        <para num="B.">Remote Shut Down Notice.<para num="(1)">The Department may issue a remote shutdown notice if it is deemed necessary to protect:<para num="(a)">The safety of a dockless vehicle user; or</para>
            <para num="(b)">Public safety.</para>
          </para>
          <para num="(2)">The Department shall ensure a remote shutdown notice includes:<para num="(a)">The duration of the shutdown period;</para>
            <para num="(b)">The reasoning behind the shutdown;</para>
            <para num="(c)">Which vehicle type the permit holder is instructed to shut down; and</para>
            <para num="(d)">The geographic area within Baltimore City in which the vehicles should be shut down.</para>
          </para>
          <para num="(3)">Within two hours of receipt of a remote shutdown notice from the Department, a permit holder shall remotely shut down:<para num="(a)">Part of their fleet, as specified in the notice; or</para>
            <para num="(b)">Their entire fleet, as specified in the notice.</para>
          </para>
        </para>
      </section>
      <section prefix="Regulation" num=".15" heading="Fleet Size.">
        <para num="A.">Minimum and Maximum Fleet Sizes.<para num="(1)">For each permitted vehicle type, a permit holder may initially operate a fleet consisting of:<para num="(a)">A minimum of 150 dockless vehicles; and</para>
            <para num="(b)">A maximum of 1500 dockless vehicles.</para>
          </para>
          <para num="(2)">A permit holder’s total fleet may include a combination of vehicle types allowed by their permit if there is a minimum of 150 vehicles of each type.</para>
        </para>
        <para num="B.">Adaptive Vehicle Exemptions.<para num="(1)">The Department may exempt a permit holder that includes adaptive dockless vehicles in their fleet from:<para num="(a)">The requirement to maintain a minimum of 150 vehicles for adaptive dockless vehicles; and</para>
            <para num="(b)">The requirement to maintain a minimum of 150 vehicles for other permitted dockless vehicle types.</para>
          </para>
          <para num="(2)">A permit holder that includes an adaptive dockless vehicle in their fleet shall ensure the adaptive dockless vehicle:<para num="(a)">Is officially approved by the Director; and</para>
            <para num="(b)">Is not included in the count for the maximum number of vehicles allowed in a permit holder’s fleet.</para>
          </para>
        </para>
        <para num="C.">Timelines for Reaching Minimum Fleet Size.<para num="(1)">A permit holder permitted in the previous year shall reach the minimum fleet size per vehicle type within 20 days of permit issuance.</para>
          <para num="(2)">A new permit holder shall reach the minimum fleet size within 60 days of permit issuance.</para>
          <para num="(3)">A permit holder who introduces a new vehicle type shall reach the minimum fleet size within 60 days of receiving approval of the new vehicle type from the Department.</para>
        </para>
        <para num="D.">Fleet Increases.<para num="(1)">Each quarter, a permit holder may request a fleet increase of up to 250 vehicles in excess of the limits established in &lt;cite data-path="14.02.01.15|A."&gt;§A of this Regulation&lt;/cite&gt;.</para>
          <para num="(2)">In reviewing a fleet increase request, the Department shall assess:<para num="(a)">Performance during the period prior to the evaluation; and</para>
            <para num="(b)">Projections for the subsequent quarter.</para>
          </para>
          <para num="(3)">The Department may:<para num="(a)">Set an overall fleet cap; and</para>
            <para num="(b)">Revoke a fleet increase.</para>
          </para>
        </para>
      </section>
      <section prefix="Regulation" num=".16" heading="Parking and Operation.">
        <para num="A.">In General.<para num="(1)">A permit holder shall instruct users to:<para num="(a)">Park a dockless vehicle in compliance with &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-19"&gt;City Code Article 31, § 38-19&lt;/cite&gt;;</para>
            <para num="(b)">Operate a dockless vehicle in compliance with &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-18"&gt;City Code Article 31, § 38-18&lt;/cite&gt;; and</para>
            <para num="(c)">Provide end of trip pictures that show:<para num="(i)">The location a vehicle was parked; and</para>
              <para num="(ii)">The manner in which a vehicle was parked.</para>
            </para>
          </para>
          <para num="(2)">A permit holder shall use end of trip pictures:<para num="(i)">When a parking violation is reported by the Department; and</para>
            <para num="(ii)">To disable a user account when three or more end of trip pictures fail to provide the information required by &lt;cite data-path="14.02.01.16|A.|(1)|(c)"&gt;§A(1)(c) of this regulation&lt;/cite&gt;.</para>
          </para>
        </para>
        <para num="B.">Notice and Response.<para num="(1)">Upon notification that a dockless vehicle is improperly parked, a permit holder shall reposition or remove the vehicle within:<para num="(a)">Three hours of notification by the Department; and</para>
            <para num="(b)">Six hours of notification by a member of the public.</para>
          </para>
          <para num="(2)">The Department may perform a check of parking complaint response times, during which the Department may:<para num="(a)">Report an illegally parked vehicle officially; or</para>
            <para num="(b)">Anonymously report an illegally parked vehicle as a member of the public.</para>
          </para>
        </para>
        <para num="C.">Abandoned Vehicles.
If a dockless vehicle has been parked at the same location and not ridden for five consecutive days, a permit holder shall:<para num="(1)">Perform a mechanical check of the dockless vehicle; and</para>
          <para num="(2)">Relocate the dockless vehicle to another block face.</para>
        </para>
        <para num="D.">Mobile Application Requirements.
A permit holder shall:<para num="(1)">Ensure a dockless vehicle mobile application displays:<para num="(a)">Applicable operating laws within four menu selections from the home screen; and</para>
            <para num="(b)">The location of parking corrals installed by the Department; and</para>
          </para>
          <para num="(2)">Provide a discount through the mobile application to a user who ends their trip by parking a dockless vehicle in a parking corral installed by the Department.</para>
          <para num="(3)">Upload the location of parking corrals installed by the Department to a dockless vehicle mobile application within 10 days of notification from the Department.</para>
        </para>
        <para num="E.">No Parking Zones.<para num="(1)">The Department may establish a no parking zone on the public street in accordance with &lt;cite data-path="14.02.01.16|E.|(2)"&gt;§E(2) of this regulation&lt;/cite&gt;.</para>
          <para num="(2)">For a no parking zone established in accordance with &lt;cite data-path="14.02.01.16"&gt;this regulation&lt;/cite&gt;, the Department shall:<para num="(a)">Identify the no parking zone in the MDS Policy API; and</para>
            <para num="(b)">Notify a permit holder of the no parking zone through the MDS Policy API.</para>
          </para>
          <para num="(3)">Within 72 hours of notification from the Department, a permit holder shall prohibit a user from ending a trip in a no parking zone.</para>
        </para>
        <para num="F.">No Operation Zones.<para num="(1)">The Department may establish a no operation zone on the public street in accordance with &lt;cite data-path="14.02.01.16|F.|(2)"&gt;§F(2) of this regulation&lt;/cite&gt;.</para>
          <para num="(2)">For a no operation zone established in accordance with &lt;cite data-path="14.02.01.16"&gt;this regulation&lt;/cite&gt;, the Department shall:<para num="(a)">Identify the no operation zone in the MDS Policy API; and</para>
            <para num="(b)">Notify a permit holder of the no operation zone through the MDS Policy API.</para>
          </para>
          <para num="(3)">The Department shall ensure compliance with a no operation zone via testing of vehicles.</para>
          <para num="(4)">Within 72 hours of notification from the Department, a permit holder shall ensure their vehicles lose electric assistance or drive when a user rides into a no operation zone.</para>
        </para>
        <para num="G.">Reduced Speed Zones.<para num="(1)">The Department may establish a reduced speed zone on a public street in accordance with &lt;cite data-path="14.02.01.16|G.|(2)"&gt;§G(2) of this regulation&lt;/cite&gt;.</para>
          <para num="(2)">For a reduced speed zone established in accordance with &lt;cite data-path="14.02.01.16"&gt;this regulation&lt;/cite&gt;, the Department shall:<para num="(a)">Identify the reduced speed zone in the MDS Policy API; and</para>
            <para num="(b)">Notify a permit holder of the reduced speed zone through the MDS Policy API.</para>
          </para>
          <para num="(3)">The Department shall ensure compliance with a reduced speed zone via testing of vehicles.</para>
          <para num="(4)">Within 72 hours of notification from the Department, a permit holder shall ensure their vehicles are limited to eight miles per hour when a user rides into a reduced speed zone.</para>
        </para>
        <para num="H.">A permit holder will be subject to the compliance inspection process in &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;, including the issuance of a warning or citation, if a violation of the provisions of &lt;cite data-path="14.02.01.16"&gt;this regulation&lt;/cite&gt; occurs.</para>
      </section>
      <section prefix="Regulation" num=".17" heading="Seizure and Recovery.">
        <para num="A.">The Department may seize a dockless vehicle if:<para num="(1)">A permit holder fails to comply with a request to reposition or remove a vehicle in accordance with &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;; or</para>
          <para num="(2)">A dockless vehicle is in a location where it cannot be accessed by a permit holder.</para>
        </para>
        <para num="B.">At the time of seizure, the Department shall:<para num="(1)">Notify the permit holder in accordance with &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31|§38-24"&gt;City Code Article 31, § 38-24&lt;/cite&gt;;</para>
          <para num="(2)">Take pictures that indicate that the dockless vehicle is in violation of &lt;cite data-path="14.02.01"&gt;this chapter&lt;/cite&gt;;</para>
          <para num="(3)">Record the identification number of the dockless vehicle; and</para>
          <para num="(4)">Record the property number assigned to the dockless vehicle by the Towing Division.</para>
        </para>
        <para num="C.">If the Department seizes a dockless vehicle, the Department shall charge a permit holder the following fees from the refundable performance bond:<para num="(1)">$220.00, for five or fewer e- scooters seized at the same time;</para>
          <para num="(2)">$220.00, for more than five e-scooters seized at the same time, plus $44.00 per each e-scooter beyond the fifth;</para>
          <para num="(3)">$220.00, for three or fewer bicycles or e-bicycles seized at the same time; and</para>
          <para num="(4)">$220.00, for more than three bicycles or e-bicycles seized at the same time, plus $73.33 per bicycle or e-bicycle beyond the third.</para>
        </para>
        <para num="D.">After the first 48 hours from the initial seizure date, the Department may charge a permit holder $15.00 for each 24-hour period for each group of:<para num="(1)">Up to five e-scooters; or</para>
          <para num="(2)">Up to three bicycles or e-bicycles.</para>
        </para>
        <para num="E.">Recovery of Seized Vehicles.<para num="(1)">A permit holder shall retrieve a seized dockless vehicle from:</para>
          <para num="(2)">A permit holder shall notify the Towing Division of the person who will retrieve a seized vehicle by calling 410-396-9958 or 410-545-3417.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".18" heading="User Education.">
        <para num="A.">A permit holder shall provide in-app user education on proper operation of a dockless vehicle by:<para num="(1)">Developing an in-app quiz for new users that:<para num="(a)">Contains a minimum of five questions approved by the Department pertaining to:<para num="(i)">Parking;</para>
              <para num="(ii)">Operations; or</para>
              <para num="(iii)">General safety; and</para>
            </para>
            <para num="(b)">Requires a score of at least 80 percent before the third rental of a dockless vehicle by a user; and</para>
          </para>
          <para num="(2)">Displaying a banner on the app home screen for up to one week of each month that highlights relevant information determined by the Department.</para>
        </para>
        <para num="B.">A permit holder shall provide in-person user education on proper operation of a dockless vehicle by:<para num="(1)">Hosting or participating in a minimum of one community event per deployment district annually to display safety information;</para>
          <para num="(2)">Attending a minimum of two community events annually between November and February; and</para>
          <para num="(3)">Attending a minimum of four public meetings upon invitation by the Department.</para>
        </para>
        <para num="C.">Access to Additional User Data.<para num="(1)">A permit holder may request that users “opt in” to provide access to:<para num="(a)">Location services; or</para>
            <para num="(b)">Files on a user’s phone.</para>
          </para>
          <para num="(2)">A permit holder may not prevent use of a dockless vehicle based on a user’s decision to grant or deny the data noted in &lt;cite data-path="14.02.01.18|C.|(1)"&gt;§C(1) of this regulation&lt;/cite&gt;.</para>
        </para>
        <para num="D.">Departmental Survey.
Within 10 days of notification by the Department, a permit holder shall:<para num="(1)">Include a clickable link to a yearly Department survey in the mobile application; and</para>
          <para num="(2)">Send the survey link to active users via e-mail.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".19" heading="Special Events.">
        <para num="A.">The Department may require a permit holder to provide staffing for special events expecting over 5,000 attendants in accordance with &lt;cite data-path="14.02.01.19"&gt;this regulation&lt;/cite&gt;.</para>
        <para num="B.">Upon notification from the Department, a permit holder shall be required to:<para num="(1)">Designate an individual as a staff contact for event organizers;</para>
          <para num="(2)">For events expecting 5,000-9,999 people in attendance, provide up to two staffers for:<para num="(a)">Up to one hour before the event;</para>
            <para num="(b)">During the event; and</para>
            <para num="(c)">Up to one hour after the conclusion of the event;</para>
          </para>
          <para num="(3)">For events expecting over 10,000 people in attendance, provide up to three staffers for:<para num="(a)">Up to one hour before the event;</para>
            <para num="(b)">During the event; and</para>
            <para num="(c)">Up to one hour after the conclusion of the event.</para>
          </para>
        </para>
      </section>
      <section prefix="Regulation" num=".20" heading="Pricing.">
        <para num="A.">Except as provided in &lt;cite data-path="14.02.01.20|B."&gt;§B of this regulation&lt;/cite&gt;, a permit holder may not:<para num="(1)">Set a higher price for the use of a dockless vehicle in a certain part of the City; or</para>
          <para num="(2)">Base pricing on a users’:<para num="(a)">Inclusion in a federally protected class;</para>
            <para num="(b)">Genetic information; or</para>
            <para num="(c)">Citizenship.</para>
          </para>
        </para>
        <para num="B.">A permit holder may use a pricing variation to:<para num="(1)">Incentivize proper operation of a dockless vehicle; or</para>
          <para num="(2)">Increase usership among underserved or low-income populations.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".21" heading="Advertising and User Engagement.">
        <para num="A.">A permit holder shall ensure that user engagement, including participation at required community events, is inclusive of:<para num="(1)">Underserved populations; and</para>
          <para num="(2)">Low-income populations.</para>
        </para>
        <para num="B.">A permit holder may not:<para num="(1)">Use the name of a City agency, including the Department, without prior written approval;</para>
          <para num="(2)">Use the logo of a City agency, including the Department, without prior written approval’ and</para>
          <para num="(3)">Use the following to display third-party advertising:<para num="(a)">A dockless vehicle;</para>
            <para num="(b)">A mobile application;</para>
            <para num="(c)">A kiosk;</para>
            <para num="(d)">Related physical infrastructure; or</para>
            <para num="(e)">Related web-based infrastructure.</para>
          </para>
        </para>
      </section>
      <section prefix="Regulation" num=".22" heading="Data and Reporting.">
        <para num="A.">GPS.
A permit holder shall ensure each dockless vehicle in their fleet is equipped with on-board GPS technology that does not rely on a user’s mobile device to obtain spatial information.</para>
        <para num="B.">Publicly Accessible Application Program Interface (API).<para num="(1)">The permit holder shall provide a publicly accessible API.</para>
          <para num="(2)">The permit holder shall ensure that:<para num="(a)">The public API is in a gbfs.json file format;</para>
            <para num="(b)">There are no “stations” in the parlance of GBFS, therefore both station_status.json and station_information.json should return an empty list;</para>
            <para num="(c)">FreE-Bicycle-status.json is required;</para>
            <para num="(d)">The field “vehicle_type” is added to the public API to describe the vehicle type, which may be:<para num="(i)">“Bicycle”;</para>
              <para num="(ii)">“E-Bicycle”;</para>
              <para num="(iii)">“Scooter”; or</para>
              <para num="(iv)">Another type of specified permitted vehicle;</para>
            </para>
            <para num="(e)">The Department is instructed on how to request authentication, if the public API requires authentication;</para>
            <para num="(f)">The location of the public API is provided to the Department; and</para>
            <para num="(g)">A smart phone-based application used to rent dockless vehicles is not considered the public API program interface required by &lt;cite data-path="14.02.01.22|B.|(1)"&gt;§B(1) of this regulation&lt;/cite&gt;.</para>
          </para>
          <para num="(3)">The permit holder shall provide access to at least 50 requests per hour.</para>
          <para num="(4)">The Department shall post the location of the public API to the Department’s website.</para>
        </para>
        <para num="C.">Mobility Data Specification (MDS) Policy API.<para num="(1)">A permit holder shall:<para num="(a)">Provide an MDS Policy API to the Department for a dockless vehicle trip in Baltimore City, including trips which:<para num="(i)">Start in Baltimore City;</para>
              <para num="(ii)">End in Baltimore City; or</para>
              <para num="(iii)">Pass through Baltimore City;</para>
            </para>
            <para num="(b)">Adhere to an MDS of 1.0 or newer, as set by the OMF;</para>
            <para num="(c)">Post the MDS Policy API on GitHub under the OMF Mobility Data specification;</para>
            <para num="(d)">Provide API endpoints, including:<para num="(i)">A trip;</para>
              <para num="(ii)">A status change;</para>
              <para num="(iii)">A vehicle; and</para>
              <para num="(iv)">Real-time data;</para>
            </para>
            <para num="(e)">Update or add endpoints to the MDS Policy API within:<para num="(i)">Sixty days of notification from the Department for required published endpoints; and</para>
              <para num="(ii)">Ninety days for beta endpoints;</para>
            </para>
            <para num="(f)">Change vehicle status to ‘Unknown’ if a vehicle is suspected to be:<para num="(i)">Vandalized; or</para>
              <para num="(ii)">Missing for five or more days;</para>
            </para>
            <para num="(g)">Ensure GPS data are transmitted from a dockless vehicle on-trip at a minimum frequency of once per 30 seconds;</para>
            <para num="(h)">Develop and maintain a working Wi-Fi connection to ingest MDS Policy API endpoints provided by the Department; and</para>
            <para num="(i)">Share current data through the MDS Policy API at least once per 24 hours.</para>
          </para>
          <para num="(2)">The Department may require additional or updated endpoints published by OMF.</para>
          <para num="(3)">The Department may share the MDS Policy API with a third-party aggregator in accordance with &lt;cite data-path="14.02.01.22|C.|(4)"&gt;§C(4) of this regulation&lt;/cite&gt; for the purpose of:<para num="(a)">Secure data storage; and</para>
            <para num="(b)">Analysis.</para>
          </para>
          <para num="(4)">To share data with a third-party aggregator in accordance with &lt;cite data-path="14.02.01.22|C.|(3)"&gt;§C(3) of this regulation&lt;/cite&gt;, the Department shall enter into a memorandum of understanding with a third-party aggregator that:<para num="(a)">Includes a provision governing the public release of data by a third-party aggregator; and</para>
            <para num="(b)">Is made available for a permit holder to review prior to being finalized.</para>
          </para>
        </para>
        <para num="D.">Reporting.<para num="(1)">Time Sensitive Reports.
A permit holder shall report the following to the Department within 24 hours of notice:<para num="(a)">Non-deployment request at a location by an adjacent property owner for verification by the Department;</para>
            <para num="(b)">A vehicle that is in a location where the permit holder cannot retrieve it, including a body of water; and</para>
            <para num="(c)">An issue that could affect public safety, including:<para num="(i)">A report of criminal activity involving a dockless vehicle;</para>
              <para num="(ii)">A report of a crash involving a dockless vehicle;</para>
              <para num="(iii)">Contact with the Baltimore City Police Department;</para>
              <para num="(iv)">Contact with the Baltimore City Fire Department; or</para>
              <para num="(v)">A defect in equipment.</para>
            </para>
          </para>
          <para num="(2)">Monthly Reports.
A permit holder shall provide the Department with a monthly report by the tenth business day following the final day of the month which:<para num="(a)">Uses the Department’s reporting template;</para>
            <para num="(b)">Is in Excel or CSV format;</para>
            <para num="(c)">Includes:<para num="(i)">A report of each dockless vehicle lost due to theft or vandalism;</para>
              <para num="(ii)">Aggregated repair information on a permit holder’s dockless vehicle fleet by model of vehicle and type of repair;</para>
              <para num="(iii)">Each illegal parking request from the public;</para>
              <para num="(iv)">Each customer complaint received with response time noted;</para>
              <para num="(v)">A record of attendance at a City meeting;</para>
              <para num="(vi)">The number of people in attendance at a community event;</para>
              <para num="(vii)">A summary of marketing efforts;</para>
              <para num="(viii)">The number of users that took a trip on a dockless vehicle during the reporting period;</para>
              <para num="(ix)">The number of rides by low-income pass users during the reporting period;</para>
              <para num="(x)">The number of rides by cash users during the reporting period;</para>
              <para num="(xi)">The number of rides by non-smart phone users during the reporting period;</para>
              <para num="(xii)">The number of users provided for in &lt;cite data-path="14.02.01.22|D.|(2)|(c)|(ix)"&gt;§(2)(c)(ix)&lt;/cite&gt;&lt;cite data-path="14.02.01.22|D.|(2)|(c)|(xi)"&gt;-(xi)&lt;/cite&gt; of &lt;cite data-path="14.02.01.22"&gt;this regulation&lt;/cite&gt; disaggregated by the type of plan and user home zip code;</para>
              <para num="(xiii)">The number of users of the low-income pass; and</para>
              <para num="(xiv)">An update to maintenance or operational plan.</para>
            </para>
          </para>
          <para num="(3)">Software Issues and Hacking Events.
A permit holder shall:<para num="(a)">Notify the Department of a change to a data portal, including a response to a notification from the Department regarding:<para num="(i)">A software glitch;</para>
              <para num="(ii)">An issue with hacking; or</para>
              <para num="(iii)">A data portal;</para>
            </para>
            <para num="(b)">Acknowledge a notification from the Department about data and reporting within 24 hours;</para>
            <para num="(c)">Provide the Department with a plan for addressing an identified problem;</para>
            <para num="(d)">Provide a progress update to the Department once per 48 hours while the problem persists; and</para>
            <para num="(e)">Permanently fix an issues within 60 days of receiving notice of the problem.</para>
          </para>
          <para num="(4)">User Privacy.
A permit holder shall protect user privacy by:<para num="(a)">Complying with Payment Card Industry Data Security Standards for an electronic payment;</para>
            <para num="(b)">Notifying a user of a mobile device feature that the mobile application accesses; and</para>
            <para num="(c)">Not releasing personal user data to an entity:<para num="(i)">Unrelated to operations; or</para>
              <para num="(ii)">That intends to use the data in a commercial sale to a third party.</para>
            </para>
          </para>
        </para>
      </section>
      <section prefix="Regulation" num=".23" heading="Security Bond.">
        <para num="A.">Security Bond.<para num="(1)">A permit holder shall provide a security for performance in the amount of $10,000 to the Department.</para>
          <para num="(2)">A permit holder shall ensure the security is in the form of:<para num="(a)">A performance bond;</para>
            <para num="(b)">A refundable bond; or</para>
            <para num="(c)">Another security acceptable to the City.</para>
          </para>
        </para>
        <para num="B.">Rental Taxes.<para num="(1)">A permit holder shall remit a rental tax to the Department of Finance twice annually in accordance with &lt;cite data-path="14.02.01.23"&gt;this section&lt;/cite&gt;.</para>
          <para num="(2)">January – June.<para num="(a)">The Department shall invoice a permit holder by July 15 for the tax provided for in &lt;cite data-path="14.02.01.23|B.|(2)|(b)|(i)"&gt;§B(2)(b)(i) of this regulation&lt;/cite&gt;.</para>
            <para num="(b)">The permit holder shall:<para num="(i)">Pay a tax of $0.10 per rental for dockless vehicle rentals between January 1 and June 30 annually; and</para>
              <para num="(ii)">Remit the tax within one calendar month after receiving an invoice from the Department.</para>
            </para>
          </para>
          <para num="(3)">July – December.<para num="(a)">The Department shall invoice a permit holder by January 15 for the tax provided for in &lt;cite data-path="14.02.01.23|B.|(3)|(b)|(i)"&gt;§B(3)(b)(i) of this regulation&lt;/cite&gt;.</para>
            <para num="(b)">The permit holder shall:<para num="(i)">Pay a tax of $0.10 per rental for dockless vehicle rentals between July 1 and December 31 annually; and</para>
              <para num="(ii)">Remit the tax within one calendar month after receiving an invoice from the Department.</para>
            </para>
          </para>
          <para num="(4)">A permit holder shall submit the following to the Department with each remitment of the annual tax:<para num="(a)">A list of the total number of transactions during the reporting period; and</para>
            <para num="(b)">A digital copy of:<para num="(i)">Payments during the reporting period; and</para>
              <para num="(ii)">Transactions during the reporting period.</para>
            </para>
          </para>
        </para>
      </section>
      <section prefix="Regulation" num=".24" heading="Procedures for Claims Against Security Bond.">
        <para num="A.">Authorization to Draw Against Security.
The City may deduct from the security provided by a permit holder to recover incurred costs if:<para num="(1)">A permit holder fails to remove from the public street a dockless vehicle that is:<para num="(a)">Unsafe;</para>
            <para num="(b)">Unpermitted; or</para>
            <para num="(c)">Abandoned;</para>
          </para>
          <para num="(2)">The Department seizes a dockless vehicles due to a violation of these regulations; or</para>
          <para num="(3)">A permit holder’s dockless vehicle causes damage to public property.</para>
        </para>
        <para num="B.">Notification.
If the City intends to deduct from a permit holder’s security as provided in &lt;cite data-path="14.02.01.24|A."&gt;§A of this regulation&lt;/cite&gt; the Department shall provide written notice to a permit holder prior to the deduction which states:<para num="(1)">The reason for the deduction;</para>
          <para num="(2)">The amount of the deduction;</para>
          <para num="(3)">Information on submission of an objection to a deduction in accordance with &lt;cite data-path="14.02.01.24|C."&gt;§C of this regulation&lt;/cite&gt;.</para>
        </para>
        <para num="C.">Objection Submission.
A permit holder may submit an objection to a planned deduction to their security bond:<para num="(1)">In writing; and</para>
          <para num="(2)">Within 7 days of the date of the written notice.</para>
        </para>
        <para num="D.">Notification of Outcome.<para num="(1)">The Department shall provide a permit holder with written notification of a decision rendered regarding their objection which:<para num="(a)">Provides the reason for denying the objection; or</para>
            <para num="(b)">Confirms acceptance of the objection.</para>
          </para>
          <para num="(2)">The Department shall send the notification to the permit holder three days before a deduction is made.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".25" heading="Insurance.">
        <para num="A.">Required Insurance.
A permit holder shall procure and maintain the coverage required in the permit agreement during:<para num="(1)">The term of an initial dockless vehicle permit; or</para>
          <para num="(2)">The renewal of a dockless vehicle permit:</para>
        </para>
        <para num="B.">A permit holder shall name The Mayor and City Council of Baltimore as an additional insured on the permit holder’s:<para num="(1)">Commercial general liability insurance; and</para>
          <para num="(2)">Commercial automobile liability policies.</para>
        </para>
        <para num="C.">A permit holder shall indemnify the Mayor and City Council of Baltimore from liability relating to:<para num="(1)">The issuance of a dockless vehicle; or</para>
          <para num="(2)">The provision of services under a dockless vehicle permit.</para>
        </para>
        <para num="D.">The City shall notify a permit holder before resolution or settlement of claims for which the City will seek indemnification.</para>
      </section>
      <section prefix="Regulation" num=".26" heading="Citations.">
        <para num="A.">The Department may:<para num="(1)">Issue a citation under &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|1|§40-14"&gt;City Code Article 1, § 40-14&lt;/cite&gt; to a permit holder found to be in violation of:<para num="(a)">&lt;cite data-path="14.02.01"&gt;This chapter&lt;/cite&gt;; or</para>
            <para num="(b)">&lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31"&gt;City Code Article 31&lt;/cite&gt;, Subtitle 38; or</para>
          </para>
          <para num="(2)">Issue a citation under &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|1|§41-14"&gt;City Code Article 1, § 41-14&lt;/cite&gt; to a permit holder found to be in violation of:<para num="(a)">&lt;cite data-path="14.02.01"&gt;This chapter&lt;/cite&gt;; or</para>
            <para num="(b)">&lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31"&gt;City Code Article 31&lt;/cite&gt;, Subtitle 38.</para>
          </para>
        </para>
        <para num="B.">Notification of Violation.
If a permit holder is found to be in violation during a compliance inspection, the Department shall:<para num="(1)">Issue a first warning to the permit holder noting the violation;</para>
          <para num="(2)">Issue a second warning to a permit holder if the violation recurs within 60 days of the first warning; and</para>
          <para num="(3)">Issue a citation if the violation recurs within 60 days of the second warning.</para>
        </para>
        <para num="C.">Abatement Period.
The Department shall:<para num="(1)">Grant an abatement period to a permit holder to fix a violation; and</para>
          <para num="(2)">Issue an additional citation to a permit holder who commits an additional violation within 60 days of a granted abatement period.</para>
        </para>
        <para num="D.">Appeals<para num="(1)">A permit holder may appeal:<para num="(a)">A civil citation to the District Court of Baltimore City; or</para>
            <para num="(b)">An environmental citation to Environmental Control Board.</para>
          </para>
          <para num="(2)">For a citation issued in accordance with &lt;cite data-path="14.02.01.26|D.|(1)|(b)"&gt;§ D(1)(b) of this regulation&lt;/cite&gt;, a permit holder may appeal a decision rendered by the Environmental Control Board to the Circuit Court.</para>
        </para>
      </section>
    </container>
  </container>
  <container prefix="Subtitle" num="03" heading="Right of Way">
    <container prefix="Chapter" num="01" heading="Street Cuts">
      <section prefix="Regulation" num=".01" heading="Adoption, Applicability and Scope of Regulations.">
        <para num="A.">These rules and regulations are promulgated by the Baltimore City Department of Transportation (“DOT”) pursuant to &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|26"&gt;City Code Article 26&lt;/cite&gt;, Subtitle 15.</para>
        <para num="B.">These rules and regulations are in addition to all applicable laws found in &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|26"&gt;Baltimore City Code Article 26&lt;/cite&gt;, other applicable sections of Baltimore City Code, and Maryland State Code.</para>
        <para num="C.">Scope of Regulations.<para num="(1)">These rules and procedures are intended to ensure proper excavation of the public way;</para>
          <para num="(2)">These rules and procedures are intended to ensure complete restoration of the public way to match preexisting conditions; and</para>
          <para num="(3)">These rules and procedures are intended to ensure the proper use of the public way while work is ongoing.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".02" heading="Definitions.">
        <para num="A.">In &lt;cite data-path="14.03.01"&gt;this chapter&lt;/cite&gt;, the following terms have the meanings indicated.</para>
        <para num="B.">Terms Defined.<para num="(1)">"ADA" means the federal Americans with Disabilities Act.</para>
          <para num="(2)">Bicycle Facility.<para num="(a)">"Bicycle facility" means infrastructure to accommodate or encourage bicycling.</para>
            <para num="(b)">"Bicycle facility" includes a:<para num="(i)">Bike lane;</para>
              <para num="(ii)">Bike parking facility;</para>
              <para num="(iii)">Storage facility; or</para>
              <para num="(iv)">Shared roadway specifically designated for bicycle use.</para>
            </para>
          </para>
          <para num="(3)">"Blanket permit" means an authorization that allows a person to undertake an action related to a street cut in the right-of-way without first applying for a street-cut permit for that location.</para>
          <para num="(4)">"Book of Standards" means the Baltimore City Department of Transportation Book of Standards, which is incorporated by reference into &lt;cite data-path="14"&gt;this title&lt;/cite&gt;.</para>
          <para num="(5)">"Crosswalk" means a pedestrian crossing delineated by:<para num="(a)">A pavement marking; or</para>
            <para num="(b)">Signage.</para>
          </para>
          <para num="(6)">"Decorative surface" means a non-functional, ADA-compliant element installed to aesthetically enhance or otherwise embellish a right-of-way.</para>
          <para num="(7)">"Demarcation materials" means a warning surface treatment applied to an affected roadway, including a:<para num="(a)">Flex post;</para>
            <para num="(b)">Monolithic curb; or</para>
            <para num="(c)">Vertical barrier.</para>
          </para>
          <para num="(8)">"Department" means the Baltimore City Department of Transportation.</para>
          <para num="(9)">"Directional boring" means a trenchless method of installing underground conduit and facilities with minimal impact along a prescribed underground path.</para>
          <para num="(10)">"Director" means the Director of Transportation or the Director's designee.</para>
          <para num="(11)">"Duration" means the time during which an activity required by a street cut occurs.</para>
          <para num="(12)">"Emergency" means a situation that arises as the result of an unforeseen event in which excavation is needed to abate imminent potential danger to life, health, or property.</para>
          <para num="(13)">"Excavation" has the meaning stated in &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|26|§15-1|(d)"&gt;City Code Article 26, §15-1(d)&lt;/cite&gt;.</para>
          <para num="(14)">Facility.<para num="(a)">"Facility" means utility infrastructure used for the provision of services.</para>
            <para num="(b)">"Facility" includes infrastructure for the transportation of:<para num="(i)">Water;</para>
              <para num="(ii)">Energy; and</para>
              <para num="(iii)">Telecommunications.</para>
            </para>
          </para>
          <para num="(15)">"Landscaped area" means an outdoor space improved with living vegetation or synthetic material designed to be visually appealing.</para>
          <para num="(16)">"Pavement marking" means a device or material that is used on a road to demarcate lanes and conduct traffic.</para>
          <para num="(17)">"Pavement type" means a reference to the material from which a road is constructed, including:<para num="(a)">Flexible material;</para>
            <para num="(b)">Rigid material; or</para>
            <para num="(c)">Composite material.</para>
          </para>
          <para num="(18)">"Performance security" means a:<para num="(a)">A performance bond;</para>
            <para num="(b)">An irrevocable letter of credit;</para>
            <para num="(c)">A cash deposit; or</para>
            <para num="(d)">A combination of the items noted in &lt;cite data-path="14.03.01.02|B.|(18)|(a)"&gt;§B(18)(a)&lt;/cite&gt;&lt;cite data-path="14.03.01.02|B.|(18)|(c)"&gt;-(c)&lt;/cite&gt; of &lt;cite data-path="14.03.01.02"&gt;this Regulation&lt;/cite&gt;.</para>
          </para>
          <para num="(19)">Person.<para num="(a)">"Person" has the meaning stated in &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|general|§1-107"&gt;City Code General Provisions Article, §1-107&lt;/cite&gt;.</para>
            <para num="(b)">"Person" includes a government entity that performs work on the right-of-way.</para>
          </para>
          <para num="(20)">"Primary street" means an arterial road as defined by the Department.</para>
          <para num="(21)">"PROWAG" means the Federal Public Rights-of-Way Accessibility Guidelines.</para>
          <para num="(22)">Right-of-Way (ROW).<para num="(a)">"Right-of-way" means an area intended to facilitate the movement of pedestrians that falls within the boundary lines of a public:<para num="(i)">Street, including a curb;</para>
              <para num="(ii)">Alley;</para>
              <para num="(iii)">Sidewalk;</para>
              <para num="(iv)">Footway; or</para>
              <para num="(v)">Property otherwise owned or controlled by the City of Baltimore.</para>
            </para>
            <para num="(b)">"Right-of-way" includes a public way as it is referred to in &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|31"&gt;Article 31 of the Baltimore City Code&lt;/cite&gt;.</para>
          </para>
          <para num="(23)">"Right-of-Way (ROW) permit" means a permit, including a street-cut permit, issued by the Department that allows temporary use of the public right-of-way to perform work related to facilities.</para>
          <para num="(24)">"Separate offense" means each day that a violation continues.</para>
          <para num="(25)">"Stop work order" means the issuance of an administrative order by the Department to cease work at an excavation site due to a violation of:<para num="(a)">The Baltimore City Code;</para>
            <para num="(b)">A regulation adopted under the Code of Baltimore Regulations Annotated; or</para>
            <para num="(c)">A condition of the permit until the violation is abated.</para>
          </para>
          <para num="(26)">"Street cut" means work which involves excavating a road.</para>
          <para num="(27)">"Street-cuts permit" means a permit required by or issued under &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|26|15"&gt;subtitle 15, of Article 26 of the Baltimore City Code&lt;/cite&gt;.</para>
          <para num="(28)">"Traffic Control Plan (TCP)" means an arrangement intended to preserve safe pedestrian and vehicular traffic to the greatest extent possible for the duration of work in a road.</para>
          <para num="(29)">"TMC" means the Department's Transportation Management Center.</para>
          <para num="(30)">"Traffic control channelization device" means a device used to:<para num="(a)">Warn roadway users of conditions created by work activities in or near the road; and</para>
            <para num="(b)">Guide roadway users for the duration of the work.</para>
          </para>
          <para num="(31)">"Unsafe condition" means an unsatisfactory physical condition existing at a street cut location that has the potential to result in injury, death, or property damage if not corrected.</para>
          <para num="(32)">"Utility" means a person that owns or operates facilities used to provide a transmittable service to customers, including:<para num="(a)">Electrical service;</para>
            <para num="(b)">Gas service;</para>
            <para num="(c)">Water service;</para>
            <para num="(d)">Sewer service, including stormwater drainage; or</para>
            <para num="(e)">Telecommunication networks.</para>
          </para>
        </para>
      </section>
      <section prefix="Regulation" num=".03" heading="Exceptions to Street-cuts Permits.">
        <para num="A.">Unless the work qualifies as an emergency excavation under &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|26"&gt;City Code Article 26&lt;/cite&gt;, §15-13, no person, including a City agency, may excavate in a Public Way without first obtaining a Street-cuts permit.</para>
        <para num="B.">Directional Drilling is not permitted within the City Right-of-Way<para num="(1)">for electrical utilities and facilities,</para>
          <para num="(2)">for other utilities and facilities, including sanitary and gas lines, without prior written approval from the Director.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".04" heading="Applications for a Street-cuts Permit.">
        <para num="A.">An application for a Street-cuts Permit<para num="(1)">shall include the following information:<para num="(a)">applicant name and contact information;</para>
            <para num="(b)">contractor name and contact information;</para>
            <para num="(c)">work location and address;</para>
            <para num="(d)">description of proposed work;</para>
            <para num="(e)">information for the Street-cut including:<para num="(i)">requested start date and time;</para>
              <para num="(ii)">requested end date and time;</para>
              <para num="(iii)">street lane, bicycle facility or sidewalk closures;</para>
              <para num="(iv)">use of steel plates;</para>
              <para num="(v)">length, depth and width of any trench;</para>
              <para num="(vi)">work which will occur on weekends;</para>
              <para num="(vii)">work which will occur at night;</para>
              <para num="(viii)">a Traffic Control Plan (“TCP”), if required;</para>
              <para num="(ix)">estimated number of Street-cuts; and</para>
              <para num="(x)">drawing showing the location, type, size, and TCP.</para>
            </para>
          </para>
          <para num="(2)">shall provide evidence of Performance Security in an amount specified on the DOT website at transportation.baltimorecity.gov/<para num="(a)">A single Performance Security may be used for multiple permits by the same contractor as allowed by the Department.</para>
            <para num="(b)">Contractors who fail to maintain a minimum Performance Security, as determined by the Director, shall be prohibited from working in the Public Way, unless specifically authorized by the Director.</para>
          </para>
          <para num="(3)">shall provide a point of contact in case of emergency that includes:<para num="(a)">a name, email address, and phone number;</para>
            <para num="(b)">someone who is available on a 24-hour basis.</para>
          </para>
        </para>
        <para num="B.">An applicant shall be required to submit the following for a permit:<para num="(1)">Drawings or acceptable sketches which shall include or identify:<para num="(a)">the size and location of each Street-Cut;</para>
            <para num="(b)">pavement restoration details;</para>
            <para num="(c)">pavement type; and</para>
            <para num="(d)">work that impacts any traffic on one of the following roadway classes, as defined by Roadway Functional Classification map located at https://transportation.baltimorecity.gov:<para num="(i)">Collector,</para>
              <para num="(ii)">Minor Arterial,</para>
              <para num="(iii)">Other Principal Arterial,</para>
              <para num="(iv)">Freeway and Expressway, or</para>
              <para num="(v)">Interstate Principal Arterial.</para>
            </para>
            <para num="(e)">a final pavement marking plan consistent with the applicable requirements for pavement marking as set forth in the Book of Standards issued by the Department of Transportation and the Department of Public Works (“DPW”) (the “Green Book”), including:<para num="(i)">bicycle facilities;</para>
              <para num="(ii)">parking facilities;</para>
              <para num="(iii)">crosswalks; and</para>
              <para num="(iv)">other pedestrian pavement marking.</para>
            </para>
          </para>
          <para num="(2)">Within 5 days of application submission, an applicant shall submit a color photograph including:<para num="(a)">the current pavement condition of the right-of-way;</para>
            <para num="(b)">the date; and</para>
            <para num="(c)">a time stamp.</para>
          </para>
        </para>
        <para num="C.">An applicant is required to submit a Traffic Control Plan (“TCP”).<para num="(1)">Traffic Control Plans are required when any of the following conditions exist:<para num="(a)">sidewalk closure or detour;</para>
            <para num="(b)">bicycle facility closure or detour; or</para>
            <para num="(c)">roadway closure or detour on a roadway.</para>
          </para>
          <para num="(2)">All lanes in the roadway shall be treated as travel lanes, unless clearly marked as a parking lane by a solid white line.</para>
          <para num="(3)">A TCP shall include:<para num="(a)">a site plan covering 2 to 3 blocks in each direction from the construction site;</para>
            <para num="(b)">the installation and location of advanced warning signs which include:<para num="(i)">for any roadway lane closure, a minimum of the following three advanced warning signs installed at least 300 feet apart, unless a request to change the spacing is submitted for prior approval:<para num="(A)">Road Work Ahead,</para>
                <para num="(B)">Right/Left/Center Lane Closed Ahead, and</para>
                <para num="(C)">a transition sign for the lane being closed.</para>
              </para>
              <para num="(ii)">for a parking lane closure, no arrow board is required; however, the following three advanced warning signs shall be installed at least 300 feet apart:<para num="(A)">Road Work Ahead,</para>
                <para num="(B)">Curb Lane Closed Ahead, and</para>
                <para num="(C)">a transition sign for the lane being closed.</para>
              </para>
              <para num="(iii)">for the closure of multiple roadway lanes<para num="(A)">an arrow board is required for each lane being closed, and</para>
                <para num="(B)">the placement of advanced warning signs as required by the Manual on Uniform Traffic Control Devices (“MUTCD”).</para>
              </para>
            </para>
            <para num="(c)">a flagging operation and multiple lane closure for utility cuts and work areas that extend more than 10 feet from the curb lane;</para>
            <para num="(d)">when a flagging operation is provided for by the applicant or required by the Department:<para num="(i)">all directions of travel must be controlled by a flagger;</para>
              <para num="(ii)">it must be noted on your application when working at a signalized intersection; and</para>
              <para num="(iii)">advanced warning signage must include Flagman Ahead signs;</para>
            </para>
            <para num="(e)">road closure detours shall<para num="(i)">be clearly signed to direct traffic around the road closure and reestablish travel back to the road after the closure;</para>
              <para num="(ii)">include the following advanced warning signs:<para num="(A)">Road Closed Ahead,</para>
                <para num="(B)">Detour ahead, and</para>
                <para num="(C)">Road Closed;</para>
              </para>
              <para num="(iii)">include a physical barrier at the actual road closure for all directions of travel;</para>
            </para>
            <para num="(f)">roadway classification;</para>
            <para num="(g)">a note to contact TMC each work morning prior to start of work and each afternoon at end of work;</para>
            <para num="(h)">all affected bicycle and pedestrian facilities and the traffic control for each;</para>
            <para num="(i)">traffic control channelization devices to be used;</para>
            <para num="(j)">location of all steel plates in the area affected;</para>
            <para num="(k)">information as to any pedestrian detours which shall:<para num="(i)">maintain a minimum 4 foot ADA accessible path for pedestrians when work is conducted on a sidewalk:<para num="(A)">the ADA accessible pathway may be located in a parking lane, and</para>
                <para num="(B)">shall have an appropriate physical barrier between vehicles and pedestrians;</para>
              </para>
              <para num="(ii)">if a sidewalk is to be closed, the closure must be at the nearest intersection crosswalk with signs directing pedestrians across the street, and<para num="(A)">the sidewalk on the opposite side of the street must be ADA accessible, and</para>
                <para num="(B)">must include a ramp and 4-foot pedestrian pathway;</para>
              </para>
            </para>
            <para num="(l)">information as to any bicycle facility detours which shall provide for or adhere to the following:<para num="(i)">lane and road closures include lane transitions for bicyclists, and</para>
              <para num="(ii)">if the bicycle lane cannot be maintained, an explanation of why it cannot be maintained and an alternate route for the bicyclist; and</para>
              <para num="(iii)">if a bicyclist must use the sidewalk as an alternate route, warning signage must include:<para num="(A)">Bike Lane Closure, and</para>
                <para num="(B)">Dismount and Walk Bicycle on Sidewalk;</para>
              </para>
            </para>
            <para num="(m)">any other TCP control needed for unique locations or work;</para>
            <para num="(n)">for Emergency work performed under a blanket permit, a trained and certified emergency traffic manager shall be on-site at all times until the contractor has provided the Department with a TCP which is approved.</para>
          </para>
          <para num="(4)">The following conditions, if not immediately corrected, constitute a violation of the Street-cuts permit and may result in a fine or issuance of a Stop work order:<para num="(a)">failure to obtain an approved TCP when required to do so,</para>
            <para num="(b)">failure to maintain at the work site a copy of the approved TCP for inspection, or</para>
            <para num="(c)">failure to adhere to the conditions of the TCP.</para>
          </para>
          <para num="(5)">No equipment, materials, or other construction matter is permitted to be staged or stored, in bicycle facilities, on sidewalks, or within other non-motorized travel facilities unless the contractor obtains<para num="(a)">prior written approval, and</para>
            <para num="(b)">any additional required permits.</para>
          </para>
        </para>
        <para num="D.">Applications for a Street-cuts permit are<para num="(1)">processed through the DOT Right-of-Way Permits Section which is located at 401 East Fayette Street, Lower Level, Baltimore, Maryland 21202;</para>
          <para num="(2)">on the DOT website under Quick Forms; and</para>
          <para num="(3)">submitted by email with all required information to &lt;u&gt;row.permit.documents@baltimorecity.gov&lt;/u&gt;.</para>
        </para>
        <para num="E.">The applicant listed on a Temporary Use Right-of-Way Permit<para num="(1)">is responsible for all work performed under the permit, including but not limited to any subcontractor; and</para>
          <para num="(2)">will receive any notice from the Department concerning the work.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".05" heading="Issuance of a Street-cuts Permit.">
        <para num="A.">A Street-cuts permit shall be issued upon<para num="(1)">the provision of the required information,</para>
          <para num="(2)">receipt by DOT of the required permit fees,</para>
          <para num="(3)">payment of the required Performance Security, and</para>
          <para num="(4)">correction of outstanding or unresolved deficiencies with existing permits.</para>
        </para>
        <para num="B.">It is the contractor’s responsibility to<para num="(1)">schedule the work, and</para>
          <para num="(2)">notify DOT of completion of the work<para num="(a)">with sufficient time for the work to be inspected and approved prior to the expiration of the permit; and</para>
            <para num="(b)">sufficient time constitutes notice to DOT a minimum of 48 hours prior to the expiration date of the permit.</para>
          </para>
        </para>
        <para num="C.">Notice to DOT of an Emergency Excavation shall be made by<para num="(1)">calling the Street-cuts Section, at 410-396-2889, between the hours of 7 am and 4:30 pm Monday-Friday;</para>
          <para num="(2)">calling the TMC, at 443-984-2189, 24 hours a day; or</para>
          <para num="(3)">email to &lt;u&gt;streetcuts@baltimorecity.gov&lt;/u&gt;, 24 hours a day.</para>
        </para>
        <para num="D.">A Blanket Permit shall be issued to a utility provider or the Department of Public Works (“DPW”) for Emergency Excavations only.<para num="(1)">A Utility provider with a Blanket Permit shall complete a permit application within<para num="(a)">18 hours of beginning the emergency excavation, or</para>
            <para num="(b)">the next business day.</para>
          </para>
          <para num="(2)">Emergency Excavations shall be inspected by DOT Street-cuts Section prior to backfilling of the excavation.<para num="(a)">The utility provider shall notify DOT Street-cuts Section that the excavation is ready for inspection.</para>
            <para num="(b)">Notice shall be made as set forth in &lt;cite data-path="14.03.01.05|C."&gt;Regulation .05.C&lt;/cite&gt;.</para>
          </para>
        </para>
        <para num="E.">A Street-cut permit fee shall be assessed in accordance with a fee schedule, established by the Director and approved by the Board of Estimates (“BOE”).<para num="(1)">Street-cut permit fees are in addition to the Temporary Use of the Right-of-Way Permit fee.</para>
          <para num="(2)">Current Street-cut permit fees are posted on the DOT website at    transportation.baltimore.gov/quick-forms.</para>
          <para num="(3)">Additional fees may be assessed as provided in these regulations and allowed by law.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".06" heading="Performance Schedule and Standards.">
        <para num="A.">Any person doing excavation work shall:<para num="(1)">always maintain the Street-cut permit on site, and</para>
          <para num="(2)">exhibit the permit when requested to do so by the Department.</para>
        </para>
        <para num="B.">If an excavation is interrupted by an agency of Baltimore City, the permittee shall<para num="(1)">notify DOT Street-cuts Section immediately, and provide the following information:<para num="(a)">permit number,</para>
            <para num="(b)">location of excavation,</para>
            <para num="(c)">City agency involved in the interruption,</para>
            <para num="(d)">City agency contact person,</para>
            <para num="(e)">City agency work order number,</para>
            <para num="(f)">expected length of the interruption, and</para>
            <para num="(g)">procedures taken to secure the site.</para>
          </para>
          <para num="(2)">Upon verification of an interruption caused by an agency of Baltimore City, the Street-cuts Section shall notify the permittee of<para num="(a)">additional time allowed under the permit to account for the interruption, and</para>
            <para num="(b)">any additional requirements pertaining to the permit.</para>
          </para>
        </para>
        <para num="C.">Prior to being given permission to disturb existing bicycle facilities, an applicant for a Street-cut permit shall provide proof that no alternative to such action is available.       D.   When restoring an open Street-cut a permittee must:<para num="(1)">comply with all conditions and requirements of the permit;</para>
          <para num="(2)">conform with current rules, regulations, and standards of Baltimore City; and</para>
          <para num="(3)">ensure restoration matches preexisting conditions.</para>
        </para>
        <para num="D.">Prior to beginning work in any roadway, the permittee shall<para num="(1)">meet with the Traffic Division to review and develop a pavement marking plan for the affected roadway; and</para>
          <para num="(2)">where the affected roadway has bicycle facilities, meet with the Traffic Division and the Bicycle Planning Section to review and develop<para num="(a)">a pavement marking plan, and</para>
            <para num="(b)">demarcation materials.</para>
          </para>
        </para>
        <para num="E.">When an Order to Remove or Relocate a Pole is issued by the Department it shall:<para num="(1)">be in writing and signed by the Director or the Director’s designee; and contain the following:<para num="(a)">name of the permit holder,</para>
            <para num="(b)">facts that support issuing a pole removal or relocation order, and</para>
            <para num="(c)">the location of the pole.</para>
          </para>
          <para num="(2)">The Order shall be served by:<para num="(a)">delivery to any employee, agent, contractor, or sub-contractor of the permit holder on site;</para>
            <para num="(b)">mailing or emailing a copy of the order to the address on file for the permit holder; or</para>
            <para num="(c)">sending a facsimile to the permit holder to the fax number on file for the permit holder.</para>
          </para>
          <para num="(3)">The location of the pole shall not create non-compliance with the ADA.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".07" heading="Pavement Repairs and Restoration.">
        <para num="A.">Regardless of cut type, repairs will be done in accordance with Baltimore City DOT Standards.<para num="(1)">The Book of Standards is located on DOT’s website at:
&lt;u&gt;https://transportation.baltimorecity.gov/transportation/bookofstandards&lt;/u&gt;.</para>
          <para num="(2)">The DOT Street Cuts Section has the authority to increase the requirements of pavement restoration beyond minimum standards shown in the standard details based on<para num="(a)">site conditions, and</para>
            <para num="(b)">Street-cuts permit application information.</para>
          </para>
        </para>
        <para num="B.">Applicants and contractors shall adhere to the Street-cuts policies contained in these regulations; however,<para num="(1)">the Director has the discretion to permit exceptions to this policy under special circumstances; and</para>
          <para num="(2)">such exceptions shall be approved by the Director in writing.</para>
        </para>
        <para num="C.">The following are additional requirements for pavement repairs:<para num="(1)">when a utility cut is within 5 feet of a new or preexisting cut, both cuts shall be encapsulated into a single patch<para num="(a)">by milling away the intervening existing surface to allow for a single surface patch when one cut is preexisting and one cut is new; or</para>
            <para num="(b)">by combining the cuts into a single full-depth patch when both cuts are new; and</para>
            <para num="(c)">combined patches are subject to applicable Baltimore City DOT Standards.</para>
          </para>
          <para num="(2)">During resurfacing, the longitudinal pavement joints shall be constructed within 6 inches of the lane lines and not within the travel lanes.</para>
          <para num="(3)">If more than 50 percent of an asphalt or asphalt overlaid (composite) roadway is disturbed during longitudinal or transverse trenching, the entire block shall be milled and resurfaced<para num="(a)">from curb to curb, or</para>
            <para num="(b)">to the median curb, if applicable.</para>
          </para>
          <para num="(4)">The entire intersection must be milled and resurfaced if<para num="(a)">an asphalt or asphalt overlaid (composite) intersection is trenched diagonally, or</para>
            <para num="(b)">more than 50 percent of the intersection is disturbed during longitudinal and/or transverse trenching.</para>
          </para>
          <para num="(5)">All utility cuts must be backfilled and compacted in accordance with<para num="(a)">Baltimore City Standards outlined in Article 32.01.10 of the City of Baltimore Department of Public Works Specifications for Materials, Highways, Bridges, Utilities, and Incidental Structures (the “Green Book’);</para>
            <para num="(b)">the standards are found at &lt;u&gt;https://generalservices.baltimorecity.gov/gs-majorprojects/greenbook&lt;/u&gt;.</para>
          </para>
          <para num="(6)">Suitable fill material must be placed in 6-inch lifts and tamped with a mechanical tamper; and<para num="(a)">material one foot below subgrade must be compacted to 92 percent,</para>
            <para num="(b)">material in the top one foot must be compacted to 97percent; and</para>
            <para num="(c)">compaction of all material must be per the Modified Proctor ASTM D1557 (“AASHTO T180”).<para num="(i)">In lieu of borrow, CR-6 or excavation fills, #57 stone may be used; and</para>
              <para num="(ii)">it must be placed in no greater than one-foot lifts and tamped with a mechanical tamper.</para>
            </para>
          </para>
          <para num="(7)">Crusher Run Aggregate (“CR-6”) or Graded Aggregate Base (“GAB”) must be used for the proposed roadway paving sub-base, and<para num="(a)">must meet the requirements of Article 32 11 23.10 of the Green Book; and</para>
            <para num="(b)">Recycled Concrete (“RC-6”) may not be used for the sub-base material.</para>
          </para>
          <para num="(8)">The Contractor must supply compaction testing results for<para num="(a)">any paving patch greater than 1,000 square feet in area, and</para>
            <para num="(b)">any trench longer than 100 feet.</para>
          </para>
          <para num="(9)">A permittee must submit to the Department, at streetcuts@baltimorecity.gov, within 24 hours of the compaction:<para num="(a)">a copy of the compaction test results;</para>
            <para num="(b)">relevant location;</para>
            <para num="(c)">work date(s), and</para>
            <para num="(d)">designated permit number</para>
          </para>
        </para>
        <para num="D.">Final pavement restorations must include:<para num="(1)">removal of temporary backfill;</para>
          <para num="(2)">properly squaring off all Street-cuts to the bottom of the sub-base;</para>
          <para num="(3)">proper permanent backfills and compaction as specified in &lt;cite data-path="14.03.01.07|C.|(5)"&gt;Regulation .07.C(5)&lt;/cite&gt;;</para>
          <para num="(4)">permanent street restoration as specified in<para num="(a)">these Street-cuts regulations;</para>
            <para num="(b)">the City of Baltimore DOT Standards; and</para>
            <para num="(c)">the DPW Green Book;</para>
          </para>
          <para num="(5)">the patch must be installed so that it will remain flush with the surrounding pavement for 1 year after the work has been completed, inspected, and approved.</para>
        </para>
        <para num="E.">For utility upgrades and repairs that are performed in advance of a scheduled DOT contract, DOT may, at its sole discretion, allow the permit holder to provide temporary pavement repairs<para num="(1)">based upon the timing of the work in relation to the DOT contract schedule and the extent of the proposed trench excavations necessary for the utility work;</para>
          <para num="(2)">the type of temporary repair to be allowed will be decided by the Department on a case-by-case basis; and</para>
          <para num="(3)">the temporary pavement trench repair must conform to the current backfill procedures.</para>
        </para>
        <para num="F.">If the permittee uses steel plates to secure the public way during construction, they shall conform to:<para num="(1)">the Green Book; and</para>
          <para num="(2)">Baltimore City DOT Book of Standards.</para>
        </para>
        <para num="G.">Crosswalks.
In executing a street cut that disturbs a crosswalk, a person shall ensure that:<para num="(1)">The crosswalk is restored in accordance with the "Continental Crosswalk" style standards outlined in the Book of Standards;</para>
          <para num="(2)">Notwithstanding the provisions of &lt;cite data-path="14.03.01.07|G.|(1)"&gt;§G(1) of this regulation&lt;/cite&gt;, the crosswalk is restored with a decorative surface that:<para num="(a)">Matches the characteristics of a preexisting decorative surface; and</para>
            <para num="(b)">Is in accordance with standards provided by the Department when applicable;</para>
          </para>
          <para num="(3)">Each portion of a disturbed crosswalk is restored, including a portion of a disturbed crosswalk that is:<para num="(a)">Faded;</para>
            <para num="(b)">Missing; or</para>
            <para num="(c)">Otherwise noncompliant with an expected standard.</para>
          </para>
          <para num="(4)">The crosswalk is restored from curb to curb, unless the undisturbed portion of the crosswalk is:<para num="(a)">Compliant with the Book of Standards; and</para>
            <para num="(b)">In good condition, meaning it is:<para num="(i)">In new or like-new condition;</para>
              <para num="(ii)">Free of fading;</para>
              <para num="(iii)">Free of peeling; and</para>
              <para num="(iv)">Not otherwise defective in a way that reduces its visibility;</para>
            </para>
          </para>
          <para num="(5)">Notwithstanding the provisions of &lt;cite data-path="14.03.01.07|G.|(4)"&gt;§G(4) of this regulation&lt;/cite&gt;, the crosswalk is restored from curb to curb when trenching is done lengthwise through the crosswalk; and</para>
          <para num="(6)">When required by the Department to resurface an intersection in its entirety, each abutting crosswalk is restored as required by &lt;cite data-path="14.03.01.07|G.|(4)"&gt;§G(4) of this regulation&lt;/cite&gt;.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".08" heading="Work by Utilities in Advance of a Scheduled DOT Contract.">
        <para num="A.">If a public or private utility owns a facility, or is planning to perform work, in a right-of- way that is scheduled to be repaved by the Department of Transportation, the utility shall:<para num="(1)">notify the Department of any planned utility work scheduled for the current fiscal year or the next 2 fiscal years within the limits of the Department’s scheduled repaving work;</para>
          <para num="(2)">coordinate such utility work with the Department;</para>
          <para num="(3)">investigate, test, repair and upgrade the utility’s existing facilities so that future maintenance or replacement will not be required for a minimum of 5 years after the right-of-way is repaved; and</para>
          <para num="(4)">immediately notify the Department of any emergency work that takes place in a rightof-way scheduled by the Department to be repaved during the current calendar year.</para>
        </para>
        <para num="B.">When DOT submits plans for its proposed work to all utilities several times during the design process, each utility shall consider and inform the Department of all the improvements it will need to make based on:<para num="(1)">uploads from DOT which will include scheduled roadways and repaving limits to the utility coordination platforms/software;</para>
          <para num="(2)">communication about scheduled roadways at the monthly utility coordination meetings held at DOT; and</para>
          <para num="(3)">any other communications between the Department and utility providers regarding scheduled roadway repaving locations.</para>
        </para>
        <para num="C.">When properly advised by a utility pursuant to &lt;cite data-path="14.03.01.08|B."&gt;Regulation .08.B&lt;/cite&gt;, DOT will consider delaying the advertisement, or altering the contract, to allow utility work to be completed first.</para>
      </section>
      <section prefix="Regulation" num=".09" heading="Violations and Fines.">
        <para num="A.">The following fineable offenses are for work being performed in a Public Way:

        &lt;table&gt;
          &lt;thead&gt;
            &lt;tr&gt;
              &lt;th&gt;Violation&lt;/th&gt;
              &lt;th&gt;Occurrence&lt;/th&gt;
            &lt;/tr&gt;
          &lt;/thead&gt;
          &lt;tbody&gt;
            &lt;tr&gt;
              &lt;td&gt;Failure to obtain a Street Cuts permit prior to beginning work or, in an emergency where permit cannot be obtained ahead of work, within 18 hours of an emergency street-cut (Absence of a permit at jobsite)&lt;/td&gt;
              &lt;td&gt;Daily&lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr&gt;
              &lt;td&gt;Unsafe job site, TCP setup, or other unsafe condition&lt;/td&gt;
              &lt;td&gt;Daily&lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr&gt;
              &lt;td&gt;Not reporting intended work forty-eight (48) hours prior and/or steel plate placement as required on permit&lt;/td&gt;
              &lt;td&gt;Daily&lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr&gt;
              &lt;td&gt;Compaction testing not performed&lt;/td&gt;
              &lt;td&gt;Daily&lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr&gt;
              &lt;td&gt;Non-compliant installation of steel plates&lt;/td&gt;
              &lt;td&gt;Daily&lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr&gt;
              &lt;td&gt;Not clearing away construction debris&lt;/td&gt;
              &lt;td&gt;Daily&lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr&gt;
              &lt;td&gt;Not providing for temporary patching or plating until full restoration is completed&lt;/td&gt;
              &lt;td&gt;Daily&lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr&gt;
              &lt;td&gt;Patch not flush with the surrounding pavement&lt;/td&gt;
              &lt;td&gt;Daily&lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr&gt;
              &lt;td&gt;Absence of identification markings (if faded, they must be refreshed daily)&lt;/td&gt;
              &lt;td&gt;Daily&lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr&gt;
              &lt;td&gt;Blocked travel lanes before 9:00 AM or after 3:00 PM on weekdays without prior written DOT authorization&lt;/td&gt;
              &lt;td&gt;Daily&lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr&gt;
              &lt;td&gt;Incorrect traffic control (TCP) setup and/or absence of the approved TCP in site&lt;/td&gt;
              &lt;td&gt;Daily&lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr&gt;
              &lt;td&gt;Use of unapproved materials&lt;/td&gt;
              &lt;td&gt;Daily&lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr&gt;
              &lt;td&gt;Failure to construct to Baltimore City standards&lt;/td&gt;
              &lt;td&gt;Daily&lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr&gt;
              &lt;td&gt;Final striping not completed within 15 calendar days of permanent restoration&lt;/td&gt;
              &lt;td&gt;Daily&lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr&gt;
              &lt;td&gt;Street Cuts not fully restored to be permanent within one hundred twenty (120) days from start of work in the public way&lt;/td&gt;
              &lt;td&gt;
                &lt;p&gt;Daily (beginning day 121 and each  day until permanent restoration is&lt;/p&gt;
                &lt;p&gt;complete)&lt;/p&gt;
              &lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr&gt;
              &lt;td&gt;Steel plates extending beyond thirty (30) days in the public right-of-way without an approved extension&lt;/td&gt;
              &lt;td&gt;Daily (beginning day 31 and each day until steel plating is removed and replaced with temporary patching or until full and permanent restoration is complete)&lt;/td&gt;
            &lt;/tr&gt;
            &lt;tr&gt;
              &lt;td&gt;Permanent patch failure within the one-year warranty period if not corrected with thirty (30) days of notice&lt;/td&gt;
              &lt;td&gt;
                &lt;p&gt;Daily (beginning day 31 and each day&lt;/p&gt;
                &lt;p&gt;until permanent restoration is&lt;/p&gt;
                &lt;p&gt;complete)&lt;/p&gt;
              &lt;/td&gt;
            &lt;/tr&gt;
          &lt;/tbody&gt;
        &lt;/table&gt;
      </para>
        <para num="B.">A schedule of fines as previously approved by the BOE for the violations set forth in &lt;cite data-path="14.03.01.09|A."&gt;Regulation .09.A&lt;/cite&gt; are<para num="(1)">posted on the DOT website at transportation.baltimorecity.gov; and</para>
          <para num="(2)">subject to amendment by the Director with the approval of the Board of Estimates.</para>
        </para>
        <para num="C.">Unless specifically provided, fines may be imposed by DOT without provision of a Pre-Fine Notice.<para num="(1)">The Street-cuts Section is not required to issue a Pre-Fine Notice for any violation observed during inspection operations; and</para>
          <para num="(2)">DOT will not issue a Pre-Fine Notice for failure to complete permanent restoration within 120 days.</para>
        </para>
        <para num="D.">In the case of failure to complete full restoration of the Public Way within 120 days of the start of work;<para num="(1)">the total fine amount imposed will be equal to:<para num="(a)">the number of days past 120 days until the restoration is completed (b) times the daily fine amount per violation.</para>
          </para>
          <para num="(2)">The following time periods are not included in the calculation of the 120-day period within which full restoration must be completed:<para num="(a)">the winter season, which is defined generally as the period from November 15 to March 15, or</para>
            <para num="(b)">when paving plants are closed as determined by the Department.</para>
          </para>
          <para num="(3)">Any permit holder that is not able to complete full restoration within the 120-day period must<para num="(a)">make a written request for an extension to the Street-cuts Section prior to the expiration of the 120-day period, and</para>
            <para num="(b)">demonstrate good cause for the extension.</para>
          </para>
          <para num="(4)">The Street-cuts Section may then grant written extension for a reasonable time to the permit holder.</para>
          <para num="(5)">When no request for an extension of the 120-day period has been granted:<para num="(a)">Street-cuts not completed within the 120-day restoration period are required to apply for a new permit;</para>
            <para num="(b)">the new permit start date is the expiration date of the previous permit;</para>
            <para num="(c)">the new permit expiration date is the expected date that permanent restoration will be complete for the street cut; and</para>
            <para num="(d)">the permit fee owed to the City is for the entire timeframe.</para>
            <para num="(e)">these requirements are in addition to any fines imposed.</para>
          </para>
        </para>
        <para num="E.">Steel plates may not extend beyond 30 days in the public way unless<para num="(1)">an extension has been granted by the Department; and</para>
          <para num="(2)">the extension notification can be found at &lt;u&gt;https://transportation.baltimorecity.gov/quick-forms.&lt;/u&gt;</para>
        </para>
        <para num="F.">Permanent patch failure within the 1-year warranty period will be given a 30-day notice for repairs:<para num="(1)">a new permit is required for the repair;</para>
          <para num="(2)">beyond the 30-day notice period, a fine will be imposed until such time as the patch is repaired and approved; and</para>
          <para num="(3)">an additional 1-year warranty will take effect starting from the day of final approval of the repair.</para>
        </para>
        <para num="G.">The following unsafe conditions existing at a Street-cut may result in a fine:<para num="(1)">utility trench, permanent patch within the warranty phase, or utility cut where paving restoration is left:<para num="(a)">1 inch or more below existing grade, or</para>
            <para num="(b)">2 inches or more above existing grade;</para>
          </para>
          <para num="(2)">Utility trench, permanent patch within the warranty phase, or utility cut on roadways with bicycle facilities where paving restoration is left:<para num="(a)">¼ inch or more below existing grade, or</para>
            <para num="(b)">½ inch or more above existing grade;</para>
          </para>
          <para num="(3)">debris left onsite by a contractor for 24 hours or more;</para>
          <para num="(4)">wooden boards placed over utility cut;</para>
          <para num="(5)">fenced site where the fence has collapsed;</para>
          <para num="(6)">an exposed excavation left unattended;</para>
          <para num="(7)">blocking of a bicycle facility by equipment, debris, vehicles, signs or other obstruction;</para>
          <para num="(8)">blocking a pedestrian walkway, crosswalk, curb ramp or other facility by equipment, debris, vehicles, signs or other obstruction; and</para>
          <para num="(9)">any circumstance where the contractor has left work in a state considered to be a substantial threat to public safety.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".10" heading="Stop Work Orders.">
        <para num="A.">The Director or the Director’s designee may issue a stop work order for work conducted on public right-of-way when it is determined that a violation of any of the following has occurred:<para num="(1)">State law or code;</para>
          <para num="(2)">City Code</para>
          <para num="(3)">DOT regulation; or</para>
          <para num="(4)">the requirements imposed by a permit issued for the project.</para>
        </para>
        <para num="B.">The Director or the Director’s designee may also issue a stop work order for any of the following:<para num="(1)">a project that endangers public health or safety; or</para>
          <para num="(2)">failing to abate a violation in a timely manner for which a notice was issued.</para>
        </para>
        <para num="C.">A stop work order shall<para num="(1)">be in writing;</para>
          <para num="(2)">signed by the Director or the Director’s designee; and</para>
          <para num="(3)">contain the following:<para num="(a)">name of the violator;</para>
            <para num="(b)">facts that support issuing a stop work order;</para>
            <para num="(c)">the location at which the violation occurred;</para>
            <para num="(d)">reference to the specific provision of law, regulation, or permit that has been violated; and</para>
            <para num="(e)">the remedial measures required for to abate the violation.</para>
          </para>
        </para>
        <para num="D.">The Department must serve a stop work order by<para num="(1)">delivering it to any employee, agent, contractor, or sub-contractor of the permit holder on site;</para>
          <para num="(2)">mailing or emailing a copy of the order to the address on file for the permit holder; or</para>
          <para num="(3)">sending a facsimile to the permit holder to the fax number on file for the permit holder.</para>
        </para>
        <para num="E.">A stop work order becomes effective as soon as it is served via one of the methods in Regulation 10.D., regardless of whether delivery is accepted.</para>
        <para num="F.">Upon the issuance of a stop work order the violator shall<para num="(1)">immediately cease all work as specified in the order and comply with all directives contained in the order to abate the violation, and</para>
          <para num="(2)">contact the Street-cuts Section to request on on-site inspection for correction of the violation<para num="(a)">by phone 410-396-5889 or</para>
            <para num="(b)">email &lt;u&gt;streetcuts@baltimorecity.gov&lt;/u&gt;.</para>
          </para>
        </para>
        <para num="G.">A stop work order remains in effect until the Department notifies the permit holder in writing of its termination or modification.</para>
        <para num="H.">Termination of the stop work order does not preclude separate enforcement action by the Department relating to the present or a subsequent violation.</para>
      </section>
      <section prefix="Regulation" num=".11" heading="Administrative Hearings.">
        <para num="A.">Any person aggrieved by a decision or action of the Department under &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|26"&gt;City Code Article 26&lt;/cite&gt;, subtitle 15, may appeal the decision or action to the Director.</para>
        <para num="B.">A person shall be notified in writing of an appealable decision or action taken by the Department, and the notice shall<para num="(1)">be sent<para num="(a)">via first class mail, and</para>
            <para num="(b)">by email or facsimile, to the email address or facsimile number on record for the aggrieved person.</para>
          </para>
          <para num="(2)">Email notification is effective as of the date of transmission by the Department.</para>
        </para>
        <para num="C.">An appeal of a decision or action shall be filed by requesting a hearing<para num="(1)">within 10 days of the date of notification, or the date of receipt of the notice, whichever occurs first,</para>
          <para num="(2)">in writing and sent to the DOT Street-cuts Section by<para num="(a)">first class mail to: Baltimore City Department of Transportation, Street Cuts Section, 520 Fallsway, Baltimore, MD  21202; and</para>
            <para num="(b)">by email to &lt;u&gt;streetcuts@baltimorecity.gov&lt;/u&gt;.</para>
          </para>
          <para num="(3)">If no timely request for a hearing is filed, the aggrieved person shall be deemed to have waived the right to an administrative hearing.</para>
        </para>
        <para num="D.">The hearing shall be scheduled within a reasonable time after a request for a hearing is received, and<para num="(1)">DOT shall send a Hearing Notice to the aggrieved person by<para num="(a)">first class mail and</para>
            <para num="(b)">electronic mail requesting receipt confirmation;</para>
          </para>
          <para num="(2)">the Hearing Notice shall<para num="(a)">set the date, time and location of the hearing,</para>
            <para num="(b)">designate the Hearing Officer; and</para>
            <para num="(c)">describe the purpose and nature of the hearing</para>
            <para num="(d)">set forth any rules or procedures that may be required by the Hearing Officer.</para>
          </para>
        </para>
        <para num="E.">A Hearing Officer<para num="(1)">may be any individual member of the DOT designated as such by the Director of the DOT; but</para>
          <para num="(2)">shall not be the DOT employee who made the decision or took the action being appealed; and</para>
          <para num="(3)">shall have discretion to set reasonable limits for<para num="(a)">the time for the aggrieved party to present its case;</para>
            <para num="(b)">the time for the agency response;</para>
            <para num="(c)">the time for, and any limits on, cross examination; and (d) the time for closing arguments.</para>
          </para>
          <para num="(4)">may shorten or extend any time limits designated in these regulations<para num="(a)">at his discretion, and</para>
            <para num="(b)">for good cause shown.</para>
          </para>
        </para>
        <para num="F.">Not later than 5 days after the date of the Hearing Notice, the aggrieved party shall advise DOT in writing, via first class mail and electronic mail requesting receipt confirmation,<para num="(1)">if it will be represented by counsel and identify its counsel; or</para>
          <para num="(2)">if the aggrieved party will not be represented by counsel, designate an individual to present the aggrieved party’s case at the hearing.</para>
        </para>
        <para num="G.">Formal evidence rules and trial procedures shall not apply, and the Hearing Officer<para num="(1)">may admit and give effect to evidence which possesses probative value commonly accepted by reasonable and prudent persons in the conduct of their affairs;</para>
          <para num="(2)">may exclude incompetent, irrelevant, immaterial, and unduly repetitious evidence;</para>
          <para num="(3)">may take judicial notice of general, technical, and scientific facts; and</para>
          <para num="(4)">shall give effect to the rules of privilege recognized by law.</para>
        </para>
        <para num="H.">All evidence, including records and documents, in the possession of DOT, the involved
City agency or the City of Baltimore which the Hearing Officer desires to utilize may<para num="(1)">be made a part of the record in the case, and</para>
          <para num="(2)">be received in the form of copies, excerpts, or by incorporation by reference.</para>
        </para>
        <para num="I.">The hearing shall<para num="(1)">proceed as follows:<para num="(a)">the Hearing Officer shall begin the hearing with a statement concerning the purpose of the hearing and the procedures that will be followed.</para>
            <para num="(b)">each party may present its case by narrative or by witnesses.</para>
            <para num="(c)">cross-examination of any witness shall be permitted; however, the parties will not be permitted to argue or engage in debate.  The Hearing Officer may reasonably limit or terminate cross examination at any time.</para>
            <para num="(d)">the Hearing Officer may question any witness or party at any time.</para>
            <para num="(e)">each party may present its final arguments and summarize its position.</para>
            <para num="(f)">each party shall have the right to make any additional statements before the hearing it terminated.</para>
            <para num="(g)">at the discretion of the Hearing officer, the hearing may be adjourned to another date, continued, and postponed.</para>
          </para>
          <para num="(2)">Notwithstanding the procedures in &lt;cite data-path="14.03.01.11|I."&gt;Regulation .11.I&lt;/cite&gt;., the Hearing officer may, in his discretion,<para num="(a)">decide the order and manner in which testimony and evidence is to be presented and</para>
            <para num="(b)">make changes to the hearing procedure.</para>
          </para>
        </para>
        <para num="J.">Following the hearing, the Hearing Officer shall<para num="(1)">make every attempt to render a decision within 30 days from the conclusion of the hearing,</para>
          <para num="(2)">base the decision on the facts and evidence introduced into the record,</para>
          <para num="(3)">prepare a decision of each hearing which contains the following information:<para num="(a)">date of the hearing,</para>
            <para num="(b)">name of the Hearing Officer;</para>
            <para num="(c)">name of the aggrieved party;</para>
            <para num="(d)">names, titles and affiliations of persons in attendance;</para>
            <para num="(e)">the purpose and nature of the hearing;</para>
            <para num="(f)">brief description of documents, testimony and data presented;</para>
            <para num="(g)">findings and conclusions of the Hearing Officer regarding the action or decision being appealed; and</para>
            <para num="(h)">the decision of the Hearing officer.</para>
          </para>
          <para num="(4)">send a copy of the decision to the aggrieved party, or his attorney of record; by<para num="(a)">first class mail, or</para>
            <para num="(b)">when provided, by email.</para>
          </para>
        </para>
        <para num="K.">Upon the direction of the Hearing Officer or the aggrieved party, a record of the proceedings may be made.<para num="(1)">The record is adequate if in the form of a tape recording.</para>
          <para num="(2)">The aggrieved party shall have access to the tape-recording during City business hours, and may have a transcript made at its expense.<para num="(a)">The City shall designate the transcriber, and</para>
            <para num="(b)">the cost of the transcript preparation shall be paid before the transcript is prepared.</para>
          </para>
        </para>
        <para num="L.">Within ten 10 days of DOT’s service of the final decision of the Hearing Officer, the aggrieved party may submit a written request for a review of the decision of the Hearing Officer,<para num="(1)">which shall be sent by<para num="(a)">first class mail to: Baltimore City Department of Transportation, Street Cuts Section, 520 Fallsway, Baltimore, MD  21202,  and</para>
            <para num="(b)">email to: streetcuts@baltimorecity.gov;</para>
          </para>
          <para num="(2)">if no written request for a review is filed within the time required by these rules, the aggrieved party will be deemed to have waived its rights to any further review of the decision of the Hearing Officer.</para>
        </para>
        <para num="M.">If a timely request for review is made, a Review Hearing Officer shall be appointed who<para num="(1)">may be an individual member of the DOT designated by the Director to serve as the Review Hearing Officer, but</para>
          <para num="(2)">shall not be<para num="(a)">the Hearing Officer or</para>
            <para num="(b)">the DOT employee who made the decision or took the action being appealed.</para>
          </para>
        </para>
        <para num="N.">The review shall proceed in the following order:<para num="(1)">prior to the review proceeding, any party may submit to the Review Hearing Officer and the other party, a brief containing a statement of facts and arguments;</para>
          <para num="(2)">the Review Hearing Officer shall begin the review hearing with a statement concerning the purpose of the review;</para>
          <para num="(3)">any party may present a brief articulation of its arguments and summarize its position;</para>
          <para num="(4)">any party may answer any questions posed by the Review Hearing Officer;</para>
          <para num="(5)">the Review Hearing Officer has the discretion to request additional testimony or evidence;</para>
          <para num="(6)">at the discretion of the Review Hearing Officer, the review hearing may be adjourned to another date, continued, or postponed.</para>
        </para>
        <para num="O.">Following the review proceeding, the Review Hearing Officer<para num="(1)">shall make every attempt to render a final decision of the review within 30 days;</para>
          <para num="(2)">may affirm, reverse, or modify the Hearing Officer’s decision;</para>
          <para num="(3)">shall consider the entire record;</para>
          <para num="(4)">shall make his decision in writing; and</para>
          <para num="(5)">shall send a copy of the decision to the aggrieved party.</para>
        </para>
        <para num="P.">The decision of the Review Hearing Officer shall constitute the final decision of the Director.</para>
        <para num="Q.">Under &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|26"&gt;City Code Article 26&lt;/cite&gt;, §15-36, a party aggrieved by a final decision of the Director may appeal that decision to the Circuit Court for Baltimore City in accordance with the Maryland Rules of Civil Procedure.</para>
      </section>
    </container>
    <container prefix="Chapter" num="04" heading="Curbside Commercial Permits">
      <section prefix="Regulation" num=".01" heading="Scope.">
        <text>&lt;cite data-path="14.03.04"&gt;This chapter&lt;/cite&gt; establishes:</text>
        <para num="A.">A framework for the temporary private use of public space in order to promote an active, accessible, safe, and vibrant urban environment;</para>
        <para num="B.">Restrictions on the location, construction, and use of a curbside facility;</para>
        <para num="C.">Insurance requirements for curbside facility permit holders;</para>
        <para num="D.">The application process for a curbside facility permit, including obtaining a minor privilege to construct the curbside facility;</para>
        <para num="E.">Responsibilities for permit holders;</para>
        <para num="F.">Enforcement of the Curbside Permit Guidelines; and</para>
        <para num="G.">Rules regarding revocation of a minor privilege.</para>
      </section>
      <section prefix="Regulation" num=".02" heading="Definitions.">
        <para num="A.">In &lt;cite data-path="14.03.04"&gt;this chapter&lt;/cite&gt;, the following terms have the meanings indicated.</para>
        <para num="B.">Terms Defined.<para num="(1)">“ADA” means the federal Americans with Disabilities Act.</para>
          <para num="(2)">“Applicant” means the individual or entity pursuing a permit under this policy.</para>
          <para num="(3)">“BCDOT” means the Baltimore City Department of Transportation.</para>
          <para num="(4)">“Curbside Facility” means the commercial spaces permitted and regulated by this policy.</para>
          <para num="(5)">“Dimension” means measurable width, length, depth, and height of a curbside facility using feet and inches.</para>
          <para num="(6)">“Floodplain” means the same as &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|7|§1-2|(w)"&gt;City Code Article 7, § 1-2(w)&lt;/cite&gt;.</para>
          <para num="(7)">“Floodplain district” means the same as &lt;cite data-doc="City of Baltimore, Md., Code" data-path="|7|§1-2|(x)"&gt;City Code Article 7, § 1-2(x)&lt;/cite&gt;.</para>
          <para num="(8)">“Forbidden road space” means portions of the public right-of-way including:<para num="(a)">Crosswalks,</para>
            <para num="(b)">Pedestrian ramps,</para>
            <para num="(c)">Bike lanes,</para>
            <para num="(d)">Transit lanes or facilities,</para>
            <para num="(e)">Driving lanes,</para>
            <para num="(f)">Intersection space,</para>
            <para num="(g)">No-parking zones,</para>
            <para num="(h)">Commercial truck bays,</para>
            <para num="(i)">Handicapped parking spots,</para>
            <para num="(j)">Fire lanes,</para>
            <para num="(k)">Garages or driveways, and</para>
            <para num="(l)">Restricted parking zones that BCDOT will not consider for a curbside facility.</para>
          </para>
          <para num="(9)">“Indoor area” means the interior space of a structure with a ceiling and sides enclosed by:<para num="(a)">A combination of permanent or temporary walls, windows, or doorways, whether open or closed, or</para>
            <para num="(b)">Other physical barriers extending from floor to the ceiling.</para>
          </para>
          <para num="(10)">“Local design standards” means neighborhood-specific aesthetic rules issued by Baltimore City.</para>
          <para num="(11)">“Membrane structure” means an element erected utilizing fabrics, foils, and other textiles with the support of tension cables.</para>
          <para num="(12)">“Minor privilege fee schedule” means a list of fees for minor privileges that is approved by the Board of Estimates and posted for public view on the BCDOT website.</para>
          <para num="(13)">“Minor privilege permit” means an approval of a temporary minor privilege” as defined by Baltimore City Charter, Article VIII, § 9.</para>
          <para num="(14)">“Modular” means a method of design and build with standardized units allowing for a streamlined process in the construction or dismantling of a curbside facility.</para>
          <para num="(15)">“Parking lane” means a space abutting the curb that is<para num="(a)">Designated for on-street public vehicle storage, and</para>
            <para num="(b)">Contiguous to the property to which the curbside facility permit is issued.</para>
          </para>
          <para num="(16)">“Partner agency” means the following Baltimore City agencies and entities:<para num="(a)">Fire Department,</para>
            <para num="(b)">Police Department,</para>
            <para num="(c)">Health Department,</para>
            <para num="(d)">Parking Authority of Baltimore City,</para>
            <para num="(e)">Planning Department,</para>
            <para num="(f)">Department of Housing and Community Development,</para>
            <para num="(g)">Baltimore Development Corporation,</para>
            <para num="(h)">Liquor Board, and</para>
            <para num="(i)">Environmental Control Board.</para>
          </para>
          <para num="(17)">“Permanently attached” means a curbside facility which is nailed or bolted to the rightof-way or an existing building.</para>
          <para num="(18)">“Permit holder” means a person or entity who has been issued a permit to operate a curbside facility.</para>
          <para num="(19)">“Protective vertical element” means a barrier designed to deflect a vehicular impact while protecting facility occupants, including:<para num="(a)">Water-filled Jersey barriers;</para>
            <para num="(b)">Weighed barrels;</para>
            <para num="(c)">Concrete barriers; or</para>
            <para num="(d)">Other portable barriers.</para>
          </para>
          <para num="(20)">“Stop work order” means a formal demand issued by the City requiring the permit holder to remove their facility from the right-of-way.</para>
          <para num="(21)">“Temporary” means something that lasts for period of time and is not permanent.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".03" heading="Restrictions.">
        <para num="A.">A Minor Privilege Permit for a curbside facility shall be restricted to a parking lane.</para>
        <para num="B.">BCDOT may consider installations within the following restricted parking zones:<para num="(1)">Loading zones,</para>
          <para num="(2)">Metered parking,</para>
          <para num="(3)">Valet zones, and</para>
          <para num="(4)">Street sweeping corridors.</para>
        </para>
        <para num="C.">A curbside facility may not be permanently attached to sidewalks, roads or buildings, and doing so may result in automatic permit revocation.</para>
        <para num="D.">A curbside facility may not use:<para num="(1)">Amplified music,</para>
          <para num="(2)">Live entertainment, or</para>
          <para num="(3)">Open flames.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".04" heading="Applicant Responsibilities.">
        <para num="A.">An applicant shall obtain all permits relevant to their curbside facility including:<para num="(1)">A minor privilege permit,</para>
          <para num="(2)">Other permits as required by law.</para>
        </para>
        <para num="B.">An applicant shall obtain commercial general liability insurance which:<para num="(1)">Provides coverage of one million dollars per occurrence,</para>
          <para num="(2)">Provides a minimum total aggregate of two million dollars, and</para>
          <para num="(3)">Designates the Mayor &amp;amp; City Council of Baltimore as an additional named insured.</para>
        </para>
        <para num="C.">An applicant shall obtain the following insurance policies to cover a curbside facility:<para num="(1)">Commercial general liability,</para>
          <para num="(2)">Umbrella insurance,</para>
          <para num="(3)">Worker’s compensation, and</para>
          <para num="(4)">Liquor liability if applicable.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".05" heading="Design Standards.">
        <para num="A.">A permit holder shall adhere to the following fire safety guidelines:<para num="(1)">A curbside facility built primarily out of untreated wood or other flammable material shall be built a minimum distance of ten feet from a building; and</para>
          <para num="(2)">A curbside facility built primarily out of fire-resistant material such as treated wood shall be built a minimum distance of five feet from a building.</para>
        </para>
        <para num="B.">BCDOT may not approve a curbside facility that:<para num="(1)">Functions as an indoor area;</para>
          <para num="(2)">Is within 15 feet of a fire hydrant;</para>
          <para num="(3)">Is within 15 feet of a pull-in bus stop;</para>
          <para num="(4)">Is within 15 feet of dumpster;</para>
          <para num="(5)">Is on a street with a running slope of five percent or more;</para>
          <para num="(6)">Is on a street with a posted speed limit above 30 miles per hour;</para>
          <para num="(7)">Is located in or interferes with the functions of forbidden road space;</para>
          <para num="(8)">Intrudes on the sidewalk;</para>
          <para num="(9)">Is not ADA compliant;</para>
          <para num="(10)">Is more than one level;</para>
          <para num="(11)">Obstructs visibility of a traffic control sign or street sign;</para>
          <para num="(12)">Blocks stormwater drainage; or</para>
          <para num="(13)">Permanently restricts access to utilities.</para>
        </para>
        <para num="C.">A curbside facility shall:<para num="(1)">Fit within the width of the parking lane;</para>
          <para num="(2)">Use a protective railing or barrier which does not obstruct visibility above three feet, as determined by BCDOT;</para>
          <para num="(3)">Provide for a minimum seven feet of clearance between the ground plane and overhead elements;</para>
          <para num="(4)">Have an entrance which:<para num="(a)">Is accessible via the abutting sidewalk,</para>
            <para num="(b)">Is at least 48 inches wide,</para>
            <para num="(c)">Is flush with the curb, and</para>
            <para num="(d)">Meets ADA compliance standards;</para>
          </para>
          <para num="(5)">Feature protective vertical elements within the parking lane which separate the curbside facility from forbidden road space;</para>
          <para num="(6)">Be free of any tripping or slipping hazards; and</para>
          <para num="(7)">Incorporate lighting and reflective elements.</para>
        </para>
        <para num="D.">A permit holder may incorporate the following weather mitigating elements:<para num="(1)">Canopies;</para>
          <para num="(2)">Umbrellas;</para>
          <para num="(3)">Transparent igloos or bubbles; and</para>
          <para num="(4)">Other protective elements approved by BCDOT.</para>
        </para>
        <para num="E.">An elevated curbside facility built flush with the curb shall be designed to support a minimum of 100 pounds per square foot.</para>
        <para num="F.">A curbside facility may be constructed using modular design practices.</para>
        <para num="G.">A curbside facility shall adhere to local design standards and adherence shall be reviewed on an annual basis.</para>
        <para num="H.">A curbside facility located within a floodplain district may be required to implement additional safety measures.</para>
      </section>
      <section prefix="Regulation" num=".06" heading="Application Process.">
        <para num="A.">An applicant is required to submit a site plan during the application submission process.</para>
        <para num="B.">A site plan shall be drawn to scale, clearly labeled and include the following:<para num="(1)">Dimensions,</para>
          <para num="(2)">Property limits,</para>
          <para num="(3)">Existing objects,</para>
          <para num="(4)">Location of a heating device to be used in the curbside facility, if applicable,</para>
          <para num="(5)">Site features including:<para num="(a)">Posted speed limit,</para>
            <para num="(b)">Grade of the roadway,</para>
            <para num="(c)">Pavement type,</para>
            <para num="(d)">Parking restrictions, and</para>
            <para num="(e)">Access to utilities.</para>
          </para>
        </para>
        <para num="C.">A permit application shall be reviewed by BCDOT within 60 days.</para>
        <para num="D.">BCDOT shall submit the application to partner agencies for review and comment during the 60-day review period.</para>
        <para num="E.">Following the review period, BCDOT may:<para num="(1)">Approve the permit application,</para>
          <para num="(2)">Request that the applicant revise the application, or</para>
          <para num="(3)">Reject the application.</para>
        </para>
        <para num="F.">Upon BCDOT approval, the applicant shall:<para num="(1)">Send a copy of the application via certified mail return receipt requested to abutting property owners to notify them of the proposed curbside facility; and</para>
          <para num="(2)">Provide the return receipt to BCDOT as proof of notification.</para>
        </para>
        <para num="G.">BCDOT shall submit the application to the Board of Estimates for final review and approval of the minor privilege permit application.</para>
        <para num="H.">An applicant shall pay a minor privilege fee assessed by the Board of Estimates upon the issuance of a minor privilege permit.</para>
        <para num="I.">Payment of the minor privilege fee shall be:<para num="(1)">By check or money order in the required amount, and</para>
          <para num="(2)">Payable to the Director of Finance.</para>
        </para>
        <para num="J.">The minor privilege fee is calculated by the method in the curbside commercial section of the minor privilege fee schedule approved by the Board of Estimates.</para>
        <para num="K.">A final site plan and payment shall be submitted to BCDOT Special Events section by:<para num="(1)">Mail addressed to BCDOT Special Events at the Harry S. Cummings Building at 401 East Fayette Street, Baltimore, MD 21202; or</para>
          <para num="(2)">In person at the lobby of the Harry S. Cummings Building on 401 East Fayette Street, Baltimore, MD 21202.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".07" heading="Permit Holder Responsibilities.">
        <para num="A.">A permit holder is responsible for the following maintenance tasks required to keep the curbside facility safe for consumption of food and beverage:<para num="(1)">Cleaning the curbside facility daily, including:<para num="(a)">Removing all trash and food waste, and</para>
            <para num="(b)">Implementing non-toxic preventative pest control measures;</para>
          </para>
          <para num="(2)">Securing tables and chairs so that they may not be used outside business hours; and</para>
          <para num="(3)">Repairing any structural failures or defects immediately upon discovery.</para>
        </para>
        <para num="B.">A permit holder may not serve patrons in a curbside facility with known structural or sanitation deficiencies.</para>
        <para num="C.">A permit holder who desires to make a structural alteration to an existing curbside facility shall<para num="(1)">Submit a new application for the alteration, including a site plan, and,</para>
          <para num="(2)">Be subject to review by BCDOT and its partner agencies.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".08" heading="Enforcement of Regulation Guidelines.">
        <para num="A.">A curbside facility is a temporary installation and BCDOT may require removal of the curbside facility:<para num="(1)">On a permanent basis if site conditions no longer permit the curbside facility to operate safely, or</para>
          <para num="(2)">On a temporary basis if removal of the curbside facility is necessary for reasons including:<para num="(a)">Maintenance or repairs within the public right-of-way,</para>
            <para num="(b)">Extreme weather event preparation,</para>
            <para num="(c)">Flooding, and</para>
            <para num="(d)">Other emergencies.</para>
          </para>
        </para>
        <para num="B.">A permit holder who fails to remove a curbside facility upon request may be liable for costs incurred by BCDOT in removing the curbside facility.</para>
        <para num="C.">A permit holder shall be subject to random inspections by BCDOT and partner agencies.</para>
        <para num="D.">BCDOT and partner agencies may enforce these regulations by:<para num="(1)">Investigating complaints,</para>
          <para num="(2)">Issuing warnings,</para>
          <para num="(3)">Issuing stop work orders,</para>
          <para num="(4)">Confirming the validity of permits, and</para>
          <para num="(5)">Recommending the revocation of permits.</para>
        </para>
        <para num="E.">The City and its agencies shall not be liable for costs associated with the removal, restoration, or replacement of a curbside facility.</para>
      </section>
      <section prefix="Regulation" num=".09" heading="Revocation of Minor Privilege.">
        <para num="A.">The City may revoke or refuse to renew a minor privilege.</para>
        <para num="B.">BCDOT may issue a stop work order for a curbside facility that is noncompliant with the rules in the curbside commercial regulations.</para>
        <para num="C.">A permit holder whose curbside facility is noncompliant with these regulations may have their minor privilege permit revoked without a hearing.</para>
      </section>
    </container>
    <container prefix="Chapter" num="05" heading="Parking – Persons With Disabilities and Helpers">
      <section prefix="Regulation" num=".01" heading="Scope.">
        <text>&lt;cite data-path="14.03.05"&gt;This chapter&lt;/cite&gt; establishes rules and regulations that govern reserved parking for persons with disabilities and their helpers, including:</text>
        <para num="A.">The application process for a reserved parking space; and</para>
        <para num="B.">The renewal process for a reserved parking space.</para>
      </section>
      <section prefix="Regulation" num=".02" heading="Definitions.">
        <para num="A.">In &lt;cite data-path="14.03.05"&gt;this chapter&lt;/cite&gt;, the following terms have the meanings indicated.</para>
        <para num="B.">Terms Defined.<para num="(1)">Applicant.<para num="(a)">“Applicant” means a person applying for a disabled parking space.</para>
            <para num="(b)">“Applicant” includes:<para num="(i)">A person with disabilities; and</para>
              <para num="(ii)">A helper.</para>
            </para>
          </para>
          <para num="(2)">“Department” means the Baltimore City Department of Transportation.</para>
          <para num="(3)">“Director” means the Director of the Baltimore City Department of Transportation.</para>
          <para num="(4)">“Disability space” means a reserved parking space for a person with disabilities.</para>
          <para num="(5)">“Helper” means a person who:<para num="(a)">Renders assistance to a person with disabilities; and</para>
            <para num="(b)">Resides with the person with disabilities for whom a disability space is assigned.</para>
          </para>
          <para num="(6)">“PABC” means the Parking Authority of Baltimore City.</para>
          <para num="(7)">“Person with disabilities” means an individual that meets the criteria of City Code Article 31, §9-1(a)(1-3).</para>
          <para num="(8)">“Renewal application” means the form that is provided for a space-holder to complete annually to maintain a disability space.</para>
          <para num="(9)">“Space-holder” means a person that has received a disability space through an approved application.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".03" heading="Initial Application Process.">
        <para num="A.">An applicant applying for a disability space for the first time shall:<para num="(1)">Complete an application in the form that the Director requires; and</para>
          <para num="(2)">Acquire the application form by:<para num="(a)">Obtaining a copy from the PABC office; or</para>
            <para num="(b)">Downloading a copy from the PABC website.</para>
          </para>
        </para>
        <para num="B.">An applicant shall ensure a submitted application contains:<para num="(1)">The required medical documentation; and</para>
          <para num="(2)">The noted requirements as specified in the application.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".04" heading="Renewal Applications.">
        <para num="A.">To maintain an assigned disability space, a space-holder shall complete a renewal application  in accordance with these regulations.</para>
        <para num="B.">Distribution of Renewal Application.
The PABC shall:<para num="(1)">Ensure a renewal application is issued to a space-holder each year following the initial date that the disability space was awarded; and</para>
          <para num="(2)">Issue the renewal application to the address listed in the space-holder’s initial application.</para>
        </para>
        <para num="C.">A space-holder shall return a renewal application to the PABC within 90 calendar days of receipt.</para>
      </section>
    </container>
  </container>
  <container prefix="Subtitle" num="09" heading="Traffic">
    <container prefix="Chapter" num="01" heading="Public Traffic Calming Requests">
      <section prefix="Regulation" num=".01" heading="Scope.">
        <text>These regulations:</text>
        <para num="(1)">Implement a plan for fulfilling public service requests for traffic calming through the 311-system in Baltimore City;</para>
        <para num="(2)">Create a prioritization system for traffic calming that accounts for equity; and</para>
        <para num="(3)">Expand the toolkit of traffic calming options to promote safety and livability on City streets.</para>
      </section>
      <section prefix="Regulation" num=".02" heading="Definitions.">
        <para num="A.">In &lt;cite data-path="14.09.01"&gt;this chapter&lt;/cite&gt;, the following terms have the meanings indicated.</para>
        <para num="B.">Terms Defined.<para num="(1)">“Arterial street” means freeways, multilane highways, and other important roadways that supplement the United States Interstate System.</para>
          <para num="(2)">“BCDOT” refers to the Baltimore City Department of Transportation.</para>
          <para num="(3)">“Collector street” means major and minor roads that connect local roads and streets with arterials.</para>
          <para num="(4)">“Complete Streets” means a program in Baltimore City that enables access, mobility, economic development, attractive public spaces, health, and well-being for all people.</para>
          <para num="(5)">“Corridor” means the roadway and adjacent affected roadways where traffic calming is requested.</para>
          <para num="(6)">“Equity Priority Zones” means equity zones defined by the Complete Streets Manual.</para>
          <para num="(7)">“Local or neighborhood street” means roads that service limited vehicular traffic and are the primary access to residential areas, neighborhoods, and other local areas.</para>
          <para num="(8)">“Neighborhood” means community identified by the Baltimore City Planning Department’s official “Neighborhood Statistical Area Map”.</para>
          <para num="(9)">“Prioritization process” means procedure by which streets or corridors are selected and ranked for traffic calming projects.</para>
          <para num="(10)">“Service Request (SR)” or “311 Service Request” means a request made via phone or online to the Baltimore City 311 System.</para>
          <para num="(11)">“Stakeholder” means individuals or entities that are affected by &lt;cite data-path="14.09.01.02"&gt;this regulation&lt;/cite&gt;.</para>
          <para num="(12)">“Traffic Calming” means devices or methods used to slow the speed of traffic or reduce volume of traffic.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".03" heading="Initiation of the Traffic Calming Process.">
        <para num="A.">Arterial streets are:<para num="(1)">not subject to the requirements for local or collector streets; and</para>
          <para num="(2)">subject to a separate investigation process for alternative traffic calming measures.</para>
        </para>
        <para num="B.">A stakeholder requesting traffic calming in a neighborhood on a local or collector street shall:<para num="(1)">live within the neighborhood;</para>
          <para num="(2)">own or operate a business within the neighborhood;</para>
          <para num="(3)">represent a school or daycare facility within the neighborhood;</para>
          <para num="(4)">represent a Community Organization within the neighborhood; or</para>
          <para num="(5)">be a public, elected official, or his or her designee, whose district’s boundaries are within or include a portion of the City of Baltimore.</para>
        </para>
        <para num="C.">To initiate the traffic calming process, the Stakeholder must complete a 311 Service Request by:<para num="(1)">calling 311; or</para>
          <para num="(2)">filling out an online survey<para num="(a)">through the mobile phone application for 311 Service Requests; or</para>
            <para num="(b)">on City of Baltimore’s 311 website.</para>
          </para>
        </para>
        <para num="D.">A Stakeholder shall provide the following information to be considered for a traffic calming request:<para num="(1)">legal first and last name;</para>
          <para num="(2)">email address or phone number;</para>
          <para num="(3)">street address;</para>
          <para num="(4)">start and end points of the roadway segments where the need for traffic calming should be investigated;</para>
          <para num="(5)">a specific address or location where speed or cut-through traffic are of concern;</para>
          <para num="(6)">any relevant and necessary information regarding the traffic calming service request.</para>
        </para>
        <para num="E.">For BCDOT to consider a Service Request, the Stakeholder must provide the information found in &lt;cite data-path="14.09.01.03|D."&gt;Regulation .03D&lt;/cite&gt; in full.</para>
        <para num="F.">After submission, the stakeholder will be given:<para num="(1)">a time period for receiving an update for the service request;</para>
          <para num="(2)">the service request number; and</para>
          <para num="(3)">if using online or mobile application, a confirmation email with:<para num="(a)">A copy of the completed service request form; and</para>
            <para num="(b)">The information listed above in &lt;cite data-path="14.09.01.03|D."&gt;Regulation .03.D&lt;/cite&gt;.</para>
          </para>
        </para>
      </section>
      <section prefix="Regulation" num=".04" heading="Investigation of Traffic Calming Request.">
        <para num="A.">The BCDOT shall<para num="(1)">evaluate the need and feasibility of traffic calming, and</para>
          <para num="(2)">simultaneously provide the Service Request to the Baltimore City Fire Department for notification and feedback.</para>
        </para>
        <para num="B.">Data collection and analysis shall proceed immediately following the BCDOT determination of a valid request for traffic calming.</para>
      </section>
      <section prefix="Regulation" num=".05" heading="Data Collection and Analysis.">
        <para num="A.">BCDOT Traffic Division shall collect data within the study corridor.</para>
        <para num="B.">The information collected will be analyzed by BCDOT to determine if traffic calming is<para num="(1)">warranted, and</para>
          <para num="(2)">feasible.</para>
        </para>
        <para num="C.">Data collection units may be deployed on site to collect data related to speed.</para>
        <para num="D.">Data collection units shall be deployed based on engineering judgement.</para>
        <para num="E.">A site visit may be conducted to document conditions including:<para num="(1)">roadway grade;</para>
          <para num="(2)">roadway width and cross-section;</para>
          <para num="(3)">roadway horizontal geometry;</para>
          <para num="(4)">lane configurations;</para>
          <para num="(5)">adjacent land-use;</para>
          <para num="(6)">multimodal traffic operations; and</para>
          <para num="(7)">other related geometric and operational roadway features.</para>
        </para>
        <para num="F.">The following elements may be reviewed:<para num="(1)">crash data over the previous 6 years;</para>
          <para num="(2)">street type and target speed in accordance with the Baltimore Complete Streets Manual; and</para>
          <para num="(3)">Equity Priority Zones.</para>
        </para>
        <para num="G.">Local and collector roadways with longitudinal grades of 8 percent or lower that meet the traffic calming criteria for need and feasibility can proceed to the prioritization process.</para>
        <para num="H.">Local or collector roadways with longitudinal grades greater than 8 percent require further engineering review to determine the applicability and feasibility of<para num="(1)">traffic calming, or</para>
          <para num="(2)">other mitigation measures:</para>
        </para>
      </section>
      <section prefix="Regulation" num=".06" heading="Prioritization Process.">
        <para num="A.">Following data collection, and approval, BCDOT shall:<para num="(1)">Move the traffic calming Service Request forward to the prioritization process; and</para>
          <para num="(2)">Submit the Service Request for further engineering or review by Baltimore City Fire Department.</para>
        </para>
        <para num="B.">If the application does not meet the criteria threshold of the data collection and analysis, BCDOT shall issue a statement to the Stakeholder denying the Service Request.</para>
        <para num="C.">BCDOT shall prioritize traffic calming requests based on:<para num="(1)">Severity and prevalence of speeding based on initial data investigation and historical data;</para>
          <para num="(2)">Severity and prevalence of crashes based on historical data;</para>
          <para num="(3)">The presence of school zones; and</para>
          <para num="(4)">Equity Zones as identified on BCDOT’s Equity Map.</para>
        </para>
        <para num="D.">Prior to the beginning of construction season, the prioritization process will determine the construction program on an annual basis.</para>
      </section>
      <section prefix="Regulation" num=".07" heading="Community Involvement.">
        <para num="A.">Prior to implementation of traffic calming measures, BCDOT shall notify stakeholders of the following information:<para num="(1)">A summary of the traffic calming plan;</para>
          <para num="(2)">The timeframe of the project comment period; and</para>
          <para num="(3)">Contact information pertaining to comments or an opt-out request.</para>
        </para>
        <para num="B.">BCDOT shall notify stakeholders by:<para num="(1)">Postcard or letter;</para>
          <para num="(2)">Electronic communication;</para>
          <para num="(3)">Social media; or</para>
          <para num="(4)">Other community outreach methods.</para>
        </para>
        <para num="C.">BCDOT may post signs on the street in question with the information above.</para>
        <para num="D.">The following conditions apply to opt-out requests:<para num="(1)">Only opt-out requests from stakeholders abutting the immediate project block(s) shall be considered;</para>
          <para num="(2)">Stakeholders may be required to provide proof of residency when opting out;</para>
          <para num="(3)">Comments must be submitted within the specified response period.</para>
        </para>
      </section>
      <section prefix="Regulation" num=".08" heading="Construction Scheduling">
        <para num="A.">Upon conclusion of the public comment period and pending funding availability, BCDOT will schedule the traffic calming devices or measures for installation using the location’s score from the prioritization process.</para>
        <para num="B.">Local and collector streets that are approved for the installation of traffic calming measures will be scheduled for construction on an annual basis.</para>
        <para num="C.">Arterial streets may be scheduled for construction separately from local and collector streets to allow for additional analysis, more comprehensive treatments, or other factors.</para>
      </section>
      <section prefix="Regulation" num=".09" heading="Review">
        <text>After installation of traffic calming devices, BCDOT may review traffic calming devices for effectiveness.</text>
      </section>
      <section prefix="Regulation" num=".10" heading="Traffic Calming Devices">
        <para num="A.">Types and descriptions of traffic calming devices are available for review within the Design Guidance section of the Baltimore Complete Streets Manual.</para>
        <para num="B.">Options for traffic calming devices include:<para num="(1)">speed humps, speed tables, and speed cushions;</para>
          <para num="(2)">curb extensions, also known as bump-outs or bulb-outs;</para>
          <para num="(3)">rumble strips;</para>
          <para num="(4)">hardened centerline treatments;</para>
          <para num="(5)">raised crosswalks;</para>
          <para num="(6)">raised intersections;</para>
          <para num="(7)">chicanes;</para>
          <para num="(8)">mini-roundabouts, also known as neighborhood traffic circles;</para>
          <para num="(9)">traffic signal timing and operations;</para>
          <para num="(10)">vehicle access restrictions, such as median diverters;</para>
          <para num="(11)">traffic signal timing and operations;</para>
          <para num="(12)">reduction in travelway width;</para>
          <para num="(13)">reduction in number of through or travel lanes;</para>
          <para num="(14)">Slow Streets treatments;</para>
          <para num="(15)">any combination of these devices;</para>
          <para num="(16)">other available treatments or devices.</para>
        </para>
      </section>
    </container>
  </container>
</baltimore-city-law>
