Attachment_A-_Statement_of_Work.pdf

ATTACHMENT A: STATEMENT OF WORK

NNG16534898R

COMMUNICATIONS AND SECURITY SERVICES DIVISION

Goddard Space Flight Center (GSFC)

Land Mobile Radio (LMR) Statement of Work (SOW)

April 2016

Contents

Section 1. Introduction

1.1 Overview

1.2 Place of Performance

1.3 Government Furnished Equipment (GFE) and Services

1.4 Scope (CORE REQUIREMENTS)

1.5 Scope (IDIQ REQUIREMENTS)

Section 2. P25 System and Management Requirements

2.1 Centralized Core Switching Subsystem (CSS)

2.2 LMR Features

2.3 Greenbelt Site

2.4 Wallops RF Site

2.5 Information Security

2.6 Spectrum and Regulatory Compliance

2.7 Project-Level Design Reviews

2.8 System Cutover and Acceptance

Section 3. P25 Operations & Maintenance (O&M) Requirements

3.1 Preventative Maintenance

3.2 Corrective Maintenance

3.3 Program Control

Appendix A. Abbreviations and Acronyms ............................................................. A-1

List of Tables

Table 2.1 Greenbelt UHF Frequencies

Table 2.2 Wallops UHF Frequencies

Section 1. Introduction

1.1 Overview

This Statement of Work (SOW) describes the functions and requirements to be performed under contract to the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC), for the installation and maintenance of its Land Mobile Radio (LMR) systems that currently operate at the Greenbelt, Maryland facility and the Wallops Flight Facility (Wallops) in Wallops Island, Virginia.

This SOW is for the installation of the Greenbelt and Wallops Radio Frequency (RF) Sites to Project (P25) technology, with a P25 core switching platform located at either Greenbelt or a secure Contractor facility. This SOW also includes provisions to upgrade the RF Sites at other NASA installations (identified in Section 1.2) to the P25 standard, and integrate them with the core switching platform.

1.2 Place of Performance

The core requirements of this contract consist of the installation and maintenance of the P25 system that will be located at the NASA locations in Greenbelt, Maryland and Wallops Island, Virginia. The Indefinite Delivery Indefinite Quantity (IDIQ) components of the Contract allows for the installation and maintenance of P25 RF Sites by the issuance of individual delivery/Tasks orders and integrated with the core switching platform for other NASA installations as follows:

Independent Verification and Validation (IV&V), Fairmont, West Virginia

NASA Headquarters (NASA HQs), Washington, DC

Goddard Institute for Space Science (GISS), New York, New York

White Sands Complex (WSC), Las Cruces, NM

White Sands Missile Range Launch Complex 36 (WSMR LC36), Las Cruces, NM

White Sands Test Facility (WSTF), Las Cruces, NM

El Paso Forward Operating Facility (EPFOF), El Paso, TX

Other NASA Centers and/or support installations

1.3 Government Furnished Equipment (GFE) and Services

The following GFE will be made available at the Greenbelt and Wallops facilities as well as other NASA facilities that may be integrated through the issuance of delivery/task orders:

Network connections between RF Sites and the core switching platform.

Intra-site cabling between the RF Sites and connected equipment (e.g. dispatch consoles, management interfaces, recorder).

Rack space in telecommunications spaces to host equipment.

Access to the Greenbelt and Wallops facilities and badges required to allow designated Contractor support staff to access on-site LMR equipment.

1.4 Scope (CORE REQUIREMENTS)

The Contractor shall install a P25 system for Greenbelt and Wallops that is pursuant to system requirements identified in Section 2. Greenbelt will use the Ultra High Frequency

(UHF) frequencies identified in Table 2.1 and integrate with the Cisco telephony system.

Wallops will use the UHF frequencies identified in Table 2.2, operate in simulcast mode, and integrate with the Mission Voice Conferencing System, located at Wallops.

The Contractor shall provide a complete warranty for all delivered material and software and perform the following activities as defined in more detail in Section 3:

Continuous system monitoring, and incident tracking

Proactive preventative maintenance

Service Level Agreement (SLA) based corrective maintenance

Authorization and Accreditation certification prior to acceptance

Presentations and documentation

The Contractor shall include all hardware/ and software and material required to maintain and implement a P25 RF Site at Greenbelt and Wallops.

1.5 Scope (IDIQ REQUIREMENTS)

By the issuance of individual delivery/task orders, the Contractor shall install and/or maintain a P25 system for the NASA facilities/installations specified in Section 1.2. The Contractor shall include all hardware/ and software and material required to install, maintain and/or implement a P25 RF Site as required. Requirements for the other NASA installations are not included in the SOW, and orders may be issued to undertake these upgrades. System & Management and/or Operations & Maintenance requirements will be defined by the issuance of delivery/task orders. Section 2 and 3 of this SOW does not convey the specific requirements for the other NASA facilities that may integrate a P25 RF Site.

By the issuance of individual delivery/task orders the Contractor shall also perform engineering services required to expand the capabilities of the LMR system at any location. Expanded capabilities may include additional coverage areas, integration with

GFE voice or data systems, and deployment of additional LMR features identified in Section 2.2.3.

Additional items/components may also be ordered by the issuance of task orders.

Section 2. P25 System and Management Requirements

2.1 Centralized Core Switching Subsystem (CSS)

2.1.1 The availability of the LMR system to perform its intended function shall be a minimum of 99.995 percent of the time within any consecutive 365 day period, where the unavailability of any required service constitutes a failure. System longevity shall be 10 or more years from installation.

2.1.2 The Contractor shall integrate a P25 Phase II compliant Core Switching Subsystem (CSS). The CSS shall be scalable to accommodate additional RF sites at other NASA Installations; in addition to Greenbelt and Wallops; with an aggregate of 5,000 subscribers.

2.1.3 All critical call processing servers within the P25 CSS shall have redundant hardware, where backup elements restore radio communication within 35 seconds, and all data subsystems and services are restored within 75 seconds.

2.1.4 The Contractor shall provide, maintain, and manage a backup and restore function that is sufficient for them to comfortably maintain service availability requirements identified in requirement 2.1.1.

2.1.5 The system shall be configured to allow talk-groups to be shared between any and all NASA facilities that share the common CSS, including the facilities identified in Section 1.2 that may be integrated after contract award.

2.1.6 The CSS shall be configured with security partitioning between NASA facilities for all software interfaces provided to NASA (e.g. monitoring application, configuration application, voice recordings), such that personnel from one facility are only permitted to view, or affect change, for their respective facility, and are not permitted to view, or affect change, for any other facility.

2.1.7 The CSS shall be configured to provide NASA access to system administration and system monitoring functions. The system shall allow NASA to configure accounts and permissions for personnel within their facility in a least-privilege context, where users are restricted to only the required applications, and permissions within those applications are restricted such that administrators are only permitted to perform their required duties.

2.1.8 The system shall be configured to allow trunking to be maintained at each RF Site in the event that the centralized radio switch is unavailable. The Contractor shall describe the capabilities that are lost in the event that the centralized radio switch is unavailable.

2.1.9 The system shall conform to open standards and rely on Commercial-Off-the- Shelf (COTS) hardware and software.

2.1.10 The system shall be configured to record and log all activity on all talk-groups for Greenbelt and Wallops, as well as any other NASA installations identified in Section 1.2, such that NASA can access and save recordings over a secure Internet Protocol (IP) connection for a minimum of three months. The Contractor shall have a centralized recorder to support both the Greenbelt and Wallops facilities, or individual recorders for each facility.

2.1.11 The delivered system shall include a secure IP interface to data networks to enable software applications on Government Furnished Equipment (GFE) computers or mobile phones to communicate.

2.1.12 The Contractor shall provide a physical interface and procedure that allows NASA personnel at Greenbelt and Wallops to manually reprogram radios as an alternative to Over-the-Air-Programming (OTAP).

2.1.13 The Contractor shall provide data on Subscriber and system components Mean- Time-Between-Failures (MTBF) and Mean-Time-To-Restore (MTTR).

2.1.14 The System shall be configured to provide wide area trunking, roaming, seamless handoff when roaming, and Linear (CQPSK) Simulcast to Subscribers.

