by clicking on the page. A slider will appear, allowing you to adjust your zoom level. Return to the original size by clicking on the page again.
the page around when zoomed in by dragging it.
the zoom using the slider on the top right.
by clicking on the zoomed-in page.
by entering text in the search field and click on "In This Issue" or "All Issues" to search the current issue or the archive of back issues respectively.
by clicking on thumbnails to select pages, and then press the print button.
this publication and page.
displays a table of sections with thumbnails and descriptions.
displays thumbnails of every page in the issue. Click on a page to jump.
allows you to browse through every available issue.
FCW : May 30, 2014
Commentary | ALAN P. BALUTIS Years ago, one of the major indus- try analyst rms spoke about the evolution of the CIO role at an organization and described that evolution in four phases. First came the CIO as the head of information resources manage- ment (IRM), where he or she was responsible for the computer center and backroom IT operations. The second was the CIO as a direct report to the chief nancial of cer because it was the latter who would rst recognize the potential of IT to reduce staf ng and save money. Third was the CIO as a peer to the CFO --- and to other manage- ment and administrative CXOs --- because senior managers saw the value of IT to the enterprise. And, nally, in the fourth and last stage, the CIO was the executive guiding organizational transforma- tion because the CEO saw how technology might change the way the rm or the agency did business. In 2008 and 2009, the Obama admin- istration spoke about that transfor- mative power --- how technology might change the way the govern- ment and the country delivered transportation, education, health care and so on. When I left public service several years ago, the government seemed to be solidly rooted in the third stage. CIOs at Commerce, Treasury, Transportation, Environmental Protection Agency, Social Security Administration and other agencies had emerged from reporting to the CFO or the assistant secretary for management and were direct reports to the secretary or deputy secretary. Under the leadership of rst Mark Forman and then Karen Evans, the Of ce of Management and Budget and the CIO Council were driving a series of initiatives (such as the Quicksilver project and e-government portfolio) that were intended to change not only the way government conducted its internal business (e.g., payroll, per- sonnel, procurement, etc.), but also the way it delivered services to citi- zens, the business community, and to state and local governments and the educational community. The beachfront had been secured, and the breakthrough was imminent. So what the heck happened? At an April event sponsored by AFFIRM (how ironic, the Asso- ciation for Federal Information Resources Management), a panel of federal IT veterans came together to discuss the role of the CIO --- 18 years after the passage of the Clinger-Cohen Act, which created the CIO position across govern- ment. One of the panel members took issue with the House-passed Federal IT Acquisition Reform Act, which would give department/ agency-level CIOs clear authority over all IT budgets and spending. He noted a distinction between "commodity IT" --- such as email, data centers and cloud comput- ing --- and "mission IT," where the responsibility, he stated, rested squarely with a component agency. So let me understand this: Say I was the CIO at a government agen- cy, perhaps the Commerce Depart- ment (which I was). So I should not worry about the habitually over-budget and behind-schedule weather observation satellite pro- gram? I shouldn t concern myself with the Census Bureau s plans for the 2020 decennial census, the larg- est government mobilization short of war? I shouldn t concern myself with trade or export systems, the real heart of the Commerce sec- retary s focus? Instead of dealing with the multi-year, billion-dollar enterprise systems that draw inter- est and attention from Congress and the White House, I should focus on email, data centers and maybe the secretary s problems with his BlackBerry? If that is the case, I should also forsake my title and mandate as the agency CIO. And I should be happy to be the director of IRM. What progress we have made in the decade I ve been gone! ■ Does anyone want to be a CIO? Focusing too much on "commodity IT" is an abdication of the CIO's mission --- and Clinger-Cohen's vision for the role The CIO should be dealing with the multi- year, billion-dollar enterprise systems that draw attention from Congress and the White House. ALAN P. BALUTIS is senior director and distinguished fellow at Cisco Systems. 12 May 30, 2014 FCW.COM
May 15, 2014
June 30, 2014