AMD 2 Att 1 POES EL SOW 5.6.22.pdf

PDF 341 KB Posted

Attached to
Polar Operational Environmental Satellites (POES) Extended Life (EL) Operations Support
Solicitation number
1332KP22BNEEB0001
Issued by

About this file

This statement of work outlines requirements for the Polar Operational Environmental Satellites (POES) Extended Life Operations Support contract. The contractor shall provide a Ground System as a Service capability to assume on-orbit operations responsibilities for the NOAA-15, NOAA-18, and NOAA-19 satellites. Specific requirements include transitioning operations from the government's ground system to the contractor's commercial system within 182 days, operating the satellites 9x5 including command, control and data downlink functions, and meeting IT security certification standards. The contractor must also maintain COMSEC equipment, develop required documentation such as a mission operations transition plan, and submit quarterly project status reports. The National Oceanic and Atmospheric Administration is seeking these services to continue collecting science data from the POES constellation in a more cost-effective manner.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

NATIONAL OCEANIC AND ATMOSPHERIC ADMINISTRATION (NOAA)

STATEMENT OF WORK (SOW) FOR THE POLAR OPERATIONAL

ENVIRONMENTAL SATELLITES (POES) EXTENDED LIFE (EL)

OPERATIONS SUPPORT

1. GENERAL

NOAA’s POES satellite system is the secondary data source complementing the flagship Joint Polar

Satellite System (JPSS) Mission, which operates out of a different ground system and is the primary data source for NOAA Low Earth Orbiting (LEO) observations. Data from the POES series supports a broad range of environmental monitoring applications including weather analysis and forecasting, climate research and prediction, global sea surface temperature measurements, atmospheric soundings of temperature and humidity, ocean dynamics research, volcanic eruption monitoring, forest fire detection, global vegetation analysis, search and rescue, and many other applications. NOAA’s strategic expectations in supporting its federal, domestic and international partners requires the continuation of science collection from these observatories, while at a reduced operations cost.

NOAA requires the continuation of the POES satellite system, and seeks to migrate its core Command, Control and Communications (C3S) Capabilities to a Contractor-provided Ground System. The purpose of this SOW is to accomplish this migration and to demonstrate the concept of operating Government owned meteorological satellites by means of a Ground System as a Service (GSaaS) capability.

1.1. BACKGROUND

NOAA’s Polar Operational Environmental Satellites (POES) satellite system offers the advantage of daily global coverage, by making polar orbits nearly 14 times per day approximately 520 miles above the surface of the Earth. The orbits are circular, with an altitude between 830km morning orbit and 870km afternoon orbit and are sun synchronous. The Earth's rotation allows the satellite to see a different view with each orbit, and each satellite provides two complete views of weather around the world each day.

Currently, NOAA operates three POES satellites - NOAA-15, NOAA-18, and NOAA-19, all of which are out of propellant and cannot perform propellant based maneuvers. Status on the current operations of the

NOAA POES Satellites as well as orbital characteristics can be further found at the following URL:

https://www.ospo.noaa.gov/Operations/POES/status.html

Current POES operations capabilities utilize a single northern hemisphere downlink per orbit. The

Government ground stations at Fairbanks, Alaska, and Wallops Island, Virginia, support communication with the observatories over either L-Band or S-Band for the downlink of observatory science data as well as command and control. The satellites perform a secondary service with the transmission of real-time imager and sounder data to the international user community. Use of either S-Band or L-Band can facilitate downlink of POES Mission Data, yet Mission Operations requires the continual Direct Readout

Services (e.g., bent-pipe) downlink of Using L-Band, High Resolution Picture Transmission (HRPT) is continually broadcast to the Direct Readout community. Further information on the POES Direct Readout

Services utilized by the POES GS can be found at the following URL:

https://noaasis.noaa.gov/POLAR/HRPT/hrpt.html

The POES instruments include the Advanced Very High Resolution Radiometer (AVHRR) instrument and the Advanced TIROS Operational Vertical Sounder (ATOVS) suite. The EUMETSAT-provided

