Quote from: woods170 on 06/18/2019 01:42 pmQuote from: gongora on 06/15/2019 10:40 pmDragon is smaller than NASA really wanted for CRS, I don't see it being competitive for the Gateway missions...Emphasis mine.With all due respect but that statement is not rooted in fact. NASA, under COTS/CRS-1 issued only two high-level requirements which had any effect on spacecraft size:- Minimum amount of pressurized cargo to be transported up to ISS.- Minimum amount of cargo missions to be flown.NASA did not require the COTS contractors to have their spacecraft be of a minimum size/weight. Had NASA really wanted the contractors' spacecraft to be of a certain minimal size than they would have issued a requirement for it. But NASA didn't.I haven't read the new RFP closely, but it seems to me the above is true for Gateway cargo too, no specific requirement for minimal size of the spacecraft, so I don't see how Dragon can be uncompetitive when the size is not even in the requirement.
Quote from: gongora on 06/15/2019 10:40 pmDragon is smaller than NASA really wanted for CRS, I don't see it being competitive for the Gateway missions...Emphasis mine.With all due respect but that statement is not rooted in fact. NASA, under COTS/CRS-1 issued only two high-level requirements which had any effect on spacecraft size:- Minimum amount of pressurized cargo to be transported up to ISS.- Minimum amount of cargo missions to be flown.NASA did not require the COTS contractors to have their spacecraft be of a minimum size/weight. Had NASA really wanted the contractors' spacecraft to be of a certain minimal size than they would have issued a requirement for it. But NASA didn't.
Dragon is smaller than NASA really wanted for CRS, I don't see it being competitive for the Gateway missions...
Quote from: JohnFornaro on 06/18/2019 12:18 pmIn a way, that would be like starting to drive across Death Valley and not topping off your radiator or filling up the gas tank.If the person topping off your radiator insists that your vehicle must only take liquid helium as a coolant, that might not be insane.
In a way, that would be like starting to drive across Death Valley and not topping off your radiator or filling up the gas tank.
Quote from: Negan on 06/17/2019 10:56 pmQuote from: joek on 06/17/2019 09:09 pmWhy would SpaceX bother with this distraction?It's not a distraction. It's a payload for Chomper. Would be better to just use a Starship directly.
Quote from: joek on 06/17/2019 09:09 pmWhy would SpaceX bother with this distraction?It's not a distraction. It's a payload for Chomper.
Why would SpaceX bother with this distraction?
It's true that you could dock to ISS and have the crew transfer cargo, but that seems like a waste of astronaut time, and it seems less like providing NASA the service of moving cargo to Gateway if NASA employees (and a Cosmonaut or two for that matter) are doing part of the transport work
Quote from: JEF_300 on 06/18/2019 09:53 pmIt's true that you could dock to ISS and have the crew transfer cargo, but that seems like a waste of astronaut time, and it seems less like providing NASA the service of moving cargo to Gateway if NASA employees (and a Cosmonaut or two for that matter) are doing part of the transport workWhat about robotic transfer? Theres a few companies working on IVA robotics systems already, and I'd think cargo transfer (basically just "move this box from point A to point B") should be a lot easier than most other tasks they're looking at. Have an unmanned Dragon or Dream Chaser (sans expendable module) launch and dock directly to the PPE vehicle. No astronaut time needed, minimum of expendable hardware, and eliminating ISS from the equation means a different LEO staging orbit can be used (ISS is probably higher inclination and lower altitude than ideal)
Quote from: brickmack on 06/19/2019 10:23 pmQuote from: JEF_300 on 06/18/2019 09:53 pmIt's true that you could dock to ISS and have the crew transfer cargo, but that seems like a waste of astronaut time, and it seems less like providing NASA the service of moving cargo to Gateway if NASA employees (and a Cosmonaut or two for that matter) are doing part of the transport workWhat about robotic transfer? Theres a few companies working on IVA robotics systems already, and I'd think cargo transfer (basically just "move this box from point A to point B") should be a lot easier than most other tasks they're looking at. Have an unmanned Dragon or Dream Chaser (sans expendable module) launch and dock directly to the PPE vehicle. No astronaut time needed, minimum of expendable hardware, and eliminating ISS from the equation means a different LEO staging orbit can be used (ISS is probably higher inclination and lower altitude than ideal)My first thought upon reading this was "that's crazy." But the more I think about... I'm starting to really like this idea. Robotic transfer, while difficult, is certainly possible and could be helpful to NASA too. And if you use it, you get a rather nice architecture, almost elegant. Neat.
Or send a commercial astronaut up there to do cargo stowage, etc. May even be cheaper than developing a robotic IVA system.
Quote from: JEF_300 on 06/17/2019 09:37 pmI wonder if one of the PPE contractors will propose an Ion Cycler of some sort. Take your PPE design, have it pick up a pressurized cargo module and refuel in LEO, travel to the station over 3-6 months, and when it's done at the gateway, jettison the cargo module, return to LEO, and wait for a new shipment.All of the Gateway PPE losing bidders are planning to propose this, though as I mentioned upthread it seems SNC is the only one with much of a shot (if any). Don't need to jettison the cargo module, a PPE-sized propulsion module can easily do a round-trip LEO-cislunar-LEO mission with a Cygnus PCM/Dream Chaser expendable module/similar without expending anything. Bringing the cargo module back allows return payload capacity (via docking at ISS and handing samples off to some crew/logistics vehicle there), and reduces hardware cost (not just the pressure vessel, but docking hardware as well), and probably wouldn't be a 1:1 mass savings anyway since there now need to be detachable reusable interfaces between those modules, and the pressure vessel can no longer be used as a structural element (as on SNC's PPE).Transit time would probably be closer to 6 months each way than 3, based on previous studies of similarly-sized tugs with electric propulsion systems of comparable thrust and ISP. NASA requirement for the Gateway PPE was <100 days from launch to insertion at NRHO, but that was assuming a launch to at minimum a GTO-like trajectory, not starting in LEO. The first use of each unit could cut a lot of that outbound travel time out though, by launching directly to TLI (triple-reusable FH is easily big enough to throw any of the PPE concepts direct to TLI). So probably the first mission would be ~2 months from launch to first docking, then ~3 months at the Gateway for cargo transfer and whatever, ~6 months to return to LEO, 1 month at ISS for cargo transfer and refueling, ~6 months outbound, repeat.
I wonder if one of the PPE contractors will propose an Ion Cycler of some sort. Take your PPE design, have it pick up a pressurized cargo module and refuel in LEO, travel to the station over 3-6 months, and when it's done at the gateway, jettison the cargo module, return to LEO, and wait for a new shipment.
Flight rate is to low to justify Jupiter development costs. Would've viable for LEOs higher flight rate. May yet happen if we get commercial LEO stations.
Quote from: TrevorMonty on 06/22/2019 11:05 amFlight rate is to low to justify Jupiter development costs. Would've viable for LEOs higher flight rate. May yet happen if we get commercial LEO stations.A lot also depends on the size of cargo pod you deliver. Altius has looked a little at using something like our 75kg Bulldog servicing vehicle for delivering cargo pods, but that would be much smaller chunks than Jupiter (probably in the 200-500kg class). I think the trick would be finding a size where you could leverage a design that was useful for other stuff too, so that Artemis doesn't have to pay for the full development and fixed cost of the tug. But not throwing away a complex prox ops package/maneuvering vehicle every time has some real appeal to it. We looked at a variant of tugs in the Refueling Element proposal we put together for Orbit Beyond for the HLS BAA Refueling Element study. As it is, they didn't select our base study, just two of the prototypes. That could mean that they didn't like the concept of tugs, or already had someone else with a tug-based idea. ~Jon
It's too bad they're painting themselves into a corner with this RFP. Looking for something Cygnus sized, that does its own AR&D, has a 3yr lifetime on station, etc. Basically guaranteeing something that's going to cost a lot, and likely not have great pathways to lower cost in the future.~Jon
Quote from: jongoff on 06/27/2019 11:05 pmQuote from: TrevorMonty on 06/22/2019 11:05 amFlight rate is to low to justify Jupiter development costs. Would've viable for LEOs higher flight rate. May yet happen if we get commercial LEO stations.A lot also depends on the size of cargo pod you deliver. Altius has looked a little at using something like our 75kg Bulldog servicing vehicle for delivering cargo pods, but that would be much smaller chunks than Jupiter (probably in the 200-500kg class). I think the trick would be finding a size where you could leverage a design that was useful for other stuff too, so that Artemis doesn't have to pay for the full development and fixed cost of the tug. But not throwing away a complex prox ops package/maneuvering vehicle every time has some real appeal to it. We looked at a variant of tugs in the Refueling Element proposal we put together for Orbit Beyond for the HLS BAA Refueling Element study. As it is, they didn't select our base study, just two of the prototypes. That could mean that they didn't like the concept of tugs, or already had someone else with a tug-based idea. ~JonIt's too bad they're painting themselves into a corner with this RFP. Looking for something Cygnus sized, that does its own AR&D, has a 3yr lifetime on station, etc. Basically guaranteeing something that's going to cost a lot, and likely not have great pathways to lower cost in the future.~Jon
Question 2: When is the contractor required to have the one successful flight for CLIN 1 and three successful flights for CLIN 2?Answer 2: The Common Launch Vehicle Configuration is required to meet the successful flight requirements before each CLIN 1, GLS Mission, or CLIN 2, Specialized Delivery Mission. A Common Launch Vehicle Configuration which has not yet flown may be proposed. In this situation, the Offeror shall include a credible solution which shows how the minimum successful flight requirements will be met.Question 10: Can the one prior, or three prior, successful flight(s) of the commercial launch service be a Low Earth Orbit (LEO) flight or must it be a flight beyond LEO?Answer 10: The one, or three, successful flight(s) requirement of the Common Launch Vehicle Configuration can be a LEO flight.
Quote from: jongoff on 06/27/2019 11:10 pmIt's too bad they're painting themselves into a corner with this RFP. Looking for something Cygnus sized, that does its own AR&D, has a 3yr lifetime on station, etc. Basically guaranteeing something that's going to cost a lot, and likely not have great pathways to lower cost in the future.~JonI'm not following. What would cost less and have better pathways to a lower cost? It seems like they are taking ISS commercial resupply and taking it to the next step. Should be relatively incremental.