2.2 LMR Features

2.2.1 The system shall provide text messaging to and from dispatch consoles and subscriber units.

2.2.2 The system shall be configured to provide OTAP to all P25 subscribers (mobiles, portables, fixed) and dispatch consoles as required to allow NASA to update device configurations.

2.2.3 While these features are not immediately required, the Contractor shall ensure that all related hardware, software, and license costs are included for IDIQ purchase to ensure that NASA can execute a task order to implement the following features for any or all of the NASA facilities in the scope of the Contract.

The system shall have the capability to support the following features.

a) Identify the Global Position System (GPS) location for all subscriber units.

b) Centralized and distributed Over-The-Air-Rekeying (OTAR)

c) Inter-Switching System Interface (ISSI) interface to integrate with other

P25 trunked networks

d) Interface to integrate with conventional P25 systems

2.3 Greenbelt Site

2.3.1 The Contractor shall install one 5 Channel RF Site at Greenbelt using the available frequencies in Table 2.1 below, operating in a two-slot Time Division Multiple Access (TDMA) standard for 12 KHz radio channels:

CHANNEL

TRANSMIT

MHz

RECEIVE

MHz

SPACING

11 406.2375 415.2375 12.5 kHz

27 406.4375 415.4375 12.5 kHz

59 406.8375 415.8375 12.5 kHz

75 407.0375 416.0375 12.5 kHz

91 407.2375 416.2375 12.5 kHz

107 407.4375 416.4375 12.5 kHz

123 407.6375 416.6375 12.5 kHz

Table 2.1 Greenbelt UHF Frequencies

2.3.2 The Contractor shall install and configure both a prime and backup dispatch console, with each capable of providing all dispatch services. The Contractor shall provide all interfaces required to connect the dispatch consoles to the LMR system over GFE provided communication links.

2.3.3 The system shall be integrated with the Cisco IP telephony system at the Greenbelt facility such that radio users can place and receive telephone phone calls.

2.3.4 The Greenbelt system shall provide a minimum of 95% coverage, 95% of the time between portable radios and handheld, vehicle, and dispatch radios operating at head level (talk-in) and hip level (talk-out) for a service area to include: all outside areas within the perimeter of the Greenbelt campus, and the following areas that are within a 7 mile radius of the Greenbelt perimeter. The system shall provide a Delivered Audio Quality (DAQ) of 3.4 or higher and a Bit Error Rate (BER) of 2.6 or lower across the service area.

Cherrywood Lane/Greenbelt Metro Drive (Greenbelt Metro Station) (4 Miles)

Visitor’s Center (borders perimeter)

Powder Mill Road/Baltimore Washington Parkway (1 Mile)

Riverdale Road/Baltimore Washington Parkway (3 Miles)

85th Avenue/Harkins Road (New Carrollton Metro Station)

10200 Greenbelt Road, Lanham, MD (Aerospace Building) (1.5 Miles)

Laurel-Bowie Road/Baltimore-Washington Parkway (5 Miles)

Powder Mill Road/Edmonston Road (beginning of USDA Farms) (4 Miles)

Cherry Lane, Laurel, MD

University of MD, College Park, MD

Martin Luther King Jr. Highway & US Highway 50

Martin Luther King Jr. Highway & Forbes Boulevard

Greentech-IV Building (L40), Hubble Drive, Lanham, MD (in-building as well as coverage at the Guard Station in parking lot)

Baltimore-Washington Parkway Employee Entrance/Exit (from the Security Guard Booth to the end of the ramps getting on/off the Parkway)

2.4 Wallops RF Site

2.4.1 The Contractor shall install two 6 Channel RF Sites at Wallops using the available frequencies in Table 2.2 below, operating in a two-slot TDMA standard for 12 KHz radio channels:

CHANNEL

TRANSMIT

MHz

RECEIVE

MHz

SPACING

11 406.2375 415.2375 12.5 kHz

27 406.4375 415.4375 12.5 kHz

59 406.8375 415.8375 12.5 kHz

75 407.0375 416.0375 12.5 kHz

