Attach_1_4.19_SOO.pdf

Statement of Objectives

National Oceanic and Atmospheric Administration (NOAA)

National Environmental Satellite, Data, and Information Service (NESDIS) Office of Satellite and Ground Services (OSGS)

Radio Frequency Interference Monitoring System (RFIMS)

April 19, 2017

ACQUISITION SENSITIVE

ii

Table of Contents 1 Background

2 Scope

3 Applicable Documents

4 Project Objectives

4.1 Management Objectives

4.2 Systems Engineering Objectives

4.3 Quality Control Objectives

5 System Objectives

6 Key Performance Parameters

7 Constraints and Risks

8 Deliverables

9 Period of Performance

10 Place of Performance

11 Travel

12 Government Furnished Property/ Information

13 COR or Assistant COR

14 IT Security Requirements

15. Contract Data Requirements List (CDRL) – content and format

Appendix A. Glossary

Tables Table 1: NOAA Earth Stations Locations Table 2: RFIMS KPPs Table 3: Deliverables Table 4: Total POP for all CLINs = 60 Months Table 5: NOAA Earth Stations Table 6: DOD Earth Stations Table 7: DOI Earth Stations

1 Background The National Oceanic and Atmospheric Administration (NOAA) is an agency that enriches life through science. NOAA plays several distinct roles within the Department of Commerce (DOC) and focuses on the condition of the oceans and the atmosphere. NOAA is comprised of various line, staff, and program offices that serve as vital contributors to NOAA’s mission. NOAA’s Mission is to understand and predict changes in climate, weather, oceans, and coasts, to share that knowledge and information with others, and to conserve and manage coastal and marine ecosystems and resources.

The National Environmental Satellite, Data, and Information Service (NESDIS) is a NOAA line office dedicated to providing timely access to global environmental data from satellites and other sources to promote, protect and enhance the Nation's economy, security, environment and quality of life. To fulfill its responsibilities, NESDIS acquires and manages the Nation's operational environmental satellites, operates the NOAA National Data Centers, provides data and information services including earth system monitoring, performs official assessments of the environment, and conducts related research.

Within NESDIS, the Office of Satellite Ground Services (OSGS) is responsible for consolidating the development and sustainment of all satellite ground systems. OSGS leverages common ground services and guides development of an integrated ground enterprise. The OSGS Mission is to:

• Sustain - Sustain NESDIS legacy ground systems and develop early enterprise elements.

• Enable - Transition and sustain next generation ground segments for the Joint Polar Satellite System and the Geostationary Operational Environmental Satellite – R Series.

• Create: Develop and deploy common Ground Enterprise Architecture Services.

The Radio Frequency Interference Monitoring System (RFIMS) Project resides under the program portfolio responsibility of the OSGS.

DOC identified 15 megahertz (MHz) of Federal use spectrum between 1675 - 1710 MHz suitable for sharing with commercial wireless carriers. Additionally, DOC and other Federal incumbents were required to develop and submit transition plans to implement spectrum relocation and sharing arrangements. As a result, the Federal Communications Commission (FCC) completed an auction of the third Advanced Wireless Services (AWS-3) spectrum and Long-Term Evolution (LTE) wireless carriers will eventually share use of the 1695 – 1710 MHz band following proper coordination with Federal agencies.

In the DOC Transition Plan, NOAA identified 17 Federal meteorological satellite Federal earth stations, within 15 Protection Zones, documented in the National Telecommunications and Information Administration (NTIA) Manual of Regulations and Procedures for Federal Radio Frequency Management, September 2015 Revision of the May 2013 Edition, footnote US88, in the 1675 – 1710 MHz band. NOAA earth stations will require protection from potential radio frequency (RF) interference once LTE wireless carriers begin sharing the band. There is a risk that uplink RF transmission from wireless carrier LTE user equipment (UE) may interfere with satellite downlink communications at NOAA earth stations.

In order to protect earth station communications, the OSGS is executing a project and undertaking contractual action to implement an RFIMS across NOAA’s Federal earth stations. The RFIMS will enable Government operators to detect RF interference, classify the nature of RF interference, identify the source(s) of interference, and notify wireless carriers sharing the 1695 – 1710 MHz band of interference.

The OSGS’s objective is to select a vendor capable of successfully designing, developing, and deploying an integrated RFIMS and centralized monitoring solution. The RFIMS should enable the OSGS to work with commercial wireless carriers in eliminating interference issues in areas where NOAA shares the 1695 – 1710 MHz band with wireless carriers.

The National Telecommunications and Information Administration (NTIA) Institute for Telecommunications Sciences (ITS), Spectrum and Propagation Measurements Division, will serve as OSGS’s Developmental Test and Evaluation, Operational Test and Evaluation, and Independent Verification and Validation agent for the detect, classify, and identify aspects of the RFIMS acquisition effort. NTIA/ITS has provided years of RF signal collection, analysis, and expertise to government agencies as well as overseeing and conducting electromagnetic signal collection activities at the DOC Table Mountain Facility. NOAA will expect the contractor to coordinate with ITS regarding in-house and field test and evaluation activities of the RFIMS, for subsystems and the complete system, during the design, development, and operational phases of the acquisition effort.

2 Scope This statement of objectives (SOO) describes the scope of work, objectives, tasks, and resources needed to meet NOAA’s objectives for the design, development, testing, and deployment of Radio Frequency Interference Monitoring System (RFIMS) subsystems at 17 Federal earth stations and a centralized management location. Additionally, NOAA may pursue the option to acquire up to 18 additional RFIMS subsystems for Department of Defense (DOD) earth stations and acquire up to five (5) additional RFIMS subsystems for Department of Interior (DOI) earth stations. DOD and DOI earth stations will not be part of the NOAA integrated RFIMS and centralized monitoring system.

