MAS - Peniel Solutions, LLC - 47QSMA19D08PC

PENIEL SOLUTIONS, LLC 47QSMA19D08PC PAGE

GENERAL SERVICES ADMINISTRATION

Federal Supply Service

Authorized Federal Supply Schedule Price List On-line access to contract ordering information, terms and conditions, up-to-date pricing, and the option to create an electronic delivery order are available through GSA

Advantage!®, a menu-driven database system. The INTERNET address GSA

Advantage!® is: GSAAdvantage.gov.

Multiple Award Schedule

FSC Group: Office Management; Information Technology

FSC Class: R616, R617, D399, J070, 7030

Contract Number: 47QSMA19D08PC

Period Covered by Contract: March 1, 2019 to February 28, 2029

Peniel Solutions, LLC

3473 Satellite BLVD STE 221 North Duluth, GA 30096

Corporate: (678)735-4800 Toll Free (866) 878-2490

Fax: (678) 735-4831 Email: jmcgriff@penielsolutions.com; ccolclough@penielsoutionscom www.penielsolutions.com www.TransAccessDM.com

Business size: Small, Service Disabled Veteran Owned, SBA Certified Small Disadvantaged Business

For more information on ordering from Federal Supply Schedules go to the GSA

Schedules page at GSA.gov.

Price list current as of Modification #PA-0027 effective 8/18/2025

Prices Shown Herein are Net (discount deducted) https://www.gsaelibrary.gsa.gov/ElibMain/contractorInfo.do?contractNumber=47QSMA19D08PC&contractorName=PENIEL+SOLUTIONS%2C+LLC&executeQuery=NO mailto:jmcgriff@penielsolutions.com http://www.penielsolutions.com/ http://www.transaccessdm.com/

CUSTOMER INFORMATION

1a. Table of awarded special item number(s) with appropriate cross-reference to item descriptions and awarded price(s).

Large Category Subcategory SIN SIN Title

Information Technology

IT Services 54151S Information Technology Professional

Services

Information Technology

IT Software 54151 Software Maintenance Services

Information Technology

IT Services 54151HACS Highly Adaptive Cybersecurity

Services

Information Technology

IT Software 511210 Software Licenses

Office Management Records

Management

493110RM

Physical Records Management Services

Office Management Records

Management

518210ERM

Electronics Records Management Solutions

Miscellaneous Complementary OLM Order Level Materials

1b. Identification of the lowest priced model number and lowest unit price for that model for each special item number awarded in the contract. This price is the Government price based on a unit of one, exclusive of any quantity/dollar volume, prompt payment, or any other concession affecting price. Those contracts that have unit prices based on the geographic location of the customer, should show the range of the lowest price, and cite the areas to which the prices apply. See Page 4

1c. If the Contractor is proposing hourly rates, a description of all corresponding commercial job titles, experience, functional responsibility and education for those types of employees or subcontractors who will perform services shall be provided. If hourly rates are not applicable, indicate “Not applicable” for this item. See Page 6

2. Maximum order for each SIN:

SIN

Maximum Order

Limit (MoL) 54151S $500,000.00

54151 $500,000.00

54151HACS $500,000.00

511210 $500,000.00

493110RM $1,000,000.00

518210ERM $1,000,000.00

OLM $250,000.00

3. Minimum order: $0.00

4. Geographic coverage (delivery area): 48 Contiguous States and Washington DC for SINs 493110RM and SIN 518210ERM; Domestic and Overseas for SIN 511210, 54151 and 54151S

5. Point(s) of production: Duluth GA and Washington DC

6. Discount from list prices or statement of net price: Net prices are included on this price list.

7. Quantity discounts: None

8. Prompt payment terms: Information for Ordering Offices: Prompt payment terms cannot be negotiated out of the contractual agreement in exchange for other concessions. Net

9. Foreign items: None

10a. Time of delivery: 30 Days ARO SIN 511210, 493110RM and 518210ERM; 10 Days ARO SIN 54151; As agreed upon by the customer Agency for SIN 54151S and

54151HACS

10b. Expedited delivery: Contact Vendor

10c. Overnight and 2-day delivery: Contact Vendor

10d. Urgent requirements: Contact Vendor

11. F.O.B. point(s): Destination

12a. Ordering address(es):

Peniel Solutions, LLC 3473 Satellite BLVD STE 221 North

Duluth, GA 30096 Corporate: (678)735-4800 Toll Free (866) 878-2490 Fax: (678) 735-4831