91 407.2375 416.2375 12.5 kHz

107 407.4375 416.4375 12.5 kHz

123 407.6375 416.6375 12.5 kHz

Table 2.2 Wallops UHF Frequencies

2.4.2 The Wallops RF Sites shall be configured to operate in simulcast mode.

2.4.3 The Contractor shall maintain synchronous timing between the two Wallops RF Sites, and provide tools and procedures to identify when timing is not synchronized.

2.4.4 The Contractor shall install and configure three dispatch consoles, two in the Dispatch Center and one in the Emergency Operations Center (EOC). The Contractor shall provide all interfaces required to connect the dispatch consoles to the LMR system over GFE provided communication links.

2.4.5 The Wallops system shall include an interoperability gateway to interface with the Wallops Mission Operations Voice Enhancement (MOVE) intercom system, where conventional channels are assigned individual Talk-Group IDs. The delivered system at Wallops shall contain primary and backup T1 interface that support Push-To-Talk (PTT) signaling, and the Contractor shall work with MOVE engineering staff as required to configure the interface in its operational configuration. The Wallops LMR to MOVE interface shall be included in acceptance testing. This interconnection is not initially required for the Greenbelt installation; however, any required hardware, software, or licensing shall be included for component purchase to later implement this interconnection for any NASA facility in scope of the Contract.

2.4.6 The Wallops system shall provide, at a minimum 95% coverage, 95% of the time between handheld, vehicle, and dispatch radios operating at head level (talk-in) and hip level (talk-out) for all areas within the perimeters and in transit between the Mainbase, Mainland, and Island. The system shall provide a DAQ of 3.4 or higher and a BER of 2.6 or lower across the service area.

2.4.7 The Wallops system shall be configured such that subscribers and dispatch consoles have the ability to communicate with the following mutual aide frequencies: 155.220 MHz, 155.255 MHz, 154.220 MHz, 154.430 MHz, 154.445 MHz, 155.685 MHz. Mutual aide frequencies include the Wicomico, Somerset, Accomack, and Northampton counties, and the town of Chincoteague.

2.5 Information Security

2.5.1 All LMR system components shall comply with IT security standards defined by the Office of Management and Budget (OMB) Circular A-130, NIST Special Publications 800-37 and 800-53a and the NASA Procedural Requirements (NPR) 2810.1a, Security of Information Technology. While NASA will have the responsibility to update the System Security Plan (SSP) to include the new P25 LMR IT system, the Contractor shall perform the following duties, in collaboration with NASA, to make required updates to the SSP and ultimately gain Authorization and Accreditation (A&A):

Provide a written response to system-specific security controls upon request from NASA for inclusion in the SSP

Participate in an official audit of A&A compliance against the P25 IT System

Resolve issues where the IT System in not compliant with NASA and NIST requirements. A&A compliance shall be a prerequisite for NASA’s final acceptance of the system from the Contractor.

2.5.2 The Contractor shall ensure that A&A compliance is maintained for the Term of the Contract. Contractor duties include the proactive maintenance of software (e.g. Operating System updates, anti-virus updates), and participation in the

NASA Continuous Monitoring process to include the routine testing of security controls and the ongoing remediation of security deficiencies. The Contractor shall also include alternative/contingency plans if any upgrades or updates fail to work.

2.5.3 The Contractor shall comply with the latest version of the NIST Special Publication 800-53 rev 4 (Recommended Security Controls for Federal Information Systems and Organizations) for a moderate system.

2.5.4 The Contractor shall review results of GFE vulnerability scanning against the operational system and report upon the impact of applying recommended updates to system configurations or Operating Systems (OS), and apply updates that are expected to improve the confidentiality, integrity, or availability of the system without adversely affecting performance. The Contractor shall support the NASA Vulnerability Management program upon request, by participating in quarterly vulnerability scans to ensure that there is no operational impact to the LMR system. The Contractor shall provide NASA a justification for not installing recommended updates and develop a Plan of Action and Milestone (POAM) for each vulnerability that cannot be mitigated.

