Is it just me, or is there a pattern developing here?

[Rick]

Ask anyone who worked OSP

Me2,

I do work at KSC. I support Shuttle and ALSO support Ares. As you would say: "Wrong".

Your information is totally incorrect. I guess it depends who one wishes to believe. A vast majority who supports the right thing to do, or a SMALL minority who is anti-stick.

To me, its a no brainer.

[Me2]

Me2,

I do work at KSC. I support Shuttle and ALSO support Ares. As you would say: "Wrong".

Your information is totally incorrect. I guess it depends who one wishes to believe. A vast majority who supports the right thing to do, or a SMALL minority who is anti-stick.

To me, its a no brainer.

The stick is an unnecessary duplication of effort, waste of resources and a jobs program. If your job wasn't on the line you would come to the same conclusion. The "vast majority" of KSC workers have no clue about launch vehicle architectures and launch vehicle design. Most of KSC was not involved with the ESAS and doesn't even know what the ESAS is. They only know their pocket books and to do what JSC and MSFC tell them to do. Griffin has stated that the goal of the ESAS was 10 healthy centers. The goal should be maximizing the tax payers money, which means launch vehicles that are more effient and use less labor. That excluded shuttle derived vehicles. What would be better for the nation is not good for Brevard County.

My information is correct and comes from JSC/MSFC CxP data (not KSC CxP data).

[Andrew]

The stick is an unnecessary duplication of effort, waste of resources and a jobs program. If your job wasn't on the line you would come to the same conclusion.

Even though I already know the answer, I'll leave it to Rick to tell you what his job is and isn't relying on. To give you a hint, though, you are "wrong."

The "vast majority" of KSC workers have no clue about launch vehicle architectures and launch vehicle design. Most of KSC was not involved with the ESAS and doesn't even know what the ESAS is. They only know their pocket books and to do what JSC and MSFC tell them to do.

Forgive me, but you just got done saying that we should ask around OSB. You even confirmed that by saying some of them "are at KSC" and that "Since you are at KSC, you should know the organization that they are part of."

Were you mistaken, then?

My information is correct and comes from JSC/MSFC CxP data (not KSC CxP data).

Well, I know several people at JSC who agree with Rick and me. Do you want to revise your position that you weren't referring to JSC, either, and only to MSFC? Because McDade knows plenty 'o folks up there and can shoot down that third iteration of your hypothesis, as well.

-Andrew

[Rick]

The stick is an unnecessary duplication of effort, waste of resources and a jobs program. If your job wasn't on the line you would come to the same conclusion. The "vast majority" of KSC workers have no clue about launch vehicle architectures and launch vehicle design. Most of KSC was not involved with the ESAS and doesn't even know what the ESAS is. They only know their pocket books and to do what JSC and MSFC tell them to do. Griffin has stated that the goal of the ESAS was 10 healthy centers. The goal should be maximizing the tax payers money, which means launch vehicles that are more effient and use less labor. That excluded shuttle derived vehicles. What would be better for the nation is not good for Brevard County.

My information is correct and comes from JSC/MSFC CxP data (not KSC CxP data).

Me2,

Forgive me, but you might want to know the facts prior to making assumptions, which you evidently know little to nothing about.

My job is NOT on the line at Kennedy, as I am a "site" person, which means I am not tied to any contract.

For a change in this thread, here are specifics about my job(s) at KSC.

Programs I support:

STS. Specifically in FSSO.

ISS. IT support for contractor and NASA technicians and quality control.

GPS. Support regarding both IT and general photographic support.

Ares I. Support for both the upper stage and IU.

I do find your remarks indicating that KSC employee"s in general haven't a clue insulting at best. There are monthly "All Hands" meetings that update employee's about Ares I and V with REAL timelines. Have you attended any of these at KSC?

Further, hundreds of employees have filtered into Ares, many have relocated to support the program.

I respect your objections, but see little evidence that you've provided other than personal opinion to justify your anti-stick position.

If you could, please provide factual information, that can be validated instead of assumtions that you cannot prove it would help your cause in my opinion.

By the way, what do you do as a NASA civil servant and where do you work?

[Spacenut]

rick, I am not surprised you did not get an answer to this one. Me2 seems to pick the posts he wants to respond to, and not others which is ashame!!!

[Me2]

Programs I support:

STS. Specifically in FSSO.

ISS. IT support for contractor and NASA technicians and quality control.

GPS. Support regarding both IT and general photographic support.

Ares I. Support for both the upper stage and IU.

So in 2010, no shuttle means no FSSO, No shuttle means no Boeing ISS support needed. And if Ares I goes away, you only have GPS to rest on

[Rick]

So in 2010, no shuttle means no FSSO, No shuttle means no Boeing ISS support needed. And if Ares I goes away, you only have GPS to rest on

In a worst case scenario as you outline, yes, you are correct.

One thing that many, except friends of mine at work and personally know about me is that I've never thought that working at KSC would be a permanent job.

All the years I've worked there I've considered working for the space program a privilage. It was my choice to begin working there years ago, and I could have, if I wanted to seek work elswhere.

If I leave, or am laid off, I'd consider my time at KSC a great ride.