70RNPP19R00000004_Section_B-M_AMD0001.pdf

70RNPP19R00000004

SECTION B – SUPPLIES OR SERVICE/PRICES

1.0 CONTRACT TYPE

This is a hybrid type contract with Cost-Plus-Award-Fee (CPAF), Firm-Fixed-Price (FFP), and Cost

Reimbursement (CR) contract line items (CLINs)

< LABOR RATES TO BE INCLUDED AT TIME OF AWARD>

2.0 TRAVEL COSTS

All travel will be reimbursed at cost in accordance with the Federal Travel Regulations (FTR). The

Contractor shall seek written Government approval (Contracting Officer (CO) or COR) at least two weeks in advance, prior to incurring any costs associated with non-local travel.

Local travel will not be reimbursed within a 50 mile radius of the worksite. As the Contractor may locate personnel outside the Washington D.C. metropolitan area, for purposes of local travel only, the worksite shall be considered the Washington D.C. metropolitan area, or the location of contractor’s personnel, whichever is within the 50 mile radius.

The Contractor shall use the federal lodging and per diem allowances in accordance with FAR 31.205-46 and the applicable FTR governing the travel performed directly referable to this contract. The

Government will not reimburse transportation costs in excess of coach class commercially scheduled air or ground transportation by the most expeditious route.

Travel reimbursement request must be submitted (in writing) in sufficient time for the Contracting

Officer or Contracting Officer Representative to give prior approval, and must identify (i) the name of the traveler, (ii) destination (s) including itinerary, (iii) purpose of the travel, and (iv) cost breakdown.

To be reimbursed, invoices, including travel expenses must include a detailed breakdown of the actual expenditures invoiced.

3.0 MATERIALS/OTHER DIRECT COSTS (ODCs)

The Contractor shall procure material/ODCs when essential to task performance and approved by the

Program Manager and the Contracting Officer. ODCs must be approved by the CO prior to incurring any costs. ODCs must be approved by the CO, and must be necessary, allowable, and allocable for performance of this contract. ODCs must be submitted in sufficient time to the CO to give prior approval, and must identify the purpose of the ODCS and provide a detailed cost breakdown. The

Contractor shall maintain the original or legible copy of receipts for all ODCs invoiced. The Contractor shall be reimbursed on an actual cost basis.

All materials purchased by the Contractor for the use or on behalf of the Federal Government shall become the property of the Federal Government. The Contractor shall document the transfer of materials in addition to an account of all materials consumed during the performance of the contract.

The Contractor shall furnish a copy of such documents at Quarterly Program Management Review

Meetings.

(End of Section B)

SECTION C – DESCRIPTION/SPECIFICATIONS

CYBERSECURITY AND INFRASTRUCTURE SECURITY AGENCY (CISA)

EMERGENCY COMMUNICATIONS DIVISION (ECD)

PRIORITY TELECOMMUNICATIONS SERVICES (PTS)

PERFORMANCE WORK STATEMENT (PWS)

1.0 PURPOSE

The purpose of this Performance Work Statement (PWS) is to specify the work outcomes required of the

Contractor to provide and support communications services at a level that assures a high probability of their availability and performance to meet the needs of authorized National Security and Emergency

Preparedness (NS/EP) users under all levels of stress. The Contractor shall provide task/program management, engineering, service agreements acquisition, and operations, administration, maintenance, and provisioning (OAM&P) support for Priority Services (PS). PS consists of legacy

Government Emergency Telecommunications Service (GETS), Special Routing Arrangement Service

(SRAS), Wireless Priority Service (WPS), and Next Generation Network (NGN) Priority Service (PS). In addition to the services described above, under optional CLINs, when exercised by the Government, the

Contractor shall support the planning, implementation and testing of bridging and NGN PS technology refreshment-type changes that will contribute to the continuing viability and effectiveness of the PS as it transitions to NGN. The Contractor shall furnish all personnel, materials, services, and facilities necessary to perform the requirements set forth in this PWS.

2.0 SCOPE

This PWS specifies the outcomes required of the Contractor, to provide carrier service agreements, requisite OAM&P and engineering support for PS and other related priority services. Engineering is required for sustainment and technology refreshment of the specified services to ensure the service capabilities do not degrade, as Public Switched Network (PSN) technology upgrades occur, and that the services continue to be effective under all levels of stress.

3.0 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 telecommunications infrastructure, the 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. PS, by cost-effectively leveraging the PSN, 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.

4.0 PERIOD OF PERFORMANCE

See Section F – Item 1.0.

5.0 PERFORMANCE OBJECTIVES, GOALS, AND OUTCOMES

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 OEC requires contractor engineering, acquisition, program management, integration, coordination, and OAM&P support.

The purpose of this PWS is to specify the performance requirements for the Contractor to provide communications services and service support at a level that assures a high probability of their availability to meet the needs of authorized NS/EP communications users under all levels of stress. The Contractor shall provide engineering and planning; implementation, integration, and coordination;

