Autonomous On Orbit Logistics and Sustainment Architecture

• Q1 answer expanded: A new numbered point 2 was added explaining that if an offeror has a mitigation plan (during the contract or follow-on work), evaluators treat the flight-derived lesson as risk reduction; with no mitigation, the Government treats it as an inherent technology risk regardless of the company's view.
• Q1 answer restructured: The original answer text was reformatted into a numbered list, with a small wording change ("inherit" risk phrasing carried over as-is).
• No other Q&A entries changed: Q2 through Q8 are identical in substance.
• Q9 still unanswered in the visible text: The A9 response still reads "The topic discusses a..." (truncated), so applicants still lack a usable answer to the autonomy, performance, maturity, and feasibility-evidence questions.

Why it matters: Applicants proposing a new docking interface informed by prior flight literature now have guidance that a documented mitigation plan converts a novelty concern into risk reduction, so proposals should explicitly describe mitigation actions. The Q9 gap remains open and should be watched for a follow-up response before the October 7 question deadline.

• Added a Q&A on whether a new docking and utility interface informed by publicly released Orbital Express design literature and experienced personnel meets the D2P2 “distinctly separate” requirement.
• The Government says it cannot make a prospective determination. Applicants may not use prior SBIR/STTR work to justify D2P2 readiness; the proposed effort must be novel and distinct from prior SBIR/STTR work. Applicants should explain that separation, but the answer does not confirm that using public design lessons will qualify.
• Existing Q&As were renumbered; no other answer changes are evident from the provided text.

• Q1, disconnected/degraded operations: A new answer says continued operation during communications loss is a mitigation for comms loss during a logistics mission. Applicants should address how their prototype handles operations when communications are unavailable.
• Q2, authority transfer and autonomous execution: A new answer says that for commercially operated services to government assets, the Government likely retains spacecraft authority and an ongoing veto to pause or abort logistics actions. It also says the system likely should not preserve prior authority or decisions/actions after an authority change. This affects command-and-control design and raises a recordkeeping issue applicants may want to clarify, given the question’s focus on an auditable mission record.

• Added two unanswered questions: one asks whether prototypes must continue operating during disconnected or degraded communications and reconcile mission data after reconnection; the other asks whether Systems-of-Systems prototypes should track and enforce authority over assets or actions, including delegation and an auditable transfer history. Applicants do not yet have government answers on these operational and recordkeeping expectations.
• The previous multi-part Q7 on acceptable product scope, priority servicing use case, client interfaces, and ground versus orbital demonstration is absent from the updated Q&A excerpt.
• The existing answered Q&As remain, renumbered Q3–Q8; their answers are unchanged in the provided text.

• New Q1 added, still unanswered ("Response Pending"): asks whether a terrestrial hardware-in-the-loop demo using flight-representative software and a representative coupling interface satisfies the Phase II "must demonstrate" language for the 12-month D2P2 effort, or whether a flight-qualified or on-orbit demo is expected. Applicants planning ground-based prototypes should watch for the answer.
• Renumbering only: the prior Q1–Q5 are now Q2–Q6, with no visible change in their text. These are the DSIP cost volume Year 2 zeros guidance (follow-up questions due before Oct 7), virtual Phase II kickoff and deliverables, the OOSL CDW/DRM location, autonomy/safe recovery/GFE/prior-SBIR limits, and the product boundary question. Any citations to old question numbers will be off by one.
• Possible unseen changes: the text is truncated at the end of Q6/A6, so any edits to the ground-versus-orbital demonstration answer cannot be confirmed. The earlier answer said no orbital flight demo is required, with a ground-based demonstration acceptable.
• No questions were removed.

Description information changed.

Description information changed.

Description information changed.

Description information changed.

Description information changed.

Description information changed.

Description information changed.

Description information changed.

Description information changed.

Description information changed.

Description information changed.

Description information changed.

Status changed from status: Pre-Release to status: Open.

Description information changed.

Description information changed.