Next Generation 9-1-1 Request for Proposal (i3 Functionality and Emergency Service IP Network) RFP # NCT-2011-23 ADDENDUM #3 12-May-10



Similar documents
Next Generation 9-1-1

The State of 911 Webinar Series. National 911 Program March 14, :00 PM

NG Deployments in U.S.A.

The on NG9-1-1 Part I of III

The number LEON COUNTY NG9-1-1, RFP # BC Addendum #3

Supplement No Telephone - PA P.U.C. No. 5 Palmerton Telephone Section 10 Company Original Sheet 1 UNIVERSAL EMERGENCY SERVICE NUMBER - 911

ENP Study Group Wireless-VOIP

Looking Beyond Data Synchronization for Mission Critical GIS Data

9-1-1 Services for Interconnected VoIP and Local Exchange Carriers

CITY OF OAK CREEK VoIP Telephone System Addendum

Glossary of Terms and Definitions

Geographic Information Systems (GIS)

CLEARSPAN 911/E911 Overview

INdigital ESinet SIP interconnection

NG9-1-1 Explained. John Chiaramonte, PMP, ENP. April 14, 2011

SMS to Overview

T-Mobile Text to Services

PURCHASING DEPARTMENT

SERVICES CATALOG. FRONTIER COMMUNICATIONS OF ALABAMA, LLC Section 16 Original Sheet 1 S16. CENTREX

EENA NG112 Committee. Long Term Definition Document Conference call 1 of February 2012

County of Stanly 201 South Second Street ALBEMARLE, NORTH CAROLINA 28001

GARTNER REPORT: SIP TRUNKING

CS4700/CS5700 Fundamentals of Computer Networking

IOWA STATEWIDE NG9-1-1 GIS STANDARDS. Presented by Iowa HSEMD and

9-1-1 Glossary of Terms

TLN VoIP Q&A Document

How To Use A Voip Phone For Free

Next Generation (NG9-1-1)

Federal Communications Commission. Next Generation 911

How the ETM (Enterprise Telephony Management) System Relates to Session Border Controllers (SBCs) A Corporate Whitepaper by SecureLogix Corporation

ADDENDUM. University of (702) ANSWER: A. INITIAL TERM. Page 1

Sprint s Partner Interexchange Network (PIN) A New Approach to Scalable Voice Peering

AT&T IP Flexible Reach Service

Clayton County Central Services

Request for Proposal RFP No. IT Phone System Replacement

NENA Information Document on: The Effect of Mass Calling Events on Legacy SR to PSAP Trunking

Kennesaw State University s Department of Sports and Recreation

ESINET NG911. Aparna Pragadeeswar Vinoth

Request for Proposals: Telecommunications and Local and Long Distance Services. Response to RFIs/Questions. Updated January 23, 2013

2014 National 911 Progress Report

Priority Access to PSAPs. Informational Packet

CENTURYLINK NG9-1-1 with Managed CPE Technical Service Exhibit for State of Arizona System

City of Woodinville, Washington

Dialogic. BorderNet Products Interwork and Connect Seamlessly and Securely at the Network Edge

Looking For Trouble: Emergency Call Handling Using Aruba Wireless LANs

EL SEGUNDO UNIFIED SCHOOL DISTRICT REQUEST FOR PROPOSAL (RFP) VoIP TELEPHONY INSTALLATION #06 16 ADDENDUM 2

Vega 100G and Vega 200G Gamma Config Guide

LOCATION DATA MANAGEMENT: THE ESSENTIAL GUIDE TO ALI MANAGEMENT BEST PRACTICES

Enhanced Enterprise SIP Communication Solutions

How To Buy a VoIP Phone System

ConneXon s response to Ofcom Consultation Document

November The Business Value of SIP Trunking

SIP Trunking: Evolution and Position in the Market Today VoiceCon, November 2008

EASYNET CHANNEL PARTNERS LIMITED PARTNER MASTER SERVICES AGREEMENT SIP TRUNKING SERVICE PRODUCT TERMS

Intrado Direct VPC Guide VoIP ALI Data Provisioning Process Version

SIP Trunking Steps to Success, Part One: Key Lessons from IT Managers Who ve Been There

COMPLETE YOUR GO-TO-MARKET PLAN BUSINESS SOLUTIONS BARRY DERRICK PRODUCT MARKETING MANAGER

PSTN Transition to IP

MARY ANN SAAR SECRETARY, DPSCS ROBERT L. EHRLICH, JR. GOVERNOR MICHAEL S. STEELE DEPARTMENT OF PUBLIC SAFETY AND CORRECTIONAL SERVICES

