But, it's not 180M a launch, is it? In fact when you add the government's total EELV cost during this block buy divided by the number of launches, it's going to be more than twice that much.
Quote from: Nomadd on 08/14/2012 08:14 pm But, it's not 180M a launch, is it? In fact when you add the government's total EELV cost during this block buy divided by the number of launches, it's going to be more than twice that much.Right. One report mentioned $19 billion for 46 launches ($413 million each). Another mentioned $15 billion for 40 launches ($375 million each). The total reportedly only includes four Delta 4 Heavy launches during the 2013-2017 span. These totals likely include the launch readiness contract costs. - Ed Kyle
But the fact is, an Iridium like constellation would serve a lot of needs better than a geo sat ever could. But not at $180 million a launch.
Quote from: Nomadd on 08/14/2012 08:14 pmBut the fact is, an Iridium like constellation would serve a lot of needs better than a geo sat ever could. But not at $180 million a launch. Not really. That is only a small part of the DOD needs.
Quote from: Jim on 08/15/2012 01:11 pmQuote from: Nomadd on 08/14/2012 08:14 pmBut the fact is, an Iridium like constellation would serve a lot of needs better than a geo sat ever could. But not at $180 million a launch. Not really. That is only a small part of the DOD needs. Say that the next time you're trying to hold a conversation with a half second delay while under fire, or control some device in real time.
ULA fighting back against efforts to stop block buy.http://blog.al.com/space-news/2012/08/ula_asks_us_rep_mo_brooks_for.html"We welcome the competition," ULA production manager Daniel Caughran told Brooks." Interesting info in this report included the following:"ULA Chief Operating Officer Dan Collins said the plant is ramping up production from eight rockets a year to 12 or 13."and "During Thursday's tour, Brooks saw two Atlas rockets in final stages of assembly and one massive Delta IV. News photographers were allowed to take pictures of the Atlas boosters, but not the Delta. Defense Department security regulations and federal law prohibit assembly images, plant security said."Strange, that last bit. Can't take a picture of a rocket that will, ultimately, stand on a launch pad for all to see? - Ed Kyle
Or is there in fact some objective set of standards for what they are paying for like multiple independent inspections and tests of everything?
Not a set of standards, but the ability to see all test data and analyze it independently. Not just for the vehicles that they are flying but for the whole fleet.
If SpaceX had:A. A proven track recordB. Didn't blow up engines in flight.I might be ok with this. But because of that, and because of the far longer and more extensive record of the EELV vehicles this strikes me as nothing more then politics at their worst intruding into things......again. Seems like an obama gambit to put "new space" ahead again. I don't mind competition, especially when SpaceX is involved, but in this case they just don't have the credentials to warrant this, IMO. We'll just have to see how this works out.
Just curious about what the military is really buying when they are paying for "can't fail" levels of reliability in launchers. Obviously the launchers can in fact fail no matter how many dump truck loads of cash they burn to propitiate the rocket gods.
Quote from: Jim on 08/29/2012 06:06 pmNot a set of standards, but the ability to see all test data and analyze it independently. Not just for the vehicles that they are flying but for the whole fleet.I think that's a better description than the GAO got out of ULA on the subject. It sounds like what you're mostly buying is an assurance that a) the supplier will take detailed records (of both tests but also parts mfg and assembly) and b) Storing all that data in case you want to analyze it later Which sounds a pretty expensive bill for things the business *should* be doing to improve its products anyway + archiving it just in case. Back when the cutting edge of document storage was manually copied microfilm and test results really *were* spools of papers from chart recorders that *may* have been defensible. But 10s of $m ? Either ULA are doing *very* sophisticated processing (lots of human intervention and processing time) on this data before putting it in storage or the mfg/test of an LV generates literally TB of data.Either (both) is possible but they just seem *very* unlikely.
No, it is also the additional human interaction with the customer. It takes many addtional MTS to deal with the customer requests.
Which suggests *standardized* meeting and data formats and probably support tools to assist them. Also as this a FAR process (mission assurance is a cost plus element of the contract according to the GOA) doesn't the govt have substantial access to the contractors database by default already?Your description makes it sound *much* more ad hoc, with govt officials rounding up people and asking them for data more or less at random, rather than getting it themselves given their access to the contractor systems.
It isn't data in databases nor "govt officials". The gov't gets all the flight data, standard analyses and participates in standard reviews. It is more about the off nominal stuff were the engineers asking why did this happen or what are you going to do fix this or prevent this from happening.Also, still providing access to databases and such still requires manpower.
Quote from: Jim on 10/25/2012 10:04 amIt isn't data in databases nor "govt officials". The gov't gets all the flight data, standard analyses and participates in standard reviews. It is more about the off nominal stuff were the engineers asking why did this happen or what are you going to do fix this or prevent this from happening.Also, still providing access to databases and such still requires manpower.I'm still have trouble understanding the *scale* of these costs. An engineer working a 40 hour week is 2080 hrs a year.The Bureau of Labor Statistics reckons about $50 an hour salary for an aerospace engineer. http://www.bls.gov/oes/current/oes172011.htmBut IIRC the rule of thumb is all support expenses make their costs *double* their salary. So 2080hs @ $100/hr gives $208k/yrso $100m buys 480 *full* time engineers to work on nothing but "mission assurance"However if I'm 100% out that $100m would only buy 240 engineers.Which might be OK except Spacex build 80% of their launch vehicles with 1600 staff *total*. While I can understand *payloads* are different (possibly radically so) the core *functions* of the LV's (and their major sub assemblies) are essentially the *same*. I would therefor expect that just as the LV's are "modular" in terms of engines, stages, strapons so each major component has a standard chunk of "mission assurance" that is assembled with it as the LV for a particular payload is assembled.
Quote from: john smith 19 on 10/27/2012 06:37 pmI'm still have trouble understanding the *scale* of these costs. An engineer working a 40 hour week is 2080 hrs a year.The Bureau of Labor Statistics reckons about $50 an hour salary for an aerospace engineer. http://www.bls.gov/oes/current/oes172011.htmBut IIRC the rule of thumb is all support expenses make their costs *double* their salary. So 2080hs @ $100/hr gives $208k/yrso $100m buys 480 *full* time engineers to work on nothing but "mission assurance"However if I'm 100% out that $100m would only buy 240 engineers.Which might be OK except Spacex build 80% of their launch vehicles with 1600 staff *total*. While I can understand *payloads* are different (possibly radically so) the core *functions* of the LV's (and their major sub assemblies) are essentially the *same*. I would therefor expect that just as the LV's are "modular" in terms of engines, stages, strapons so each major component has a standard chunk of "mission assurance" that is assembled with it as the LV for a particular payload is assembled. Engineers straight out of college may have a salary around 50K/yr, but that can't be the industry average. Besides, that's just their salary. You forget about the benefits cost, plus the standard overhead costs of having an employee, like office space, office equipment (including computers, software, etc), the employers share of payroll taxes, etc. Besides, just running the quality operation itself is expensive. What do you think it costs every time SpaceX test fires an engine in Texas ? I'm sure it's not gas it up and go. And even with their quality processes, they aren't finding all the manufacturing / assembly flaws. You could argue that SpaceX needs to spend more on mission assurance.
I'm still have trouble understanding the *scale* of these costs. An engineer working a 40 hour week is 2080 hrs a year.The Bureau of Labor Statistics reckons about $50 an hour salary for an aerospace engineer. http://www.bls.gov/oes/current/oes172011.htmBut IIRC the rule of thumb is all support expenses make their costs *double* their salary. So 2080hs @ $100/hr gives $208k/yrso $100m buys 480 *full* time engineers to work on nothing but "mission assurance"However if I'm 100% out that $100m would only buy 240 engineers.Which might be OK except Spacex build 80% of their launch vehicles with 1600 staff *total*. While I can understand *payloads* are different (possibly radically so) the core *functions* of the LV's (and their major sub assemblies) are essentially the *same*. I would therefor expect that just as the LV's are "modular" in terms of engines, stages, strapons so each major component has a standard chunk of "mission assurance" that is assembled with it as the LV for a particular payload is assembled.
But IIRC the rule of thumb is all support expenses make their costs *double* their salary. So 2080hs @ $100/hr gives $208k/yrso $100m buys 480 *full* time engineers to work on nothing but "mission assurance"However if I'm 100% out that $100m would only buy 240 engineers.
Engineers straight out of college may have a salary around 50K/yr, but that can't be the industry average. Besides, that's just their salary. You forget about the benefits cost, plus the standard overhead costs of having an employee, like office space, office equipment (including computers, software, etc), the employers share of payroll taxes, etc.
Quote from: john smith 19 on 10/27/2012 06:37 pmBut IIRC the rule of thumb is all support expenses make their costs *double* their salary. So 2080hs @ $100/hr gives $208k/yrso $100m buys 480 *full* time engineers to work on nothing but "mission assurance"However if I'm 100% out that $100m would only buy 240 engineers.Which would be $200/hr.Quote from: Lurker Steve on 10/27/2012 09:13 pmEngineers straight out of college may have a salary around 50K/yr, but that can't be the industry average. Besides, that's just their salary. You forget about the benefits cost, plus the standard overhead costs of having an employee, like office space, office equipment (including computers, software, etc), the employers share of payroll taxes, etc.What the problem is? Seems like he made an effort to suggest an industry average, already including the costs you mention.
What the problem is? Seems like he made an effort to suggest an industry average, already including the costs you mention.
but if we go with the cost for the *top* 10% of aerospace engineers $71.06/hr. *doubling* that to account for benefits and support costs gives $142.12. A 40 hr week at that rate gives $295609.6
ULA has around 3500 people for two launch sites, 5 pads, 3 launch vehicle families and integration efforts for around 30 different spacecraft.
There isn't provision for survival through a year that has more costs than revenues. ULA dosn't get to keep and reinvest its profits.
The comment here is that ULA recieves a yearly $650M launch assurance contract that would cover the cost of all of ULA's employees salaries and overhead. This ensures ULA dosn't have to fire anybody because it isn't launching often enough, or even at all. ULA is basiclly a cash basis operated company, it must maintain a positive profit. There isn't provision for survival through a year that has more costs than revenues. ULA dosn't get to keep and reinvest its profits.The charges per launch vehicle would be for those purchases for parts and services that ULA pays someone else to provide.
*mission* assurance is the per mission costs to improve mission reliability which is broken out as a separate cost plus contract (apart from the LV purchase, which is fixed price)
My company uses a standard engineering cost of around 125-135/per man hour. That just a fully loaded estimate for covering salary / benefits / and the facility overhead.
But IIRC the rule of thumb is all support expenses make their costs *double* their salary. So 2080hs @ $100/hr gives $208k/yr
Quote from: Lurker Steve on 10/28/2012 05:18 pmMy company uses a standard engineering cost of around 125-135/per man hour. That just a fully loaded estimate for covering salary / benefits / and the facility overhead. Fine, but I'm still not getting it.BTW, when I do this sort of figuring, I use 2000 hours; it includes a two week vacation, and is easier for me to multiply by 2.Anyhow, John Smith was starting out at $50/hr, which is a hundred grand a year; doubled to two hundred grand, in the ballpark of your two hundred fifty to two hundred seventy grand.I took his number to roughly mean an average or maybe a median cost, some higher, some lower. I took his term "all support services" to be roughly equivalent to our term "fully burdened".Quote from: john smith 19 on 10/27/2012 06:37 pmBut IIRC the rule of thumb is all support expenses make their costs *double* their salary. So 2080hs @ $100/hr gives $208k/yrEven then, you think his estimate is too low?
Quote from: Jim on 10/27/2012 07:25 pmULA has around 3500 people for two launch sites, 5 pads, 3 launch vehicle families and integration efforts for around 30 different spacecraft.The comment here is that ULA recieves a yearly $650M launch assurance contract that would cover the cost of all of ULA's employees salaries and overhead.
Which sounds a pretty expensive bill for things the business *should* be doing to improve its products anyway + archiving it just in case.
$650M / 3500 = $185K/yr.Whether they launch or not? And launch costs are added to this?
Isn't this $650M an expensive bill?
Why is it necessary, other than from ULA's parochial viewpoint of profitability, to grant them a monopoly for more than three years?
But seriously, the 3500 employees to keep the hardware in a "useable" state whether or not they launch has got to be an excessive cost. Is it the case that if they do launch something, they must hire additional people, since the 3500 are maintaining this hardware are kept employed full time at that effort?That cannot be.
If this is not a sort of economic blackmail, then what would it be called?
Quote from: JohnFornaro on 10/28/2012 02:58 pmWhat the problem is? Seems like he made an effort to suggest an industry average, already including the costs you mention.The source of my numbers washttp://www.bls.gov/oes/current/oes172011.htm#topbut if we go with the cost for the *top* 10% of aerospace engineers $71.06/hr. *doubling* that to account for benefits and support costs gives $142.12. A 40 hr week at that rate gives $295609.6 [edit] per year.so (assuming you're team is *exclusively* composed of aerospace engineers at the top 10% of the industry pay scale on *nothing* but "mission assurance" $100m gets you 338 engineers a year.Caveats. I'm not an American so I cannot confirm that the "fully burdened" cost of an employee is 2x their annual salary. I can't remember where I saw that figure as a rule of thumb and I could be wrong. Increasing the multiplier (the direction I would *expect* it to go) would reduce the number of engineers.but that is still one *hell* of a lot of variance between launches needing *all* this one off attention.
As to whether [heh] $650m is fair or not it seems the USAF waived its right to detailed cost data at certain stages (GAO 12-822, 11-641, 08-1039) so it's a bit difficult to tell, although this appears to be changing. One of the key drivers of the ULA merger was that Lockheed agreed to drop its lawsuit on how Boeing acquired about 5000 pages of its internal proprietary documentation. DoD had the choice of having its 2 key LV suppliers tear themselves to pieces in the courts or join hands and let bygones be bygones. They chose the latter and got the FTC agree.
What GAO Recommends (September 2008)GAO recommends the Secretary of Defense take actions to: ensure the regular reporting of key information on program status, produce an independent life-cycle cost estimate, and ensure the program’s staffing meets its needs. DOD concurred with the recommendations. ...The EELV program currently faces uncertainties in the reliability of the vehicles used to launch military and other government spacecraft as well as its budget for future years and in the merger of its two principal suppliers. Taken together, these unknowns require careful monitoring and oversight to ensure a fairly long track record of launch successes can continue.
What GAO Recommends (September 2011)Among other things, GAO recommends DOD assess engine costs and mission assurance activities, reassess the length of the proposed block buy, and consider how to address broader launch acquisition and technology development issues.DOD generally concurred with the recommendations. ...What GAO FoundDOD officials believe the launch industrial base is unstable and plan to implement an acquisition strategy they believe will help stabilize it. The leading proposal would commit the government to a block buy of eight common booster cores—the main component of a launch vehicle—each year, for a 5-year term. However, this approach may be based on incomplete information and although DOD is gathering data that it needs as it finalizes the new acquisition strategy, some critical knowledge gaps remain.
What GAO Recommends (08-13-12)GAO is making no new recommendations in this report. DOD reviewed and concurs with this report. ...Ensure launch mission assurance activities are sufficient and not excessive, and identify ways to incentivize the prime contractor to implement efficiencies without affecting mission success as DOD develops a new contracting structure for the EELV programSome action taken; more action needed
But we still don't know if "launch mission assurance activities are sufficient and not excessive", do we? After four years of round the clock work, by one guy: the Program Executive Officer for Space Launch. "More action needed." Sheesh.
Quote from: JohnFornaro on 10/30/2012 01:07 pmBut we still don't know if "launch mission assurance activities are sufficient and not excessive", do we? After four years of round the clock work, by one guy: the Program Executive Officer for Space Launch. "More action needed." Sheesh.He *might* have a few assistants.
After four years of work on launch mission assurance, more action is still needed, and launch mission assurance is by no means guaranteed by the corporation. So far, it appears that that action will cost more than $650M/yr. Since the work is still not complete, and the issuance of a deadline is assiduously avoided by the PEV in question, it is not yet clear how much more money is needed to "incentivize" the private corporation in question.
A suspicious person might get the idea the DoD was not trying very hard to find out exactly how this money is being spent.