communications services and operations, administration, maintenance, and provisioning support as required for existing PS voice services as well as future services support that will ensure NS/EP communications requirements are met through current and next generation communications networks.

This PWS requires the Contractor to arrange for provisioning selected voice capabilities, as well as future services, within carrier networks and to maintain these services through OAM&P activities specified herein, and to engineer, implement, test and maintain NS/EP priority communications services within converging and next generation communications networks.

In acquiring priority service, the Contractor shall be restricted to US owned carriers, service providers, and vendors; unless specifically authorized by the Government to deal with non US owned companies.

In recognition that the vast majority of telecom vendors are foreign owned, OEC will streamline its approval process. The Contractor shall be prohibited from contracting for Priority Service with service providers utilizing Chinese manufactured telecommunications equipment for handling NS/EP traffic, unless specifically authorized by the government.

The Contractor shall provide the following support:

(a) Provide and maintain specified wireline and wireless voice service within the carrier subcontractor networks in accordance with NS/EP Priority Services Functional Requirements Specification (FRS) and the Special Routing Arrangement Service (SRAS) FRS, as modified by the respective Requirements Traceability and Verification Matrices (RTVMs) and this PWS.

(b) Provide service evolution planning for the continued enhancement and evolution of NS/EP priority services in conjunction with the evolution of the communications service providers under subcontract.

(c) Provide additional service implementation and OAM&P within the carriers’ (specified in section 5.2.) evolving networks and those carriers’ interfaces to the networks of other providers of NS/EP Priority Services in order to maintain and enhance NS/EP communications.

(d) Investigate and provide recommendations for other IP based priority data services.

The Contractor shall provide these services with minimal adverse impact upon public communication network facilities, commercial traffic, and Government networks, while minimizing cost and risk to the Government.

The Contractor is encouraged to provide solutions that minimize the number of mechanisms used to achieve a higher probability of call/session establishment from the User Equipment (UE) to the network, and the network to the UE (i.e., end-to-end communications) during times of network stress

(coordination with AT&T, Sprint and Verizon will be required). The Contractor is highly encouraged to reuse technology in order to contribute to minimal service-specific development and subsequent monetary cost. Lastly, in acquiring carrier services, the Contractor shall work to ensure that the investment is protected from service provider upgrades. OEC recognizes that service provider migration to new platforms such as 5G could require added NS/EP investments; however, acquired NS/EP services shall be protected from upgrades/changes to existing platforms. Service providers, when replacing PS enabled network equipment on existing platforms shall be required to enable the new products with equivalent PS features and functions at no additional cost to the Government.

5.1. Contract/Program Management

Contract/Program Management Objective:

The Contractor shall manage the contract through the use of the following:

Project plan

Quality Assurance Surveillance Plan (QASP)

Status meetings with the government

Status reports to the government

In maintaining nationwide PS coverage and follow-on services, the Contractor shall provide the following support:

Program and engineering management to ensure that schedule, cost, and performance goals are met

Planning and coordination to manage PS agreements with service providers

Establishing processes for quality assurance to include producing the Quality Assurance Surveillance Plan (QASP), and for progress and cost reporting

Serving on the Service Provider Council, along with T-Mobile, to ensure PS follow-on services are interoperable and to resolve issues that may arise

Adhering to DHS Certification & Accreditation (C&A) requirements and providing requisite documentation regarding database or other collection of DHS data in order to obtain and maintain full Authority to Operate

5.2. GETS, SRAS, and WPS Services

5.2.1. GETS Service Objective

The Contractor shall sustain GETS and where required SRAS by renewing the requisite service subcontracts to maintain GETS/SRAS priority features and functions within local exchange carriers’ (LEC) networks. In order to sustain GETS/SRAS, the Contractor shall establish LEC arrangements to maintain GETS priority features and functions within carrier networks during the base year period, and be prepared to retain the arrangements for all option years.

GETS carrier subcontracts shall include the following:

GETS features shall be provided on all switches for which the features are available in the software release deployed on the switch

GETS features shall be configured and maintained in accordance with Contractor provisioning guidelines

Where Advanced Intelligence Network (AIN) infrastructure is available and Alternate Carrier Routing

(ACR) has previously been provided, ACR shall continue to be provided for GETS calls

GETS Operational Measurement data shall be provided to the Contractor daily from switches with GETS features

If delivered under the previous carrier service subcontract, call record data shall be continue to be provided to the Contractor monthly for all GETS calls

The Contractor shall establish service agreements expeditiously to ensure no lapse in service.

The Contractor shall present the results of these subcontract negotiations to the OEC in a briefing. Subject to OEC approval, the Contractor shall enter into subcontracts with the LECs for GETS.

After establishing service subcontracts, if all or any portion of the LEC networks specified in section 5.2.1.1 is acquired by another company, the Contractor shall pursue continuation of GETS service with the acquiring company under section 5.6. Technology Refreshment.

5.2.1.1. GETS Carrier Agreements

The Contractor shall subcontract with the LECs shown in Table 1 below. For any Tier I, II, or III LEC required, as shown in Table 1, for which a service arrangement is not in place at the time of contract award, the Contractor shall establish a service arrangement, consistent with arrangements with the other carriers, as a task under section 5.6. Technology Refreshment.

The Contractor shall structure the GETS required LEC agreements as basic work and optional tasking, to reflect the government’s objective/desire to pursue alternative direct contracts to acquire specific GETS

LEC services. The optional tasks are unilateral options solely at the government’s discretion.

Table 1

TIER 1 TIER 2 TIER 3

CenturyLink (including legacy carrier: tw Telecom)

Cincinnati Bell Ben Lomand

Frontier East Ascension

Hawaiian Telecom GTA Teleguam

Claro Matanuska

TDS Micronesia

Neutral Tandem

Windstream Pioneer Telephone

Shentel

Consolidated

Communications,Mattoon, IL

Peerless Network

5.2.1.2. Carrier Agreement Requirements

The Contractor may include the following OAM&P-type requirements for GETS in their carrier agreements.

• Provisioning Requirements: Specifies the provisioning of the GETS features, to include parameter settings and routing

• OA&M Reporting Requirements: Specifies the GETS operational data that the carrier shall deliver to the Contractor

• GETS Billing Data Reporting Requirements: Specifies carrier reporting to the Contractor of GETS completed and billable calls

• GETS Call Detail Records Reporting Requirements: Specifies carrier reporting to the Contractor of all GETS call attempts

• Annual Carrier Reviews: Specifies the requirements for the carrier to conduct an Annual Program Review including Network Evolution and Roadmap planning for the Contractor and the Government (virtual meetings preferred)

• Configuration Report Requirements: Specifies the GETS provisionable parameters that the carrier must audit and verify are provisioned according to the Provisioning Requirements

• Generic Network Service Verification Test (NSVT) Test Plans and Reports: Specifies the service verification testing and reporting that the carrier shall perform in coordination with the Contractor to ensure GETS functionality in an operational network

• Other Network Data: As specified, other data decided by OEC in the Service Provider Council (SPC) as relevant to determine NGN service performance, including handset data.

5.2.2. WPS Service Objective

The Contractor shall sustain WPS by providing the requisite contracting support to maintain WPS priority features and functions within wireless carrier networks. In order to sustain WPS, the Contractor shall make arrangements with wireless carriers to maintain WPS priority features and functions within their networks.

WPS carrier subcontracts shall include the following:

WPS features shall be provided on all mobile switching centers (MSCs) and radio access networks (RANs) for which the features are available in the software release deployed on the MSCs and RANs.

WPS features shall be configured and maintained in accordance with provisioning guidelines specified by the Contractor

WPS operational measurement data shall be provided to the Contractor daily from all network components that generate WPS-specific OMs

Call record data shall be provided to the Contractor monthly for all WPS calls

The Contractor shall negotiate with the carriers to extend the existing carrier subcontracts as the basis for establishing the new contracts.

After establishing service subcontracts, if all or any portion of the carrier networks is acquired by another company, the Contractor shall pursue continuation of WPS with the acquiring company under section

5.6.Technology Refreshment.

5.2.2.1. WPS Carrier Agreements

WPS required carrier agreements are as follows:

T-Mobile

US Cellular

General Communications Inc. (GCI)

Cellcom

C-Spire

Cellular One

5.2.2.2. Carrier Agreement Requirements

The Contractor shall continue the following OAM&P-type requirements for WPS in their carrier agreements by extending the pre-existing subcontracts which include these requirements. Contractor labor to support these requirements shall be included under section 5.4.

• Provisioning Requirements: Specifies the provisioning of the WPS features, to include parameter settings and routing

• OA&M Reporting Requirements: Specifies the WPS operational data that the carrier shall deliver to the Contractor

• Configuration Report Requirements: Specifies the WPS provisionable parameters that the carrier must audit and verify are provisioned according to the Provisioning Requirements

• Generic NSVT Test Plans and Reports: Specifies the service verification testing and reporting that the carrier shall perform in coordination with the Contractor to ensure WPS functionality in an operational network

• WPS Billing Data Reporting Requirements: Specifies carrier reporting to the Contractor of WPS completed and billable calls

• WPS Call Detail Records Reporting Requirements: Specifies carrier reporting to the Contractor of all WPS call attempts

• Other Network Data: As specified, other data decided by OEC in the SPC as relevant to determine 4G and 5G service performance

• Annual Carrier Reviews: Specifies the requirements for the carrier to conduct an Annual Program Review including Network Evolution and Roadmap planning for the Contractor and the Government (virtual meetings preferred).

5.3. Engineering Support

5.3.1. Sustainment Engineering

The Contractor shall provide engineering to extend the service viability for GETS and WPS carriers, while ensuring that these services support user requirements in a manner that protects NS/EP equities. The Contractor shall seek to reduce program costs by engineering solutions and negotiating carrier agreements that extend the lifespan of existing priority services. Contractor shall coordinate sustainment engineering, as appropriate, with AT&T, Sprint, and Verizon through the OEC and the SPC.

