Request for Information (RFI) For Network Service Platforms 1 Background and Introduction In February 2012, Congress enacted The Middle Class Tax Relief and Job Creation Act of 2012, containing landmark provisions to create a nationwide interoperable broadband network for the police, firefighters, emergency medical service professionals and other public safety officials. The law s governing framework for the deployment and operation of this network, which is to be based on a single, national network architecture, is the new "First Responder Network Authority" (FirstNet), an independent authority within NTIA. FirstNet holds the spectrum license for the network, and is charged with taking all actions necessary to build, deploy, and operate the network, in consultation with Federal, State, tribal and local public safety entities, and other key stakeholders. This RFI requests information about potential network service platforms for the network. It is organized as a number of enablers, core services, and interconnection with emergency services, namely: Enablers: a. IP Multimedia System (IMS) b. Messaging c. Location d. Presence e. Evolved Multimedia Broadcast Multicast System (E-MBMS) f. Identity Management g. Device Management (expands Devices RFI questions to include network side) Core services/applications: a. Push-To-Talk (PTT) b. Voice over LTE (VoLTE) c. Rich Communications Services (RCS) d. Mission Critical Voice/ Direct Mode Interconnection with Emergency Services including: a. NG9-1-1 b. Commercial Mobile Alert System (CMAS) (aka Wireless Emergency Alerts (WEA)) 1 P a g e
FirstNet is requesting information to help determine future acquisitions, including contract requirements, and potential vendors. Specifically, FirstNet is looking for vendors with core competencies and demonstrated experience in developing and sustaining public safety quality products, and for products and services that have, but are not limited to, the following capabilities: Service Enablers enablers such as location and presence that provides the context, in these examples, to allow the development of useful applications for FirstNet end-users. Core Applications applications and platforms that are essential for First Responders such as Voice and Push-to-Talk. Emergency Services interconnection with existing emergency services such the evolving NG9-1-1 services and the existing Commercial Mobile Alert System (CMAS). 2 Purpose FirstNet is conducting market research as part of its planning for the potential future acquisition of network services to be used with the FirstNet Network (FNN). In accordance with FAR 15.201(e), responses to this RFI are not offers and cannot be accepted by the Government for the basis of forming a binding contract. This RFI is being issued solely for the gathering of information for planning purposes, and it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This RFI does not commit the Government to a contract for any supply or service whatsoever. Furthermore, the Government is not at this time seeking proposals and will not accept unsolicited proposals. Responders are advised that the Government will not reimburse vendors or any other organizations for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested parties expense. Not responding to this RFI does not preclude participation in a future RFP, if one is issued. Submissions will be used by FirstNet to determine the maturity of the market and the state of the industry for applicability to meet FirstNet needs and FNN interoperability. This RFI is a request for interested parties to describe their products, services, technical capabilities and demonstrated experience with LTE network services applicable to public safety along with other sustaining elements for a full FNN user ecosystem. All interested parties are requested to provide written responses to the criteria below. Small businesses to include 8(a), service disabled veteran owned, HUBZone, women-owned, and other small businesses are encouraged to provide timely responses to this RFI. In addition to providing essential information to plan acquisitions, a response to this RFI is necessary in order to assist FirstNet in determining the potential levels of interest and technical capability within the small business community to provide required equipment or elements. Responses to the RFI will be used to assist FirstNet in establishing the degree to which a small business set-aside is feasible, including the potential for small business/large business team arrangements. FirstNet is also investigating the industry s capability to provide additional services to include, but not limited to, priority, preemption, home network treatment for roaming users, class of service and quality of service 2 P a g e
treatment, application security architectures, local control and many other elements of the FNN architecture that will have network services implications. Information provided in response to this RFI will also be used to assess the viability of current market technical, managerial, operational and support capabilities available for determining to what level threshold and objective requirements should be set for the FNN. Submissions will be used by FirstNet to determine the maturity of the market and the state of the industry, which will be used to assist FirstNet in defining what objective requirements and potential business models are viable for a complete FirstNet operational environment. 3 Request for Technical Information Format FirstNet is providing a Microsoft Excel file appendices containing two Question / Answer templates for the vendor to submit with answers. It contains sixteen tabs at the bottom of the worksheet which provide these templates: Functional Responses Spreadsheets: IP Multimedia System (IMS) Messaging Location Presence, Network Address Book (NAB), and Groups Evolved Multimedia Broadcast Multicast System (E-MBMS) Identity Management Device Management (expands Devices RFI questions to include network side) Push-To-Talk (PTT) Voice over LTE (VoLTE) Rich Communications Services (RCS) Mission Critical Voice/ Direct Mode NG9-1-1 Commercial Mobile Alert System/ Wireless Emergency Services (CMAS/ WEA) Compliance Matrix Spreadsheet Technical Criteria The vendor must use these templates to submit their answers. All submissions must be in combinations of Microsoft Word and Excel formats. Responses must be submitted in both hard copy (two Binders) and soft copy (Microsoft Word and Excel) format. In addition to the requested responses, submissions should also include additional product and service specifications for FirstNet to reference as needed. These additional specifications and brochures do not count against the 100 page limit. Furthermore, responses must include any materials or sources referenced in the RFI response. We request the submission of product specifications as requested by each RFI to be in a binder and softcopy form. 3 P a g e
The assessment of capability statements will be based on the criteria as submitted via the Functional Responses Spreadsheet and Compliance Matrix Spreadsheet. Responders submitting capability statements for this project should limit submissions to data essential to the assessment. Any and all information obtained for these purposes will be used solely to assist the Government in understanding the capabilities available in the marketplace and thus results will not be disclosed to respondents. 3.1 Functional Responses Spreadsheet This spreadsheet contains a list of questions in one column and an additional column for vendor responses. After inputting responses, the totality of all the pages in this spreadsheet when printed must not exceed the number pages and font requirements described in Section 4 of these directions. Be aware that Microsoft Excel changes the font size that is printed if you force it to print so many pages wide and so many pages tall. To prevent the automatic change of font, it is suggested not to set the width of pages in the page layout. The vendor may set the height of each row of each requirement to fit the vendor s response for the requirement as the vendor sees appropriate without changing font sizes. All submissions must be in Word and Excel format. All submissions shall meet the font, paper orientation, paper size, and number of page requirements described in Section 4 of this RFI. 3.2 Compliance Matrix Spreadsheet To facilitate the understanding of requirements, the appendix of this RFI contains a matrix extracted from the original source of the requirements. The source documents are also available via the URLs that are contained in the References tab. This matrix was developed by FirstNet and is for network service platforms. The requirements listed in this document are subject to change as FirstNet continues to evolve the associated network architectures and business models. There are two steps for the vendor to fill out this spreadsheet: STEP #1 For each requirement, place an X in any one or more column labeled A, B, C, D, and E that appears after the Source Requirement column that best represents the compliance of your product to meet the requirement. Here are the column meanings A. Meets requirement now B. Meets requirement by EOY 2013 C. Partially meets the requirement (% complete selection) D. Requirement is defined on the company s roadmap E. No plans to meet this requirement 4 P a g e
STEP #2 For each requirement, indicate in the Column Vendor Response column, a brief comment that speaks about the selected input in Step #1. If vendor indicates, A. Meets requirement Nothing is required in the vendor response column B. Meets requirement by the EOY 2013 Nothing is required in the vendor response column. C. Partially meets the requirement In the vendor response column, provide a narrative on the part that meets the requirement) and when/if/never meeting the remainder. D. Requirement is defined on the company s roadmap In the vendor response column, provide Qtr/Yr requirement will be met. E. No plans to meet this requirement Nothing is required in the vendor response column An example appears on a subsequent page herein. The matrix does not count towards the 100 page limit for the Functional Responses spreadsheet indicated in section 3.1, but the vendor must limit responses in the Vendor Response column in this Compliance Matrix spreadsheet indicated in this section 3.2 to 10 lines for each requirement number in accordance to the font and page layout guidelines in section 4 without removing or adjusting the column size of the Vendor Response column. 5 P a g e
Figure 1 - Example Notional Matrix Reqt Number Requirement Description Source of Requirement Network Service Platforms Role [RACI] A) Meets Reqt now B) Meet reqt. by EOY 2013 C) Partially Meets Percent D) Roadmap Date E) Not in current plans Vendor Response (10 Line Maximum per Requirement Number) (When printed, this table must fit the width of 8.5" x 11" landscape oriented paper without affecting font size requirements described in RFI) The matrix does not count towards the 100 page limit 1. General Requirements 1.01 Infrastructure upgrades for the FNN SHALL be performed in such a way as to minimize outage areas, such as upgrading sites that are not adjacent. NPSTC Table 12: 4 Responsible 1.02 1.03 Applications deployed by FirstNet SHALL support device addressing. Applications deployed by FirstNet SHALL support user addressing. NPSTC Table 22: 2 NPSTC Table 22: 3 Accountable Accountable 6 P a g e
4 Instructions for Submissions 4.1 Format of Responses Responses must be submitted in both hard copy and soft copy (Microsoft Word and Excel) format. Hard copy submissions must be in the form of two binders with labeled section dividers that correspond with the RFI sections and worksheet tabs. Soft copy submissions must be submitted both via email and on a thumb drive. FACSIMILE SUBMISSIONS WILL NOT BE ACCEPTED. Submissions must maintain the existing formatting - landscape page layout, one-sided, single spaced, 11-point type (Times New Roman, Cambria, Calibri, or Courier fonts only) with halfinch margins. Vendor must use the MS Excel templates as described in Section 3 for their responses. Responses must include any materials or sources referenced in the RFI response. In addition to the requested responses, submissions should also include additional product and service specifications for FirstNet to reference as needed. On all submissions, please include your company's name, point of contact, address, phone number, DUNS number, CAGE Code, and Tax ID. Responders are advised that the Government will not pay for any information or administrative cost incurred in response to this announcement. Responders to this announcement are solely responsible for all expenses associated with responding to this RFI. The preferred North American Industry Classification System (NAICS) Code for this work is 517210 Wireless Telecommunications Carriers. Respondents can recommend an alternative NAICS code that corresponds to the capabilities presented in their response. 4.2 Key Dates Questions or clarifications to this RFI must be received via email to the Point of Contact cited below no later than Monday, July 22, 2013 at 5 pm Eastern Daylight Savings Time. The opportunity for clarification of this RFI will not change the submission deadline date identified above. All questions and answers will be made available in a FAQ format via an amendment to this RFI. Oral communications are not permissible. FedBizOpps will be the sole repository for all information related to this RFI. Submissions must be received via email by the Point of Contact cited below no later than Friday, August 30, 2013 at 5 pm Eastern Daylight Savings Time. 4.3 Protection of Marked Proprietary Information The Government acknowledges its obligations under the Trade Secrets Act (18 U.S.C. 1905) to protect information qualifying as confidential under this statute. Pursuant to this statute, the Government is willing to accept any proprietary (e.g., trade secret) restrictions placed on 7 P a g e
qualifying data forwarded in response and to protect it from unauthorized disclosure subject to the following: 1. Clearly and conspicuously mark qualifying data with the restrictive legend (all caps) proprietary with any explanatory text, so that the Government is clearly notified of what data needs to be appropriately protected. 2. In marking such data, please take care to mark only those portions of the data or materials that are truly proprietary (over breadth in marking inappropriate data as proprietary may diminish or eliminate the usefulness of your response - see item 3 below). Use circling, underscoring, highlighting or any other appropriate means to indicate those portions of a single page which are to be protected. 3. The Government is not obligated to protect unmarked data. Additionally, marked data that is already in the public domain or in the possession of the Government or third parties, or is afterward placed into the public domain by the owner or another party through no fault of the Government will not be protected once in the public domain. Data already in the possession of the Government will be protected in accordance with the Government's rights in the data. 4. Proprietary data transmitted electronically, whether by physical media or not, whether by the respondent or by the government, shall contain the proprietary legend, with any explanatory text, on both the cover of the transmittal e-mail and at the beginning of the file itself. Where appropriate for only portions of an electronic file, use the restrictive legends proprietary portion begins and proprietary portion ends. 5. Properly marked proprietary information will only be shared with Government personnel with a need to know and authorized contractor advisory and support personnel who are either statutorily or contractually bound to keep such information confidential and protect it against release to third parties. 4.4 Mailing Address Responses to the RFI must be submitted via e-mail to the contact indicated below. Questions concerning submissions should also be directed to: Thomas Dolislager Email: RFI-Core_Network_Services@firstnet.gov Binders and thumb drives must arrive within 2 days of email submissions and should be mailed to: FirstNet Network Service Platforms RFI Attn: Thomas Dolislager 3130 Crow Canyon Place, Suite 210 San Ramon, CA 94583, USA 8 P a g e