2.5.5 The Contractor shall comply with NASA requirements for malicious code protection by providing the current version of the NASA standard anti-malware software (i.e. Symantec Endpoint Protection (32 and 64 bit)) on all compatible hosts. The Contractor shall procure and maintain compliant licensing and ensure that the version of the application, signature files, and engines are maintained per NASA standards.

2.5.6 The Contractor shall comply with NASA requirements for patch management.

2.5.7 The Contractor shall validate system compliance against the Agency Security Configuration Standards (ASCS), and the Center for Internet Security (CIS) Benchmarks.

2.5.8 The Contractor shall provide documentation that demonstrates that any remote connections for management, monitoring, and troubleshooting are compliant with NASA security policy.

2.5.9 The system design shall be IP based and support end-to-end encryption between all system components. The Contractor shall provide details on all encryption standards that are supported, and the associated cost of any additional hardware or software required to support encryption.

2.5.10 The system shall meet NIST and other NASA Security requirements and standards to ensure end to end user confidentiality. This requirement shall extend to the subscriber, dispatch and RF Site equipment, both local and remote.

The Contractor shall describe their security posture.

2.5.11 The system shall allow for secure access from the Contractor’s Network Operations Center (NOC) facility. The Contractor’s NOC shall be federally certified.

2.5.12 The system shall allow for the local and remote distribution of security updates and patches while continuing to provide wide area LMR service to subscribers and Dispatch Consoles.

2.5.13 The system shall comply with Federal Information Processing Standard (FIPS) 140-2, the Minimum Security Requirements for Federal Information and Information Systems.

2.5.14 The Contractor shall participate in annual and ad-hoc A&A continuous monitoring activities.

2.5.15 The Contractor’s solution shall describe their support and compliance with IPv6.

2.6 Spectrum and Regulatory Compliance

2.6.1 All LMR equipment shall meet P25 requirements for Chapters 5 and 8 of the latest version of the National Telecommunications and Information Administration (NTIA) Rules and Regulations for Radio Equipment.

2.6.2 In the event that the Government or Contractor suspects that the LMR system is interfering with GFE systems; the Contractor shall provide a written analysis of frequencies and power densities transmitted by the RF Site, and take immediate action to isolate and eliminate the source of interference.

2.6.3 All LMR equipment shall be installed, operated, and tested in accordance with NASA standards, 29 Code of Federal Regulations (CFR) 1910 Occupational Safety and Health Standards; 29 CFR 1926 Safety and Health Regulations for

Construction; NPR 8715.3 NASA General Safety Program Requirements, and relevant industry standards and practices including but not limited to FCC, NFPA, ANSI, ASME, NEMA, Underwriters Laboratories (UL), and Network Equipment Building System (NEBS) standards for safety, as well as GPR 1860.3 Radio Frequency Radiation Protection, GPR 8715.8 Fall protection requirements for NASA and GPR 1700.6 Confined Space Program at NASA.

2.6.4 The Contractor shall conform to MIL-STD810 C and D Environmental Test Methods and Engineering Guidelines.

2.6.5 The Contractor shall comply with emergency response standards provided by National Fire Protection Association (NFPA) 1221 and NFPA 1561.

2.6.6 The Contractor shall provide lightning and surge protection on Contractor provided system infrastructure and cabling. The Contractor shall ensure that all equipment is properly grounded by attachment to building and/or tower grounding system as applicable, and in accordance with the latest revision of the National Electrical Code (NEC).

2.7 Project-Level Design Reviews

2.7.1 The Contractor shall support a Technical Interchange Meeting (TIM) between NASA and Contractor personnel at the Greenbelt facility. The TIM shall serve as the initial review of Contractor plans to meet LMR requirements and delivery schedule, and allow NASA to convey technical detail and operating concepts to allow the Contractor to develop a design that meets both system and operational requirements.

2.7.2 The Contractor shall present a System Design Review (SDR) at the Greenbelt facility presentation. The SDR shall demonstrate to NASA that all system requirements and operational configurations have been met and are traced to the Contractors proposed system design and architecture. NASA shall have the opportunity to write Review Item Discrepancy (RID) against the SDR to document any issues or recommendations to be formally addressed by the Contractor. The SDR milestone shall be the means by which the Contractor obtains NASA Contracting Officer (CO) written concurrence to continue to refine the design towards a Critical Design Review. The written authorization to proceed will be provided by the NASA CO following the completion of the SDR and after resolution of all RIDs.

