United States — Maine Act or statute

United States — Maine legislation

Maine Revised Statutes, Title 25, § 2926: Emergency Services Communication Bureau, 1993

The bureau is established to run Maine’s 9-1-1 system and must carry out planning, quality assurance, and technical support duties.

911 servicespublic safety answering pointsquality assurancerulemaking

Professional statute overview

Enactment structure, operative effect and source provenance

Official source

01

Purpose and legislative effect

“The bureau is established to run Maine’s 9-1-1 system and must carry out planning, quality assurance, and technical support duties.”

Use this record to locate individual provisions, understand the instrument’s recorded structure, and move from a research summary to the exact source text.

02

How the instrument operates

  1. 01

    Start with the recorded version

    Enacted 1993 · Source version 1 Oct 2025. The date shown identifies this source expression and should not be treated as proof that no later change exists.

  2. 02

    Locate the controlling provision

    Use the provision map, part headings and full-text filter to move from the broad subject to the exact legal language.

  3. 03

    Read conditions and exceptions together

    Keep subsections, definitions, provisos and cross-references in context before drawing a legal conclusion.

  4. 04

    Verify currency and official wording

    Confirm later legislation, commencement notices and corrections with the official publisher before advice, filing or reliance.

03

Research entry points

Selected provisions across the instrument. Open any row to continue with the exact stored text.

04

Source and current-law status

Source record view

Source record from legislature.maine.gov · Enacted 1993 · Source version 1 Oct 2025

Verify current force

The source record does not state a definitive current-law status. Check the official publisher and later amendments before relying on this text.

Source-indexed provision map

Sections and provisions

Search by section, heading, part or exact legal wording. Every result remains linked to the stored source record.

Showing 1 of 1 provisions

Provision
§ 2926Emergency Services Communication BureauProvision

The bureau is established to run Maine’s 9-1-1 system and must carry out planning, quality assurance, and technical support duties.

1. Bureau established. The Emergency Services Communication Bureau is established within the Public Utilities Commission to implement and manage 9‑1‑1, including the deployment of 9‑1‑1 service using emerging communications technologies, including, but not limited to, Internet protocol enabled services, that are capable of connecting users to public safety answering points. [PL 2025, c. 167, §22 (AMD).] 1-A. Quality assurance. The bureau shall develop and implement a quality assurance program to audit and monitor compliance with emergency dispatching standards, practices and procedures of public safety answering points. [PL 2009, c. 617, §6 (NEW).] 2. System design. In consultation with the 9‑1‑1 Council, established in Title 5, section 12004‑I, subsection 74‑A, the bureau shall develop all necessary system elements, standards and cost estimates necessary to provide for the installation and operation of a statewide 9‑1‑1 system, including, but not limited to, the following: A. Development of network design specifications; [PL 1993, c. 566, §9 (NEW).] B. Development of minimum public safety answering point requirements including 24-hour operation; emergency backup power; secured communication areas; separate administrative phone lines for nonemergency calls; call recording and playback equipment; TDD equipment, as defined in Title 35‑A, section 8702, subsection 6; maximum call handling times; and minimum mandatory staff training requirements for 9-1-1 call answering and dispatching; [PL 2019, c. 339, §5 (AMD).] C. After consultation with the affected public and private safety agency officials, identification of appropriate public safety answering point sites based on consideration of the existing dispatching capabilities of public and private safety agencies, the expressed preferences of municipalities throughout the State and overall system cost; [PL 1993, c. 566, §9 (NEW).] D. Identification of appropriate technology for system networks, public safety answering point equipment and database requirements; [PL 2025, c. 167, §22 (AMD).] E. Procedures for developing and maintaining address and routing database; [PL 2025, c. 167, §22 (AMD).] F. Procedures for cooperation and coordination with telephone utilities and municipalities for implementation and maintenance; [PL 2001, c. 439, Pt. EEEE, §3 (AMD).] G. Standards and procedures to establish the confidentiality and prevent the dissemination of reports and records handled by public safety answering points and of the bureau; [PL 1993, c. 566, §9 (NEW).] H. Estimates of the cost of establishing an operational 9‑1‑1 system; [PL 2025, c. 167, §22 (AMD).] I. Procedures for collecting and administering the necessary funds for 9-1-1; and [PL 2025, c. 167, §22 (AMD).] J. Standards and procedures for developing and maintaining the system databases and for ensuring the confidentiality of those databases pursuant to section 2929. [PL 2001, c. 439, Pt. EEEE, §4 (NEW).] [PL 2025, c. 167, §22 (AMD).] 2-A. Goal. To the extent possible, the bureau shall establish a total of between 16 and 24 public safety answering points. The bureau shall seek to coordinate any reduction in the number of public safety answering points to achieve this goal with any contractual obligations it may have or may enter into that are or could be affected by that reduction. Prior to implementing a reduction in the number of public safety answering points, the bureau shall make a finding regarding the need for the reduction based on an evaluation of the costs and benefits of the reduction, taking into account impacts on ratepayers, each affected municipality, plantation, county or unorganized territory and the State. [PL 2025, c. 167, §22 (AMD).] 2-B. Exceptions. Notwithstanding subsection 2‑A, the bureau may authorize the establishment of a public safety answering point on a determination that a public safety answering point is necessary to ensure public safety and access to 9‑1‑1 services. [PL 2025, c. 167, §22 (AMD).] 3. Rulemaking. The Public Utilities Commission shall adopt by rule the bureau's standards, specifications and procedures developed under subsection 2 after consultation with the 9‑1‑1 Council. [PL 2025, c. 167, §22 (AMD).] 4. Technical assistance. The bureau may provide support for the development of street address information sufficient to support 9-1-1 services. The bureau shall provide technical assistance to any municipality in the development of street address information at the request of the interested municipality, plantation, county or unorganized territory. [PL 2025, c. 167, §22 (AMD).] 5. Call answering coverage. [PL 2025, c. 167, §22 (RP).] 6. System databases. The system databases, wherever located or stored, are the property of the bureau and their confidentiality is governed by section 2929. [PL 2001, c. 439, Pt. EEEE, §5 (NEW).]
Section 2926Verify source

Legislative relationships

0 referenced instruments

Names are derived from the stored provision headings and citation-enrichment layer. Treat this as a research index and verify each relationship against the source text.

No structured legislative relationships were detected

The statute remains fully searchable by provision. Consult the source text for amendments and cross-references that have not yet been indexed.

Recorded versions and source checkpoint

1 version available in this collection

Current-law checkpoint
  • 1 Oct 2025 · currentEnglish

Source-linked research

Ask AI about this statute

The overview, provisions, and source records above are public. Continue in a separate conversation with this statute’s jurisdiction and source version attached.

About this LexChat collection

Statute information is organised from identified legislative sources for professional research. Corrections can be reported to hello@esheria.ai.