<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="stratml.xsl"?>
<StrategicPlan><id>http://xml.gov/stratml/drybridge/FEARMP.xml</id><Name>Federal Enterprise Architecture Records Management Profile Version 1.1</Name><Description>The RM Profile is a framework that overlays, or cross-cuts, the inter-related FEA reference
models: the Business Reference Model (BRM), Service Component Reference Model (SRM),
Technical Reference Model (TRM), Data Reference Model (DRM), and Performance Reference
Model (PRM). The RM Profile provides an overview of the FEA and explains how the reference
models provide a context for applying effective records management practices. Additionally, the
RM Profile includes a description of how each reference model currently addresses records
management and how agencies can use the various records management resources in the RM
Profile to improve their records management programs.</Description><OtherInformation>Establishing a Records Management (RM) Profile in the Federal Enterprise Architecture (FEA)  provides the framework for embedding common and consistent records management procedures and practices into agency business processes.  Currently, the RM Profile is a high-level concept.   As the FEA and concepts associated with each of the reference models mature, the RM Profile  will evolve to reflect emerging records management standards, technologies, and guidance.</OtherInformation><StrategicPlanCore><Organization><Name>National Archives and Records Administration</Name><Acronym>NARA</Acronym><Identifier>_09cbb3f2-ff4e-11df-8656-ec3c7a64ea2a</Identifier><Description></Description><Stakeholder><Name>ERPWG</Name><Description>Federal Agency Representatives of the Electronic Records Policy Working Group - Government Partner</Description></Stakeholder><Stakeholder><Name>FRC</Name><Description>Federal Records Council - Government Partner</Description></Stakeholder><Stakeholder><Name>Booz Allen Hamilton Inc.</Name><Description>Industry Partner</Description></Stakeholder><Stakeholder><Name>SRA International, Inc.</Name><Description>Industry Partner
</Description></Stakeholder><Stakeholder><Name>Records Management Officers</Name><Description>While agency RMOs may be familiar with the  specific records management requirements affecting their agency&#8217;s business, the RM Profile  can add value to their understanding by describing these requirements in the context of the  FEA.  Knowledge of the FEA reference models will better prepare agency RMOs to speak to  agency IT staff about integrating records management requirements into agency business  processes.</Description></Stakeholder></Organization><Organization><Name>Office of Management and Budget</Name><Acronym>OMB</Acronym><Identifier>_09cc8e4e-ff4e-11df-8656-ec3c7a64ea2a</Identifier><Description></Description><Stakeholder><Name>Program/Project Managers</Name><Description>Agency program and project managers are concerned with both  strategic and tactical issues affecting the mission of the agency.  From Line of Business  managers to content owners, the RM Profile is useful as a model that guides decision-making  to ensure that risks are mitigated, appropriate controls are in place, and performance  measures are monitored.</Description></Stakeholder><Stakeholder><Name>General Counsels</Name><Description>Agency GC offices are concerned with the legal ramifications of  implementing policies, procedures, or technologies.  The RM Profile can advise agency GC  offices by providing a framework for describing how records management authorities are tied  to agency business processes and enterprise architectures.</Description></Stakeholder></Organization><Organization><Name>Architecture and Infrastructure Committee</Name><Acronym>AIC</Acronym><Identifier>_09cc8f2a-ff4e-11df-8656-ec3c7a64ea2a</Identifier><Description>Federal Chief Information Officers Council</Description><Stakeholder><Name>CAF</Name><Description>Chief Architects Forum - Government Partner</Description></Stakeholder><Stakeholder><Name>NASCIO</Name><Description>National Association of State CIOs - Government Partner</Description></Stakeholder><Stakeholder><Name>IAC</Name><Description>Industry Advisory Council - Industry Partner</Description></Stakeholder><Stakeholder><Name>Chief Information Officers</Name><Description>Agency CIOs evaluate the impact of applying  management, operational, and technical controls and present options and/or recommendations resulting in appropriate solutions.  The RM Profile brings together records  management and IT issues to inform decision-making.</Description></Stakeholder><Stakeholder><Name>Enterprise Architects</Name><Description>The Agency Enterprise Architect supports the acquisition, use, and  management of an agency&#8217;s IT capabilities from varying perspectives (business, data,  applications, security, etc.), including records management services.  Enterprise Architects  ensure that records management is integrated into the Enterprise Architecture and into all  phases of IT solution development.  The RM Profile can help Enterprise Architects who are  familiar with the FEA achieve this goal.</Description></Stakeholder></Organization><Vision><Description>NARA, OMB, and the Federal CIO Council&#8217;s AIC envision the RM Profile as a framework to  ensure that agencies incorporate statutory records management requirements and sound records  management principles seamlessly into agency work processes, enterprise architectures, and  information systems.  The RM Profile is a cross-cutting guide that uses relevant FEA reference  model information (i.e., context and conditions) to help business process owners identify and  integrate records management requirements into all aspects of agency business operations. </Description><Identifier>_09cc9060-ff4e-11df-8656-ec3c7a64ea2a</Identifier></Vision><Mission><Description>To provide agency decision- makers with a framework for incorporating statutory records management requirements and sound records management principles seamlessly into agency work processes, enterprise architectures, and information systems</Description><Identifier>_c97d3ced-94bf-4bc7-ba39-daf9786662ca</Identifier></Mission><Value><Name></Name><Description></Description></Value><Goal><Name>Framework for Requirements</Name><Description>Use the FEA as the common Government-wide framework for identifying records management requirements.</Description><Identifier>_f1a7e9fa-f6b1-4bc5-a61c-a2f8fd7e90c0</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>By combining records management policies and procedures with the  foundation of the FEA reference models, the RM Profile promotes a standardized means of  implementing records management in agency enterprise architectures across the Government.   Every line of business in the FEA should incorporate records management requirements and  functionality.</OtherInformation><Objective><Name></Name><Description></Description><Identifier>_09cc9128-ff4e-11df-8656-ec3c7a64ea2a</Identifier><SequenceIndicator></SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation></OtherInformation></Objective></Goal><Goal><Name>Technologies and Business Processes</Name><Description>Identify records management issues and requirements and link them to their implementing technologies and business processes.</Description><Identifier>_0563f776-74c7-48fd-bab4-65d1c5117217</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>The RM Profile ensures that agencies  evaluate records management issues and requirements during agency planning processes.   Agencies should integrate these requirements into all areas of business operations, especially  before the implementation of systems and supporting processes.</OtherInformation><Objective><Name></Name><Description></Description><Identifier>_09cc91c8-ff4e-11df-8656-ec3c7a64ea2a</Identifier><SequenceIndicator></SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation></OtherInformation></Objective></Goal><Goal><Name>IT Governance Processes</Name><Description>Build records management requirements into agency information technology (IT) governance processes for capital planning, enterprise architecture, business process design, and the systems development life cycle.</Description><Identifier>_d26d0023-8a26-4ac1-816e-ab7fcba0e06b</Identifier><SequenceIndicator>3</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>For agency IT managers and enterprise architects in particular, the RM Profile is a  useful guide for building records management requirements into IT governance processes for  capital planning, enterprise architecture, business process design, and the systems development  life cycle.</OtherInformation><Objective><Name></Name><Description></Description><Identifier>_09cc925e-ff4e-11df-8656-ec3c7a64ea2a</Identifier><SequenceIndicator></SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation></OtherInformation></Objective></Goal><Goal><Name>Records Management Resources</Name><Description>Establish a concise and coherent body of records management resources that places this information in the proper context within the FEA.</Description><Identifier>_6aa0dc0b-5a09-45d1-b628-6e3e10b4bdb0</Identifier><SequenceIndicator>4</SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation>A key objective of the RM Profile is to bring together relevant records management resources (e.g., NARA, OMB, and GSA) as a  concise body of knowledge that will inform and guide agency decision-makers.  In this sense, it  is a communication tool.  Further, by placing these resources within the context of the FEA, they  become more meaningful and understandable to senior agency decision-makers that are familiar  with OMB&#8217;s FEA framework.</OtherInformation><Objective><Name></Name><Description></Description><Identifier>_09cc92f4-ff4e-11df-8656-ec3c7a64ea2a</Identifier><SequenceIndicator></SequenceIndicator><Stakeholder><Name></Name><Description></Description></Stakeholder><OtherInformation></OtherInformation></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate>2005-12-15</StartDate><EndDate></EndDate><PublicationDate>2010-12-03</PublicationDate><Source>http://www.archives.gov/records-mgmt/pdf/rm-profile.pdf</Source><Submitter><FirstName>Owen</FirstName><LastName>Ambur</LastName><PhoneNumber></PhoneNumber><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></StrategicPlan>