Microwave Humidity Sounder (MHS) instrument completes the ATOVS suite. The AVHRR/ATOVS https://www.ospo.noaa.gov/Operations/POES/status.html https://noaasis.noaa.gov/POLAR/HRPT/hrpt.html provides visible, infrared, and microwave data which is used for a variety of applications such as cloud and precipitation monitoring, determination of surface properties, and humidity profiles.

The NOAA POES observatories are the secondary best-effort data source complementing the flagship

Joint Polar Satellite System (JPSS) Mission which operates out of a different ground system and is the primary data source for NOAA Low Earth Orbiting (LEO) observations. Data from the POES series supports a broad range of environmental monitoring applications including weather analysis and forecasting, climate research and prediction, global sea surface temperature measurements, atmospheric soundings of temperature and humidity, ocean dynamics research, volcanic eruption monitoring, forest fire detection, global vegetation analysis, search and rescue, and many other applications. NOAA strategic expectations in supporting its federal, domestic and international partners requires the continuation of science collection from these observatories, while at a reduced operations cost.

Further information for NOAA-15 can be found at:

https://www.cpc.ncep.noaa.gov/products/stratosphere/strat_a_f/NOAA-K.pdf

Further Information for NOAA-18 can be found at:

https://www.cpc.ncep.noaa.gov/products/stratosphere/strat_a_f/NOAA-N.pdf

Further information for NOAA-19 can be found at:

https://www.cpc.ncep.noaa.gov/products/stratosphere/strat_a_f/NOAA-N_Prime.pdf

A.1.1 Terms and Definitions

A.1.2. Terms

● “Observatory” refers to the spacecraft bus fully or partially integrated with one or more flight instruments.

● “GSaaS” and “Commercial Ground System” indicate an existing ground system capability offered as a Service with the provider covering all Service maintenance, sustainment or upgrades.

The offered Service includes both the Command and Control capabilities, as well as apertures providing Ground Entry Points.

● “Mission Operations Readiness” indicates a series of End-to-End System Tests and Mission

Rehearsals to demonstrate that the Ground System and Operations Personnel are ready to provide

Operations Support.

● “Shadow Operations” indicates a period of time where the vendor-provided Ground System and

Operators are accepting and processing telemetry from the Observatory, creating products and simulating the transmission of commands.

● “Parallel Operations” indicates a period of time where both the legacy and vendor-provided

Ground System and Operators are accepting and processing telemetry and operating and producing products from the Observatory simultaneously in a coordinated manner..

A.1.3 Definitions

● Shall – Compliance by the Contractor is mandatory. Any deviations from these contractually imposed mandatory requirements require the approval of the Contracting Officer.

● Will – Designates the intent of the Government.

● Days – Means calendar days unless otherwise noted in its use.

● DACA - Days After Contract Award

A.1.4 Applicable Documents

The Documents listed in this section apply directly to the performance of the NOAA POES Extended

Life. These documents establish detailed specifications, requirements, and interface information necessary for the performance of the contract. Unless otherwise specified, the document version listed herein shall apply. Any technical specifications or interface documents developed as part of the scope of https://www.cpc.ncep.noaa.gov/products/stratosphere/strat_a_f/NOAA-K.pdf https://www.cpc.ncep.noaa.gov/products/stratosphere/strat_a_f/NOAA-N.pdf https://www.cpc.ncep.noaa.gov/products/stratosphere/strat_a_f/NOAA-N_Prime.pdf this contract are also considered applicable documents. Any inconsistency in other documents, exhibits, and attachments shall be resolved by giving precedence in the following order:

● NOAA N-PRIME Satellite to Ground Interface Control Document (IS23033284)

● PACS TELEMETRY AND COMMAND DATABASE INTERFACE CONTROL DOCUMENT

(IJPS-CSU-0036)

● NOAA N-PRIME COMSEC Security Plan

● NIST FIPS PUB 140-2 Security Requirements for Cryptographic Modules

