PS-SETA_RFI.pdf

1 | P a g e

DEPARTMENT OF HOMELAND SECURITY

CYBERSECURITY AND INFRASTRUCTURE SECURITY AGENCY (CISA)

EMERGENCY COMMUNICATIONS DIVISION (ECD)

TITLE: Priority Services Scientific, Engineering, and Technical Assistance (PS-SETA)

Submit responses to: Karen.Ma@hq.dhs.gov and Toya.Reynolds@hq.dhs.gov no later than March 22, 2021, 5:00 pm EST.

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY: This RFI is issued solely for information and planning purposes and does not constitute a solicitation. Nonetheless, submitters should properly mark their responses if the information is confidential or proprietary.

Furthermore, those who respond to this RFI should not anticipate feedback with regards to its submission other than acknowledgment of receipt, should the submitter request an acknowledgement. In accordance with FAR 15.201(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. All submissions become the property of the Federal Government and will not be returned. Responders are solely responsible for all expense associated with responding to this RFI.

1. Background:

The PS program responds to White House tasking to address the communications needs for Continuity of Operations (COOP) and Continuity of Government (COG). Through priority enhancements to the national communications infrastructure, the Office of Emergency Communications Division (ECD) can effectively and economically address the COOP/COG needs while also providing a significant benefit of assured communications during NS/EP incidents to the broader national, state, local, and non-government NS/EP community. By cost-effectively leveraging the PSN, PS helps to ensure the preparedness of the nation to prevent, respond to, and recover from, threatened and actual domestic terrorist attacks, major disasters, and other emergencies. PS has, and will, continue to support NS/EP users’ telecommunications requirements during disasters and emergencies.

2. Objectives:

Maintaining PS is vital to the Government, including National Leadership, to ensure emergency communications are available to coordinate recovery efforts in responding to disasters and crises, including acts of terrorism and war. In maintaining PS in an all-hazards environment, the ECD requires contractor engineering, integration, coordination, program management support to enable priority services in the public networks and the residential networks (triple play).

The purpose of this PWS requires the Contractor comply with the appropriate approved architectures, programs, standards and guidelines for all work performed under this contract. Apply technical expertise in priority telecommunications services systems engineering in areas such as: PSN, PS wireline and wireless network technology, and engineering practices used by PTS carrier contracts, Local Exchange Carriers (LECs), mailto:Karen.Ma@hq.dhs.gov mailto:Toya.Reynolds@hq.dhs.gov

2 | P a g e

Competitive Local Exchange Carriers (CLECs), wireline access providers e.g. cable and fiber, wireless local access network technologies, i.e. WiFi and Commercial Mobile Radio Service (CMRS) and broadband providers; satellite communications providers;

telecommunications networks modeling and simulation; requirements development and verification; and performance analysis.

The Contractor shall provide assistance in the following areas:

• Management

• NGN PS Engineering

• PS Governance

• PTS Engineering

• NGN PS Wi-Fi - Cloud Engineering

• NGN-PS Cybersecurity Engineering

• NGN PS Cable - Satellite - Fixed Wireless Engineering

• Service Providers Council administration and execution

• Customer Services Support

• Telecommunications Service Priority (TSP) Operations

• Analysis Future Services Engineering

• Emerging Future NGN PS phases

3. Specific Requirements/Tasks:

3.1. Task 1 – Management: Plan, direct, coordinate, and control all work requirements contained herein. Determine the project organization and provide overall management of the work, personnel, and physical resources, and determine mechanisms for cost and schedule control. Designate a single program manager who is responsible for the cost, schedule, and technical performance of the contract and who will serve as the central point-of-contact for both management and technical matters. Maintain a program management office within 25 miles of ECD facilitate liaison on both technical and contractual matters.

3.1.1. Management Control: Technical and management activities to support execution of all actions under this contract. Include productivity and management methods such as quality assurance, progress/status reporting, and program reviews at the contract level. Provide centralized administrative, clerical, documentation, and related functions.

3.1.2. Task Management: Project Management Plan, describing the technical approach, organizational resources, and management controls that will be used to meet the cost, performance, and schedule requirements. Monthly Status Reports (MSRs) will describe the results of quality assurance monitoring and evaluate program activities. Conduct and host Quarterly Program Status Reviews (QPSRs) to provide visibility of contract activities and obtain guidance from the Government.

Coordinate QPSR date with the COR prior to each QPSR; reviews include a briefing that provides the following information:

• A summary of resource expenditures

• An overview of work completed, in-progress, and planned for each task

3 | P a g e

• Identification of problem areas encountered by task with recommended remedial actions

• Status of all issues identified during the course of the last review

3.2. Task 2 – NGN-PS Engineering: The contractor will assist the Government by providing engineering support during analysis of cost effective designs proposed by services providers, and the correct testing methodology for priority services capabilities in all Next Generation Networks Priority Services (NGN-PS) program phases and increments.

The contractor shall assist the Government in its review of vendor and carrier services provider technical documentation and testing plans for verification and validation of priority services capabilities. NGN-PS acquisition is planned in multiple phases and increments. NGN-PS Phase 1 and Phase 2 are DHS approved programs of record, with additional future phases planned.

• Phase 1: Priority Voice

• Increment 1: Core/Backhaul VoIP

• Increment 2: Wireless Access - LTE

• Increment 3: Wireline Access

• Phase 2: Wireless Data, Video and Information Services (3 carriers, 1 cable, Cyber proof of concept, Network Diversity proof of concept, 5G Voice proof of concept, Cloud proof of concept, Identity Credentialing and Access Management proof of concept, Satellite proof of concept)

• Phase 3: Wireless Data, Video and Information Services (3 cable, 1 new carrier, Cyber Assurance, Operational Assurance, Cloud pilot, Identity Credentialing and Access Management pilot, Wi-Fi proof of concept, Fixed Wireless proof of concept, Cable 10G proof of concept)

• Phase 4: Wireless Data, Video and Information Services (2 Cloud provider, private network, 6G proof of concept VVD&IS, Artificial Intelligence proof of concept, Machine Learning proof of concept, Quantum computing NexGen GWIDS proof of concept)

The contractor shall ensure that carrier service provider development is consistent with the Next Generation Networks Priority Services Functional Requirements Documents (FRD) and follow the NGN-PS Tailored Systems Engineering Life Cycle (SELC) review process.

The SELC process includes at a minimum, monthly technical status reviews, a Preliminary Design Review (PDR), a Critical Design Review (CDR), Test Readiness Reviews (TRR) before each developmental Captive Office Test (COT) or Network Services Acceptance Test (NSAT), and a Production Readiness Review (PRR). Contractor will evaluate carrier service provider documentation such as Network Services Architecture (NSA) design document; Requirements Traceability and Verification Matrix (RVTM); Functional and Performance Test Plan and Report; Requirements gap analysis report; Risk mitigation plan/strategy; Cybersecurity threat analysis and mitigations report; OAM&P AND NSVT plans, and Future Services Plan. Contractor will provide planning, analyses and

4 | P a g e requirements documentation for FRS, Key Performance Parameters (KPPs), RVTM, etc.

for voice, data and video NS/EP priority services.

3.2.1. Programmatic Support: Provide programmatic support through preparation for and participation in staff meetings, conference calls, and QPSRs, and updating the appropriate program documents to reflect changes in budgets, schedule, architectures, and requirements. It also includes providing summary minutes and agreed upon action items of all meeting with the service providers.

3.2.2. Technical Support: The contractor shall provide technical support activities that include, but are not limited to:

3.2.2.1. Participate in the initial and continuing evaluation effort and in the resulting process to engineer, implement, test, and deploy NGN-PS voice, video, and data solutions.

3.2.2.2. Review and evaluate designs and development efforts from PTS service provider contracts to recommend the best approach on the adequacy of these designs and development efforts to comply with the FRD, and to meet key performance parameters.

3.2.2.3. Work with service providers and vendors to identify standardized methodologies for NS/EP priority services that focuses on priority and quality of service (QoS) mechanisms. Priority mechanisms will include, but not be limited to: invocation of Access Class Barring (ACB), High Priority (HPA), Enhanced Access Barring (EAB), Allocation and Retention Priority (ARP), LTE paging priority, and Quality Class Identifier (QCI), exemption from overload control, use of differentiated services code point (DSCP) and measurement of voice quality or performance. The SETA shall assess the efficacy of these features in providing priority service and monitor feature compliance testing. The SETA will recommend and review service provider recommendations for adding additional features such as standardized Enhanced Multi-Media Priority Services (eMPS), data, video and information services priority mechanisms.

3.2.2.4. The SETA shall assess service provider compliance by monitoring the service provider’s implementation of the NGN-PS Tailored SELC process, unless ECD approves a service provider’s request for substitution of commercial best practices. Specifically, the SETA will monitor service provider design and development at the different SELC milestone phases and notify ECD of any variance in schedule or performance using an integrated master schedule (IMS) and RTVM. The service provider will conduct a series of SELC reviews for each phase of this project that details what priority capabilities they will provide, how they will fulfill the requirements and they will be verified, and when the service is ready for operation. Contractor will document increasing detail of how the FRD requirements will be met in a RTVM and IMS after each successive service provider SELC review and provide a quarterly presentation to ECD of service provider variance in schedule and performance.

3.2.2.5. The FRD addresses what requirements need to be addressed by the service provider, while the PDR and the CDR provide the design details of how

5 | P a g e the capabilities will address the requirements. The later stage reviews focus on assessment of service readiness and the mechanisms to continuously verify that the service is operating within its expected parameters by the use of testing and operational measurements. The later stages are supported by the developmental TRRs, one or more functional and performance COTs and NSAT, and the Production Readiness Review. At the end of each service provider’s SELC review and associated document acceptance by ECD, contractor will create CISA SELC process briefings and/or assessment reports for reviews.

3.2.2.6. Update the NGN-PS Engineering/Implementation Plan (EIP) to reflect information on NGN-PS as implemented by the PTS service provider, LECs, CLECs, and/or CMRS providers and Multiple System Operators (MSOs) based on their Service Engineering and Operations Plans, the results of acceptance testing, or information obtained at TIMs. When requested or needed, revise the FRD.

3.2.3. Subtask 3.3 – Ensure testing that is consistent with the NGN-PS Test and Evaluation Master Plan (TEMP) and work with the Operational Test Agent (OTA) to ensure that the relevant tests are being run and data are being collected as needed by the OTA

3.2.3.1. The contractor shall assist the Government in its review of vendor and service provider test plans and shall participate in testing events including service acceptance testing of priority service in PTS service provider contracts, LEC, CLEC, and MSO networks. Review and provide comments to the test plan, test cases, test reports and all other supporting test documents.

3.2.3.2. Review test plans and attend COTs or other Product Test activities intended to stress test NS/EP Priority Services software to verify it is capable of meeting the KPPs and the functional requirements specified in the vendor’s RVTM in a simulated all-hazards laboratory environment. Specifically, the COT verifies:

• NS/EP feature activation and parameter provisioning during Handset Verification Acceptance testing (HVAT)

• NS/EP priority and quality of service recognition in the service provider network

• NS/EP message marking at all ingress and egress

• OM verification for NS/EP calls.

3.2.3.3. Review test plans and attend NSAT activities to ensure the NS/EP Priority Services software is provisioned and implemented correctly in a limited production environment and to verify potential correct operation within a service provider’s live network. Specifically, the NSAT verifies that:

• Priority capabilities are activated and provisioned according to the NS/EP service provider’s Method of Procedures (MOPs) and the Provisioning Requirements.

6 | P a g e

• When so provisioned, NS/EP calls are processed successfully in accordance with the applicable NS/EP Feature Vendor’s functional hardware and software requirements and

• Allow NS/EP calls to be identified and priority features triggered on an end-to-end basis with the quality of service specified in the KPPs. Service provider’s PS capabilities are interoperable with other PTS service providers networks

3.2.4. Subtask 3.4 – Technical Analysis White Papers: When tasked by the Government COR, research, evaluate, and analyze issues, questions and other information, and propose alternatives and recommended solutions. Identify and resolve systems-level issues through participation in, and possible hosting of, priority services meetings. Anticipate as many as four (4) issue papers per year on a variety of topics.

3.2.5. Subtask 3.5 – TIM Support: Provide support for Technical Interchange Meetings (TIMs) and Government ad hoc meetings addressing technical issues.

Meeting support may include preparation, participation, recording the results, and providing ECD with a summary of the meeting resulting action items, updates, and resolutions. Participation will be required in, among others, gatherings of service providers and IC subcontractors (e.g., Government Industry Requirement meetings, PTS Carrier meeting, GETS/WPS Team Forums, etc.), and in Team Forums. Work includes:

• Recommend technical issues for discussion

• Prepare agenda

• Identify issues and associated potential impacts, alternative solutions, and strategic recommendations to reduce risk

• Assist in developing presentation materials

• Coordinate with contractors and service providers for appropriate meeting times and places

• Participate in meetings

• Provide meeting minutes which include the issues discussed and the action items

3.2.6. Subtask 3.6 – Engineering Assessments

3.2.6.1. Review, research, evaluate, and analyze NGN-PS voice, video, and data technologies for priority services application and bring potential solutions to the attention of the Government. Participate in evaluating the prototyping of these technologies, attend meetings, provide comments, and participate in executing test scenarios, protocols, and networks.

3.2.6.2. Monitor evolving technology development and implementation efforts by service providers, provide assessments identifying impact to NGN-PS program and present issues requiring resolution to ECD.

3.2.6.3. Research, evaluate, and analyze issues, questions, and other information related to NGN-PS voice, video, and data, and attend technical meetings, provide and review contributions, and assist in the development and

7 | P a g e update of the NGN-PS Architecture if requested by the task lead. Conduct an Architecture Study focusing primarily on the video and data portions of the NGN- PS effort.

3.2.7. Subtask 3.7 – If requested by the task lead, contractor will attend industry meetings evaluate and summarize technical contributions that impact Priority Services. Contractor can conduct technical research but does not set policy nor establish priorities, as all decisions are made by government personnel.

5.3 Task 3 – Priority Services Governance Support: Provide Governance support to the ECD programs and document the support provided/progress made in the MSRs.

5.3.1 Subtask 3.1 – Program Documentation Repository: Maintain an electronically and a hard copy accessible compendium of program documentation for ECD programs including PTS, CASM and NGN PS Phase 1, Phase 2 and future phases. Receive, catalogue, and develop documents and abstracts, maintaining them to provide easy access/reference. Classified documents are to be kept in an approved classified storage container in a DSS cleared facility.

Documentation may include:

• Deliverables for Government contracts that relate to PTS, CASM, NGN-PS, Phase 1, Phase 2 and any future NGN-PS Phases.

• Past programmatic PTS, CASM and NGN-PS documents

• SOWs and Task Orders of PTS, CASM and NGN-PS Government contracts

• Other Miscellaneous PTS, CASM and NGN-PS documents

• Documents on telecommunications technology applicable to Priority Services

Program Office.

Physical storage requirements of the library:

• Secured room with access limited to library staff and faculty Security

POC

• 300 sq ft

• Minimum of 3400 linear feet of shelving; each shelf should be 12” deep and 12” tall

• Within the room an area to stack boxes of hard copies to be checked

Required configurations of server for electronic storage, search and retrieval:

• X64-based PC with dual 2.7 GHz processors

• 8 GB RAM

• Minimum 750 GB hard drive (no partitioning needed)

NOTE: Governance support may expose the Contractor to certain Government procurement-sensitive information; therefore, the Contractor’s proposal must include a mitigation strategy to show how the Governance work is organizationally separated from other parts of the Contractor organization, to protect procurement-sensitive information from disclosure outside the performing staff. Contractor staff may be required to sign non-disclosure agreements.

8 | P a g e

• Required software configuration o Microsoft Windows Server 2019 Datacenter o Office 2019, Adobe Reader, WinZip Pro o ZyLAB Information Management Platform, Version 6.7.

o Server must not have open internet access

5.3.1.1 Implement, upon Government approval, improvements to the search techniques, reports, and presentation of the data housed in the Repository.

Prepare and maintain electronic database indexes and document finding aids.

Provide the master database electronically, upon Government request.

5.3.1.2 Catalog and file contract deliverables and all other pertinent documents in a secured room, to protect the proprietary and procurement-sensitive nature of some of the data. Acquire and maintain, as a part of the Program Documentation Repository, proprietary agreement statements for both the prime contractor and their subcontractors.

5.3.1.3 Maintain a Document Review Log in the Repository to track deliverables, proposals, or other engineering assessment documents reviewed in Tasks 2 through 11.

5.3.1.4 Upon completion or termination of the contract, transition the entire Program Documentation Repository to the Government, ensuring that all activities under this subtask are in full compliance with the DHS Management Directive 0550.1 Records Management Directive and its associated DHS Records Management Handbook.

5.3.2 Subtask 3.2 – Documentation Assessment: Perform a semi-annual “Documentation Deep Dive” in which each program’s documents and artifacts are assessed for relevance, consistency, and up-to-date language. Inventory artifacts, assess whether they require updating, prioritize the updates base on available budget and reporting priorities, and report the results of the assessment to the Government.

Provide technical briefings/reports of recommendations, analyses, and justifications regarding the budgeting and allocations process. (Budgets and plans must evolve as new technologies are introduced in the PSN, broadband, next generation, and wireless networks.)

5.3.3 Subtask 3.3 – Program Governance Documentation: Ensure the ECD programs including, but not limited to the PTS, CASM and NGN-PS programs meet CPIC, Systems Engineering Life Cycle (SELC), and the DHS Acquisition Directive 102-01 requirements. Assist the Government in updating current documents or developing documents, such as, but not limited, to those listed below, as identified by the Government.

Mission Need Statement Acquisition Program Baselines Integrated Master Schedule Concept of Operations Operational Requirements Document

Analysis of Alternatives/Alternatives Analysis Cost Benefit Analysis Life Cycle Cost Estimates (LCCE) LCCE Annual Updates Resource Request Requirements

9 | P a g e

Systems Engineering Lifecycle (SELC) Tailoring Plan Integrated Logistics Support Plan Test and Evaluation Master Plan Functional Requirements Document Risk Management Plan Program Risk Registers SELC Reviews and Briefings

Resource Allocation Plan Resources Allocation Decision Expenditure Plan Operational Analyses INVEST reporting Inputs to OMB Business Case

5.3.3.1 Develop and maintain a “Fact Book” consisting of approved language, assumptions, statistics, financials, and other information as required to ensure consistency across documents and briefings. Document support provided and progress made in the MSRs.

5.3.3.2 Update the appropriate Program Plan to reflect changes in budgets, architectures, and requirements. Ensure that the plan supports any applicable OMB Business Case submissions, both annual and monthly. Essential OMB Exhibit items to be addressed in the plan include, but are not limited to:

• project description

• program justification/authorization

• funding and milestone schedule baselines, with noted variances

• risk assessment/management that addresses schedule

• initial and lifecycle costs

• technical obsolescence

• feasibility and service reliability

• interoperability and dependencies between investments

• surety (asset protection) considerations

• capability to manage the investmen

• overall risk of investment failure

• need for change management

• business process for investment management

• technology impacts

• security / privacy

• assessment of project resources

5.3.3.3 Strategic outlook provides support for documented responses to oversight entities such as the Office of Management and Budget (OMB) and Congressional staff, and provide assistance in submitting updates to the ECD Annual Report.

5.3.3.4 Provide as-needed support to plan, prepare, review, coach, and deliver briefings, testimony, or updates to CISA and DHS executives, acquisition review boards, and oversight entities such as the Inspector General, OMB, Government Accountability Office (GAO), and other entities. Artifacts may include PowerPoint presentations, read-ahead information, technical artifacts, or other documents.

10 | P a g e

5.4 Task 4 – PTS Engineering (Optional): Review, research, analyze, test, and evaluate priority services information, including White House requirements for voice, video, data, and information services. Provide technical support identifying and coordinating proprietary and non-proprietary technical and programmatic data, as well as any other issues associated with the PTS Contract, and its GETS local exchange carriers (LEC), WPS carriers, vendors, and operators, the Priority Telecommunications Service (PTS) carrier contracts (GETS long distance, GETS LEC, WPS carriers), Cable providers, Cloud providers, Fixed wireless providers, Satellite providers, and Wi-Fi access vendors and manufacturers. Document support provided and progress made in the MSRs.

5.4.1 Programmatic Support: Provide programmatic support through preparation for and participation in staff meetings, conference calls, and QPSRs.

5.4.2 Technical Support, Papers, and Reporting: While staying current with emerging telecommunications technologies by reviewing technical papers and industry announcements, meeting with leading carriers and vendors, and attending related seminars, conferences, or similar industry forums, provide the following:

• Participate in the process to plan, engineer, implement, test, and deploy new or enhanced functionality. include: WPS CDMA Enhanced Overload Performance; interoperability testing of satellite devices such as INMARSAT, Global Star, and Iridium, interoperability testing of fixed and secure mobile devices such as the DoD Mobility Classified Capability (DMCC) Secure Mobile phones, secure Iridium satellite phones, and other Voice-over Secure IP (VoSIP) devices. Analyze, assess, and support Priority Services interfaces and interoperability with other networks e.g.

Defense Switched Network (DSN), Diplomatic Telecommunications Service (DTS), and GSA’s Enterprise Infrastructure Solutions (EIS).

Analyze, assess, and support WPS interoperability with FirstNet to meet the objective of interoperability.

• Update the current DHS dialing instruction for secure devices handbook for using GETS/WPS.

• Support development and testing of the GETS/WPS Dialer App including on-going improvement capabilities such as the addition of an electronic GETS card distribution capability

• Review service provider technical documentation as well as participate in testing events. Tests include, but are not limited to, product assessment working sessions, test case scenario development, captive office testing, validation office testing, network service acceptance testing, , network service verification testing, and readiness testing.

• Review PTS provides trouble ticket analysis and recommendation support

• Develop various use cases to support standards activities.

• Gather technical and operational satellite information to: 1) Evaluate operational concepts and procedures for satellite communications use; 2) Evaluate the ability of the GETS and WPS services to interoperate with satellite services; 3) Evaluate the satellite service and refine user requirements for future satellite services; 4) Develop appropriate supporting documentation including lessons learned.

