The vendor is required to provide a commercial off-the-shelf (COTS), web-based, cloud-hosted audit management application that is FedRAMP-authorized. This solution may replace the current system and may involve migrating existing projects and data.
- Dashboards Configured software solution shall have:
a. Project Dashboards: Dashboards of major project information. Some possible examples include comments/notes and status of items contained in a project (for example in- progress, ready for review, and reviewed).
b. General Database Dashboards: Dashboards that summarize project universe information. For example, a dashboard that would summarize information from all projects within a given timeframe or project status based on milestones or phases (planning, fieldwork, reporting etc.), and finding details such as monetary impact and number of recommendations made.
- Reports configured software solution shall have:
a. Ability to generate reports across database fields in the entire database to include but not limited to:
i. Ability to create reports for tracking milestones - Possible examples include initial and revised dates compared to actual dates and cumulative time between milestones
ii. Ability to create reports to track projects. Examples of possible tracking elements include by Division, project status, origin, fiscal year expected to be completed/completed, scope, group, cost data (questioned costs/better use of funds), and project objective.
iii. Ability to generate reports that track monetary impact related to findings.
iv. Ability to track the number of recommendations and status of recommendations (i.e. concur/non-concur, open and closed) per project and summarize that information for the project universe.
v. Ability to export reports into standard formats (i.e. Word and Excel).
v. Ability to export reports into standard formats (i.e. Word and Excel).
- Distinct Projects configured software solution shall have:
a. Permissions, Attributes, and Schedule
i. Self-contained projects with unique permissions and roles. Role based permissions determine access and type/level of access to the projects.
ii. Unique project number for each project.
iii. Ability to record planned and multiple iterations of revised and actual milestones for each project to establish and track a schedule baseline.
b. Project Browser Audit Software System
i. Ability for users to see, access and filter projects by project information. Examples of filters could include title, project number, status of the project, phase of project and milestones.
ii. Allow the user to use various search terms to find and access a project. Examples include Project Title or Project Number.
- Providing Project Documentation to External Parties
a. Ability to export all data in the original structure related to a project including but not limited to documents, metadata in a format so that it can be accessed by external parties without requiring the purchase of additional software licensing.
b. Metadata may include but not be limited to electronic links between items, preparer and reviewer sign off histories, reviewer comments, users assigned to the project, and flags/identifiers associated with items.
- System Configurability and Centralized Management shall have:
a. User-friendly, intuitive, graphical interface following industry standard best practices allowing users to easily navigate the software after training.
b. Ability to create multiple project templates.
c. Ability to revise project templates.
d. Ability to create new unique audit projects.
e. Ability to create, assign, and change permissions at a global and project level based on user roles such as administrator, director, manager, reviewer, preparer, or combination of roles. This will allow centralized policy management by the agency.
f. Ability to create administrator accounts to perform administrative tasks in all projects.
g. Separate user accounts can be created and used for performing system administration actions.
h. Ability to assign staff to different projects with permissions specific to each project.
i. Ability to assign a group of users read only access to projects.
j. Ability to copy existing projects to create new projects.
k. Ability to copy parts of existing projects to create or incorporate into new projects.
I. Ability to configure data fields captured in projects that can be globally reported.
m. Configurable fields and labels for project information. Examples include project objective, division the project falls under, fiscal year completed/expected to be completed, project milestones (up to 20 customizable fields for milestones), project status, project findings including monetary impact (questioned costs/better use of funds) and non-monetary impact, report recommendations, number of recommendations, whether client concurred or non-concurred with recommendations, and status of recommendation.
n. Ability to make a project read only once it is complete so no additional changes can be made.
o. Ability to indicate that a project has been completed.
p. Ability to mark a project as cancelled or suspended and restrict access to read only.
Ability to reverse cancelation or suspension when needed.
q. Ability to generate and delete projects for training purposes.
r. Ability to delete projects.
