We are requesting comments on two draft documents as part of our Federal Electronic Records Modernization Initiative (FERMI). The documents are the Electronic Records Management Federal Integrated Business Framework (ERM-FIBF) (Excel spreadsheet) and the Use Cases for Electronic Messages (Word document). Through FERMI, we have been working to improve the way agencies acquire ERM services and solutions. These documents serve as tools agencies can use when procuring services or solutions to manage electronic messages. They can be used by agencies to demonstrate how vendors perform the described requirements and workflows.
We welcome participation in the development of the ERM-FIBF and the Use Cases. As we would like to hear feedback from a variety of stakeholders, please share widely. You can comment here or fill out our feedback form (Excel spreadsheet) and email to PRMD@nara.gov with any questions or comments for consideration by February 23, 2018. We will review all the comments we receive.
We anticipate releasing the final version of the Use Cases for Electronic Messages in Spring 2018.
We developed the ERM-FIBF according to standards set out in the Federal Integrated Business Framework (FIBF) developed by GSA’s Unified Shared Services Management (USSM) office. The FIBF serves as a model to help the Federal government better coordinate and document common business needs, improve processes and performance, and drive economies of scale. With the development of the ERM-FIBF, NARA hopes to ensure records management requirements conform to the FIBF and are addressed in all Federal Service Areas.
This Use Cases for Electronic Messages document is based on the ERM-FIBF. The Use Cases document, which also includes visual workflows, is written from a high-level perspective and is intended to cover all types of electronic messages. We intend for agencies to use the use cases to demonstrate how vendors and service providers meet the requirements for managing electronic messages. The scenarios reflect an ideal flow of events and do not have to be accomplished in the exact way they are outlined in the Use Cases. The goal is to meet the requirements.
The date on the Use Cases is 2017, not 2018.