11 | P a g e

• When required, provide written reports summarizing comments and concerns.

• Review and contribute to the process established for the development and standardization of Industry Requirements documentation as related to future generation wireless and wireline technologies.

• Provide architecture and planning support, as well as meeting support including briefings, agendas, and meeting summaries.

• Review survivability or other studies that are produced as part of the PTS program. Ascertain that reasonable engineering concepts were applied in its production and summaries.

• GETS and WPS Security Classification Guide

• The Contractor shall develop a GETS and WPS Security Classification

Guide to incorporate any technical or administrative changes or modifications required. A review is required on an annual basis and an update is required every five years. The contractor will support the coordination both internal and external to include the White House and all of the participating service providers.

5.4.3 Technical Analysis White Papers: When tasked by the Government COR, research, evaluate, and analyze issues, questions and other information, and propose alternatives and recommended solutions. Identify and resolve systems-level issues through participation in, and possible hosting of, priority services meetings.

Anticipate as many as twenty (20) issue papers per year on a variety of topics;

examples include 8YY Toll Free Database Dip Analysis, GETS Performance Analysis, Priority E911 Services, and WPS Performance Analysis.

5.4.3.1 TIM Support: Provide support for Technical Interchange Meetings (TIMs) and Government ad hoc meetings addressing technical issues. Meeting support may include preparation, participation, recording the results, and providing the Government task lead with resulting action items, updates, and resolutions. Participation will be required in, among others, gatherings of service providers and PTS subcontractors (e.g., PTS carriers’ contract TIMs, GETS/WPS Team Forums, etc.), and in Team Forums. Work includes:

• Recommend technical issues for discussion

• Prepare agenda

• Identify issues and associated potential impacts, alternative solutions, and recommendations

• Assist in developing presentation materials

• Coordinate with contractors and service providers for appropriate meeting times and places

• Coordinate and participate in weekly ECD, PTS Contractors, and PTS carrier contractors Technical Coordination meetings

• Participate in meetings

• Provide a written summary

5.4.3.2 Technical Updates: Update the GETS/WPS

Engineering/Implementation Plan (EIP) to reflect information on GETS/WPS as

12 | P a g e implemented by the PTS carrier contracts, LECs, CLECs, and/or CMRS providers and Multiple System Operators (MSOs) based on their Service Engineering and Operations Plans, the results of acceptance testing, or information obtained at TIMs. When requested, update the Functional Requirements Specifications

(FRS).

5.4.4 Engineering Assessments - The contractor shall assist the ECD with requirements analysis including: analyzing updated White House NS/EP telecommunications requirements; updating PTS Functional Specification Requirements (FRS) to align to the revised White House requirements; and revising carrier NGN service requirements to respond to these updated requirements. The contractor shall review carrier service offerings to ensure that proposed services would comply with the Functional Requirements Specification (FRS), Key Performance Parameters (KPP), and modeled parameters; and is consistent with proposed and existing standards, technology, and anticipated vendor product offerings and performance. The contractor shall capture these analyses by submitting technical requirements documents. Prepare a technical requirements document based on the new White House operational requirements for voice, video, data, and information services. Assist with the Government’s Configuration Control Board