The Contractor shall include in Carrier Annual Program Reviews a section on future services planning that addresses carrier plans for network and service evolution as they impact sustaining GETS and WPS.

The Contractor shall submit to the Government a monthly White Paper and a briefing that addresses sustainment engineering topics. The Contractor shall coordinate White Paper and briefing topics with the Program Manager.

5.3.1.1 Sustainment Engineering for Interoperability

The Contractor shall provide engineering to maintain GETS interoperability and to maintain WPS interoperability. Contractor’s engineering shall maintain interoperability of PS features across the PS feature set and across multiple carriers. The Contractor shall perform actions to remediate interoperability issues that do not incur implementation costs to the OEC. In those instances in which the Contractor recommends remedial actions that may incur costs, the Contractor shall provide the OEC with a decision brief to initiate a Technology Refreshment contract modification.

5.3.1.2 Sustainment Engineering for Performance

The Contractor shall provide engineering to ensure that GETS performance and WPS performance meets the stated objectives. The performance objectives are:

GETS: Enhanced call completion rates for NS/EP users that are greater than what the general public experiences during disaster or crisis with the objective of 90% call completion at eight times busiest hour traffic profile in their network

WPS: Enhanced call completion rates for NS/EP users that are greater than what the general public experiences during disaster or crisis with the objective of 80% call completion at a minimum of twenty times busiest hour traffic profile in their network Contractor’s performance engineering shall support the Operational Support testing and end-to-end performance metrics (section 5.4.).

5.3.1.3 Monitoring GETS, SRAS, and WPS Viability

The Contractor shall work with all service providers under contract to monitor viability of PS. The Contractor will provide regular reports on carrier plans to transition to IP. Reports should include time schedules for migrating to IP, decommissioning circuits and networks, reduction in existing technology coverage or availability, and any carrier plans that will lead to PS performance degradation.

5.3.1.4 Sustainment Engineering for Viability Extension

The Contractor shall provide GETS and WPS engineering to extend the service viability by analyzing carrier network evolution and technology changes to identify potential impacts to GETS and WPS and to engineer a cost-effective solution, if required. The Contractor shall analyze potential and actual carrier network evolution and technology changes. This shall include Contractor investigation, as appropriate, of hybrid networks and technologies. The Contractor shall identify potential impacts of the technological changes on GETS and WPS viability, and the Contractor will continually monitor carrier networks status.

As appropriate the Contractor shall evaluate candidate actions to address the impacts and present recommendations to the government.

5.3.2. Service Providers Council (SPC)

SPC Meeting Support: OEC established a Service Providers Council (SPC) under the PTS carrier contracts for the purpose of ensuring Next Generation Network (NGN) Priority Service (PS) priority telecommunications solutions being developed and deployed are interoperable. The SPC consists of AT&T, Verizon, Sprint, the Integration Contractor, T-Mobile, and OEC. OEC requires support for the SPC consisting of engineering assessments and standards support to promote interoperability for NGN priority service feature enhancements. The Contractor, in their role as the IC, shall represent all its service providers under contracts at the SPC. In addition to telecommunications engineering and interoperability standards expertise, the Contractor shall participate in SPC Working Groups (WG).

Anticipated WG groups will include, but not be limited to the following: Network to Network Interface (NNI), WPS on VoLTE Performance, future WPS on 5G, GETS on VoIP Performance, NGN Standards, and NGN GETS Wireline Interoperability. Additionally, the Contractor shall support NGN special topics, such as: Authentication, peering and roaming, Apps, user priority levels, handset metrics, use cases, traffic mix, congestion scenarios, Network Function Virtualization (NFV), Software-Defined Networks (SDN), impact of Internet of Things (IoT), vendor equipment settings, TDM and hybrid network performance and schedule for sunsetting, NGN PS Phase 2 for video and data priority, and security. Further engineering expertise is required to research and advise OEC participants of potential issues and to recommend solutions that are standards based such as review, research, and analyze priority services information to provide technical assessments and recommendations for NGN PS enhancements. This support includes identifying and coordinating proprietary and non-proprietary technical and programmatic data from AT&T, Verizon, Sprint, IC (including its subcontractors), T-Mobile, and associated vendors.

5.3.3. Future Services Engineering

The Contractor shall provide engineering to plan for NGN PS for GETS carriers referenced in Paragraph

5.2.1.1 and WPS carriers referenced in Paragraph 5.2.2.1. Contractor shall coordinate sustainment engineering, as appropriate, with AT&T, Sprint, and Verizon through the OEC and the Service Provider

Council. The Contractor shall support NS/EP telecommunications requirements by planning for the transition of Legacy PS to NGN PS without experiencing a gap in support and an associated NS/EP telecommunications shortfall. The Contractor shall also support engineering follow-on NGN PS by identifying candidate initiatives that leverage the commercial carrier NGN investments to achieve cost-effective NGN PS solutions.

