Attachment 1-McMurdo PENGUIN Ground Stations Statement of Work.pdf

Doc No: PEN-ANT-SOW-001 Rev: 0.7.3 Date: 08.14.2026

PENGUIN Ground Stations | Statement of Work

Working Draft v0.7.3 – 103308142026 | Page 1

Statement of Work McMurdo PENGUIN Ground Stations

Receive-Only L-/S-/X-Band Ground Station Systems

Rev: 0.7.3 Draft Baseline Prepared by Alex Albadree

Document Number PEN-ANT-SOW-001 Revision 0.7.3 Document Type Working Draft Date 08.14.2026 Project PENGUIN Ground Stations Program/Context Office of Low Earth Orbit Observations / Near Earth Orbit Network Author Alex Albadree - Office of Low Earth Orbit Observations Primary Audience Antenna Vendor

Internal working draft prepared as the Rev 0.7.3 statement of work baseline for iterative development.

Note: This revision is intended to serve as the initial working baseline for development of a formal procurement statement of work for up to five receive-only L-/S-/X-band low Earth orbit antenna systems to be deployed at

McMurdo Station, Antarctica.

Working Draft v0.7.3 – 103308142026 | Page 2

McMurdo PENGUIN Ground Stations

Statement of Work

Review/Signature/Approval Page

Reviewed & verified by:

Name Role Signature Date Andrew W. Royle Chief Engineer Miguel Reyes LEO Penguin PM MR 05.22.2026 Nikolas D. Sinkola C3S Polar SME NDS 05.19.2026 William G. Munley Senior Advisor WGM 06/18/2026 Todd Schira NAaaS Penguin PM TS 09/04/2026 Deborah Carter NAaaS Program Support DC 09/04/2026 Mustafa Oktay NAaaS RF/Antenna SME MO 09/04/2026

Approved by

Released By:

Working Draft v0.7.3 – 103308142026 | Page 3

Document control note

This revision is intended to serve as the initial working baseline for development of a formal procurement statement of work for up to five receive-only L-/S-/X-band low Earth orbit antenna systems to be deployed at McMurdo Station, Antarctica. The document is structured to remain mission-driven and performance-based while leaving detailed implementation design to the contractor.

Document Change Record Revision Date Description of Changes Author

0.1 05.13.2026 Initial system-of-systems working backbone for internal planning AA

0.2 05.14.2026 Refocused SOW for antenna vendor material procurement only;

moved LGSS, NSF/ASC, and site integration roles to Government integration context

AA

0.3 05.19.2026 Added 3.4 Environmental Compatibility and Cold-Weather Design Disclosure

AA

0.4 05.19.2026 Updated antenna-vendor SOW language to clarify ASC management, RF/IFoF optional IFL scope, electrical/RF drawing deliverables, antenna material package elements, radome inclusion, FEP CCSDS VCID wording, included roadmap or limitations for adapting to future orbit element format changes, updated packaging standards and compliance with TL-MAN- 0002, and cargo-container/logistics considerations for USAP shipment flow.

AA/NDS

0.5 05.22.2026 Updated foundation interface treatment as GFI/design constraint;

added communication, primary contact, and contracting authority language; added delivery schedule to the controlled TBD/TBR list;

and strengthened TL-MAN-0002 USAP packing/shipping compliance language.

AA/MR

0.6 05.27.2026 Added radome RF performance disclosure language requiring antenna G/T performance basis, identification of whether G/T includes radome effects, and separate radome RF loss/insertion loss assumptions for applicable bands and polarizations.

AA

0.7 05.27.2026 Incorporated review comments to clarify EPS-Sterna L-band Stored Mission Data (SMD) reception; remove unnecessary acquisition-context language; update NSF/ASC wording to “currently performed by KBR”; simplify Port Hueneme delivery and site installation responsibility language; revise maintenance terminology from philosophy to requirements/approach;

strengthen spares language to require proposed and delivered spares/special tools for antenna, radome, and vendor-provided optional subsystems; add review-package CDRL concept for formal reviews; and identify proposal-response content and Appendix B as items to move to the solicitation/RFP package later.

Updated scheduler/propagator/contact planning capability from optional vendor feature to required part of the proposed antenna solution, while allowing implementation through native ACU capability, vendor software, integrated third-party software, or documented external interfaces.

AA/AWR

0.7.1 06.16.2026 Streamlined main-body SOW sections by moving detailed technical, interface, verification, logistics, training, spares, maintenance, and sustainment content into applicable CDRL/DID summaries; added and updated CDRL references throughout the

AA

Working Draft v0.7.3 – 103308142026 | Page 4

SOW body; and performed CDRL matrix and consistency cleanup.

0.7.2 06/18/2026 Incorporated WGM review comments addressing NEON mission wording, LGSS/NSF/ASC terminology, future X-band requirements language, radome/base-interface wording, Do Not Freeze packaging requirements, contact/NAaaS coordination notes, acronym cleanup, and minor grammar corrections; updated CDRL-018 to capture warm-storage and Do Not Freeze material handling requirements.

AA/WGM

0.7.3 08/14/2026 Added Sterna L-band mission baseline updates based on EUMETSAT response, including 1.707 GHz receive frequency,

3.6 MHz theoretical bandwidth, approximately ±45 kHz maximum

Doppler, no additional EPS-Sterna guard/filter/IF bandwidth requirement, and reference IF scheme of 720 MHz ±7.5 MHz.

