QuestionsAnswers 2.pdf
PDF 107 KB Posted
- Attached to
- CIS Capability Studies III: Lunar Surface User Terminals & Network Orchestration and Management Systems (NextSTEP-2 BAA: Appendix Q) Federal contract opportunity
- Solicitation number
- NNH16ZCQ001K-CIS-Appendix_Q
About this file
This document contains questions and answers related to a federal contract opportunity for Lunar Surface User Terminals and Network Orchestration and Management Systems.
The key details are:
The contract opportunity is part of the Next Space Technologies for Exploration Partnerships-2 (NextSTEP-2) Broad Agency Announcement (BAA) issued by NASA. It seeks industry-led capability studies for two areas: 1) Lunar Surface User Terminals that must meet technical requirements to support lunar surface exploration and ensure interoperability, and 2) Advanced Network Orchestration and Management Systems to control and interface with a globally distributed network of Satellite Ground Systems.
The questions and answers provide clarification on technical requirements, specifically related to "unaided vs aided scenarios" for the user terminals and the expected acceleration and jerk values. Additional context is provided on the jitter and frequency requirements for the S-band carrier. Proposers are encouraged to consider various operational profiles and use cases for the user terminals when addressing the technical requirements.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| SF 30 Amend 2 7-26-24 Signed.pdf | ||
| NNH16ZCQ16CQ001K_CIS_APP Q_SF33-AMEND 2.pdf | ||
| NNH16ZCQ16CQ001K_CIS_APP Q_SF33-AMEND 3.pdf | ||
| SF 30 Amend 3 Signed.pdf | ||
| Enclosure A - Appendix Q Rev 3.pdf | ||
| Enclosure A - Appendix Q - 7-8-24.pdf | ||
| Enclosure A - Appendix Q - Rev 1 7-25-24.pdf | ||
| NNH16ZCQ001K-CIS_APP Q_SF30_AMEND 1.pdf | ||
| Enclosure A - Appendix Q - Rev 1.pdf | ||
| NNH16ZCQ16CQ001K_CIS_APP Q_SF33-AMEND 1.pdf | ||
| RFP Q A.pdf | ||
| Enclosure E - Standard FAR Patent and Data Rights Clauses and Provisions.pdf | ||
| Enclosure A - Appendix Q - Lunar User Terminals and NOMS.pdf | ||
| SF33-CIS BAA.pdf | ||
| Enclosure F - NOMS Demonstration Use Case.pdf | ||
| Enclosure D-Corporate Contributions Worksheet.pdf | ||
| Enclosure C - Pricing Template.pdf | ||
| Enclosure B - Model Contract.pdf |
Show all 18
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
No. Question Answer 1 Section 4.1.2.e.iii, 4.1.3.gii:
• Clarify what is meant by “unaided scenarios” vs aided scenarios?
• Provide additional information or quantization of “expected acceleration and jerk values””
• Aided refers to leveraging additional information/measurements from any source other than the single Augmented Forward Signal (AFS) signal being tracked.
Specifically, the aiding metric could be an inertial measurement system, additional receivers, or any other tool that would provide acceleration/state estimation information to reduce challenges associated with signal acquisition and tracking.
• Expected acceleration and jerk values are not defined by either the LunaNet Interoperability Specifications (LNIS) or AFS, but instead can be derived from receiver use case and expected acceleration/jerk of any AFS signal provider. Proposers are encouraged to consider whether their lunar user terminal design is to be deployed as part of an Astronaut’s EVA suit, on a Lunar Terrain Vehicle (LTV), on a satellite in Lunar orbit, or anywhere else in cislunar space, and how those different operational profiles may influence the range of potential acceleration/jerk values. For additional information on potential user scenarios, see Section “3.2.3 Position, Navigation, and Timing (PNT) Services” of Lunar Relay Services Requirements Document (SRD) (ESC-
LCRNS-REQ-0090).
2 Section 4.1.3.h.iv: Is this specification the jitter of the transmitted S-band carrier, or something else?
The jitter of the transmitted S-band carrier.
3 Section 4.1.3.h.v: The requirement of <
0.1 MHz seems abnormally large. Can
you confirm the units as MHz?
The correct requirement is < 0.1 mHz.
4. Does the “expected acceleration and jerk” refer to RF effects (e.g., Doppler) or physical acceleration/jerk of the device?
For the purpose of Requirement 4.1.2.e.iii, the focus is on ensuring the AFS receiver can retain signal tracking performance throughout any received RF effects or signal changes (doppler, doppler rate) caused by the device’s physical motion (acceleration/jerk).
File details come from the government source that posted it. Updated .