Feds need to get it together with enterprise architecture

Tools

Federal agencies are required to take an enterprise architecture approach to IT, combining strategic planning, business requirements and technology.

But these plans need to be better formalized and shared in order to facilitate shared services across agencies, said Federal Chief Enterprise Architect Scott Bernard, speaking at a conference in D.C. last week.

In fact, Bernard went on to note that the use of competing architectures perpetuates the type of silos that currently exist. The use of multiple email, accounting and help desk systems, for example, indicates that shared services--and the resulting efficiency--are not a priority for government agencies.

Bernard cited a number of government initiatives that would benefit from sound enterprise architecture: the Federal Data Center Consolidation Initiative, the White House's digital strategy and the Office of Management and Budget's PortfolioStat review process.

For more:
- read FCW's account of Bernard's talk
- see the 2012 Common Approach to Federal Enterprise Architecture issued by the Executive Office (.pdf)

More on enterprise architecture:
Rapid business model change strains enterprise architectures
Bottom-up change hits enterprise networks
SOA lessons from Twitter, Netflix