The RFIMS must be capable of detecting RF interference, classifying the nature of RF interference (e.g., LTE, non-LTE, out-of-band emission, or spurious emission), identifying the source(s) of interference, and notifying NOAA operators and wireless carriers of interference. NOAA must develop an RFIMS to protect meteorological satellite earth stations from LTE interference in the 1695 – 1710 MHz band it will begin to share with wireless carriers in April 2018. NOAA desires protection at designated earth stations by April 2018 but is unsure if this objective is possible due to the anticipated technical complexity in developing the RFIMS. However, the Agency encourages prospective bidders to propose a solution based on an implementation schedule that enables NOAA to monitor federal earth stations by the April 2018 transition deadline. Table 1 below identifies the initial set of NOAA satellite earth stations that will require an RFIMS.

Table 1: NOAA Earth Stations Locations Location Facility

Fairbanks, AK Fairbanks Command and Data Acquisition Station (FCDAS) Anchorage, AK Elmendorf Air Force Base (AFB) Barrow, AK Barrow Observatory Monterey, CA Monterey Boulder, CO Space Weather Prediction Center Miami, FL Atlantic Oceanographic and Meteorological Laboratory (AOML) Miami, FL National Hurricane Center Barrigada, GU Andersen AFB Ford Island, HI Hickam AFB Suitland, MD NOAA Satellite Operations Facility (NSOF) Greenbelt, MD Goddard Space Flight Center Bay St. Louis, MS Stennis Space Center Kansas City, MO Kansas City Norman, OK Norman Guaynabo, PR Guaynabo Wallops Island, VA Wallops Command and Data Acquisition Station (WCDAS) Fairmont, WV Remote Backup

Section 11: Travel identifies the federal earth station locations for optional DOD and DOI RFIMS subsystems.

3 Applicable Documents The following documents are relevant to this SOO:

1. Federal Information Security Modernization Act of 2014, December 2014.

2. DOC Information Technology Security Program Policy, September 2014.

3. Commerce Information Technology Requirement (CITR)-019, Risk Management Framework, July

2012.

4. FCC Public Notice DA 14-1023 FCC and NTIA: Coordination Procedures in the 1695-1710 MHz

Bands, Appendix A, July 18, 2014.

5. FCC Amendment of the Commission's Rules with Regard to Commercial Operations in the 1695-

1710 MHz, 1755-1780 MHz, and 2155-2180 MHz Bands, FCC-13-102, July 23, 2013.

6. FCC Rules and Regulations for Title 47 Code of Federal Regulations (CFR), Part 2 (§2.106), Table of

Frequency Allocations, Footnote US88.

7. FCC Rules and Regulations for Title 47 CFR, Part 27, Subpart L—1695-1710 MHz, 1710-1755 MHz, 1755-1780 MHz, 2110-2155 MHz, 2155-2180 MHz, 2180-2200 MHz Bands (§27.1134), Protection of Federal Government operations.

8. Commerce Spectrum Management Advisory Committee Final Report Working Group 1 - 1695 - 1710 MHz Meteorological - Satellite, Revision 1, July 23, 2013.

9. National Institute of Standards and Technology (NIST) Standard Publication (SP) 800-53 Revision 4, Security and Privacy Controls for Federal Information Systems and Organizations, April 2013 (updated January 22, 2015).

10. NIST Federal Information Processing (FIPS) SP 200, Minimum Security Requirements for Federal Information and Information Systems, March 2006.

11. NIST FIPS SP 199, Standards for Security Categorization of Federal Information, February 2004.

4 Project Objectives NOAA has identified the following project objectives for an RFIMS that will be located at each Federal earth station location:

1. Enable sharing of the frequency spectrum between NOAA and wireless carriers due to the FCC-led Auction-97 of the 1695 – 1710 MHz band; ensuring satellite downlink integrity is not compromised while allowing wireless carriers to maximize access to the frequency band.

2. Develop, deliver, install and maintain a RF monitoring system that can detect RF interference in real-time, classify the nature of RF interference in real-time, identify the source(s) of interference, and notify NOAA operators of interference.

a. NOAA defines interference as any power exceedance above the interference power spectral density threshold to the required satellite signal quality at federal earth stations.

b. Interference events can occur in the 1695 – 1710 MHz band, affecting Polar Operational Environmental Satellite (POES) and Meteorological Operational Satellite (METOP) downlink transmissions. Interference events can also occur in the adjacent 1675 – 1695 MHz band, affecting Geostationary Operational Environmental Satellite (GOES) downlink transmissions.

3. A more detailed description of the functional capabilities NOAA desires for the system are as follows:

a. Detect - The system should detect, in real-time, “interference events” where the interference level lies at or above -161.4 decibel-watts (dBW)/ 180 kilohertz (kHz) interference power spectral density (IPSD) (-161.4 dBW mean power over a 1-ms time interval in a 180 kHz equivalent noise bandwidth) or configurable protection threshold power level, during NOAA’s earth station downlink reception at the receiver. NOAA desires a monitoring system capable of adjusting the interference detection threshold between -161.4 dBW/ 180 kHz IPSD (i.e., highest sensitivity) and a less sensitive IPSD value. The Government encourages prospective offerors to recommend the less sensitive IPSD value for the adjustable interference detection threshold range. The system should be capable of detecting interference events within 1670 – 1710 MHz;