2.7.3 The Contractor shall present a Critical Design Reviews (CDR) at the Greenbelt facility. The CDR shall demonstrate to NASA that all requirements and operational configurations have been met and mapped into the Contractors proposed system design and architecture. The CDR shall also include all training material required to conduct classes identified in requirement 2.8.3.

NASA shall have the opportunity to write RIDs against the CDR to document any issues or recommendations to be formally addressed by the Contractor. The CDR milestone shall be the means by which the Contractor obtains NASA CO written concurrence to proceed with the implementation of the LMR system. The authorization to proceed will be provided by the NASA CO following the completion of the CDR and after resolution of all RIDs.

2.7.4 The Contractor shall develop a Site Acceptance Test (SAT) Plan for NASA approval. The SAT plan shall include step-by-step procedures, expected results, success criteria, and a Requirement Verification Matrix (RVM) that delineates traceability from each LMR SOW requirement to the specific step(s) in the test procedure. The SAT Plan shall include comprehensive coverage test procedures based on standards set forth in the Telecommunications Industry

Association (TIA) Telecommunications Systems Bulletin 88 (TSB-88) to assess coverage requirements set forth in Sections 2.3.4 (Greenbelt Coverage Requirements) and 2.4.6 (Wallops Coverage Requirements).

2.8 System Cutover and Acceptance

2.8.1 The Contractor shall install the LMR system in full and configure the entire LMR system in its operational configuration prior to the Cutover Period. NASA will provide the contractor with all relevant users, configurations, permissions, and software settings to enable the contractor to enable the Contractor to fully configure the system to meet NASAs requirements and operating environment.

2.8.2 The Contractor shall present a Test Readiness Review (TRR) prior to the cutover to demonstrate to NASA that the system is fully installed in its operational configuration and ready to support the execution of SAT procedures. The TRR shall also include the schedule for all test events, the system under test, and test participants. NASA shall have the ability to write RIDs against the TRR to document any issues or recommendations to be formally addressed by the Contractor.

2.8.3 The Contractor shall work with NASA and the current maintenance contractor to define and implement a design that allows the new P25 system to operate concurrently with either the Legacy Harris system or a conventional repeater system for a 2-week Cutover Period. The Cutover Period shall begin after the TRR and officially start at such time that both LMR systems are operated concurrently.

2.8.4 The Contractor shall conduct the following training classes during the Cutover Period on the system that is configured in its operational state. The Contractor shall provide all necessary equipment required for each training class and provide customized training material in both paper and electronic format.

System Administration (6 attendees) – All functions that LMR System Administrators will require to operate and configure the LMR system, including but not limited to, verifying health and status, provisioning new subscribers, reprogramming subscribers while directly connected or remote, modifying talk groups and user assignments, and any troubleshooting techniques to be performed by NASA personnel.

User Radio Operations (30 attendees) – All functions and services that are available to any and all subscribers.

Recorder Training (3 attendees) – All functions required for NASA to configure recorder policy, playback recordings, and save and archive recordings.

2.8.5 The Contractor shall participate in A&A audit and assessment activities during the Cutover Period, including but not limited to, interviews, demonstrations on the operational system, and work to remediate security deficiencies. The LMR system shall be A&A certified before NASA will formally accept and provide final payment to the Contractor

2.8.6 The Contractor shall execute the Site Acceptance test with NASA personnel and contract staff at both the Greenbelt and Wallops sites during the Cutover Period.

The SAT shall include the execution of the SAT Plan specified in Section 2.7.4.

The SAT shall also include comprehensive coverage testing for the Service Areas specified in Sections 2.3.4 and 2.4.6, verification of coverage in buildings and underground tunnels, and an evaluation of intermodulation and spurious and harmonic emissions across the Service Area. The Contractor shall bear all material and labor costs to resolve issues with coverage or emissions in the Service Areas.

