RFI_Audit Software Requirements.xlsx
XLSX spreadsheet 21 KB Posted
- Solicitation number
- OAA-24-00164
About this file
This document is a Request for Information (RFI) issued by the Department of Labor (DOL) to identify companies interested in providing an Audit Management Information System for enterprise audit management and tracking.
The RFI states that the purpose is to gather information about potential solutions to meet the DOL's requirements, which are outlined in the attached Draft Performance Work Statement (PWS). The PWS details various functional, technical, and performance requirements for the audit management system, including capabilities related to infrastructure, security, system configurability, document management, review processes, cross-indexing, independent referencing, and reporting. Interested parties are asked to respond to the RFI questionnaire, provide a capabilities statement, and offer estimated pricing for market research purposes. The RFI is for information gathering only and does not commit the government to issuing a contract.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFI Notice for SAM.gov.docx | DOCX document | |
| RFI Questionnaire_Audit Management Information System.docx | DOCX document | |
| Draft PWS for Audit Management Information System.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Audit Mgmt Vendor Req
| Requirements | Met without additional development | Met with additional development | Cannot be met | |
| Infrastructure Requirements – Unclassified Network | ||||
| A1 | Communicates clearly defined software patch and upgrade schedules to afford proper planning | |||
| A2 | Performs testing prior to patch/upgrade installations to production environment to ensure functionality | |||
| A3 | Provide the ability to extract all data from off-premise cloud (FedRAMP certification required) | |||
| A4 | Ensure compatibility with Windows 10 or higher | |||
| A5 | Ensure compatibility with MS Office 365 and above | |||
| A6 | Supports load-balancing (i.e. high availability, failover, clustering) to ensure seamless operations | |||
| A7 | Must support virtual machines and/or virtual desktop infrastructure (VDI) to provide flexibility for a broad user base | |||
| A8 | Must support single user sign-on/PIV cards consistent with federal employee access and credentials | |||
| A9 | Must handle slow or latent connections via VPN or remote connections to ensure availability and performance | |||
| Security | ||||
| C1 | Provides full logging of user activity to support agency reporting requirements | |||
| C2 | Provides access to logs and activity reports to ensure availability of information for analysis and decision-making | |||
| C3 | Must be FIPS 140-02 encryption capable | |||
| C4 | PIV access required, must be supported | |||
| System Configurability and Centralized Management | ||||
| D1 | Provides user-friendly, intuitive graphical interface to ensure usability and accessibility for all users | |||
| D2 | Must be compliant with revised Section 508 accessibility standards to ensure accessibility, meeting all Section 508 criteria | |||
| D3 | Provides the ability to create multiple project templates to ensure new projects include all required steps based on their type, so unique work efforts can follow out-of-the-box or ad hoc workflows | |||
| D4 | Provides ability to create templates for auditors/analysts to document work, including designated fields to ensure unique business needs | |||
| D5 | Ability to create and assign permissions on user roles such as administrator, supervisor, manager, independent referencer, reviewer, preparer, or combination of roles | |||
| D6 | Ability to assign users to different projects with different roles and permissions specific to each project to ensure flexibility | |||
| D7 | Centralized policy management to ensure consistency and ease of use | |||
| D8 | Ability to copy projects (extend, rollover) to reuse templates and project details | |||
| D9 | Configurable fields, labels, and flags for project information, recommendations to account for unique business requirements | |||
| Retention/archiving/storage | ||||
| E1 | Must support Agency records retention requirements and policies, to ensure appropriate disposition of audit artifacts | |||
| E2 | Ability to access completed/finalized projects, for the purpose of analysis and reporting | |||
| E3 | Ability to push completed/archived projects to latest software version to ensure accessibility and support historical analysis | |||
| Training | ||||
| F1 | Must provide training in simulated production environment with current work product so Agency can verify necessary functionality included with the proposed solution | |||
| F2 | Provides robust training for administrators to ensure ongoing local support | |||
| F3 | Supports train-the-trainer efforts to ensure agency staff can transfer knowledge | |||
| F4 | Provides training documentation as needed to supplement local support | |||
| Support | ||||
| G1 | Provides access to daily technical support to address urgent issues within 1-2 days | |||
| G2 | Provides access to detailed reference materials to facilitate timely issue resolution | |||
| Distinct Projects | ||||
| H1 | Provides functionality to create self-contained projects with unique permissions and roles to ensure need-to-know, restricted access to audit activities | |||
| H2 | Must provide unique project identifiers to differentiate various audit records and activities | |||
| H3 | Must provide ability to establish, monitor, and revise milestones for each project to support tracking and analytics | |||
| H4 | Ability to design and manage projects for analysis for specific audits as well as multiple audit records | |||
| H5 | Must provide ability to deploy separate instances for different agencies/organizations allowing separation of work and access, ensuring access is based on roles and permissions | |||
| Document management | ||||
| I1 | Provides support for current and future Microsoft Office file types, including Outlook to ensure interoperability with standard software | |||
| I2 | Provides support for current and future Acrobat PDF files to ensure key functionality is maintained in support of audit processes | |||
| I3 | Must support for industry-standard media files (audio, video, image) | |||
| I4 | Creates unique identifier for each attached file to differentiate artifacts | |||
| I5 | Provides ability to update/replace attachments with version control management capabilities, to ensure appropriate copies are maintained for routine use | |||
| I6 | Provides ability to import/export/replace documents with version control management capabilities | |||
| I7 | Ensures support for large numbers of attachments with each project, including large individual attachments to ensure complete records and collection of associated artifacts with the appropriate audit record | |||
| I8 | Provides ability to restrict access to attachments within a project to support need-to-know access and privacy | |||
| I9 | Provides functionality to easily share selected attachments across projects to support convenience and re-use of artifacts | |||
| I10 | Provides ability to lock attachments to prevent changes to ensure consistency and integrity of the audit record | |||
| I11 | Provides functionality to set follow-ups by date and follow-up type based on specific correspondence, due actions, documents, and artifacts | |||
| Review processes for all documentation, including findings and recommendations | ||||
| L1 | Provides ability to support preparer sign-offs to ensure recording of appropriate status of audit activities and artifacts | |||
| L2 | Provides ability to support reviewer sign-offs, including multi-level reviews, to support layered review and signatures | |||
| L3 | Provides functionality to support reviewer-to-preparer comments and retain them for integrity and consistency, indicating status of each comment and artifact | |||
| L4 | Provides ability to support peer-to-peer comments and notes that are retained for accuracy, integrity and consistency | |||
| L5 | Provides ability to identify changes were made to audit records and artifacts after supervisory review to determine status of recommendations, notes, and key documentation steps | |||
| Cross-Indexing | ||||
| M1 | Provides ability to index auditor/analyst write-ups to supporting documentation | |||
| M2 | Provides functionality to link documentation to artifacts created within software as well as attachments such as Word, Excel, Acrobat documents to ensure related artifacts are associated with the appropriate records | |||
| M3 | Provides ability to efficiently handle large numbers of indices within individual documents and across the audit file | |||
| Independent Referencing | ||||
| N1 | Provides capability to review and verify cross-index of all statements of fact within MS Word reports to ensure all documentation is available per each record | |||
| N2 | Provides ability to add visual indicators or status showing independent referencer has verified that indexed evidence supports each statement of fact (e.g. tickmarks) | |||
| Findings and Recommendations | ||||
| O1 | Provides ability to develop and document findings based on audit work, so all findings are associated with the appropriate record | |||
| O2 | Provides ability to develop and document recommendations based on audit work, so all findings are associated with the appropriate record | |||
| Miscellaneous Features | ||||
| Q1 | Supports copy/paste within the application and across findings, recommendations, and other artifacts associated with the record | |||
| Q2 | Supports inline and on-demand spell-check, with editable dictionary | |||
| Q3 | Provides ability to create and format tables within the application to support analysis and reporting | |||
| Q4 | Provides ability to generate reports and dashboards across all data sets and platform for each project and sets of projects based on key indicators | |||
| Q5 | Provides ability to create standard reports for tracking milestones – initial and revised dates compared to actuals, so work-in-progress and completed items can be analyzed | |||
| Q6 | Provides ability to automate creation of required ad hoc and out-of-box reports | |||
| Q7 | Provides ability to generate ad hoc and out-of-box reports on all database fields | |||
| Q8 | Supports creating of ad hoc reports and queries to ensure unique analysis activities and reporting are complete and accurate |
File details come from the government source that posted it. Updated .