however, the monitoring system should cover a frequency range spanning from 1670 - 1755 MHz. NOAA will require the contractor to validate the actual receive sensitivity of the RFIMS required to meet interference detection objectives.

b. Classify - The system should classify the types of RF interference it detects at -161.4 dBW/180 kHz IPSD or higher in real-time. NOAA desires a monitoring system capable of adjusting the interference classification threshold between -161.4 dBW/ 180 kHz IPSD (i.e., highest sensitivity) and a less sensitive IPSD value. The Government encourages prospective offerors to recommend the less sensitive IPSD value for the adjustable interference classification threshold range. Where “classify” is the discrimination between interference caused by 1695 – 1710 MHz LTE UEs or other co-channel RF transmissions and all other radio frequency interference (RFI) such as out-of-band and spurious emissions.

i. Out-of-band emission includes interference from a frequency or frequencies outside the 1695 – 1710 MHz band but within the 1670 – 1755 MHz frequency range.

ii. Spurious emission includes interference to the 1695 – 1710 MHz band from harmonics, intermodulation products, and frequency conversion products within the 1670 – 1755 MHz frequency range.

c. Identify - The system should determine if the RFI, at -161.4 dBW/180 kHz IPSD or higher, is resulting from 1695 – 1710 MHz LTE UE uplink wireless transmission or other sources of interference. NOAA desires a monitoring system capable of adjusting the interference identification threshold between -161.4 dBW/ 180 kHz IPSD (i.e., highest sensitivity) and a less sensitive IPSD value. The Government encourages prospective offerors to recommend the less sensitive IPSD value for the adjustable interference identification threshold range. The system should identify the wireless carrier(s) responsible for operating the tower(s)/sector(s) that are communicating with the UE(s) causing the interference in real-time.

i. NOAA desires a system that can identify the UE(s) creating interference and the wireless carrier antenna sector(s) responsible for communicating with the interfering UE(s).

ii. If identification of the wireless carrier antenna sector(s) responsible for communicating with the interfering UE(s) is not possible, NOAA encourages prospective vendors to recommend a solution that makes identification of interfering UEs and the responsible wireless carriers effective and efficient.

d. Notify - The system should notify NOAA operators and the wireless carriers, that wireless carriers are creating interference to NOAA. The “Notify” function is to provide the wireless carriers with access to the monitoring system data so they can mitigate interference as soon as it occurs, and then acknowledge completion of interference mitigation.

4. Provide real-time, two-way, communication between a centralized monitoring facility and the wireless carriers. The communication solution should leverage the existing Internet connectivity at the centralized monitoring facility. The centralized monitoring facility will be at a NOAA location.

5. Consolidate the data from all 17 NOAA federal earth station locations so that a Government operator at a single location can:

a. Access the data,

b. Analyze the data,

c. Archive the data,

d. Generate reports.

6. Comply with the Federal, DOC, NOAA, and FCC, and NIST laws, regulations, policies, standards and guidelines listed in Section 3: Applicable Documents.

7. Maintain and archive technical data from all interference events.

a. Examples of technical data would include information such as RFI events as occurring in the 1670 – 1710 MHz frequency range, AWS-3 wireless carrier(s) associated with RFI events, frequencies, power levels, and timestamps for detected RFI events. Vendors are encouraged to recommend the types of data NOAA should collect, maintain, and archive.

b. NOAA’s initial assumptions are a 90-day active period for short-term data storage at remote earth stations prior to transfer to the centralized management facility for long-term archive. Vendors are encouraged to recommend times for short and long-term RFI data storage.

The following subsections identify management, systems engineering, and quality control objectives for the RFIMS.

4.1 Management Objectives

NOAA has identified the following management objectives for the RFIMS Project:

1. Allow the contractor the maximum flexibility to innovatively manage the projected schedule, performance, risks, warranties, subcontracts, and data to provide a RFIMS solution that satisfies NOAA’s performance requirements.

2. Using project management knowledge, processes, skills, tools, and techniques to meet RFIMS Project requirements.

3. Managing of scope, schedule, cost, quality, and risks to meet RFIMS Project requirements.

4. To maintain clear Government visibility into the project schedule, performance, and risks as well as cost expenditures throughout all phases of the development and deployment cycle.

5. Developing a work breakdown structure to decompose the total scope of work to accomplish project objectives and create required deliverables.

6. Using an integrated master schedule to provide the RFIMS Team with accurate and timely schedule and performance information throughout the life cycle of the project.

7. Using cost management methodology that manages and controls costs so the project can be completed within the approved budget.

8. Using earned value management that is fully aligned with the Work Breakdown Structure of the

RFIMS Project and with sufficient granularity to facilitate an accurate assessment of schedule performance, cost performance, and progress of the project.

9. Using risk management methodology that proactively identifies, analyzes, mitigates, monitors, and controls project risks.

10. Using change management plan to define how changes will be monitored and controlled.

11. Using communications management methodology to ensure timely and appropriate planning, collection, creation, collaboration, distribution, and management of project information.

12. Developing a NOAA and contractor integrated project team partnership to assist in achieving project goals.

13. Management reviews, over the project life cycle, for tracking, reviewing, and regulating progress to meet performance objectives.

14. Developing and maintaing of software code based on Capability Maturity Model Integration (CMMI) for Development Level 3 or equivalent standards and delivery of all code, documentation, and technical data.

4.2 Systems Engineering Objectives

NOAA has identified the following systems engineering objectives for the RFIMS Project:

1. Using a contractor experienced in using well-defined and mature processes such as Capability Maturity Model Integration for Development Level 3.

2. Using an industry standard system development life cycle (SDLC) for requirements development, requirements validation, system design, implementation, integration, testing and validation.