Removed HKTM from the McMurdo Sterna language; updated antenna hardware baseline to reflect four-meter class reflector, feed support assembly, full-motion three-axis LEO tracking pedestal/positioner, and installed three-band feed system; added controlled TBDs for NOAA/NAaaS completion of S-band and X-band performance/interface requirements.

AA

0.7.4 09/16/2026 Clarified optional Sterna L-band FEP data-output requirements, including CADU generation as the EPS-Sterna baseline output from McMurdo to the Payload Data Processing (PDP) facility;

updated CDRL-009 and related acronyms.

AA

Working Draft v0.7.3 – 103308142026 | Page 5

Table of Contents

1.0 Introduction and Background

1.1 Purpose

1.2 Acquisition Context

1.3 Use of Terms

2.0 Scope of Work

2.1 Scope

2.2 Exclusions from Scope

3.0 Antenna and Radome System Description

3.1 Antenna System Material Package

3.2 Radome Package

3.3 Foundation and Mechanical Compatibility

3.4 Environmental Compatibility and Cold-Weather Design Disclosure

4.0 RF, IF, Frequency Conversion, and IFL Interface Requirements

4.1 Purpose of RF/IF Interface Definition

4.2 Required RF/IF Output Data

4.3 Frequency Conversion Disclosure

4.4 Downstream Compatibility Data

4.5 Optional Integrated IFL Transport Capability

4.6 IFL Interface Data When IFL Is Not Vendor-Provided

4.7 RF/IF, IFL, and Transport Scope Clarification

5.0 Antenna Control, M&C, Scheduler, and Cybersecurity Interfaces

5.1 Antenna Control Unit and Antenna M&C Interface

5.2 Scheduler / Propagator / Contact Planning Capability

5.3 Cybersecurity and Network Interface Data

6.0 Optional Sterna L-band FEP/Demodulator Capability

6.1 Optional Vendor-Proposed Sterna L-band FEP

6.2 FEP Mission Compatibility

6.3 FEP IF Input and Receive-Chain Compatibility

6.4 FEP Channelization and Redundancy

6.5 FEP Data Processing and Distribution

6.6 FEP M&C, Scheduler, Timing, and Network Interfaces

6.7 FEP Rack, Power, Cooling, and Maintainability

6.8 FEP Cybersecurity and Software Sustainment

6.9 FEP Verification Evidence

6.10 Third-Party or Government-Procured FEP Path

7.0 Government Integration Context

7.1 Purpose of Integration Context

7.2 Planned LGSS Role

7.3 Planned NSF/ASC Role

7.4 Planned Site Infrastructure Interfaces

7.5 Planned Downstream RF/IF, IFL, FEP, and Data Center Integration

Working Draft v0.7.3 – 103308142026 | Page 6

7.6 Support to Downstream Integration

7.7 Interface Ownership and Assumption Control

8.0 Factory Verification and Acceptance

8.1 Verification Approach

8.2 Factory Test Plan and Procedures

8.3 Factory Acceptance Testing

8.4 Interface Verification

8.5 Compliance Matrix

8.6 Factory Test Report

8.7 Pre-Shipment Review and Acceptance

8.8 Acceptance Limitations

9.0 Packaging, Delivery, and Logistics

9.1 Packaging Approach

9.2 Packaging Standards and Compliance

9.3 Packaging Protection Features

9.4 Transport Shock, Vibration, and Handling

9.5 Storage, Preservation, and Delayed Installation

9.6 Delivery Location and Logistics Handoff

9.7 Shipping Container and Staging Considerations

9.8 Packaging, Shipping, Storage, and Preservation Plan

10.0 Installation Support, Training, Spares, and Sustainment

10.1 Purpose of Installation and Sustainment Support

10.2 Installation Support Documentation

10.3 Installation Support Options

10.4 Site Checkout and Post-Installation Support Data

10.5 Training

10.6 Maintenance Requirements

10.7 Spares and Special Tools

10.8 Warranty and Support Process

10.9 Sustainment and Obsolescence Planning

11.0 Deliverables and CDRL Approach

11.1 CDRL Matrix/Deliverable

11.2 CDRL Data Item Description Summaries

11.2.1 CDRL-001 - Project Schedule

11.2.2 CDRL-002 - Monthly Status Report

11.2.3 CDRL-003 - Antenna/Radome Interface Control Document

11.2.4 CDRL-004 - Mechanical, Electrical, and RF Interface Drawings

11.2.5 CDRL-005 - RF/IF Output and Frequency Conversion Interface Document

11.2.6 CDRL-006 - Integrated IFL Option / IFL Interface Description

11.2.7 CDRL-007 - ACU and Antenna M&C Interface Document

11.2.8 CDRL-008 - Scheduler / Propagator / Contact Planning Capability Description

11.2.9 CDRL-009 - Optional Sterna L-band FEP Technical and Interface Data Package

11.2.10 CDRL-010 - Cybersecurity and Network Interface Description

11.2.11 CDRL-011 - Compliance Matrix

Working Draft v0.7.3 – 103308142026 | Page 7

11.2.12 CDRL-012 - Factory Test Plan / Procedures

11.2.13 CDRL-013 - Factory Test Report

11.2.14 CDRL-014 - Installation, Lifting, Handling, and Alignment Procedures

11.2.15 CDRL-015 - Operations and Maintenance (O&M) Manual

11.2.16 CDRL-016 - Training Materials

11.2.17 CDRL-017 - Spares, Warranty, and Sustainment Plan

11.2.18 CDRL-018 - Packaging, Shipping, Storage, and Preservation Plan

11.2.19 CDRL-019 - End Item/Pre-Shipment Data Package