A.1.5 Reference Documents

These documents contain information that may be useful in enhancing the understanding of the work required by this SOW.

● Polar Operational Environmental Satellites (POES) Office of Satellite Operations (OSO) Concept of Operations in the Initial Joint Polar-orbiting Operational Satellite System (IJPS) Era

(ML008910-NOAA-POES IJPS OSO)

● Polar-Orbiting Operational Environmental System Concept of Operations (ML007949-NOAA-

POES KLM OSO)

2.0 SPECIFIC REQUIREMENTS/TASKS

The Contractor shall provide a GSaaS capability, in the form of engineering services and information technology (IT) functionality, to assume on-orbit operations responsibilities for the NOAA-15, NOAA-

18, and NOAA-19 observatories.

The Contractor shall be able to perform all services identified within this SOW remotely without the need for Contractor personnel being on-site at Government facilities. Contractor access to Government facilities is acceptable on a limited basis, especially in support of initial POES Operations Transition activities as required. Contractor access to Government Facilities shall be coordinated in advance with the

COR. All Contractors, both long-term and short-term, entering Government Facilities must have valid picture identification. Personnel on this task will not have local or network access to any non-public

Department of Commerce Information Technology resources. All Contractors shall be escorted at all times.

TASK 1. POES OPERATIONS TRANSITION

In performing the transition of POES Operations from the Government operated POES Ground System to

Contractors Commercial Ground System, the Contractor shall:

1. Accomplish all mission operations readiness, shadow operations and parallel operations activities necessary to independently operate the NOAA-15, NOAA-18, and NOAA-19 observatories as well as training any contractor provided operations staff no later than 182 Days after the start date of the contract. Such activities include, but are not limited to:

a. Provide Task Management Support for all activities pertaining to NOAA POES Extended

Life Transition work. This includes the management and oversight of all activities performed by contractor personnel, including subcontractors, to satisfy the requirements identified in this contract. Such activities also include, but are not limited to, cost, schedule and risk management as well as status reporting.

i. The Contractor shall develop a Quarterly Project Status Review Package to the specifications identified in Section 3.0 CDRL.

b. Schedule, coordinate, and host a Project Kick-Off Meeting at any location approved by the

Government within 7 days of contract award. The meeting shall provide an introduction between the Contractor personnel and Government personnel who will be involved with the contract. The Project Kick-Off Meeting shall provide the opportunity to discuss technical, management, and security issues, and travel authorization and reporting procedures.

c. Develop and deliver a Mission Operations Transition Plan, specifications identified in

Section 3.0 CDRL, detailing the approach to performing an operations transition from the

Government’s Legacy functionality to the Contractor’s commercial ground system no later than 60 Days post Contract Award..

d. Migrate and incorporate the POES Command and Telemetry (C&T) Databases into the commercial ground system

e. Incorporate POES COMSEC within the Contractors commercial ground system along with the ability to send valid COMSEC Encrypted commands to the NOAA POES observatories. Further information detailed in Section 2.2 TASK 2. POES

COMMERCIAL GROUND SYSTEM.

f. Migrate existing POES Command Procedures (Proc’s) to a Vendor Provided Solution, as required.

g. Develop valid On-Board Table Loads used to facilitate contact scheduling and science data collection of the NOAA POES observatories in accordance with the NOAA N-PRIME

Satellite to Ground Interface Control Document

h. Develop and validate the following which includes, but is not limited to command procedures, scripts, display pages, plots, Standard Operating Procedures (SOPs), contingency operating procedures, observatory planning rules/constraints, used to operate the integrated mission system.

i. Validate all Operations Products in an operations-like environment utilizing the highest fidelity simulator available and/or as otherwise approved by the Government during the

Project Kick-Off Meeting.

j. Produce operations readiness artifacts for each developed operations product for

Government Evaluation, prior to initial use with a POES Observatory, or as otherwise identified by the Government.