Contractor’s Future Services Engineering shall, include, but not be limited to, the following:

NGN GETS engineering to analyze carrier network evolution and technology changes to plan follow-on GETS on IP-based networks and, if required, to model planned NGN GETS performance to ensure planned investments will meet the stated objectives.

NGN MPS (Multi-Media Priority Service) engineering to analyze carrier network evolution and technology changes to plan follow-on NGN WPS (presumed to be 4G LTE and 5G) and, if required, to model planned NGN WPS performance to ensure planned investments will meet the stated objectives.

Support the Government in developing standards contributions and implementing these standards-based features on GETS and WPS carriers that are on the contract to the Contractor to ensure NGN PS interoperability i.e., network-to-network interface (NNI) to support PS interoperability objectives. The Contractor shall perform actions to implement these features that do not incur implementation costs to the OEC. In those instances in which the Contractor recommends that such implementation that may incur costs, the Contractor shall provide the OEC with a decision brief to initiate a Technology Refreshment contract modification.

Contribute to NGN PS interfaces and interoperability with FirstNet to meet the objective of interoperability.

Contribute to NGN PS interfaces to interoperate with other government networks.

Support optimum PS coverage to meet the objective of affordability that reduces overlap while considering SRAS locations.

Develop an annual Future Services Plan (FSP) that identifies potential NS/EP priority services investments. For each potential NS/EP investment, the FSP shall include the following:

o Develops business cases that assesses industry trends and technological advancements, provides an estimated return on investment, identifies the potential for leveraging carrier commercial investments with a leverage factor that estimates the cost savings, judges the lifespan of the potential investment, protects the investment from service provider upgrades, investigates affordable bridging alternative solutions, identifies alternatives to accelerate service to market (Ex.

limited operating capability), and utilize a strategy that minimizes risk of chasing technology.

o Support the government in implementing IP NNIs that will pass NS/EP markers

The Contractor shall include in Carrier Annual Program Reviews a section on future services planning that addresses carrier plans for network and service evolution as they impact evolution to NGN PS.

5.4. Operational Support

The Contractor shall support GETS, SRAS, and WPS performance to meet the stated Program objectives for intra/interagency emergency communications, international interface, interoperability, nationwide coverage, survivability/endurability, and voice-band service. The Contractor shall develop cost-effective methodologies to assess:

GETS/SRAS and WPS performance to ensure services are operating effectively

Coverage areas and capacity within those coverage areas are being maintained through network evolution

User assistance is being provided and user needs are met

Effective carrier coordination of operations is being achieved through the network operations center

Timely detection and correction of service problems is being achieved.

The Contractor shall serve as the central POC for all PS operational measurements and usage data.

The Contractor will develop an Operational Plan that documents needed carrier data to assess PS performance, including during crisis and emergencies.

5.4.1. Legacy GETS and WPS Operational Data

The Contractor shall collect, process and archive all legacy GETS and WPS operational measurements and usage data. The Contractor shall develop, operate and maintain applications for data collection and processing and databases for archiving the data. Supported by the Government through the Government’s direct contracts with AT&T, Sprint, and Verizon, the Contractor shall reach agreements with AT&T, Sprint, and Verizon for collecting Legacy GETS and WPS operational measurements (OMs) and usage data, and working collaboratively to analyze OMs and usage data, and to identify, track, and resolve service problems. If reaching agreements with ATT, Sprint, or Verizon directly entails costs from any of these carriers, the Contractor shall submit a proposal under Technology Refreshment to the Government that includes these costs.

For legacy GETS call data, the government will arrange for Verizon, AT&T and Sprint to provide GETS call detail records to the Contractor as GFI. The Contractor shall coordinate and compile the GETS call data records and prepare the consolidated data records for government use. The Contractor shall sort call data records by the organizational entities in the PIN/Subscriber database.

5.4.2. NGN PS - NGN GETS (GETS VoIP) and NGN WPS (WPS on VoLTE) Operational Data

The Contractor shall coordinate with the Government to develop a plan to collect, process and archive all NGN PS operational measurements, configuration verification and usage data. The plan shall include, supported by the Government through the Government’s direct contracts with AT&T, Sprint, and Verizon, the Contractor reaching agreements with AT&T, Sprint, and Verizon for collecting NG PS operational measurements (OMs) and data, and working collaboratively to analyze OMs and data, and to perform configuration verification. When tasked by the Government, the Contractor shall submit a proposal under Technology Refreshment for executing the plan.

In a separate effort, the Contractor will utilize carrier data to identify, track, and resolve service problems. When tasked by the Government, the Contractor shall submit a proposal under Technology Refreshment for executing the plan.

