Attachment 3 - TRD.xlsx
XLSX spreadsheet 31 KB Posted
- Attached to
- SDA Tranche 0 Tracking Layer
- Solicitation number
- HQ085020R0003
- Issued by
-
Space Development Agency
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
Final TRD
| Attachment 3 - Tracking Layer T0 WFOV Technical Requirements Document | |||
| ID | Title | Requirement | Explanation/Justification |
| Launch and Orbit Requirements | |||
| LO-1 | Orbit Altitude | The space vehicles shall be compatible with an orbit altitude of 1000 km (circular). | SDA Tracking and Transport Tranche 0 Layers are expected to launch together on two launch vehicles, and the two Layers are expected to share orbital planes and altitudes. Launch insertion orbit may be less (~950 km) and SV maneuvers will be required to achieve operational orbit. |
| LO-2 | Orbit Inclination | The space vehicles shall be compatible with an orbit inclination of 80-100 degrees. | |
| LO-3 | Orbital Configuration | The space vehicles will be configured in two adjacent planes to maximize stereo coverage for targets of opportunity (TOOs). | |
| LO-4 | SV Operational Lifetime (After Checkout) | The space vehicles shall have an operational lifetime of 4 years (Threshold), 5 years (Goal) after checkout. | |
| LO-5 | Mission Class | The space vehicles shall adhere to the guidelines for class C, per NASA NPR 8705.4 in Appendix C, as tailored per government approval. Other proven flight hardware parts or up-screening is allowed as long as the SV meets minimum class C requirements. | |
| LO-6 | Propulsion and Disposal | The proposed solution shall include a propulsive capability that supports all stages of the mission from separation from the Launch Vehicle (LV) to disposal. | The disposal must be consistent with the "U.S. Government Orbital Debris Mitigation Standard Practices, November 2019 Update" and AFI 91-202, where ODMSP takes precedence. The offerors may assume that the SVs are released from the LV into a nominal 950 km circular orbit at the same inclination and ascending node as their operational orbit. The offerors are responsible for providing sufficient propulsive capability to account for launch insertion errors typical of EELV-class vehicles, in-plane drift, and station-keeping, as well as the disposal referenced above. |
| LO-7 | Initial Launch Capability | The space vehicles shall have an initial launch capability no later than 4QFY22. | |
| Mission Performance Requirements | |||
| MP-1 | SV OPIR Field of View (FOV) Coverage | Each SV shall provide total OPIR sensor coverage of at least 5000 square degrees (Threshold), 12000 square degrees (Objective). | SV designs are desired that a) minimize the overall constellation size and presumed cost for an objective LEO Tracking system with global OPIR stereoscopic coverage when accounting for solar outages, and b) maximize total OPIR sensor coverage in T0. |
| MP-2 | Pixel Instantaneous FOV (IFOV) | Each OPIR sensor shall provide a pixel instantaneous FOV (IFOV) of no greater than 450 microradians at the edge of the Earth at the horizon when in view. | |
| MP-3 | OPIR Sensor Ground-Sample Distance (GSD) | Each OPIR sensor shall provide Ground-Sample Distance (GSD) over its FOV of < 1.5 km. | |
| MP-4 | Star-/Space-View Calibration | The space vehicles shall support stellar imaging via off-nadir pointing of the OPIR sensor boresite at least 5 deg above limb (Threshold) and of full sensor FOV (Objective) above Earth limb with at least ~30 min duration, at least twice daily. | Cross-link contacts may be broken during off-earth pointing. A dedicated calibration campaign is anticipated during early-orbit checkout that will require more frequent off-earth viewing than in nominal mission operations, which may require infrequent off-earth collects depending on achieved calibration stability. |
| MP-5 | On-orbit Calibration Pointing Mode | The space vehicles shall provide capability to support periodic on-orbit calibration in which SV orientations offer stellar views simultaneously for OPIR sensors and star trackers. | |
| MP-6 | Goniometric Accuracy | The system shall provide focal plane vector table (FPVT) accuracy, after calibration, for each pixel over an OPIR sensor FOV of less than 0.1 IFOV relative to the optical boresight. | |
| MP-7 | On-board Data Storage | The space vehicles shall provide, for the purpose of downlink transmission, on-board storage to accomodate: |
a) Full-frame images for at least 50 min (Threshold), 12 hr (Objective)
b) State-of-health telemetry data for at least 48 hr (Threshold), 7 days (Objective)
c) Executed commands/scripts for at least 48 hr (Threshold), 7 days (Objective) Full-frame images are assumed to meet MP-1, 2, 3, 20, 24.
| MP-8 | On-board Mission Data Processor (MDP) | The space vehicles shall provide on-board Mission Data Processor capability to calibrate images, suppress background scene clutter, and generate exceedances and tracklets for a range of realistic missile targets, to downlink in a OPGA-compatible standard format. | This capability is expected not to reside in the BMC3 module. It may reside within payload or bus electronics. Exceedances are calibrated pixel outputs whose signal exceeds a given threshold after background suppression. Contractor should evaluate capability to detect stressing and realistic below-the-horizon targets, e.g., HGVs (see classified appendix), for a range of atmospheric and scene illumination conditions, to achieve a given probability of detection and false exceedance rate. Scene backgrounds should include structured features such as terrain (e.g., high albedo), clouds of varying types/altitidues (e.g., cirrus, water, water/ice) over a significant portion of the FOV. A nominal revisit or track update rate of 1 sec is assumed. Contractor may propose collection and processing conops that could include some type of frame combination to support this. |
| MP-9 | Concurrent Data Collection and Data Transmission | The space vehicles shall be capable of concurrent data collection and data transmission to ground. | |
| MP-10 | Solar Rejection | Each OPIR sensor shall provide Solar Rejection Angle (SRA), defined as the angle from the edge of the FOV beyond which the edge of the sun's disk does not impinge on the front optic, of less than 20 deg, or the OPIR sensor baffles shall have L/D greater than or equal to 1.5, where L is the baffle length measured from the front optic to baffle entrance and parallel to the optical axis, and D is the front optic diameter. | Designs are desired that minimize sensor solar outages and thus minimize the overall constellation size that can provide stereo coverage without solar outages. NET requirements in MP-19, 20 apply when the sun is outside the solar rejection angle. |
| MP-11 | Solar Impingements | Space vehicles shall be either capable of preventing harm to any system due to solar illumination, or impervious to harm due to solar illumination. | Intent is that optics and FPA are protected from damage due to direct sunlight. |
| MP-12 | Payload Unobstructed Field of View | Space vehicles shall provide an unobstructed FOV to the top surface of the highest optic of the OPIR sensors over the solar rejection angle defined in MP-10. | Intent is to preclude shadowing by, and reflections from, SV components onto OPIR sensor optics. Highest optic is the first or front optic through which photons pass into an OPIR sensor. |
| MP-13 | OPIR Spectral Band | Each OPIR sensor shall be compatible with imaging in nominally either a SWIR or a SWSTG spectral band that is sensitive to a reference target signature as described in the classified appendix. | Expectation is that the classified spectral band will be selected by contractor. A single spectral band is sufficient. Government will consider solutions that utilize additional spectral bands. Government expects flight background data to be available in FY22 that could inform optimization of spectral band choice, if schedule and AI&T flow permit. |
| MP-14 | Shortwave Infrared (SWIR) Spectral Band | SWIR band edges at 10% of peak transmittance shall be TBS (see classified appendix). | If SWIR band is used |
| MP-15 | SWIR See-to-Ground (SWSTG) Spectral Band | SWSTG band edges at 10% of peak transmittance shall be TBS (see classified appendix). | If SWSTG band is used |
| MP-16 | Out-of-band (OOB) Spectral Transmittance | OPIR sensor OOB spectral transmittance, defined for wavelengths outside of bands starting at TBS offset from band edges, relative to peak transmittance, shall be less than TBS (see classified appendix). | |
| MP-17 | Absolute Radiometric Accuracy | OPIR sensor absolute radiometric accuracy shall be better than TBS (see classified appendix). | |
| MP-18 | Relative Radiometric Accuracy | OPIR sensor relative radiometric accuracy shall be better than TBS (see classified appendix). | |
| MP-19 | SWIR Noise-Equivalent Target (NET) | OPIR sensor-level NET at end of life (EOL), in SWIR spectral band at 1.5 microflick (Threshold), 3 microflick (Objective) background shall be no greater than TBS (see classified appendix) over the full FOV for an average target phasing with respect to pixel position. NET applies to post-processed data collected while imaging with the sun outside of the solar exclusion zone defined in MP-10. | Target phasing refers to position of a point-source target relative to pixel center and accounts for relative motion between sensor and target. NET is to be assessed for an average phasing, not best case (i.e., when a target is static in the scene and centered on a pixel). NET is to be assessed on post-processed data, i.e. after calibration and background suppression. |
| MP-20 | SWSTG NET | OPIR sensor-level NET at EOL, in SWSTG spectral band at 4.0 microflick background shall be no greater than TBS (see classified appendix) over the full FOV for an average target phasing with respect to pixel position. NET applies to post-processed data collected while imaging with the sun outside of the solar exclusion zone defined in MP-10. | Target phasing refers to position of a point-source target relative to pixel center and accounts for relative motion between sensor and target. NET is to be assessed for an average phasing, not best case (i.e., when a target is static in the scene and centered on a pixel). NET is to be assessed on post-processed data, i.e. after calibration and background suppression. |
| MP-21 | Focal Plane Array (FPA) Maximum Frame Rate | The space vehicles shall provide an OPIR sensor Focal Plane Array (FPA) maximum frame rate that shall be at least 30 Hz. | |
| MP-22 | OPIR Sensor Integration Times | The space vehicles shall provide OPIR integration times at least spanning the range of 10-1000 msec. | |
| MP-23 | On-Orbit Calibration Capability | The space vehicles shall provide an on-board capability to characterize pixel operability and response uniformity across the FOV. | |
| MP-24 | Target State Vector Accuracy | The system shall provide target state vector accuracy less than TBS km and TBS km/s (see classified appendix). | |
| MP-25 | Closely-Spaced Objects (CSO) Separation | Each OPIR sensor shall be able to detect, with a probability greater than or equal to 0.9, Closely-Spaced Objects (CSOs) separated by 2 pixel IFOVs for targets of equal intensity and SNRs greater than or equal to 30, with a probability of false alarm less than or equal to 0.1. | Detection is defined as correctly detecting two targets when two targets are present, whereas a false alarm is defined as detecting two targets when only one target is present. |
| MP-26 | Resiliency Capabilities | Resiliency capabilities to be considered shall include TBS (see classified appendix). | |
| MP-27 | Continuous Imaging Operations | The space vehicles shall be designed to support continuous imaging operations. | Intent is to avoid duty cycle conops e.g., due to power or thermal constraints. |
| MP-28 | Mission Data Format | Mission data and messages (e.g., exceedances, tracklets) shall be delivered to the GEP in an OPGA-compatible standard format. | This data format ensures compatibility with the current OPIR enterprise ground architecture. |
| MP-29 | Exceedance Message Latency | The space vehicles will demonstrate latency of exceedances from collection to receipt at GEP. | |
| BMC3 Hardware Module | |||
| BMC3-1 | BMC3 Module Swap | The BMC3 module will be designed as a separate module to allow potential portability and shall conform to the following SWaP constraints: a) < 30 x 15 x 15 cm |
b) < 10 kg
c) < 15 W (survival power)
| d) < 250 W (peak with max processing) | Vendor must provide a BMC3 compute module within SWaP constraints to reduce risk for future tranches. These are not necessarily the same SWaP constraints that will be used for Tranche 1. | |||
| BMC3-2 | BMC3 Module Design Life | The BMC3 module shall have a threshold 2-year design life and objective 4-year design life. | BMC3 module must last long enough to generate sufficient data for risk reduction for future tranches while still allowing for cost, performance and schedule benefits derived from utilizing commercial radiation tolerant components (if desired). | |
| Attitude and Orbit Control | ||||
| AOC-1 | Stabilization Method | The space vehicles shall be stabilized in all three axes. | ||
| AOC-2 | Pointing Modes | The space vehicles shall be compatible with the following pointing modes: Nadir and Ram Fixed (for mission operations), Earth-Centered Fixed (for cued operations), Off-Earth Inertial Point/Track (for star collects), Sun Pointing (for solar array charging), Safe. | The OPIR sensors may be body-fixed to their space vehicles, and thus pointed via bus slewing. In-plane crosslinks are assumed to have stable links for mission operations. Yaw-steering is permissable provided the in-plane crosslink connections can be maintained during the process. Yaw flips at the poles are permissible. Off-earth pointing may break in-plane links. | |
| AOC-3 | Slewing Capability | The space vehicles shall be able to slew the OPIR sensor and star tracker boresites at 0.3 deg/sec or less and settle within 30 sec or less. | Slewing is assumed to mean a change from one pointing location/mode to another. Slewing is distinct from tracking. | |
| AOC-4 | Line-of-Sight (LOS) Knowledge Uncertainty, Random | The space vehicles shall provide LOS knowledge random uncertainty, after calibration, of OPIR sensor boresites of less than 0.1 pixel IFOV (worst axis, 1 sigma) over a 30 Hz frame time, where attitude determination system sample rate is at least 100 Hz. | ||
| AOC-5 | LOS Knowledge Uncertainty, Bias | The space vehicles shall provide LOS knowledge bias uncertainty, after calibration, of less than 0.1 pixel IFOV (worst axis) for each OPIR sensor over 20 min. | ||
| AOC-6 | LOS Control Accuracy, Bias | The space vehicles shall provide LOS control accuracy during imaging operations, after calibration, of less than 0.1 FOV width (see MP-1) (worst axis, 1 sigma) over 1 sec. | ||
| AOC-7 | LOS Rate Knowledge | The space vehicles shall provide LOS rate knowledge uncertainty during imaging operations of OPIR sensor boresites of less than 3 pixel IFOV per second (worst axis). | ||
| AOC-8 | LOS Control Accuracy, Random | The bus-imparted high-frequency LOS jitter during a frame time at each OPIR sensor mounting location shall not exceed 0.1 pixel IFOV (worst axis, 1 sigma) for frequencies greater than 13.4 Hz (1/2.26T Hz, where T = 33 msec). |
The space vehicle low-frequency LOS drift over 30 frames shall not exceed 0.1 pixel IFOV (worst axis, 1 sigma) for frequencies below 13.4 Hz (1/2.26T Hz, where T = 33 msec).
| AOC-9 | Orbit Position Knowledge | The space vehicles shall provide orbit position knowledge to less than 10 m (3 sigma) at a rate of ≥ 30 Hz. |
| AOC-10 | Orbit Velocity Knowledge | The space vehicles shall provide orbit velocity knowledge to less than 0.02 m/s (3 sigma) at a rate of ≥ 30 Hz. |
| Communications Architecture & Cybersecurity | ||
| Comm-1 | Communication Architecture Overview | SV communication architecture shall include: |
a) two OISLs per SV for in-plane transmission (Threshold), and up to two OISLs per SV for cross-plane and ground transmission (Objective),
b) one Ka Tx/Rx antenna per SV,
c) one V-band RF crosslink as backup to OISLs at least through CDR,
| d) routing protocols per Transport Tranche 0 RFP, with no requirement for Link 16, IBS links. | The communication architecture should be designed to support the goals of the Tranche 0 WFOV program that are defined in the SOW. In support of this goal, the envisioned communication architecture should transport mission data and satellite vehicle (SV) state of health telemetry through crosslinks and space-to-ground links into a government ground entry point (GEP). The crosslinks should employ a network architecture such that Tranche 0 can demonstrate the routing of mission sensor data to assess the trade of on-board processing vs. ground processing in light of downlink communications infrastructure strategies. The space-to-ground link should be sized to accommodate the mission sensor data into the government GEP. The GEP will primarily use a 3.7 meter antenna. The TT&C subsystem should be attended (i.e., manned) to operate during launch, early on-orbit operation, and contingency with a high availability. | |||
| Comm-2 | Encryption | The space vehicles shall use NSA Type I encryption for all links. | ||
| Comm-3 | Classification of Onboard Data Handling | Onboard data handling within the Tracking SV payload shall be at SECRET in order to handle potential data fusion and Link-16 message processing. Data requiring classification beyond collateral SECRET will be encrypted at origin and decrypted at its destination and may transit the Tracking Layer SVs without further security measures | ||
| Comm-4 | Red-Black Separation | The communication architecture shall be designed to ensure proper separation of Red (classified plaintext) and Black (unclassified encrypted) data | ||
| Comm-5 | Command Authentication | Commands shall be authenticated by the destination SV. Intermediate nodes on the network do not need to authenticate, although each link between nodes will be encrypted | ||
| Telemetry, Tracking, and Commanding | ||||
| TTC-1 | TT&C Frequency Band (Launch and Early On-Orbit Ops) | The space vehicles shall operate with a frequency plan to operate the TT&C system during launch, early on-orbit operations and contingency by providing multiple contacts per day. | A single (Ka-band) solution shall be used for all phases of operations. | |
| TTC-2 | TT&C Frequency Band (On Station) | The space vehicles shall be able to receive commands from the Government GEP at Ka-band (30-31 GHz). | ||
| TTC-3 | TT&C Coverage | The space vehicles shall provide near 4π steradian coverage from the TT&C antenna(s). | ||
| TTC-4 | TT&C Link Availability | The space vehicles shall provide a TT&C link availability of at least 99%. | Link availability applies when SV is in contact with GEP. | |
| TTC-5 | TT&C Waveform | The space vehicles shall provide a TT&C system that use an open waveform or government proprietary standards. | ||
| TTC-6 | TT&C Data Rate | The space vehicles shall provide TT&C data rates of ~1Mbps. | ||
| TTC-7 | Command and Telemetry Bit Error Rate (BER) after Forward Error Correction (FEC) | The space vehicles shall provide a command and telemetry bit error rate not to exceed 1e-7. | ||
| TTC-8 | State-of-Health (SOH) Telemetry | The space vehicles shall be capable of publishing for downlink system state-of-health (SOH) telemetry at 1 Hz. | Intent is capability for 1 Hz telemetry insight, not 1 Hz realtime downlink. | |
| Mission Data Downlink | ||||
| DL-1 | Mission Data Downlink | The space vehicles shall provide a space-to-ground link for mission data and SOH that can support a variable data rate. | For example, Digital Video Broadcast - S2 (DVB-S2) Modulation and Coding Standard, using the Variable Coding Modulation/Adpative Coding Modulation feature to increase the data throughput during benign weather conditions. | |
| DL-2 | Mission Data Downlink Frequency Band | The space vehicles shall downlink OPIR mission data using military Ka-band, operating within 20.2 -21.2 GHz, and interface to a government GEP (Ground-Entry Point). | Ka is assumed to downlink TT&C and SOH telemetry as well as mission data. | |
| DL-3 | Mission Data Link Availability | The space vehicles shall provide a mission data link availability of at least 98%. | Link availability applies when SV is in contact with GEP. | |
| DL-4 | Mission Data Downlink BER after FEC | The space vehicles shall provide a mission data downlink bit error rate not to exceed 1e-9. | ||
| DL-5 | SV Mission Data Downlink | Each space vehicle must be able to downlink mission data at a rate of at least 100 Mbps (Threshold), 500 Mbps (Objective). | RF link should be designed to close into Government GEP at 90%ile link availability, with capability to increase data rate if the weather is benign. Objective may be achieved by use of additional components to the baseline Ka-band downlink. Lossless compression should be used to maximize daily downlinked data. | |
| Crosslink (OISL, RF) | ||||
| XL-1 | Crosslink Connectivity | The space vehicles shall provide crosslink connectivity between adjacent SVs within the plane (Threshold), cross-plane connectivity (Objective 1), connectivity to Transport layer (Objective 2). | Both optical and RF crosslinks are expected to be interoperable between Transport and Tracking Layers (OISL to OISL and RF to RF, not OISL to RF). | |
| XL-2 | Crosslink Architecture | The space vehicles shall interface with other SVs using a networking protocol architecture. | Refer to Networking General information described in the Transport Layer RFP. | |
| XL-3 | Crosslink Encryption | The space vehicles shall provide IP-based Security Protocol encrypted crosslinks. | ||
| XL-4 | Optical Inter-Satellite Link (OISL) Compatibility | The space vehicles shall provide OISL terminals that comply with the SDA Transport Layer OISL standard. | Refer to the SDA Draft OISL Standard for more detail on the laser terminals. This should include, and not be limited to, the wavelength, FOR, and modulation scheme. | |
| XL-5 | RF Crosslink Frequency Band | The space vehicles shall plan for RF crosslink terminals that operate in V-band (40-75 GHz) (until at least CDR). | Refer to SDA Transport RFP. | |
| XL-6 | Crosslink BER (Bit Error Rate) after FEC (Forward Error Correction) | The space vehicles shall provide a crosslink bit error rate not to exceed 1e-6 (Threshold), 1e-9 (Objective). | Refer to SDA Draft OISL standard. | |
| XL-7 | Crosslink SWaP | RF and OISL crosslinks should be designed with similar SWaP and data rates should be commensurate with the specified SWaP. | SDA understands design trade-offs will have to address SWaP. Refer to Transport RFP/SOW 4.4.2 - Optical Intersatellite Links and Radio Frequency crosslinks - Technical Objectives | |
| Software | ||||
| SW-1 | Command Execution Accuracy | The space vehicles shall provide a command execution accuracy of +/- 1 sec. | ||
| SW-2 | Software Uploads | The space vehicles shall provide the capability to upload new software, commands, and look-up tables as needed, throughout the mission life. | ||
| SW-3 | On-board Time Reference | The space vehicles shall provide an on-board time reference 1 PPS (pulse per second) with an accuracy of less than 100 ns with respect to UTC. | ||
| SW-4 | Stored Command Execution | The space vehicles shall provide the capability for stored command execution. | ||
| SW-5 | Command Execution | The space vehicles shall support scripted, stored, and real-time command sequences. | SV command scope is assumed to include ability to command settings, functions, and modes for sensors, processors, and other SV components as required and as described above, e.g. in MP-4, 5, 7, 8, 21, 22, and AOC-2. | |
| SW-6 | Compression | The space vehicles shall support lossless compression for wideband mission data downlink. | ||
| Fault Detection and Correction | ||||
| FDC-1 | SV Safe Mode | The space vehicles shall provide a safe mode, i.e., a minimum-power state in which SOH telemetry can be downlinked by command. | ||
| FDC-2 | SV Irreversible Damage | The space vehicles shall not be irreversibly damaged in safe mode for any duration. | ||
| FDC-3 | SV Power Positive | The space vehicles shall be power-positive in safe mode. | ||
| FDC-4 | SV Autonomous Battery Charging | The space vehicles shall autonomously recover a sufficient state of charge in safe mode to be able to transition into controlled operations when communications resume. | ||
| FDC-5 | SV Safe Mode Initiation | The space vehicles shall be able to initiate safe mode both autonomously and by command. | ||
| FDC-6 | SOC Load Shedding | The space vehicles shall autonomously shed loads in an ordered sequence when battery state of charge drops below established limits. | ||
| FDC-7 | SOC Safe Mode Initiation | The space vehicles shall autonomously enter safe mode when battery state of charge drops below established limits. | ||
| FDC-8 | Power Fault Handling | The space vehicles shall be designed in a way that no system suffers irreversible damage if power to that system is instantaneously terminated. | ||
| FDC-9 | SV System Reset | The space vehicles shall have a System Reset that restarts every critical processor and places the space vehicle in a known state capable of executing commands. | ||
| FDC-10 | SV Hard System Reset | The space vehicles shall have a Hard System Reset that restarts critical components without using processor(s) and/or software. | ||
| FDC-11 | SV Reset Actuation | The space vehicle System Reset shall be capable of execution both autonomously and by command. | ||
| FDC-12 | SV Autonomous Reset | The space vehicles shall implement a Command Loss Timer that implements a System Reset that shall be executed if no commands are received from the ground within 1 day. | ||
| FDC-13 | SV End of Life Passivation | The space vehicles shall have the ability to passivate the spacecraft at the end of life through a series of ground commands. |
| Acronyms/Definitions | ||
| AI&T | Assembly, Integration, and Test | |
| BER | Bit Error Rate | |
| BMC3 | Battle Management, Command, Control, and Communications | |
| EELV | Evolved Expendable Launch Vehicle | |
| FEC | Forward Error Correction | |
| GEP | Ground Entry Point | |
| GSD | Ground Sample Distance, referenced perpendicular to LOS | |
| HGV | Hypersonic Glide Vehicle | |
| (I)FOV | (Instantaneous) Field of View | |
| IP | Internet Protocol | |
| LOS | Line of Sight | |
| NET | Noise Equivalent Target | |
| OISL | Optical Inter Satellite Link | |
| OPGA | Overhead Persistent Ground Architecture | |
| OPIR | Overhead Persistent Infrared | |
| PPS | Pulse Per Second | |
| RF | Radio Frequency | |
| SNR | Signal-to-Noise Ratio | |
| SRA | Solar Rejection Angle | |
| SV, LV | Space Vehicle, Launch Vehicle | |
| SWIR | Shortwave Infrared | |
| SWSTG | Shortwave See To Ground | |
| TBS | To Be Specified | |
| TOO | Target of Opportunity | |
| UTC | Coordinated Universal Time |
File details come from the government source that posted it. Updated .