Attach 3 Tracking Layer T0 WFOV TRD (Draft).xlsx
XLSX spreadsheet 22 KB Posted
- Attached to
- SDA Tracking Layer Tranche 0 DRAFT RFP Federal contract opportunity
- Solicitation number
- SDA-SN-20-0009
- Issued by
- Space Development Agency
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Tracking T0 Questions and Answers.xlsx | XLSX spreadsheet | |
| Attach 1 - Tracking Layer TO WFOV SOW (Draft).pdf | ||
| HQ085020R0003.pdf | ||
| Attach 2 - Tracking Layer T0 WFOV Proposal Instructions (Draft).pdf | ||
| Attach 5 - Tracking Layer T0 WFOV Deliverables List (Draft).pdf | ||
| Attach 7 - Tracking Layer T0 WFOV CDRLs (Draft).pdf | ||
| Attach 4 - Tracking Layer T0 WFOV Evaluation Factors (Draft).pdf | ||
| Attach 6 - Tracking Layer T0 WFOV GFE List (Draft) .pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
SDA T0 WFOV TRD Draft RFP
| Attachment 3 - 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. | 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. |
| 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 yeard (Goal) after checkout. | |
| LO-5 | Mission Class | The space vehicles shall be class C, per NASA NPR 8705.4 as tailored per government approval. | |
| 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 [TBR] 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. |
| Mission Performance Requirements | |||
| MP-1 | OPIR Sensor Field of View (FOV) | Each OPIR sensor shall provide a field of view (FOV) of at least > 50 x 50 deg or > 50 deg conical, full angle [TBR]. | |
| MP-2 | Pixel Instantaneous FOV (IFOV) | Each OPIR sensor shall provide a pixel instantaneous FOV (IFOV) of no greater than 450 microradians [TBR] 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 their FOV of < 1.5 km [TBR]. | |
| MP-4 | Stellar Calibration | 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. An OPIR sensor boresite shall be pointed at least 5 deg above limb (Threshold, TBR) or such that the full FOV is viewing space (Objective). SVs shall support stellar calibration data collections of up to ~30 min [TBR] maximum duration, including a return to nominal earth viewing and imaging operations that meet LOS requirements. The system shall be capable of performing at least two such calibrations per day [TBR]. | Cross-link contacts may be broken during off-earth pointing. A dedicated calibration campaign is anticipated during early-orbit checkout that may require more frequent (and possibly of longer duration) off-earth viewing than in nominal mission operations, for which the frequency of off-earth collects will depend on achieved radiometric and goniometric calibration, and thermal stability of the offset between OPIR sensor and star tracker boresites. |
| MP-5 | 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 [TBR] relative to the optical boresight. | |
| MP-6 | On-board Data Storage | The space vehicles shall provide, for the purpose of downlink transmission, on-board storage to accomodate (Threshold): a) full-frame images for at least 50 min [TBR], b) state-of-health telemetry data for at least 48 hr [TBR]; and c) executed commands/scripts for at least 48 hours [TBR]. Higher storage capacity Objectives TBS. | Full-frame images are assumed to meet MP-1, 2, 3, 20, 24. |
| MP-7 | On-board Mission Data Processor | The space vehicles shall provide on-board Mission Data Processor capability to generate exceedances for downlink in OPGA 79 format. Algorithm parameters, to include exceedance threshold, shall be modifiable by ground command. | This capability is expected not to reside in the BMC module; it may reside within payload or bus electronics. Exceedances are calibrated image chips obtained after background suppression processing and thresholding. | |
| MP-8 | Concurrent Data Collection and Data Transmission | The space vehicles shall be capable of concurrent data collection and data transmission to ground. | ||
| MP-9 | 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 [TBR] (Threshold), 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 [TBR] (Threshold). SRA and L/D Objectives TBS. | 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-10 | Solar Impingements | Space vehicle shall be 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 direct sunlight. | |
| MP-11 | Payload Unobstructed Field of View | The 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. [TBR] | Intent is to preclude shadowing by, and reflections from, SV components onto OPIR sensor optics. | |
| MP-12 | OPIR Spectral Band | Each OPIR sensor shall be compatible with imaging in a SWIR or 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. 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-13 | Shortwave Infrared (SWIR) Spectral Band | SWIR band edges at 10% of peak transmittance shall be TBS (see classified appendix). | ||
| MP-14 | SWIR See-to-Ground (SWSTG) Spectral Band | SWSTG band edges at 10% of peak transmittance shall be TBS (see classified appendix). | ||
| MP-15 | 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-16 | Absolute Radiometric Accuracy | OPIR sensor absolute radiometric accuracy shall be better than TBS (see classified appendix). | ||
| MP-17 | Relative Radiometric Accuracy | OPIR sensor relative radiometric accuracy shall be better than TBS when assessed over TBS period (see classified appendix). | ||
| MP-18 | SWIR Noise-Equivalent Target (NET) | If applicable, OPIR sensor-level NET at end of life (EOL), in SWIR spectral band at 1.5 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 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 a typical phasing, not best case, i.e. when a target is static in the scene and centered on a pixel. | |
| MP-19 | SWSTG NET | If applicable, 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. | 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 a typical phasing, not best case, i.e. when a target is static in the scene and centered on a pixel. | |
| MP-20 | Focal Plane Array (FPA) Maximum Frame Rate | The space vehicles shall provide an OPIR sensor Focal Plane Array (FPA) maximum frame rate shall be at least 30 Hz [TBR]. | ||
| MP-21 | OPIR Sensor Integration Times | The space vehicles shall provide OPIR integration times at least spanning the range of 10-1000 msec [TBR]. | ||
| MP-22 | On-board Calibration Capability | The space vehicles should provide on-board capability to characterize pixel operability and response uniformity across the FOV. | ||
| MP-23 | Target State Vector Accuracy | The system shall provide target state vector accuracy less than TBS km and TBS km/s after TBS s of observation (see classified appendix). | ||
| MP-24 | 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-25 | Resiliency Capabilities | Resiliency capabilities to be considered shall include TBS (see classified appendix). | ||
| MP-26 | 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-27 | Mission Data Format | The space vehicles shall be capable of delivering raw full-frame images to GEP, along with mission data messages in the defined OPGA-79 format. | This data format ensures compatibility and minimial changes with the current OPIR enterprise ground architecture. Definition can be found in the bidder's library. | |
| 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, precluding yaw steering. Yaw flips at the poles are permissible. Off-earth pointing may break in-plane links. | |
| AOC-3 | Slewing Capability | The space vehicles shall be sufficiently agile to support all pointing modes. SVs shall support a maximum slew rate for any axis of the OPIR sensor and star tracker boresites of at least 0.3 deg/sec (Threshold) [TBR], 1 deg/sec (Objective) [TBR]. SVs shall be able to slew and settle to image-quality LOS within 100 sec or less [TBR]. | Slewing is assumed to mean a change from one pointing location/mode to another. Slewing is distinct from tracking to maintain a pointing mode. Settling implies meeting LOS control and knowledge requirements for imaging operations. | |
| AOC-4 | Line-of-Sight (LOS) Knowledge Uncertainty, Random | The space vehicles shall provide LOS knowledge random uncertainty, after calibration, for imaging operations, of OPIR sensor boresites of less than 0.1 pixel IFOV (worst axis, 1 sigma) over a frame time. [TBR] | Intent is that SV attitude determination system provides sufficient update rate to support on-board or on-ground mission data and attitude data processing to meet overall sensing and metric accuracy requirements. | |
| AOC-5 | LOS Knowledge Uncertainty, Bias | The space vehicles shall provide LOS knowledge bias uncertainty, after calibration, for imaging operations, of less than 0.1 pixel IFOV (worst axis) for each OPIR sensor over 20 min [TBR]. | ||
| AOC-6 | LOS Control Accuracy, Bias | The space vehicles shall provide LOS control accuracy during imaging operations, after calibration, for imaging operations, of less than 0.1 FOV width (see MP-1) (worst axis, 1 sigma) [TBR]. | ||
| 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) [TBR]. | ||
| AOC-8 | LOS Control Accuracy, Random | The high-frequency LOS jitter during a frame time, during imaging operations, at each OPIR sensor mounting location shall not exceed 0.1 pixel IFOV [TBR] (worst axis, 1 sigma) for frequencies greater than 13.4 Hz (1/2.26T Hz, where T = 33 msec) [TBR]. | ||
| The space vehicle low-frequency LOS drift, during imaging operations, over 30 frames shall not exceed 0.1 pixel IFOV [TBR] (worst axis, 1 sigma) for frequencies below 13.4 Hz (1/2.26T Hz, where T = 33 msec) [TBR]. | Intent is that jitter and drift do not degrade point-response function or LOS knowledge sufficiently to violate other mission performance requirements. Actual values are tradeable. | |||
| AOC-9 | Orbit Position Knowledge | The space vehicles shall provide orbit position knowledge to less than 10 m (3 sigma) using GPS. | SVs are assumed to provide GPS/GNSS-based position, navigation, and timing information and telemetry to support space/ground processing. Refer to Transport RFP. | |
| AOC-10 | Orbit Velocity Knowledge | The space vehicles shall provide orbit velocity knowledge to less than 0.02 m/s (3 sigma) using GPS. | SVs are assumed to provide GPS/GNSS-based position, navigation, and timing information and telemetry to support space/ground processing. Refer to Transport RFP. | |
| Communications Architecture | ||||
| 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 or 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 TT&C subsystem should be attended (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. | ||
| 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 mutliple contacts per day (TBD). | A single (Ka-band) solution is preferred for all phases of operations. A less desirable option is to use use USB or SGLS compatible transceivers to provide multiple contact opportunities per day. | |
| TTC-2 | TT&C Frequency Band (On Station) | The space vehicle shall be able to receive commands from the Government GEP at Ka-band (30-31 GHz) [TBR]. | ||
| TTC-3 | TT&C Coverage | The space vehicles at LEO shall provide near 4π steradian coverage from the TT&C antenna(s) [TBR]. | ||
| 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. | Examples include USB and/or Dual-band USB/SGLS (Objective) modulation. | |
| TTC-6 | TT&C Data Rate | The space vehicles shall provide TT&C data rates of 1Mbps [TBR]. | ||
| TTC-7 | Command and Telemetry Bit Error Rate (BER) after Forwared 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 a minimum rate of 1 Hz [TBR]. | Intent is capability for at-minimum 1 Hz telemetry insight rate, not for a 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. [TBR] | ||
| DL-5 | Daily Mission Data Downlink Volume | The space vehicles must be able to downlink mission data at a rate of at least 250 GB/day (Threshold) [TBR]; higher data rates (Objective TBS). | An RF link would be designed to close at 500 Mbps into Government GEP at 98% link availability, with capability to increase data rate if the weather is benign. | |
| Crosslink (OISL, RF) | ||||
| XL-1 | Crosslink Connectivity | The space vehicles shall provide crosslink connectivity between adjacent SVs within the plane (Threshold), cross-plane connectivity [TBR] (Objective 1), connectivity to Transport layer [TBR] (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. [TBR] | ||
| 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 | RF Crosslink Transmission Rate | V-band crosslinks shall support data rates of TBS Mb/s [TBR] (Threshold), 1 Gb/s [TBR] (Objective). | ||
| XL-7 | 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. | |
| 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 [TBR]. | ||
| 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. | ||
| 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 shall be executed if no commands are received from the ground within [TBS] days. | ||
| 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 | |
| SV, LV | Space Vehicle, Launch Vehicle |
| OPIR | Overhead Persistent Infrared |
| LOS | Line of Sight |
| (I)FOV | (Instantaneous) Field of View |
| RF | Radio Frequency |
| OISL | Optical Inter Satellite Link |
| NRL | Naval Research Laboratory |
| GEP | Ground Entry Point |
| NLT, NGT | No Less Than, No Greater Than |
| NET | Noise Equivalent Target |
| IP | Internet Protocol |
| TBS, TBD | To Be Specified, To Be Determined |
| TBR | To Be Reviewed |
| SWIR | Short Wave Infra Red |
| SWSTG | Short Wave IR See To Ground |
| BER | Bit Error Rate |
| FEC | Forward Error Correction |
| SNR | Signal to Noise Ratio |
| GSD | Ground Sample Distance (defined as perpendicular to LOS) |
| TOO | Target of Opportunity |
| EELV | Evolved Expendable Launch Vehicle |
| BMC | Battle Management & Control |
| SRA | Solar Rejection Angle |
| FOR | Field of Regard |
| GPS | Global Positioning System |
| GNSS | Global Navigation Satellite System |
| BMC | Battle Management & Control |
| OPGA | Overhead Persistent GEOINT Architecture |
File details come from the government source that posted it. Updated .