If the Contractor cannot make arrangements with Verizon, AT&T and Sprint, then the Government shall make arrangements with AT&T, Sprint and Verizon to supply operational data required for the plan. For NGN PS GETS call data, the Government will, if required, arrange for Verizon, AT&T and Sprint to provide GETS call detail records to the Contractor as GFI. The Contractor shall coordinate and compile the GETS call data records and prepare the consolidated data records for government use. The Contractor shall sort call data records by the organizational entities in the PIN/Subscriber database.

The Contractor shall also assess establishing a PS dashboard to monitor service performance from a variety of network feeds. The Contractor shall submit under Optional Technology Refreshment a proposal to implement the dashboard.

5.4.3. GETS Readiness

The Contractor shall seek to maintain user subscription and authentication processes for service readiness at a 100% error free level. To achieve this objective, the Contractor, exclusively, shall perform the following:

Create and Manufacture a Secure PIN: The Contractor shall ensure that each PIN created has a unique

12-digit number.

Distribute PINs to Users: The Contractor shall distribute PINs to users via the POCs to facilitate POC control of the PINs; POCs have the responsibility to distribute the PINs to their users.

Objective for routine processing - Receive, approve, provision in GETS IXCs, and mail GETS card to

POCs for routine requests for activation of GETS subscriptions is >90% of routine requests completed within 72 business

Objective for expedited processing - Receive, approve, provision in GETS IXCs, and mail GETS card to

POCs for routine requests for activation of GETS subscriptions is >90% of expedited requests completed within 8 business week hours

Release PINs to the Networks: The Contractor shall forward requests to the IXCs with any required

PIN data. PIN data provided to the IXCs shall not identify the associated NS/EP Priority Services users or organizations.

Update PIN Database: Upon creation and distribution of PINs, the Contractor shall update the PIN database.

Continuously Synchronize PINs and PIN Databases: The Contractor shall synchronize PINs with the

PIN database.

Release Partial PIN Databases to POCs: The Contractor shall release to each POC a partial PIN database consisting of only those PINs issued to that POC.

Electronic transfer of PIN data shall be encrypted.

5.4.4. WPS Readiness

The Contractor shall seek to maintain user subscriptions (approximately 235,000) and authentication process for service readiness at a 100% error free level. To achieve this object, the Contractor, exclusively, shall perform the following:

• Release WPS subscriptions to the Networks. The Contractor shall forward WPS subscriptions to the appropriate WPS service provider for provisioning in the service providers’ subscriber database. Only the

WPS telephone number and priority level shall be provided to the service provider.

• Update WPS Subscription Database. For each new WPS subscriber, the Contractor shall update

Contractor’s WPS Subscriber database.

• Quarterly, synchronize service provider WPS subscription information with Contractor’s WPS Subscriber

Database.

o Objective for routine processing - Receive, approve, and submit to WPS carrier routine requests for activation of WPS subscriptions >90% of routine requests completed within 24 business week hours o Objective for expedited processing – Receive, approve, and submit to WPS carrier expedited requests for activation of WPS subscriptions is >90% of expedited requests completed within 8 business week hours.

5.4.5. Security

The Contractor shall maintain PS security by ensuring the following:

Compliance with GETS and SRAS security classification guides

Compliance with DHS 4300B, DHS National Security System Handbook

Carriers maintain PS security through commercial best practices

Support the new objective of enhanced security by exploring new means for NGN GETS and SRAS security other than PIN use i.e., identity management as part of Future Services Engineering, Paragraph 5.3.3.

The Contractor shall ensure that only properly authorized persons have access to GETS/WPS data, including GETS and WPS calls records and other performance data.

The Contractor shall ensure that all GETS card number information is provided the appropriate level of protection against disclosure.

The contractor shall maintain GWIDS and upgrade its security, as necessary to reduce the probability of a data breach.

The contractor shall construct and accredit a secure room to administer the PIN database if required.

Specifically, the Contractor shall perform the following:

o Create a log and log all authentication attempts to access GWIDS o Log all changes to user privileges o Store the logs in an encrypted table o Ensure that the log can only be accessed via an interface to prevent tampering / deletion o Develop procedures and algorithms to analyze information in the audit logs o Encrypt the connection strings in configuration files to prevent use of the strings in backdoor attacks o Conduct SQL injection reviews and penetration tests to identify additional risks to be plugged o Encrypt the 12 digit PIN in the unclassified database for transfer and encrypt PIN data when transmitting to POC and carriers o Detect re-use of POC accounts by new POCs o Encrypt the monthly secure offsite data to ensure it cannot be read if the CDs are stolen in transit o Enhance GWIDS to be able to notify users, upon command, in case of a Sensitive Information breach.

o Expand the log to include the specific data accessed by a GWIDS user o Expand the log to include the bulk data exports o Develop procedures and algorithms to analyze the above information in the audit logs o Conduct additional SQL injection reviews and penetration tests to identify additional risks to be plugged o Populate the development and test environments with fictional data versus real GWIDS user data o Conduct a privilege escalation review process to minimize the ability of a hacker to obtain

“superuser” privileges o The Contractor shall support OEC’s effort to obtain and maintain authority to operate (ATO)

