JRMS Submission Team

Records Management Services Background


Working since January 2005, an Interagency Project Team (IPT) comprised of stakeholders in records management and enterprise architecture from 18 Federal agencies and the National Archives and Records Administration (NARA), facilitated by members of the NARA Records Management Service Components Program Office produced a document capturing the functional requirements for seven essential Records Management Services that can be supported in an electronic environment.

The resulting document is:
"Functional Requirements, Attributes, and Unified Modeling Language Class Diagrams for Records, Management Services, September 7, 2006"

and can be found at:
http://doc.omg.org/gov/2006-09-13


Excerpts from the September 7, 2006 Requirements Document
(emphasis added)

Click for Program Site

On September 7, 2006, an Interagency Project Team (IPT) comprised of stakeholders in records management and enterprise architecture from 18 Federal agencies and the National Archives and Records Administration (NARA), facilitated by members of the NARA Records Management Service Components Program Office, met and reviewed proposed updates to the report “Functional Requirements and Attributes for Records Management Services, December 7, 2005.” The IPT approved the update of the December 7, 2005, report unanimously.

The IPT authoring this updated report represents a community of interest in the field of records management as envisioned in the Federal Enterprise Architecture (FEA). The IPT approves this report as a set of records management service (RMS) functional requirements, attributes, and Unified Modeling Language (UML) class diagrams ready for acquisition and development purposes, and for submission to the FEA's component repository, CORE.gov. The RMS adds value to previous work such as the Records Management Profile of the FEA. It is envisioned that IPT members and other agencies will use this report to help them improve their records management capabilities through the acquisition and development of systems as they evolve theiragency enterprise architectures.

During the period of December 2005 through August 2006, the Records Management Service Components Program Office received comments and suggestions from industry, academia, and government. These were collected, documented, and presented to the Interagency Project Team on September 7, 2006, for their consideration in producing an updated report for use in their RMS acquisition and development activities.

The IPT identified seven records management activities they believe can be supported by services within an electronic environment, including the services-oriented architecture defined in the FEA. The seven records management services are: Record Capture, Provenance, Category, Authenticity, Case File, Disposition, and Reference. These are documented in the report “Functional Requirements, Attributes, and Unified Modeling Language Class Diagrams for Records Management Services, September 7, 2006.”

 

Interagency Project Team
January 2005 – September 2006

  • Department of Agriculture

  • Department of the Treasury

  • Department of Commerce

  • Department of Transportation

  • Department of Defense

  • Department of Veterans Affairs

  • Department of Energy

  • Environmental Protection Agency

  • Department of Health and Human Services

  • General Services Administration

  • Department of Homeland Security

  • Housing and Urban Development

  • Department of Justice

  • National Aeronautics & Space Administration

  • Department of Labor

  • National Archives and Records Administration

  • Department of State

  • Social Security Administration

  • Department of the Interior

IPT members were named by their Chief Information Officers (CIO), E-Government program managers, and the Deputy Archivist of the United States as qualified to speak and vote for their agencies on session objectives, requirements approval, and future activities. As a community of interest, members agreed upon a shared vocabulary, grounded in statute and regulation, in order to support the exchange of information in pursuit of common goals, interests, and business objectives in the domain of records management.