A New Strategic Direction for the Federal Enterprise Architecture Community - DRAFTThe Federal Enterprise Architecture (EA) community is at a crossroad regarding the way that architects individually and collectively contribute to Administration and Agency initiatives. This summary briefing describes a change in direction for the EA community to include purpose, goals, methods, and actions.Background: The Federal EA community consists of enterprise architects, domain-specific architects (e.g., business, data, systems, networks, and security), solution architects, and EA program staff in federal agencies. This community has existed since the Clinger Cohen Act of 1996 required agencies to develop and maintain IT architectures and the eGovernment Act of 2002 required OMB to oversee the establishment of enterprise architectures and defined related roles for the Federal CIO Council, which currently sponsors the Architecture and Infrastructure Committee (AIC). Other notable events include the release of the Federal Enterprise Architecture Framework in 1999, publication of the “Practical Guide to Federal Enterprise Architecture” in 2001, updates to OMB Circular A-130 on the “Management of Federal IT Resources” in 2001, the 2002-2005 release of the Federal EA Reference Models, the 2007 release of the Consolidated Reference Model, and the 2008 release of the Federal Segment Architecture Methodology. For nearly a decade, EA programs, methods, and architectures have been established, however, in a number of cases current approaches do not deliver sufficient tangible value in improving agency mission performance or in supporting Administration initiatives. Reasons cited include an over-focus on technology, long delivery timeframes, high costs, and a lack of executive buy-in. As a result, while there is still a significant amount of agency-level architecture activity occurring, the resulting work can be either under-utilized or under-valued. Bottom Line - Results: The Federal EA community’s recognition of the need to change and the actions described in this strategic summary will provide for revitalization and the meaningful engagement that is the bottom line desired outcome. The community does provide some value at present, but is not near its potential for helping the federal government to meet its ongoing need for new or better services with limited resources. Helping the Administration and Agencies to solve problems and improve mission performance is well within the capability of the Federal EA community and will continue to be the unifying goal for future activities.Federal Enterprise Architecture Community of PracticeFEACoP_7d4da8bc-f3fa-11df-ad05-04747a64ea2aCommunity Governance: The primary leadership and oversight elements for the Federal EA community are: (1) the Federal CIO at OMB; (2) the Federal Chief Architect at OMB; (3) the FEA Program Management Office at OMB, and (4) the Federal CIO Council’s Architecture and Infrastructure Committee and its subcommittees (currently Governance, Services, Data Architecture, Emerging Technologies, and Technology Infrastructure).Federal CIO at OMBFederal Chief Architect at OMBFEA Program Management Office at OMBFederal CIO Council’s Architecture and Infrastructure CommitteeFederal CIO Council’s Architecture and Infrastructure Committee and its subcommittees (currently Governance, Services, Data Architecture, Emerging Technologies, and Technology Infrastructure).Chief Architect’s ForumHolds meetings and participates in AIC activities.Other Government and Industry GroupsOther government and industry groups such as the Industry Advisory Council, the National Association of State CIOs, Architecture Plus, TechAmerica, and the Society for Information Management’s EA Working Group participate in community activities. Industry and government sponsored conferences, seminars, and workshops on EA and related topics provide additional forums for collaboration.Industry Advisory CouncilNational Association of State CIOsArchitecture PlusTechAmericaSociety for Information Management’s EA Working GroupTo be a trusted, knowledgeable resource that helps to accomplish mission goals, drive change, and optimize resources through proven enterprise architecture methods._7d4dacea-f3fa-11df-ad05-04747a64ea2aFederal enterprise architects provide leading-edge analysis and design services that align strategic priorities with mission capabilities and technology solutions._7d4dae02-f3fa-11df-ad05-04747a64ea2aCollaboration, Engagement, and ResultsRevitalize the community through collaboration, engagement, and results tracking._7d4daef2-f3fa-11df-ad05-04747a64ea2a1_7d4dafd8-f3fa-11df-ad05-04747a64ea2aLeadership SupportGain leadership support for the ongoing participation of architects in key strategic initiatives._7d4db0c8-f3fa-11df-ad05-04747a64ea2a2Agency LeadersFederal Enterprise Architects_7d4db1ae-f3fa-11df-ad05-04747a64ea2aDiversity of ViewsEnsure that the full diversity of views within the community are always heard and considered._7d4db28a-f3fa-11df-ad05-04747a64ea2a3_7d4db370-f3fa-11df-ad05-04747a64ea2aMethodsOverhaul methods for federal architecture to be more agile, timely, and efficient._7d4db460-f3fa-11df-ad05-04747a64ea2a4_7d4db546-f3fa-11df-ad05-04747a64ea2aLaw and PoliciesUpdate law/policy to reflect new priorities, methods, and desired outcomes._7d4db640-f3fa-11df-ad05-04747a64ea2a5_7d4db7b2-f3fa-11df-ad05-04747a64ea2aCareer Path and TrainingDevelop a career path and training standards for federal enterprise architects._7d4db8b6-f3fa-11df-ad05-04747a64ea2a6Federal Enterprise Architects_7d4dba1e-f3fa-11df-ad05-04747a64ea2aNear-Term Actions[Take] Near-Term Actions (FY 2011)_7d4dbbfe-f3fa-11df-ad05-04747a64ea2a7Strategic InitiativesIdentify where and how the EA community can add value in key strategic initiatives._7d4dbd0c-f3fa-11df-ad05-04747a64ea2a7.1Agility, Methods, and MetricsIdentify agency initiatives that use agile development and identify EA methods and metrics._7d4dbe38-f3fa-11df-ad05-04747a64ea2a7.2High-Level DocumentDevelop a high-level document that promotes standardized, agile architecture methods._7d4dbf6e-f3fa-11df-ad05-04747a64ea2a7.3Online Content and ResourcesReview the online content and resources that are currently available to the EA community._7d4dc090-f3fa-11df-ad05-04747a64ea2a7.4Online CommunityEstablish an online community collaboration and knowledge management environment._7d4dc1b2-f3fa-11df-ad05-04747a64ea2a7.5TechStat, IT Dashboard, and A-11 Budget ProcessIntegrate EA elements into the TechStat process, IT Dashboard, and updated Exhibit 300/53._7d4dc2de-f3fa-11df-ad05-04747a64ea2a7.6EA Reporting and MetricsIdentify what type of agency-level EA reporting and metrics should be required by OMB._7d4dc414-f3fa-11df-ad05-04747a64ea2a7.7Core Architecture ModelsIdentify a few “core” architecture models that every program/system must have._7d4dc7b6-f3fa-11df-ad05-04747a64ea2a7.8Long-Term Actions[Pursue] Long-Term Actions (FY 2012-2014)_7d4dc93c-f3fa-11df-ad05-04747a64ea2a8Architecture MethodsDevelop new architecture methods for sector-wide and government-wide initiatives._7d4dca90-f3fa-11df-ad05-04747a64ea2a8.1Law and PolicyUpdate EA-related law and policy (e.g., Clinger-Cohen, eGov Act, A-130, and the FEA)._7d4dcbda-f3fa-11df-ad05-04747a64ea2a8.2Governance ProcessesIdentify how to better integrate EA into business and technology governance processes._7d4dcd38-f3fa-11df-ad05-04747a64ea2a8.3Training and CertificationIdentify standards and core knowledge areas for the training and certification of architects._7d4dce8c-f3fa-11df-ad05-04747a64ea2a8.4Security and PrivacyDevelop methods to better integrate security and privacy into EA approaches._7d4dcff4-f3fa-11df-ad05-04747a64ea2a8.5Audit MethodologyDevelop methods to audit agency EA program maturity and effectiveness._7d4dd170-f3fa-11df-ad05-04747a64ea2a8.6Interoperable COTS ToolsPromote commercial architecture tools that are interoperable and can share models/data._7d4dd2d8-f3fa-11df-ad05-04747a64ea2a8.72010-11-17http://xml.fido.gov/stratml/carmel/iso/FEACoP.xmlOwenAmburOwen.Ambur@verizon.net