11.2.20 CDRL-020 - As-Delivered Configuration Record

11.2.21 CDRL-021 - Environmental Compliance and Cold-Weather Design Disclosure

11.2.22 CDRL-022 - Review Packages and Briefing Materials

11.3 Vendor Response Expectations

12.0 Government-Furnished Information

13.0 Reviews, Meetings, and Reporting

15.0 Place of Performance, Delivery, and Travel

16.0 Communication and Primary Contacts

17.0 Acronyms and Definitions

Appendix A - Contractor’s Responsibility Summary

Working Draft v0.7.3 – 103308142026 | Page 8

1.0 Introduction and Background

Driven by the NOAA Satellite Observing System Architecture (NSOSA) study, the National Environmental Satellite, Data, and Information Service (NESDIS) established an enterprise planning framework to evaluate alternative architectures and plan for an operational environmental satellite system beginning in the late 2020s.

By leveraging a mix of satellite platforms and global partnerships, NESDIS ensures a resilient portfolio for NOAA's future space-based observations.

Within NESDIS, the Office of Low Earth Orbit (LEO) Observations maintains long-standing partnerships that support the acquisition, transport, processing, and distribution of environmental satellite data. These partnerships include cooperation with the European Organization for the Exploitation of Meteorological Satellites under the JPSS Program and are expected to expand to support the European Organization for the Exploitation of Meteorological Satellites (EUMETSAT) Polar System Second Generation (EPS-SG) constellation of microwave sounders.

Parallel to this sensing capability, the NESDIS Antenna as a Service (NAaaS) program represents the vision for a unified enterprise ground architecture. NAaaS modernizes data acquisition and transport through agile, multi-partner support, establishing a high-performance backbone for the entire observing system.

Together, LEO and NAaaS serve as the dual pillars of the NESDIS strategy. By integrating advanced sensing with a resilient ground network, NESDIS achieves a mission-effective and adaptable enterprise capable of managing the evolving rate of technological change.

McMurdo Station, Antarctica, provides a strategic high-latitude location for polar-orbiting satellite data acquisition. At approximately 77.8 degrees south latitude, McMurdo enables frequent access to polar-orbiting satellites and supports Stored Mission Data downlink opportunities for NOAA and partner mission satellites.

Additional receive-only ground station capability at McMurdo is required to maintain continuity, resiliency, and growth capability for NOAA environmental data acquisition architecture.

The receive-only antenna and radome systems procured under this effort are expected to support known near-term mission needs, including EPS-Sterna L-band data acquisition at McMurdo. The Sterna L-band mission baseline includes Stored Mission Data (SMD) reception. The delivered antenna system is expected to include installed L-, S-, and X-band receive hardware capability. NOAA/NAaaS will establish S-band and X-band performance and interface specifications to support future mission requirements; these parameters are identified in the procurement technical specification.

1.1 Purpose

The purpose of this Statement of Work (SOW) is to describe the procurement, fabrication, factory integration, verification, documentation, delivery, and installation-support documentation of receive-only antenna systems and associated radome systems for deployment at McMurdo Station, Antarctica.

This SOW defines the scope, deliverables, factory verification obligations, interface data obligations, optional capability offerings, delivery support, and sustainment support. Detailed technical performance requirements shall be provided in the applicable technical specification documents, interface control documents, drawings, and data deliverables referenced by this SOW.

1.2 Acquisition Context

This SOW is for the antenna provider only. The Contractor shall provide the antenna/radome material package and all associated technical data, interface definitions, verification evidence, and installation-support documentation required to enable Government-designated parties to install, integrate, test, and transition the systems at McMurdo Station.

Working Draft v0.7.3 – 103308142026 | Page 9

The Government currently plans to use Low Earth Orbit Ground Sustainment Services (LGSS), National Science Foundation (NSF), the NSF Antarctic Support Contract (ASC), and/or other Government-designated organizations to perform downstream site preparation, installation, data center rack integration, matrix switch integration, Front End Processor (FEP) integration, electrical and fiber tie-ins, and site acceptance activities under separate contractual or programmatic direction. This information is provided as integration context only and does not assign work to those organizations under this SOW.

1.3 Use of Terms

The term LGSS means Low Earth Orbit Ground Sustainment Services, a NOAA-awarded contract expected to support installation and integration activities when authorized by the Government. LGSS tasking is not assigned by this antenna vendor SOW.

The term NSF/ASC means the National Science Foundation and/or the Antarctic Support Contract currently performed by Leidos and expected in the future (FY27) to transition to Kellogg Brown & Root (KBR) responsible for McMurdo site and facility support activities as coordinated by the Government. NSF/ASC tasking is not assigned by this antenna vendor SOW.

2.0 Scope of Work

2.1 Scope

The Contractor shall provide up to five receive-only L-/S-/X-band antenna systems and associated radome systems for deployment at McMurdo Station, Antarctica.

1. Four-meter class reflector and feed support assembly.

2. Full-motion (LEO) satellite tracking pedestal or positioner with three-axis tracking capability.

3. Three-band feed system supporting installed L-, S-, and X-band receive capability.

4. Antenna-side RF/IF hardware, including feed, Line Noise Amplifiers (LNAs), filters, downconverters, and output interfaces as applicable to the selected design.

5. Optional integrated Intermediate Fiber Line (IFL) transport capability, including RF/IF-over-fiber

(RF/IFoF) equipment, if proposed.

6. Optional Front-End Processor (FEP) / demodulator capability for the Sterna L-band mission baseline, if proposed.

