Very nice article Chris.I'm still interested, that in the QA he actually said that they had coordinated clocking with SNC and Boeing, in fact, he said that "Yes, and as a launch provider, we try to maintain compatibility with all potential spacecraft." Could this mean that SpaceX and ULA are sort of coordinating through backchannels and/or SNC and Boeing things like clocking and such? Could this be the birth of some "de facto" standard for US space vehicles? I've noticed that in the SNC concept video, the ULA crew access is on the port side. It would be interesting when the SpaceX crew access is released to the public to see if they have gone with a similar clocking. If I were SpaceX, I would try to get the same way for SNC and Boeing to be able to bid on their LV needs. And ULA has already coordinated SNC and CST, so might as well coordinate with the Dragon so they can, at least state, that they can offer a backup capability.
Quote from: baldusi on 08/29/2012 05:35 pmVery nice article Chris.I'm still interested, that in the QA he actually said that they had coordinated clocking with SNC and Boeing, in fact, he said that "Yes, and as a launch provider, we try to maintain compatibility with all potential spacecraft." Could this mean that SpaceX and ULA are sort of coordinating through backchannels and/or SNC and Boeing things like clocking and such? Could this be the birth of some "de facto" standard for US space vehicles? I've noticed that in the SNC concept video, the ULA crew access is on the port side. It would be interesting when the SpaceX crew access is released to the public to see if they have gone with a similar clocking. If I were SpaceX, I would try to get the same way for SNC and Boeing to be able to bid on their LV needs. And ULA has already coordinated SNC and CST, so might as well coordinate with the Dragon so they can, at least state, that they can offer a backup capability.No, not really. It is ULA just working with its customers. There is no "standard" to be made. Atlas has its own umbilical locations, as well as Delta and Falcon. This constrains the possible available clocking positions as it relates to spacecraft access. Then there is the flight orientation considerations (the preferred launch vehicle orientation may not be the same as the spacecraft)Any "standard" would only work on new launch vehicles.
This can be deleted later. Where is the link of the USA concept of new mlp that can handle all the vehicles (Delta, Atlas and Falcon)?
Unless of course the "standard" was for a mobile launch platform interface to the pad, in which case the individual launchers would not require a change.
But my point is that roughly, things should get relatively easy to adapt from one vehicle to the other if they put all the access on the "zenith" side of the spacecraft and the crew access slightly to port (like 30 to 45 deg).At least, that's the reasoning that I did. Since you're much more knowledgeable, I would like to understand what I'm missing.
Quote from: Downix on 08/29/2012 06:08 pmUnless of course the "standard" was for a mobile launch platform interface to the pad, in which case the individual launchers would not require a change.No, because the crew access is not on the MLP.
Saturn had crew access on its MLP, so your argument falls apart.
Quote from: Downix on 08/30/2012 12:55 amSaturn had crew access on its MLP, so your argument falls apart.We aren't talking Saturns and no one is going to use LC-39 with vehicle specific MLP's, so your argument falls apart.
Quote from: Jim on 08/29/2012 06:28 pmhttp://www.unitedspacealliance.com/universal-launch-complex.cfmNot much detail there.True. But very neat. I wonder how much of this is encouraged by ULA's desire to lower their costs by going for commonality between elements of Delta and Atlas. I guess once your pad (or pads) can accommodate both of them it's not that big a leap to the idea of making it totally flexible to handle major known (or *plausible*) architectures. Any idea how far this idea has got?
http://www.unitedspacealliance.com/universal-launch-complex.cfmNot much detail there.