k. Implement the commercial ground system using the IT Security processes described below in Task 2 item 2.3. Deliver IT security documentation, including the Service Level

Agreement (SLA, CDRL 3), Information Security Agreement (ISA, CDRL 4), and

Interface Control Document (ICD, CDRL 5).

l. Attend and complete comprehensive observatory training detailing the specifics of how to operate and maintain the POES observatories prior to the start of a POES shadow operations on the Contractor’s ground system. The Government will lead all observatory training activities associated with the Contractor’s operations personnel and will provide all relevant observatory design information to the Contractor. Throughout the Government

Training process, the Government shall encourage active collaboration and discussion on how to best streamline the training to reflect the Contractor’s provided solution..

TASK 2. POES COMMERCIAL GROUND SYSTEM

In assuming responsibility of the POES Commercial Ground System, the Contractor shall:

1. Support the configuration, delivery, and maintenance of a Commercial Ground System capable of supporting operations independently of the Government's ground system functionality. The

Contractor shall provide its approach for supporting the configuration, delivery, as well as ongoing operations and maintenance (O&M) of a Commercial Ground System as a part of the

Project Kick-off Presentation.

a. Perform the primary functions of a Command, Control and Communications System

(C3S), which includes Command and Control, Mission Planning and Scheduling, Trending and Analysis, Flight Dynamics as well as Ground Station Radio Frequency functionality.

b. Support configuration management of the commercial ground system, operations products, and delivered items, including but not limited to flight software, simulators, Telemetry and Command (T&C) databases, and all other contractor deliverables per the

CDRL.

c. Capture and provide collected Science Mission Data (SMD) from the NOAA-15, NOAA-

18, and NOAA-19 observatories and deliver it to a Contractor-owned Commercial Cloud

Based Object Store for Government to access and fetch the data in order to perform science processing.

d. Maintain the following minimum operational service level requirements within the

Contractor’s commercial ground system when facilitating POES Operations. At a minimum, the Contractor shall:

i. Perform Health and Safety Contacts with each POES Observatory.

1. Perform both Encrypted and Clear-Mode Commanding to the POES

Observatories, including:

a. Perform Encrypted Commanding within every 8 hours to the

POES Observatories

b. Perform a Data Authentication Unit (DAU) Reset at the beginning of every contact to rotate and verify the DAUs on the

POES Observatories.

c. Perform On-Board Clock updates at regular intervals (e.g. Daily)

d. Perform Commanding to both the Control and Non-Control

Sides of the On-Board Processor (OBP)

e. Perform Generation and Uploads of Stored Table Load’s

(STDCMD) and Ephemeris Load’s (EPHEM)

f. Perform Validation of any Commands and or Load’s prior to use on a POES Observatory

2. Perform Telemetry Decommutation and Analysis of the POES

Observatories, including but not limited to:

a. On-board Clock Drift and Error Messages

b. Gyro Drift and Errors

c. Microwave Humidity Sounder (MHS) Instrument(s)

d. MHS Interface Unit (MIU)

e. Advanced Microwave Sounding Unit (AMSU) Instrument(s)

f. Advanced Very High Resolution Radiometer (AVHRR) Instrument(s)

g. Solar Backscatter Ultraviolet Radiometer (SBUV)

Instrument(s)

h. Space Environment Monitor (SEM) Instrument(s)

3. Perform Decommutation and Analysis of special TIROS Information

Processor (TIP) and DWELL Real-Time Telemetry

4. Perform Telemetry Decommutation and Analysis of embedded and ancillary numonics and or metadata within Downlinked High Resolution

Picture Transmission (HRPT), Stored AMSU Information Processor

(SAIP), Stored TIROS Information Processor (STIP) and Global Area

Coverage (GAC) data products. Processing of Science Data or Images is not required or expected for these data products by the commercial ground system.

5. Monitor, Update, Compare and Maintain an Spacecraft State Table for each POES Observatories

6. Monitor and Command the POES Observatories into TIP, DWELL

Modes

ii. Perform Recorder Management of the POES Observatories

