Labels and Tags

Accountability (69) Adequate documentation (6) ADR in procurement (3) Allocation of risks (5) Best interest of government (11) Best practices (19) Best value (15) Bidder prejudice (11) 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 (29) Competitive position (2) Compliance (33) Conflict of interest (31) Contract administration (25) Contract disputes (1) Contract extension or modification (8) Contract terms (2) Contract types (6) Contract vs solicitation dispute (2) Contractor responsibility (19) Conviction (3) Cooperative purchasing (3) Cost and pricing (13) Debarment (4) Determinations (8) Determining responsibility (34) Disclosure requirements (7) Discussions during solicitation (9) Disposal of surplus property (3) Effective enforcement requirement (35) Effective procurement management (3) Effective specifications (36) Emergency procurement (14) eProcurement (5) Equitable tolling (2) Evaluation of submissions (22) Fair and equitable treatment (14) Fair and reasonable value (23) Fiscal effect of procurement (14) Frivolous protest (1) 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 (5) Lore vs Law (4) market research (7) Materiality (3) Methods of source selection (32) Mistakes (4) Models of Procurement (1) Needs assessment (11) No harm no foul? (8) Other procurement links (14) Outsourcing (33) Past performance (12) Planning policy (33) Politics of procurement (48) PPPs (6) Prequalification (1) Principle of competition (93) Principles of procurement (24) Private vs public contract (15) Procurement authority (5) Procurement controversies series (78) Procurement ethics (19) Procurement fraud (27) Procurement lifecycle (9) Procurement philosophy (16) Procurement procedures (30) Procurement reform (63) Procurement theory (11) Procurement workforce (2) Procurment philosophy (6) Professionalism (17) Protest - formality (2) Protest - timing (12) Protests - general (37) Purposes and policies of procurement (10) Recusal (1) Remedies (16) Requirement for new procurement (4) Resolution of protests (4) Responsiveness (13) Restrictive specifications (5) Review procedures (12) Scope of contract (16) Settlement (2) Social preference provisions (59) Sole source (47) Sovereign immunity (2) Staffing (7) Standard commercial products (2) Standards of review (2) Standing (6) Stays and injunctions (6) Structure of procurement (1) Substantiation (9) Surety (1) Suspension (6) The procurement record (1) The role of price (10) The subject matter of procurement (22) Trade agreements vs procurement (1) Training (32) Transparency (60) Uniformity (6) Unsolicited proposals (2)

Tuesday, March 26, 2013

Eureka! IT discovers competition!

There is essential information in this article that you will only get by reading the source at the link.

Feds Stoke IT Vendor Competition
the idea of promoting increased competition among IT vendors serving the federal market has resurfaced as a cost-cutting tool.

The reasons for the lack of diversification range from technical requirements to sheer inertia. MeriTalk reported that 65 percent of respondents said they specify a manufacturer to ensure compatibility with existing infrastructure, 17 percent contend it's what management wants, 11 percent said it saves time, and seven percent said "it's just what we always do."

In a recent survey of federal IT professionals, almost half believe that adding a competitor to IT infrastructure projects drives down acquisition costs. According to MeriTalk, an online community for both government and private sector IT professionals, results of the survey it conducted indicated that federal agencies could save 20 percent of their annual budgets by adding a competitor.

That equals about $15.8 billion per year, government-wide. Also, nearly half of the agencies that use multiple IT vendors contend that supplier diversification increases network performance.

Federal agencies still fall short of having adequate supplier diversification when it comes to IT infrastructure, according to the MeriTalk survey, which was conducted in January.

Federal law requires agencies to conduct "fair and open" competition in procurement. While the law does provide exceptions when certain circumstances come into play, such as technical requirements, obtaining such exceptions is not routine.

"The government has a substantial burden to demonstrate why the normal competitive requirements should be waived," Alan Chvotkin, vice president and counsel at the Professional Services Council, told the E-Commerce Times.

Despite the law, and the acknowledged advantages of vendor diversification, MeriTalk reported that 76 percent of survey respondents said their agency's IT infrastructure procurements specify a vendor at least some of the time. 77 percent reported that their agency's IT infrastructure acquisitions are contracted directly with suppliers, rather than with a reseller or integrator, at least some of the time.

Nearly two-thirds of the 208 respondents reported that they only have one or two vendors in several key areas: network operations, client operating systems, and data center operating systems. Supplier diversity for server and storage hardware is only slightly better, the survey showed.

"It is time to redesign the critical network infrastructure to accommodate current and future network bandwidth and security needs," Robbins said. "There is a tipping point where maintaining the old infrastructure becomes substantially more expensive than acquiring new. While it depends on the agency, the average refresh cycle is estimated at four to seven years for basic infrastructure lease or purchase."

Recent research from Gartner showed that adding a second vendor to an enterprise network infrastructure would reduce capital expenditures by at least 30 percent, while only minimally increasing operating expenditures.

The issue is important given the more rapid pace of change and improvement associated with IT infrastructure vs. highways and roads, which are replaced or upgraded perhaps every 20 years or even longer. "

About 70 percent of every IT dollar spent by the federal government goes to supporting legacy systems and infrastructure, according to the General Accounting Office. "The IT network infrastructure in the federal government was designed decades ago and has evolved over the last 20 years -- increasing complexity and driving up support costs along the way," said Robbins. "Agencies typically have been very slow to modernize their networks and this is costing them millions of dollars each year."

"It's a little tricky to define exactly what constitutes 'vendor lock-in.' It could come from agency preference, the way a contract is written, or what a particular vendor is offering. Sometimes agencies accept 'proprietary' services which reduce options," said Chvotkin.

That perception was borne out by MeriTalk, which reported that agencies consider 30 to 40 percent of their IT infrastructure locked up by current vendors in a reliance on standards, systems, or technologies that would be considered proprietary.

In a genuine pursuit of system integrity, agency IT specialists may close themselves off to potentially better pricing or better performance by writing specifications that are so technically detailed that they effectively eliminate competition.

In the acquisition process, agencies need "to be sure that the legal requirements for competition are followed," Gordon said, "and not allow 'wired' procurements, whether explicitly calling for a particular name brand, or disguised with the specifications written so as to favor one company."

Gordon was among several panelists who addressed the vendor competition issue at a February 27 hearing conducted by the House Committee on Oversight and Government Reform. The committee, headed by Rep. Darrell Issa (R-Calif.), is investigating federal IT contracting, and Issa is seeking feedback on his proposed bill to reform IT procurement.

During the hearing, Professional Services Council CEO Stan Soloway said that "competition is the single most effective means by which federal agencies can drive down their IT costs while also improving performance and efficiency."

No comments: