SECTION 251.7. Guidelines for Implementing Integrated Services  


Latest version.
  • (a) Purpose. It is the purpose of this rule to allow for the integration of appropriate technologies into the 9-1-1 call-taking equipment that enhance or facilitate the delivery of a 9-1-1 call (voice or text), while providing safeguards to protect the 9-1-1 equipment from failure due to the integration of faulty or inappropriate applications.

    (b) Definitions. Unless the context clearly indicates otherwise, terms contained in this rule are defined as shown in Commission Rule 252.7, Definitions.

    (c) Integrated Services. A regional planning commission (RPC) shall meet the following requirements for integration:

    (1) Integrated Services.

    (A) Eligible Services. Personal Computer (PC) based Integrated Workstation (IWS) 9-1-1 call-taking equipment has the capability of expanding the traditional 9-1-1 Automatic Number Identification (ANI) and Automatic Location Identification (ALI) feature functionality to allow for additional public safety software applications. The Commission is supportive of such advancement in emergency services call-taking capabilities; however, 9-1-1 funds may only be used for applications that are eligible strategic plan budget components for the purposes of the delivery of a 9-1-1 call. To ensure the integrity of 9-1-1 is maintained, only the following 9-1-1 funded and non-9-1-1 funded features are eligible integrated services:

    (i) Expanded or Supplemental Location Information;

    (ii) Call Recording and Playback;

    (iii) Paging;

    (iv) Texas Law Enforcement Teletype Services (TLETS);

    (v) Computer Aided Dispatch Gateway;

    (vi) Graphical/Mapping Displaying of Location;

    (vii) Call Handling Protocols;

    (viii) Information Management (MIS);

    (ix) Short Message Service (SMS); and

    (x) Real Time Text (RTT).

    (B) Other Services. Integrated services other than the above-mentioned applications must have a demonstrated applicability to the direct provisions of delivering 9-1-1 and emergency call-taking services and will require Commission approval.

    (C) System Security. Operating procedures must be established by the RPC, and security measures taken and demonstrated, to ensure that non-Commission-approved software applications cannot be integrated into the IWS platform. At no time should the 9-1-1 call-taking equipment permit access to the Internet.

    (D) Memory Usage. Baseline memory and CPU usage of the operating system should maintain the "80/20" performance rule, thereby demonstrating that 80% of the total memory and CPU is available to the operating system applications, while 20% of the total memory and CPU remains unused. The installation and use of software should not lead to the degradation of equipment or services subsequent to the installation of the ancillary software.

    (E) Testing. Prior to integrating and deploying the expanded applications onto a IWS 9-1-1 call-taking environment, the following testing must be completed according to Commission policy, to ensure the stability and reliability of the 9-1-1 system:

    (i) Documented "Lab" testing shall be completed by the IWS Vendor and RPCs or Districts demonstrating the successful integration of the authorized applications. Test scenarios should include documentation of the operating system requirements, detailed functionality results as each application is integrated and evaluated independently, and load testing results of all systems operating together on the IWS workstation.

    (ii) Documented "Live" testing in a PSAP shall also be completed by the IWS Vendor with cooperation and coordination by the RPC or District, demonstrating the successful integration of the authorized applications. Test scenarios should include documentation of the operating system requirements, detailed functionality results as each application is integrated and evaluated independently, and load testing results of all systems operating on the IWS workstation, as well as a standardized set of basic call-taking functions.

    (F) Testing Documentation. Documentation of the testing shall be maintained by the RPC, and submitted to the Commission upon request.

    (2) Graphical Display (Mapped ALI). Requirements of RPC. Prior to the implementation of graphical display of location information at a PSAP, a RPC shall meet the following requirements:

    (A) Develop a digital map in accordance with standards to be determined by the Commission.

    (B) Establish and adopt a database maintenance plan, including GIS data.

    (C) Perform testing to ensure that the telephone number (TN) data is mapping correctly on the PSAP screen prior to implementing mapped ALI "live" at a PSAP.

    (D) Submit a strategic plan amendment according to Commission policy.

    (d) Applicability to Emergency Communications Districts (Districts). This rule shall apply to Districts receiving 9-1-1 Equalization Surcharge funds.

Source Note: The provisions of this §251.7 adopted to be effective December 13, 1995, 20 TexReg 10187; amended to be effective May 31, 1998, 23 TexReg 5425; amended to be effective September 5, 1999, 24 TexReg 6711; amended to be effective July 6, 2003, 28 TexReg 4885; amended to be effective July 18, 2004, 29 TexReg 6621; amended to be effective June 3, 2014, 39 TexReg 4235; amended to be effective October 16, 2018, 43 TexReg 6815