12b. Ordering procedures: For supplies and services, the ordering procedures, information on Blanket Purchase Agreements (BPA’s) are found in Federal Acquisition Regulation

(FAR) 8.405-3.

13. Payment address:

Peniel Solutions, LLC 3473 Satellite BLVD STE 221 North

Duluth, GA 30096 Corporate: (678)735-4800 Toll Free (866) 878-2490 Fax: (678) 735-4831

14. Warranty provision: Standard Commercial Warranty

15. Export packing charges: N/A

16. Terms and conditions of rental maintenance, and repair: N/A

17. Terms and conditions of installation: N/A

18a. Terms and conditions of repair parts: N/A

18b. Terms and conditions for any other services: N/A

19. List of service and distribution points: N/A

20. List of participating dealers: N/A

21. Preventative maintenance: N/A

22a. Special attributes such as environmental attributes: N/A

22b. Section 508 compliance: Yes

23. Unique Entity Identifier (UEI) number Data Universal Number System (DUNS) number:

929799901

24. Notification regarding registration in the System for Award Management (SAM) database. Registered

SIN 518210ERM Vendor Certification for Electronic Records Management

Solutions

Version 3.0 (As of MAS Refresh 18)

For the purposes of the MAS Solicitation, eight (8) specific elements of Electronic Records Management

(ERM) Services have been identified. These 8 elements are fully defined and the corresponding requirements are identified in NARA’s Universal Electronic Records Management Requirements spreadsheet attachment to the Solicitation. These requirements have been established and are administered by the National Archives and Records Administration (NARA). Vendors may provide any combination of the 8 elements of ERM solutions; however, vendors must certify that they are capable of meeting all standards associated with the elements they propose by completing this self-certification. Vendors must include a completed copy of this certification in their published GSA MAS Contract Price List to help illustrate their ERM capabilities to federal customer agencies.

Proposed Elements of Electronic Records Management Services:

By selecting the below Elements, you are self-certifying you meet NARA’s Universal ERM Requirements for that Element. Select all Elements that apply.

Element 1 - Office Management Applications

Element 2 - Electronic Messages

Element 3 - Social Media

Element 4 - Websites

Element 5 - Photographs (Born-Digital and Scanned Images)

Element 6 - Digital Audio and Video

Element 7 - Structured Data

Element 8 - Shared Drives

In the space below you must provide a brief summary description for each of the above Elements that you have checked off. The summary must include which ERM products/ services/ solutions — currently awarded under SIN 518210ERM of your MAS contract — are related to the respective Element. Example questions are provided for each Element to assist with your response. Those questions are based on NARA’s Universal

Electronic Records Management Requirements and reflect common questions from agencies. If you cannot provide a summary description for a given Element, or you do not currently offer products/services/solutions under SIN 518210ERM related to that Element, you cannot self-certify that Element on this form. Please use as much space as you need below, but be concise! Please respond as “Not applicable” for any Element you did not select above.

The specifics of your below responses are not part of the evaluation criteria for adding SIN 518210ERM. The intention of the below section is to assist agencies with market research and help agencies understand your offerings / capabilities as they relate to the above ERM Elements you have selected.

If you have questions about the above ERM Elements and the information on NARA’s Universal ERM

Requirements spreadsheet, please contact NARA’s Records Management Policy Team at rmpolicy@nara.gov.

Element 1 - Office Management Applications

Please provide a brief summary of your awarded offerings (products/services/solutions) under SIN 518210ERM that help agencies meet Element 1. Some example questions to consider are: Which office management applications does your service/solution manage (e.g. Microsoft 365, Google Workspace, etc.)? How do you associate Office Management documents with a records schedule? How do you apply metadata to Office Management documents?

[Response for Element 1 here — use as much space as you need. If you did not self-certify this Element in the above section, please put “Not Applicable.”]

TransAccess GCR is able to store any file format for storage, indexing and apply any relevant retention schedules. This includes documents generated by office management applications such as Microsoft 365

(Word, Excel, etc.) In addition to manual upload and storage, our application is able to automate and ingest files/documents generated from these office management solution platforms via our REST API. All files uploaded are associated with the selected office’s file plan to enforce departmental policies, naming conventions etc. Our system allows the customer to import all NARA-approved record schedules into the application. The uploaded and approved records schedules will be codified into a departmental file plan within the application, which consolidates guidance around information governance for easy reference. This makes records easy to store, retrieve, and dispose, as well as answering questions like how to name and file records, handle disposition and destruction, how to transfer records to NARA, and more. This process guarantees that records are accurately classified and managed in accordance with the department’s approved records schedules. This automated approach to records management allows record staff to quickly conduct compliance checks to verify that records are being managed according to their appropriate record schedule.