1. Perform data accountability and data quality assessments between files on the recorder and those successfully downlinked

iii. Maintain continuous High Resolution Picture Transmission (HRPT) downlink for all POES Observatories.

iv. Perform a SMD Downlink once an orbit (~120 Minutes) for each POES

Observatory. Specific SMD format types include, but are not limited to:

1. GAC (Global Area Coverage)

2. High Resolution Picture Transmission (HRPT)

3. TIP (TIROS Information Processor)

4. STIP (Stored TIROS Information Processor)

5. SAIP (Stored AMSU Information Processor)

v. Provide SMD to the Government within 13 minutes of receipt on the ground within an Cloud Based Object Store.

1. Indefinitely Store for the life of the contract all downlinked SMD data in the Contractor-owned Cloud Based Object Store

2. Attempt re-transmit of SMD after an unsuccessful downlink

e. The Government will allow the Contractor to leverage the following functionality as

Government Furnished Property and Expertise upon request:

● Property:

o Existing POES Observatory Simulators, Table Loads, Products, Command and Telemetry Databases or Command Procedures o POES Observatory Telemetry Archive Data o POES Observatory and Ground System Documentation and

Configurations o NIST FIPS 140-2 Compliant KIT-223 Ground COMSEC Encryptors and

COMSEC Key Material

● Expertise:

o Government Observatory & Instrument Subject Matter Experts (SME)

2. Protect cryptographic equipment and key material in accordance with applicable policies including but not limited to Government furnished Communications Security (COMSEC) material and devices to support operations of the NOAA POES Observatories and the applicable

COMSEC Security Plan (CSP) and Key Management Plan (KMP) documentation for NOAA

POES Observatories. Specifically, the Government will provide FIPS 140-2 Compliant KIT-223

Ground Units that will need to be interfaced via RS-232 and/or RS-422 connections to the

Contractor. Additionally, the Contractor shall:

a. As part of the Mission Operations Transition Plan, describe the implementation of the transition of the COMSEC Security Boundary and Material to a Contractor Furnished

COMSEC Account, while avoiding or minimizing interruptions to ongoing POES

Operations.

b. Provide a review of the Contractor implemented COMSEC security controls by the

Government prior to the delivery of any cryptographic equipment and key material.

c. Resolve any discrepancies identified by the Government in review of the Contractor’s implemented solution prior to the delivery of any cryptographic equipment and key material.

3. Meet adequate IT security requirements for the provision of a Commercial Ground System.

Specific IT Security Requirements acceptable to the Government can be third party certifications under a recognized IT security standard such as International Organization for Standardization and the International Electrotechnical Commission (ISO/IEC) 27001 and/or US National Institute of Standards and Technology (NIST) 800-53 rev. 5

(https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final) and or other applicable security certifications as appropriate. The Contractor shall justify their choices and approach via the IT

Security deliverables identified below of which are detailed within Section 3.0 CDRL.

a. The Contractor shall ensure that:

i. The certification chosen and auditing/validation process proposed meets Federal cyber security standards as described in the Federal Information Security

Management Act of 2002 (FISMA).

1. https://csrc.nist.gov/projects/risk-management/fisma-background

ii. The use of non-US-based assets, if any, shall be secured and shall protect U.S.

National and NOAA interests as it pertains to POES Life Extension. Secure use of non-US persons, if any, must also be addressed to ensure protection of U.S.

National and NOAA interests as it pertains to POES Life Extension.

iii. Software Supply Chain Security shall be achieved as mandated by the Executive

Order on Improving the Nation’s Cybersecurity, dated May 12, 2021 and described in Section 4. Enhancing Software Supply Chain Security. The

Contractor shall describe how they maintain supply chain security.

1. https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-on-improving-the-nations-cybersecurity/

iv. In order for the Government to monitor IT security status, the current certification package for the Contractor’s security certification shall be provided to the Government upon demand within a reasonable timeframe of request.