2.8.7 After the SAT, the Contractor shall continue to provide development, engineering, and delivery services until completion of final acceptance by NASA.

This support shall include, but shall not be limited to, the following:

Providing a primary point of contact

Providing status reports as required by NASA

Resolving any open discrepancies during testing SAT

Monitoring and maintenance pursuant to terms set forth in Section 3 (P25 Operations and Maintenance Requirements) of this SOW

2.8.8 Final Acceptance of the LMR System shall be considered complete when all deliverable products have been inspected; the SAT is complete; all open discrepancies identified during SAT have been resolved; A&A compliance is formally granted; training is complete; and the LMR System has operated nominally for fourteen (14) consecutive days after the SAT. At such time, the Contractor shall provide a letter of Final Acceptance to be approved by NASA.

2.8.9 After Acceptance Testing has been completed, the Contractor shall decommission all legacy system infrastructure as identified by NASA (e.g.

powering down all equipment, removal from racks, disconnecting and removing antennas). The Government will dispose of the equipment.

2.8.10 The Contractor shall ensure that the new LMR systems are fully operational, accepted based on requirements in Section 2.8, all discrepancies have been resolved, at both Greenbelt and Wallops.

Section 3. P25 Operations & Maintenance (O&M) Requirements

The requirements set forth in Section 3 pertain to the Operations and Maintenance (O&M) of a P25 system and apply to both the Greenbelt and Wallops facilities with the exception of 3.3.2.

3.1 Preventative Maintenance

3.1.1 The Contractor shall actively monitor LMR hardware and software components on a 24x7x365 basis, and an alerting function shall be configured to provide real-time alerts to both the Contractor and NASA when failures are detected. The Contractor shall describe the alerting functions that are available (e.g. Short Message Service (SMS), email)) and indicate whether the monitoring function is fully standards based (e.g. Simple Network Management Protocol version 3 (SNMPv3)).

3.1.2 The Contractor shall provide a Preventative Hardware Maintenance Plan (PHMP) for NASA approval within one month of the contract effective date that includes the plan and interval to perform preventative maintenance activities for each hardware devices, and the mechanism and procedure by which the Contractor is notified of changes to any Vendor preventative maintenance guidelines.

3.1.3 The Contractor shall notify NASA immediately when LMR application software updates are available, including but not limited to patches or product enhancements available through the software maintenance program; identifying the nature of the update and any enhancements or new features contained within the update. The Contractor shall install such updates on fielded LMR components within 1 month after receiving written approval from NASA, and train NASA when new features are available.

3.1.4 The Contractor shall implement a technical procedure, schedule, and plan of action to maintain all software within the entire computing environment. This plan shall include all devices that require software or firmware updates (e.g.

application and Operating System software, anti-virus), the process to identify when new updates are required, the method to distribute updates to each type of affected device, and method to verify that updates were successfully deployed. The Contractor shall test all updates in a lab environment prior to fielding and ensure that all updates are fielded within one month of release.

3.1.5 The Contractor shall, upon NASA request, assist in the development of a

Contingency Plan and the testing of disaster recovery scenarios.

3.1.6 The Contractor shall develop and submit a risk analysis report on a yearly basis, due 10 days after the end of the calendar year, which proactively identifies areas that need improvement, such as hardware reliability, system timing, coverage assessment, and system configuration. The risk analysis shall include a physical survey of the equipment and operating conditions.

3.2 Corrective Maintenance

3.2.1 The Contractor shall provide a full warranty for all hardware and software that is installed under contract and bear all material and labor costs to replace any components that fail due to normal operational usage (the Contractor is not expected to cover damaged equipment that result from Acts of Mother Nature, or NASA’s negligence).

3.2.2 The Contractor shall arrive on-site at Greenbelt or Wallops to address the failure of LMR infrastructure and coverage enhancing equipment within 2 hours of outage notification, inclusive of travel time, on a 24x7 basis, 365 days per year.

If unable to meet the 2-hour criteria, the Contractor shall notify the facility points of contact personnel as soon as possible.

3.2.3 The Contractor shall restore failed services within 4 hours of arriving on-site at Greenbelt or Wallops, on a 24x7 basis, 365 days per year. The Contractor shall ensure that replacements parts for all infrastructure equipment are readily available in order to meet the 4-hour criteria for return to service.

