The federal government has technology needs just like any private corporation. It is hard to find good IT talent and even harder to retain that talent.
So, the various IT departments within the federal government often turn to contractors to subsidize the existing federal staff. The idea is that these "experts" can come in and hit the ground running — no training required. They perform a very specialized function, and, in theory, do it very well. When the job is done or the contract expires, they vanish and move on to another client. It sounds like a cost-effective idea.
But is it?
I have been running a cybersecurity division for a federal agency for enough years to become fully jaded with the contractor selection process. Some will argue that I have no idea what I am talking about. I am just a dumb fed who cannot possibly comprehend what it takes to survive in the private sector.
Actually, I ran an IT corporation for about 10 years. I know exactly what it costs to pay for a benefits package, health insurance, training and all the other costs that go into fully burdening a billable hourly rate for IT professionals. Some will be offended that I am calling "all contractors" thieves or liars. I can accept that, and I know there are very skilled contractors doing IT work for the fed every day; however, I also know that for every IT rockstar currently employed by the fed, there are about 20 that are terrible.
The contractor selection process begins with the fed issuing a request-for-proposal (RFP), which contains a rather lengthy description of the type of work and other details. Companies then submit proposals for the work which they customize to fit the RFP. These proposals now need to be reviewed, so that the best candidate wins the contract. The fed creates a review panel hopefully consisting of people (feds) that are qualified to decide who that company should be.
I have sat on a number of these panels and reviewed a myriad of proposals sent in by private contracting corporations — many of them pitifully lacking in just about every area. When a contracting official has to begin the process by reminding the panel that they cannot take off points due to poor grammar, misspellings or unclear sentence/paragraph structure, it is a sudden reminder that we, as a federal agency, embrace mediocrity. It is like coming to a job interview without showering, wearing gym clothes, and handing in a resume full of typos and other glaring errors, yet being told by your company to "ignore all that." Personally, I find it very hard to ignore.
Alas, the futility of my exercise is clear. Many of the proposals are just bad. It's tough to overlook the inexperience and ambiguity I am reading, but I am told I must — and so I do. Thank you, Uncle Sam, for appealing to the lowest common denominator, and ensuring that my contractor support will be terrible for the next year, and then likely for the four option years that will follow.
One of the sections of each proposal typically includes resumes of the actual people who will support the contact. There are times this section looks fantastic. But wait! The people that are being pitched with this proposal have no intention of being a part of this new contract. What a scam!
Contractors lament about high overhead costs, marketing expenses and how they are barely breaking even on their contracts. But IT contractors are commonly charging the government $200K or more per year per person and paying them $100-120K per year. I recently learned of a contractor to a federal agency who was being paid $175 per hour for Cisco work which breaks down to about $350K per year. Even if the net profit to the contracting company was a measly $150K (sarcasm intended), that's not too bad for one employee.
And here is where the contractor magic gets even better — if you demonstrate that you will tolerate substandard talent and not complain, they will start filtering in "professionals" to your office who cannot possibly command salaries higher than $45K-$75K anywhere. So they are charging $200K per year and fill the slot with a person that they only pay around $50K. The profit margin just got a lot bigger, and my technical support just got a lot worse.
A healthy contractor relationship should be rather simple. It should offer valued experience and talent for a reasonable price. If either the talent or cost is not reasonable, then the contract should be re-evaluated.
Labels and Tags
Accountability (66) Adequate documentation (4) ADR in procurement (3) Allocation of risks (5) Best interest of government (11) Best practices (19) Best value (14) Bidder prejudice (9) Blanket purchase agreement (1) Bridge contract (2) Bundling (6) Cancellation and rejection (2) Centralized procurement structure (12) Changes during bid process (13) Clarifications vs Discussions (1) Competence (9) Competition vs Efficiency (27) Competitive position (2) Compliance (32) Conflict of interest (28) Contract administration (24) Contract disputes (1) Contract extension or modification (8) Contract terms (2) Contract types (6) Contract vs solicitation dispute (1) Contractor responsibility (18) Conviction (3) Cooperative purchasing (3) Cost and pricing (13) Debarment (4) Determinations (8) Determining responsibility (32) Disclosure requirements (7) Discussions during solicitation (9) Disposal of surplus property (3) Effective enforcement requirement (34) Effective procurement management (3) Effective specifications (35) Emergency procurement (13) eProcurement (5) Equitable tolling (2) Evaluation of submissions (20) Fair and equitable treatment (13) Fair and reasonable value (23) Fiscal effect of procurement (13) Good governance (8) Governmental functions (26) Guam (14) Guam procurement law (12) Improper influence (11) Incumbency (12) Integrity of system (29) Interested party (7) Jurisdiction (1) Justification (1) Life-cycle cost (1) Limits of government contracting (4) Lore vs Law (4) market research (6) Materiality (3) Methods of source selection (28) Mistakes (3) Models of Procurement (1) Needs assessment (10) No harm no foul? (8) Other procurement links (14) Outsourcing (31) Past performance (10) Planning policy (33) Politics of procurement (46) PPPs (6) Prequalification (1) Principle of competition (87) Principles of procurement (20) Private vs public contract (15) Procurement authority (5) Procurement controversies series (75) Procurement ethics (17) Procurement fraud (27) Procurement lifecycle (9) Procurement philosophy (15) Procurement procedures (29) Procurement reform (56) Procurement theory (11) Procurement workforce (2) Procurment philosophy (6) Professionalism (17) Protest - formality (1) Protest - timing (10) Protests - general (35) Purposes and policies of procurement (8) Recusal (1) Remedies (16) Requirement for new procurement (4) Resolution of protests (3) Responsiveness (11) Restrictive specifications (3) Review procedures (12) Scope of contract (16) Settlement (2) Social preference provisions (59) Sole source (45) Sovereign immunity (2) Staffing (7) Standard commercial products (1) Standards of review (2) Standing (5) Stays and injunctions (6) Structure of procurement (1) Substantiation (9) Surety (1) Suspension (6) The procurement record (1) The role of price (8) The subject matter of procurement (22) Trade agreements vs procurement (1) Training (32) Transparency (59) Uniformity (5) Unsolicited proposals (2)
Thursday, July 10, 2014
Why hire mediocrity when you can contract for it?
The government contractor 'scam?' (Note: This is one of a series of guest columns written by Federal Report readers on the Federal News Radio website. I have taken editorial liberties, as usual, so you should read the source.)