7. Scheduler, propagator, and contact planning capability or interface approach required to support antenna contact planning, pass execution, and antenna control system integration.

8. Factory integration and factory acceptance testing.

9. Interface control documentation.

10. Mechanical interface drawings and foundation compatibility data.

11. Electrical and RF drawings, including system block diagrams, signal-flow diagrams, power interface diagrams, and RF/IF interface diagrams.

12. RF/IF output definition, frequency conversion data, signal levels, and interface data.

13. Installation, lifting, handling, and maintenance documentation.

14. Training materials and training support.

15. Proposed spares, special tools, and sustainment planning information.

16. Warranty support.

17. Packaging, delivery, and pre-shipment data package.

The antenna systems shall support the Sterna L-band mission baseline for receive-only data acquisition at McMurdo. EPS-Sterna is the known near-term mission driver for the L-band procurement baseline; however, the acquisition shall not be limited to EPS-Sterna only. The Sterna L-band receive path shall support the Government-provided Sterna/AWS L-band mission baseline, including receive frequency, bandwidth, Doppler assumptions, polarization, modulation, coding, RF/IF output, and reference IF assumptions as defined in the applicable technical specification. NOAA/NAaaS will establish S-band and X-band

Working Draft v0.7.3 – 103308142026 | Page 10 performance and interface specifications to support future mission requirements; these parameters are identified in the procurement technical specification.

Data deliverables, interface documents, verification evidence, support documentation, and configuration records associated with the scope elements identified in this section shall be provided in accordance with Section 11.0 and the applicable Contract Data Requirements List (CDRLs).

2.2 Exclusions from Scope

Unless specifically added by the Government through the procurement action, the Contractor is not responsible for the following:

1. McMurdo site civil works.

2. Concrete foundation procurement or installation.

3. Site electrical infrastructure.

4. Site fiber infrastructure.

5. Data center rack infrastructure procurement.

6. Matrix switch procurement.

7. Facility power, breakers, outlets, or facility electrical work.

8. Network switch procurement or Government network integration.

9. Rack-level Power Distribution Units (PDUs), patch panels, RF cabling, network cabling, or internal data center rack cabling.

10. Physical installation of the antenna systems at McMurdo, except for vendor-provided installation support if requested and priced.

11. Site acceptance execution, except for vendor support if requested and priced.

12. LGSS contractual work.

13. NSF/ASC contractual work.

The Contractor shall provide the interface data and support documentation required to enable Government-designated parties to perform the excluded downstream installation and integration activities.

3.0 Antenna and Radome System Description

3.1 Antenna System Material Package

The Contractor shall provide a complete antenna system material package suitable for receive-only LEO satellite data acquisition at McMurdo Station. The antenna system material package shall include all vendor-provided hardware, software, firmware, documentation, interface data, factory test evidence, and support materials required for Government review, shipment, installation planning, and downstream integration.

The antenna system material package shall include, as applicable to the selected design:

1. Four-meter class reflector or aperture assembly.

2. Feed support assembly.

3. Full-motion LEO satellite tracking pedestal, positioner, riser, or equivalent tracking structure with three-axis tracking capability.

4. Drive motors, servo drives, brakes, gears, bearings, and motion-control hardware.

5. Encoders or position feedback devices.

6. Cable wrap, slip ring, fiber rotary joint, or equivalent cable management approach, if applicable.

7. Three-band feed system supporting installed L-, S-, and X-band receive capability.

8. L-band RF path for EPS-Sterna mission support.

9. Technical performance and interface standards for S-band systems shall be defined by

NOAA/NAaaS to ensure compatibility with prospective mission needs. These criteria are detailed in the procurement specification.

Working Draft v0.7.3 – 103308142026 | Page 11

10. NOAA/NAaaS will define the technical performance and interface standards for X-band systems to ensure compatibility with prospective mission needs; these criteria are detailed in the procurement specification.

11. LNAs, filters, diplexers, downconverters, splitters, bias tees, and other RF payload hardware as applicable.

12. Antenna Control Unit.

13. Antenna-local Monitor and Control (M&C) hardware and software.

14. Global Position System (GPS), timing receiver, or supported timing interface, if applicable.

15. Environmental protection equipment such as heaters, dehumidifiers, dehydrators, pressurization hardware, purge hardware, temperature sensors, humidity sensors, and protective enclosures as applicable.

16. Safety controls, maintenance controls, local control boxes, emergency stops, warning indicators, and service tooling as applicable.

17. Mounting hardware, lifting hardware, access hardware, and handling provisions as applicable.

The final delivered configuration, including hardware, software, firmware, optional subsystems, serial numbers, configuration identifiers, and configuration-controlled records shall be documented in the End Item / Pre-Shipment Data Package and As-Delivered Configuration Record in accordance with CDRL-019 and

CDRL-020.

3.2 Radome Package

The Contractor shall provide the radome as part of the antenna system package. The radome package shall include the radome structure, base/interface hardware (mounting plate), sealing materials, access provisions, installation documentation, maintenance documentation, repair materials or recommended repair kit, and all hardware and documentation required to support shipment, installation planning, maintenance, and downstream integration.

The Contractor shall provide antenna/radome interface data required to verify compatibility with the antenna motion envelope, foundation interface, maintenance access envelope, installation sequence, environmental design basis, and RF performance requirements. Radome mechanical, installation, access, and interface data shall be provided in accordance with CDRL-003, CDRL-004, CDRL-014, and CDRL-015.