Prospective vendors may propose predictive, iterative, or adaptive life cycles for completing the project.

3. Using a requirements development process to include requirements definition, requirements analysis, and requirements management through the SDLC.

4. Developing a proof of concept and associated prototype(s) to demonstrate feasibility of meeting validated RFIMS requirements.

5. Developing an RFIMS that utilizes the best technical approach to maximize performance while minimizing life cycle operations and maintenance cost.

6. Actively engaging with NOAA RFIMS technical team members and NOAA RFIMS stakeholders throughout the project.

7. Prospective contractors may propose their recommended SDLC or may consider using life cycle reviews such as the following to control progress of RFIMS development:

a. Integrated Baseline Review (IBR) to establish the performance measurement baseline.

b. System Requirements Review (SRR) to verify and validate the set of system requirements before the Contractor starts detailed design activities.

c. Alternative Systems Review (ASR) to validate there is sufficient understanding of the technical maturity, feasibility, and risk of the preferred solution in terms of meeting operational, affordability, and technology needs.

d. Preliminary Design Review (PDR) to demonstrate the preliminary design meets all system requirements with acceptable risk, within cost and schedule constraints, and establishes the basis for proceeding with detailed design.

e. Critical Design Review (CDR) to demonstrate the maturity of the design is sufficient to start with full-scale fabrication, assembly, integration, and testing.

f. Integration, Verification, and Validation reviews as RFIMS components are assembled into higher-level subsystems and elements.

g. Test Readiness Review (TRR) to ensure the RFIMS test article, test facility, support personnel, and test procedures are ready for testing.

h. Operational Readiness Review (ORR) to examine the actual system characteristics and the procedures used in the RFIMS operation and ensure all system and support hardware, software, personnel, procedures, and user documentation accurately reflect the deployed state of the system.

i. System Acceptance Review (SAR) to perform a combination of factory and site acceptance testing.

j. Other management related reviews as required to control RFIMS system development based on the type of existing risks or issues.

8. Use of change and configuration management processes that control how informal and formal changes are proposed, analyzed, planned, implemented, and released as the system evolves through the SDLC phases.

9. Developing and delivering training required for NOAA to operate, maintain, and sustain the

RFIMS.

4.3 Quality Control Objectives

NOAA has identified the following quality control objectives for the RFIMS Project:

1. A minimum of International Organization for Standardization 9001 Certification, demonstrating a quality management system to meet NOAA requirements.

2. Adherence to the NOAA Quality Assurance Surveillance Plan and developing a contractor Quality Control Plan (QCP) specifically tailored to the RFIMS requirement and incorporated from the proposal at time of contract award.

3. Close collaboration with RFIMS Team members for functional and technical quality control to ensure the developed RFIMS adheres to agreed quality criteria.

5 System Objectives NOAA has identified the following high-level system objectives for the RFIMS:

1. Capable of monitoring the 1670 - 1755 MHz frequency range that includes the 1695 - 1710 MHz AWS-3 Frequency Band, enabling Government operators to monitor for RFI to the following satellite systems:

a. Geostationary Operational Environmental Satellite (GOES),

b. Polar Operational Environmental Satellite (POES),

c. Meteorological Operational Satellite (METOP) systems,

d. All future NOAA satellite missions which use 1670 – 1710 MHz.

2. The system will be deployed at up to 17 NOAA Federal earth stations and be architecturally scalable to support management of up to 32 NOAA Federal earth stations without requiring significant changes to the system architecture or software. Delivery, installation and sustainment includes all spare parts and associated warranties. This is independent of any optional DOD or DOI systems.

3. The system will be capable of monitoring for RF interference to Federal earth station receivers, where interference is defined as RFI from both 1695 – 1710 MHz and adjacent frequency band AWS-3 LTE and non-LTE transmissions, and will be limited to below the -161.4 dBW/ 180 kHz IPSD threshold. NOAA defines interference as any degradation to the required satellite signal quality at federal earth stations where the interference level is at or above the -161.4 dBW/ 180 kHz IPSD.

a. NOAA desires a system capable of detecting any interference equal to or higher than an IPSD of -161.4 dBW/ 180 kHz. However, NOAA also realizes this receive sensitivity may result in the monitoring system triggering many notification events.

b. NOAA encourages vendors to propose a solution that balances the need to identify qualifying interference events yet serves as an effective and suitable system for the NOAA operational environment.

c. NOAA defines an effective and suitable system as meeting the technical objectives in a manner that does not create a burden for operational end users such as providing excessive notification alarms due to intermittent interference events occurring between the detection and identification or classification thresholds.

d. Offerors should address this challenge in their proposals by describing how they plan to achieve system objectives while implementing a solution that is operable or will work well in NOAA’s operational earth station environment.

4. Capable of identifying detected and classified sources of LTE and non-LTE RFI, occurring within the 1670 - 1710 MHz frequency range, at Federal earth stations to include:

a. Identify the LTE wireless carrier(s), operating in the 1695 – 1710 MHz band, associated with LTE RFI events.

b. Identify the source(s) of the RFI events as occurring in the lower adjacent band (1670 - 1695 MHz), the A1 Block (1695 - 1700 MHz) or the B1 Block (1700 - 1710 MHz); and identify the AWS-3 wireless carrier associated with the RFI, if applicable.

c. Identify and summarize the frequencies, power levels, and timestamps for detected RFI events.

d. Detecting, classifying, and measuring LTE RFI from UEs with the minimum number of resource blocks used by the wireless carriers.