Within the certification package the Contractor needs to define and justify two timeframes: (1) delivery of initial package after award; (2) delivery of ad hoc, on https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final https://csrc.nist.gov/projects/risk-management/fisma-background https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-on-improving-the-nations-cybersecurity/ https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-on-improving-the-nations-cybersecurity/ https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-on-improving-the-nations-cybersecurity/ demand copies in response to the Government’s need for visibility for monitoring purposes.

v. That they are specific with regards to their planned IT Security implementation for the commercially provided solution and shall not simply offer the

Government a menu of tools and options to choose.

b. Document and justify its Commercial Ground Systems service levels as it pertains to availability, integrity and confidentiality in an IT Security Service Level Agreement

(SLA). Reference Section 3.0 CDRL section below for further details.

c. Develop, in coordination with the Government, an Information Security Agreement (ISA) detailing the security of any interconnectivity between the commercial ground system and the Government. Reference Section 3.0 CDRL section below for further details. At minimum interfaces with the Government will include, but are not limited to:

i. Mission Data Accessibility to the Government's Science Data Processing System

ii. Remote Access to telemetry and housekeeping data from the POES

Observatories for purposes of Surveillance and Flight Engineering Support by the

Government

d. Develop, in coordination with the Government, an Interface Control Document (ICD) detailing the technical interfaces provided by the commercial ground system to the

Government. Reference Section 3.0 CDRL section below for further details. At minimum, interfaces with the Government shall include:

i. Mission Data Accessibility to the Government's Science Data Processing System

ii. Remote Access to telemetry and housekeeping data from the POES

Observatories for purposes of Surveillance and Flight Engineering Support by the

Government

e. Ensure the Contractor’s commercial ground system shall not reside within the

Government FISMA boundary; however, the Contractor shall be required to provide artifacts upon request from the Government’s ATO/SCA team to facilitate assessment of

Government/Contractor Interfaces

i. Support the security authorization process for Government FISMA systems that interface with the commercial ground system.

ii. Support the Government-sponsored team that maintains the Government's

FISMA system’s Authority to Operate (ATO) and performs an annual System

Controls Assessment (SCA) as it pertains to Government/Contractor Interfaces.

TASK 3. POES OPERATIONS

In assuming responsibility of ongoing POES mission operations, the Contractor shall:

1. Perform 9x5 on-orbit flight operations with automation, of the NOAA-15, NOAA-18, and

NOAA-19 observatories. This includes all activities necessary to maintain observatory health and safety, while maintaining ongoing science mission data collection.

2. Provide continuity for daily operations activities, and perform on-going monitoring & analysis, including back orbit limit checking, as well as configuration management, troubleshooting, performance reporting and trending, and operation of onboard POES observatory systems as well as the Contractor-provided commercial ground system. The Contractor shall work with the

Government to identify an appropriate method to convey the daily status of POES Operations.

The Contractor shall support the Government in mission support coordination meetings, as required.

3. Plan, rehearse, and execute all unique and non-routine activities such as attitude maneuvers, instrument calibrations, and anomaly recovery activities annually.

4. Conduct post event analysis for all unique and infrequent activities within 24 Hours of a completed flight activity.

5. Perform yearly proficiency tests of key ground system functionality, as well as proficiency tests with ground stations in order to validate routine and contingency procedures as well as system configuration and ensure proper training and certification of the flight operations staff.

6. Maintain and continuously execute the training and certification program after successful POES operations transition to the Contractor’s ground system.

7. Provide the Government remote access to the commercial ground system as required, to perform ongoing surveillance, anomaly resolution support, and/or to facilitate orderly transition of operations from the Governments legacy capabilities in association with TASK 1 - POES

OPERATIONS TRANSITION.

8. Submit for approval any changes to the Observatory configuration and/or elements or facilities within the flight operations domain (e.g. Observatory) to the Government prior to execution.

a. Specific changes that require approval include any non-nominal or contingency loads and or critical commanding