5.4.6. Enhanced Operational Support

Contractor shall improve OAM&P application methods and processes, including an enhanced means for measuring service performance. Contractor shall provide:

A cost-effective service performance monitoring and testing program that ensures Service performance and availability by conducting, and reporting on monthly post-implementation random testing. The post-implementation monitoring and testing shall be conducted using:

o WPS Remote Service Verification Process (RSVP) system or an equivalent, deployed at multiple sites dispersed nationally.

o GETS Remote Service Verification Process (RSVP) system or an equivalent, deployed at multiple sites dispersed nationally.

At the direction of the Government, the Contractor shall coordinate its testing program with AT&T, Verizon, and Sprint, to achieve maximum integration and effectiveness.

The Contractor shall obtain public call performance so PS performance can be compared to general network performance.

The performance monitoring and testing processes shall include documenting trouble detection and resolution through the normal OAM&P trouble handling and troubleshooting process.

Contractor shall maintains WPS phone accounts for WPS RSVP or an equivalent system and OEC testing and report to the government on usage of phones in those accounts.

5.4.7. Enhanced Service Performance Metrics

The Contractor shall:

Provide and maintain a Performance End-to-End Reporting Service (PEERS) application using “big data analytics” to process, qualify and integrate operational and usage data to produce a measurement of GETS and WPS end-to-end service performance

Provide and maintain applications and data collection for both GETS/WPS test calls (WPS RSVP) and user calls (PEERS) that assesses PS performance compared to the general public during and after disasters in the focused disaster area.

Plan the refinement and development of the PEERS approach for assessing end-to-end service performance in a hybrid network where NS/EP calls traverse both circuit and IP-based networks, submit the plan to the Government, and implement the plan when tasked by the Government

The Contractor shall continue to improve OAM&P applications and processes by providing and maintaining web-based reporting of service performance information (PEERS) through a PS

Management Dashboard.

5.4.8. Carrier Support

To ensure carrier services meet objectives, and for continuity, the Contractor shall provide operational support for the following carrier requirements to the extent that they are included in carrier agreements. Contractor shall maintain and update, as required by Sustainment Engineering and Technology Refreshment task results, these requirements carried over from the pre-existing carrier subcontracts and re-established under this PWS

Provisioning Requirements

OA&M Reporting Requirements.

Configuration Audits and Reporting Requirements. Contractor shall perform annual configuration audits with each carrier under agreement to provide GETS or WPS. Contractor shall work with carriers to pursue automation of quarterly configuration audits, with corrective measures being taken if errors are found, to the extent practical. Contractor shall pursue developing a database for archiving network information gathered from the configuration audits and make carrier network information available to the OEC.

Generic NSVT Test Plans and Reports Requirements. Contractor shall conduct NSVTs annually for each GETS and WPS carrier under subcontract for service, and prepare and submit to the Government a Test Report for each NSVT, with verification data, until such time as NSVTs are integrated with the overall testing program.

Billing Data Reporting Requirements.

Call Detail Records Reporting Requirements.

Annual Carrier Meeting Requirements. Contractor shall conduct Annual Program Reviews with the major carriers under subcontract for GETS and WPS, with virtual meetings preferred. APRs shall review the carrier’s past year service performance and future network and services evolution plans.

For GETS configuration data, the Contractor shall continue to provide Configuration Reports.

5.4.9. Testing Service

The Contractor shall develop an integrated and consistent approach to PS operational testing. The Contractor shall serve as the overall tester for PS by developing an affordable testing program.

Operational testing will consist of Legacy GETS and WPS testing, and NG PS testing for WPS on VoLTE and NGN GETS services that are operational at time of contract award.

Developmental, implementation and operational testing would be tasked as part of Technology Refreshment for new and upgraded services being developed and deployed.

As directed by the Government, and supported by the Government through the Government’s contracts with AT&T, Sprint and Verizon for the testing program, the Contractor shall conduct testing with AT&T, Sprint, and Verizon for services that are operational at time of contract award.

5.5. Optional Transition Services

5.5.1 Contract Phase In

The Contractor shall participate in a transition period for the Transition Task. During this period the Contractor shall coordinate with the Outgoing Contractor to transition this function to the new Contractor. The Contractor shall coordinate with the OEC and the Outgoing Contractor to determine the approach, major milestones, and schedule for this transition.

To ensure continuous GETS and WPS operations, the Contractor shall pursue placing agreements with the GETS LEC and WPS carriers for commencement, after the current carrier agreements expire.

5.5.2 Contract Phase Out