e. Capable of identifying all RFI when NOAA is tracking satellites from five-degree elevation angles to zenith (e.g., between five and 90 degrees). NOAA does not require notification of RFI for elevation angles below five degrees to be sent to wireless carriers; however, the system should provide such RFI information at best effort if the system is so capable.

5. Capable of notifying identified interfering wireless carriers of RF environment status and RFI events.

6. Capable of detecting interference from terrestrial and airborne platforms via diffraction and ducting propagation paths.

7. Capable of detection, classification, identification, and notification to support spectrum time sharing between NOAA and wireless carriers.

a. The wireless carrier may propose time-sharing for a situation where satellite receive antennas are at elevations above 45 degrees, over 360 degrees in azimuth.

b. The wireless carrier may propose time-sharing for a situation where satellite receive antennas are at elevations below 45 degrees, over a contiguous subset of potential azimuths.

8. Capable of providing interference information from a minimum of 17 remote monitoring stations to a centralized management facility. The system should be scalable to support collection of interference information from up to 32 earth stations. NOAA will confirm the number of additional earth stations required.

a. The centralized management facility is the site responsible for communicating with wireless carriers in real-time and during engineering activity to include:

i. Implementing communication interfaces to access collected data regularly or as needed when triggered by specified alarm conditions in real-time.

Communication interfaces should leverage existing Internet connectivity at federal earth stations.

ii. Communications between remote monitoring stations and the centralized management location, through a secure approach, that includes at a minimum, authentication and authorization.

iii. Information such as frequency domain spectrum analysis measurements and tabular interference data.

iv. Access for up to 100 simultaneous users.

v. Single user authentication.

vi. Restricted access to authorized and authenticated users.

vii. Access to long-term and short-term data.

1. Short-term data would include RFI detection, classification, and identification information the remote monitoring subsystems collect.

2. Long-term data would include information NOAA could use to analyze interference trends such as the types of RFI that occur most frequently, per earth station location, and the responsible wireless carriers.

viii. Ability to remotely configure monitoring systems at federal earth stations from the centralized management facility remotely.

ix. A centralized management facility with the ability to backup system-wide RFI summary data archived at the facility.

x. Earth station monitoring subsystems capable of local control by Government operators and remote control from the centralized management facility.

9. Provide redundant or mirrored data storage for federal earth stations and a centralized management facility with backup capability to include:

a. System archive search capability.

b. Data export capability from a system archive.

c. Generating statistical reports from archived RFI events.

d. Allow an operator to perform engineering analyses of interference events, such as playback, plotting, and trend analysis.

e. Prospective offerors should recommend the amount of data to collect at earth stations based on an understanding of NOAA’s objectives and their proposed solution.

10. Centralized management facility capable of managing and monitoring interference data from all remote monitoring systems at federal earth stations. The system will include a graphical user interface for management, operations capability, and access to all system functionality.

Prospective offerors should propose a centralized management solution based at a Government facility.

11. A description of the modularity and extensibility for the proposed monitoring system and what is required to support upgrades such as, ability to operate in additional frequency bands (e.g., S- Band frequencies) and ability to classify and identify signal waveforms for developing and new wireless technologies such as:

a. LTE-Advanced, LTE-Advanced Pro, and future 3rd Generation Partnership Project (3GPP) LTE releases

b. Fifth Generation wireless systems and future 3GPP radio access technologies

c. Technologies that currently or are planned to support the Internet of Things (IoT)

i. LoRa Alliance Technology Low Power Wide Area Network specification that is projected to provide long range communications based on chirp spread spectrum modulation

ii. LTE Machine Type and Machine-to-Machine Communications

iii. LTE Narrowband IoT

12. Uses application program interfaces instead of proprietary standards for external communication interfaces.

13. Capable of manual, semi-autonomous, and autonomous operation which are defined as:

a. Autonomous: Operated by a computer without a need for human control or intervention.

b. Semi-autonomous: Providing some autonomous capabilities and requiring some human control or intervention.

c. Manual: Requiring human control or intervention.

14. Providing the required system availability at 17 NOAA federal earth stations and the centralized management location.

a. Provide at least 99% system availability at Wallops and Fairbanks command and data acquisition stations.

b. Provide at least 95% system availability at other NOAA Federal earth stations.

c. Offerors should include a discussion on availability in their proposals and describe how they propose to achieve the desired metric.

15. Remote monitoring and centralized management subsystems capable of supporting remote software maintenance and software upgrades.

16. Capable of generating interference reports to include:

a. Generating a system-wide status report for a user-defined period.

b. Generating an RFI status report for a selected earth station for a specified period.

c. Generating an incident report from an RFI event.

17. Capable of detecting RFI events, at or above -161.4 dBW/ 180 kHz IPSD, with a probability of correct detection for each event to be greater than 90%.

18. Capable of classifying and identifying RFI events, at or above -161.4 dBW/ 180 kHz IPSD, with a probability of correct classification and identification for each event to be at least 95%.

6 Key Performance Parameters This section includes key performance parameters (KPPs) to establish measurable benchmarks for the system objectives Section 5 defines. The KPPs in Table 2 represent measurable criteria for the successful development of a RFIMS.

Table 2: RFIMS KPPs KPP # Parameter Desired Performance

1 Receive Sensitivity

RFIMS with a minimum receive sensitivity threshold of -161.4 dBW/ 180 kHz IPSD

2 Detection Detection of RFI events, at or above -161.4 dBW/ 180 kHz interference power spectral density (contractor to validate), with a probability of correct detection for each event to be greater than 90%.

3 Detection Detection of RFI event within 1 second of occurrence.

4 Classification Classification of RFI as LTE or non-LTE, at a detection level of -161.4 dBW/ 180 kHz IPSD, with the probability of correct classification greater than 95% and the probability of false classification less than 5%.

5 Classification Classification of RFI event within 1 minute of occurrence.

6 Identification Identification of RFI as LTE or non-LTE, at a detection level of -161.4 dBW/ 180 kHz IPSD with the probability of correct identification greater than 95% and the probability of false classification less than 5%.

7 Identification Identification of the source(s) of interference in real-time not to exceed 10 seconds.

8 Notification Notification of RFI event occurrence to wireless carrier in real-time and acknowledgement from wireless carrier of completed RFI mitigation.

9 Availability Provide an overall system availability of 95%.

10 Availability Provide at least 99% system availability at Wallops and Fairbanks command data acquisition stations where the system availability includes reporting of RFI through the central monitoring facility.

11 Availability Provide at least 95% system availability at all other NOAA federal earth stations where system availability includes reporting of RFI through the central monitoring facility.

Table 2 identifies notional KPPs. However, NOAA encourages prospective offerors to recommend detection, classification, identification, and notification metrics that will enable the Agency to identify and mitigate interference to satellite earth stations as fast as possible and exceeding the above KPPs.

7 Constraints and Risks

1. Prospective offerors should expect to decompose NOAA’s high-level system objectives into detailed system-level requirements, as needed, to support the development of RFIMS throughout the SDLC lifecycle.

2. NOAA will not complete the requirements definition and decomposition process to detailed system-level requirements and will solely rely on the contractor to perform this work and verify/validate those requirements when they are defined.

3. NOAA has not fully developed a proof-of-concept for a system capable of classifying the nature of unacceptable RF interference to satellite ground stations (e.g., LTE UE uplink signals, background impulsive noise, or out-of-band emissions); and will rely on the contractor to complete this development.

4. NOAA has not fully developed a proof-of-concept for a system capable of identifying the source(s) of LTE UE-generated interference to satellite ground stations and will rely on the contractor to complete this development.

8 Deliverables Table 3 identifies the list of Contract Line Items (CLINs), reference Contract Data Requirements (CDRLs) list, and deliverables the contractor should provide to the Government for the RFIMS Project. The contractor should propose a deliverable submission period for the CLINs that have “to be proposed (TBP)” as a submission frequency in Table 3.

Table 3: Deliverables

CLIN

Reference and

CDRL

Deliverable Format and Medium Submission Frequency

Receiving Official

CLIN 0001

A001

Kick-off Meeting Contractor’s briefing material in Microsoft PowerPoint format.

(Reference FAR 42.5)

Within ten business days after contract award

Contracting Officer (CO)

CLIN 0001 –

A002

Monthly Activity and Progress Report

Submitted in Microsoft Word format by electronic submission. Contractor’s format and content is acceptable.

(Reference FAR 42.11)

No later than the fifth working day of each month

Technical Monitor

(TM),

Contracting Officer’s Representat ive (COR), CO

CLIN 0001 –

A003

Project Management Plan

Submitted by electronic submission.

Format and content per: See SOO Section 15.

(Reference PMBOK Guide)

Within 30 calendar days after contract award and updates as required

TM, COR

CLIN 0001 –

A004

Project Management Status Review Data Package

Submitted in Microsoft Word format by electronic submission.

Format and content per: See SOO Section 15.

Every 30 calendar days through the period of performance (POP)

TM, COR

CLIN

Reference and

CDRL

Deliverable Format and Medium Submission

Frequency Receiving

Official

CLIN 0001 –

A005

Contract Performance Report

Submitted in Microsoft Word format by electronic submission.

Format and content per: DI-MGMT-81861.

Every 30 calendar days through the POP

TM, COR,

CO

CLIN 0001 –

A006

Earned Value Management System Plan

Submitted in Microsoft Word format by electronic submission.

Format and content per: See SOO Section 15.

(Reference FAR 34.2)

Within 30 calendar days after contract award

TM, COR,

CO

CLIN 0001 –

A007

Contract Funds Status Report

Submitted in Microsoft Word format by electronic submission.

Format and content per: DI-MGMT-81468.

Quarterly through the

POP

TM, COR,

CO

CLIN 0001 –

A008

Meeting Minutes

Submitted in Microsoft Word format by electronic submission. Contractor’s format and content is acceptable.

No later than two business days after meeting; updated as required

TM, COR

CLIN 0001 –

A009

Risk Management Plan

Submitted in Microsoft Word format by electronic submission.

Format and content per: DI-MGMT-81808.

Within 30 calendar days after contract award and updated as required

TM, COR

CLIN 0001 –

A010

Contractor's

QCP

Submitted in Microsoft Word format by electronic submission. Contractor’s format and content is acceptable.

At proposal submission with applicable updates made throughout performance

COR, CO

CLIN 0001 –

A010

Corrective Action Plans

Submitted in Microsoft Word format by electronic submission. Contractor’s format is acceptable.

(Reference RFIMS Quality Assurance Surveillance Plan (QASP)).

As-Required per QASP criteria.

COR, CO

CLIN 0001 –

A011

Risk Register Submitted in Microsoft Excel format by electronic submission. Contractor’s format and content is acceptable.

Minimum of every 30 calendar days through the POP or more frequently if required

TM, COR

CLIN 0001 –

A012

Integrated Master Schedule

Submitted in Microsoft Project or PDF format by electronic submission.

Format and content per: DI-MGMT-81650.

Contract award + updates every 30 calendar days

TM, COR

CLIN 0001 Medium-fidelity Prototype

Detection, classification, identification, and notification capability proof of concept validation through the Contractor performing active research and development with analytical and laboratory studies.

270 calendar days after contract award

TM, COR

CLIN 1001 High-fidelity Prototype

Detection, classification, identification, and notification capability demonstration through testing of prototyping in representative earth station environment. The Contractor must integrate technology elements with reasonably realistic supporting elements.

180 calendar days after contract option award

Reference and

CDRL

Deliverable Format and Medium Submission

Frequency Receiving

Official

CLIN 1001 –

A013

Configuration Management Plan

Submitted in Microsoft Word format by electronic submission.

Format and content per: DI-CMAN-80858B.

(Reference MIL-HDBK-61A).

Within 30 calendar days after contract award and updates as required

TM, COR

CLIN 1001 –

A014

Configuration Item Identification List

Submitted in Microsoft Word format by electronic submission.

Format and content per: DI-CMAN-80858B (Reference MIL-HDBK-61A).

Initial: Ten business days prior to System PDR Final: Ten business days prior to System CDR

TM, COR

CLIN 0001 –

A015

Change Requests, Deviations, and Waivers

Submitted in Microsoft Word format by electronic submission.

Format and content per: DI-CMAN-80858B.

(Reference MIL-HDBK-61A, 6.3)

As generated TM, COR

CLIN 1001 –

A016

System Document Tree

Submitted in Microsoft Word format by electronic submission.

Format and content per: DI-IPSC-81432.

Initial: Ten business days prior to System PDR Final: Ten business days prior to System CDR

A017

System Drawing Tree

Submitted in Microsoft Visio or Portable Document Format (PDF) by electronic submission.

Format and content per: DI-IPSC-81432.

Initial: Ten business days prior to System PDR Final: Ten business days prior to System CDR

A018

System Specification Tree

Submitted in Microsoft Word format by electronic submission.

Format and content per: DI-IPSC-81432.

Initial: Ten business days prior to System PDR Final: Ten business days prior to System CDR

TM, COR

CLIN 0001 –

A018

IBR Data Package and Meeting

Submitted in Microsoft Word format by electronic submission.

Format and content per: See SOO Section 15.

Ten business days prior to IBR

TM, COR

CLIN 0001

A019

System Engineering Management Plan

Submitted in Microsoft Word format by electronic submission Format and content per:

http://www.acqnotes.com/acqnote/careerfiel ds/systems-engineering-management-plan-semp

Within 30 calendar days after contract award and updates as required

TM, COR

CLIN 0001

A020

Operational Concept Document

Submitted in Microsoft Word format by electronic submission.

Format and content per: Project Performance International PPA-000950-10.

Initial: Prior to SRR Final: Prior to PDR

TM, COR

CLIN 0001 –

A021

System Requirements Specification/ Document

Submitted in Microsoft Word format by electronic submission.

Format and content per: Project Performance International PPA-002235-9.

Initial: Prior to SRR Final: Prior to PDR

TM, COR

CLIN 0001 –

A022

SRR Package and Meeting

Technical review materials and coordination of meeting. Contractor’s format and content is acceptable.

Ten business days prior to SRR

TM, COR

http://www.acqnotes.com/acqnote/careerfields/systems-engineering-management-plan-semp http://www.acqnotes.com/acqnote/careerfields/systems-engineering-management-plan-semp http://www.acqnotes.com/acqnote/careerfields/systems-engineering-management-plan-semp

Reference and

CDRL

Deliverable Format and Medium Submission

Frequency Receiving

Official

CLIN 0001 –

A023

ASR Package and Meeting

Technical review materials and coordination of meeting. Contractor’s format and content is acceptable.

Ten business days prior to ASR

TM, COR

CLIN 1001 –

A024

System Design Description/ Document

Submitted in Microsoft Word format by electronic submission.

Format and content per: DI-IPSC-81432A.

Initial: Prior to PDR Final: Prior to CDR

A025

PDR Package and Meeting

Technical review materials and coordination of meeting. Contractor’s format and content is acceptable.

Ten business days prior to PDR

A026

CDR Package and Meeting

Technical review materials and coordination of meeting. Contractor’s format and content is acceptable.

Ten business days prior to CDR

A027

System Security Plan

Submitted in Microsoft Word format by electronic submission.

Format and content per: Contract Section H Special Provision and NIST Special Publication 800-18 Rev 1.

TBP by the contractor TM, COR

A028

System Integration and Test Plan

Submitted in Microsoft Word format by electronic submission.

Contractor’s format and content is acceptable.

TBP by the contractor TM, COR

A029

Detailed Test Plan(s) and Procedures

Submitted in Microsoft Word format by electronic submission. Contractor’s format and content is acceptable.

Initial: 60 calendar days prior to testing Final: Ten business days prior to testing

TM, COR

CLIN 2001

A030

TRR Package and Meeting

Technical review materials and coordination of meeting. Format and content per DI-

IPSC-81439A.

Ten business days prior to TRR

TM, COR

CLIN 1001 –

A031

Post-Test Data Packages

Submitted in Microsoft Word format by electronic submission. Contractor’s format and content is acceptable.

Ten business days after completion of testing

TM, COR

CLIN 1001 –

A032

Operational Readiness Review Package and Meeting

Technical review materials and coordination of meeting. Contractor’s format and content is acceptable.

Ten business days prior to ORR

TM, COR

CLIN 2001-

A033

System Installation Plan

Submitted in Microsoft Word format by electronic submission. Contractor’s format and content is acceptable.

Initial: Fifteen business days after CDR Final: 90 calendar days after CDR

Reference and

CDRL

Deliverable Format and Medium Submission