(CCB).

5.4.4.1 Review and analyze deliverables from the PTS contract, and PTS network service provider contracts (Subcontracts, LECs, CLECs, CMRS Providers, MSOs Wireless Providers, Switch Vendors, Wi-Fi technology vendors, Cloud application designers, Cloud infrastructure vendors, and Cloud transport providers), focusing comments on technical issues, up to approximately 90 document reviews per year. Recommend which deliverables warrant formal comments focused on technical issues and maintain a status log of all deliverables received.

5.4.5 SRAS Engineering - This task provides technical assistance for the Special Routing Arrangement Service (SRAS), to improve this service significantly through IP packet-based access networks and cloud services. The Contractor shall review, research, evaluate, and analyze SRAS information and provide technical support to identify and coordinate proprietary and non-proprietary technical and programmatic data, as well as any other issues associated with the PTS, support the survivability analysis and PTS carrier contracts. The contractor shall assess the impact of STIR SHAKEN alternatives on the IP segment, and ID authentication on backwards compatibility with TDM segments of the networks so that SRAS activities are not blocked by the terminating LEC or cable or fiber service provider. The Contractor shall document support provided and progress made in the MSRs.

5.4.5.1 Programmatic Support - The Contractor shall provide programmatic support to the Government SRAS task leader through preparation for and participation in staff meetings, conference calls and QPSRs.

