Management

Feds should formalize architecture, chief architect says

data abstract

Public or private sector, every agency and organization has an enterprise architecture, and the federal government's chief enterprise architect believes these strategic plans should be formalized to improve the government's ability to share services between agencies.

"Architecture is nothing if not applied," said Federal Chief Enterprise Architect Scott Bernard, speaking at a conference Oct. 29 in Washington.

Enterprise architecture has gained steam in federal agencies since a 2012 White House directive mandated agency heads to create agency-wide enterprise architectures that meld strategic drivers, business requirements and technology in hopes of reducing duplication and enhancing engagement between agencies and the public sector.

And its importance continues to grow, Bernard said.

Enterprise architecture, which Bernard defined simply as the combination of strategic, business and technology planning, plays a major role in several key agency-wide initiatives. PortfolioStat, the Federal Data Center Consolidation Initiative, the White House's digital strategy and cloud computing could all yield better results when run by agencies with sound enterprise architectures in place, he said.

And, unlike many processes in IT, Bernard said agencies should not operate with more than one enterprise architecture. This is one time, he said, when you don't want a backup.

"Centralized or decentralized, [agencies] should not be using competing architectures," Bernard said.

The government has room to improve in using enterprise architecture to promote shared services, with the first step simply accepting it as a priority, Bernard said.

It makes little sense for agencies to have multiple e-mail systems, IT help desks and different methodologies and systems to deliver accounting, travel or finance services. Yet those "low-hanging fruit" are still hanging in many agency trees.

"I think we can be more efficient with a few instances, but it requires agencies to be aware – they have to understand shared services is a priority and pursue it," Bernard said.

About the Author

Frank Konkel is a former staff writer for FCW.

The Fed 100

Read the profiles of all this year's winners.

Featured

  • Then-presidential candidate Donald Trump at a 2016 campaign event. Image: Shutterstock

    'Buy American' order puts procurement in the spotlight

    Some IT contractors are worried that the "buy American" executive order from President Trump could squeeze key innovators out of the market.

  • OMB chief Mick Mulvaney, shown here in as a member of Congress in 2013. (Photo credit Gage Skidmore/Flickr)

    White House taps old policies for new government makeover

    New guidance from OMB advises agencies to use shared services, GWACs and federal schedules for acquisition, and to leverage IT wherever possible in restructuring plans.

  • Shutterstock image (by Everett Historical): aerial of the Pentagon.

    What DOD's next CIO will have to deal with

    It could be months before the Defense Department has a new CIO, and he or she will face a host of organizational and operational challenges from Day One

  • USAF Gen. John Hyten

    General: Cyber Command needs new platform before NSA split

    U.S. Cyber Command should be elevated to a full combatant command as soon as possible, the head of Strategic Command told Congress, but it cannot be separated from the NSA until it has its own cyber platform.

  • Image from Shutterstock.

    DLA goes virtual

    The Defense Logistics Agency is in the midst of an ambitious campaign to eliminate its IT infrastructure and transition to using exclusively shared, hosted and virtual services.

  • Fed 100 logo

    The 2017 Federal 100

    The women and men who make up this year's Fed 100 are proof positive of what one person can make possibile in federal IT. Read on to learn more about each and every winner's accomplishments.

Reader comments

Wed, Oct 30, 2013 OccupyIT

Well if you can't say you're essential its hard to justify your job, right? Unfortunately, most enterprise architectures have little practical impact on the organization (besides unintended consequences) and are outward reporting requirements to another navel gazing comittee. They also are pretty much still wrestling with the most mundane back office functions which should have been resolved eons ago. Very few even consider the real Program level activity of the Agency that is what matters to constituents and taxpayers. Let's say you won't get your bonus if you're still trying to describe you email system or accounting as 'enterprise'. Call a GS-11 and ask them how the ridiculously expensive Enterprise Architecture Club has improved their lives and work. And, no, BYOD isn't it.

Please post your comments here. Comments are moderated, so they may not appear immediately after submitting. We will not post comments that we consider abusive or off-topic.

Please type the letters/numbers you see above

More from 1105 Public Sector Media Group