The Contractor shall identify the RF performance impact of the radome, including radome insertion loss, frequency-dependent loss where applicable, polarization impacts, and the resulting effect on antenna receive Gain-to-Noise Temperature (G/T). Radome RF performance data shall be provided in accordance with CDRL- 005.

3.3 Foundation and Mechanical Compatibility

The Government will provide the foundation design drawings, site layout constraints, and foundation interface data as Government-Furnished Information. The Government-provided foundation interface shall be treated as a design constraint for the antenna/radome system, including the radome base interface and antenna mounting interface.

The Contractor shall verify and document compatibility between the proposed antenna/radome system and the Government-provided foundation interface. The Contractor shall identify any deviations, adapter hardware, interface conflicts, access constraints, installation constraints, loading concerns, cable/fiber entry conflicts, grounding/bonding conflicts, or other impacts requiring Government review.

Foundation and mechanical compatibility data shall be provided in accordance with CDRL-003 and CDRL- 004.

Working Draft v0.7.3 – 103308142026 | Page 12

3.4 Environmental Compatibility and Cold-Weather Design Disclosure The Contractor shall identify whether the proposed antenna/radome system, including outdoor, antenna-mounted, radome-mounted, and antenna-integrated subsystems, is capable of meeting the Government-provided McMurdo environmental design basis, including operation at -50°C where specified in the applicable technical requirements document.

The Contractor shall identify whether compliance with the lower-end temperature requirement is achieved using the contractor’s’s standard product baseline, an existing catalog option, a modified configuration, a custom design, or conditional operating constraints. The Contractor shall identify any subsystem exceptions, required passive or active thermal provisions, cold-start or warm-up limitations, storage/transit constraints, and cost, schedule, power, maintenance, warranty, or logistics impacts.

Environmental compatibility and cold-weather design disclosure data shall be provided in accordance with

CDRL-021.

4.0 RF, IF, Frequency Conversion, and IFL Interface Requirements

4.1 Purpose of RF/IF Interface Definition

The mission interface control documents and the antenna procurement technical specifications will define the detailed mission performance requirements. For the known near-term L-band mission, documentation and supporting procurement specification shall establish the required receive frequency, polarization, modulation, bandwidth, signal compatibility, and mission data interface expectations. NOAA/NAaaS will establish S-band and X-band performance and interface specifications to support future mission requirements; these parameters are identified in the procurement technical specification.

For the Sterna L-band receive path, the antenna/RF chain shall support the EPS-Sterna L-band downlink centered at 1.707 GHz. The Sterna L-band bandwidth to be used for the ground receive path is 3.6 MHz, theoretical, with no transmitter roll-off factor applied. The maximum Doppler assumption for EPS-Sterna is approximately ±45 kHz. No additional guard band, filter bandwidth, or IF bandwidth beyond the EPS-Sterna nominal signal bandwidth is required for EPS-Sterna. Where an IF implementation is used, the EPS-Sterna Ground Segment reference IF scheme used for antenna/receiver sizing is 720 MHz ±7.5 MHz.

This section defines the RF/IF interface data the Contractor shall provide so that the Government can integrate the antenna system with downstream IFL equipment, matrix switches, FEP/demodulator equipment, scheduler/M&C systems, and mission interfaces.

The Contractor shall define the RF/IF output architecture for each supported receive band and receive path.

The Contractor shall identify whether each output is provided at native RF, IF, or another converted frequency.

RF/IF output and frequency conversion interface data shall be provided in accordance with CDRL-005.

4.2 Required RF/IF Output Data

For each supported L-, S-, and X-band receive path, the Contractor shall provide RF/IF output data sufficient to support Government review of downstream IFL, matrix switch, FEP/demodulator, test equipment, and mission compatibility. The Sterna L-band receive-path baseline is defined by the Government-provided Sterna/AWS mission baseline and applicable technical specification. NOAA/NAaaS will establish S-band and X-band performance and interface specifications to support future mission requirements; these parameters are identified in the procurement technical specification.

The RF/IF output data shall define the receive-path architecture, supported bands, polarization capability, channel mapping, RF or IF output characteristics, output level range, bandwidth, dynamic range, gain, noise contribution, G/T performance basis, radome RF loss impacts, filtering, spectral sense, control dependencies, and interface limitations affecting downstream equipment selection and integration.

Working Draft v0.7.3 – 103308142026 | Page 13

If additional conversion, filtering, amplification, attenuation, equalization, or signal conditioning is needed for compatibility with downstream equipment, the Contractor shall identify the need and provide recommended interface constraints. Detailed RF/IF output data shall be provided in accordance with CDRL-005.

4.3 Frequency Conversion Disclosure

The Contractor shall identify whether the antenna system performs frequency conversion for each supported L-, S-, and X-band receive path. For the Sterna L-band receive path, the frequency conversion disclosure shall be traceable to the Government-provided Sterna/AWS L-band mission baseline and reference IF assumptions.

NOAA/NAaaS will establish S-band and X-band performance and interface specifications to support future mission requirements; these parameters are identified in the procurement technical specification. The Contractor shall identify the frequency conversion approach, conversion location, resulting RF/IF output characteristics, local oscillator assumptions where applicable, spectral inversion status, tuning capability, and dependencies between antenna tuning, ACU control, M&C commands, scheduler configuration, and downstream equipment configuration.

This information is required because the frequency conversion approach directly affects IFL selection, matrix switch selection, FEP input compatibility, scheduler configuration, test planning, and mission support.

Frequency conversion disclosure data shall be provided in accordance with CDRL-005.