5.4.5.2 Technology enhancement and readiness Testing - The Contractor shall participate in the process to plan engineer, implement, test, and deploy new or enhanced SRAS functionality. The Contractor shall review service provider

13 | P a g e technical documentation as well as participate in testing events that include SRAS functionality. The Contractor may be responsible for the review of SRAS Survivability Studies that are produced as part of the SRAS program. The Contractor shall ascertain that reasonable engineering concepts were applied in its production and summaries. And, when required, the Contractor shall provide written reports summarizing comments and concerns. The Contractor may also be tasked to produce an SRAS engineering report for the Government.

5.4.5.3 The contractor shall assist the Government in its review of vendor and carrier test plans and shall participate in testing events including service acceptance testing of priority service in PTS carrier contracts, LEC, CLEC, and MSO networks. Review and provide comments to the test plan, test cases, test reports and all other supporting test documents.

5.4.5.4 Review test plans and attend Captive Office Test (COT) or Product Test activities intended to stress test NS/EP Priority Services software to verify it is capable of meeting the Key Performance Parameters (KPPs) and the functional requirements specified in the vendor’s RVTM in a simulated all-hazards laboratory environment. Specifically, the COT verifies:

• NS/EP feature activation and parameter provisioning

• NS/EP priority and quality of service recognition in the service provider network

