Section 128.57 | County systems receiving disbursements to provide wireless 9-1-1 service.
(A) A countywide 9-1-1 system receiving a disbursement under section 128.55 of the Revised Code shall provide countywide wireless enhanced 9-1-1 in accordance with this chapter beginning as soon as reasonably possible after receipt of the first disbursement or, if that service is already implemented, shall continue to provide such service. Except as provided in divisions (B), (C), (E), and (F) of this section, a disbursement shall be used solely for the purpose of paying either or both of the following:
(1) Any costs of the following:
(a) Designing, upgrading, purchasing, leasing, programming, installing, testing, or maintaining the necessary data, hardware, software, and trunking required for the public safety answering point or points of the 9-1-1 system to provide wireless, enhanced, or next generation 9-1-1 service;
(b) Processing 9-1-1 emergency calls from the point of origin to include any expense for interoperable bidirectional computer aided dispatch data transfers with other public safety answering points or emergency services organizations and transferring and receiving law enforcement, fire, and emergency medical service data via wireless or internet connections from public safety answering points or emergency services organizations to all applicable emergency responders, exclusive of mobile radio service costs.
(2) Any costs of training the staff of the public safety answering point or points to provide wireless enhanced 9-1-1.
(B) A subdivision or a regional council of governments that certifies to the steering committee that it has paid the costs described in divisions (A)(1) and (2) of this section and is providing countywide wireless enhanced 9-1-1 may use disbursements received under section 128.55 of the Revised Code to pay any of its personnel costs of one or more public safety answering points providing countywide wireless enhanced 9-1-1.
(C) After receiving its July 2013 disbursement under division (A) of section 128.55 of the Revised Code as that division existed prior to the amendments to that division by H.B. 64 of the 131st general assembly, a regional council of governments operating a public safety answering point or a subdivision may use any remaining balance of disbursements it received under that division, as it existed prior to the amendments to it by H.B. 64 of the 131st general assembly, to pay any of its costs of providing countywide wireless 9-1-1, including the personnel costs of one or more public safety answering points providing that service.
(D) The costs described in divisions (A), (B), (C), and (E) of this section may include any such costs payable pursuant to an agreement under division (I) of section 128.03 of the Revised Code.
(E)(1) No disbursement to a countywide 9-1-1 system for costs of a public safety answering point shall be made from the 9-1-1 government assistance fund or the next generation 9-1-1 fund unless the public safety answering point meets the standards set by rule of the steering committee under section 128.021 of the Revised Code.
(2) The steering committee shall monitor compliance with the standards and shall notify the tax commissioner to suspend disbursements to a countywide 9-1-1 system that fails to meet the standards. Upon receipt of this notification, the commissioner shall suspend disbursements until the commissioner is notified of compliance with the standards.
(F) The auditor of state may audit and review each county's expenditures of funds received from the 9-1-1 government assistance fund to verify that the funds were used in accordance with the requirements of this chapter. All funds generated from the next generation 9-1-1 access fee imposed under sections 128.41 and 128.42 of the Revised Code may be used only for 9-1-1 related expenses.
Last updated September 14, 2023 at 4:38 PM
Available Versions of this Section
- September 29, 2013 – House Bill 59 - 130th General Assembly [ View September 29, 2013 Version ]
- September 29, 2015 – House Bill 64 - 131st General Assembly [ View September 29, 2015 Version ]
- October 3, 2023 – Amended by House Bill 33 - 135th General Assembly [ View October 3, 2023 Version ]