4.4 Downstream Compatibility Data

The Contractor shall provide RF/IF interface data in sufficient detail to allow the Government to determine compatibility with downstream equipment, including IFL hardware, matrix switches, FEP/demodulators, test equipment, and mission validation equipment.

The Contractor shall identify whether the proposed antenna output architecture is directly compatible with common FEP input architectures or whether downstream conversion, filtering, amplification, attenuation, equalization, or signal conditioning may be required.

The Contractor shall identify any special interface constraints that could affect downstream integration.

Downstream compatibility data shall be provided in accordance with CDRL-005.

4.5 Optional Integrated IFL Transport Capability

The Contractor may propose an integrated IFL transport solution as an optional part of the antenna system package. If proposed, the integrated IFL solution should provide a complete antenna-side signal transport approach suitable for downstream connection to Government-provided site fiber infrastructure.

The Contractor shall identify whether the proposed integrated IFL transport solution is part of the Contractor’s standard product baseline, an existing product option, a modified configuration, a third-party integrated solution, or a custom implementation. The Contractor shall identify any cost, schedule, licensing, sustainment, cybersecurity, M&C, environmental, or integration impacts associated with the proposed IFL solution.

Monitor/control status integration through the antenna ACU, antenna M&C system, or another documented vendor interface is preferred where available in the vendor standard product baseline or where achievable without significant customization, cost growth, or schedule impact.

Integrated IFL transport data shall be provided in accordance with CDRL-006.

4.6 IFL Interface Data When IFL Is Not Vendor-Provided

If the Contractor does not provide an integrated IFL transport solution, the Contractor shall provide the RF/IF, mechanical, power, control, telemetry, environmental, and interface data required for the Government or Government-designated integration party to procure and integrate compatible IFL equipment.

The Contractor shall identify any interface constraints, assumptions, limitations, or recommended downstream equipment characteristics required to preserve receive-chain performance and compatibility.

Working Draft v0.7.3 – 103308142026 | Page 14

IFL interface data shall be provided in accordance with CDRL-006.

4.7 RF/IF, IFL, and Transport Scope Clarification

The Contractor shall clearly identify which RF/IF, IFL, frequency conversion, and signal transport elements are included in the proposed antenna system package and which elements are assumed to be provided by the Government or Government-designated integration party.

The Contractor shall not assume compatibility with Government-provided or third-party downstream equipment unless the Contractor has provided sufficient interface data for Government review.

The Contractor shall identify all assumptions, exceptions, limitations, and recommended downstream equipment characteristics required to preserve receive-chain performance.

5.0 Antenna Control, M&C, Scheduler, and Cybersecurity Interfaces

5.1 Antenna Control Unit and Antenna M&C Interface

The Contractor shall provide the Antenna Control Unit and antenna-local monitor and control capability required to operate, monitor, maintain, and troubleshoot the antenna system.

The Contractor shall define the ACU/M&C architecture, control boundaries, command interfaces, telemetry interfaces, operating modes, tracking modes, timing dependencies, cybersecurity-relevant network interfaces, external control interfaces, user access assumptions, software/firmware update approach, and integration interfaces required for Government review and downstream integration.

The Contractor shall identify which ACU/M&C functions are included in the standard product baseline and which functions require optional licensing, customization, additional hardware, additional software, or recurring support.

ACU and antenna M&C interface data shall be provided in accordance with CDRL-007.

5.2 Scheduler / Propagator / Contact Planning Capability

The Contractor shall propose a scheduler, propagator, and contact planning approach as part of the antenna system solution. The proposed capability may be native to the antenna control system, provided through vendor software, supported through an integrated third-party product, or implemented through documented interfaces to Government or third-party planning tools.

The Contractor shall clearly identify the proposed approach, including functionality, limitations, required interfaces, required Government-provided inputs, and any separately licensed or separately priced components.

If the Contractor does not provide an integrated scheduler or propagator capability, the Contractor shall provide the ACU, M&C, tracking, timing, and interface data required for the Government to integrate a separately procured scheduler or propagator.

For Sterna L-band operations at McMurdo, the proposed scheduler, propagator, and contact planning approach shall support representative high-volume McMurdo contact planning using Government-provided Sterna orbit data, Two-Line Elements (TLEs), planned-pass products, or other Government-provided contact planning inputs. The Contractor shall identify support for AOS/LOS prediction, contact duration calculation, elevation-mask assumptions, minimum-contact-duration assumptions, pass execution status, missed-pass reporting, incomplete-contact reporting, and setup or transition-time constraints between contacts.

Scheduler, propagator, and contact planning capability data shall be provided in accordance with CDRL-008.

5.3 Cybersecurity and Network Interface Data

Detailed cybersecurity requirements will be defined in the applicable technical requirements document. This SOW does not replace or fully define the cybersecurity requirements for the antenna system.

Working Draft v0.7.3 – 103308142026 | Page 15

The Contractor shall provide cybersecurity and network interface data for all vendor-provided networked equipment, software, remote access tools, APIs, web interfaces, update mechanisms, scheduler interfaces, optional IFL status interfaces, optional Front-End Processor (FEP) interfaces, and M&C interfaces so the Government can assess integration, accreditation, and operational security impacts.

The Contractor shall identify which cybersecurity capabilities are included in the vendor baseline and which capabilities require optional licensing, additional hardware, additional software, customization, or recurring vendor support.

Cybersecurity and network interface data shall be provided in accordance with CDRL-010.

6.0 Optional Sterna L-band FEP/Demodulator Capability