• NS/EP message marking at all ingress and egress

• OM verification for NS/EP calls.

5.4.5.5 Review test plans and attend Network Service Acceptance Test (NSAT) activities to ensure the NS/EP Priority Services software is provisioned and implemented correctly in a limited production environment and to verify potential correct operation within a service provider’s live network. Specifically, the NSAT verifies that:

• Are activated and provisioned according to the NS/EP service provider’s Method of Procedures (MOPs) and the Provisioning Requirements.

• When so provisioned, NS/EP calls are processed successfully in accordance with the applicable NS/EP Feature Vendor’s functional hardware and software requirements and

• Allow NS/EP calls to be identified and priority features triggered on an end-to-end basis with the quality of service specified in the KPPs.

5.4.5.6 Review test plans and attend End-to-End Network Service Verification Test (NSVT), which is very similar to NSVT, but is end-to-end testing with NS/EP service provider’s network. The end-to-end NSVT verifies that a service provider’s NS/EP features:

• Are activated and provisioned according to the NS/EP service provider’s Method of Procedures (MOPs) and the Provisioning Requirements, and

14 | P a g e hardware and software requirements.

• Allow NS/EP calls to be identified and priority features triggered on an end-to-end basis with the quality of service specified in the KPPs.

5.4.5.7 Deliverable/Documentation Reviews - The Contractor shall review deliverables and documentation from, but not limited to, the SRAS Service Providers and the IC as directed by the Government, and provide analytical comments. The contractor shall assist in preparation of SRAS concept of operations (CONOP) and update of SRAS activation/ deactivation procedures as require. The Government anticipated up to a maximum of twenty (10) document reviews per year. The Contractor shall recommend which deliverables warrant formal comments focused on technical issues. The contractor shall maintain a status log of all deliverables and documents received.

5.4.5.8 Technical Requirements Documentation - The Contractor shall provide SRAS technical support to the Government to organize, review and evaluate SRAS related issues associated with the IC and PTS contracts.

Engineering assessments of architectures, networks, and vendor capabilities shall include recommendations to ensure compliance with the FRD. The Contractor shall provide SRAS wi-fi and cloud architecture and planning support, as well as meeting support including briefings, agendas, and meeting summaries.

5.4.5.9 SRAS Security Classification Guide - The Contractor shall develop a SRAS Security Classification Guide to incorporate any technical or administrative changes or modifications required. A review is required on an annual basis and an update is required every five years. The contractor will support the coordination both internal and external to include the White House and all of the participating service providers. Priority Video, Data and Information Service KPPs and Functional Requirements: ECD has developed key performance parameters (KPPs) and Functional Requirements for priority voice telecommunications services. Relevant KPPs and functional requirements are required for priority video, data and information services. The contractor shall review previous work performed on this subject and identify gaps and shortfalls in that work. The contractor shall recommend corrective action. As part of the corrective action, the contractor shall recommend specific values and the justification for those values.