3.2.4 The Contractor shall repair or replace all non-working hand-held and desktop radios and restore to original working condition within 4 weeks after receiving the defective unit.

3.2.5 The Contractor shall use original equipment replacement items when performing remedial maintenance. In the event that original parts are not available, the Contractor shall guarantee that parts are replaced with those of equivalent form, fit, and function, and that all parts are certified for use by NASA and relevant regulatory authorities.

3.3 Program Control

3.3.1 The Contractor shall support monthly status teleconferences or attend in-person as required. The status reviews shall start after contract award and continue through the life of the contract, and include as a Powerpoint presentation of the project action items, schedule, and status of task orders.

3.3.2 The Contractor shall support an in person presentation to NASA management at the Greenbelt facility on a quarterly basis that includes items such as current Contract status, outstanding issues and proposed resolutions and implementation schedule.

3.3.3 The Contractor shall provide a monthly report that includes all integration, preventative maintenance, and corrective maintenance activities performed during the given month, and a schedule for planned activities. Both reports shall be sent to the Greenbelt Contracting Officer’s Representative (COR) by the 10th day of the month following a completed month.

3.3.4 Upon NASA request, the Contractor shall assist NASA in the production of any project management documentation and deliverables required by the GSFC Code 760 Configuration Control Board (CCB) or other NASA LMR stakeholders (e.g. Facilities Management Division, Protective Services, Health & Safety).

A-1

Appendix A. Abbreviations and Acronyms

Acronym Definition

A&A Assessment & Accreditation

ACSC Agency Security Configuration Standards

CCB Configuration Control Board

CDR Critical Design Review

CFR Code of Federal Regulations

CIS Center for Internet Security

CO Contracting Officer

COR Contracting Officer Representative

COTS Commercial-Off-The-Shelf

CSS Core Switching Subsystem

DAQ Data Audio Quality

EOC Emergency Operations Center

EPFOF El Paso Forward Operating Facility

FCC Federal Communications Commission

FDCC Federal Desktop Core Configuration

FIPS Federal Information Processing Standard

GFE Government Furnished Equipment

GISS Goddard Institute for Space Studies

GPS Global Positioning System

GSFC Goddard Space Flight Center

IDIQ Indefinite Delivery Indefinite Quantity

IEEE Institute of Electrical and Electronics Engineers

IP Internet Protocol

ISSI Inter-Switching System Interface

IT Information Technology

A-2

IV&V Independent Verification & Validation

LMR Land Mobile Radio

MOVE Mission Operations Voice Enhancement

MTBF Mean-Time-Between-Failures

MTTR Mean-Time-to-Restore

NASA National Aeronautics and Space Administration

NASA HQs NASA Headquarters

NEBS Network Equipment Building System

NEC National Electrical Code

NFPA National Fire Protection Association

NIST National Institute of Standards and Technology

NOC Network Operations Center

NPR NASA Procedural Requirement

NTIA National Telecommunications and Information Administration

OMB Office of Management and Budget

O&M Operations and Maintenance

OS Operating System

OTAP Over-the-Air-Programming

OTAR Over-the-Air-Re-Keying

P25 Project 25

PHMP Preventative Hardware Maintenance Plan

POAM Plan of Action and Milestone

PTT Push-to-Talk

RF Radio Frequency

RID Review Item Discrepancy

RPM Radio Personality Management

RVM Requirement Verification Matrix

SAT Site Acceptance Testing

SDR System Design Review

A-3

SLA Service Level Agreement

SMS Short Messaging Service

SNMPv3 Simple Network Management Protocol

SOW Statement of Work

SSP System Security Plan

TDMA Time Division Multiple Access

TIA Telecommunications Industry Association

TIM Technical Interchange Meeting

TRR Test Readiness Review

TSB Telecommunications Systems Bulletin

UHF Ultra High Frequency

UL Underwriters Laboratories

WSC White Sands Complex

WSMR LC36 White Sands Missile Range Launch Complex 36

WSTF White Sands Test Facility