b. Exclusions to this approval process include nominal SMD Downlink, Health and Safety contact and recorder management commanding procedures, as well as communication and science observation Stored Table Load’s (STDCMD) and Ephemeris Load’s

(EPHEM).

9. Notify the Government of the execution of any POES Contingency procedures, On-Orbit

Anomalies, and or other irregular items (e.g. Limit Violations) within 30 Minutes of an identified event. The Contractor shall also include the Government in any POES Contingency and or

Anomaly activities once initially notified until successful remediation of the particular event.

3.0 Contract Data Requirements List (CDRL)

The Contractor shall provide all data and documentation deliverables in accordance with the Contract

Data Requirement List (CDRL) below. Unless otherwise agreed upon, all deliverables shall be submitted to the COR assigned to this contract.

MATURITY:

● Initial: The first submission of an item which shall be revised and resubmitted at a later date.

● Final: The complete, thorough submission of an item for approval, review, or information that, to the best of the contractor’s knowledge and intention, shall not require further revision or updates.

However, this does not preclude updating if later found to be necessary. Any updates shall require the same "approval/review" process as was required for the original submissions.

CATEGORY:

● A – Approval: CDRL items in this category require approval by the NOAA COR or Contracting

Officer prior to use by the contractor. Receipt by the Government shall occur within the time specified in the "Due Date" column. Requirements for re-submission shall be as specified by the

Contracting Officer. The Contractor shall resubmit the updated document within 14 calendar days of receiving comments from the Government. Acceptance shall be presumed unless otherwise indicated in writing by the Contracting Officer or the duly authorized representative within 30 days of receipt.

● I – Information: Data in this category shall be delivered to the Government within the time period specified in the “Due Date” column for the purpose of determining current program status, progress, and future planning requirements.

Item Due Date, Maturity Category

( A , I )

Quarterly Project Status Review Package

Quarterly

The first reporting period consists of the first full 3 months of performance plus any fractional part of the initial month. Thereafter, the reporting period shall consist of three full calendar months. The first report shall be due January 10, 2023.

Thereafter, reports shall be due on or before the 10th day following each reporting period.

I

Kick-Off Presentation Final - 7 DACA I

Service Level Agreement (SLA) Final - 60 DACA A

Information Security Agreement (ISA) Final - 60 DACA A

Interface Control Document (ICD) Final - 60 DACA A

Mission Operations Transition Plan Initial - Contract Award

Final - 60 DACA

I

A

Transition Out Plan Final - 90 days prior to end of contract A

1. Quarterly Project Status Review Package

This report shall include a description of the activities during the quarterly reporting period, and the activities planned for the ensuing reporting period. The first reporting period consists of the first three months of performance plus any fractional part of the later month. Thereafter, the reporting period shall consist of a nominal calendar year quarter. This report shall include, but is not limited to:

● Status of open issues and problems from prior reporting periods

● Status of Action Items; As Applicable

● Technical status for operational system and subsystem activities, including any subcontract technical performance

● Technical status of the POES Observatories

● Schedule detailing any transition and or development items, as applicable

● When applicable, current operations training and certification status

● Safety and Mission/Software assurance reports, including hazards status

● Business issues, including personnel changes

● Significant plans and activities for the following month

● Problems encountered during the reporting period, and anticipated approaches for resolution

(including, as appropriate, technical issues, manpower and staffing, supplier and subcontractor issues, etc.)

● Risk Status using the standard 5x5 report for each task order, including risk mitigations and burn-down plans

● Summary of Financial Reporting including explanation of variances and staffing issues.

2. Kick-Off Presentation

The Kick-Off Presentation shall be submitted 7 days after award. The Project Kickoff meeting materials shall provide an introduction between the Contractor and Government personnel involved with the activities of this Contract. The Project Kick-Off Meeting materials shall include technical & management overviews, identified security issues, travel authorization, as required, and reporting procedures. The

Project Kick-Off Meeting materials shall include the following:

● The Contractor’s approach to carry out the transition activities of Task 1, covering these topics at a minimum:

o Task management of the transition.

o Technical, management, and security risks and issues, and planned mitigation approach for any identified.

o Migration of the POES Command and Telemetry (C&T) databases and command procedures (Procs).

o Incorporation of POES COMSEC into the Contractor’s system.

o Development or adaptations, testing, and certification of command generation and table loads of each POES Observatory.

o Development and validation of all POES operations products, including approach to attain Government acceptance of the process and products.

o Contractor personnel training and qualification to operate the POES Observatories.

● The Contractor’s approach, as outlined in the proposal, to carry out Task 2 to execute the configuration, delivery, and maintenance of its Commercial Ground System.

● The Contractor’s approach, as outlined in the proposal, to carry out Task 3 to perform POES mission operations of the NOAA-15, NOAA-18, and NOAA-19 observatories.

● Travel authorization and reporting procedures.

3. Service Level Agreement (SLA)

The Contractor shall propose IT Security performance metrics as it pertains to availability, integrity and confidentiality. As this is a best value acquisition, the approach needs to balance cost with service level and performance. The Contractor shall justify their proposed service levels and performance metrics in a best value context.

The Contractor shall propose their own set of performance metrics. However, these metrics must include:

● NIST 800-53 rev. 5 Incident Response (IR) controls or their equivalent in ISO 27001 or other framework

● NIST 800-53 rev. 5 Supply Chain Risk Management (SR) controls or their equivalent in ISO

27001 or other framework

● Timeframe for the Contractor to respond to a Government request to view the IT security certification package

● Other metrics that the Contractor selects to demonstrate compliance with their chosen IT Security certification framework

4. Information Security Agreement (ISA)

The Contractor shall co-develop the ISA with the Government. The Government will provide a starting point template within ten days after the kickoff meeting and the ISA will be completed within 60 days of award. See the Secure Bidders Library Attachment “NESDIS_ISA_Template_v3_01-26-2017” for an ISA template that includes specific content requirements.

5. Interface Control Document (ICD)

The Contractor shall co-develop the ICD with the Government. The Government will provide a starting point template within ten days after the kickoff meeting and the ICD will be completed within 60 days of award. See the Secure Bidders Library Attachment “DRAFT – ICD_Template_v1_09022021 HD” for an

ICD template that includes specific content requirements.

6. Mission Operations Transition Plan

The Mission Operations Transition Plan shall define the approach and plan for achieving operational readiness and transitioning operations of the POES Constellation to the Contractor’s commercial ground system while not negatively affecting ongoing POES mission operations.

If the Contractor requires additional Government support for testing or shadow and/or parallel operations, the Contractor shall request this from the Government and include the applicable need within the Mission

Operations Transition Plan.

The Contractor shall provide its developed Validation, Rehearsal and Parallel/Shadow Operations procedures within the Mission Operations Transition Plan.

The Mission Operations Transition Plan shall include at a minimum:

• Implementation plan

• Transition Schedule

• Readiness reviews

• Regression test approach

• Transition readiness test approach

• Transition activities test procedures

• Post-test verification and validation

• Staff and operational readiness activities

4.0 Contract Payment Schedule

The Contractor shall invoice payments for TASK 1 - POES OPERATIONS TRANSITION, Labor Hours component, will be invoiced monthly until completion of the transition task. Any TASK 1 Invoicing shall be sent by the Contractor separate of any FFP invoicing.

The Contractor shall comply with the FFP payment schedule below for TASK 2 - POES COMMERCIAL

GROUND SYSTEM and TASK 3 - POES OPERATIONS.

Payment Milestone Payment

Project Kick-off Meeting Initial Payment for first 3 Months of Forecasted Work, Invoice submitted upon delivery of the Kick-Off Presentation CDRL

Quarterly Project Status Review (QPSR) Package

Quarterly Invoice for the specific Option Period, to occur every

3 months after the initial Project Kick-off Meeting; Invoice submitted upon delivery of the QPSR CDRL.

File details come from the government source that posted it. Updated .