5.5 NGN-PS Wi-Fi - Cloud Engineering (Optional): The contractor will assist the Government by providing wi-fi and cloud engineering support during analysis of cost-effective designs proposed by network and cloud service providers, and the correct testing methodology for priority services capabilities in all Next Generation Networks Priority Services (NGN-PS) program phases and increments. The contractor shall assist the Government in its review of vendor and cloud service provider technical documentation and testing plans for verification and validation of priority services capabilities. NGN-PS acquisition is planned in multiple phases and increments. Phase 2 is an approved program of record, with additional future phases planned.

15 | P a g e

• Phase 2: Wireless Data, Video and Information Services (3 carriers, 1 cable, Cyber proof of concept, Network Diversity proof of concept, 5G Voice proof of concept, Cloud proof of concept, Identity Credentialing and Access Management proof of concept, Satellite proof of concept)

• Phase 3: Wireless Data, Video and Information Services (3 cable, 1 new carrier, Cyber Assurance, Operational Assurance, Cloud pilot, Identity Credentialing and Access Management pilot, Wi-Fi proof of concept, Fixed Wireless proof of concept, Cable 10G proof of concept)

• Phase 4: Wireless Data, Video and Information Services (2 Cloud provider, private network, 6G proof of concept VVD&IS, Artificial Intelligence proof of concept, Machine Learning proof of concept, Quantum computing NexGen GWIDS proof of concept)

5.5.1 The contractor shall ensure that carrier service provider development is consistent with the Next Generation Networks Priority Services Functional Requirements Documents (FRD) and follow the NGN-PS Tailored Systems Engineering Life Cycle (SELC) review process. The SELC process includes at a minimum, monthly technical status reviews, a Preliminary Design Review (PDR), a Critical Design Review (CDR), Test Readiness Reviews (TRR) before each developmental Captive Office Test (COT) or Network Services Acceptance Test (NSAT), and a Production Readiness Review (PRR). Contractor will evaluate wi-fi vendors/manufactures and cloud service provider documentation such as product design, prototyping plan, supply chain and manufacturing controls, firmware-readable version register review, hierarchical design, Network Services Architecture (NSA) design document; Requirements Traceability and Verification Matrix (RVTM);

Functional and Performance Test Plan and Report; Requirements gap analysis report;

Risk mitigation plan/strategy; Cybersecurity threat analysis and mitigations report;

OAM&P AND NSVT plans, and Future Services Plan. Contractor will provide planning, analyses and requirements documentation for FRD, Key Performance Parameters (KPPs), RVTM, etc. for voice, data and video NS/EP priority services.

5.5.2 Programmatic Support: Provide programmatic support through preparation for and participation in staff meetings, conference calls, and QPSRs, and updating the appropriate program documents to reflect changes in budgets, schedule, architectures, and requirements. It also includes providing summary minutes and agreed upon action items of all meeting with the service providers.

5.5.3 Technical Support: The contractor shall provide technical support activities that include, but are not limited to:

5.5.3.1 Participate in the initial and continuing evaluation effort and in the resulting process to engineer, implement, test, and deploy NGN-PS voice, video, and data solutions.

5.5.3.2 Review and evaluate designs and development efforts from PTS service provider contracts to recommend the best approach on the adequacy of

16 | P a g e these designs and development efforts to comply with the FRD, and to meet key performance parameters.

5.5.3.3 Work with wi-fi vendors/manufactures and cloud service providers to identify standardized methodologies for NS/EP priority services that focuses on priority and quality of service (QoS) mechanisms. Priority mechanisms will include, but not be limited to: invocation of Access Class Barring (ACB), High Priority (HPA), Enhanced Access Barring (EAB), Allocation and Retention Priority (ARP), LTE paging priority, and Quality Class Identifier (QCI), exemption from overload control, use of differentiated services code point (DSCP) and measurement of quality or performance. The SETA shall assess the efficacy of these features in providing priority service and monitor feature compliance testing. The SETA will recommend and review service provider recommendations for adding additional features such as standardized Enhanced Multi-Media Priority Services (eMPS), data, video and information services priority mechanisms.

5.5.3.4 The SETA shall assess service provider compliance by monitoring the service provider’s implementation of the NGN-PS Tailored SELC process, unless ECD approves a service provider’s request for substitution of commercial best practices. Specifically, the SETA will monitor service provider design and development at the different SELC milestone phases and notify ECD of any variance in schedule or performance using an integrated master schedule (IMS) and RTVM. The service provider will conduct a series of SELC reviews for each phase of this project that details what priority capabilities they will provide, how they will fulfill the requirements and they will be verified, and when the service is ready for operation. Contractor will document increasing detail of how the FRD requirements will be met in a RTVM and IMS after each successive service provider SELC review and provide a quarterly presentation to ECD of vendors/manufactures and cloud service provider variance in schedule and performance.

