▲ 18 ▼ [Eric Berger] One space station company sues another for copying its work (arstechnica.com) submitted 2 days ago by threelonmusketeers@sh.itjust.works to c/spaceflight@sh.itjust.works 4 comments fedilink hide all child comments Axiom suing Vast was not on my bingo card...
[–] threelonmusketeers@sh.itjust.works [S] 2 points 2 days ago (3 children) Axiom suing Vast was not on my bingo card... permalink fedilink source hideshow 3 child comments replies: [–] burble@lemmy.dbzer0.com 2 points 1 day ago (2 children) This is wild. They phoned it in so hard that they couldn't even ctrl+f... permalink fedilink source parent hideshow 2 child comments replies: [–] threelonmusketeers@sh.itjust.works [S] 1 point 1 day ago* (last edited 18 hours ago) (1 child) Huh, this is an interesting development: Several hours after publication of this article, Vast released additional information about the origin of the planning document. The company stated: The Mission Integration and Operations Management Plan was provided to Vast in the normal course of business by a subcontractor that supplies services to Vast and Axiom, using standard documentation adapted from prior missions, as is common practice for NASA private astronaut missions. The version provided to Vast included material carried over from an earlier Axiom mission. Within a day of submitting the document to NASA, Vast proactively informed NASA that the document needed to be corrected and resubmitted a revised version the next day. When NASA later asked us to take additional steps, we did so immediately, and we have cooperated with NASA throughout. Vast did not take anything from Axiom, and any suggestion otherwise is false. Can the subcontractor that "included material carried over from an earlier Axiom mission" be anyone other than... SpaceX? This would imply that SpaceX failed to perform the Ctrl+H find-and-replace, but also that no one at Vast actually read the document before passing it on to NASA... which would not be a great look for either company... permalink fedilink source parent hideshow 1 child comment replies: [–] burble@lemmy.dbzer0.com 2 points 21 hours ago Sounds like it. Pretty incredible work, right there. permalink fedilink source parent
[–] burble@lemmy.dbzer0.com 2 points 1 day ago (2 children) This is wild. They phoned it in so hard that they couldn't even ctrl+f... permalink fedilink source parent hideshow 2 child comments replies: [–] threelonmusketeers@sh.itjust.works [S] 1 point 1 day ago* (last edited 18 hours ago) (1 child) Huh, this is an interesting development: Several hours after publication of this article, Vast released additional information about the origin of the planning document. The company stated: The Mission Integration and Operations Management Plan was provided to Vast in the normal course of business by a subcontractor that supplies services to Vast and Axiom, using standard documentation adapted from prior missions, as is common practice for NASA private astronaut missions. The version provided to Vast included material carried over from an earlier Axiom mission. Within a day of submitting the document to NASA, Vast proactively informed NASA that the document needed to be corrected and resubmitted a revised version the next day. When NASA later asked us to take additional steps, we did so immediately, and we have cooperated with NASA throughout. Vast did not take anything from Axiom, and any suggestion otherwise is false. Can the subcontractor that "included material carried over from an earlier Axiom mission" be anyone other than... SpaceX? This would imply that SpaceX failed to perform the Ctrl+H find-and-replace, but also that no one at Vast actually read the document before passing it on to NASA... which would not be a great look for either company... permalink fedilink source parent hideshow 1 child comment replies: [–] burble@lemmy.dbzer0.com 2 points 21 hours ago Sounds like it. Pretty incredible work, right there. permalink fedilink source parent
[–] threelonmusketeers@sh.itjust.works [S] 1 point 1 day ago* (last edited 18 hours ago) (1 child) Huh, this is an interesting development: Several hours after publication of this article, Vast released additional information about the origin of the planning document. The company stated: The Mission Integration and Operations Management Plan was provided to Vast in the normal course of business by a subcontractor that supplies services to Vast and Axiom, using standard documentation adapted from prior missions, as is common practice for NASA private astronaut missions. The version provided to Vast included material carried over from an earlier Axiom mission. Within a day of submitting the document to NASA, Vast proactively informed NASA that the document needed to be corrected and resubmitted a revised version the next day. When NASA later asked us to take additional steps, we did so immediately, and we have cooperated with NASA throughout. Vast did not take anything from Axiom, and any suggestion otherwise is false. Can the subcontractor that "included material carried over from an earlier Axiom mission" be anyone other than... SpaceX? This would imply that SpaceX failed to perform the Ctrl+H find-and-replace, but also that no one at Vast actually read the document before passing it on to NASA... which would not be a great look for either company... permalink fedilink source parent hideshow 1 child comment replies: [–] burble@lemmy.dbzer0.com 2 points 21 hours ago Sounds like it. Pretty incredible work, right there. permalink fedilink source parent
[–] burble@lemmy.dbzer0.com 2 points 21 hours ago Sounds like it. Pretty incredible work, right there. permalink fedilink source parent