Slashdot Mirror


US Gov't Pays IT Contractors Twice As Much As Its Own IT Workers

bdcny7927 writes "The U.S. federal government pays outside IT contractors nearly twice as much for computer engineering services as it pays its own computer engineers, and 1.5 times more for IT management work, according to a non-profit watchdog group. 'The study points out that IT specifically "is widely outsourced throughout the federal government because of the assumption that IT companies provide vastly superior skills and cost savings." The Project on Government Oversight says its salary comparisons prove that those cost savings are not being realized. However, the comparisons do not address any cost savings that might be achieved through the skills, processes or systems that private IT services companies might deliver. The POGO researchers say that the federal government itself does not know how much money overall it saves or wastes with its sourcing decisions and has no system for doing so.'"

256 of 382 comments (clear)

  1. It's Called "Blame Pay" by WrongSizeGlass · · Score: 4, Interesting

    Being able to point the finger of blame at an outside source has significant value.

    1. Re:It's Called "Blame Pay" by Anonymous Coward · · Score: 1

      It also doesn't hurt that outside contractors don't get nearly the same benefits or protections that government employees do.

    2. Re:It's Called "Blame Pay" by AliasMarlowe · · Score: 1

      Being able to point the finger of blame at an outside source has significant value.

      And this is the primary motivation behind employing contractors in many places.
      A slightly different rationale applies to taking on consultants. Their job is to figure out what you want to do, and then provide "outside expert opinion" that this is, in fact, the best strategy. They take the blame like contractors, but pocket the money anyway.

      --
      Those who can make you believe absurdities can make you commit atrocities. - Voltaire
    3. Re:It's Called "Blame Pay" by scumdamn · · Score: 1

      With twice the pay you can pay for your own benefits. They need to do a cost per employee study to see if cost savings really are being realized.

    4. Re:It's Called "Blame Pay" by hrvatska · · Score: 1

      It also doesn't hurt that outside contractors don't get nearly the same benefits or protections that government employees do.

      What benefits and protections did you have in mind? I've been one of those government contractors, and my brother is a systems programmer for NOAA. We've compared pay and benefits. I make a good bit more than he does. We pay about the same amount for health insurance for comparable plans. We get about the same number of days off. He has more legal holidays but I get more vacation days that I can take when I want or take as half days. I get a better pension. Our 401k plans are comparable. I'm not sure who has better job security. We've got a backlog of work in my organization. He works in an organization whose budget the Republicans are trying to cut. Every time there's a threatened federal shutdown they have to prepare to mothball the facility's IT infrastructure. It gets stressful after while.

    5. Re:It's Called "Blame Pay" by jellomizer · · Score: 2

      There is the fact you can politically blame them value.
      There is the fact that they can dropped at any particular time value.
      There is the fact that they don't need to pay for benefits value.
      There is the fact they can be pushed to part time value.
      There is the fact that they will keep your full time staff honest value.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    6. Re:It's Called "Blame Pay" by lucm · · Score: 2

      > With twice the pay you can pay for your own benefits.

      Not with the kind of healthcare, pension and other benefits available in the public sector. Many employees of the government have a guaranteed pension rate, something that a private contractor has no way to get.

      --
      lucm, indeed.
    7. Re:It's Called "Blame Pay" by lucm · · Score: 1

      aka "outsourcing risk", which is a no-brainer especially in heavily unionized organizations

      --
      lucm, indeed.
    8. Re:It's Called "Blame Pay" by Skarecrow77 · · Score: 2

      My brother works for an IT company contracted to the military. He does less than I do, and makes nearly 1.5x as much as a matter of -normal- pay. Every two years he gets sent out of country for 3 months, and he earns like 3x normal pay if it's a country with an active war.

      His benefits are pretty decent, and he gets almost European levels of PTO.

      I'm quite envious. I guess that's what a Top Secret SCI clearance will do for you.

    9. Re:It's Called "Blame Pay" by Larryish · · Score: 1

      Federal Government: The left hand doesn't know what the right hand is doing.

      News at 11.

    10. Re:It's Called "Blame Pay" by MozeeToby · · Score: 1

      You could argue that the public sector workers are accepting less pay in return for a more steady, in fact nearly guaranteed even in the long term, paycheck.

      I also find it confusing: "[IT is] widely outsourced throughout the federal government because of the assumption that IT companies provide vastly superior skills and cost savings." Then they present their findings that contractors are paid more than public sector workers, then we get "However, the comparisons do not address any cost savings that might be achieved through the skills, processes or systems that private IT services companies might deliver."

      So, if they get paid more for the same work... except it isn't the same... the government believes they bring better skills and experience to the job and therefore pays them more.

    11. Re:It's Called "Blame Pay" by chill · · Score: 4, Informative

      They do not get twice the pay. No way in hell.

      Read the article again and you'll see that they compared the BILLING RATE for contractors. The people doing the work don't get that. Usually 30%+ is taken off the top by the contract house/management company.

      Nor did they account for the benefits costs. The true cost of the employee should be salary plus benefits.

      I say this as someone who not only has worked both sides of that fence, but is currently hiring for Federal IT (InfoSec) positions. I've seen an average of 100+ applicants for each position advertised and most are contractors desperate to become full-time Feds.

      --
      Learning HOW to think is more important than learning WHAT to think.
    12. Re:It's Called "Blame Pay" by Ozymandias_KoK · · Score: 1

      The right hand doesn't, either.

    13. Re:It's Called "Blame Pay" by cayenne8 · · Score: 5, Informative
      Actually, it isn't that bad at all.

      You get yourself in the door of a good Federal contract.....form a "S" corp and get on as a subcontractor. You bill out at anywhere from $65-$80/hr....and you're golden.

      This will keep you comfortable in salary....it is enough to figure to take off about 3-4 weeks a year for vacation and sick leave. You get yourself set up with a high deductible medical insurance policy (like $1200) and you use this ONLY for emergencies (heart attack ,etc), and with this you are eligible to set up a HSA (Health Savings Account) where you can stick back over $3K a year pre-tax.

      As a 1099 contractor, you can write off all kinds of things, even mileage driving to the site daily if you have to drive...lots of perfectly legal deductibles.

      A nice thing with the "S" corp, is that it can also save you a good deal of money on employment taxes, (SS and medicare). Do get a CPA for advice on this, but you can do something like:

      Say you pay yourself a salary or about $40K through the company. You bill for $100K for the year.

      You only have to pay SS and medicare on that $40K, the rest of the $60K falls through on your personal taxes at the end of the year (dividends or whatever you want to call them from the company) and you only pay normal state and federal income taxes on that portion.

      About the only PITA, is the paperwork you need to do. YOu can get a service to handle your payroll if you want, but these days with electronic access, you can easily set up with your state and the feds and pay your taxes quarterly on the income portion. Just document stuff well, and it actually is a pretty nice way to go.

      The HSA is something I like, and wish was more easily available..not just with high deductible plans. This isn't like the FSA's you get through your normal W2 employer, it isn't a "use it or lose it" type thing...it keeps building and building. At retirement, you can convert this to retirement funds. You can also invest from this account if you so wish...

      When I was doing this...I had no problem paying for my routine meds and Dr. visits with my HSA money. Often when I'd tell the Dr. that I'd be paying...they'd give me at least a 15% discount right off the bat...

      Unfortunately, the Feds have more and more, bastardized the contractor paradigm. They deal more and more exclusively with only the LARGE contract houses...and is harder these days to get a 1099 gig...the big houses want you on as a W2 employee.....and then, you get the worst of both worlds as far as job security and pay go. Even that still isn't horribly bad, but you lose all the freedom (no more fscking having to 'earn' vacation and sick leave hours....and all the tax breaks.

      More difficult to find...but not impossible.

      If nothing else, if you can get in on a Federal contracting IT program as a W2...get in, get some experience and foot in the door and meet people. Makes it much easier on the next gig...to get them to let you sub contract to them and go the 1099 route.

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    14. Re:It's Called "Blame Pay" by cayenne8 · · Score: 3, Informative

      I say this as someone who not only has worked both sides of that fence, but is currently hiring for Federal IT (InfoSec) positions. I've seen an average of 100+ applicants for each position advertised and most are contractors desperate to become full-time Feds.

      One reason for this is, that the contracting paradigm is no longer what it was before.

      I'd posted earlier...the Feds, more and more...are only hiring contractors through large contracting houses. These contracting houses, hire people as W2 employees...they get the worst of both worlds. Sure they get benefits, health, etc....but they really lose out on what balances out the contracting life. In a normal contracting life, you get a very high bill rate. From this, you pay yourself, your vacation/sick time, etc. It makes up for the level of 'job security' that you have to put up with in being a contractor.

      When you are a W2 employee of the contracting house....you don't get that high pay, but you still only have the job stability of the regular contractor....and you aren't really treated as a real 'employee' by anyone.

      But, as I'd mentioned before...if you can get in to the contractor world, even as W2 for awhile, it can lead you to being able to get into a subcontractor role yourself, and do the 1099 gig.

      But those are harder to find....so, with that being the case, yes...jumping over to the Federal side, for what can be a lifetime job, isn't a bad thing to look into...I've looked into it myself.

      It helps if you've worked in the fed contracting world for awhile for that jump too....you get in good with those working in fed IT programs, they can help pull strings to get you in. And if you've been doing federal IT stuff, likely as not, you already have clearances, which also help grease the skids to jumping to the govt. side of things.

      If you're getting a bit older, and have made some good money....jumping over to the govt. side isn't a bad thing, for the job security and extra benefits, along with 'decent' pay. It isn't contractor pay by a long shot in most cases....but it is much more secure.

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    15. Re:It's Called "Blame Pay" by cayenne8 · · Score: 1

      What benefits and protections did you have in mind? I've been one of those government contractors, and my brother is a systems programmer for NOAA. We've compared pay and benefits. I make a good bit more than he does. We pay about the same amount for health insurance for comparable plans. We get about the same number of days off. He has more legal holidays but I get more vacation days that I can take when I want or take as half days. I get a better pension. Our 401k plans are comparable. I'm not sure who has better job security.

      It doesn't sound like you are truly a 'government contractor'. Sounds like you are a W2 employee for a company contracting with the govt.

      There's a difference.

      Do you get salary or do you negotiate for your part of the bill rate per hour?

      I'm guessing you're W2. That's a good way to get in the door....but if you really want to do good money and have more freedom, you need to try to get out of the W2 thing...and subcontract 1099 with this company or some other....it is hard for a small guy to get a direct contract with the feds, but if you work at it, you can get a 1099 subcontractor gig with some of the bigger houses, or a sub to a sub....which still can net you a good bit of the bill rate.

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    16. Re:It's Called "Blame Pay" by Bardwick · · Score: 1

      This is definatley the dream. I was actually doing it for awhile, then budget cut (contractors are first in line). I was out of work for 3 months.... $65/hour is good money, IF you work all year. i agree with the large contract company shift. I hate it, but it makes sense. It's called the "prefered vendor list". Honda was sending/dealing with over 60 IT contractor houses. Said "skrew that noise" and went down to 3. Non-competes kicking in all over the place, it was a nightmare.

    17. Re:It's Called "Blame Pay" by lucm · · Score: 4, Insightful

      I've been working less than 1.5 year as an employee for a government agency. Then I left, but that short employment time granted me a 320$ monthly payment for 20 years after I reach 65 y/o. It's not that much because it is an amount in today's money, but it was just 1.5 years. In that same time to get the same pension as a private contractor I would need to save close to 1000$ a month, and it would also require Mr Market to give me a steady 8-9% return each year until I retire.

      As a government employee I also had all kinds of health benefits, paid gym membership, many discounts on hotels, plane tickets and car rental, lower premium on house and car insurance, and more vacation that I needed; I also got a tax break because of the pension fund, and more tax breaks if I decided to apply for an optional group IRA, where the government would put money if I declined the gym membership. And no paperwork, I just had to sign on the dotted lines when they hired me.

      As a contractor I now make more than twice the salary, I can put all kinds of stuff on my tax and shuffle things around to save a buck here and there, I can takes months of vacation whenever I want, but there is just no way that in the long run I'll have a better pension.

      --
      lucm, indeed.
    18. Re:It's Called "Blame Pay" by poofmeisterp · · Score: 1

      With twice the pay you can pay for your own benefits. They need to do a cost per employee study to see if cost savings really are being realized.

      That is a very nice suggestion with valuable data in the end! I'll start the allocation process for hiring contractors to mine that data immediately! Excellent work! Now, about your job..... It looks like we're going to be doing a little house-cleaning..... :>

    19. Re:It's Called "Blame Pay" by poofmeisterp · · Score: 1

      I'm sorry, in my line of work as a government employee, I do not know what "right hand" means. Having that knowledge is not in my job description.
      /snark

    20. Re:It's Called "Blame Pay" by tacokill · · Score: 1

      Great post. I am not a contractor but I am an S-Corp owner and what you say is right on about pay vs. distribution (aka: dividends).

      Again, great reply.

    21. Re:It's Called "Blame Pay" by poofmeisterp · · Score: 1

      Ah, and don't forget statistics....

      "Pay NO attention to the 150,000 contractors we have; they aren't part of the equation. Doesn't factor into the important numbers! Right now we have a low number. Only 150 employees. The federal cutbacks are excellent! We aren't over-employing too many people and the job is still getting done. Efficiency is top-notch!"

    22. Re:It's Called "Blame Pay" by Anonymous Coward · · Score: 1

      Having been a government IT contractor - the government gets a raw deal here. They paid 3-4 times to my firm what my firm paid me for what was essentially a full time position.

    23. Re:It's Called "Blame Pay" by Solandri · · Score: 1

      The true cost of the employee should be salary plus benefits.

      It's salary + benefits + employer's share of SS, Medicare/Medicaid taxes + unemployment insurance + worker's comp insurance + hiring/training costs + travel expenses (many contractors "commute" by flying out on Mondays, living in a rented apartment, and flying home on Fridays). I would assume the government is paying for workspace and equipment, but if they're not, tack that on as well. Many smaller companies without a lawyer on staff also have employment practices liability insurance to protect them from the cost of a lawsuit filed by an employee.

      A 2:1 ratio between what it costs the company to retain and maintain a tech employee vs. what the employee receives in salary + benefits sounds about right to me. This MIT/Sloan page says a tech worker at a fully managed company costs about 2.7x his/her base salary. So 2:1 is in the right ballpark.

    24. Re:It's Called "Blame Pay" by geekoid · · Score: 3, Interesting

      I am a government employee. A software developer. I have been for 6 years, and I was private sectors for a couple of decades prior.

      I have been on both sides of this specific issue

      The best IT staff I have worked with is the government employees. The most mediocre and bad were private sector. I suspect it has to do with it being easier to get a private sector job.

      The software built in house lasts, ans lasts, and lasts. Out sourced work always runs longer and over, always has issues, and never is really going until years after the 'final roll out'.

      I get calls pretty regularly from people in the private sector offering me jobs. Not interviews, actually over the phone jobs. Usually someone who knows me from my past gets into management and they look me up. I could make 50% more.

      I don't take the because I value time, a lot. I work hard for 40 hours, done in 4 10's. Then I go home. If they need me, I get OT or comp time. I spend a lot of time with my family. I have friends making 100-140K, but 80-100 hour weeks. I did that for years, and what for? making some one else rich.

      This "inefficient and lazy government worker" statements have been disproven time, and time again.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    25. Re:It's Called "Blame Pay" by sehryan · · Score: 1

      With you except for numbers 3 and 5.

      I might be not understanding #3, but generally, the feds DO pay for a contractors benefits. They pay for everything the contracting company is going to offer the employee, plus a fee on top of that. Now, there is the long term benefit in that the federal government is not responsible for retirement and health care for these workers when they retire. But in the daily (or annual) grind, the feds are paying benefits to contractors.

      As for #5, assuming you are considering the "full time staff" actual feds, then you are way off base. It is nearly impossible to eliminate a fed that isn't performing as well as their contract brethren, especially one that has a lot of years in the system. And Lord help you if you if one of those feds is a vet.

      --
      The world moves for love. It kneels before it in awe.
    26. Re:It's Called "Blame Pay" by Larryish · · Score: 1

      OMG that is hilarious. Literal LOL.

    27. Re:It's Called "Blame Pay" by Cherita+Chen · · Score: 2

      No, Federal Employees certaintly don't have a "Guaranteed Pension Rate",unless you consider $250 a month a solid pension with which to live on. Federal Employees have a 401K setup similar to the private sector (Thrift Savings Plan) - which comprises the bulk of thier retirement. Yes there is a pension, but it's typically under $1K per month, not to mention SS is factored in there - which most Feds will never see.

      --
      I'm not fat, just big boned...
    28. Re:It's Called "Blame Pay" by PopeRatzo · · Score: 3, Insightful

      It also doesn't hurt that outside contractors don't get nearly the same benefits or protections that government employees do.

      And it really doesn't hurt that an outside contracting firm can make a fat campaign contribution.

      Funny, but it's actually pretty hard to find an example where the outsourcing or privatization of any government service actually turned out to be more efficient and less expensive than just having the government do the job.

      And, as Chile learned, that goes double for privatized social security. The administrative costs went from about 2% when the government ran their social security to almost 20% when it was privatized. They are now trying to end privatization of social security in Chile and put it back in the government's hands for just that reason. Yet, it doesn't stop a certain group of candidates who were debating last night to win the nomination for the US presidency from holding up Chile's privatized social security as a success story.

      --
      You are welcome on my lawn.
    29. Re:It's Called "Blame Pay" by Viewsonic · · Score: 1

      This is what the article is talking about. The contractors get paid the same, but the company doing the sourcing gets profit ON TOP of the normal pay.

    30. Re:It's Called "Blame Pay" by blair1q · · Score: 1

      It's also the fact that the project itself is outsourced. When you only know a few of the requirements before letting the contract, and have no means of managing the project yourself down to the line level, you hire someone else to do it. Then you have no control over internal project management, though the government does typically send along some people to audit and observe.

      Blame is a freebie they get after the fact when something goes tits-up after costing 3X what it was bid for.

    31. Re:It's Called "Blame Pay" by lucm · · Score: 1

      > anyway it was 8 months before I got the job, six months of that was background checks

      The hiring process as a permanent took forever but it did not really matter because I was already working there as a contractor; also the background check was not that long because I already had a security clearance from a previous gig. It's the first time you get a clearance that is painful, especially when you need the one that requires the local police of the area(s) where you lived over the past 10 years to confirm that you have a good reputation and have never been involved in an investigation (the cops need almost two months just for that certification).

      As for the paperwork, what I meant is that basically it was all setup for me, anytime I had to do something it was usually online, or at least I got called to HR and guided through the papers I had to sign; it was unpleasant to deal with expense accounts, especially when going out of the country with the currency exchange, but there was a single guide and all I had to do was follow procedure.

      All this, compared to what I have to do as a private contractor, is "no paperwork". Now I have to worry about a lot of stuff, forms, and various registrations, and even if I have someone to take care of the accounting, someone for the tax, someone for the legal work, I still have to manage a lot of things and check that I meet the various deadlines, and I have to check myself about whatever laws and regulations I have to follow. It's a lot of time wasted on paperwork and research, and a lot of it changes frequently. I am currently thinking about hiring a part-time general manager even if I am the single employee of my own company. Paperwork is insane, especially because I do business in more than one jurisdiction.

      > I must be working at a different US government agency

      I was in a good organization, one that was bringing in money, so I guess it was a bit better than some others where funding was tight. I think there are even better positions, such as officers in the army, but it was a good gig. Unfortunately politics were crazy, it was really hard to see any kind of progress, and the people that were better rewarded and promoted were the ones that kept to themselves and did not try to fix broken stuff. Because of the sheer volume of cash coming in, making a business case to improve something was very difficult, because the perception was always that the risk was not worth the savings.

      On my first day there my boss told me that the problem in the IT group was that there was too much money so people were lazy and always went with the easy, expensive solutions. After a while I had to agree with him, this place was filled with extremely talented people but never getting no for an expense request, no matter the amount, created all kinds of lousy attitudes, such as "throwing hardware at it" or "throwing IBM at it". Also the big brass was always happy to tell the auditors that they had IBM this and IBM that so they would be reassured that IT was in good hands.

      --
      lucm, indeed.
    32. Re:It's Called "Blame Pay" by Firehed · · Score: 1

      Twice the cost hopefully covers paying for your own benefits. Stuff like health insurance adds up incredibly quickly when your employer is not paying 80% of your premium (which in itself is overall cheaper per employee thanks to economies of scale and negotiating power). Not to mention all of the general overhead BS that's normally covered by your employer.

      In terms of how costs break down, you'd probably come out ahead getting (for example) $20/hr as an employee vs $40/hr as a contractor. Not only do those $5 errands like more printer paper add up in hard costs, but the opportunity costs are massive when you're billing by the hour. Hint: unless you've hired an assistant, it's extremely unlikely that you can find the time for 40 billable hours in a work week.

      Take that at face value as whether it's worth having the government work with contractors - there's a lot of stuff unrelated to actual dollars spent that factors in. But the above is just the reality of why contractors (need to) get paid significantly more per hour than salaried workers with benefits.

      --
      How are sites slashdotted when nobody reads TFAs?
    33. Re:It's Called "Blame Pay" by Javagator · · Score: 2
      They do not get twice the pay. No way in hell.

      Right. I think the contractor's employee gets paid about one third of the billing rate. The rest of the money goes to paying for office space, taxes, support people (managers, accountants, secretaries), company profit, training, etc. Hiring contractors gives the government a lot of flexibility. If they need a system that uses technology X, they can hire a contractor with the relevant experience for the project, and when the project is over, the contractor is gone. Also, it is a lot easier to avoid a contractor who has done a poor job in the past than it is to fire a government employee.

    34. Re:It's Called "Blame Pay" by Javagator · · Score: 1
      he earns like 3x normal pay if it's a country with an active war.

      They would have to pay me a lot more than that.

    35. Re:It's Called "Blame Pay" by IANAAC · · Score: 1

      he earns like 3x normal pay if it's a country with an active war.

      They would have to pay me a lot more than that.

      And yet there are plenty of people that choose to accept such a situation.

      I'm probably considered too old (and yet single) to be considered for such a contract - I'm 50, but if they'd take me, I'd probably accept. One thing I've learned in my years is that there is danger wherever you happen to be.

      Living in the middle of the woods in northern Wisconsin this summer, I was close to gone in two severe storms (but, hey - I got a lot of firewood out of it). Add I'm quite sure the government has the training for survival skills pretty well covered, unlike us civilians, that have to learn it all on our own.

    36. Re:It's Called "Blame Pay" by Xaositecte · · Score: 1

      While I was in the military (communications job in the Air Force) - there were a few people in the 50-60 year old range working as contractors out in the desert.

      The physical requirements for contractors are much less strict than the physical requirements for actual military members in a war zone, to the point where I'm not even sure if there are any standardized physical requirements.

    37. Re:It's Called "Blame Pay" by Courageous · · Score: 1

      Read the article again and you'll see that they compared the BILLING RATE for contractors.

      The following things are, ball park, the truth, of many federal defense contractors:

      1. A company will often bill out employees at 1.45X their salary when they are ON SITE at the government facility.

      2. A company will often bill out employees at 2.5X their salary when they work at the contractor facility.

      These numbers are pretty low. Companies like Oracle and what not often have "burdened rates" in the 3-4X range.

      C//

    38. Re:It's Called "Blame Pay" by Courageous · · Score: 1

      It ranges from 1.5X for company employees who work at the government site, to 2.5X for employees who work at the company site. Each company is different, but that range is pretty accurate. The Sloan page isn't much wrong, either.

    39. Re:It's Called "Blame Pay" by guruevi · · Score: 1

      The pay as a contractor was quite a bit higher for me than salaried even though I now work for the same company in a similar position (other department though). The rate charged however was a little over double (~$180/hour) yet the place I worked at still had to provide me with office space etc.

      I never understood why you wouldn't just hire somebody instead of paying more than double for the same person to come and waste a lot of time because they're not actually working for YOU. They're working for someone else, someone who doesn't have your best interests at heart and they get commissioned on top of that for selling other products to you (ever wondered why those contracting companies are Microsoft Gold Partners and Cisco, Oracle etc. certified if they're just basically an HR replacement?) instead of looking for the best fit for your project.

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    40. Re:It's Called "Blame Pay" by BenEnglishAtHome · · Score: 1

      The Civil Service Retirement System was killed for new hires in, what, 1983? When it was replaced with FERS (Federal Employee Retirement System), management at nearly every agency engaged in a 6-month all-out propaganda war to convince CSRS employees to switch to FERS. There were multiple mandatory meetings where outside experts would come in and tell everyone that if they'd just drop CSRS and convert to FERS, they'd all be millionaires by the time they retired. Seriously, we're talking full-court press, here, all the time, for months on end.

      I was in the last group of employees at my agency and district to come in under CSRS so I was still wet behind the ears when the FERS conversions kicked in. Still, after only about a year on the job, I had learned one thing: If it's voluntary and management wants me to do it this desperately, it must be bad for me.

      I'm not joking. I did no financial analysis. I just saw that management was desperate beyond my ability to describe to get everyone to convert and I knew that if those lying bastards wanted me to do something...then I shouldn't. That was the sole basis for my decision to stick with CSRS.

      Now, almost 30 years later, I've just retired. I have no debts; decent (not great) life, health, and long-term care insurance; a little money in the bank; a little money in the Thrift Savings Plan; and a pension that's just a little more money each month than what I require to live.

      Thank God for the paranoia that was instilled into me by the mid-level management bastards I routinely encountered all those decades ago. Sticking with CSRS is the single smartest financial decision I've made in the last 30 years. My heart goes out to all those folks who swallowed the propaganda and switched to the new system.

    41. Re:It's Called "Blame Pay" by sl4shd0rk · · Score: 1

      > Many employees of the government have a guaranteed pension rate,

      The only thing guaranteed these days is the corruption.

      --
      Join the Slashcott! Feb 10 thru Feb 17!
    42. Re:It's Called "Blame Pay" by nemoest · · Score: 1

      If you worked for the United States Federal Government and were paying into FERS, the Federal Employees Retirement System, or CSRS (the old system) and only have 1.5 years of creditable service then you are not eligible for payments from EITHER. You have to have 5 years of creditable service just to be eligible. See: http://www.opm.gov/retire/pre/fers/eligibility.asp and look under the heading Deferred Retirement for FERS and http://www.opm.gov/retire/pre/csrs/eligibility.asp under the heading Optional for CSRS. I'm going to assume we aren't talking about CSRS though, because that was eliminated for all new employees hired after 1987.

      Good news though! Unless you got a payout of your retirement contributions you can always go back and work for the Feds for another 3.5 years to qualify. With 5 years of service at age 62 you could very well get the $320 a month payment you mention.

      Generally speaking, the FERS payment follows this formula:
      (1% * (AVERAGE(your highest 3 yearly salaries)) * Years of Creditable Service)

      So for example, if you become well paid GS-12 employee for 3.5 years in the Washington DC area (I'll assume step 1, 2, and 3) (Ref: http://www.opm.gov/oca/11tables/html/dcb.asp), then when you turn age 62 you would be eligible and receive . . .

      (1% * ((74872 + 77368 + 79864)/3)) * 5 = $3868.40 per year ... roughly $322 a month.

      Now, your personal retirement situation may be entirely different, but I'd go call your previous HR department and validate whether or not you are currently eligible, because unless you didn't state a key fact in your post that changes the situation, I do not believe you currently are.

    43. Re:It's Called "Blame Pay" by laird · · Score: 1

      There are plenty of good reasons to hire outside contractors, even though they almost always cost more per hour than employees.

      1) You can satisfy temporary "bumps" in demand without hiring and then firing people. It's routine to need a lot of dev capacity while building, then scale down when the system is complete so you're doing maintenance and enhancements rather than heavy lifting.

      2) You can save a lot of time, because you can get an entire team of developers via contract in a matter of weeks, while the process of approving hires, recruiting, hiring, etc., to build an entire team can take months.

      3) You can get access to specialized skills that you may not need ongoing,

      4) You can get access to people that aren't willing to work for the published government pay scales. Govnment salaries are fixed by regulations, so you can't negotiate salary. The result is that people who are highly skilled can make 2x as much in private industry than the government is legally allowed to pay. So to get access to the best dev's, you pretty much have to hire them as consultants. Especially since government salaries have been frozen for decades (falling badly behind private industry), benefits are getting cut, and job security isn't what it used to be. So if you're good, you don't end up working as a government employee unless the government is REALLY lucky.

    44. Re:It's Called "Blame Pay" by samwichse · · Score: 1

      +1 this.

      I'm also a government employee, and I'll say our IT staff are pretty good, in spite of their relatively low pay. I believe the support staff are capped at GS7, while some of the admins top out 11-12.

      In spite of a bunch of the bureaucratic BS you have to put up with, most people there seem to prefer working here with the lower salaries (and benefits which offset this) to private industry.

      Sam

    45. Re:It's Called "Blame Pay" by Slashdot+Parent · · Score: 1

      If nothing else, if you can get in on a Federal contracting IT program as a W2...get in, get some experience and foot in the door and meet people. Makes it much easier on the next gig...to get them to let you sub contract to them and go the 1099 route.

      Do you really have to suffer through the whole contractor bit to get a federal IT job? Isn't there somewhere that federal IT jobs are posted? Is it possible for a random Joe to get one?

      My dream is to get an entry-level federal IT job that I'm vastly overqualified for that I could do in my sleep, that's 90+% telework, and get all of the awesome benefits. How do I make my dream a reality?

      Don't judge me; I have my reasons.

      --
      They don't grade fathers, but if your daughter's a stripper, you fucked up. --Chris Rock
    46. Re:It's Called "Blame Pay" by Envy+Life · · Score: 1

      The best IT staff I have worked with is the government employees. The most mediocre and bad were private sector. I suspect it has to do with it being easier to get a private sector job.

      I'm glad to hear that. My experience with government IT departments are that they are filled with a disproportionate amount of unhappy people jockeying for position on pet projects that they can ride into retirement with the least amount of work. They do this because they know they can't get fired and are guaranteed a nice pension, having to work 40 hours or less per week. There are some nice and talented people who work in government but it just seems really difficult to weed out the bad eggs.

      In the private sector I've run across both talented and untalented people too... the untalented ones usually wind up getting let go and move on, many times eventually changing careers. Most of the most talented people I know are driven by using latest technology and creativity that is found mostly small private companies. It amounts to a tradeoff is excitement and hope for a bigger payoff.. or stability with a greater chance of long-term payoff. A personal choice. In terms of pay vs hours worked over ones' lifetime, goverment IT is a better deal than private sector, even though the pay appears lower

      This is what's so disheartening about the contracting agencies who have a stranglehold on these contracts at a 100% markup for sub-par workers. It's a misguided trust given to contracting agencies without proper accountability in place. Things would be more efficient if run like small private sector companies.

  2. Luckily... by fuzzyfuzzyfungus · · Score: 3, Insightful

    Conveniently, we have plenty of shrill talking heads telling us that the private sector is always more efficient. That should be a viable substitute for so called "empirical evidence".

    1. Re:Luckily... by Anonymous Coward · · Score: 2, Insightful

      Not the private sector. Government contracting is steeped in politics.

    2. Re:Luckily... by jellomizer · · Score: 1

      It is, but as a contractor you are able to break a lot of politics.

      For one you are not part of the Bureaucratic System. So you can go talk to whatever level you need too, vs going up the chain. Secondly you are hired for performance, you can make those little mistakes that could hurt a full time employee.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    3. Re:Luckily... by idontgno · · Score: 1

      Not in all cases. Your contract may attach you to a specific spot in the org chart. You'll still be serving a particular bureaucratic master. You'll have to honor his ulterior motives and unstated plans, carry his water and fight his battles, or you'll discover you're more expendable than a "civil servant" with tenure and some collective bargaining leverage.

      This is particularly the case of contractors hired by OMB Circular A-76 provisions, which are often executed as headcount-by-headcount replacement of salaried personnel with contractor equivalents.

      Sorry. Not every contractor works on a "project" or in an "independent consultant" role. Some contractors are just cogs in the same old machine.

      --
      Welcome to the Panopticon. Used to be a prison, now it's your home.
    4. Re:Luckily... by Baloroth · · Score: 1

      More efficient != cheaper. In fact, it is usually the opposite. Car analogy: more fuel efficient cars are (usually) more expensive. More power efficient computers: more expensive. Better workers: more expensive. It may well be they pay twice as much for a contractor, who performs twice as much work as an inhouse employee.

      Or it might not. However, being supplied with one small piece of information doesn't give the whole picture or determine whether private or public sector employees are more efficient. Could well be those public employees spend all their time on /.

      --
      "None can love freedom heartily, but good men; the rest love not freedom, but license." --John Milton
    5. Re:Luckily... by HangingChad · · Score: 2

      Conveniently, we have plenty of shrill talking heads telling us that the private sector is always more efficient.

      That is the biggest lie I saw perpetrated in government contracting. That the private sector could always do a job cheaper. Big, fat lie in most cases. What it did do is keep the number of government workers artificially low while lining the pockets of campaign contributors running the outsource contractors (I'm looking at you CACI).

      The occasional benefit to contractors was that getting rid of the incompetent ones was maybe a little easier, but not always even that. We chased a guy off a project where EDS was one of the contractors, but they kept billing him on the project by moving him to a different office. IBM told us they fired one of the project managers on a failed fix cost contract, yet he was mysteriously present at a contractor's presentation on another project.

      Security clearances are expensive and finding people who qualify for the clearance and the job is hard, so contracts cheat. Why not? There are no consequences for getting caught. No fines, no suspensions, no loss of government contracts. Sure, there are threats all the time, and one or two might get kicked off a project from time to time. But mostly incompetence slides.

      --
      That's our life, the big wheel of shit. - The Fat Man, Blue Tango Salvage
    6. Re:Luckily... by pnutjam · · Score: 1

      Why does everybody think an accounting office is not factoring in these costs already? These guys know how to count money.

    7. Re:Luckily... by poofmeisterp · · Score: 1

      Conveniently, we have plenty of shrill talking heads telling us that the private sector is always more efficient. That should be a viable substitute for so called "empirical evidence".

      Pay no attention to the man behi....

    8. Re:Luckily... by poofmeisterp · · Score: 1

      What it did do is keep the number of government workers artificially low while lining the pockets of campaign contributors running the outsource contractors (I'm looking at you CACI).

      Pardon me for my poor translation, but.. *clears throat*

      "Sir, which set of numbers do you wish to use in this argument?"

    9. Re:Luckily... by Anonymous Coward · · Score: 1

      If they were being paid twice as much, but doing three times as much work, they would still be more efficient. /DNRTFA

    10. Re:Luckily... by Courageous · · Score: 1

      I'm wiling to hear your evidence. What is the multiplier rate to calculate the cost to employ of a government employee, typically?

      C//

    11. Re:Luckily... by Anonymous Coward · · Score: 1

      Conveniently, we have plenty of shrill talking heads telling us that the private sector is always more efficient.

      Right, and who is overpaying their contractors again?

  3. Not surprised by GameboyRMH · · Score: 1

    I know a foreign government that does the same, if it makes you Americans feel any better...

    --
    "When information is power, privacy is freedom" - Jah-Wren Ryel
    1. Re:Not surprised by poofmeisterp · · Score: 1

      I know a foreign government that does the same, if it makes you Americans feel any better...

      Is this before or after failure?

    2. Re:Not surprised by Asic+Eng · · Score: 1

      I know private companies which do the same. One of them has outsourced IT to another company and (among many other ridiculous things) now pays $135 per month and mailing list on top of all the other expenditure. They actually went and replaced the working mailing list servers and substituted them with the supplier's crappy system, just so they could pay them that insane rate. They also hire contractors they don't even interview.

      It's unavoidable - the bigger the organization the bigger the gap between the interests of individual employees from the interests of the organization. Madness, incompetence and bribery finds fertile ground there. Dilbert shows what's going on in private industry, and everybody new to the strip always thinks its creator must work in the same company.

  4. Really? by ccguy · · Score: 5, Insightful

    People having life time jobs make less than people willing to work on a day-by-day basis, with twice the hours, triple the productivity, working in any location the job requires? Really?

    I hope this is the first of a series of articles called 'real life eye openers'. To be distributed among public workers worldwide.

    1. Re:Really? by GameboyRMH · · Score: 5, Insightful

      Do you have any first-hand experience with this? Because I do, and in my experience the contractors are pampered telecommuters who only physically pop in a few times per week.

      In fact we had a big issue a few years back where we had to replace a bunch of contractors with full-time government workers because they are that much more expensive and an accountability nightmare.

      And since I've already stated where I work, I was one of the people who replaced a contractor. I take in somewhere between a third and a half of what the contractor did and you bet your ass I get more done as a full-time employee, even on just the 1 or 2 duties that the contractor had vs. the many more I also have now.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    2. Re:Really? by anjin-san+3 · · Score: 1

      twice the hours, triple the productivity

      You have a citation for these claims? It's not mentioned anywhere in the article.

    3. Re:Really? by GameboyRMH · · Score: 1

      Local Tea Party meetings, I'd guess.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    4. Re:Really? by segfaultcoredump · · Score: 4, Informative

      Sorry, I've worked both sides of this fence, and you should have stopped before you even typed the first word.

      The contractors for the fed/military/etc do not work day to day, twice the hours or have triple the productivity.

      They are given year+ long contracts, work the same hours, and have the same or less productivity. The perms face the exact same thing, their entire division can be wiped away with the stroke of a budgeting pen.

      We are not talking about day labors here, all federal contracts are long and well defined. While your project may get canceled with the next _YEARLY_ budget, the odds of it suddenly going under are next to 0.

      As a fed contractor, I never put in more than 40 hours a week. That is what we had in the budget, and to do more than that would have resulted in issues. The "cost+" contracts that would let me work 80 hour weeks and have the contracting agency get paid for it are few and far in between. Most are fixed at the rates and the number of hours, it does them no good to have you work more than your scheduled rate.

      The productivity thing is pure bullshit. I've seen incompetent admins on both sides, but most are on the contracting side because the contracting firm wants to keep a larger % of the cut to themselves, and thus toss inexperienced newbies into the slot in the hopes that nobody will notice. The real kicker is that as a contractor you have an incentive to not really fix things, but to just patch them. After all, why fix something once and for all when your job depends on the customer needing to have you around to constantly fix something?

    5. Re:Really? by Daniel+Dvorkin · · Score: 1

      People having life time jobs make less than people willing to work on a day-by-day basis, with twice the hours, triple the productivity, working in any location the job requires? Really?

      You have no idea what you're talking about. None. Permanent federal and state employees invariably work harder, and produce more, for less money, than contractors brought in from a consulting firm whose CEO happens to be some senator's brother-in-law.

      --
      The correlation between ignorance of statistics and using "correlation is not causation" as an argument is close to 1.
    6. Re:Really? by ccguy · · Score: 1

      Do you have any first-hand experience with this?

      Plenty. In Spain, but I think it's safe to consider this a rather general thing.
      And to be honest, with the amount of public workers around here (3 million, total population around 45), there just shouldn't be any contractors, well paid or not.

    7. Re:Really? by Hognoxious · · Score: 1

      with the amount of public workers around here (3 million, total population around 45), there just shouldn't be any contractors, well paid or not.

      Quantity != quality.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    8. Re:Really? by GameboyRMH · · Score: 1

      If you add up all those things it still might not even bring me to half the contractor's pay. Not significant in the face of the price difference.

      Also we fire people on a whim around here (we just say there are "confidentiality issues," our office's verision of "It's coming right for us!").

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    9. Re:Really? by nine-times · · Score: 1

      an accountability nightmare.

      Honestly I feel like this is as much a problem as anything else. In my experience, contractors sort of lack "buy in". They have no skin in the game, so to speak. It's a little too easy for them to walk away without having really fixed your problem, and if anything it often ends up being in their interest to do a crappy job, because then you have to pay them to come back and fix everything that broke.

    10. Re:Really? by hrvatska · · Score: 1

      People having life time jobs make less than people willing to work on a day-by-day basis, with twice the hours, triple the productivity, working in any location the job requires? Really?

      Having spent some years working on federal contracts, I can't say that I've noticed a real difference between government programmers and contractors in terms of productivity per hour and quality of work. I used to put in more hours than the government employees, but after a certain number of hours your productivity and quality falls off. Fifty percent more hours does not equal fifty percent more productivity. Sometimes it just means more bugs that get caught in test or corrections after the code reviews are done. Generally speaking, I wasn't on site at government locations five days a week. Most of the time I'd work from home, only showing up as needed. I still occasionally work on government contracts, but I don't have to travel for them anymore. Other people from my team do the onsite work, and I collaborate with them remotely.

    11. Re:Really? by GameboyRMH · · Score: 1

      I'm a cubicle drone doing nothing military-related. We're all just sharing anecdotes, which is fine as long as we label them as such rather than making sweeping (and Reaganesque) statements like the GP did.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    12. Re:Really? by iceperson · · Score: 1

      You seem to be confused, a 1 year contract for Lockheed, Northrup, etc... isn't a 1 year contract for the employee. The company the contractor works for can replace them any time they want without cause. Oh, and let's not forget the 4 weeks paid VACA and other benefits gov't employees get that contractors don't.

      Disclaimer: I'm a government contractor who's salaried and I'm expected however many hours a week it takes to get my job done without overtime pay. Sometimes that's less than 40, but my average is closer to 45 hours a week.

    13. Re:Really? by leenks · · Score: 1

      I too have worked both sides of the fence. As a contractor I feel more obliged to do things properly, and I am rewarded by being respected on the team I'm on and being one of the "go to" people for the rest of the team. On top of that, by doing things properly I'm keeping myself on my toes and improving my skills. What is the point in muddling through and just bodging everything? I'd go insane if I worked like that...
       

    14. Re:Really? by thetoadwarrior · · Score: 1

      I think someone needs an eye opener in regards to contractors and how much work they actually do.

    15. Re:Really? by pnutjam · · Score: 1

      Everything you said is true. Gov. jobs haven't been guaranteed for at least a decade. They are sweating budget shutdowns and the issue with IT, "Everything works great, what do you do all day?".

      The gov used to be on the cutting edge, showing companies how to treat workers fairly, but those days are gone...

    16. Re:Really? by tiny69 · · Score: 1

      So you knew what the government was paying the contracting company for the position. The contractor themselves was only making 1/3 to 1/2 of what the contracting company was getting paid for the position. Unfortunately, the contracting companies prefer to to hire people that only meet the requirements in the statement of work so that they can pay less in salary and keep more for themselves. Someone that exceeds the requirements will want a higher salary.

      --
      Go not unto/. for advice, for you will be told both yea and nay (but have nothing to do with the question)
    17. Re:Really? by Synerg1y · · Score: 1

      At some point in life "some" of us make the choice to pick up a skill or 2 to help improve our success rates, others are never given this opportunity, others aren't give the opportunity but take it anyways. But as long as your happy, who cares?

      I certainly wouldn't be working over 40 hours a week...

      Is the knowledge I have worth another 40 though to grand total to 80? What if I can do something cause of the knowledge that takes me 5 minutes that takes another employee 5 days of data entry? HMMM

    18. Re:Really? by geekoid · · Score: 1

      " triple the productivity"
      incorrect

      half would be closer.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    19. Re:Really? by bill_mcgonigle · · Score: 1

      It's a little too easy for them to walk away without having really fixed your problem

      Sounds like a bad contract, no?

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    20. Re:Really? by geekoid · · Score: 1

      I was a contractor, and if you aren't getting 4 weeks a year, then you have a horrid contract with your agency.

      Every long term contract(1 year of more) I had always had 4 weeks paid vacation in the contract.

      "..salaried and I'm expected however many hours a week i..."

      That model of work leads to less productivity, lower moral, and poor workmanship.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    21. Re:Really? by geekoid · · Score: 1, Troll

      Becasue people with the thinking power of the loal TEA party ahve this mind set.

      I don't have it, so they shouldn't have it.

      as opposed to:
      Hey, look at what they have, how can we get it?

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    22. Re:Really? by segfaultcoredump · · Score: 2

      Having worked in education, dot.com startups (during the boom and bust years), federal (DoD) and now Local government, I have found that the desire to "do things properly'"is not a trait of the type of job (contract, perm, etc), it is a trait of the individual.

    23. Re:Really? by geekoid · · Score: 1

      This is an anecdote, but one I find ammusing..now.

      A contractor brought in "there best people" into a project.
      We were tossing a way to quickly pass data.
      I suggested a binary string, and explained why.
      there 'best of the best' didn't know what binary was other then "ones" and "zeros"

      I talked to a few more of their people, turns out they didn't know anything past the rudimentary programming, and nothing in depth.

      I went to my boss, and then to my bosses boss and told them what happened and they should get rid of them.
      They did an investigation, and got rid of the contract..of course that had already spent 10 million dollars.

      Funny outcome. They got another contractor, and then 2 months later the people from the previous contractor started showing up. They all moved to a different company, they one we hires.
      I told theory project manager that those guys are the reason we got rid of the prior contracting company. The incompetent fools disappeared.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    24. Re:Really? by magamiako1 · · Score: 3, Insightful

      God forbid we give people paid vacation time, sick days, holidays, and basic healthcare coverage. What has this world come to!?

    25. Re:Really? by magamiako1 · · Score: 1

      If you knew anything about the relationship between government and contractors here in the DC region you would know that most of those things do not apply to the individual.

      As an individual IT worker, you yourself do not have to worry about personal coverage. In fact, typically speaking you will get at least some coverage from the company you "work for" (i.e. Best IT Government Solutions, LLC). It will be significantly less most of the time than your average FT position *anywhere* will cover.

      For the most part, when people mention "government contractors" here, it USUALLY means "full-time job without any of the benefits". And that's really all it comes down to.

    26. Re:Really? by segfaultcoredump · · Score: 1

      Disclamer: I was a salaried contractor who worked for Northrop who was sub for Lockhead who worked for the USAF. A typical oversized, multi-year, multi-billion dollar contract.

      Northrop could not replace me at any time they wanted without cause any easier than my current government employer could. (my current employer is a local county.) Nobody in that entire building ever got fired "just because." Its often bantered about, but given that most of the contractors were ex-military in their 40's (I was one of two exceptions) it never happened. Once they got you in there, it was simply too expensive to swap you unless you royally screwed up and the customer wanted you out of there. And I got full benefits from Northrop, including vacation, sick, medical, 401k, etc, etc. I get more or less the exact same benefits from my current employer (401k, no pension).

      I was salaried, but I had to declare all of my hours to the project for billing purposes. They did not want me to burn hours faster than what was allotted in the contract, so they really didn't want me there more than 40 unless something major came up. My current job is also salaried, and on average I probably work the same average number of hours.

      Now, individual situations can alter this perception. Maybe you worked for SAIC or some other warm body shop in a contract from hell that had high turnover. But in all of those cases, the issue was not that folks got fired, it's that they all left the second they found a better paying job because the contract went to the lowest bidder, and SAIC only wanted to pay 1/3rd to 1/4 of the rate to the actual person doing the job to cover their "overhead" ($60/hr for a system admin to SAIC results in $20/hr to the actual contractor. Any takers for a unix admin with a security clearance for @$30-40k/yr? No? Didn't think so.).

      We do use contractors/consultants at my current job in two cases:

      1) Very short term 'in, do xyz, get out' implementation or staff augmentation projects. Basically, install this software, train the IT staff and get out. Those are all $250+/hr consultants and we limit how long they are in house. They are very expensive ($500k/yr) but we only use them to get over critical staff shortages or crunch periods.

      2) Contract to hire for new folks at the help desk. Mostly because we can, er, fire them faster. That said we have yet to do it "just because." In all cases the idiot screwed up not once, not twice but three times within the first two weeks and got walked. But when you get here those conditions are very explicit. Going through the interview phase is a pain in the ass for us (we'd rather be doing real work) so once somebody is here we'd rather it work out than not. It actually cost us more to go that route but the process is faster so nobody cares.

    27. Re:Really? by Anonymous Coward · · Score: 1

      I'll bite (and, being i'm on govt network login is inaccessible here, so hopefully this will be modded up to be seen)

      I've been a contractor for nearly a decade, with about 99% of it spent in government offices. While you may have seen something different every office I've been in (and this is all federal/military not state) we've always been required to be on site, even if the job could easily be done remotely. While true that the contractors cost more, the actual take home pay and benefits is less than our govt counterparts, the rest of that cost all goes to the contracting company. For instance, one of my positions cost approx $110/hr to bill, and my actual pay rate was $28/hr. The highest paid IT contractors I've run into were pulling about $40-$45/hr. Last year there was the big insourcing movement, and many of my co-workers transitioned from contractor to govt had a fairly significant pay raise in doing so.

      YMMV of course, the differences in what we're seeing could simply be due to what part of govt. we've worked with.

    28. Re:Really? by tsotha · · Score: 1

      I have first hand experience as well, and where I worked on an average per-person basis the civil servants were doing far less than half the work the contractors were doing. A few came to work drunk every day. When Doom II came out for Sun workstations all the government employees in my organization locked themselves into their respective offices for about two weeks and left the contractors to keep the lights on. The managers were resigned to just carrying the dead wood since everyone knew trying to discipline slackers meant climbing an Everest of paperwork and in the end would result in nothing more than an official harassment complaint against the manager.

      And worse, they did a lot of unnecessary travel on the taxpayer dime. We had some equipment in Subic Bay, and they were constantly dreaming up laughable reasons to go there and get a week of nights away from the wife in Olongapo. Then they cheated on their travel reimbursements.

      If government employees in your organization work full days, and, you know, actually work it's not a typical civil service group. In my experience.

    29. Re:Really? by stephanruby · · Score: 1

      And in other news, the same tax watchdog found that FedEx invoices were usually twice the cost of US Post Office bills, therefore proving without a shadow of a doubt that the US Post Office is generally much more efficient and cost-effective than FedEx in all cases.

    30. Re:Really? by jmactacular · · Score: 1

      "The real kicker is that as a contractor you have an incentive to not really fix things, but to just patch them. "

      As a contractor, I take offense with this. Being a contractor or not has no bearing on the quality you produce. Quality of work is determined by quality of the worker, it's that simple. To suggest an IT contractor would even need to create more work for himself is out of touch with the reality of IT itself. There is always more work. There is always some new requirement, new feature, new technology, or list of bugs that needs attention. In fact, most contractors do good work, so they can get the next contract.

      Personally, I am committed to quality, because I take great pride in my work. It upsets me greatly if someone manages to somehow find a bug in what I produce. But we're all human, contractor or perm.

      At the end of the day, the saying goes: speed, quality, cost, pick 2.

    31. Re:Really? by ccguy · · Score: 1

      And since I've already stated where I work, I was one of the people who replaced a contractor. I take in somewhere between a third and a half of what the contractor did and you bet your ass I get more done as a full-time employee, even on just the 1 or 2 duties that the contractor had vs. the many more I also have now.

      Well, my guess then if you are that good is that in not much time you'll just leave and come back as a contractor yourself, so you get paid what you are worth.

    32. Re:Really? by HornWumpus · · Score: 1

      Just an aside. If you are not kicking out at least 1/3 of your 'contract to hires' you are ether doing an amazing job of interviewing or you are letting future 'air thieves'* in.

      The best place I ever worked kicked back about 1/3 of experienced people during the 90 probation period. It was amazing to have co-workers you could count on to do their jobs.

      The best HR and interview process will let good BSers weasel through. BSers are toxic to projects unless hired for that aspect and strictly managed (the marketing exception).

      Set traps for BSers during their probation. Play stupid. Real stupid, they are expecting it. If they try to 'baffle you with bullshit' fire their asses immediately.

      * You know someone is an 'air thief' if during a meeting you find yourself thinking 'someone could have used that air for something useful.'

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    33. Re:Really? by HornWumpus · · Score: 1

      WTF is a binary string?

      I know null terminated string, I know unicode string, I know sting and length pair, but binary string?

      Do you call them binary floats too?

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
    34. Re:Really? by jackbird · · Score: 1

      7.5% for SE tax plus $25,000/year at the top end for health benefits still doesn't equal double.

    35. Re:Really? by Courageous · · Score: 1

      I've been in the business 20 years. You're not going to like this.

      Because of the pay general cultural issues associated with government positions, it attracts a certain caliber of employee.

      On a whole, directly employed government employees: these are most certainly not your lions, tigers, and bears, oh my.

      As a fed contractor, I never put in more than 40 hours a week.

      Alas, this is more about you than it is about anything else. Which is, to say, and to wit: you were not and are not one of those apex predators I was referring to above.

      Sorry about that.

      C//

    36. Re:Really? by joocemann · · Score: 1

      You're full of it. As a government contractor I was able to achieve what was required by contract in under 3 hours a day. I made way more than direct employees of the same job and about 4x what I made in the military doing far more work.

      Lol...triple productivity... apparently you don't work for lockheed or caci. Where is it that you work again?

    37. Re:Really? by segfaultcoredump · · Score: 1

      I see reading comprehension is not one of your strong points, but I'm happy to say that you are very good at jumping to conclusions.

      As I said before, as a fed contractor, I was restricted to working more than that. I could want to have be there for 80, but the higher ups told me to not screw up the accounting, and not to even think about going off clock since an audit would nail them. When I left they back fill me with two new folks. My former co-workers bitched about my leaving, but the 50% pay raise was too much to ignore and I was bored out of my mind there.

      So I jumped to a consulting firm in the middle of the dot com boom days. In one year I billed almost 3000 hours. Take out the vacation and 2 weeks from having a kid and I'm over 70 as an average. Add in the crap that was off the clock and it is higher.

      If you have been around for 20+ years you should know that on average you get most of your work done in the first 20 hours of the work week. After that its an exponential decay. After 60 you are just taking up space and consuming coffee. (The occasional crunch time is one thing, but I'm talking averages). But when you are a consultant billing $300/hr, the company who is cutting your checks really does not care as long as the customer is happy.

      So much for your assessment of my abilities.

      And the odd thing is that the group that I now work with in a local county government (all direct) is by far the best damn group I have ever seen or had to work with. Based on your off the cuff assessment, we should not exist. We should all want to leave for more money and the thrill of working long hours.

      What you fail to understand is that it not the type of job you are in. I've seen good and bad groups of contractors, consultants, government workers, education, commercial, etc. I've run into incredible people in places I least expected to. I've also run into some real idiots in spots where you wonder how they ever survived there. You name an industry or group and I'm sure somebody will toss out an example of a good team and an example of a crap team. In the end it is the people you work for and with. Good people want to work with other good people. Its a positive feedback cycle. A good group knows when they are talking to other good people. The flip side is also true. Bad people work with other bad people (and the dunning-kruger effect is in full effect in those environments)

      And please don't confuse productivity and quality with 60+ hour work weeks, or even 45+. We had a security guy who did 70+ every week. He was a hard worker and knew the talk but fundamentally lacked any real skills. When he left to become a consultant we replaced him with a few small shell scripts. (he spent 20+ hours just creating new user accounts; by hand in ldap. One guy wrote a script and it now takes us 10 minutes a week, if that) The firm he now works for has no clue that he has no clue, because the entire company has no clue. But the owner knows some folks with three letter titles from the golf course and they get security assessment gigs because of it. C'est la vie.

    38. Re:Really? by segfaultcoredump · · Score: 1

      On average I'd say 2/3rd fail to make it past the first month. We have had some that didn't even make it past the first week. (HINT: do not make sexist comments to your female coworker. )

      We don't try and trap them, but it seems that their inflated sense of self worth and job skills are such that we think that they actually go out of their way to screw up and then argue with us about how they didn't screw up. We typically give them a 2nd chance to fix it once we point it out to them. The thought is that if they can learn from their mistakes then they have hope. If not, well.... Next...

    39. Re:Really? by segfaultcoredump · · Score: 1

      Don't take personal offense but step back and look at the client -> agency -> contractor relationship and how fundamentally screwed up it is.

      Most importantly, ask yourself if your primary purpose in being at a clients site is to make the customer happy or if it is to make your employer money.

      We all want to say our primary job it is to make the customer happy, but in reality our primary job is to make the employer employer money (or else you wont be in business very long. Customers are usually happier if you don't charge them).

      Now are you doing your employer (the folks who sign your checks) any favors by reducing the long term amount of work that needs to be done?

      You may say counter by saying that if you do a good job then the customer will hire you back and it makes your employer more money in the long run. In reality, if the customer was qualified to determine if you did a good job (fix it permanently) vs an adequate one (patch it), then you would probably not be there to being with (otherwise they would do it themselves). As others have said in the past, "adequacy is sufficient, all else is superfluous."

      Yes, this is a very Machiavellian view of the contracting world.

      This has nothing to do with how you as an individual approach a given situation. You may have a higher personal ethical standard and want to go well above and beyond the call of duty. I've met a number of consultants/contractors/perms/temps/whatever who are like this. I like working with these people, mostly because they will work as a team and do what is right for the project as a whole and not just their department or group.

      But I also have to face the reality that the contracting environment as it is setup today is fundamentally flawed in that it financially encourages mediocre work.

    40. Re:Really? by cthulhu11 · · Score: 1

      Does the article compare apples to apples? Are benefits paid for employees but not contractors factored in? When I was offered a job at NASA, working for Sterling Software or CSC (I forget who had the contract at the time), I was told that that contractor thing was mostly due to the near impossibility of getting rid of direct employees if they had to for whatever reason.

    41. Re:Really? by Jarik_Tentsu · · Score: 1

      I know someone who works in Enterprise Architecture/IT strategy and has done consulting work for both private and public sectors.

      He said that when he worked for an Australia government organisation, the general work culture all the way from the bottom IT workers to the senior management was one of mediocrity and barely any emphasis placed on performance. As long as workers fill their most basic contract requirements, everyone is happy - even if they're incompetent.

      Apparently the CIO himself admitted that some of his senior management staff were useless and incompetent but didn't want to replace them simply because they had worked in the organisation for years.

      You wouldn't see that in the private sector at all. And I guess the argument here would be that external IT contractors would have a similar work ethic. I'd argue it'd be more of management itself that needs to be replaced, as opposed to the lower level contractors.

    42. Re:Really? by Courageous · · Score: 1

      Who's confusing productivity with overtime? Not I. The willingness to work overtime represents work ethic.

      Working consistent flat 40's is definitely not normal in any government contracting position. Like I said, I've been in the business 20 years. I should know.

      There are only certain personality types who are willing to go to work in the "slow lane". And without question, government positions are the slow lane: lower pay, lower hours, much slower promotions that are based not on merit, but time in service, and little chance of layoff. This attracts a certain personality type.

      What I am saying is true. It's in the very nature of the market.

    43. Re:Really? by uufnord · · Score: 1

      Do you have any first-hand experience with this? I do, and you're wrong. As a contractor for a gov't office (previously), I wouldn't get paid if I wasn't in the office, with time accounted for by a manager who worked for the office that I worked at. If you're allowing contractors to become "pampered telecommuters", you're doing it wrong. If you or your office are managing these contractors wrong, it's not the contractors fault, it's the fault of the manager. You're assigning blame incorrectly.

    44. Re:Really? by _0xd0ad · · Score: 1

      A "string" is a series of bytes. Each byte contains 8 binary bits.

      "ASCII" is a character code. Each ASCII character contains 7 binary bits.

      Storing ASCII characters in a string leaves 1 unused bit in each byte. You figure it out, dumbass: what's the difference between an "ASCII" string and a "binary" string?

      Now, who needs CS 101 again?

    45. Re:Really? by Courageous · · Score: 1

      You, Mr. AC, should not be commenting on this business. It's not true that a salaried employee has to be paid over time. I'm in management at a Defense company, and I am highly acquainted with the Law.

    46. Re:Really? by Courageous · · Score: 1

      Please do not try to recover from this. These were the exact words: "Working more than 40 is overtime. Even if you're "salaried"." These words were, in fact, FALSE. Your other words "OP said that his contract specified 40 hours per week" are also not true words. OP said no such thing. WTF.

      OP actually knows a lot more about the field (and the FAR) than you do. You can find it in the words "most are fixed at the rates and the number of hours, it does them no good to have you work more than your scheduled rate." OP is aware of something here that you were not. He's aware of mandatory rate reductions associated with working an exempt/salaried employee overtime. So while you, Mr. AC, are pretending to know something about labor law, OP actually knows something.

      As to the finer details of whether or not a specific firm has improperly qualified a salary employee as "exempt," and said implications, this is not on subject, I am not interested in discussing this with you.

    47. Re:Really? by Courageous · · Score: 1

      Calling an employee "salaried" doesn't make him or her exempt.

      It also doesn't make him or her non-exempt, so it is flat out wrong to declare "Working more than 40 is overtime. Even if you're "salaried"." Never mind that indeed most salaried positions *are* exempt. You're attempting to distract me from this untrue statement. It's not going to work. Increasingly shrill messages won't make a wrong statement true.

      C//

    48. Re:Really? by Courageous · · Score: 1

      If you're a contractor working as labor, you are most likely non-exempt. If you're an engineer or IT guy, you're probably exempt. If you're a young engineer or IT guy, you are probably exempt, but might be misqualified. Employers misqualify young engineers as exempt all the time. Unfortunately.

      The situation is quite complicated. For example, I am exempt, but until last year I was paid O/T regardless. My last promotion ended all possibility of paid O/T for me, but it is routinely expected that I work O/T. That's special, but the rules aren't predictable in a fashion you might think (except for the labor law violations, but let's disregard those).

      Here's the deal. You can almost always work overtime on a DoD contract. The consequences depend greatly on the contract time and the exempt status of the employee. The general scattergram of all this is that yes, an employee CAN work uncompensated O/T for the government, but the various accounting mechanisms will not reward them (or for that matter, the company) for it if they do.

      You can also work for the government for free. But the legal circumstances of this would take about a week of talk to describe. The short version is that if you work for free for work you said you were working for pay, it better be out of company profit or better not be paid to the employee at all. This is a complicated discussion and won't get into it.

      Now I work in engineering; someone in a different field may have a different experience. But over here where I sit, rolling their eyes and dismissing the probability of working O/T "because there is no point and no pay" is a good indicator that the portion of the otherwise scarce raise budget has some chance of going to someone else.

      Which is not to say that I'm at all interested in giving big raises to ineffective people who think plotting a lot of O/T means that I will think they are bright.

      C//

    49. Re:Really? by LunaticTippy · · Score: 1

      The US average is about 30% for benefits, 70% for wages. Many workers place a premium on employer-provided benefits because they are unable to buy them at any price on the open market.

      --
      Man, you really need that seminar!
  5. Interesting Table Flip by mfh · · Score: 1

    I was under the impression that you outsource to SAVE money. My perception is changed.

    --
    The dangers of knowledge trigger emotional distress in human beings.
    1. Re:Interesting Table Flip by Anonymous Coward · · Score: 1

      Actually, the contractors are hired because the government employees, by and large, either are not capable or are not willing to do the work. As a matter of fact, after having 15 years of IT experience running the gamut of web development to systems and network engineering and seeing valuable and worthwhile employees... even though the government IT employees make half as much as the contractors, the government employees are paid twice as much as the skills and experience warrant.

      The real cost savings.... fire the government employees that are not willing to assume responsibility and do even moderately difficult work.

      That being said, this certainly does not apply to ALL government employees. I work with one and they lucked out, let me tell you. He is an EXCELLENT technician and works hard... the scary thing is... he didn't even interview for the position... he submitted his resume and after two months received an offer letter and started working the next week. From my experience, the federal IT workers are worthless five out six times.

    2. Re:Interesting Table Flip by bluefoxlucid · · Score: 1

      Federal benefits are also ass-expensive.

    3. Re:Interesting Table Flip by AliasMarlowe · · Score: 1

      I was under the impression that you outsource to SAVE money. My perception is changed.

      Outsourcing reduces headcount. It does not necessarily reduce actual cost or improve quality or timeliness. Many of us could cite counterexamples, where outsourcing increased costs and/or reduced quality and/or led to delays. From the CEO's point of view (which comes largely from market silliness), the effect of outsourcing on total costs or achieved output is much less relevant than its impact on the fixed cost part of total costs, and supposedly[*] gives greater flexibility in dropping costs should business decline.

      [*]Most of the smart subcontractors (and even many stupid or ineffectual ones) will insert contractual conditions which subvert this, in the interests of obtaining a guaranteed income.

      --
      Those who can make you believe absurdities can make you commit atrocities. - Voltaire
    4. Re:Interesting Table Flip by Jakester2K · · Score: 1

      The real cost savings.... fire the government employees that are not willing to assume responsibility and do even moderately difficult work.

      Can we include Congresscritters in this plan?

    5. Re:Interesting Table Flip by SwedishPenguin · · Score: 1

      Nope, you outsource to benefit your buddy's private sector company, who then takes the profits and invests them in the Cayman Islands (maybe giving you a small share in the process)..

    6. Re:Interesting Table Flip by lucm · · Score: 1

      > the government employees are paid twice as much as the skills and experience warrant

      I completely agree. One time I had to deploy a web application (COTS) in a government agency, and I had to show the ropes to the tech lead in charge of the web development team that was supposed to take over the maintenance. After the webapp was installed, the guy kept asking me to "install in the intranet"; I showed him that it was accessible from a browser on the internal network but he kept asking for this to be installed "in the intranet". I asked him to show me the "intranet", and I had to follow him to his workstation where there was an Intranet shortcut on the desktop. It was a bookmark for "http://intranet". Basically all I had to do was to edit a static index.html page to add a link to the new webapp, and the guy was happy that it was "installed" properly.

      Surprisingly all maintenance for the web application (simple patches from the vendor) ended up being done by my company, because their internal "web development team" was too busy with other projects.

      I don't know how much these guys were paid, but it was too much.

      --
      lucm, indeed.
    7. Re:Interesting Table Flip by RatherBeAnonymous · · Score: 1

      This is the logical disconnect in outsourcing.

      Contractors are in it for the money. Outsourcing vendors are in it for the money. Everyone is looking to get their cut of the cash. With an independent contractor the real person doing the work is going to charge more to compensate for the fact that they have no job security and may spend months between jobs and they pay more for individual health care plans than a large employer does for their employee health plans. With an outsourcing company that highers the contractors, the individuals may get paid less because they get a group rate on health insurance, but the outsourcing company charges more and takes a percentage for themselves. Unless it's something you can outsource to India or China or anywhere the labor costs are low, outsourcing costs more.

    8. Re:Interesting Table Flip by pnutjam · · Score: 1

      From my experience, IT workers are worthless five out of six times. It takes luck and skill to find someone who is at the top of their game and willing to stay there.
      /especially since no one will pay for it...

    9. Re:Interesting Table Flip by leenks · · Score: 1

      Except that this is talking primarily about embedded contractors, so it doesn't reduce headcount - you still have the same number of people on your premises, just split over two different budgets. As a contractor I can tell you there is definitely more flexibility to drop staff at a whim - my notice period was recently reduced to *one* week, as opposed to the staff who have a twelve week notice period.

      Oh, and I don't get the extra healthcare, training, car parking (expensive, and a 20 minute walk from the car park), flexitime, pension (final salary), shorter hours, childcare assistance, etc.

    10. Re:Interesting Table Flip by magamiako1 · · Score: 1

      Replace $federal with $null, and you have a much closer approximation.

      And if you think it has anything to do with skillset as to why a government agency goes "outside", you *really* need to take a step back and look at things, because that is so far from the truth.

  6. Any surprise? by papasui · · Score: 4, Insightful

    Temporary workers always make more money per hour than those doing it full time, its the trade off for the convience of having an on demand workforce. It's also very misleading to go strictly off per hour wage when your not including the total compansation package into the mix. Full-time employees will get PTO, insurance, 401k/pensions, etc. That isn't a small chunk of change.

    1. Re:Any surprise? by narcolepticjim · · Score: 3, Insightful

      The workers are often full-time employees of the contractor (e.g., General Dynamics IT). They get benefits along with their salary.

    2. Re:Any surprise? by Lunix+Nutcase · · Score: 5, Informative

      Actually they factored in the extra 40% cost of benefits on top of the government employees salaries and the private contractors were still 1.5-2 times more expensive. The people doing this study weren't so dumb as to not factor that in:

      Because the contractor billing rates published by GSA include not only salaries but also other costs including benefits contractors provide their employees,[66] POGO added OPM’s 36.25 percent benefit rate to federal employee salaries[67] and BLS’s 33.5 percent loading to private sector employee salaries to reflect the full fringe benefit package paid to full-time employees in service-providing organizations that employ 500 or more workers.[68] All supporting data for this study are found in Table 1 and Appendices B through D.[69]

    3. Re:Any surprise? by shmlco · · Score: 1

      If they are in the employ of the contractor (General Dynamics IT), then even though the government might be paying them twice as much per hour, they're not getting paid twice as much per hour since General Dynamics IT is pocketing a significant percentage of the money.

      In short, they could well be "paid" the same amount, or even less.

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    4. Re:Any surprise? by narcolepticjim · · Score: 1

      I *think* the rule is the contractor can take 10% of your rate, the subcontractor can do the same, and the rest must go to your salary and benefits.

    5. Re:Any surprise? by blair1q · · Score: 1

      In the best of conditions, the bid spells out everything involved, and it's reasonable.

      Then the bid includes mandatory profit levels for the contracting company.

      That's cash. All of the administrative and productive costs are accounted for, and they just put a fat colored block on top and leave it there.

    6. Re:Any surprise? by jmactacular · · Score: 1

      Exactly. Moreover, when it comes to budgeting, one thing you don't have to worry about with contractors is the rising cost of health care benefits. With perm employees, many people lose out on seeing an increase in wages, because their employer is picking up the rising cost of their health care. Which is why that "benefit" should be decoupled from employment. After all, your company doesn't pay for your car insurance.

    7. Re:Any surprise? by jittles · · Score: 1

      40% isn't a high enough markup on the contract employees. My company does government contracts and I often get to see the pay rates + bill rates. When you take into account the overhead of maintaining and running a building, paying benefits, etc, the company has to charge about $3 for every $1 the employee gets paid. That includes such costs as HR, as well.

      That's the rate for a Cost + Fixed Fee contract. We prefer these because they are cheaper for the government. We are not allowed to profit, as a company, on anything except for that fixed fee. So all that cost has to go to employee + overhead, or else we can get busted. The latest trend for contracts is Firm Fixed price, which is actually more expensive for the government. Why? Because the government only pays out as certain milestones are reached. That means that my company has to get financing from a bank to pay employees until we get paid. Or we have to have the cash on hand to front the cost of the contract. So, there is often interest charged in addition to overhead + profit.

    8. Re:Any surprise? by Av8rjoker · · Score: 1

      I must be taking this out of context or some comments because this is a ridiculous statement. Temp workers ALWAYS make far less than full-time employees. I've worked quite a few temp jobs, since that's the direction this stupid fucking country is going, and I've always made less money than full-time equivalents while getting no benefits, no time off, and on top of that I get treated like a second class worker at some places *cough*nintendo,snapon,xerox*cough*.

      I've been at....... uh, a large search engine company.... as a temp, for 1.5 years now. I've gotten no raise, I can't afford to buy into their shitty health insurance, and I make maybe 20k a year. The part of the country I live in now is very expensive to live (coming from Wisconsin). If I don't get my paycheck each week, I'm completely screwed.

      That is my experience as a temp. I hate life.

    9. Re:Any surprise? by Dahamma · · Score: 1

      Yep. That's the issue. If they were motivated independent contractors working efficiently on their own and paying their own benefits, that would be one thing. But in this case it's mostly dime a dozen subcontracted workers where most of the extra money goes to a huge company that got the contract through lobbyists or backroom deals anyway.

      Not that different from Blackwater and how they charged like 3-4x per "contractor" for security services as what the highest paid US soldiers ever made in Iraq...

    10. Re:Any surprise? by Hognoxious · · Score: 1

      That's why General Dynamics get paid twice as much; because they have to pay their employees even when they're on the bench.

      Or did you seriously think the full hourly/daily billing rate goes straight into the employee's pocket?

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  7. only twice as much? by Enry · · Score: 4, Insightful

    That actually isn't that bad, given that the cost of an employee is way more than what their salary is (sick time, vacation time, health insurance, retirement, other benefits, etc.) all add up.

    I'd be more concerned if it was 5-6x as much. 2x is a relative steal.

    At the same time, if the feds only need someone for a few months for a specific project, it's a lot cheaper to bring in a consultant for the time needed than hire someone and have them working for you way too long.

    1. Re:only twice as much? by black+soap · · Score: 1

      2X is normal. If you are providing the office they work out of, and all equipment, it might go down a little, but paying 2X for outside consultants actually ends up about breaking even.

      Now, if you are hiring an entire department of them, it might work out differently.

    2. Re:only twice as much? by 12345Doug · · Score: 1

      Additionally until recently 20 years in was enough for a pensioned retirement with full health care until death. Doesn't sound bad until you realize that you can be looking at 40+ additional years of pensions and health care you are paying for on an employee that provided 20 years of output. It's the long term costs that really need to be factored to get a true assessment on contractor or employee value.

    3. Re:only twice as much? by UnknowingFool · · Score: 1

      Also I'm not sure how they compare the two unless it was by title only which may not be the best comparison. One friend of mine was working as a contractor with a government DBA. My friend wouldn't call himself a DBA but has extensive experience working with databases even on the administration side. Designing a new table, my friend could not convince the DBA to use an integer key for state. Instead the DBA was going to use text and index that instead. The reason: The DBA didn't want to write the join statements in SQL. There are probably stories on both sides of the fence on this one; however, it is easier to get rid of an incompetent contractor than a government employee.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    4. Re:only twice as much? by Antisyzygy · · Score: 3, Informative
      Pretty sure they factored that it and still found them to be more expensive.

      Actually they factored in the extra 40% cost of benefits on top of the government employees salaries and the private contractors were still 1.5-2 times more expensive. The people doing this study weren't so dumb as to not factor that in: Because the contractor billing rates published by GSA include not only salaries but also other costs including benefits contractors provide their employees,[66] POGO added OPM’s 36.25 percent benefit rate to federal employee salaries[67] and BLS’s 33.5 percent loading to private sector employee salaries to reflect the full fringe benefit package paid to full-time employees in service-providing organizations that employ 500 or more workers.[68] All supporting data for this study are found in Table 1 and Appendices B through D.[69]

      That was posted by Lunix Nutcase above.

      --
      That brings me to an interesting point, / . is just "the ramblings of socially-inept, technology-literate news-mongers".
    5. Re:only twice as much? by Whorhay · · Score: 2

      As someone who went from being a contractor to a civil servant, in a workplace with about a 50:50 mix with 400+ workers I think I can speak to this.

      The first year I worked as a contractor I had in my possession a piece of paper I was undoubtedly not supposed to have. It listed all the pertinent details of the contract slot including the $ amount the government was paying for it, $154K. My salary was under 40% of that. Now in this job everything was furnished by the government including equipment and workspace.

      When I transitioned to a GS position (doing the exact same things in the same office, in fact at the same desk) I actually received a pay increase of more than 10% to move to the lowest step of the appropriate pay grade for the position. And thanks to the wonders of a pay stub that actually displays all of the governments contributions on my behalf I can see what I cost them above and beyond my salary. All together it comes to a tiny bit over $98K a year.

      So by hiring me as a civil servant they saved $56K a year. Not to mention my pay is better, my pay increases are better, I can actually earn significant awards and recognition, vacation is more plentiful, sick time actually exists and accumulates, I get retirement savings matching. The list goes on and on, and I'm still cheaper for the tax payers as a civil servant than as a contractor.

      Now of course there are highly skilled geniuses out there that a department might need on an occassional basis, and hiring them as a civil servant wouldn't work. But paying a premium on every single slot to account for that 1% or less is a huge waste.

    6. Re:only twice as much? by Whorhay · · Score: 1

      I believe "recently" was 1986 http://www.opm.gov/retire/pre/fers/index.asp

    7. Re:only twice as much? by geekoid · · Score: 1

      2 x for less results.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    8. Re:only twice as much? by sjames · · Score: 1

      Many of the contractors they're talking about are contracted for a year or more at a time and are often for all practical purposes permanent.

  8. Worth every penny by GlobalEcho · · Score: 5, Insightful

    I am guessing that in about half these cases, at the individual level, the contractors are former government employees who weren't getting paid their fair market value by the public sector. Given that a good IT worker is worth about 5 times a medioce one and 20 times a bad one, they're probably a much better value, on average, than those "left behind". Consulting budgets and the like also let huge bureaucracies get necessary work done that is internally impossible because it is "not in the budget".

    The other half these cases, I am also guessing, will prove to be unnecessary wastes of money even worse than typical government IT initiatives.

  9. I don't work in the public sector. by Tolkien · · Score: 2

    I don't make as much as a Highly Paid Consultant, either, but fuck off! This should be considered normal. Do you think the zillions of perks you get as an employee for the government (health insurance, unions, more holiday time, guaranteed pay raises) are free?

    1. Re:I don't work in the public sector. by Hatta · · Score: 4, Informative

      POGO's report is freely available on the web. If you actually look at their methodology, you'll see that they included benefits.

      Because the contractor billing rates published by GSA include not only salaries but also other costs including benefits contractors provide their employees,[66] POGO added OPMâ(TM)s 36.25 percent benefit rate to federal employee salaries[67] and BLSâ(TM)s 33.5 percent loading to private sector employee salaries to reflect the full fringe benefit package paid to full-time employees in service-providing organizations that employ 500 or more workers

      --
      Give me Classic Slashdot or give me death!
    2. Re:I don't work in the public sector. by DigiShaman · · Score: 1

      Your tax dollars at work baby!

      --
      Life is not for the lazy.
    3. Re:I don't work in the public sector. by Anonymous Coward · · Score: 1

      Ha! I like the methodology disclaimer:

      The most critical limitations are that:

      1) the government’s coding, classification, and data collection systems are inconsistent and do not allow for reliable cost analyses[72];

      2) government websites do not provide access to agency documents that detail cost estimates and the justifications for outsourcing decisions;

      3) the government does not publish information on the number of actual contractor employees holding a specific occupational position under any given contract;

      4) the government only lists the ceiling prices that it can be billed by contractors for the specific occupational positions—the government is at liberty to negotiate prices that are lower than those listed, but it does not publish those negotiated rates (however, based on POGO’s review of GSA contracts, and anecdotal evidence, the government tends to pay the listed billing rates rather than negotiating lower rates[73]);

      5) government websites do not disclose what the expected cost savings for service contracts are, nor the actual savings (or lack of savings) that result from those contracts. These shortcomings prevent government officials, as well as the public, from accurately assessing outsourcing costs.

    4. Re:I don't work in the public sector. by Divide+By+Zero · · Score: 1
      Having worked both public and private sector IT, I'm interested in your perception of "zillions of perks".

      Health insurance: Provided at a discounted rate to public sector employees as well as private. Working public sector, I have the local BC/BS HMO, for which I pay out of my paycheck. Working public sector, same thing. I paid part, my employer paid part. I see no difference.

      Unions: I've never been a member of a union, public or private. No difference there.

      More holiday time: Two weeks a year time off both ways. Private sector, I had the day after Thanksgiving and the day before Christmas off. Public, I get Columbus Day and Washington's Birthday off. On balance, not much of a difference, if any.

      Guaranteed pay raises: I don't know if you remember, but federal employees' pay rates were frozen last year. Now I have guaranteed NO pay raises for a few years. I imagine private employees don't have legislation prohibiting them from getting cost-of-living increases. There's a difference, but not the one you'd expect.

      Are there more, or are we taking four as being equivalent to "zillions", and "roughly equivalent compensation" for "perks"?

      --
      Dare to Hope. Prepare to be Disappointed.
    5. Re:I don't work in the public sector. by Shihar · · Score: 1

      The cost isn't what you are paying the IT folks per hour. The cost is how much you shell out in your overall IT budget. I work in the private sector and occasionally outsource various jobs. Might the per hour cost of an in house programmer be cheaper? Maybe, but I don't care about the per hour cost. Out sourcing is without a doubt cheaper. The reason is simple. I don't need a programmer 40 hours a week, every week of the year. I need a programmer in bits and bursts. I can't get the money to hire a programmer and then find the management to put them under, especially when market conditions are uncertain.

      The cost of hiring someone is pretty brutal. It isn't just what you pay them and the benefits, but it is also what you have to pay them should you lay them off, and the blow to moral if you keep hiring and firing people as needed. Getting a few thousand to contract for a narrowly defined project is comparably easier and cheaper.

      So, seeing that the government more or less does exactly what I do doesn't get my blood in a boil, especially considering that with government unions it makes it even harder and more expensive for the government to downsize should the need arise or the work dry up. If you are going to need programmers to continuously work on or support something, in house is certainly the way to go. If you don't need someone for 40 hours a week from now until the end of time, outsourcing to a contractor is a solid way to keep costs down and let you remain flexible on your IT spending , especially in uncertain market conditions.

    6. Re:I don't work in the public sector. by Call+Me+Black+Cloud · · Score: 1

      They included benefits but they compared the fully-loaded contract rate vs the government employees pay and benefits. The fully loaded rate includes overhead - that's what pays the salary of the employees who don't bill to a contract (such as HR), infrastructure (office costs), plus a profit. They did not compare salary + benefits to salary + benefits.

    7. Re:I don't work in the public sector. by Tolkien · · Score: 1

      I live in Canada, health insurance with the government here means you get quite well covered, though my Mum (now retired) with MS might say otherwise; the already-expensive drugs she has to take would otherwise probably cost tens of thousands per month. She had to go to the hospital a little while ago due to a burst appendix and her insurance covered a private room for her privacy. Unions I wouldn't know about, I just know that once you have a gov't job, you're set for life unless you do your job poorly intentionally, even then then mostly you'd get passed around between departments getting "promotions" and "extra training" (true story/anecdote about one of my Mum's former co-workers). It's difficult to get rid of you. Here in Canada, whenever there's a holiday where you'd get the option to choose which day off you'd like, such as Thanksgiving's Monday or Friday, the gov't always gives you both. Guaranteed pay raises, I imagine are due to your pay also being based on your years of service/experience.

  10. US Govt doesn't know how to spend wisely?!! by cod3r_ · · Score: 1

    When did this happen?

    1. Re:US Govt doesn't know how to spend wisely?!! by Bob+the+Super+Hamste · · Score: 1

      What you thought bridges to no where and $50,000 water fountains (bubblers for some of you) were good deals.


      Yes I did actually notice your sarcasm.

      --
      Time to offend someone
  11. I'm an independant contractor... by Sooner+Boomer · · Score: 3, Informative

    ...and I work for a state govt. I have to cover all my insurance costs, all the SS and other mandatory deductions, plus vacation and other paid time off. Some states are trying to mandate paid vacations and health insurance - even for baby sitters. This raises the costs considerably. PLUS - we are actually accountable: if we don't perform up to spec, we can lose money. A govt employee, esp. a federal employee has (in essence) a sinecure.

    --
    Chaos maximizes locally around me.
    1. Re:I'm an independant contractor... by Bob+the+Super+Hamste · · Score: 1

      And before some people claim BS on some of this there was a recent dust-up here in Minnesota over our current governor's executive order to allow in home private daycare workers to unionize. Now granted this won't exactly be a state mandate for benefits and other things it is a possible mandate for all daycare workers to be part of a union. I say possible as the executive order hasn't been issued and no one know what is in it so it may just republicans making hay.

      --
      Time to offend someone
    2. Re:I'm an independant contractor... by cod3r_ · · Score: 1

      everyone has to make a living and all businesses have to be profitable to survive. I don't think the issue is really that independent contractos charge too much.. it's just that they charge enough the government ought to just hire good people on full time. unless they just can't find good people who want to work for them and have no choice but to go outside contractor

    3. Re:I'm an independant contractor... by Antisyzygy · · Score: 1

      Im not sure why it should ever be illegal or legally discouraged to unionize. Seems like a violation of your rights.

      --
      That brings me to an interesting point, / . is just "the ramblings of socially-inept, technology-literate news-mongers".
    4. Re:I'm an independant contractor... by cayenne8 · · Score: 1

      I have to cover all my insurance costs, all the SS and other mandatory deductions, plus vacation and other paid time off.

      Well, you *did* take under consideration these payments (vacation, sick time, insurance) when you negotiated your bill rate, right?

      Also, I hope you incorporated yourself, and did something like a "S" corp, which will allow you to save money on the SS and medicare....so that you don't have to pay those taxes on everything your company bills for and brings in....???

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    5. Re:I'm an independant contractor... by blair1q · · Score: 1

      Tell that to PATCO.

    6. Re:I'm an independant contractor... by AmberBlackCat · · Score: 1

      ...and I work for a state govt. I have to cover all my insurance costs, all the SS and other mandatory deductions, plus vacation and other paid time off. Some states are trying to mandate paid vacations and health insurance - even for baby sitters. This raises the costs considerably. PLUS - we are actually accountable: if we don't perform up to spec, we can lose money. A govt employee, esp. a federal employee has (in essence) a sinecure.

      So basically all the same expenses as the Federal Government with its own employees, except you get paid much more.

  12. More costs involved. by CapnStank · · Score: 4, Insightful

    Cost to run in-house IT/etc.:
    - Personel wage
    - Facilities
    - Administrative costs
    - Training
    - + others

    Cost to pay contractors:
    - Wage/Contract cost

    Typically they're similar or the contract will come in lower. Wage is not the only variable in the entire equation

    1. Re:More costs involved. by RandCraw · · Score: 1

      Lower cost? That's the very point that the OA disputes.

      In fact, contractors who work on-site (as most do for the gov't), incur the same costs as gov't in-house staff do for facilities, admin costs, training, etc. In practice, the only savings due to outsourcing are health care and retirement, and outside of the military, these account for nowhere near 50% of an in-house gov't staff salary.

      This fallacy is exactly what the gov't concluded in the OA.

      I've worked as a contractor for several gov't customers. A case might be made that contractor skills are superior (doubtful) or that it's easier to replace incompetent contractors (true). Is that worth at least a 33% premium for the contractor? Maybe.

    2. Re:More costs involved. by Darkinspiration · · Score: 1

      Unless your contracted worker work on site for easy access and overview, Now you get to provide all the above plus Wage/Contract cost.

    3. Re:More costs involved. by jittles · · Score: 1

      I would beg to differ. Except on military installations, most of the contractors I have met work in corporate facilities. The only ones that I have seen work on facility provide hardware/software support of government systems.

    4. Re:More costs involved. by Call+Me+Black+Cloud · · Score: 1

      Exactly. I was going to post essentially what you did.

      An article linked from the POGO site quoted a trade rep: "The fact is that POGO's report draws false conclusions by comparing fully burdened contractor rates — which include all costs charged to the government, such as salaries, benefits, overhead, supplies, equipment, materials, rent and more — to an estimate of just salaries and benefits paid to a similar government workforce,"

      I am a federal contractor and I guarantee no one billing the government on our contract makes the kind of money alleged by POGO. We work in our own facility, we buy our own equipment, provide our own IT support, plus the overhead people (HR, senior management, for example) are paid from what the company bills for my time.

      As you stated, a fair comparison would be to factor in what the government pays for its facilities, equipment, executives, employee welfare, insurance. Also, it's impossible to get rid of a government employee. If we don't perform, though, they can terminate the contract.

  13. $268,653 per year? by ShavedOrangutan · · Score: 1

    I know lots of people in federal IT contracting. NOBODY makes that kind of money. I call B.S. on this whole article.

    And the gov't employees make more, work less, and walk away with a pension.

    --
    Godaddy is a scam and a ripoff.
    1. Re:$268,653 per year? by Morty · · Score: 4, Informative

      It's not about what the people make, it's about what the people cost. Remember that when the government hires a contractor, there is usually a contracting company. The company gets a lot more money per employee than the employee sees. Some of that is fair per-employee costs such as payroll taxes and employer-funded health care. Some of that is overhead -- the company's HR, payroll, accounting, contract offices, and profits come out of charging more per-employee.

    2. Re:$268,653 per year? by byteherder · · Score: 1

      I know lots of people in federal IT contracting. NOBODY makes that kind of money. I call B.S. on this whole article.

      You just don't know the right people. When I was working on a government contract, I was billed at $220/hr. Of course, I only got a fraction of that in salary. But still to the point, there are contractors and contracting companies billing the government at rates that would get them to $268,000/yr.

    3. Re:$268,653 per year? by demonbug · · Score: 1

      I know lots of people in federal IT contracting. NOBODY makes that kind of money. I call B.S. on this whole article.

      And the gov't employees make more, work less, and walk away with a pension.

      Lol. I used to work in private consulting. My "list" hourly rate was $122 per hour (most clients got an automatic 10% off; some were as much as 20%-30% off; a few unfortunates paid full price), which comes out to $244k per year assuming 100% billable. Do you think I actually made that? Hell, no! I was probably getting paid 1/4th that - including benefits - max. But that was the cost to a client to hire me. That's how consulting companies make money - the junior staff get billed out at insanely high rates for their experience level, and the difference goes to paying for everything else and providing profits. Sure, the most senior people might have been billing out at $200+ per hour, but a) they actually got paid a good portion of that, and b) clients rarely want to pay for much of their time.

      If a client actually had enough work to keep someone like me busy year after year then it would probably be cheaper to just hire their own staff person. Of course to get the expertise that comes with hiring a consulting company, just hiring the junior-level person who would be doing most of the work isn't really going to be a replacement - you would need to have enough work to justify an entire group, from junior level up to seniors and even management.

      Probably the best solution in terms of bang-for-the-buck for the government would be to establish a sort of in-house consultancy and hire them out to various divisions - but the way budgets are set up (and the way hiring is done) that really isn't feasible most of the time. It is politically and bureaucratically easier just to hire a private consultant for each project that doesn't fit neatly into what a division was set up to do.

      So, yes - hiring outside contractors is actually more expensive than hiring your own workers, but there is a lot more that goes into it. And while I'm positive (from first-hand experience) that a lot of the extra going to those private contractors is really wasted money (going to corporate profits rather than paying for work), I'm not sure there is a better way short of completely throwing out the bureaucracy and starting over with a more flexible design. The best option is probably to have a few auditors making sure that A) work that is being contracted out isn't work that could just as easily be done by the people you've already got, and, of course B) making sure that contracts are written in such a way to minimize the costs to the government (in my view the largest source of government waste currently is the failure to do B - contracts are often horribly one-sided, with the government getting the shit end of the stick).

    4. Re:$268,653 per year? by blair1q · · Score: 1

      Not unsurprisingly, exactly the same thing happens in purely private contracting.

      There's a reason your CEO drives a Jag even though he produces no code.

      Take your salary and bennies, and multiply by 1.6-2.5, and that's what any good salesman can sell your time and effort for.

    5. Re:$268,653 per year? by QuantumRiff · · Score: 1

      I'd love to be your mechanic! With a $90/hour shop rate, thats $180,000 He's taking home... Right?

      --

      What are we going to do tonight Brain?
  14. Consultant Rate != Employee Salary by thesandbender · · Score: 1

    You can't just compare a consultants rate to an employees salary. The government is paying for the employee's health care, pension, etc. As an independent consultant I have to pay for all that out of my rate. Additionally I have to carry Errors & Omissions Insurance, General Liability, Workman's Comp and several other things that are just the cost of doing business. A one-to-one comparison is very misleading.

    1. Re:Consultant Rate != Employee Salary by Lunix+Nutcase · · Score: 2

      Yes, you can't which is why they factored in benefits and everything else into the salaries they quote for government workers.

      Because the contractor billing rates published by GSA include not only salaries but also other costs including benefits contractors provide their employees,[66] POGO added OPM’s 36.25 percent benefit rate to federal employee salaries[67] and BLS’s 33.5 percent loading to private sector employee salaries to reflect the full fringe benefit package paid to full-time employees in service-providing organizations that employ 500 or more workers.[68] All supporting data for this study are found in Table 1 and Appendices B through D.[69]

      You aren't being as clever as you think you are.

  15. HA! by Anonymous Coward · · Score: 1

    "IT companies provide vastly superior skills"

    Anyone who has ever seen a contract change within a government contractor knows that is not true. I used to work for a major contractor in IT at a NASA center. The contract went though a change to a new contractor. What happens is that the existing contractor and other contractors bidding for the job all put in a bid claiming the talent of the people who already do the job. Yes, the company bidding on the work assumes that most of the workers currently doing the job can be rehired to do the job. So even when a new contractor wins the contract, the existing employees get to apply for the jobs they already have. The new contractor comes in with an attitude of "We're doing you a favor by letting you apply for / keep your job". And ultimately, about 90% of the employees stay the same. The brightest employees tend to say "Screw this" and leave soon, but the dead weight still stays around through each contract turnover.

    1. Re:HA! by BosstonesOwn · · Score: 1

      I have lived through this numerous times.

      I have left and got better pay other places. To be honest also I miss the perm folks, but the talented contractors tend to always move to greener pastures one we realize that the companies are not going to treat us well once we move over.

      Best thing I ever did ? - become a contractor
      Worst thing I ever did ? - become a contractor

      I'd like a slot but to be honest, all the perks they give I don't see in my pay check and when I have to pay taxes on it I end up making less then the perms. But this article fails to mention that we contractors pay for everything ourselves. So when it comes down to it we make less by a little.

      --
      This package Does Not Contain a Winner
  16. in other news by nimbius · · Score: 1

    private corporations routinely pay IT contractors more than their own IT workers for the privilege of
    being able to quickly hire and fire anyone they like without the cumbersome and frustrating effort of dealing with health, dental and life insurance as well as 401k and training/certification benefits. Thats right, the art of oursourcing is also a clever means of engineering around your inherent value as a human being. Much the same as "benefits" are a delightful means of ensuring corporations never pay their employees what theyre really worth. all glory to the invisible hand of the market.

    --
    Good people go to bed earlier.
    1. Re:in other news by tftp · · Score: 1

      able to quickly hire and fire anyone they like without the cumbersome and frustrating effort of dealing with health, dental and life insurance as well as 401k and training/certification benefits. Thats right, the art of oursourcing is also a clever means of engineering around your inherent value as a human being.

      I'm all for it. I don't need company-provided "health, dental and life" insurances; I reject them whenever I work as an employee; I can take care of my own needs myself, thank you very much.

      Much the same as "benefits" are a delightful means of ensuring corporations never pay their employees what theyre really worth.

      Every human, employee or a contractor, is always paid what he is worth in the given time and place, by definition. His compensation defines the worth. There is no other, divine measure of worth. If you are a genius, stop digging trenches and start working on a pocket teleportation device or on an LNR car. If you can't, you are in your rightful place already.

    2. Re:in other news by QuantumRiff · · Score: 1

      In public companies, Employees are counted as a liability, and contractors are counted as a 'cost of doing business'. They appear in different areas of the balance sheet, and can be used to make your company appear to be doing much better than it is.. That is the reason private corporations routinely hire contractors.. or because they have a single, short term project.

      --

      What are we going to do tonight Brain?
  17. Re:It's Called "Kickbacks" by FriendlyLurker · · Score: 1

    Or that outside contracting companies are a nice source of kickbacks that could not be "handled" otherwise.

  18. I'm certain .... by PPH · · Score: 1

    ... that the gov't could commission a study to nail this figure down.

    The POGO researchers say that the federal government itself does not know how much money overall it saves or wastes with its sourcing decisions and has no system for doing so.

    Any private IT consultants willing to take this task on for a truckload of cash?

    --
    Have gnu, will travel.
    1. Re:I'm certain .... by blair1q · · Score: 1

      The GAO and CBO are supposed to be doing exactly that, but they're too busy trying to prove that SSA isn't a fucking Ponzi scheme right now.

  19. Smaller Government by Bigbutt · · Score: 1

    Actually it was at least initially part of the smaller government initiative back in the 90's. All the IT folks had to be contractors. No government IT folks. Our first couple of contracts were so badly written that servers didn't get updated. If a server broke, the government paid to replace it. But if it got old, the contractor pays for a replacement. So as long as we could keep it going, it wouldn't cost the contractor anything.

    [John]

    --
    Shit better not happen!
    1. Re:Smaller Government by blair1q · · Score: 1

      If you don't know how to make an old server look like a broken server, I'm not sure I'd pay you anything...

    2. Re:Smaller Government by Bigbutt · · Score: 1

      As a fresh full time Unix Admin at the time, I was proud I could keep an ancient Sun pizza box running smoothly. When our Usenix server bailed, I spent several days trying to recover the Sun array when the lead admin finally dropped by to see what I was doing. He said it was built with a MTBF of 6 months and running RAID 0 so a disk fails, we replace the disk, lay out a new file system and let the Usenet feeds fill it back up again. A failing I have is keeping gear running long after it should have been pitched. It's a point of pride, what can I say? Prior to that, I was the last admin in the building that was able to keep LAN Manager running well on some cast off server hardware when everyone else went to Novell.

      I'm somewhat better now. I make my complaints about old hardware and am ignored. About the same results, I'm thinking :)

      [John]

      --
      Shit better not happen!
  20. not apples to apples by Casimireffect · · Score: 1

    Exactly. This survey seems to compare the rate that the government pays a contractor versus the salary that an employee makes. Those are not the same because all the benefits you mentioned, plus overhead. It costs a lot more than salary to run a business -- office space, power, HR, management, legal fees, accountants, etc. I guarantee the actual consultant isn't getting nearly all of the money that the gov't is paying the contractor for his services. However, when the government pays an employee a salary, by definition he gets all of that money.

  21. Re:comparing apples to oranges by Lunix+Nutcase · · Score: 1

    No, actually they aren't. If you had bothered to read their methodology on their study you would know this:

    Because the contractor billing rates published by GSA include not only salaries but also other costs including benefits contractors provide their employees,[66] POGO added OPM’s 36.25 percent benefit rate to federal employee salaries[67] and BLS’s 33.5 percent loading to private sector employee salaries to reflect the full fringe benefit package paid to full-time employees in service-providing organizations that employ 500 or more workers.[68] All supporting data for this study are found in Table 1 and Appendices B through D.[69]

  22. Re:when oh when by lwriemen · · Score: 1

    For the most part, often. According to the data Capers Jones has presented, contracted software work will be produced at about twice the rate of in-house work. It's not always true and it doesn't mean a company could run on only external workers. There is the domain knowledge aspect that pretty much requires in-house nurturing, otherwise the job could probably be handled by off the shelf software.

  23. How you define compensation by fermion · · Score: 1
    The article seems to be changing terms. At first it talks about total compensation, which to some degree might be comparable. If the total compensation of a contractor is significantly greater than the total compensation of the fully funded employee, then that might be a problem. However later in the article it talks of pay of the contractor, pay of the federal employee, and salary of the private sector. This of course is silly. The cost of an employee is far greater than the salary. There is pension, health, workers comp, etc.

    Even if the article is comparing total compensation to total compensation, which I doubt it is, there may be other cost involved. There have been times when I supplied my own equipment and I have charged beyond a normal hourly rate for the use of the equipment.

    For contractors that are hired for short time, it is not uncommon in industry to pay them large amounts of money. For instance, I have seen many contractors come in for a few weeks a years being paid double what an equivalent worker would make. It is not cost effective to have such a person on payroll, but their specific skills are sometimes needed. Think of a plumber or electrician.

    Which is not to say there is not waste. Just to say the article does not make a compelling case for waste, and certainly not a compelling case for 50% waste, which is what everyone wants to believe so that we have these historically low tax rates without negatively effecting economic growth.

    --
    "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
    1. Re:How you define compensation by Lunix+Nutcase · · Score: 2

      Because the contractor billing rates published by GSA include not only salaries but also other costs including benefits contractors provide their employees,[66] POGO added OPM’s 36.25 percent benefit rate to federal employee salaries[67] and BLS’s 33.5 percent loading to private sector employee salaries to reflect the full fringe benefit package paid to full-time employees in service-providing organizations that employ 500 or more workers.[68] All supporting data for this study are found in Table 1 and Appendices B through D.[69]

      Straight from the study where they outline their methodology. So even with a 36.25% benefit rate added to their salaries these contractors were still nearly 2 times more expensive.

    2. Re:How you define compensation by Stradivarius · · Score: 1

      Even so that's still not all the relevant costs to consider, if you want to truly know whether it is more cost-effective to contract or perform the work in-house.

      The authors of the study note many big gaps in their data in their methodology section, yet they go on to proclaim the government is "wasting billions" by contracting instead of hiring directly. The lack of data is so grave that such a conclusion - or in fact any conclusion as to whether the contracts were worth it or not - cannot be justified. For example:

      The contractor rates used as comparison were ceilings, not the actually negotiated rates paid (which are not published).

      The authors did not have access to government documents containing the analysis and justifications for decisions to contract work out.

      The study did not include contractor "overhead" costs - facilities (expensive in the DC metro area), supplies, administrative costs, etc. These easily add up to be more than the cost of the IT/engineering worker, even for a relatively small (read: lean) contractor. This overhead rate gets wrapped into the rate billed to the government, which is why you see multipliers like in the article. If the contractors were government employees, most of those costs don't go away.

      They did not include the costs of executing the contracts themselves.

      They did not include the costs associated with firing employees in government vs eliminating a contractor or telling the contracting company to provide a different worker. That includes the question of whether many contractors' being based in Virginia (a right-to-work state) rather than DC itself has any effect on such costs.

      They didn't have data on how much fluctuation in contract needs exists: If a government organization's needs fluctuate a lot, requiring different skill sets each year, then contracting for those skills as-needed makes more sense than creating a large churn in the government workforce. Conversely, if the roles required are usually the same, there may be advantages to building up the institutional knowledge in-house. This issue was ignored.

      They didn't have sufficiently detailed data to determine whether the government or the contractors had higher quality, more experienced, etc workers.

      The list could go on. There are way too many significant unknowns to draw much of a conclusion.

  24. Is this a good thing or a bad thing? by boyfaceddog · · Score: 1

    Let me try spinning this

    GOVERNMENT IT WORKERS PAID LESS THAN SAME WORKERS IN PRIVATE SECTOR
    Obama claims government tightening belt
    PRIVATE SECTOR CONTRACTORS BILKING THE US
    Senate hearings commence in two weeks
    GOVERNMENT UNIONS KEEPING COSTS DOWN
    Union leaders praised for austerity
    GOVERNMENT UNION WORKERS FORCED TO WORK FOR LESS THAN PRIVATE SECTOR
    Bill O'Reily attacks unions for not protecting worker's rights

    Here's what I think the 'real' spin should be:
    WORKERS AT DIFFERENT COMPANIES PAID DIFFERENTLY
    Film at eleven.

    --
    Here will be an old abusing of God's patience and the king's English.
  25. Pure bullshit by MikeRT · · Score: 1

    In the information technology category, POGO found that the federal government is paying contractors to provide computer engineers an average of $268,653 per year. That's nearly twice the average $136,456 it pays its own computer engineers and nearly twice the average private sector salary of $131,415.

    $268k is the combined invoice for the employee; $136k is the actual compensation of the GS14 or GS15 in question. Government contractor employees, unlike government employees, often work unpaid overtime for the government. That $268k may actually be 2500 hours instead of the 2080 hours normal to a 40 hour work week over a year.

    1. Re:Pure bullshit by jank1887 · · Score: 1

      I have yet to have met a GS14 or 15 who isn't regularly donating time to the government. You can claim up to a certain amount in 'credit hours' as long as its during core working hours (limited to banking ~24hours I think). Outside that, you usually need supervisory approval to claim either comp or overtime, and that needs to be approved the pay period before you want to claim it. So if something comes up that day, and people are working until 7-8pm when their normal hours end at 5pm, odds are they're working some of those hours for free. Just like any other business. Sure every GS employee is still 'paid hourly', but at a certain level its expected you'll get the work done, whenever. Just like in the private sector.

    2. Re:Pure bullshit by blair1q · · Score: 1

      unpaid overtime for the government.

      If you didn't negotiate Level-of-Effort, you screwed yourself.

  26. Near Impossible to Fire by Koreantoast · · Score: 1

    There's a reason why they're paid more: contractors serve at the whim of the government and can be fired at anytime. While they may be paid more, they lack the job security and numerous benefits that Federal employees receive. They can jettisoned at any time at the government's pleasure. I would also add that Federal employees are near impossible to fire. The paperwork to get rid of an underperforming worker is so complex and onerous that many departments simply transfer them or "promote them out" to get rid of ineffective employees. In fact, I think it would be easier to simply dissolve an entire department than to fire an individual employee. As one friend joked, "You'd have to kill someone get fired, and even then, it would depend on the circumstances." So yes, you're paying a premium for disposable labor.

  27. Just 2X ? by mbone · · Score: 1

    I'm surprised it's only a factor of 2.

    This has been a racket perpetrated since at least the Reagan administration, if not the beginning of time. Politicians make a big noise about how they are cutting government spending and gaining the efficiencies of the private market, by replacing civil servants with contractors. The contractors are much more expensive, which makes the companies hiring them a lot of money, some of which they use to lobby the politicians for more outsourcing. Politicians get campaign contributions, beltway bandits get rich, but somehow the government doesn't get more efficient.

    (Yes, there is a little bit of truth in the quick hiring and firing abilities of private contractors. It is true that it is hard to fire people from the government - but you can RIF them, if their program goes away. In practice, however, people rarely get fired or let go from either side of the divide, at least at the professional level. They get transferred around, but rarely laid off, and almost never fired. And, note well, civil servants are forbidden to directly lobby for their programs; contractors aren't. It can make a difference, and it makes it hard to perform mass layoffs of contractors.)

  28. It's also called "circumventing red tape" by dcavanaugh · · Score: 2

    The amount of administrative red tape to hire a "permanent" employee is immense. In government, this is tantamount to a lifetime offer of employment, so it is not to be undertaken lightly. Management needs to be sure there is a lifetime of work for the position and the candidate has to be a good long-term investment risk.

    With a lot less red tape, it is possible to scrape some budget money together THIS YEAR to hire a contractor. And it's not all that hard to get this year's money carried over to next year. And if by some chance the budget is cut, there is no collective bargaining crisis to determine who bumps who and which unfortunate soul loses a game of musical chairs.

    Hiring contractors is the workaround to almost any administrative obstacle. Government has MANY hiring policies (affirmative action for example). Outsourcers can do a better job of ignoring (or pretending to comply with) just about any HR policy mandate. Hypothetically, you can verbally tell an outsourcer that you want an attractive blonde woman for a certain job, and they will present a list of candidates, all of whom happen to be cute blondes. The only people who will even know about the opportunity are those who meet the undocumented pre-screening requirements. I'm exaggerating with the specifics of my example, but this kind of thing happens all the time.

    Kickbacks are part of the game as well. The outsourcing machine has a lot of moving parts, lubricated with an abundance of grease.

  29. how this is different from commercial IT by david.emery · · Score: 1

    i suspect the same set of concerns applies to a lot of outsourced commercial IT.

    But there's a lot of contracting overhead between the agency and the actual guy/gal doing the work. Add to that the substantial overhead costs for compliance to all the Federal Acquisition Regulations (FARs). Within the Government, there are major problems attracting -and retaining- talent; the Government trains them and if they're good, they go get much better paying/much better working conditions jobs in industry. The truly bad employees do get weeded out. So what you're left with in the Government IT ranks is generally a lot of mediocre people for whom the job security of a Civil Service job is their primary benefit. And the Government fails to invest in training, etc. So their primary job skill is supervising contractors. I don't envy Govt IT workers, but I'm not sure under the current system they would be able to execute without substantial contractor support.

  30. A few thoughts... by Registered+Coward+v2 · · Score: 1

    I wonder if the salary comparisons were all in costs of the federal employee - which I doubt because then you're at at a GS11/12 step 5 or so position for the quoted numbers, assuming a 1.5x salary multiplier to account for benefits. A 14 step 9 in DC already makes 133K per the salary table - so an all in cost would be around 200K minimum.

    What contractors bring is the ability to change the staffing levels quickly. Unlike federal employees, who after a year, are very hard to let go; a contractor can be terminated rather quickly for virtually any reason. So, the life cycle cost is probably much less than for an employee.

    The contractor isn't getting all than money either - as much as 20 - 30% is going to the company he or she works for to cover costs and profit. I know a lot of contractors that would gladly convert to federal positions because of the security and benefits but can't - the positions just aren't there. Unless Congress approves and funds positions an agency can't hire someone - even if both sides would love to do that. So, hiring contractor is a way to get needed skills without having federal positions. It's not like government agencies have tons of funded vacant positions in IT that they can't fill.

    My point is a simple salary comparison doesn't tell the whole story.

    --
    I'm a consultant - I convert gibberish into cash-flow.
    1. Re:A few thoughts... by dwpro · · Score: 1

      See the numerous other replies in this thread, or God forbid, RTFA, where the methodology is mentioned.

      Because the contractor billing rates published by GSA include not only salaries but also other costs including benefits contractors provide their employees,[66] POGO added OPM’s 36.25 percent benefit rate to federal employee salaries[67] and BLS’s 33.5 percent loading to private sector employee salaries to reflect the full fringe benefit package paid to full-time employees in service-providing organizations that employ 500 or more workers.[68] All supporting data for this study are found in Table 1 and Appendices B through D.[69]

      --
      Millions long for immortality who do not know what to do with themselves on a rainy Sunday afternoon. -- Susan Ertz
    2. Re:A few thoughts... by Registered+Coward+v2 · · Score: 1

      See the numerous other replies in this thread, or God forbid, RTFA, where the methodology is mentioned.

      Because the contractor billing rates published by GSA include not only salaries but also other costs including benefits contractors provide their employees,[66] POGO added OPM’s 36.25 percent benefit rate to federal employee salaries[67] and BLS’s 33.5 percent loading to private sector employee salaries to reflect the full fringe benefit package paid to full-time employees in service-providing organizations that employ 500 or more workers.[68] All supporting data for this study are found in Table 1 and Appendices B through D.[69]

      Actually, I did RTFA and nothing in it discussed POGO's methodology or its limitations. In fact, it said To make its cost comparisons, POGO used the General Services Administration's listed contractor billing rates alongside data from the Office of Personnel Management and the Bureau of Labor Statistics. which sheds no light on the methodology or how the comparison was determined.

      As for the other posts, yea, I missed them. I RTFA and made some comments based on the article. However, while POGO did make adjustments what is telling is this part:

      However, there are a number of factors that potentially limit the accuracy of POGO’s findings. For instance, over the course of our investigation, we discovered some disturbing limitations to the federal databases available to us. The most critical limitations are that: 1) the government’s coding, classification, and data collection systems are inconsistent and do not allow for reliable cost analyses[72] ; 2) government websites do not provide access to agency documents that detail cost estimates and the justifications for outsourcing decisions; 3) the government does not publish information on the number of actual contractor employees holding a specific occupational position under any given contract; 4) the government only lists the ceiling prices that it can be billed by contractors for the specific occupational positions—the government is at liberty to negotiate prices that are lower than those listed, but it does not publish those negotiated rates (however, based on POGO’s review of GSA contracts, and anecdotal evidence, the government tends to pay the listed billing rates rather than negotiating lower rates[73]) ; and 5) government websites do not disclose what the expected cost savings for service contracts are, nor the actual savings (or lack of savings) that result from those contracts. These shortcomings prevent government officials, as well as the public, from accurately assessing outsourcing costs.

      In short, they really don't know how accurate their data is but decided to base conclusions on it. That's not to say their isn't a problem with what the feds pay for outsourced IT but headlines as in TFA Fed. Government Pays IT Contractors Nearly Twice As Much As Its Own IT Workers are misleading. TFA cherry picked key parts to make it sound like the sky is falling without providing any details to put context around the numbers.

      --
      I'm a consultant - I convert gibberish into cash-flow.
  31. Small $ to scale up and down at will by ravenscar · · Score: 1

    Whoever wrote this article must not recall the major downsizing that occurred in many U.S. IT shops between 99-01. A large number of permanent employees were let go in that period. That resulted in a number of problems including decreased morale and the outflow of tons of knowledge - knowledge that had been built up in a single worker that management figured would never leave. Because of those problems, a number of changes were made. One of those changes was to keep, as permanent workers, a small set of skilled people that would necessary even in times when IT demand was limited. In times of increased demand, the shops would ramp up with temporary workers. While, this philosophy comes with its own set of problems, I largely agree with its intent and results.

    The need for this is even greater in government shops. Remember, in many government sectors, when a person is permanent they really are permanent. There are contractural obligations that prevent the government from letting people under all but the most extremem circumstances. Downsizing permanent IT employees to cut $$ out of the budget just isn't possible. In today's world, where government needs to be able to scale up and down frequently, the best option is to do so with temporary employees.

    Are temporary employees more expensive? Sure. You have to pay a premium to someone to have the luxury of letting them go at any time for any reason - especially when doing so isn't just a possiblity it's a guaranty. In addition, temporary employees often bring specific skills into the shop that you need for a limited time, but wouldn't want to maintain permanently. These skills cost $$.

    The cost of IT outsourcing is likely the least of most government's problems...

  32. mea culpa by thesandbender · · Score: 1

    That's what I get for not RTFA completely.

  33. Executive Summary by ThatsNotPudding · · Score: 1

    We don't have to pay for contractors' insurance and benefits (and probably neither do the contractors, who might farm out some work to their own contractors). At this rate, whether public or private, the retirement plans for *actual* workers look more and more like the Soylent Green screen play. Or maybe Mad Max.

  34. Film at 11 by Hognoxious · · Score: 1

    In other news, that steak dinner that cost me 20 bucks at a restaurant could have been made at home for a Lincoln.

    --
    Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  35. That's a pretty good deal for the Federal Govt by Timmy+D+Programmer · · Score: 1

    Since, the 'Pay' is only about half of a federal employees cost. So it's a wash, now bring in the fact that they likely only need the contractor for a limited time, and now its a good deal.

    --


    (If at first you don't succeed, do it different next time!)
    1. Re:That's a pretty good deal for the Federal Govt by dwpro · · Score: 1

      They factored that in. Try again.

      Because the contractor billing rates published by GSA include not only salaries but also other costs including benefits contractors provide their employees,[66] POGO added OPM’s 36.25 percent benefit rate to federal employee salaries[67] and BLS’s 33.5 percent loading to private sector employee salaries to reflect the full fringe benefit package paid to full-time employees in service-providing organizations that employ 500 or more workers.[68] All supporting data for this study are found in Table 1 and Appendices B through D.[69]

      --
      Millions long for immortality who do not know what to do with themselves on a rainy Sunday afternoon. -- Susan Ertz
  36. I'm guessing there is a lot of ripping off by Sycraft-fu · · Score: 1

    A story on this point:

    A friend of mine consults for DC public schools. Yes he does make quite a bit but it isn't actually a story about him, he at least delivers for his money.

    So they want him to write a bigass database processing script. It will get fed data from a bunch of sources, including a web interface for users, and have to process it and store it in a Quickbase (Intuit's online database service). No problem, this is what he does best. So they've laid out for him what they require, he lays out for them what he'll require in terms of time and materials. Only material is a server. He tells them he'll need a simple Linux server, doesn't have to be all that powerful nor does it need to be dedicated, just some place the script and web server to live. He figures this is an easy request.

    Turns out not. They don't do their own IT, they outsource it all. So they say they have to go get approval for the funds. This surprises him since they are paying him like 5 figures for all the development work, so what should a server matter? Well turns out the company they outsource IT to charges them $3000/month for a basic Linux VM. I'm talking like 20GB disk space, 1 virtual CPU, 1GB RAM.

    He was just floored.

  37. Re:Are you kidding me? by NickstaDB · · Score: 1

    AC... This was me, updated Firefox logged me out!

  38. Bennies are accounted for... by Radical+Moderate · · Score: 2

    ...in the study. I work in government IT, and figuring the cost of benefits is standard procedure when we're working up a budget, and trivially simple. Here's a link to the actual study

    You're right about bringing in consultants for short-term projects, of course it makes more sense than hiring.

    --
    Never let a lack of data get in the way of a good rant.
    1. Re:Bennies are accounted for... by Enry · · Score: 1

      Still, only 2x isn't that bad.

  39. Unanswered question: Total cost? by Anonymous+Freak · · Score: 1

    Is that SALARY or TOTAL COST?

    I bet they're comparing contractor total cost to government employee salary.

    Oh, look, there it is:

    To make its cost comparisons, POGO used the General Services Administration's listed contractor billing rates alongside data from the Office of Personnel Management and the Bureau of Labor Statistics. The researchers point out that its government salary data does not incorporate overhead costs—management and administration, supplies, facilities—that private outsourcing firms may factor into their billing rates.

    --
    Another non-functioning site was "uncertainty.microsoft.com."
    The purpose of that site was not known.
    1. Re:Unanswered question: Total cost? by dwpro · · Score: 1

      Actually, that's not quite it. They did at least some due diligence.

      Because the contractor billing rates published by GSA include not only salaries but also other costs including benefits contractors provide their employees,[66] POGO added OPM’s 36.25 percent benefit rate to federal employee salaries[67] and BLS’s 33.5 percent loading to private sector employee salaries to reflect the full fringe benefit package paid to full-time employees in service-providing organizations that employ 500 or more workers.[68] All supporting data for this study are found in Table 1 and Appendices B through D.[69]

      --
      Millions long for immortality who do not know what to do with themselves on a rainy Sunday afternoon. -- Susan Ertz
  40. Article admits skill levels not factored in by drnb · · Score: 1

    Conveniently, we have plenty of shrill talking heads telling us that the private sector is always more efficient. That should be a viable substitute for so called "empirical evidence".

    Not really. The article admits that skill levels are not factored into the comparison. The article mentions that the outside contractors may possess superior skill levels and be better trained and that there may be savings related to having more capable people running and implementing a project. I'm not claiming this is necessarily the case, I'm just saying the it is premature to make claims as to whether money is being well spent or wasted. I know some very highly skilled people who work in a government IT job, however I've also met some that were more comparable to DMV workers.

    Perhaps I missed it but its also not clear if the comparison is strictly based on wages vs hourly billing rates or whether other employee benefits are also factored in, social security contributions, insurance , vacation, retirement contributions (if not a full pension), etc.

  41. A sore subject by borkthafork · · Score: 1

    I am a soldier currently deployed to Iraq in support of the current drawdown. I manage a videoteleconferencing suite that was supposed to be run by civilian contractors, but out of the two that worked the shop, one did his time and left on time, and the other got a better job and left early. We were sent a replacement. I had to train this person up, but then they were moved to another base to cover down on the contracting companies other commitments. My soldier and I now run the shop in place of the civilians that were there before. My soldier has learned faster and performed better than the civilian I trained and makes about 1/5th of the pay that contractor made and only gets to go home for 15 days once during the deployment. The contractor gets paid leave every three months and left us somewhat... disappointed when it came to performance. Soldiers can do what contractors can, and if left to focus on that job specifically, we may even outperform as we have invested a bit more into the outcome. Some contractors we really do need, but some are getting heavily overpaid for something a soldier could easily learn how to do. I think the system needs an overhaul.

  42. Its the same in the Private Sector.... by JATMON · · Score: 1

    Government or Private Sector contracting, it is all the same. A contractor is brought in to complete a specifc task and are kicked out when they are no longer needed. If you instead hired an employee, you would have to find them a new position once the project that you hired them for is complete. You might have to cross train them for a new position. Also, it is not easy to fire an employee unless they royally screw up and sometimes not even then. But with a contractor, you can get them replaced or just cancel the contract.

    Another benifit of having contractors has to do with PR. When have you ever heard about a company or government agency get bad publicity for getting rid of a bunch of contractors? But if you have to layoff employees, it makes the news. Canceling/ending a contract just does not have the same negitive stigma that layoff do eventhough in the end, depending on the contracting company, the same number of people could be unemployeed.

  43. Flexibility is one of the reaons by Pragmatix · · Score: 1

    I have spent some time working on government contracts where I was one of many contractors sitting at the client location full time. Part of the reason that particular agency used contractors was because their HR process was very difficult to deal with. It was very hard to hire new full time employees and it was almost impossible to fire anyone. The director knew he was paying more for the contractors, but he also knew he could quickly alter his workforce if his budget changed.

    As far as costs go, the full time employees were probably paid 10-15% or so less than the contractors (in terms of what the contractors took home), but they had much better benefits (not to mention job security). Most of the contractors worked for consulting companies, and they were the ones raking in the cash, not the actual contractors. In fact the agency I worked for forced everyone to go through a middle-man company if you wanted to do any work for them. The middle-man took from 10 to 20% off the top just for time entry and billing.

    Don't forget that many government agencies have no real incentive to save money. If an agency improves their efficiency and slashes the budget by 10 million dollars, it just means they get less money the next year. It is why you sometimes hear about agencies going crazy at the end of the fiscal year and using up their remaining budget to buy whatever they can, regardless of need, so they can show they spent their allocated monies.

  44. Ever known a gov't employee who got fired? by iceperson · · Score: 1

    Me either. So much for accountability...

    I've been working for the government pretty much since I joined the Marines in '91, and I can't name 1 government employee who was fired in that time. In fact, we had a male employee who physically assaulted one of the women in our office enough to put her in the hospital and him and jail, and when he returned they had to accommodate him with a work area because he had a restraining order!

    1. Re:Ever known a gov't employee who got fired? by GameboyRMH · · Score: 1

      Yeah I know plenty, 3 at this job alone.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    2. Re:Ever known a gov't employee who got fired? by geekoid · · Score: 1

      I know several. 5 in fact.
      1 got pgysical with another employee, he was dismissed the same dat
      2 due to general incompetence. They went through the system, so it took 8, and 6 months.
      2 for having sex in the bathroom.

      Also, look for people who 'resign'. I know plenty who suddenly 'resigned'

      Are you telling my you don't know ANYONE who was discharged before the end of their contract in the marines?

      Accountability is much higher in government work, then in the private sectors.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    3. Re:Ever known a gov't employee who got fired? by iceperson · · Score: 2

      Sure I knew people who were discharged, but in my 20 years of federal service, 8 as a Marine and another 12 as a DOD contractor, I haven't known a single civilian government employee who's been fired. I have known of at least 2 who weren't allowed to have computers though because they were found downloading porn at work. The agency had to make "accommodations" for their "illness".

      Oh, and I call BS on your same day dismissal. Didn't happen. Maybe a student aid, a summer hire, or possibly a CO-OP employee, but not a tenured gov't employee.

  45. Toilet Seats by kernelrahl · · Score: 1

    No wonder the toilet seats costs so much, someone making double can't sit on a regular old toilet seat! They need something that will stimulate the mind/bunghole to keep them well paid and all internals functioning correctly!

  46. Standard by residieu · · Score: 1

    Isn't this standard? You pay contractors more than you pay your internal workers. You need to, because you don't pay for any of the contractor's benefits. And you don't pay any of the overhead of that contractor's employers. The number I've seen thrown around is the total cost of employing someone is twice their actual pay rate.

  47. Re:Things have changed... by JATMON · · Score: 1

    I don't see why they deserve more than the contractor gets paid in PURE PROFIT with no costs of their own. If the tax payers knew, there would be a revolt. We can only assume that since these corporations have NSA contracts, that any whistle blower will be quickly "disappeared".

    Who do you think writes the proposals to win the contracts? Who do you think does all the marketing? A lot of contract awards hinge on the reputation of the contracting companies. Of course they are going to take their cut even it they sub the work out, They are the ones that did the initial work to win the contract, they are the ones that have to maintain the contact and it is their reputation that is on the line not their subcontractors. If you are awarding a contract, who would you award it to, a company that you have never heard of before or a large firm that you have had good experience with? Even on goverment contracts that are considered "Small business Set Asides", the small business will prime the contract with one or more large contractors backing them as subcontractors.

  48. WAY too much detail missing by sjbe · · Score: 1

    Lots of important details are left out of TFA:

    • Are these pay rates just salary comparisons or do they include benefits? Benefits can be 50% of the base salary or more.
    • Are they doing the same job?
    • Contractors typically get hired because they have specific expertise that is lacking in the organization. It's not clear that the government workers have the necessary skill sets or can be hired in a reasonable time frame if the necessary expertise is lacking.
    • Are they including overhead costs in these calculations? The cost of a worker is more than just salary. Contractors charge more because they have overhead and also need to make a profit.
    • Are they including search costs? It takes time to find workers to do a job (contractor or not) and it's not clear that these costs are included.
    • What about the opportunity cost of delaying while the government gets their people working on the job.
    • What liability issues are in play if any?
    • How much net savings are we talking about here? If we are just talking about a few dozen employees, then we probably don't care very much. If it is thousands then we might be talking about some real money.

    I'm a cost accountant in my day job and a good cost analysis is not a simple salary comparison.

  49. We all knew it... by hesaigo999ca · · Score: 1

    >The POGO researchers say that the federal government itself does not know how much money overall it saves or wastes with its sourcing decisions and has no >system for doing so

    We all knew this from the get go, there is absoluteley no way they will get /create the neccesary appplication or system to give them that data either, as it would be a little too detailed for the liking of that government. If you knew how much your government was wasting of your tax payer dollars when all they had to do was be a little smarter shopper, people would just stop paying their taxes.

  50. Contracting rates of 1.5-2x salary are *minimal* by Anonymous+Brave+Guy · · Score: 1

    Exactly. Paying contractors 1.5-2x the equivalent salaried staffer is probably breaking even or better for most organisations. The overheads of employing someone are far higher than most employees realise: providing a suitable place to work, all equipment and software required for the job, paid vacation and sick time, whatever pension/health cover/benefits go with the territory, training expenses, people to handle management and administrative overheads... A freelancer has to eat all of that before they even start making any useful money.

    There are a lot of advantages to being a freelancer in IT, if you are willing and able to wear all the extra hats that go with it as well as getting the day job done. But when people have a dig at me because I get "tax breaks" here in the UK, I tend to laugh, and ask how they'd feel if they only got paid for 2/3 of their working hours, didn't get paid at all for any non-working hours, had to spend perhaps 20% of the income they do get on overheads of one kind or another, etc. Usually they've got bored and conceded defeat before I run out of things I have to do personally that their employer does for them. :-)

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  51. IT contractors have a lot of over head and levels by Joe_Dragon · · Score: 1

    IT contractors have a lot of over head and levels of companies that are some times very far from the job leading to people not knowing what is going on and makeing it hard to get stuff done at times or leading to people being on site with no work to do as other parts of the contract are at a different page.

    Some contractors also rotate people in and out so you have lot's of people who don't know how the site they are on works and what needs they have.

    They are better off going in house and maybe even having a Gov IT department that does IT work for all of GOV (other then small stuff that each department needs on there own).

  52. How Do You Find These Contracts? by LifesABeach · · Score: 1

    Is there a web site, or publication that one could view? Let see for myself...

  53. Re:Contracting rates of 1.5-2x salary are *minimal by Vexer77 · · Score: 1

    I believe typical professional service consultancies aim for billing rates that are 2.8 to 3.3 times the employees salary to run profit margins of roughly 15%. And I would bet any things that contractors are WAY more efficient than government employees, based on my experience.

  54. The Worse of Socialism and Capitalism by ideonexus · · Score: 2

    Exactly. The contractor gets paid twice as much, not the employees. In fact, profit motivations of the contractor put pressure on them to pay their employees as little as possible, and since most contracts are written in such a way as to absolve the contractor of responsibility if projects fail, the easiest way to maximize profit is to hire unqualified staff.

    This is my firsthand experience. I was government contractor for 10 years. They hired me because I wasn't very qualified to write software (this was on a mission-critical aviation logistics system), but, lucky them, I worked hard and became one of their star programmers. I was the second highest-paid person on staff with our contractor in an organization of over 100 people. I found out from a leaked document that my company was making $150k a year off me after paying my salary. Since most employees were making less than half my salary, the contractor was pulling in about $15 to $20 million a year on our contract since the only overhead they had was covering our health insurance and 401ks (offices, computers, furniture, and other supplies were all provided by the government). That's $15 to $20 million a year to serve as a Human Resource department for 100 employees.

    When the contract came up for recompete, the contractor used extremely heavy-handed tactics to try and force me to sign an exclusivity agreement with them, which was pointless in a right to work state. I objected on the grounds that the company provided no added value to the contract and that the employees, most of whom were just warming chairs, would get picked up by whoever won the contract (saw this happen many times over the years). It was a principle thing and I didn't appreciate being bullied. When they continued to pressure me (a manager actually blocked the door to prevent me from leaving without signing the document), I produced the leaked document and told them I would quit without a 10% raise. They let me go without a second thought.

    Since I left, the software project I had spent the previous three years working on has completely failed without there being anyone qualified to work on it, but the contractor doesn't care because they get paid no matter what and it's cheaper to hire people with zero programming experience and pay them diddlysquat to struggle through their job than it is to reduce your profits and hire people who are educated software development. I'm not bitter about being let go, but I am bitter about the project failure. I was really dedicated to my job and felt I was making a difference in the organization, but the contractor, who honestly didn't really know anything about my job or the project I was working on (Government employees managed me directly), could only see the dollar signs.

    I assure you, this is not about placing "blame." This is all about giving government employees the ability to put checkmarks next to items on their todo list. The department where I worked hired a contractor to build a LIMS for them so they could claim progress on a project the higher-ups were demanding. The government manager who started the project took credit for making progress on it after he got promoted elsewhere, the contractor got $15 million for producing a single webpage with a a phone number field that auto-focused to the next input after you filled it in, and the new government manager killed the project and took credit for eliminating waste.

    "You need to go get rid of 250,000 contractors in the Defense Department, where you can really pick up some small change." ~ Former Republican Senator Alan Simpson, February 16, 2011 on balancing the budget (source)

    "The problem with Socialism is Socialism, the problem with Capitalism is Capitalists," as William F. Buckley once said. Government contracting combines the worst elements of socialism and capitalism.

    --
    i ~ Celebrating Science, Cyberspace, Speculation
    1. Re:The Worse of Socialism and Capitalism by Courageous · · Score: 1

      The contractor gets paid twice as much...

      Shrug. What the employee is PAID when working for the government isn't interesting. How much they COST to be employed by the government is the interesting figure. I bet it's a lot.

      C//

  55. Why hasn't anyone asked... by Ragun · · Score: 1

    Why hasn't anyone asked about benefits yet?

    I have read every single comment on this board, and no one seems to be asking about if they factored in benefits or not.

    I will take this to assume they have not, and merit my above average cleverness for the discovery. I hereby declare, by right of my ideology, that this article is fraudulent.

  56. Re:Parent is the most accurate reason here. by magamiako1 · · Score: 1

    Most of them have no idea, and it's only something you learn when spending enough time in the region to truly see how sickening it is.

    I interviewed with a few "contracting" companies here and there and demanded even half of what I get in full time positions of *private* companies (that may do government contracts), and they looked at me like I was crazy.

    That said, the pay is usually pretty damn good.

  57. THE FIX is being open & accountable by glittermage · · Score: 1

    Make the process of requirements & biding 100% open & accessible to public scrutiny for a defined time period.

    Hold any party accountable (public or private) for not delivering agreed upon results.

    End of story

  58. Re:Including Benifits by xenocide2 · · Score: 1

    Which is why the study looks at total compensation instead of just salaries:

    Because the contractor billing rates published by GSA include not only salaries but also other costs including benefits contractors provide their employees,[66] POGO added OPMâ(TM)s 36.25 percent benefit rate to federal employee salaries[67] and BLSâ(TM)s 33.5 percent loading to private sector employee salaries to reflect the full fringe benefit package paid to full-time employees in service-providing organizations that employ 500 or more workers.

    --
    I Browse at +4 Flamebait

    Open Source Sysadmin

  59. been doing that for a while by bhenson · · Score: 1

    When i deployed to Iraq, the contractors there made 140K a year. Being military i make less than 40 to do the same work for the entire year. Something tells me we need to trim the fat starting with contractors that make retarded amounts of money....

  60. God knows we can't hire new Federal employees by frank_adrian314159 · · Score: 1

    First, it would be increasing the "size" of government, even if it lowered its "cost" and the R's still wouldn't let that happen. Second, they tend to be liberals...

    --
    That is all.
  61. 40 hour limit by KingAlanI · · Score: 1

    "As a fed contractor, I never put in more than 40 hours a week. That is what we had in the budget, and to do more than that would have resulted in issues."

    There was also a strict 40-hour limit for me as a direct federal employee (summer internship; I was classified as GS).
    Moreover, they were also strict about it being 8 hours a day, 5 days a week. This meant that I couldn't work longer when I was having a good day & work less when I was having a bad day, which would have gotten more out of the same 40 hours.

    --
    I listen to both RIAA and non-RIAA stuff if I like the music, tangential business/politics nonwithstanding.
  62. should be 2.5x by Ungrounded+Lightning · · Score: 1

    Back in 1965-66 a consultant talked with some college students, including me, about consulting. One thing he mentioned was a rule of thumb for computing a consulting rate.

    For a middle-to-long-term consult the rule of thumb was one percent of an annual salary per day. This comes out to the billing rate being 2.5x the salary-only cost (assuming a 40 hour work week).

    The multiplier covers a lot of stuff. Notable items include: The work done by the consulting firm (including sales, billing, carrying receivables, government forms, and non-billable consultant time) and their profit margin. Benefits for the consultant - both ordinary benefits such as medical and the company's part of social security and replacement of retention benefits such as bonuses and stock options. Paying the consultant enough that he can absorb "dead spots" between contracts, risk of them being long, and other fallout from the company's lack of interest in retaining him past a project's end. And a premium for the actual work because he's expected to be more expert in the field than those who take salaried positions rather than risk and succeed in the consulting market.

    Many of these costs have equivalents that actually are paid for salaried personnel, but don't show up in the salary itself. For instance: Recruiting costs correspond to the consulting firm sales costs PLUS possibly the firm's recruiting costs to get the consultant onboard in the first place, but because consultants are onboard for less time the sales costs occur more often.

    Right now consulting prices are depressed, due to a flood of laid-off hi-tech workers taking consulting positions at low rates as a stop-loss. But it looks to me like the government is still getting a bargain.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  63. There's a reason for this by itsphilip · · Score: 1

    Typically organizations will bring in a consultant when they have a short-term problem that they want to solve, or just need extra hands for a big project. Now even though they're paying their contractors "twice" what they pay their employees, they are only getting money. Working as a contractor means you don't get health insurance plans, retirement, etc. Additionally, you're only bringing these folks in for (hopefully) a limited period of time, after which time they move on. So really in the end, it's pretty close to being the same money-wise. Maybe this "watchdog" group should watch something meaningful. Everyone knows contractors make a bunch of money, but there's more to it than just the money.

  64. Blah blah, poimnt to the paragon of efficiency by gatkinso · · Score: 1

    that the government is being compared against.

    It certainly isn't private enterprise.

    I know that the uproar is all about this waste (and it is) being paid for by JQ's taxes...but JQ pays for the waste in industry through higher prices.

    I know goods and services are voluntary, taxes are not, all that... but seriously, I am looking for the human enterprise that is efficient (or even equitable) and I am not coming up with much.

    --
    I am very small, utmostly microscopic.
  65. Duh by jon3k · · Score: 1

    Government IT contract workers make obscene money. I've seen horribly unqualified people taking network/system admin jobs in the middle east for $90k, $150k, $250k for a 9-12 month contract. The first $70k(ish?) is tax free. Its insane. Most of them sit in little NOCs and watch lights blink all day.

  66. What about deferred liabilities like pensions? by alexmin · · Score: 1

    Once you pay contractor, there is no unknown deferred liabilities that would likely double or triple FTE cost if accounted for.

  67. A former Government Contractor by JRHelgeson · · Score: 1

    It is EXTREMELY expensive to do work for the Federal Government - first, most these high-paying jobs require a security clearance, which costs (depending on the level of clearance) ~$25,000 to get, and $15,000 per year to maintain. Then, when you are flying for a government project, you ALWAYS have to purchase fully refundable tickets, which means you pay 2x-4x the price you pay anywhere else - because the project you're working on will ALWAYS get rescheduled at the last moment.
    Government is hopelessly dysfunctional, every project takes 2-10x longer than it should... yet if it weren't for the contractors, nothing would get done. At least a contractor can leave agency A, and go to agency B while A tries to figure out what the heck is going on.

    Joel

    --
    Good security is based upon reality and common sense. Common sense is a function of having common knowledge.
    1. Re:A former Government Contractor by Cimexus · · Score: 1

      Wow - interesting. Federal Govt. security clearances are free here (Australia) or at least free to the applicant themselves. The government department hiring the employee may pay for them - I'm not sure - or they may in fact be completely free for everyone involved. All I know is that I have had to get one several times (due to expiry etc.) and in each case, no payment of money was involved.

      We can buy whatever flights we want too (well, subject to any contractual conditions to the contrary, but I've worked with at least ten different departments here and never seen anything like that). Obviously it's at our own cost/risk if something DOES get rescheduled, but at least the choice is there.

      I can't imagine it actually costs that much in man-hours for the relevant authorities to do the necessary checks and grant you a security clearance. Quite a nice little money-maker they seem to have found there (shhh, don't give the Australian Federal Govt. any ideas!)

    2. Re:A former Government Contractor by JRHelgeson · · Score: 1

      Wow - interesting. Federal Govt. security clearances are free here (Australia) or at least free to the applicant themselves.

      Here in America, if you are going to work for the agency directly, there are no direct costs for the security clearance. So no difference there. The key here is that if you are a private contractor, that contractor must bear those costs directly themselves, and they must recoup all those costs in billable hours.

      --
      Good security is based upon reality and common sense. Common sense is a function of having common knowledge.
  68. BS on your BS by BenEnglishAtHome · · Score: 2

    I just retired from nearly 30 years at Treasury. I can't count the number of employees I've seen fired.

    Perhaps a dozen were led out in handcuffs for violating disclosure or other laws.

    I've seen behavior infractions (fisticuffs, actually) result in a "both of you go home and we'll sort it out later", with the conclusion that one voluntarily resigned and the other was fired.

    My agency was the IRS and IRS employees get ZERO slack on filing their tax returns late; 100s of employees have been fired for that reason since the Revenue Reconciliation act of 1998.

    I've seen student aides arrested and fired for stealing.

    I've seen at least a half-dozen fired for fully-documented poor job performance, a process that takes time, to be sure, but can be done.

    I've seen two fired for downloading porn. I saw one (a Special Agent, no less, who apparently thought his off-network investigative workstation was immune to audit) who was allowed to resign before he was arrested two weeks later for spending all day at work and leaving his computer running all night downloading kiddie porn.

    Hell, I even saw a *Division Chief* fired and criminally prosecuted for falsifying less than $1000 in relocation expenses on a travel voucher!

    Yes, tenured civilians in government service get fired. Maybe they don't put as much emphasis on personal accountability at whatever agencies you worked for, but I know that at the IRS, employees got fired.

    As an aside, relative to a circumstance in the GP post - I've known 7 employees who got caught having sex at work. 2 got fired. 2 got a 3-day suspension with loss of pay. But 3 got kicked upstairs/promoted out of the place. (The number is odd because one of the caught employees was screwing a contract security guard. She got promoted; he got fired.) I never really understood the rules surrounding that particular infraction.

  69. Need a 1 year limit on contracts by zippy590 · · Score: 1

    Contractors can be useful in some situations. For example if an agency is upgrading a database system, they need people to migrate the data, test the new system and train the db admins and users. For a six month project additional costs of using contract labour is justifier. If we limit contractors to one year with a given agency they will be used on these kinds of projects and not just be overpaid perma-temps.

  70. longevity of biz vs govt by minstrelmike · · Score: 1

    Most businesses go out of business in the first two years. Eventually, most businesses go out of business period.
    From a statistical point of view, comparing the costs in general of doing something that will eventually end (private industry) vs doing something that isn't supposed to end (government) seems like comparing Apples and Oracles.

  71. An outside vendor has additional costs by lsatenstein · · Score: 1

    2X the internal staff costs. Why not. As an outside vendor, I have to pay group insurance, pension benefits, and a whole slew of fees, in addition to the work of book-keeping and our admin salaries. If we make 10%-15%, per placement, we are doing well. We make some growth with volume, but then we have to pay for extra courses to keep our employees from jumping ship.

    --
    Leslie Satenstein Montreal Quebec Canada
  72. Re:comparing apples to oranges by jklovanc · · Score: 1

    So the first two points are out. The other three are still valid and there are probably more factors than that. Wages and benefits are still just paid directly to the employee. The company incurs other costs per employee.

  73. No bennies, first to go in a RIF or project end by karlandtanya · · Score: 1

    2x the cost of an employee sounds about right.
    Load factor on that employee is about 2 anyhow, more if you include ineffeciencies (idle time between projects).
    It's a wash.

    --
    "Reality is that which, when you stop believing in it, doesn't go away." - Philip K. Dick
  74. Only twice as much? by DarthVain · · Score: 1

    I find this surprising. While I never have worked for the US government, from my experience it is much much more than that.

    All consultants/contractors see government as a feedbag and will rip them off as much as possible. Its a big payday. This is hardly limited to IT workers, though they probably make up a large percentage of the total.

  75. Re:gs, wg vs contract work by _0xd0ad · · Score: 1

    BTW the female told me that Open VMS is not UNIX

    OpenVMS isn't UNIX, though many UNIX commands have been ported to it. What is OpenVMS? Which is better, OpenVMS or UNIX?

    OpenVMS was designed entirely within HP and specifically within the former Digital Equipment Corporation (DIGITAL). ...It was once certainly true that OpenVMS and UNIX were quite different. In more recent times, there are tools and C APIs on OpenVMS that directly provide or that easily support porting UNIX programs and commands

    its just an application that runs on a Microsoft Server!

    I assume they were running it in a VAX hardware emulator on a Microsoft Server. Although OpenVMS does natively support Intel Itanium-based servers, so it's possible that a Microsoft Server with the Itanium chipset could be repurposed to run OpenVMS.

    I only know what I see. This is what I see: you were ill-informed and ended up looking like a moron.