Our system captures and classifies metadata at ingestion, either automatically generating certain types metadata (like creation or modification date) to facilitate the user’s workflow or allowing metadata to inputting by the uploader. This allows organizations to create custom metadata fields as needed, and preserves metadata throughout the lifecycle, among other features such as searchability. This will support the

Capture and Metadata lifecycle phases by establishing authoritative records and (1) the description of the content of the record; (2) the structure of the record (form, format, and relationships between record components); (3) the business context in which the record was created; (4) relationships with other records and metadata; (5) identifiers and other information needed to retrieve the record; (6) the business actions and events involving the record throughout its existence.

Element 2 - Electronic Messages

Please provide a brief summary of your awarded offerings (products/services/solutions) under SIN 518210ERM that help agencies meet Element 2. Some example questions to consider are: Which electronic messages does your service/solution manage (e.g. SMS/MMS, iMessage, WhatsApp, social media messages, voicemail, etc.)? Are you able to capture SMS/MMS at the carrier-level? How do you apply metadata to electronic messages? Where are records stored (e.g. managed in the system in which they were created or in a dedicated recordkeeping system)?

[Response for Element 2 here — use as much space as you need. If you did not self-certify this Element in the

TransAccess GCR is able to store any file format for storage including SMS, iMessage and other messaging file formats; these files can then be indexed within our application and have any relevant retention schedules applied. Unless conversion is otherwise requested, these electronic messages will be stored in their native format within our TransAccess GCR database for archival and retrieval. Our system captures and classifies metadata at ingestion, either automatically generating certain types metadata (like creation or modification date) to facilitate the user’s workflow or allowing metadata to inputting by the uploader. This allows organizations to create custom metadata fields as needed, and preserves metadata throughout the lifecycle, among other features such as searchability. Electronic messages for retention and management can be ingested via manual upload or via our REST API from their originating application, further configuration may be required to ingest content from certain messaging applications due to privacy policies, proprietary restrictions etc. Our system allows the customer to import all NARA-approved record schedules into the application. The uploaded and approved records schedules will be codified into a departmental file plan within the application, which consolidates guidance around information governance for easy reference. This makes records easy to store, retrieve, and dispose, as well as answering questions like how to name and file records, handle disposition and destruction, how to transfer records to NARA, and more. This process guarantees that records are accurately classified and managed in accordance with the department’s approved records schedules. This automated approach to records management allows record staff to quickly conduct compliance checks to verify that records are being managed according to their appropriate record schedule.

Element 3 - Social Media

Please provide a brief summary of your awarded offerings (products/services/solutions) under SIN 518210ERM that help agencies meet Element 3. Some example questions to consider are: Which social media platforms does your solution/services capture and manage (e.g. Facebook, YouTube, Instagram, WordPress)? What technology is used to capture social media records? What frequency can your solution/services capture? How do you address changes in what social media platforms allow for capture?

[Response for Element 3 here — use as much space as you need. If you did not self-certify this Element in the

TransAccess GCR is able to store any file format for storage including content from social media such as

Twitter, we are capable of collecting content from all social media platforms that provide an API. These APIs allow the application to retrieve data such as posts, comments, messages, and user profiles. This content can then be indexed within our application and have any relevant retention schedules applied. Our system captures and classifies metadata at ingestion, either automatically generating certain types of metadata (like creation or modification date) to facilitate the user’s workflow or allowing metadata to inputting by the uploader. This allows organizations to create custom metadata fields as needed, and preserves metadata throughout the lifecycle, among other features such as searchability. Social media for retention and management can be ingested via our REST API from their originating application, further configuration may be required to ingest content from certain messaging applications due to privacy, proprietary restrictions etc.

Our data collection process allows us to perform specific searches based on keywords, hashtags, usernames, or other criteria specified by the customer. The retrieved data is then ingested into the TransAccess GCR

System. We can customize the frequency of data collection, and our team regularly monitors updates to the relevant platform’s content and privacy policies to adapt TransAccess GCR accordingly and explore alternative data sources (data scraping etc.) when permissible. Our system allows the customer to import all

NARA-approved record schedules into the application. The uploaded and approved records schedules will be codified into a departmental file plan within the application, which consolidates guidance around information governance for easy reference. This makes records easy to store, retrieve, and dispose, as well as answering questions like how to name and file records, handle disposition and destruction, how to transfer records to

NARA, and more. This process guarantees that records are accurately classified and managed in accordance with the department’s approved records schedules. This automated approach to records management allows record staff to quickly conduct compliance checks to verify that records are being managed according to their appropriate record schedule.

Questions for Element 4 - Websites

Please provide a brief summary of your awarded offerings (products/services/solutions) under SIN 518210ERM that help agencies meet Element 4. Some example questions to consider are: What technology do you use to crawl websites? Do you have the capability to capture internal and external sites? What formats do you use for web captures? Can you capture websites in NARA-acceptable formats? What quality assurance processes/tools do you offer?

TransAccess GCR is able to store any file format for storage including website content. It supports various formats for web captures, including HTML, PDF, and WARC (Web ARChive). We will utilize web crawling technology to capture websites, with the capability to capture both internal and external sites. We can integrate quality assurance processes and tools into the system, ensuring the accuracy, completeness, and integrity of captured web content through validation checks, checksum verification, and metadata validation.

TransAccess GCR will implement data validation and quality checks at not only the digitization level but also the application layer to ensure that all digital files uploaded or captured within the system meet the required digitized file format standards. This can include automated checks for file format, file size, file naming conventions, and other relevant parameters to ensure that all files are in the correct format. While our system accepts all file formats for storage and record indexing of metadata, certain business contexts may require a specific file format. The system can provide automated or manual file format conversion functionalities to convert digital files into the required file format standards. For example, we can automatically convert a

Word document to PDF or prompt the user to convert the file before it can be uploaded or stored within the system. Our application also provides a universal file formatting feature, which ensures our customers do not have to worry about new and emerging file formats. Incorporating guidance such as ISO 9005, we can make certain that electronic documents will maintain their original appearance consistently over time, without being affected by the tools used to generate, store, or present them. While PDF is currently dominant in the market, there are numerous other file formats in regular use, and new formats will continue to appear in the future. TransAccess GCR will ensure that our customers will not be impacted by new extensions created or updates to existing formats in the future through the provisioning of this feature.

Our system allows the customer to import all NARA-approved record schedules into the application. The uploaded and approved records schedules will be codified into a departmental file plan within the application, which consolidates guidance around information governance for easy reference. This makes records easy to store, retrieve, and dispose, as well as answering questions like how to name and file records, handle disposition and destruction, how to transfer records to NARA, and more. This process guarantees that records are accurately classified and managed in accordance with the department’s approved records schedules. This automated approach to records management allows record staff to quickly conduct compliance checks to verify that records are being managed according to their appropriate record schedule.

[Response for Element 4 here — use as much space as you need. If you did not self-certify this Element in the above section, please put “Not Applicable.”

Questions for Element 5 - Photographs (Born-Digital and Scanned Images)

Please provide a brief summary of your awarded offerings (products/services/solutions) under SIN 518210ERM that help agencies meet Element 5. Some example questions to consider are: How do you associate Photographs with a records schedule? How do you apply metadata for categorization and searchability to Photographs?

TransAccess GCR is able to store any file format for storage, indexing and apply any relevant retention schedules. This includes photographs (born-digital and scanned images) In addition to manual upload and storage, our application is able to automate and ingest files/documents generated from outside sources via our

REST API. All files uploaded are associated with the selected office’s file plan to enforce departmental policies, naming conventions etc. Our system allows the customer to import all NARA-approved record schedules into the application. The uploaded and approved records schedules will be codified into a departmental file plan within the application, which consolidates guidance around information governance for easy reference. This makes records easy to store, retrieve, and dispose, as well as answering questions like how to name and file records, handle disposition and destruction, how to transfer records to NARA, and more. This process guarantees that records are accurately classified and managed in accordance with the department’s approved records schedules. This automated approach to records management allows record staff to quickly conduct compliance checks to verify that records are being managed according to their appropriate record schedule. Our system captures and classifies metadata at ingestion, either automatically generating certain types metadata (like creation or modification date) to facilitate the user’s workflow or allowing metadata to inputting by the uploader. This allows organizations to create custom metadata fields as needed, and preserves metadata throughout the lifecycle, among other features such as searchability. This will support the Capture and Metadata lifecycle phases by establishing authoritative records and (1) the description of the content of the record; (2) the structure of the record (form, format, and relationships between record components); (3) the business context in which the record was created; (4) relationships with other records and metadata; (5) identifiers and other information needed to retrieve the record; (6) the business actions and events involving the record throughout its existence. When a file is uploaded to

TransAccess GCR, automated workflows for the purposes of quality, in addition to those related to records scheduling, will be initiated. A script will review the file during the upload process, first checking if the uploaded file is in a format that needs to be analyzed for resolution, such as JPEG or TIFF. If the file is determined to be an image, the script can extract the resolution metadata from the image file. The script can then compare the extracted resolution values against the predefined resolution requirements. If the image resolution does not meet the required criteria, the script can generate an error message indicating that the uploaded file does not meet the resolution requirements and prompt the user, indicating the reason for the failure and any necessary steps to rectify the issue, such as re-uploading a higher resolution image. The user will also be presented with an option to convert the TIFF file to PDF with full OCR (Optical Character

Recognition) or retain the TIFF formatting with OCR, with our built-in capabilities recognizing and adding text to the scanned document so it can then be indexed, searched, or annotated. This automated feature ensures that all textual documents uploaded to the system are indexed for content, and all appropriate metadata is captured and associated with each record with minimal manual intervention. Our solution is also optimized for low latency of document retrieval and viewing, [Response for Element 5 here — use as much space as you need. If you did not self-certify this Element in the

Questions for Element 6 - Digital Audio and Video

Please provide a brief summary of your awarded offerings (products/services/solutions) under SIN 518210ERM that help agencies meet Element 6. Some example questions to consider are: How do you associate Digital Audio and Video files with a records schedule? How do you apply metadata for categorization and searchability to Digital Audio and Video?

[Response for Element 6 here — use as much space as you need. If you did not self-certify this Element in the

TransAccess GCR is able to store any file format for storage, indexing and apply any relevant retention schedules. This includes digital audio and video. In addition to manual upload and storage, our application is able to automate and ingest files/documents generated from outside sources via our REST API. All files uploaded are associated with the selected office’s file plan to enforce departmental policies, naming conventions etc. Our system allows the customer to import all NARA-approved record schedules into the application. The uploaded and approved records schedules will be codified into a departmental file plan within the application, which consolidates guidance around information governance for easy reference. This makes records easy to store, retrieve, and dispose, as well as answering questions like how to name and file records, handle disposition and destruction, how to transfer records to NARA, and more. This process guarantees that records are accurately classified and managed in accordance with the department’s approved records schedules. This automated approach to records management allows record staff to quickly conduct compliance checks to verify that records are being managed according to their appropriate record schedule.

Our system captures and classifies metadata at ingestion, either automatically generating certain types metadata (like creation or modification date) to facilitate the user’s workflow or allowing custom metadata to inputting by the uploader. This allows organizations to create custom metadata fields as needed, and preserves metadata throughout the lifecycle, among other features such as searchability. This will support the

Capture and Metadata lifecycle phases by establishing authoritative records and (1) the description of the content of the record; (2) the structure of the record (form, format, and relationships between record components); (3) the business context in which the record was created; (4) relationships with other records and metadata; (5) identifiers and other information needed to retrieve the record; (6) the business actions and events involving the record throughout its existence.

Questions for Element 7 - Structured Data

Please provide a brief summary of your awarded offerings (products/services/solutions) under SIN 518210ERM that help agencies meet Element 7. Some example questions to consider are: What is your approach to managing structured data? Do you offer solutions additional to what the agency uses, work with their current systems, or both?

TransAccess GCR utilizes an open-source, relational database to serve as a robust and versatile database as a records repository hosted on a secure FedRAMP certified platform. Its design facilitates the structured organization of data, ensuring efficient storage and retrieval of information, such as user accounts, data sources, analytics, and content which will be populated through structured data imports, mappings, and transformations. Furthermore, all database instances are designed to support real-time interactions, allowing users to establish secure connections and retrieve up-to-date information seamlessly across any number of data sources through the user interfaces. Our repositories will accept any file format for storage (PDFs, emails, images etc.) as well as indexing. Our database’s encryption ensures that sensitive data will be securely stored and transmitted. This is essential for providing users with a versatile toolkit to explore and interact with data, which will be augmented with additional tools such as AWS QuickSight for data visualization.

While our records repository is hosted as a standalone application, due to the nature of records management, we do maintain connections with outside agency systems/databases. Our system manages the business-critical interfaces that we maintain with ARCIS and customer systems to ensure they are intact and functioning as designed. We maintain an interface inventory of interfaces between TransAccess GCR and all external systems, databases, applications, and components that interact with our application. In this inventory, we will document the details of each interface, including its purpose, functionality, data flow, and dependencies to anticipate any potential interruptions to our connection. We will also maintain vendor/contact information for the corresponding interfaces so that we can keep abreast of external patches, protocol changes and updates to those systems/connections that may impact our ability to communicate as well as establish a relationship and point of contact to troubleshoot issues that may arise. We have already developed automated scripts and alerts to detect if a connection has been broken/interrupted to begin incident response as soon as possible and mitigate any interruption to our customer’s electronic records management activities such as case binder tracking and requests. Our technical team continuously monitors TransAccess GCR for any database errors or performance issues. We will proactively identify and resolve any issues that may arise, ensuring that the application operates smoothly and efficiently without any disruptions. To facilitate this activity, we will utilize automated monitoring tools to continuously monitor the performance, availability, and health of the system. These tools will provide real-time alerts and notifications in case of any issues, allowing our team to quickly respond and address them before they escalate into critical problems. Our team will proactively analyze database logs and error reports to detect potential issues or trends that may impact performance or functionality. This proactive approach allows us to identify and address potential issues before they impact users or result in system downtime. We will also perform regular health checks and diagnostics, as well as ensuring that required vulnerability scanning on both the infrastructure and configuration base is conducted and properly reported (in terms of status and mitigation results).

[Response for Element 7 here — use as much space as you need. If you did not self-certify this Element in the

Questions for Element 8 - Shared Drives

Please provide a brief summary of your awarded offerings (products/services/solutions) under SIN 518210ERM that help agencies meet Element 8. Some example questions to consider are: What capabilities does your solution/services provide for identifying duplicates? What other organizational methods do you employ for managing shared drives?

TransAccess GCR is able to store any file format for storage, indexing and apply any relevant retention schedules. This includes documents from shared drives such as OneDrive and SharePoint. Over the years, our team has migrated millions of files successfully from legacy content management systems and Shared

Drives such as SharePoint and Laserfiche to HTS, ensuring that relevant records are captured and managed according to the agency’s approved records schedule. After an investigation and inventory of the structure and content of the legacy program office file share, such as the types of files, folder structure, and any metadata associated with them, we will execute our established migration procedure. Utilizing TransAccess

GCR’s REST API and content mapping process, our team of technical experts will provide loss-free data migration of these files and associated metadata, resulting in searchable records seamlessly integrated with retention schedules, version controls, and audit trails. To identify duplicates in shared drives, the system scans files based on attributes like file name, size, and checksum, flagging identical or similar files for review or removal. This process helps streamline storage usage and ensures organizational efficiency by minimizing redundant data. After this initial migration, our API will be able to provide batch updates, automatically pulling any records through the interface that may continue to be uploaded to those sites to ensure that all documents are captured and managed within the system.

[Response for Element 8 here — use as much space as you need. If you did not self-certify this Element in the

[Offeror Name] hereby certifies that we are capable of meeting all standards described in the solicitation and

NARA’s Universal Electronic Records Management Requirements attachment for each of the sections of

ERM Elements we have proposed, as indicated above.

Offeror

(To be signed only by an authorized principal, with authority to bind the undersigned contractor)

Casey Colclough__________________________

Name (Printed)

_CFO___________________________________

Title

_3/4/2024________________________________

Date

Change log for Version 3.0

1. The following ERM Elements were removed or updated in order to remain at parity with the Elements listed in NARA’s

Universal Electronic Records Management Requirements spreadsheet (Version 3)

○ Removed Cloud Services

○ Removed Engineering Drawings

○ Changed Digital Media (Photo) to Photographs

○ Combined Digital Audio and Video

2. The following ERM Elements names have been updated to remove the reference to their former name used in Version 1 of this document:

○ Element 1 - Office Management Applications: removed “(formerly ‘Desktop Applications’)” from the Element name

○ Element 7 - Structured Data: removed “(formerly ‘Databases’)” from the Element name

3. Added requirement for contractors to provide a brief summary of awarded offerings for each ERM Element that they self-certify. Added instructional language along with example questions for each Element to assist contractors with their responses.