A aviation & planes forum. AviationBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » AviationBanter forum » rec.aviation newsgroups » Military Aviation
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Speed of design of airplanes.



 
 
Thread Tools Display Modes
  #23  
Old December 30th 03, 09:01 AM
Paul F Austin
external usenet poster
 
Posts: n/a
Default


"B2431" wrote in message
...
From: (WaltBJ)
Date: 12/29/2003 10:54 PM Central Standard Time
Message-id:

If you want a new airplane fast you find another Kelly Johnson and
give him the keys and the money and leave him alone.
(P80/F104/U2/A11/SR71) Nowadays there's too many cooks and too many
beancounters and too many can'tc--ts, as Hack would say. Where's
Kelly's DNA?
Walt BJ


I bet there are a few real Kelly Johnsons out there who can't get a fair

start
the way he did. He got his start when there just wasn't as much red tape

to
fight. I wonder how another one could get started when people actually

think
Moller can make his project work and send money his way instead of backing

the
real talent.

I would hate to think there's no current version of Kelly Johnson.


It doesn't take a "Kelly Johnson". Look at the list of great (and not so
great) combat aircraft that went from contract award to service in five
years or less in the fifties: _All_the Century series, F8U, B-52, A-3, A-4,
A-5... For that matter, I believe that the Polaris system went from
scratching heads to George Washington at sea in under five years.

What it takes is risk assumption rather than risk aversion. The keystone for
the endless development schedules are those GAO reports that claim that the
sky will fall if production is approved before the system is *perfect*.
During the fifties, it was assumed that the "A" model would enter production
quickly, get into the hands of users who would identify shortcoming that
would be fixed in the "B" model and the "C" model would be the volume
production item. Some aircraft suffered major design failures (F-100, B-52)
that required serious redesign and fleet rework but no one was given the
Chinese Refrigerator Factory Quality Incentive Program. In the long run, it
saves money.


  #24  
Old December 30th 03, 01:45 PM
John Bailey
external usenet poster
 
Posts: n/a
Default

On 30 Dec 2003 06:37:53 GMT, (B2431) wrote:

From:
(WaltBJ)
Date: 12/29/2003 10:54 PM Central Standard Time
Message-id:

If you want a new airplane fast you find another Kelly Johnson and
give him the keys and the money and leave him alone.
(P80/F104/U2/A11/SR71) Nowadays there's too many cooks and too many
beancounters and too many can'tc--ts, as Hack would say. Where's
Kelly's DNA?
Walt BJ


I bet there are a few real Kelly Johnsons out there who can't get a fair start
the way he did. He got his start when there just wasn't as much red tape to
fight. I wonder how another one could get started when people actually think
Moller can make his project work and send money his way instead of backing the
real talent.

I would hate to think there's no current version of Kelly Johnson.


I found Kelly Johnson's rules for running a skunk works at
http://www.geocities.com/CapeCanaver...993/rules.html They are a
good reality check on the following thoughts.

As designs get higher and higher tech, the problem with finding Kelly
Johnson's are the holes in the candidate's technological know-how. A
frequent hole is technology for developing large scale software
systems.

Scheduling is a more advanced for software than other disciplines,
even though when done badly software is the most uncontrolled
component of a project. According to Barry Boehm(
http://sunset.usc.edu/Research_Group/barry.html)
schedule is proportional to effort raised to an exponent the value of
which is a function of:
* Precedentedness--how new is it?
* Development Flexibility--can we adapt to new methods?
* Architecture / Risk Resolution--if it don't work, can we fix it?
* Team Cohesion--aka teamwork and the will to win.
* Process Maturity--have we done this enough to know what to do?

The overall equation works out roughly to T = k*p^1.4 where T is the
time in years, k is constant with dimensions: years/(persons^1.4), and
p is the total population of workers needed to complete the project.

Net net, designs take a long time because they use many people.
They need a lot of people because:
1) requirements are complex, requiring a large number of disciplines
2) there are too few skilled people to go around.
3) you can't trust incompetent people.
4) it takes even more incompetent people to check on incompetent
people.

John Bailey
http://home.rochester.rr.com/jbxroads/mailto.html
  #25  
Old December 30th 03, 01:48 PM
mah
external usenet poster
 
Posts: n/a
Default

WaltBJ wrote:

If you want a new airplane fast you find another Kelly Johnson and
give him the keys and the money and leave him alone.
(P80/F104/U2/A11/SR71) Nowadays there's too many cooks and too many
beancounters and too many can'tc--ts, as Hack would say. Where's
Kelly's DNA?
Walt BJ


For further on this, read Ben Rich's (memory failing here) "Skunk
Works". It talks about all the levels of red tape added during the
F-117 project compared to the SR-71.

MAH
  #26  
Old December 30th 03, 02:27 PM
Jeb Hoge
external usenet poster
 
Posts: n/a
Default

"Paul F Austin" wrote in message ...

It doesn't take a "Kelly Johnson". Look at the list of great (and not so
great) combat aircraft that went from contract award to service in five
years or less in the fifties: _All_the Century series, F8U, B-52, A-3, A-4,
A-5... For that matter, I believe that the Polaris system went from
scratching heads to George Washington at sea in under five years.