6.1 Optional Vendor-Proposed Sterna L-band FEP

The Contractor may propose a FEP / demodulator solution as an optional capability. If proposed, the FEP shall support received signal demodulation, decoding, frame synchronization, data processing, storage, reporting, M&C, and data distribution functions applicable to the known Sterna L-band mission baseline only.

If the Contractor proposes a FEP, the Contractor shall provide sufficient technical, interface, operational, cybersecurity, sustainment, and verification data to demonstrate compatibility with the Sterna L-band antenna RF/IF output, optional IFL transport, downstream matrix switching, timing architecture, M&C architecture, scheduler approach, data center rack environment, and Government mission data interfaces. FEP technical and interface data shall be provided in accordance with CDRL-009.

6.2 FEP Mission Compatibility

If a FEP is proposed, the Contractor shall identify the mission compatibility basis for the proposed Sterna L-band FEP, including IF input compatibility, modulation and coding support, symbol-rate and data-rate capability, Doppler/acquisition capability, frame synchronization, data formatting, and limitations relative to the current Sterna L-band baseline.

Detailed mission performance requirements will be defined in the applicable mission ICDs and technical requirements documents. FEP mission compatibility data shall be provided in accordance with CDRL-009.

6.3 FEP IF Input and Receive-Chain Compatibility

If a FEP is proposed, the Contractor shall define the FEP input compatibility with the proposed antenna RF/IF output, optional IFL transport architecture, downstream matrix switch routing, and any assumed Government-procured or third-party IFL equipment.

The Contractor shall identify any required conversion, filtering, amplification, attenuation, equalization, calibration, or signal conditioning needed before the FEP input. FEP IF input and receive-chain compatibility data shall be provided in accordance with CDRL-009.

6.4 FEP Channelization and Redundancy

If a FEP is proposed, the Contractor shall identify available FEP channelization and redundancy options and how those options support the Government expected operational concept, including one-channel-per-contact operation, two-channel growth where available, warm-standby or spare-unit assumptions, failover assumptions, and limitations affecting channel count.

Dual-channel capability is preferred where available, but final FEP quantity, channel count, standby concept, and routing architecture will be determined by the Government during downstream integration planning. FEP channelization and redundancy data shall be provided in accordance with CDRL-009.

Working Draft v0.7.3 – 103308142026 | Page 16

6.5 FEP Data Processing and Distribution

If a FEP is proposed, the Contractor shall identify the proposed FEP data processing and distribution capability, including frame processing, packet processing, Consultative Committee for Space Data Systems (CCSDS) virtual channel or Virtual Channel Identifier (VCID) support where available, time tagging, metadata, data quality/status reporting, storage, replay, supported output protocols, file formats, and data-integrity features.

For the EPS-Sterna L-band mission baseline, Channel Access Data Units (CADUs) are the expected output from McMurdo to the EPS-Sterna Payload Data Processing (PDP) facility. If a FEP is proposed, the FEP shall be capable of generating CADU output for EPS-Sterna. Virtual Channel Data Unit VCDU / transfer frame output capability may be identified as a selectable configuration if available, but CADU output shall be supported for the EPS-Sterna baseline.

FEP data processing and distribution data shall be provided in accordance with CDRL-009.

6.6 FEP M&C, Scheduler, Timing, and Network Interfaces

If a FEP is proposed, the Contractor shall identify FEP M&C, scheduler, timing, and network interfaces required for operation, integration, monitoring, control, contact configuration, health monitoring, alarm reporting, status reporting, logging, and report generation.

FEP M&C, scheduler, timing, and network interface data shall be provided in accordance with CDRL-009.

6.7 FEP Rack, Power, Cooling, and Maintainability

If a FEP is proposed, the Contractor shall identify the rack, power, cooling, maintainability, storage, service access, spares, licensing, and software support characteristics required to support data center integration and long-term sustainment.

FEP rack, power, cooling, and maintainability data shall be provided in accordance with CDRL-009.

6.8 FEP Cybersecurity and Software Sustainment

If a FEP is proposed, the Contractor shall provide cybersecurity and software sustainment interface data for the FEP in accordance with Section 5.3 and CDRL-010, and shall include FEP-specific cybersecurity, operating system, software versioning, patch management, access control, logging, remote support, update, license management, and long-term support information in accordance with CDRL-009.

6.9 FEP Verification Evidence

If a FEP is proposed, the Contractor shall provide verification evidence demonstrating FEP compatibility with the proposed antenna RF/IF output, optional IFL equipment if included, scheduler approach, M&C interfaces, timing interfaces, network interfaces, and mission data interfaces.

FEP verification evidence shall be provided in accordance with CDRL-009 and shall be included in applicable factory verification planning and reporting deliverables.

6.10 Third-Party or Government-Procured FEP Path

If the Government procures the Sterna L-band FEP separately, the Contractor shall provide all antenna RF, IF, IFL, M&C, timing, scheduler, and interface data required to support integration with a Government-procured or third-party Sterna L-band FEP.

The Contractor shall identify whether the antenna output architecture is directly compatible with common FEP input architectures or whether downstream conversion, filtering, amplification, attenuation, equalization, or signal conditioning may be required. Applicable RF/IF and downstream compatibility data shall be provided in accordance with CDRL-005 and CDRL-009, as applicable.

Working Draft v0.7.3 – 103308142026 | Page 17

7.0 Government Integration Context

7.1 Purpose of Integration Context

This section provides the Contractor with the expected Government integration context for the McMurdo deployment. The information in this section is provided to help the Contractor understand the downstream installation environment, interface needs, and integration planning assumptions.