Frequency Receiving

Official

CLIN 2001-

Initial Operating Capability

Demonstration showing that each system can meet minimum operational capabilities at a designated earth station

A TBP number of days after the Government provides approval to proceed with production

TM, COR

CLIN 2001-

A034

System Transition and Operations Support Plan

Submitted in Microsoft Word format by electronic submission. Contractor’s format and content is acceptable.

Initial: Fifteen business days after CDR Final: 90 calendar days after CDR

TM, COR

CLIN 2001-

A035

System Operations and Maintenance Manuals

Submitted in Microsoft Word format by electronic submission. Contractor’s format and content is acceptable.

TBP by the contractor TM, COR

CLIN 2001-

A036

System Operations and Maintenance Procedures

Submitted in Microsoft Word format by electronic submission. Contractor’s format and content is acceptable.

TBP by the contractor TM, COR

CLIN 2001-

A037

System Maintenance Plan

Submitted in Microsoft Word format by electronic submission. Contractor’s format and content is acceptable.

TBP by the contractor TM, COR

CLIN 2001-

2004 Full Operating

Capability Demonstration showing the system can meet minimum operational capabilities at a designated earth station

TBP by the contractor TM, COR

CLIN 2001-

A039

Technical Data Package

Submitted in Microsoft Word format by electronic submission.

Format and content per: DI-SESS-80776A

Upon final system acceptance

TM, COR

CLIN 2001-

A040

SAR Package and Meeting

Technical review materials and coordination of meeting. Contractor’s format and content is acceptable.

Ten business days prior to SAR

TM, COR

CLIN 2001-

A041

Technical Manuals

Submitted in Microsoft Word format by electronic submission. Format and content per MIL-STD-38784.

Development/Production Phase

TM, COR

CLIN 2001-

A042

User Manuals Submitted in Microsoft Word format by electronic submission. Contractor’s format and content is acceptable.

Development Production Phase

TM, COR

CLIN 2001-

A043

System Training Plan

Submitted in Microsoft Word format by electronic submission. Contractor’s format and content is acceptable.

Development/Integration Phase

TM, COR

CLIN 2001-

A044

System Training Class and Materials

Technical and operational training materials and coordination of training session.

Contractor’s format and content is acceptable.

Development/Integration Phase

TM, COR

CLIN 2001-

A045

Equipment Sparing Policy

Submitted in Microsoft Word format by electronic submission. Contractor’s format and content is acceptable.

Development/Integration Phase

Reference and

CDRL

Deliverable Format and Medium Submission

Frequency Receiving

Official

CLIN 2001-

A046

Spares/Repair Parts TBD

Development/Integration Phase

TM, COR

CLIN 0001 –

A047

Trip Report Submitted in Microsoft Word format by electronic submission. Contractor’s format and content is acceptable.

Within five business days of trip end

COR, CO

9 Period of Performance NOAA desires protection at designated earth stations by April 2018, but is unsure if this objective is possible due to the anticipated technical complexity in developing the RFIMS. However, the Government encourages prospective bidders to implement a solution based on a schedule that enables NOAA to monitor federal earth stations by the April 2018 transition deadline. Table 4 identifies the maximum period of performance (POP) for each of the CLINs included in this contract.

Table 4: Total POP for all CLINs = 60 Months

CLIN/ Sub-CLIN CLIN/Sub-CLIN Description Duration

CLIN 0001 Concept Exploration (Phase I)

• Simulation (e.g., MATLAB)

• Medium-fidelity Prototype Development, Test, and Evaluation

Nine (9) Months

CLIN 1001 (Option) Demonstration (Phase II)

• High-fidelity Prototype Development (not to exceed five months)

• High-fidelity Prototype Test and Evaluation

Six (6) Months

CLIN 2001-2004 (Option) Installation and Deployment (Phase III)

• Produce

• Deploy

• Install, Integrate, and Test

Twenty-four (24) Months

CLIN 3001 (Option) Operations, Maintenance, and Sustainment

• Corrective Maintenance

• Adaptive Maintenance

• Preventative Maintenance

Twelve (12) Months

CLIN 3002 (Option) Operations, Maintenance, and Sustainment

• Corrective Maintenance

• Adaptive Maintenance

• Preventative Maintenance

Nine (9) Months

CLIN 4001 (Option) Installation and Deployment Phase for up to 18 DOD Sites

• Produce

• Deploy

• Install, Integrate, and Test

CLIN/ Sub-CLIN CLIN/Sub-CLIN Description Duration

CLIN 5001 (Option) Installation and Deployment Phase for up to five DOI Sites

• Produce

• Deploy

• Install, Integrate, and Test

10 Place of Performance The primary place of performance for the development effort will be at the contractor’s facility. The place of performance for integration and installation will be at NOAA facilities or for optional RFIMS installations at DOD and DOI facilities for optional RFIMS installations. The COR will coordinate access to Government installations with the host facility’s designated point of contact and security office. The contractor is required to submit a deployment schedule that will allow for pre-coordination (i.e., two weeks in advance of the scheduled date) for site access to Government facilities and equipment.

11 Travel Travel is required for this contract. Travel requirements will include monthly project and progress reviews, onsite at NOAA offices in Silver Spring, MD, and at the Government’s election at the contractor’s facility. Any travel will be on a not-to-exceed basis and reimbursed in accordance with the limitations imposed under Federal Travel Regulations. The contractor will undertake travel required to develop and implement the RFIMS. During system development, the contractor may be required to travel to earth station locations to perform surveys, measurement, testing, installation, or optimization.

Table 5 identifies the NOAA earth station locations that…