Not Just Healthcare.gov: NASA Has 'Significant Problems' With $2.5B IT Contract
schwit1 writes "According to the Inspector General, NASA and HP Enterprise Services have encountered significant problems implementing the $2.5 billion Agency Consolidated End-User Services (ACES) contract, which provides desktops, laptops, computer equipment and end-user services such as help desk and data backup. Those problems include 'a failed effort to replace most NASA employees' computers within the first six months and low customer satisfaction,' the report states (PDF). It adds that NASA lacked the technical and cultural readiness for an agencywide IT delivery model and did not offer clear contract requirements, while HP failed to deliver on multiple promises."
And I hate beta
This is what happens when you under fund the IT budget, and put in management positions MORONS that do not have a strong IT background. If the IT director can not build a pc by hand from parts and then not only install the OS, but all the drivers and then configure it completely, then configure a Cisco switch and router, he is not fit to be in a management role of IT.
Yet corporations and the Government instead put people with ZERO clue about IT to begin with in the role of management and upper management.
Do not look at laser with remaining good eye.
I've got to say that the initial post on this topic perpetuates one of the paradigms that is sticking in the craws of Slashdot users. We are not an audience. We might be users, we might be members, we most certainly are contributors. But we are not an audience.
If you persist in thinking of us that way, then you're going to get it wrong. You serve an audience differently than you serve contributing members of a community. Most of the complaints hinge on that difference.
If we were an audience, we'd be coming here for the articles. Most of the complaints are about the comment system, how difficult it is to follow a conversation, how difficult it is leave a comment, etc. I come here, most of us come here, to read what my/our fellow slashdotters have to say. The value here is the community, and the most important contributors are other members, not the site or the editors.
If you don't get that straight, then you aren't going to "get" why we're upset, so there's no chance that you'll deliver us something that we can live with. And that community is going to vanish, leaving you with nothing of value.
You can take suggestions and maybe reduce the implosion, but unless you understand *why* we're upset, you're going to be heading in fundamentally the wrong direction.
Those problems include 'a failed effort to replace most NASA employees' computers within the first six months and low customer satisfaction,'
Those problems include 'a failed effort to replace all Slashdot contributors' commenting system within the first four months and low customer satisfaction.
At least they didn't hire Dice to do their site's redesign.
NASA: We want you to make our computers awesome.
HP: How awesome?
NASA: The awesomest!
HP: So how awesome is awesomest?
NASA: As awesome as you can make it.
HP: Okay, that'll be two billion dollars.
NASA: Deal! Yay we get awesome new computers, and an an awesome new software system, that will do all sorts of cool things like be our ERP solution and our CAD software and our entire core infrastructure solution...
HP: Yay, we just made a ton of money! So.... what exactly did they want again?
Occasionally living proof of the Ballmer peak.
I can't stand the new Slashdot. I hate being referred to as "Audience" when we are making this site happen. If I wanted CNET, I'd go to CNET.
No need rocket science like NASA to have significant problems, slashdot did it with (fuck)beta!
Sorry - I don't understand the article. Too much text on the page confuses me.
Please could you re-print it with double-line spacing and a large bit of generic stock photography of a rocket or something so I know what it is about?
Maybe a big chunk of white-space at the top so I'm not confronted with a whole paragraph of text on the first screen.
Also, the screen appeared too suddenly and made me jump - which is dangerous because today is my first day wearing my big boy pants. Maybe more javascript effects would slow it down?
Yours,
A.N. Audience
In a survey of 100 programmers, 111111 thought that duck-typing was a good idea.
Dnot 4git 2 h8 BETA 2! b/c BETA sux baw1sax
Imagine you're a NASA worker with a nice (albeit old) Macbook computer to do your work on.
Some schmuck walks up to you with a brand new hp laptop with Windows 8 on it to replace your Mac.
I fail to see the scenario where the NASA worker _shouldn't_ enthusiastically shun the "helper" from hp.
When the choice is between something nice and functioning and a crappy os on a crappy piece of hardware, the choice is easy.
The problem with these "one size fits all" contracts is that one size does not fit all situations ever.
If hp wants to make this contract successful they should be forced to offer multiple options through multiple vendors where they take a cut to manage the maintenance and configuration of any of the possible selected systems.
HP FAILED to live up to their contractual obligations and we're blaming government?
FUCK THIS SITE.
Please post this to new articles if it hasn't been posted yet. (Copy-paste the html from here so links don't get mangled!)
On February 5, 2014, Slashdot announced through a javascript popup that they are starting to "move in to" the new Slashdot Beta design. Slashdot Beta is a trend-following attempt to give Slashdot a fresh look, an approach that has led to less space for text and an abandonment of the traditional Slashdot look. Much worse than that, Slashdot Beta fundamentally breaks the classic Slashdot discussion and moderation system.
If you haven't seen Slashdot Beta already, open this in a new tab. After seeing that, click here to return to classic Slashdot.
We should boycott stories and only discuss the abomination that is Slashdot Beta until Dice abandons the project.
We should boycott slashdot entirely during the week of Feb 10 to Feb 17 as part of the wider slashcott
Moderators - only spend mod points on comments that discuss Beta
Commentors - only discuss Beta
http://slashdot.org/recent - Vote up the Fuck Beta stories
Keep this up for a few days and we may finally get the PHBs attention.
-----=====##### LINKS #####=====-----
Discussion of Beta: http://slashdot.org/firehose.pl?op=view&id=56395415
Discussion of where to go if Beta goes live: http://slashdot.org/firehose.pl?op=view&type=submission&id=3321441
Alternative Slashdot: http://altslashdot.org (thanks Okian Warrior (537106))
Captcha: Overtake
The report further states that "poor implementation by HP on important aspects of the contract and inconsistent oversight by NASA" have contributed to the failings.
And this looks like NASA allowed HP to run over them.
Although, this being Government and HP being very well connected, I can just imagine a NASA manager trying to hold HP to their obligations only to have HP have one of their bitches in Congress bitch slap the NASA manager down.
I see a wonderful spaceship crashing on a planet in slow motion...
This is Slashdot, poisoned by the silly beta that brings buck feta comments in every story
All stories are contaminated, even if there is a main topic for complaining and suggesting improvements or "abandon the beta" advice.
We need to stop this.
Stop redirecting to the beta.
Stop filling stories with buck feta comments.
'nuff said
This from an organization that, when they recently redesigned their website, *still* didn't get around to forwarding http://nasa.gov/ to http://www.nasa.gov? Who would've thought?
One wonders if the government will start insourcing IT projects again since their outsourced service providers seem to suck.
Hail Eris, full of mischief...
E pluribus sanguinem
They'd have it implemented already whether you wanted it or not.
That's kind of unfair. It does not help to rave here anymore. I'm sure that by now the Slashdot crew is perfectly aware of the disaster which the Beta is according to users. Right now we have to wait a bit and see if they actually start fixing stuff, which Timothy just tried to convince us about. They cannot add the new code overnight.
Adblock Slashdot until DICE kills Beta!
Shut up
http://beta.slashdot.org/story/197857
Don't forget to renew that failed contract. If you don't have a contract or warranty active they'll charge you for things as simple as firmware downloads for the hardware they couldn't get delivered and configured on time.
I was reading this review of Slashdot Beta made last October, which shows a variety of screenshots and also has explanations from Timothy in it.
http://www.tweaktown.com/news/33368/slashdot-launches-redesigned-website-in-beta-form-we-check-it-out/index.html
Honestly, I was impressed by at least some of the reasoning, and I can see how some changes would actually be positive. The problem, though, is that not all the changes are good, and it's far too much at once. There is a potential to lose what is special about Slashdot including its moderation system. They need to examine Beta and see and what needs to change for it to be accepted by the Slashdot community. Off the top of my head:
Here's a real and serious recommendation for Timothy if he wants Beta to eventually succeed without disrupting the Slashdot community: do redirections one day out of the week, and on that one day, have a story posted by Timothy asking the community for feedback -- one day each week for experimentation ("Slashdot Labs Day"). Then for the next 6 days, they can fix the site, while readers continue to use the classic interface. Keep doing that until the big problems in Beta are ironed out and the community is halfway satisfied with it. That is seriously a simple and reliable way that they could fix this and make people happy again. You can take that one to the bank. Unfortunately I don't know if they have the sense to do so because they haven't accepted feedback very well and they haven't kept in contact with the community.
Systemd: the PulseAudio of init systems
on coming up with an acronym and not enough on proper planning and execution. This seems to be an endemic problem with our government. Beaurocracy at its best!
"If you like Slashdot classic you can keep Slashdot classic. Period."
The funny thing is that for all this talk about "We're going to make changes based on your input" horseshit, I would almost be willing to bet that they hired a contractor to do the redesign and that he's already fulfilled his contract and left. I bet that they don't even have the capacity to change the design significantly at this point without hiring a new contractor to do it.
The cow says "Moo." The dog says "Woof." The Timothy says "Thanks, valued customer. We appreciate your input."
In a sense, this is "look how incompetent the government is at implementing tech" story, but in another this could be interpreted as an attempt to trivialize what happened with healthcare.gov. "Oh gosh, nothing ever goes right for the government so what happened with healthcare.gov is par for the course (shrug)."
Except the healthcare.gov disaster was LEGISLATIVE, the constant, ongoing, still-unresolved tech catastrophe was only the impact-crater.
The fact that NASA's computer-replacement program was a boondoggle was meaningless, compared to the tech-failure of a program whose use was MANDATED by law.
-Styopa
...it's like some kind of beta or something.
And Slashdot Beta is a disaster of a project too ...
Was it done by the same contractors for Healthcare.gov? No, it was mandated by clueless Dice executives ...
Anyone who sees this kind of backlash should immediately back off, not just say : "We are staying the course ..." GWB style ...
2bits.com, Inc: Drupal, WordPress, and LAMP performance tuning.
Alpha will be a step in the right direction.
A change of course can be made overnight. There has been no commitment to maintain what the community that creates this site on a daily basis requires.
If you think fixing the unspeakable new site with new code is an option, you probably don't understand the fundamental problems with it, aside from the look and feel. It ain't Slashdot. That's the problem.
That drivel "we are not an audience" keeps getting repeated. Yes, you are an audience.
If you get your news from CBS or the BBC, are you a community or a user or member? Hardly, you are an audience, plain and simple.
Then how come, if you get news from slashdot, you are not an audience?
Right now we have to wait a bit and see if they actually start fixing stuff, which Timothy just tried to convince us about. They cannot add the new code overnight.
They don't need to add any new code, they just need to delete all the Beta code.
It's not about making the Slashdot crew aware of the disaster that Beta is - it's about making them aware that IT IS THE USERS OF THIS SITE THAT CREATE THE FUCKING CONTENT!
Wtf is this? Worst mobile design EVER!
That's what happens when you fire all the good people.
HP already has an absolutely TERRIBLE reputation from managing the navy and marine corps networks. they are TERRIBLE.
Basically ANY time you bring a government into the mix, you get massive cost multiplications, shitty design, worse implementation, and just all-around craptastic workmanship. Meanwhile, everyone sits there, pointing fingers at everyone else.
And don't even get me started on graft and corruption.
Seriously, look at fucking social security in this country. The coffers for SS have been robbed from so much that there just isn't money enough to continue supporting the program. But it's a massive cash influx for Uncle Sam. So they're not going to get rid of it. They'll keep milking it until it collapses under its own weight.
And that's basically what's going to happen with OhBlahBlahCare as well.
Chas - The one, the only.
THANK GOD!!!
Not sure who chose to higher IT. Because thats where the blame should be. Before HP had the contract, it was Dell and Lockheed Martin/EMCO handled hiring. Once they lost the contract, it switched to HP and they hiring went to company Metters, i believe, and they started hiring no experience IT at near min. wage. That is more likely the cause from my experience out at NASA.
Hi there -- this is Tim ("timothy" - posting anon because in a new browser, and because the site should work for anon. readers!), and I'd like to suggest you ask questions / make suggestions in the story posted yesterday *about* the beta instead. However, I know it's frustrating.
That said, you're right. Direct linking to comments is something that should arrive soon -- maybe not soon enough, I realize, but it's something that got pushed down the stack for too long. Yes, comments must be directly linkable, and they will be. This kind of tire-kicking (with readers actively poking) is what reveals the things that have been neglected in the design.
*This* discussion isn't the right place for a beta features discussion, though (so I'm intentionally not going to extend this thread beyond this current comment); this one is: http://meta-beta.slashdot.org/story/14/02/06/2329227/slashdot-tries-something-new-audience-responds :)
(And of course, email to feedback@slashdot.org, or comment on the blog posts at http://slashdot.org/~slashdotblog/journal -- low traffic, but we read them all.)
timothy
I work as a consultant in both the public and private sector, so my perspective on this is a bit different. I've worked for the big firms, but now work through a network of other boutique consulting firms to deliver larger projects. Each of your points has a counter argument and counter evidence. I will say that I don't think anyone gets their money's worth from the big firms. Their rates are too high and while they may have access to the right expertise, after the first week of the engagement the specialists are all gone and the client left with the B team. I've been approached many times to subcontract under one of the big firms and I've so far turned them down because they are so arrogant. They usually don't want to actually use my specific industry expertise, they just want my CV to bolster their bid. They trust their endless pool of resources and standardized methodologies to make up for their lack of expertise.
I'd also like to point out that the failure rate of IT projects in general is very high (close to 70%) with little to no difference between in house and out sourced projects. I would add that a sizable portion of my work is refocusing (or replacing / undoing) projects that were started in house and went off the rails. I also know the flip side is also true - failing external projects are brought in house just as often.
There are several good (and some bad) reasons to bring in consultants.;
When you don't have the skills in house, or when your in house skills are fully utilized on other projects it makes sense to hire contractors. Contrary to popular belief, most IT staff do not spend most of their day playing Minecraft or streaming episodes of The Big Bang Theory at work. Most IT staff I'm familiar with work 50 - 60 hours per week and have weeks of backloged operations support and in house projects. Expecting them to add yet another major project off the side of their desk is a strategy for failure. Contractors (can) bring focus. I usually only work on 1 or at most 2 major project at a time.
Hiring staff for projects is not easy and not always the best idea. When you hire someone you invest in recruiting, training, benefits, pension, etc. because you expect that person to be with you, and productive for at least 3 - 5 years. If you hire people just for a project, at the end of the project you can end up with staff who are either under utilized or under motivated because their skills and/or ambitions are no longer what you need. Alternatively, you could end up creating projects with shaky business cases just because you have some in house resources. As a consultant, while I love to be re-engaged for subsequent work, I have no expectation of such. My best marketing is to get the job done. I usually include a post implementation review 2 - 3 months after the project. For me, this is a sales opportunity, but it is also an opportunity for the client to evaluate and learn from the implementation. This is something that doesn't always happen with in house projects.
When people say contractors get paid more than in house staff they are not seeing the whole picture. The things I mentioned above - recruiting costs, training costs, benefits, pensions, health insurance, vacations, paid breaks, statutory holidays, office space, admin support and HR support are all costs for internal staff that are either paid by or not applicable to contractors. Additionally, I carry errors and omissions and liability insurance - where the client company is entirely on the hook for the errors, omissions and liability risk of its employees. Finally, contractors can only bill hours actually worked on the project (or in some cases, a fixed price) where staff are paid regardless of utilization. When you factor all of those things in, experienced staff with equivalent expertise are often paid/cost more than contractors.
The biggest problem with outsourced projects is often in procurement. I haven't seen very many good procurement departments. They are often eith
If you aren't part of the solution, then there is good money to be made prolonging the problem
It's hardly rocket science.
This has been happening sice at least the 1980's. The distressing part is that there seems to be no learning. The same mistakes are made over and over again.
putting the 'B' in LGBTQ+
"There are four ways in which you can spend money. You can spend your own money on yourself. When you do that, why then you really watch out what you’re doing, and you try to get the most for your money. Then you can spend your own money on somebody else. For example, I buy a birthday present for someone. Well, then I’m not so careful about the content of the present, but I’m very careful about the cost. Then, I can spend somebody else’s money on myself. And if I spend somebody else’s money on myself, then I’m sure going to have a good lunch! Finally, I can spend somebody else’s money on somebody else. And if I spend somebody else’s money on somebody else, I’m not concerned about how much it is, and I’m not concerned about what I get. And that’s government. And that’s close to 40% of our national income."
I am typing this on an ACES 15" MacBook Pro. We're supposed to get refreshed every three years; I got refreshed at the change to ACES, which was less than three years, but they gave me a year-old MacBook model, which was a little chintzy. They did give us decent docking stations, though, and they do replace and restore when stuff breaks within a reasonable amount of time.
My beef with ACES is their support of NASA-required software. This machine is running 10.8.3, because ACES has not blessed for 10.9 the required third-party software for whole-disk encryption, remote patch support, remote backup, and remote access.
My previous machine ran 10.6 well into the 10.8 era due to ACES' inability to support this steaming load, and I would put the odds of them certifying a load for 10.9 before 10.10 ships to be below 50%.
To a Lisp hacker, XML is S-expressions in drag.
But I see Dice is convinced that piling on to sunk costs for a broken project is a great strategy for success. Tells you all you need to know about the company. Web gazillion.0 idiots at their best! Arrogance and idiocy all rolled into a big steamer delivered fresh to your browser every day!
Fuck beta!
That is all.
The only difference between NASA and Slashdot is that NASA doesn't rely on the "audience" to keep afloat.
I can see soooooo(!) many things wrong with that statement, ...
NASA's "audience" is US taxpayers and Congress, just to start.
OT: Why does beta think I use noscript when I don't? I'll admit to ABP, however. I suggest /. get some neophytes who've never been to /. to try its commenting system, to see if they can figure out how to use it. I'll bet they (the neophytes) can't. Where's editing help and the Subject line box?
"Tongue tied and twisted, just an Earth bound misfit
There's nothing wrong with that statement. US taxpayers do not decide a thing, you are just the spectators. Can you say: No, I don't want my taxes to go to NASA? Or are you suggesting you can stop paying taxes? Good luck with that... But Slashdot "audience" CAN stop contributing! Without the contributors this site dies. Period.
It could not have been Timothy, he was with your mom at the time of the down-modding.
lucm, indeed.
http://www.youtube.com/watch?v...
ROTFLMAO @ "Chumpy" -> http://yro.slashdot.org/commen...
(You sure "talk a good game" -> http://games.slashdot.org/comm... but you can't even produce a MERE SCRIPT!, windbag...)
You aren't even on the level of a "script kiddie", & full of HOT AIR!
You certainly won't reply there in that 2nd link I posted either, as that would remove your downmods to my posts like this one you can't validly disprove or justify your downmod on -> http://games.slashdot.org/comm...
Oh, I suspect that IS the case here (simply logging out of a registered account & trolling by ac is a common troll trick around here OR using alternate registered 'luser' accounts sockpuppets to do the job will also, & Lumpy is LOADED with those & trolling - which doesn't matter: He PROVES he's all talk, no action (or skills, OR brains, lol))
(You're all TALK, & NO action "CHUMPY!)
* :)
(You know it, I know it, & so does anyone reading AND laughing their asses off @ you now... lol!)
APK
P.S.=> Answer the question in the subject-line Lumpy - since you had to "eat your wrods" in the 1st link above flavored with your FOOT IN YOUR MOUTH + the "bitter taste of SELF-defeat", lol...
... apk