This SOW does not assign work to LGSS, NSF, ASC, or any other Government-designated installation or integration party. Work performed by LGSS, NSF/ASC, or other Government-designated parties will be authorized under separate contractual or programmatic direction and is provided here only as integration context for the Contractor.

The Contractor’s responsibility under this SOW is to provide the antenna/radome material package and the technical data, drawings, procedures, verification evidence, and support documentation required to enable downstream installation, integration, and test planning by the Government and Government-designated parties.

7.2 Planned LGSS Role

The Government currently plans to use LGSS, Low Earth Orbit Ground Sustainment Services, or another Government-designated organization to support installation and integration activities under separate contractual direction. LGSS activities may include antenna assembly, radome installation support, data center rack infrastructure integration, matrix switch integration, FEP rack integration, RF cabling, network cabling, fiber patching, PDU installation, rack drawings, site checkout, and as-built documentation when authorized by the Government.

This SOW does not assign work to LGSS. The Contractor shall provide the interface data, installation procedures, handling instructions, lifting instructions, alignment procedures, support documentation, and technical assistance options required to enable LGSS or another Government-designated party to plan and perform downstream installation and integration.

Vendor-provided installation, handling, lifting, alignment, interface, and support documentation required to enable LGSS or another Government-designated party shall be provided in accordance with CDRL-003, CDRL-004, CDRL-014, and CDRL-015, as applicable.

7.3 Planned NSF/ASC Role

The Government expects NSF and/or the Antarctic Support Contractor to support McMurdo site and facility infrastructure activities under separate programmatic direction. NSF/ASC support may include site civil works, foundation installation, facility power, electrical cabinets, breakers, outlets, grounding/bonding provisions, site fiber infrastructure, fiber patch panels, data center facility support, local logistics, staging, heavy equipment coordination, access coordination, and other site support activities.

This SOW does not assign work to NSF or ASC. The Contractor shall provide the mechanical, electrical, grounding, fiber, RF/IF, environmental, logistics, storage, lifting, and installation interface data required to support Government coordination with NSF/ASC.

Vendor-provided mechanical, electrical, grounding, fiber, environmental, logistics, storage, lifting, and installation interface data required to support Government coordination with NSF/ASC shall be provided in accordance with CDRL-003, CDRL-004, CDRL-014, CDRL-018, and CDRL-021, as applicable.

7.4 Planned Site Infrastructure Interfaces

The Government-provided foundation drawing package below shall be treated as the controlling foundation interface for antenna/radome compatibility unless otherwise directed by the Government. The Government will provide the following to the Contractor:

1. Concrete foundation interface.

2. Radome base/foundation interface.

Working Draft v0.7.3 – 103308142026 | Page 18

3. Antenna mount/foundation interface.

4. Site power interface.

5. Electrical cabinet or service point interface.

6. Grounding and bonding interface.

7. Fiber interface at or near the antenna foundation area.

8. Cable and conduit entry interface.

9. Antenna/radome access and maintenance envelope.

10. Lifting, staging, and installation access requirements.

11. Environmental storage and preservation constraints before installation.

12. Site checkout interface needs.

The Contractor shall identify any Government-provided site interface data needed to complete the antenna/radome design, factory test planning, packaging, installation planning, or delivery planning. Site infrastructure interface data, assumptions, and constraints affecting the antenna/radome system shall be documented in accordance with CDRL-003, CDRL-004, CDRL-014, CDRL-018, and CDRL-021, as applicable.

7.5 Planned Downstream RF/IF, IFL, FEP, and Data Center Integration The Government expects downstream integration to include RF/IF signal transport, IFL equipment if not vendor-provided, data center rack infrastructure, matrix switches, FEP/demodulator equipment, network interfaces, timing interfaces, and mission data distribution interfaces. These downstream integration activities will be handled outside this contract unless specifically added by the Government.

The downstream integration architecture is expected to include a dedicated L-band routing path for the Sterna mission baseline. S- and X-band routing paths, matrix switch approach, RF/IF transport assumptions, and downstream interface details NOAA/NAaaS will establish S-band and X-band performance and interface specifications to support future mission requirements. These parameters are identified in the procurement technical specification. The baseline planning concept is one receive path per antenna per mission contact, with expanded or two-channel capability preserved where feasible and where supported by the applicable technical specification.

For the Sterna L-band mission baseline, the Government may use a pooled FEP architecture with operational FEPs and warm-standby spare FEPs assignable through the matrix switch architecture. Final downstream integration design, matrix switch procurement, Sterna L-band FEP procurement if applicable, rack design, rack power, rack cooling, network integration, timing architecture, and site acceptance activities will be handled outside this contract..

Vendor-provided RF/IF, IFL, FEP, ACU/M&C, scheduler, timing, network, and cybersecurity interface data required to support downstream integration shall be provided in accordance with CDRL-005, CDRL-006, CDRL-007, CDRL-008, CDRL-009, and CDRL-010, as applicable.

7.6 Support to Downstream Integration

The Contractor shall provide the documentation and technical data needed for Government-designated parties to install, integrate, test, and sustain the antenna/radome system. The Contractor shall also identify available support options for downstream integration, including remote support, on-site support, installation supervision, training, certification, troubleshooting, and post-delivery engineering support.

The Contractor shall identify any limitations to downstream integration support, including response time, support duration, travel constraints, export-control constraints, proprietary tools, license requirements, cybersecurity restrictions, or vendor-only maintenance actions.