2005 Maine Code - §2926 — Emergency Services Communication Bureau

      1. Bureau established. The Emergency Services Communication Bureau is established within the Public Utilities Commission to implement and manage E-9-1-1.[2003, c. 359, §2 (amd).]
      2. System design. In consultation with the E-9-1-1 Council, the bureau shall develop all necessary system elements, standards and cost estimates necessary to provide for the installation and operation of a statewide E-9-1-1 system, including, but not limited to, the following:
   
A. Development of network design specifications; [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 E-9-1-1 call answering and dispatching; [2001, c. 439, Pt. EEEE, §3 (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; [1993, c. 566, §9 (new).]    
D. Identification of appropriate technology for system networks, public safety answering point equipment and data base requirements; [1993, c. 566, §9 (new).]    
E. Procedures for developing and maintaining address and routing data bases; [1993, c. 566, §9 (new).]    
F. Procedures for cooperation and coordination with telephone utilities and municipalities for implementation and maintenance; [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; [1993, c. 566, §9 (new).]    
H. Estimates of the cost of establishing an operational E-9-1-1 system; [2001, c. 439, Pt. EEEE, §3 (amd).]    
I. Procedures for collecting and administering the necessary funds for E-9-1-1; and [2001, c. 439, Pt. EEEE, §3 (amd).]    
J. Standards and procedures for developing and maintaining the system databases and for ensuring the confidentiality of those databases pursuant to section 2929. [2001, c. 439, Pt. EEEE, §4 (new).] [2001, c. 439, Pt. EEEE, §§3, 4 (amd).]
      2-A. Goal. To the extent possible, the bureau shall establish a total of between 16 and 24 public service answering points. The bureau shall seek to coordinate any reduction in the number of public service 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.[2003, c. 359, §3 (new).]
      3. Rulemaking. The bureau shall adopt by rule its standards, specifications and procedures developed under subsection 2, paragraphs A to F after consultation with the E-9-1-1 Council and following at least 3 public hearings geographically dispersed throughout the State.[1993, c. 566, §9 (new).]
      4. Technical assistance. The bureau may provide support for the development of street address information sufficient to support E-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.[1993, c. 566, §9 (new).]
      5. Call answering coverage. The bureau is not required to provide call answering coverage in counties or municipalities that choose not to participate in the E-9-1-1 system.[2001, c. 439, Pt. EEEE, §5 (new).]
      6. System databases. The system databases, wherever located or stored, are the property of the bureau and their confidentiality is governed by section 2929.[2001, c. 439, Pt. EEEE, §5 (new).]

Section History:

PL 1993,  Ch. 566,   §9 (NEW).
PL 2001,  Ch. 439,   §EEEE3-5 (AMD).
PL 2003,  Ch. 359,   §2,3 (AMD).