FRCC NETWORK SERVICES REQUEST FOR PROPOSAL

VoIP Solutions Guide Everything You Need to Know

Addendum SOLICITATION NAME ADDENDUM NUMBER. VOIP Telephone System C DATE

Understanding Lync 911 for Enterprises

Request for Proposal for Telephone System Hosted VoIP System On Premise VoIP System Hybrid IP System #RFP PHONE SYSTEM 1

SIP Trunking DEEP DIVE: The Service Provider

9 Summary of California Law (10th), Partnership

Request for Proposals Voice over Internet Protocol Unified Communications System /2016

Consolidating Network Infrastructure Resources in Contact Centers

Intrado V9-1-1 Services PSAP Methods and Procedures Version

MANDATE OF THE BOARD

NICE s NG9-1-1 Solution

An Introduction to SIP

SIP Trunking Quick Reference Document

Request for Proposals Voice over Internet Protocol Unified Communications System /2016

Dialogic BorderNet Session Border Controller Solutions

How To Make A Phone System More Reliable And Reliable

10 QUESTIONS TO ASK BEFORE YOU BUY PHONE SERVICE FOR YOUR BUSINESS SHARE THIS DOCUMENT 1

4G Americas Technical Report Analysis of Transitioning to NG9-1-1 from a Wireless Service Provider Perspective

Enabling Innovation - Unleashing Unified Communications: Best Practices and Case Studies. October 18-19, 2011

Transcription:

Next Generation 9-1-1 Request for Proposal (i3 Functionality and Emergency Service IP Network) RFP # NCT-2011-23 ADDENDUM #3 12-May-10 This addendum provides answers to questions received in writing as of May 5, 2011, 5:00 CDT. Questions were entered as received except for formattting changes necessary to avoid numbering confusion.

A 8 B 8 For the Data Centers locations do they want us to price all different options? For instance DataCenter 1 to all locations on Network A, Training Center to Network B. For instance DataCenter 1 to all locations on Network A, Datacenter 1a to Network B For Instance DataCenter 1a to all locations on Network A, Training Center to Network B For instance DataCenter 1 Network A, Datacenter 1a Network B, and Training Center Network B Do they want to just move all CAMA trunks from the TDM Legacy Selective routers to the new Host Datacenters and directly terminate on the VIPERs.. (NOT i3) and also put in a ESInet with the appropriate ESRP, SBC interfaces. In this way they could have both networks the Legacy (DOCK) and the ESInet (Boat) so they could gracefully move over time to i3. The reason for so many questions about tradition 9-1-1 trunking. NCTCOG is requesting one network interconnecting the two data centers housing the Viper hosts and the 42 remote PSAPs. Pricing for three data centers is being requested to determine if there is a price advantage to a given location. In the final configuration there will only be two data centers. It is anticipated that pricing for connectivity between the data center and the MPLS cloud; and connectivity between remote sites and the MPLS cloud are independent. Pricing should presented such that NCTCOG can chose any of the data center sites independently. At implementation it is anticipated that all traffic will continue to be routed via existing selective routers. CAMA trunks from the legacy selective routers will be terminated at the data centers housing the Viper hosts. Optionally, the ESInet Responder may provide a quote for SIP trunks directly into the ESRP located at each data center. This arrangement will be used as originating networks begin offering features and functions which support the NG vision. C 8 D 8 Do they want us to provide the conversion of all SS7, PRI, CAMA to VoIP (i3) Voice traffic and deliver it to their VIPERs with RFAI, or they want someone to provide all that conversion equipment. Do they want a provider to accommodate the TDM Traditional trunking until CSEC gets in place and does the traditional TDM converting to i3 for them. The LNG functions provides this conversion. It is being procured as part of the NG solution. The ESInet Responder is not required to do any conversions. The NCTCOG NG solution will interwork with CSEC's trial network. It should be noted that the NCTCOG solution must be self sufficient and provide all the functions required of an NG solution. E 1.6.1 F Page 15 section 1.6.1 bullet point three states that Notification of intent to propose shall be received by the deadline specified. However the deadline is not listed within the key dates. What is that date and how do you want the vendors to respond? How will questions be answered? Via email, web site, etc., and will all questions and answered be supplied to all respondents? Section 1.6.1, Bullet point three should be ignored. Attendance at the mandatory Pre Proposal Conference constitutes notification of intent to bid. Questions will be posted to the NCTCOG website as they are available. 2

G Are all four pricing scenarios mandatory? Are the Managed Services an option? The Responder may choose to propose a solution for any or all of the scenarios (A-D). It should be noted that NCTCOG currently provides Tier 1 Support and EGDMS services for the region. H 1.4 Will an extension for proposal deadline be granted? The deadline will not be extended. How is this project being funded? Grants, budget, etc. This project will be funded through the 2011 NCTCOG Strategic I Plan or budget allocated by the Commission on State Emergency Communications. 1. Reference: RFP 1.6.7 Proposal Term - All submitted proposals must be binding for a period of 180 days from the proposal submission deadline. Section 1.6.7 has precedence. J 1.6.7 RFP 14.1 Term & Conditions - F. NCTCOG reserves the right to hold and accept any proposal for a period of ninety (90) days after the response deadline. Q1. The two requirements have different binding periods. Which takes precedence? K 14.1 2. Reference: RFP 14.1 Term & Conditions Q2a. Would NCTCOG accept proposed contract redlines from Respondents to be included with the RFP response package? Q2b. Will redlines to the terms and conditions result in being found non-responsive? Redlines to contract language will be accepted and should be included in the response. Submission of redlines will not result in being found nonresponsive. L 1.6.9.5 3. Reference: RFP 1.6.9.5 Price Proposal Structure Q3. Will a response be considered non-compliant if pricing is provided for only 2 or 3 of the four scenarios described in the RFP? Please refer to Addendum 1. 3

M 2.7 N 3.1 O 3.2 4. Reference: RFP Section 2.7: Q4. Some of the features listed are circuit-switched features requiring a physical connection (e.g., called party hold, caller ring back). Which of these features does NCTCOG have today? 5. Reference: RFP Section 3.1: Q5a. Of the connection types listed, which does NCTCOG have in place today? Q5b. Does NCTCOG require support of Legacy trunk types not used today? For example, how would NCTCOG use a simulated facility group.? 2.7.1 Call Party Hold - not required. 2.7.2 Caller Ring Back - not required. 2.7.3 Forced Disconnect - This is really just a requirement that the NG solution recognize a disconnect from the PSAP, release the talk path to the PSAP and pass a disconnect to the S/R or other originating network connection. Ring 2.7.4 Ringtone - It is required that the NG solution is capable of passing PSAP generated ringtone (and other PSAP generated tones and messages) to the selective router or other connected originating network. It is desired that the NG solution have the optional capability of generating ringtone to the selective router or other connected originating network in lieu of passing PSAP ringtone. Requirements in the RFP are based on published standards and is 6. Reference: RFP Section 3.2: Requirements in the RFP are based on published standards and is Q6. Which types listed (3.2.1 3.2.8) are in place today that require support? We respectfully request a clarification on the mandatory requirements needed today versus future requirements. Identifying mandatory requirements will allow for a more cost effective solution. 4

P 6.7.1 7. Reference: RFP Section 6.1.7: Q7. NENA 08-751 and 08-002 are initial NENA Stage 1 Requirements and Stage 2 Architecture documents that serve as a foundation for 08-003 (unpublished Standard stage 3 specification). NENA 08-003 clarifies Additional Data into 4 categories, Additional Call, Caller, Location, and PSAP data. Please clarify as to the specific type of additional data is being required here. NCTCOG is not in a position to address an unpublished specification. As well, there is not enough information available to determine what additional data will be available from endpoints (devices) or originating networks. The Responder should state current capabilities of the solution (if any) and any plans for future development of capability. Q 1.10.21 R 6.3 S 8.3.2 8. Reference: 6.1.12 and 1.10.2.1 : Q8. Is most of the NCTCOG ESInet infrastructure already in place? Section 1.10.2.1 describes an existing IP and MPLS network. Is the intention to replace or re-use this network? Does NCTCOG want that network expanded or a completely new network? 9. Reference: 6.3 Enhanced Routing: Q9. How does NCTCOG define enhanced routing in the context of NG9-1-1 (in contrast to Policy Based Routing)? 10. Reference: RFP 8.3.2: Q10a. Please define the expectation of fully-meshed configuration in the context of the ESInet NCTCOG requires. Q10b. Please clarify the expectation of should. Is this requirement mandatory? NCTCOG has a complete working MPLS network interconnecting the hosts and remotes. The pricing request for the ESInet infrastructure is to identify any benefits associated with partnerships or configurations emerging from activities related to providing a solution. The request is for a completely new network. Enhanced routing as used in this section refers call handling capabilities which result from policy routing. For instance, the capability through a web based application to quickly establish a polygon and provide temporary treatment to calls originating within that polygon is enhanced routing. Policy routing would be used to provide the underlying call handling. The requirement is that the customer premise router is capable of routing to multiple networks so that NCTCOG has the ability to implement a meshed network. T 8.3.13 11. Reference: RFP 8.3.13: Q11. Please clarify "opposite network". Does NCTCOG mean that the gateways/routers must be able to be configured remotely from a different network management domain? The requirement is that routers are configurable remotely from a different network management domain. 5

U 9.2.1.1 12. Reference: RFP 9.2.1.1: Q12. Please clarify the term, collectively available. Does this mean that the overall system will be available to process an emergency call 99.999% of the time or does this requirement apply to each individual component? The overall system should be available to 99.999% of the time. V 12 W 9.3.6 X 7.4 (1) 13. Reference: RFP 12 Training Plan Q13. Is this required in the proposal response or some time (e.g., 30 days) after contract execution? 14. Reference: RFP 9.3.6 Minor Trouble All problems not classified as Critical or Minor. Q14. We believe this requirement may be intended with the use of a different word, All problems not classified as Critical or Major. Please clarify. 15. Reference: RFP 7.4 number 1. Q15. We interpret requirement 1 is intended to include another word, Take GIS spatial data, convert it to ALI MSAG database formats (typically tabular) and What specific ALI MSAG database formats does NCTCOG require? Please clarify. The proposal must include "typical" training required for a technical professional that has worked with 9-1-1 CPE and/or GIS for 5 years. The Responder determines the definition of typical based on the software and hardware used in the solution. A more detailed training plan is to be produced as part of the project plan development which occurs within 30 days of contract execution. The trouble classification of "Minor" includes all problems which were not classified as either Critical or Major. NCTCOG currently uses Intrado 24, however the tool should be flexible to adapt to different formats. Y Figure 1 16. Reference: RFP Figure 1. Q16. Describe the distributed application processing requirements at the remote sites, given that the VIPERs are centrally located in Figure 1. The remote locations are remote PSAPs in a Viper Host-Remote configuration. 6

Z 6 17. Reference: RFP 6. Q17. What are the NCTCOG expected interconnection network points with the TX CSEC NG9-1-1 MPLS network (as described in CSEC RFP No. 477.1.00064)? Will it be Dallas, Austin, San Antonio, and/or Houston? Do you require four interconnections or two? The most cost effective connections for NCTCOG will be implemented. It is anticipated that Dallas is one of the most cost effective for NCTCOG. AA Appdx 1 18. Reference: Pre-Proposal Conference and Appendix 1. Q18. It appears that NCTCOG will deploy two new data centers. Is the winning Respondent permitted to collocate equipment in NCTCOG s data centers? Or is the Respondent expected to provide their own collocation to interconnect to the NCTCOG data centers? Responders should provide information which indicates cost savings related to collocation. BB 1.10.2.1 19. Reference: 1.10.2.1 Q19. NCTCOG is served by eight selective routers. Could NCTCOG provide their CLLI codes, their physical address, and the provider name of each? Physical addresses are not readily available. OWNER TANDEM NAME CLLI AT&T DALLAS DIAMOND DLLSTXDIDC0 AT&T DALLAS RIVERSIDE DLLSTXRIDS3 AT&T FORT WORTH EDISON FTWOTXEDDC3 AT&T WACO WASHINGTON WACOTX01DS1 AT&T WICHITA FALLS LAMAR WCFLTXNIDS2 CENTURYLINK ATHENS ATHNTXXA91W VERIZON CASH CASHTXXA2ED VERIZON DENTON DNTNXXA1ED VERIZON SAN ANGELO SANGTXXA02T CC 4.13 DD 6.1.13 Section 4.13 Ability to Trace a call in progress can NCTCOG clarify the requirement. In normal 911 operation every call is located as call is received. That provides the originating location of the caller what addition call Trace capability is being requested? Section 6.1.13 Are the Viper units transferring the accumulated calltaker notes and added data per NENA i3 specifications if no then how are the Viper units sending this information to the SR? This requirement must be read from the perspective of the NG solution. The call must be traced between the incoming port (originating network end) to the outgoing port (PSAP or port used to transfer end). This requirement is based on "NENA Baseline Next Generation 9-1- 1 Description". Recognizing that the standard does not yet specify how this is to be accomplished, the Responder may describe how the solution can adapt to address this type of capability once defined. 7

