We are excited to announce that analysis from June’s qualification test of @NASA_Orion launch abort motor shows positive results
Update on schedule threats, related to Orion, from the most recent ASAP meeting minutes (publically available):Quote from: ASAPThe third critical path item is Orion software, which is progressing from flight-software build to integrated-software testing. There is only one integrated test lab for the avionics software, hence it is a natural bottleneck to schedule flow. The Program works this on a continuous basis, but every piece of software must go through the Software Integration Lab (SIL), and it will remain a bottleneck in terms of any schedule acceleration.
The third critical path item is Orion software, which is progressing from flight-software build to integrated-software testing. There is only one integrated test lab for the avionics software, hence it is a natural bottleneck to schedule flow. The Program works this on a continuous basis, but every piece of software must go through the Software Integration Lab (SIL), and it will remain a bottleneck in terms of any schedule acceleration.
8 guys watching three guys lowering something with a rope. depressing.
NASA | Exploration Mission-1 – Pushing Farther Into Deep SpaceNASA.gov VideoPublished on Sep 18, 2017In the next eight minutes, you’ll experience a twenty-five-and-a-half-day mission from roll-out to recovery of the first integrated flight test of NASA’s Orion spacecraft and the Space Launch System rocket, launching from the agency’s Kennedy Space Center in Florida. This uncrewed mission will be the first in a planned series of exploration missions beyond the moon, signaling what astronauts who dare to operate in deep space will experience on future flights.https://www.youtube.com/watch?v=XcPtQYalkcs?t=001
Quote from: woods170 on 08/24/2017 11:27 amUpdate on schedule threats, related to Orion, from the most recent ASAP meeting minutes (publically available):Quote from: ASAPThe third critical path item is Orion software, which is progressing from flight-software build to integrated-software testing. There is only one integrated test lab for the avionics software, hence it is a natural bottleneck to schedule flow. The Program works this on a continuous basis, but every piece of software must go through the Software Integration Lab (SIL), and it will remain a bottleneck in terms of any schedule acceleration.Would expanding the SIL widen the bottleneck? Is it a plausible solution? Is it possible without a substantial budget increase?***Wasn't ISS USOS software a schedule-buster at one time? If so, how did they fix the problem?
https://www.youtube.com/watch?v=XcPtQYalkcs?t=001