Can Real Business Value Be Gained from Sarbanes-Oxley?

 
 
By Marcus Blosch  |  Posted 2004-05-01 Print this article Print
 
 
 
 
 
 
 

Judging from the results of this month's research (a joint CIO Insight/Gartner EXP survey of CIOs on the status of their Sarbanes-Oxley compliance programs), most CIOs feel optimistic about their efforts.

Judging from the results of this months research (a joint CIO Insight/Gartner EXP survey of CIOs on the status of their Sarbanes-Oxley compliance programs), most CIOs feel optimistic about their efforts. Their compliance mechanisms will be completed on time, and the necessary financial data will be rationalized—though it will take a lot of work. Becoming compliant will cause significant business disruption for a while, but things should calm down after the first year. And half of CIOs expect to reap a range of business benefits, including business process improvements, from their efforts.

Its good to be optimistic, and CIOs have some reason to be. More than 87 percent of respondents think their top executives take Sarbanes-Oxley compliance seriously, and, since executive sponsorship is the single most important success factor for any project, its not surprising that almost the same percentage of CIOs think their companies will be compliant by their deadline.

Most CIOs, however, think theyll get something more than bare compliance for their efforts, and we wonder if thats being a bit too optimistic. Almost half the CIOs who responded to the survey said their companies will do the minimum necessary to achieve compliance. Can those CIOs really get value—improvements in business processes—that they havent paid for?

CIOs cite problems with data structures, difficulties ensuring adequate security and business continuity, and variations in infrastructure between business units as three of the top four obstacles to compliance. These issues are closely related; they are the result of years of building information systems one-by-one in complex organizations, where data definitions, business rules and operating procedures are set department by department. A big company might have dozens of definitions built into its information systems for something as fundamental as a "product" or a "customer," and it might have hundreds of conflicting business rules for managing the data. For a company thats grown rapidly via mergers and acquisitions—as many have over the past decade—the problem is compounded.

Check out eWEEK.coms Enterprise Applications Center at http://enterpriseapps.eweek.com. Be sure to add our eWEEK.com enterprise applications news feed to your RSS newsreader or My Yahoo page:  
Next Page: Just another data warehouse project?


 
 
 
 
 
 
 
 
 
 
 

Submit a Comment

Loading Comments...
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Rocket Fuel