EXECEXECUTIVE SUMMARY
To facilitate efforts to transform the Federal Government into one that is citizen-centered, resultsoriented, and market-based, the Office of Management and Budget (OMB) is developing the Federal Enterprise Architecture (FEA), a business-based framework for Government-wide improvement. The FEA is being constructed through a collection of interrelated "reference models" designed to facilitate cross-agency analysis and the identification of duplicative investments, gaps, and opportunities for collaboration within and across Federal Agencies.
The FEA Service Component Reference Model (SRM) is intended for use in discovering government-wide business and application Service Components in IT investments and assets. It is a component-based framework that provides - independent of business function - a leverageable foundation to support the reuse of applications, application capabilities, components, and business services.
The SRM was developed in cooperation with the Solution Architect's Working Group (SAWG), Federal Agencies, the Industry Advisory Council (IAC), and the Architecture and Infrastructure Committee (AIC). It identifies seven (7) Service Domains that provide a high-level view of the services and capabilities that support enterprise and organizational processes and applications.

SERVICE COMPONENT REFERENCE MODEL VERSION 1.0
Definition
The SRM is a component-based framework that can provide - independent of business function - a leverage-able foundation for reuse of applications, application capabilities, components, and business services.
Purpose
The SRM serves to identify and classify horizontal and vertical service components that support Federal agencies and their IT investments and assets. The model will aid in recommending service capabilities to support the reuse of business components and services across the Federal Government.
Specifically, the SRM was created to:
Provide a framework that identifies service components and their relationships to the
technology architecture of agencies across the Federal Government
Classify, categorize and recommend components for the reuse of business services and capabilities across the Federal Government
Define existing service components that may be leveraged outside agency boundaries
Align and leverage existing federal guidance and application/architecture recommendations
Support the 24 Presidential Priority E-Gov initiatives
Evolve based on new services and components as they are discovered across industry and federal markets

DEVELOPMENT OF THE SRM
In developing the SRM, the FEA-PMO leveraged previous Federal architecture efforts, such as the Federal Enterprise Architecture Framework (FEAF) guidance and Agency application reference models as starting points for designing the government-wide model. Using these architectures as a point of departure, the FEA-PMO performed extensive research on industry and government application capabilities to provide a capabilities frame of reference for agencies to use.
The information contained within these sources provides concise and thorough documentation of the many services and capabilities that industry and government applications and IT investments perform. The FEA-PMO used this information to normalize and categorize service capabilities and components that support, through IT assets, the business of the Federal Government. A hierarchical structure of Service Domains, Service Types and Service Components was crafted to convey a high level categorization of capabilities. Definitions were applied to the 7 service domains, the 29 service types and the 168 supporting components.

VALIDATION
The SRM was reviewed, validated and revised by the FEA-PMO and the SAWG, then released to agencies for feedback on January 29, 2003. Agency comments on the SRM were received through March 26, 2003. This feedback was analyzed by the FEA-PMO to further advance / evolve the model. A Comment Response Document (CRD) was generated and is available through the Agency CIOs.
A first pass was performed at aligning the SRM to the Agencies' major IT initiatives, as well as to the 24 Presidential Priority E-Gov initiatives. The alignment will be validated by agencies through the Federal Enterprise Architecture Management System (FEAMS), discussed further in Chapter 4 of this document.