EE Clarification: the RFP is requesting a NENA i3 based solution but the RFP also references the RFAI specification which is not part of NENA i3. Is support for the RFAI interface required? The RFAI specification is not for example capable of PIDF-LO data as per NENA i3 thus implementing both on the ESInet would result in potential conflicts in functionality. RFAI is an interface specification as is CAMA, SS7, ISDN PRI, etc. The incumbent CPE provider supports this interface, therefore a solution with an RFAI interface provides the opportunity to utilize the incumbents capabilities. FF VIPER Capabilities for IP Connectivity: 1.0 ALI 2.0 ESInet with or without Gateway,,, NCTCOG currently uses the state provided ALI database which is an RS-232 interface. It is anticipated that IP ALI will be implemented during the NG transition. GG Viper: Text file of Ali Query to database Provider Text file OF ALI Return There is not enough information to provide a response to the item numbered 2.0. The assumption is this request is for a file of ALI query responses. If this is critical to final pricing or configuration of the solution the information will be provided during contract negotiations. Tandem s and their servicing End- Offices: served and or delivered to each PSAP NCTCOG does not have end office information. The tandems are: HH OWNER TANDEM NAME CLLI AT&T DALLAS DIAMOND DLLSTXDIDC0 AT&T DALLAS RIVERSIDE DLLSTXRIDS3 AT&T FORT WORTH EDISON FTWOTXEDDC3 AT&T WACO WASHINGTON WACOTX01DS1 AT&T WICHITA FALLS LAMAR WCFLTXNIDS2 CENTURYLINK ATHENS ATHNTXXA91W VERIZON CASH CASHTXXA2ED VERIZON DENTON DNTNXXA1ED VERIZON SAN ANGELO SANGTXXA02T 8

9-1-1 CAMA s per PSAP ALI Circuits & Ali Provider Per PSAP There are 2 to 8 CAMA trunks per PSAP for a total 174 trunks. Trunks are currently split between the host and remote. Host Tandem At At Host Remotes Total TRNG Diamond 2 0 2 Edison 12 8 20 Riverside 2 0 2 Lamar 1 1 2 II WFPD Edison 21 16 37 Riverside 1 1 2 Waco 1 1 2 CCSO Diamond 10 8 18 Riverside 14 15 29 Denton 0 4 4 MDLN Diamond 7 7 14 Edison 1 1 2 Riverside 19 15 34 Waco 2 2 4 Athens 1 1 2 Totals: 94 80 174 JJ Existing IP Scheme to all Effected PSAP s and or facilities The IP schema is adaptable such that the NG solution can be accommodated. If this is critical to final pricing or configuration the information will be provided during contract negotiations. 9

KK Current GIS DATA: SIF / WSF Capable, for ECRF functionality The NCTCOG spatial data can be published in WFS. We understand that SIF is part of a yet to be released NENA standard. The Responder should provide information regarding how their solution intends to address SIF. LL 6.1.5 Re: 6.1.5 Routing: Is NCTCOG intending to support a LIS with wireline, wireless and VoIP records? LIS, as envisioned in NENA's architecture, are implemented in originating networks. NCTCOG understands that this is not likely to become reality for some time. The Responder must describe how their solution deals with this reality. MM What is the average number of 9-1-1 calls per hour into the regional system? Calls per hour data is not currently available. The RFP provides the annual estimated calls at 1,125,000. If this is critical to final pricing or configuration of the solution the information will be provided during contract negotiations. NN OO 2.4.2 PP 2.5.8 What is the total number of civic address locations for the region? Does NCTCOG require support of this legacy feature in the NG9-1-1 system? We respectfully request a clarification on whether this is a mandatory requirement in an NG, IP environment. Identifying mandatory requirements will allow for a more cost effective solution. This feature may not be cost-effective to implement in a NG9-1- 1 system. We respectfully request clarification on whether this is a mandatory requirement, or if alternate long distance billing arrangements would be entertained. Our current geodatabase has 464,283 address points, but since it doesn't include addresses with units in most cases, we could estimate 500,000. 10

QQ 2.8.7 Does NCTCOG require support of this legacy feature in the NG9-1-1 system? We respectfully request a clarification on whether this is a mandatory requirement. Please explain why NCTCOG would want to accept anonymous calls on 9-1-1. RR 3.1.8 Does NCTCOG require support of this legacy feature in the NG9-1-1 system? We respectfully request a clarification on whether this is a mandatory requirement, given the implementation of the Viper systems. SS 4.7 This legacy feature may not be necessary or cost-effective to implement in a NG9-1-1 system. We respectfully request clarification on whether this is a mandatory requirement, or if alternate arrangements would be entertained. TT 4.12 Please see Question 21. This feature may not be cost-effective to implement in a NG9-1-1 system. We respectfully request clarification on whether this is a mandatory requirement, or if alternate arrangements would be entertained. UU 14.1.1 a. Is there a bond form? b. Will NCTCOG accept an annual renewable bond? A bond form is not provided. As indicated in the RFP, the bond must be in the amount equal to 100% of the contract price. 11