Well, part of that was the prevailing Cold War arms race "holy crap we
gotta stay ahead of the Russians" mentality, too. Not wanting to be
caught with your technological pants down when the balloon went up
served as a hell of a motivator for driving development as fast as it
could go, and also assuming a lot more risk and letting lives be more
at stake as long as the aircraft were being fielded and were ready to
fly when the call came.

We just flat-out don't have a fear factor like that now. If anything,
the scariest thing that we're facing is airframes fatiguing to pieces
in flight.
  #27  
Old December 30th 03, 03:31 PM
Ed Rasimus
external usenet poster
 
Posts: n/a
Default

On 30 Dec 2003 06:27:10 -0800, (Jeb Hoge) wrote:

"Paul F Austin" wrote in message ...

It doesn't take a "Kelly Johnson". Look at the list of great (and not so
great) combat aircraft that went from contract award to service in five
years or less in the fifties: _All_the Century series, F8U, B-52, A-3, A-4,
A-5... For that matter, I believe that the Polaris system went from
scratching heads to George Washington at sea in under five years.


Well, part of that was the prevailing Cold War arms race "holy crap we
gotta stay ahead of the Russians" mentality, too. Not wanting to be
caught with your technological pants down when the balloon went up
served as a hell of a motivator for driving development as fast as it
could go, and also assuming a lot more risk and letting lives be more
at stake as long as the aircraft were being fielded and were ready to
fly when the call came.

We just flat-out don't have a fear factor like that now. If anything,
the scariest thing that we're facing is airframes fatiguing to pieces
in flight.


I always like to watch a thread develop for a day or two before
dumping my two centavos into the mix.

It's hard to compare development cycles from WW II to Century Series
to Teen Fighters to today. While the old projects involved aerodynamic
development, then engines and T/W concerns, then shockwave management,
then agility, now the real issue isn't airplane but "weapon system."

This is one of the key reasons why the Luddites of the Legislature
occasionally suggest that tweaking 25 year old F-15s will be just as
good as buying new Raptors. "Why there's no difference in top
speed....why do you need an F-22?"

Today the airplane is only a small component. You need sensor suites
(lots more than beep-beep radar) and data fusion and stealth and
instrumentation and automation and who knows what else before the
weapon works.

Quite often the blank sheet of paper that a design starts with will
get redrawn thousands of times as technology advances, software
develops, concepts emerge, etc. Raptor is going to water a lot of eyes
when it finally goes operational and the fact that it's taken fifteen
years will soon be overlooked.


Ed Rasimus
Fighter Pilot (USAF-Ret)
"When Thunder Rolled"
Smithsonian Institution Press
ISBN #1-58834-103-8
  #28  
Old December 30th 03, 06:43 PM
Smartace11
external usenet poster
 
Posts: n/a
Default



Quite often the blank sheet of paper that a design starts with will
get redrawn thousands of times as technology advances, software
develops, concepts emerge, etc. Raptor is going to water a lot of eyes
when it finally goes operational and the fact that it's taken fifteen
years will soon be overlooked.


I worked on the ATF (soon to become F-22/F-23) engines in 1983!

Therein lies the catch. A lot of parts on the F-22 were obsolete 8 yrars ago,
like processors. The DoD used to be the largest source for electronics and the
biggest employer of software developers. Now it is just a drop in the bucket
and all the latest technology in both hardware and software goes to the
entertainment industry. We couldn't even get software peiople for the B-2
because Hollywpod was hiring them all at ten times teh salary DoD was paying.


More reasons why the development cycle is as long as it is..


  #30  
Old December 31st 03, 05:43 PM
Joe Osman
external usenet poster
 
Posts: n/a
Default

Smartace11 wrote:


Quite often the blank sheet of paper that a design starts with will
get redrawn thousands of times as technology advances, software
develops, concepts emerge, etc. Raptor is going to water a lot of eyes
when it finally goes operational and the fact that it's taken fifteen
years will soon be overlooked.


I worked on the ATF (soon to become F-22/F-23) engines in 1983!

Therein lies the catch. A lot of parts on the F-22 were obsolete 8 yrars ago,
like processors. The DoD used to be the largest source for electronics and the
biggest employer of software developers. Now it is just a drop in the bucket
and all the latest technology in both hardware and software goes to the
entertainment industry. We couldn't even get software peiople for the B-2
because Hollywpod was hiring them all at ten times teh salary DoD was paying.


More reasons why the development cycle is as long as it is..


With all the programming jobs going to India and Russia, the
defense jobs may be the only ones left for US programmers.
Or have they figured out how to offshore them also?

Joe


-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Homebuilt Aircraft Frequently Asked Questions List (FAQ) Ron Wanttaja Home Built 0 December 2nd 04 07:00 AM
amateur design consultant? Shin Gou Home Built 14 June 30th 04 01:34 AM
Homebuilt Aircraft Frequently Asked Questions (FAQ) Ron Wanttaja Home Built 0 June 2nd 04 07:17 AM
Homebuilt Aircraft Frequently Asked Questions (FAQ) Ron Wanttaja Home Built 1 January 2nd 04 09:02 PM
Homebuilt Aircraft Frequently Asked Questions (FAQ) Ron Wanttaja Home Built 4 August 7th 03 05:12 AM


All times are GMT +1. The time now is 08:09 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 AviationBanter.
The comments are property of their posters.