Volume 1 Requirements Matrix.xlsx
XLSX spreadsheet 24 KB Posted
- Attached to
- Agency Digital Asset Management System Federal contract opportunity
- Solicitation number
- 88310321Q00056
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Amendment 002.docx | DOCX document | |
| Appendix B - Contingency Plan Template.pdf | ||
| Appendix F - Configuration Management Database (CMDB) Template.pdf | ||
| Appendix E - System Security Plan Requirements.pdf | ||
| Appendix C - Incident Response Plan Template.pdf | ||
| 88310321Q00056 ADAMS.docx | DOCX document | |
| Appendix D - Quality_Assurance_Cloud_CMDB_Template.xlsx | XLSX spreadsheet | |
| Appendix G - Interface Control Document (ICD) Template.pdf | ||
| Amendment 001 Extension.docx | DOCX document | |
| 88310321Q00056 ADAMS.pdf | ||
| Appendix A - IT Security Requirements.pdf |
Show all 11
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Requirements
| REQUIREMENTS | DESIGN | DEVELOPMENT | VERIFICATION | DEPLOYMENT PREPARATION | CONTRACTOR'S RESPONSE | CONTRACTOR'S NOTES | |||||||
| Req # | Requirement Text | Verification Test Case / Step | Verification Status | Verification Criteria | UAT Test Case | UAT Status | Validation Criteria | 0-4 | Ready at Award through 90+ Days | (May be Used for Brief explanations, where applicable) | Req Priority | Yes/No | |
| 3.1.1 | NARA authorized users will have access to an ADAMS web-based system based on user roles and permissions assigned by a system administrator who can assign and create all the roles and functions of account management: permissions, roles, user groups, permissions, and restrictions. | Must | |||||||||||
| 3.1.2 | Authorized users will be able to bulk upload digital media (photos, videos, audio, graphic images) with required metadata fields populated manually at ingest, embedded in the IPTC, or uploaded with an associated csv or xml file. Users will be able to sort and collect assets in galleries or groups for exporting to their desktops, phones, internally and externally. | Must | |||||||||||
| 3.1.3 | Authorized users shall be able to manage digital special media assets via workflow. The solution should provide the capability for an authorized user to define and manage the workflow process through reporting on an audit trail that records all activity in the system, configuring and defining alerts, and through version control of digital assets. | Must | |||||||||||
| 3.1.4 | Authorized users shall be able to approve digital special media assets for use by the general public. The system should have a workflow that includes the email notification of assets awaiting approval and the email notification of assets that have been approved. Assets should be held in a queue only visible to the user and approver until the asset has been approved for release. | Must | |||||||||||
| 3.1.5 | Users will be able to perform searches for assets using and specifying all IPTC and custom metadata fields, parametric (advanced) searches, keywords. Search results will have the capability to be sorted, filtered, saved and exported. | Must | |||||||||||
| 3.1.6 | Users will be able to singularly and bulk export and crop asset derivatives in several resolutions/sizes. IE Still image as a high res tif or jpg, medium and low res jpg, and video exported in low and high res. Metadata is exported embedded in the file and as a sidecar extract alongside the derivative asset renditions. | Must | |||||||||||
| 3.1.7 | Authorized users will be able to securely share asset(s) to internal and external users (without authentication) via notification through email with a link to the selected assets. | Must | |||||||||||
| 3.1.8 | System administrator will be able to manage assets by associating an alert that will notify the system administrator to initiate a scheduled records transfer on a certain date through the employment of a proprietary metadata field designated, populated, and capable of being edited by system administrator. | Must | |||||||||||
| 3.1.9 | The system will provide canned (built-in) reports and custom reports showing approvals/rejections for any asset or user workflow. Canned and custom reports can be generated using rejection/approval or other pre-defined outcomes. | Must | |||||||||||
| 3.1.10 | Users will have access to online training which must be included with the system. | Must | |||||||||||
| 3.1.11 | The solution should be browser agnostic and accessible from Microsoft Edge and Google Chrome. | Must | |||||||||||
| 3.1.12 | The solution shall support Internet Protocol version 6 (IPv6). | Must | |||||||||||
| 3.1.13 | The solution user interface shall comply with Section 508 Standards for Electronic and Information Technology. | Must | |||||||||||
| 3.1.14 | The solution shall be in compliance with NARA IT Security Contractual Requirements by keeping an exportable, searchable audit log for modifications to digital content, have the capability for system administrator to run file integrity checks, and authenticate users using NARA's identity management and authentication services. | Must | |||||||||||
| 3.1.15 | The Vendor’s solution shall use existing NARAnet credentials and 2-factor authentication (via Security Assertion Markup Language (SAML) or NARA’s SecureAuth), when authenticating known NARA users. The Vendor’s solution may use means other than authentication for granting temporary access to external (non-NARA) users (e.g. a temporary unique link to an upload or download interface that can expire after a set amount of time). If such a methodology is proposed, the Vendor must describe how the methodology ensures that only the appropriate user(s) can access the link, and how a NARA user can restrict or terminate access to that link after a given time interval has expired. | Must | |||||||||||
| 3.2.1 | Authorized users will be able to publish assets directly to social media channels including: YouTube, Instagram, Facebook, Twitter from approved mobile and desktop devices. | Could | |||||||||||
| 3.2.2 | The solution may interoperate with multimedia editing and desktop publishing applications (Adobe Creative Suite) for editing photos, videos, and graphic images. | Could | |||||||||||
| 3.2.3 | The solution may will support a folder-based library structure. | Could | |||||||||||
| 3.3.2.1 | Software Support. Contractor phone support should be provided during standard working hours. NARA’s standard hours are defined as weekdays, not including statutory holidays, Monday through Friday between 6:30 AM and 6:00 PM ET. | Must | |||||||||||
| 3.3.2.2 | Software - Application Patches. All incremental application patches should be included and installed by the Contractor. Patches will be installed with the support of the COR. | Must | |||||||||||
| 3.3.2.3 | Operating System Patches. All operating systems (OS) patches will be tested for potential impact to the system, if any. The results will be published within 30 calendar days after being issued by the OS contractor. NARA will have access to this list. NARA personnel will install all OS patches after verifying operation from the Contractor. | Must | |||||||||||
| 3.3.2.4 | System Database Patches. All system database patches will be tested for potential impact to the system, if any. The results will be published within 30 calendar days after being issued by the system database manufacturer. NARA will have access to this list. NARA personnel will install all System Database patches after verifying operation from the manufacturer. | Must |
Agency Digital Asset Management System (ADAMS) Requirements Verification Traceability Matrix (RVTM)
&F Page &P of
File details come from the government source that posted it. Updated .