When tasked by the Government, the Contractor shall prepare a Transition Phase-Out Plan to transition tasks, Government-funded materials including test equipment, and information to an Incoming Contractor or to the Government. The Contractor shall provide requisite support to develop, document, and monitor the execution of the Transition Phase-Out Plan that may be used to transition tasks and materials to a new Contractor, or to the Government. The plan must incorporate an inventory of all services and Government-funded materials developed that are required to fully perform the services provided under this contract. The plan must include a schedule of briefings, including dates and time and resources allotted, that will be required to fully transition all Government-funded materials developed to the follow-on Contractor, and must provide the names of individuals that will be responsible for fully briefing their follow-on counterparts. The plan must ensure that the follow-on Contractor, and the Government, will be provided sufficient information and be fully briefed prior to the current expiration date of the contract, to provide adequate time for the new Contractor to have its personnel completely familiar with the requirements and in place on the turnover date. The Contractor shall plan for a 90 calendar day transition period. The plan shall provide the contact information for Contractor individuals who will be assigned to the transition team and identify their roles in the transition.

The Contractor shall participate in transition meetings with the Program Manager and project staff, and representatives of the successor Contractor and Government staff. The purpose of these meetings is to review project materials and take preparatory steps to ensure an effective transition of Contractor support. If tasked by the Government a draft transition plan is due to the Government 60 business days prior to the expiration date of the contract to allow for Government review, comment and approval.

5.6. Optional Technology Refreshment

The works described below are all optional.

5.6.1 Technology Refreshment Approach

Under a service-based approach, the Contractor shall pursue the technology refreshment project by specifying service function and performance, rather than a technical solution. The Contractor shall formulate the functional requirements to minimize dictating a specific technical solution and the performance requirements to maximize service operations, performance and performance validation through testing.

The Contractor shall utilize an approved GAO cost methodology to price software related development efforts.

The Contractor shall require the carrier to provide a service specification that describes its compliance to the service and performance specification. The Contractor shall assess the described service for effectiveness and shall deliver the service specification to the Government with the results of the effectiveness assessment as part of the Contractor’s proposal for the Technology Refreshment Task.

If authorized to proceed with implementation, the Contractor shall conduct acceptance testing to determine whether the service upgraded with the technology refreshment meets the functional and performance requirements in the subcontract statement of work and the carrier’s service specification.

After successful testing, the Contractor shall task the carrier with deploying the technology refreshment and providing the enhanced service.

The Contractor shall require the Service Provider to operate and maintain the subcontracted service, once implemented, throughout the subcontract’s Period of Performance. If the Service Provider makes network changes during the subcontract Period of Performance that affect the subcontracted service, Contractor shall require the Service Provider to demonstrate that the network changes do not compromise the service functionality or performance.

For all priority telecommunications service development and deployment initiatives, the Contractor shall be required to follow the Government’s prescribed process that follows. The Contractor may propose an alternative cost-savings process that is based on commercial practices if it can be mapped to the process that is hereby described. The Contractor must acquire Government approval for a substitute approach. The Government uses a service acquisition contract strategy based on the requirements identified in FRS documentation [Ref (a) and (b) below], which includes industry standards. The Contractor may propose using additional industry standards, as well as the standards-like Government Industry Requirements (GIR) documents as the basis for its approach to meet the requirements of the FRS; however, such an approach will be evaluated by the Government and may be used if found to be acceptable. Any vendor development initiated by the Contractor and paid for by the Government shall include Right to Use (RTU) language, where feasible, allowing other carriers, who are also approved by the Government to provide NS/EP Priority Services, to use the resulting development in their own networks at no additional vendor development cost to Government.

The Contractor may propose tailoring the NGN-PS SELC process to better match their own internal SELC processes, Such proposed tailoring will be evaluated by the Government and may be used if found to be acceptable. Regardless, the Contractor shall provide the technical reviews and testing deliverables to the Government as outlined below. Successively developed NGN-PS capabilities may result in multiple design and test reviews. Contractor documentation for design and test reviews, and Government witness testing will be the main deliverables used to verify and validate that requirements are being met. All issues concerning the subject of a review shall be resolved prior to conducting that formal technical review. The Contractor shall support direct on-site attendance at testing events of at least 6 individuals total (Government representatives and support contractors) to serve as Government witnesses. The Contractor may propose, pending Government approval, alternate approaches such as virtual participation in test events, where direct participation by 6 representatives is not possible.

The Contractor shall provide and maintain a Requirements Traceability and Verification Matrix (RTVM) that details how the NGN-PS requirements are being verified and validated at mutually-agreed upon milestones based on specified in references (a) and (b) above and any additional functional requirements agreed upon with the government. This RTVM shall include the Contractor’s planned requirements for all functions, capabilities and performance to be implemented for the proposed PS solution. The Contractor shall define interoperability and regression testing requirements drawn from reference (a) that insure the implemented capabilities are compatible with existing priority service capabilities. The Contractor shall incorporate these interoperability and regression testing requirements into the RTVM. This RTVM will be the basis of the design, implementation and testing for the remainder of the Contractor’s efforts for the proposed PS. The required verification method for all Reference (b) requirements is Demonstration, as defined in Reference (a).

Using the high-level information provided in its proposal as a basis, the Contractor shall provide a report that thoroughly identifies and describes the risks addressed by proposed priority capabilities and the level of performance improvement and/or risk mitigation expected due to deployment of each capability proposed.