Shows & Panels
- The 2014 Big Picture on Cyber Security
- AFCEA Answers
- Ask the CIO
- Connected Government
- Consolidating Mission-critical Systems
- Constituent Servicing
- The Data Privacy Imperative: Safeguarding Sensitive Data
- Eliminating the Pitfalls: Steps to Virtualization in Government
- Federal Executive Forum
- Federal Tech Talk
- Government Cloud Brokerage: Who, What, When, Where, Why?
- Government Mobility
- The Intersection: Where Technology Meets Transformation
- Maximizing ROI Through Data Center Consolidation
- Mobile Device Management
- The Modern Federal Threat Landscape
- Moving to the Cloud. What's the best approach for me
- Navigating Tough Choices in Government Cloud Computing
- Satellite Communications: Acquiring SATCOM in Tight Times
- Transformative Technology: Desktop Virtualization in Government
- Understanding the Intersection of Customer Service and Security in the Cloud
Shows & Panels
Back to the Future: Bring back the Raines Rules for IT procurement?
Wednesday - 12/4/2013, 3:46am EST
The rollout of HealthCare.gov once again shined a bright light on systemic technology and procurement management problems, raising the ghosts of past reform efforts.
A vocal group of former and current federal officials is calling for the return to the Raines Rules.
"The Raines Rules are a framework that the OMB Director Frank Raines during the Clinton administration came up with shortly after the passage of the Clinger-Cohen act, which sort of memorialized good IT management practices, some high-level management questions that really needed to be asked at federal agencies that simply weren't being asked," said Paul Brubaker, the director of planning and performance management for the Defense Department's deputy chief management officer. "They were things like: Is this function a function that should remain in government, or is it something that should be outsourced? Should we do this in- house or should we look to a private sector source? Have we reengineered our business processes before we buy IT? These were all just basically good management practices that remain good management practices today. I think that there are some lessons that can be drawn if folks are willing to get in the Hot Tub Time Machine and go back to 1996 and dust them off and look at them. I think there are things that would obviate some of the challenges we see today."
Brubaker and Mark Forman, the CEO of Government Transaction Services and a former administrator of e-government and IT at the Office of Management and Budget, played key roles in writing the 1996 Clinger-Cohen Act, which currently governs federal IT management.
Failed oversight, poor implementation
Brubaker and Forman, who spoke at the Government IT Forum sponsored by 1105 Government Information Group in Washington Tuesday, are two of the more outspoken federal IT experts who believe the management processes put in place under Clinger-Cohen remain applicable today, but just aren't followed closely enough by agencies.
Forman said the failings of HealthCare.gov is yet another example of the lack of oversight by Congress and poor implementation by agencies of the Clinger-Cohen Act.
"Bringing back something like the Raines Rules is really basic IT management practices that I think a lot of us feel that ought to be applied," Forman said. "I think things got lost. A number of management practices and tools were put in place in the Clinton and Bush administrations that were eroded. People viewed this as they do with FISMA and Exhibit 300 business cases as a compliance process. It takes an awful lot of management acumen to get the folks to understand this is really about innovation and how government can do its work better."
And with the Senate likely to approve a version of the Federal IT Acquisition Reform Act as part of the National Defense Authorization Act for 2014 next week that mirrors the House amendment, the idea of legislating better IT management once again is up for debate.
Forman said he's concerned about several provisions of FITARA, including how it changes the role of the agency chief information officer and potentially creates the opposite intent of the Clinger-Cohen Act.
"It puts a lot of pressure on the departmental CIO to be a gatekeeper," he said. "FITARA has a heavy focus on the CIO as a gatekeeper, because like HealthCare.gov — and there is no question that's part of the energy behind it especially in the Senate — people are saying, 'Wait the government is not buying the technology right. There are these horror stories, we have to stop them.' The approach that I think we are discussing here is to say, 'Let's not focus on stopping them, the bad things, that's part of it. But there is a lot of value in that technology. But what do we have to do and what is the CIO's role to take advantage of this technology?'"
Ask the right questions
Forman added the role of the CIO needs to be better defined as it relates to the deputy secretary and other political appointees.
"Everyone really should be focused on taking advantage of the technology, but it requires that mixture of business transformation for success," he said. "It's almost always going to be risky, and you can't say we are not going to take the risk because then we are not solving the problems the taxpayers need solved."
Agencies continue to struggle with the idea of transforming business processes through IT.
Brubaker said Raines Rules helps agencies ask the right questions to focus on changing the business model instead of just applying technology.