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, November 12, 2013

Shhhh... IT is a procurement problem child

A Few Places Where Government Tech Procurement Works
The botched start of is just the latest big federal tech system to fail at launch. Information technology research group Standish found that during the last decade, of the large-scale federal IT projects 94 percent have been similarly unsuccessful.

Critics say the real root of government website woes is procurement, or, government's process for buying technology. So we sought out a few places where IT procurement is actually working smoothly.

Philadelphia, like the federal government, had a hard time getting innovative businesses to compete for government tech contracts. "Startups, they may have great ideas and great technology but they're not necessarily built to make it through the procurement process. Those who make it through are those who have experience working through this cumbersome process that can take a lot of time," chief digital officer Mark Headd says.

That favors large, entrenched vendors who often turn in subpar services. As the system is now, it's just not easy for young companies to find or bid on government contracts. And because all governments — federal, state and local — fear wasting taxpayer dollars on bad results — they write layers of regulations and rules around contracting. That's a turnoff for many potential bidders.

But bidding's getting easier in the City of Brotherly Love. Philadelphia leaders decided to put technology at the heart of government, hiring Headd to team up with existing tech talent in the city, and simplify bidding for government projects. To "go where the developers are," Headd created an account for the city on GitHub, a transparent code repository, and posted its open data policy there. "It's good for us, because we're gonna get more bids, it's good for [the outside developers], because it's business they might not otherwise be aware of," Headd says.

"What we've done in Kansas City is to be a little more proactive," the city's head of procurement, Cedric Rowan says. "By being willing to look at the marketplace and willing to interject into our scopes the ability for providers to give some solutions that are maybe a little more than what we're asking for but at least give them the opportunity to be innovative in their solutions back to us."

At the federal level — the Consumer Financial Protection Bureau gets praise for its approach to tech. "We wanted to show how government could work," says Merici Vinton, who served as the agency's digital lead and oversaw the launch of the CFPB's first website, which included projects like a simple complaint submission system and a redesign of mortgage disclosure forms.

Here's what Kansas City, Philadelphia and the CFPB have in common: Encouragement and cover from the top of their departments and cities; openness in sharing requirements behind IT projects from the very beginning of the procurement process; and eagerness to have smart tech people inside their departments, and to bring them together with existing government teams.

"The website and your services that you're providing to the citizens are now your storefront. So those have to be in alignment across the agency," says Vinton.

Michael Slaby — who was one of the people who built President Obama's much-lauded 2008 and 2012 campaign technology says, "the idea that things are stacked against government — the way that we procure, the way we design projects — is all true, but it's all something we have to fix. We should make it simple for technology to empower citizens to get things from their government in a way that's seamless and easy."
You may feel as I do that this article is short on detail, implying more questions than giving answers. Read the comments to it at the link above.

No comments: