Request for Services 15-12

1.5 IN911 Background

1.5.1 Current IN911 Features, Functions and Capabilities

IN911 has evolved over time to an IP based, Emergency Services IP-network (ESInet) built to the NENA i3 standard. In addition, IN911 is used to provide connectivity, data sharing, i3 functions, language line as well as inbound and outbound 911 Text-services to the PSAPs in Indiana.

1.5.2 IN911 System Current Capabilities Detail

The following sections 1.5.2.1 – 1.5.2.7 provide specific details and information regarding the current IN911 ecosystem, including configurations, capacities, functions and capabilities.

1.5.2.1 Current Network Configuration (G-11 network)

1. 
   Redundant SS7 networking, including IS-41 messaging to support wireless carrier extended functions
   
2. 
   Provides operational bandwidth from 3 megs to 1 gig (site and application specific)
   
3. 
   Uses Router Ethernet over SONET with tertiary backup connections
   
4. 
   ESRP – dual geo-diverse ESRP’s in tandem mode, active / active
   
5. 
   Each originating service provider has connectivity to diverse LNG’s.
   
6. 
   LNG’s are dual homed with active routing to all ESRP’s
   
7. 
   ESRP supports all i3 functions and ATIS TCC/MSRP for text routing
   
8. 
   ECRF supports geospatial GIS call routing for all media types
   
9. 
   ALI-db / legacy ERDB for transitional call routing
   

1.5.2.2 ESInet

• 
  Physical network links between ESRP’s support layer 2 at 100MB to 1000MB speeds
  
• 
  VPN non-associated network between all ESRP locations
  

• 
  Fully redundant ESInet to PSAP connections
  
• 
  Tertiary connections use dedicated VPN/Metro Ethernet / Fiber
  
• 
  Currently utilizing dual 2800 series routers at each PSAP
  

1.5.2.3 i3 functional elements in operation in IN911

1. 
   LNG - all are SS7 (or PRI) to IP, fully redundant with no common fault domains
   
2. 
   LIS in the G-11 platform, this functional element is aliased by the NG-ALi
   

3. 
   BCF - this is in service in the G-11 network
   
4. 
   SIF in the G-11 platform, this functional element is aliased by the NG-ALi
   

5. 
   ECRF - this is in production in the G-11 network
   
6. 
   LVF - in the G-11 network, this functional element is aliased by the NG-ALi
   

7. 
   ESRP - this is in production in the G-11 network
   
8. 
   NG-ALI - not part of the i3 specification, but used to alias other FE’s in a
   

9. 
   LPG - this is in service in the G-11 network
   

1.5.2.4 Databases, GIS, ALI, p-ANi management

• 
  Legacy tabular routing - in the transition network service order inputs with civil addresses are LVF’d to a legacy MSAG, and the entries are used to emulate the SRdb in the ESRP.
  
• 
  Legacy pANI management is automated, and uses a web / secure CRT interface for the originating service providers (wireless and VoIP).
  
• 
  The NG-ALi platform also supports PS-ALi inputs and record validation and storage from legacy enterprise PBX customers to ensure continuity of service
  
• 
  The current G-11 platform provides geospatial routing for incoming text to 911 messages that enter the network using i3 and ATIS J-STD-110 protocols from the Intrado and TCS Text Control Centers (TCC’s)
  
• 
  GIS layer management is provided using a graphic based control interface.
  
• 
  Currently, due to the static nature of the GIS layers and the size of the state and local programs, this is provided as a managed function.
  

1.5.2.5 Text to/from 9-1-1 capabilities

• 
  Standardized, non-carrier specific, browser based application
  
• 
  Integrated mapping - with confidence polygon display
  
• 
  Rebid capability (where supported by the OSP)
  
• 
  Address resolution and automatic point display from a civil address
  

• 
  Dispatchers can initiate an outbound text session utilizing temporary, non-dialable numbers
  
• 
  Bi-lateral address recognition and automatic map display
  
• 
  System has an API into an SMS-C with connections to the SS7 IS41c network. The service provider is a trusted SMS originator
  

• 
  Fully i3 / ATIS compliant
  
• 
  Text session IRR at the workstation level
  
• 
  Full text history logging and recall at the network level
  

1.5.2.6 Disaster Recovery and service continuity capabilities (Messaging Evolution System, MEVO)

• 
  Virtual core operates as a hosted platform
  
• 
  Operates independently of IN911 PSAP facing FE’s and PSAP CPE
  
• 
  Supports configurations specific to each PSAP
  
• 
  Incorporates admin lines
  
• 
  Supports inter-agency call transfer with active directory service
  
• 
  Supports touchscreen IP phones, or alternate delivery methods
  
• 
  Call transfer
  
• 
  Call park / call hold
  
• 
  Re-bid
  
• 
  Call history
  
• 
  Archived and instant call content recording
  
• 
  Directory services
  
• 
  Positive disconnect
  
• 
  Recall previous connection
  

1.5.2.7 Other Networks using IN911 for Transport

• 
  Indiana Data and Communications System (IDACS)
  
• 
  Judicial Technology and Automation Committee system (JTAC)
  
• 
  Automated. Fingerprint. Identification. System. (AFIS)
  

1.5.3 PSAP Information

There are currently a combination of over 130 County and Municipal PSAPs in Indiana, but due to statutory consolidation, that number will eventually be less than 110 PSAPs.

For the purposes of this procurement, the following number of PSAPs are within the scope of this project and anticipated services.

1. 
   There are 91 County level Primary PSAP’s in the state as two of the counties operate in a consolidated facility (Fountain/Warren).
   
2. 
   Additionally, there are six (6) Indiana State Police (ISP) Posts connected to and served by IN911 as secondary PSAPs (calls transferred from a primary PSAP).
   

All of the 97 PSAPs are currently operational and fully deployed E9-1-1, Wireless Phase 1 and Phase 2 (91 County Primary, 6 Secondary ISP posts).

Additionally, all 97 PSAPs have the ability and are technically capable of receiving SMS-Text-to-91-1 via the Board sanctioned and provided web browser delivery method utilizing the capabilities of IN911.

60 of these 97 have implemented or are implementing a Board provided SMS Text to/from-911 solution specified in (Section 3)

Specific address information for each of the 97 Indiana PSAPs covered by this RFS will be made available to qualified respondents as appropriate and necessary for the refinement of costs and designs of proposed solution(s).

- The remainder of this page intentionally left blank -

Based on the results of a Board sanctioned statewide PSAP NG9-1-1 Baseline Assessment study completed in 2013, Figure 5 below depicts the status of each County (as of 9/2013) related to a determination of NG9-1-1 network readiness or whether a county is being served by a NG capable delivery network for voice and data.

The ultimate goal of the Board is to have this map completely green from an IN911 network perspective. While IN911 receives and routes all Wireless 9-1-1 calls to all Indiana PSAPs today, the actual physical delivery network that extends all the way to an answering PSAP may be provided by other system service providers and therefore IN911 interconnects to an equivalent functional element, typically legacy, like a Selective Router or ALI database to facilitate the delivery of wireless 911 calls.

In general, Those counties shown as not network ready (red) are still being served by traditional analog telephone networks and those that are shown as ready (green), are connected directly to the IN911 network.

This diagram is designed to familiarize respondents with the potential level of interoperability, interconnection or cooperative agreements necessary to operate or support IN911. It can be used for and referred to for costing purposes, outreach, coordination and preparation of RFS responses.

Additional due diligence, research and information gathering may be required on the part of Respondents.

1.5.4 Indiana System Service Providers (SSPs)

This diagram is designed to familiarize respondents with the potential level of interoperability, interconnection or cooperative agreements necessary to operate or support IN911. It can be used for and referred to for costing purposes, outreach, coordination and preparation of RFS responses.

Additional due diligence, research and information gathering may be required on the part of Respondents.



Figure Indiana System Service Providers For IN911

1.5.4.1 Current Basic IN911 interconnection arrangements

1. 
   LEC OSP / SSP interconnection inventory
   
   1. 
      GTE Indiana / Verizon / Frontier -
      
      1. 
         13 total LEC connection points including 3 out of state connections (OH)
         
   2. 
      United / Sprint / Embarq / CenturyLink
      
      1. 
         3 total LEC connection points, including 1 out of state (OH)
         
   3. 
      Indiana Bell / Ameritech / SBC / AT&T
      
      1. 
         4 total LEC connection points, including 1 out of state (KY)
         
   4. 
      Cincinnati Bell
      
      1. 
         2 LEC connection points both out of state (OH, KY)
         
2. 
   LEC OSP interconnection inventory (VoIP traffic)
   
   1. 
      1 logical connection to SEI (Southeastern RTC)
      
   2. 
      1 logical connection to TDS
      
   3. 
      1 logical connection to New Paris
      
   4. 
      1 logical connection to Citizens
      
   5. 
      1 logical connection to Comcast