5.5.3.5 The FRD addresses what requirements need to be addressed by the service provider, while the PDR and the CDR provide the design details of how the capabilities will address the requirements. The later stage reviews focus on assessment of service readiness and the mechanisms to continuously verify that the service is operating within its expected parameters by the use of testing and operational measurements. The later stages are supported by the developmental TRRs, one or more functional and performance COTs and NSAT, and the Production Readiness Review. At the end of each service provider’s SELC review and associated document acceptance by ECD, contractor will create CISA SELC process briefings and/or assessment reports for reviews.

5.5.3.6 Update the NGN-PS Wi-Fi and Cloud Engineering/Implementation Plan (EIP) to reflect information on NGN-PS as implemented by the PTS service provider, LECs, CLECs, and/or CMRS providers and Multiple System Operators (MSOs) based on their Service Engineering and Operations Plans, the results of acceptance testing, or information obtained at TIMs. When requested or needed, revise the FRD.

17 | P a g e

5.5.4 Subtask 5.4 – Ensure testing that is consistent with the NGN-PS Test and Evaluation Master Plan (TEMP) and work with the Operational Test Agent (OTA) to ensure that the relevant tests are being run and data are being collected as needed by the OTA

5.5.4.1 The contractor shall assist the Government in its review of vendor and service provider test plans and shall participate in testing events including service acceptance testing of priority service in PTS service provider contracts, LEC, CLEC, and MSO networks. Review and provide comments to the test plan, test cases, test reports and all other supporting test documents.

5.5.4.2 Review test plans and attend COTs or other Product Test activities intended to stress test NS/EP Priority Services software to verify it is capable of meeting the KPPs and the functional requirements specified in the vendor’s RVTM in a simulated all-hazards laboratory environment. Specifically, the COT verifies:

• NS/EP feature activation and parameter provisioning during Handset Verification Acceptance testing (HVAT)

• NS/EP priority and quality of service recognition in the service provider network

• NS/EP message marking at all ingress and egress

• OM verification for NS/EP calls.

5.5.4.3 Review test plans and attend NSAT activities to ensure the NS/EP Priority Services software is provisioned and implemented correctly in a limited production environment and to verify potential correct operation within a service provider’s live network. Specifically, the NSAT verifies that

• Priority capabilities are activated and provisioned according to the NS/EP service provider’s Method of Procedures (MOPs) and the Provisioning Requirements.

• When so provisioned, NS/EP calls are processed successfully in accordance with the applicable NS/EP Feature Vendor’s functional hardware and software requirements and

• Allow NS/EP calls to be identified and priority features triggered on an end-to-end basis with the quality of service specified in the KPPs. Service provider’s PS capabilities are interoperable with other PTS service providers networks

5.5.5 Subtask 5.5 – Technical Analysis White Papers: When tasked by the Government COR, research, evaluate, and analyze issues, questions and other information, and propose alternatives and recommended solutions. Identify and resolve systems-level issues through participation in, and possible hosting of, priority services meetings. Anticipate as many as four (4) issue papers per year on a variety of topics.

18 | P a g e

5.5.6 Subtask 5.6 – TIM Support: Provide support for Technical Interchange Meetings (TIMs) and Government ad hoc meetings addressing technical issues.

Meeting support may include preparation, participation, recording the results, and providing ECD with a summary of the meeting resulting action items, updates, and resolutions. Participation will be required in, among others, gatherings of vendors/manufactures and cloud service providers and IC subcontractors (e.g., Government Industry Requirement meetings, PTS Partner meeting, GETS/WPS Team Forums, etc.), and in Team Forums. Work includes:

• Recommend technical issues for discussion

• Prepare agenda

• Identify issues and associated potential impacts, alternative solutions, and strategic recommendations to reduce risk

• Assist in developing presentation materials

• Coordinate with contractors and service providers for appropriate meeting times and places

• Participate in meetings

• Provide meeting minutes which include the issues discussed and the action items

5.5.7 Subtask 5.7 – Engineering Assessments

5.5.7.1 The Review, research, evaluate, and analyze NGN-PS voice, video, and data technologies for priority services application and bring potential solutions to the attention of the Government. Participate in evaluating the prototyping of these technologies, attend meetings, provide comments, and participate in executing test scenarios, protocols, and networks.

5.5.7.2 Monitor evolving technology development and implementation efforts by service providers, provide assessments identifying impact to NGN-PS program and present issues requiring resolution to ECD

5.5.7.3 Research, evaluate, and analyze issues, questions, and other information related to NGN-PS voice, video, and data, and attend technical meetings, provide and review contributions, and assist in the development and update of the NGN-PS Architecture if requested by the task lead. Conduct an Architecture Study focusing primarily on the video and data portions of the NGN- PS effort.

5.5.8 Subtask 5.8 – If requested by the task lead, contractor will attend industry meetings evaluate and summarize technical contributions that impact Priority

5.6 NGN-PS Cybersecurity Engineering (Optional): The contractor will assist the Government by providing cybersecurity engineering support during analysis of cost effective designs proposed by network and cloud service providers, and the correct cybersecurity testing methodology for priority services capabilities in all Next Generation Networks Priority Services (NGN-PS) program phases and increments. The contractor

19 | P a…