REVISED Attachment F - System Requirements_.xlsx
XLSX spreadsheet 158 KB Posted
- Attached to
- Provider Management Platform RFP
- Solicitation number
- S-58100-00007532
- Issued by
- Marion County, Oregon
About this file
This document is a Requirements Traceability Matrix (RTM) for the Provider Management Platform (PMP) Implementation Project for the State of Oregon (OR), Department of Early Learning and Care (DELC). The project aims to implement a new solution to guide child care providers through licensing, background check, and ERDC enrollment processes, enable DELC employees to conduct compliance and oversight activities, and generate ERDC subsidy bills and payments. The RTM outlines functional and non-functional requirements for the system, which must support desktop, tablet, and mobile users with an intuitive interface, allow for customized reporting and dashboards, and meet stringent security and compliance standards. The system must also integrate with external systems such as the Oregon Records Management System and allow for configuration of workflows, letters, and checklists.
The RTM indicates that the PMP Implementation Project is a contract opportunity for the State of Oregon, involving the jurisdictions of Marion County and the City of Salem. The system must be cloud-based and FedRAMP-certified, with the ability to support at least 1,000 concurrent users without performance degradation and a minimum uptime of 99.9%. DELC will evaluate the vendor's ability to meet the specified requirements during the selection process.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Att F - System Requirements .xlsx | XLSX spreadsheet | |
| DELC PMP RFP Att A - Sample Contract - Final.pdf | ||
| PMP RFP Addendum 2 - FINAL.pdf | ||
| Att F continued. - User Stories .xlsx | XLSX spreadsheet | |
| ProviderManagementPlatform RFP FINAL - DOJ EIS CSS APPROVED 7.13.pdf | ||
| 33180 MMCAP Infuse Notice of Solicitation for Medication Repackaging Srvs.docx | DOCX document | |
| PMP Intent to Award - Final~1.pdf | ||
| Questions and Answers Doc - PMP RFP~1.pdf | ||
| Att E - Price Propsal v2.xls | XLS spreadsheet | |
| Att E - Price Propsal.xls | XLS spreadsheet | |
| Competitive Range Letter - PMP RFP.pdf | ||
| PMP RFP Addendum 1 ~2.pdf |
Show all 12
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
Cover Page
| State of Oregon (OR), Department of Early Learning and Care (DELC) | |
| Provider Management Platform (PMP) Implementation Project | |
| Requirements Traceability Matrix (RTM) | |
| Version: | 2.0 |
| Tab | Description |
| Cover Page | Cover page of RTM |
| Document Control | Version control and additional descriptive information. |
| Methodology | Methodology utilized for formulate requirements. |
| Requirements | Formulated list of requirements of PMP solution. |
| Common Acronyms | Acronyms frequently utilized in the RTM. |
| Definitions | Definitions for common terms used in the RTM. |
Document Control
| Document Control Information | |
| Document Information | |
| Document Name | Requirements Traceability Matrix (RTM) |
| Project Name | State of Oregon (OR), Department of Early Learning and Care (DELC) Provider Management Platform (PMP) Implementation Project |
| Document Author | DELC / Deloitte |
| Document Version | 2 |
| Document Status | Final |
| Date Released | 6/20/23 |
| Document Edit History | |||||
| Version | Date | Additions/Modifications | Prepared/Revised By | ||
| 1.00 | 06/02/2023 | Document Created | DELC/Deloitte | ||
| 2.00 | 06/13/2023 | Incorporated EIS Feedback | DELC/Deloitte | ||
| Document Review/Approval History | |||||
| Date | Name | Organization/Title | Comments | ||
| 6/8/23 | Jim Zuniga | Oregon Enterprise Information Services | Reviewed and resubmitted to DELC on 06/08/23 with feedback on the requirements tab. |
Methodology
| Methodology to Formulate PMP Requirements |
| Below is a list and overview of the process areas used to break out the requirements for the new solution. The process areas breakout the functionalities desired for the platform and the requirements which correspond to these areas. For a full overview of the methodology used, please see the Requirements Management Plan. |
| Process Area | Overview | Req. ID | L1 # |
| Non-Functional Requirements | Maintain the technical, security, and administrative functionality to provide transparent, secure, and accurate information for staff and partners. | NF | 1-9 |
| Child Care Provider Management | Guide providers through license, background check, and ERDC enrollment processes, through an online portal, to enhance user experience and provide self-service capabilities. | PM | 10-16 |
| Child Care Program Oversight and Governance | Enable DELC employees to conduct compliance, oversight, investigative and administrative processes, at both the main office and field offices, with minimal administrative burden. | OG | 17-24 |
| ERDC Subsidy Billing and Payment | Generate ERDC subsidy bills and issue payments, or corrections, to providers and labor unions in a timely and effective manner. | BP | 25-30 |
| ERDC Family Support Services | Provide ERDC families self-service capabilities and access to transparent information. | FS | 31-35 |
-The following user groups are used throughout the RTM to ensure the platform can provide the capabilities needed for these users types.
-The actual user permissions and roles of the specific users will be determined once the vendor is selected.
-Please use this table to better understand the definition and examples of the types of users within the user groups used in the requirements.
| RTM User Groups | Definition of User Group | Examples of Types of Users Associated with User Group | ||
| Internal User | Department of Early Learning and Care Agency Employees that will need to be able to log into the system to assign or work on assigned tasks in order to; facilitate license processes, oversight and compliance processes, background checks, ERDC program enrollment, billing and payments for subsidy providers and conduct additional internal functions the PMP will host for the agency. | Billing Team, Field Staff, Managers of Departments, Investigative Specialists, Background Check Unit employees, Compliance Officers, Accounting Team, Data and Analytics team members | ||
| Administrative User | Department of Early Learning and Care Agency System Administrators with the highest level of permissions over the system. | System Administrators | ||
| External User | New or Existing Providers that will need to create accounts to access the system so they can maintain compliance and status as a provider (licensed and license exempt), apply for the ERDC program, undergo the background check process, send/receive payments and conduct additional external functions the PMP will host for the agency. | Facility owners/administrators, ERDC program providers, individuals undergoing a background check, Regulated Subsidy (license exempt) providers | ||
| Family User | New or Existing Families that use services provided by DELC so that they can view actions, information, and upload information to their online portals. | |||
| While the Agency would like the system to be capable of creating this user grouping, this user group and type of external portal is not the immediate priority for the initial release of the Platform. | Families / Parents receiving benefits from the ERDC Program |
Requirements
| Requirement ID | Program Area | L1 ID | L1 Requirement | ||
| Note: L1 requirements represent primary functionality area. | L1 Status | L2 ID | L2 Requirement | ||
| Note: L2 requirements represent high level capabilities of the system. | L2 Status | L3 ID | L3 Requirement | ||
| Note: L3 requirements represent system design elements. | L3 Status | Recommended Priority | DELC Notes | Vendor Ability to Meet Requirement Criteria | Vendor Comments |
(Rationale behind meets with exception or plan / intent to meet this requirement in the future)
| NF-001-001 | Non-Functional Requirements | 1 | UX/UI | Validated | 1 | The system shall allow for intuitive cross-system search by standard and custom data fields and display custom fields as needed by standard report. | Validated | To be defined upon vendor selection | Critical |
| NF-001-002 | Non-Functional Requirements | 1 | UX/UI | Validated | 2 | The system shall support desktop, tablet, and mobile users with a user friendly interface. | Validated | To be defined upon vendor selection | Critical |
| NF-001-003 | Non-Functional Requirements | 1 | UX/UI | Validated | 3 | The system shall allow all users to reorganize landing pages in the application to allow for the display of information most relevant to the user in accessible locations. | Validated | To be defined upon vendor selection | Critical |
| NF-001-004 | Non-Functional Requirements | 1 | UX/UI | Validated | 4 | The system shall allow for user selection of page layouts and short-cuts utilized in all system functionality. | Validated | To be defined upon vendor selection | Critical |
| NF-001-005 | Non-Functional Requirements | 1 | UX/UI | Validated | 5 | The system shall allow for the ability to perform searches that include a wildcard, date ranges, and/or numerical values. | Validated | To be defined upon vendor selection | Critical |
| NF-001-006 | Non-Functional Requirements | 1 | UX/UI | Validated | 6 | The system shall provide a customized landing page that displays logical information based on the user type and modules utilized (i.e., pending tasks assigned to the user, applications or visits assigned to the user, and any past due actions assigned to the user) and is configurable by Administrative User. | Validated | To be defined upon vendor selection | Critical |
| NF-001-007 | Non-Functional Requirements | 1 | UX/UI | Validated | 7 | The standard system shall be able to generate all reports in a format compatible with Adobe Reader, Microsoft Word, or Microsoft Excel. | Validated | To be defined upon vendor selection | Critical |
| NF-001-008 | Non-Functional Requirements | 1 | UX/UI | Validated | 8 | The standard system shall allow Administrative Users to manage field labels in the user interface. | Validated | To be defined upon vendor selection | Critical |
| NF-001-009 | Non-Functional Requirements | 1 | UX/UI | Validated | 9 | The system shall support upload operations performed in the background to allow Internal Users continued access to all interface capabilities while files are being uploaded. | Validated | To be defined upon vendor selection | Critical |
| NF-002-001 | Non-Functional Requirements | 2 | Reporting | Validated | 1 | The system shall allow Internal Users to create, run, save, and re-run parameterized reports utilizing any data in the application for which the Internal User has the required permissions to access. | Validated | To be defined upon vendor selection | Critical |
| NF-002-002 | Non-Functional Requirements | 2 | Reporting | Validated | 2 | The system shall allow for billing information and billing history to be accessible for both external and Internal Users. | Validated | To be defined upon vendor selection | Critical |
| NF-002-003 | Non-Functional Requirements | 2 | Reporting | Validated | 3 | The system shall allow for scheduling and results information related to an field visit (i.e., date and outcomes of a visit) to be viewed on the External Users screens. | Validated | To be defined upon vendor selection | Critical |
| NF-002-004 | Non-Functional Requirements | 2 | Reporting | Validated | 4 | The system shall send automated text messages, emails and posts onto the Internal Users and External Users portals to create awareness of all upcoming deadlines. | Validated | To be defined upon vendor selection | Critical |
| NF-002-005 | Non-Functional Requirements | 2 | Reporting | Validated | 5 | The system shall incorporate state holidays into applicable reports. | Validated | To be defined upon vendor selection | Critical |
| NF-002-006 | Non-Functional Requirements | 2 | Reporting | Validated | 6 | The system shall provide the ability to create dashboards that combine information from all databases in the system. | Validated | To be defined upon vendor selection | Critical |
| NF-002-007 | Non-Functional Requirements | 2 | Reporting | Validated | 7 | The system shall enable the Internal Users to save searches for reuse. | Validated | To be defined upon vendor selection | Critical |
| NF-002-008 | Non-Functional Requirements | 2 | Reporting | Validated | 8 | The system shall enable users to view/report on aggregated activity and drill down on selected results to view supporting detail. | Validated | To be defined upon vendor selection | Critical |
| NF-002-009 | Non-Functional Requirements | 2 | Reporting | Validated | 9 | The system shall enable Internal Users to view and search by the External User information, date, billing number, facility, license number and assigned employees to see records. | Validated | To be defined upon vendor selection | Critical |
| NF-002-010 | Non-Functional Requirements | 2 | Reporting | Validated | 10 | The system shall maintain a historical archive of all events involving Criminal Justice Information (CJI). | Validated | To be defined upon vendor selection | Critical |
| NF-003-001 | Non-Functional Requirements | 3 | IAM | Validated | 1 | The system shall support SAML (current version). | Validated | To be defined upon vendor selection | Critical |
| NF-003-002 | Non-Functional Requirements | 3 | IAM | Validated | 2 | The system shall support MFA (Multi-Factor Authentication) for External Users. | Validated | To be defined upon vendor selection | Critical |
| NF-003-003 | Non-Functional Requirements | 3 | IAM | Validated | 3 | The system shall support configurable role based access control. | Validated | To be defined upon vendor selection | Critical |
| NF-003-004 | Non-Functional Requirements | 3 | IAM | Validated | 4 | The system shall be able to track and report on the following activities: |
Login attempts Assessments, creation, or changing/editing of permissions on user accounts, files, directories, and other solution resources Attempts to modify passwords Actions by privileged accounts
| Attempts to access, modify, or destroy history/log files | Validated | To be defined upon vendor selection | Critical | ||||||||
| NF-003-005 | Non-Functional Requirements | 3 | IAM | Validated | 5 | The systems shall allow administrator user to utilize an active directory to configure user groups and user permissions. | Validated | To be defined upon vendor selection | Critical | ||
| NF-003-006 | Non-Functional Requirements | 3 | IAM | Validated | 6 | The system shall allow for Administrative Users to create custom roles within the role based access functionality. | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-001 | Non-Functional Requirements | 4 | Security | Validated | 1 | The system shall employ network segregation. | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-002 | Non-Functional Requirements | 4 | Security | Validated | 2 | The system shall be cloud-based and FedRAMP-certified. | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-003 | Non-Functional Requirements | 4 | Security | Validated | 3 | The system shall utilize a DELC-approved anti-virus software, firewall solution, and Intrusion Prevention System (IPS). | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-004 | Non-Functional Requirements | 4 | Security | Validated | 4 | The system shall require External Users to change their password at the first login after their password has been created or reset by an administrator. | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-005 | Non-Functional Requirements | 4 | Security | Validated | 5 | The system shall support mandated reset of user passwords periodically and the ability to time out upon inactivity after configurable time. | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-006 | Non-Functional Requirements | 4 | Security | Validated | 6 | The system shall allow a maximum of 5 unsuccessful login attempts per user, after which user credentials must be reset. | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-007 | Non-Functional Requirements | 4 | Security | Validated | 7 | The system shall support transport layer encryption 1.3 (TLS 1.3) or higher. | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-008 | Non-Functional Requirements | 4 | Security | Validated | 8 | The system must use encryption of data at rest and data in transit (AES 256 or better). | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-009 | Non-Functional Requirements | 4 | Security | Validated | 9 | The system shall segregate, at least logically, all data created or used by DELC from other customer's data and disallow comingling of the data. | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-010 | Non-Functional Requirements | 4 | Security | Validated | 10 | The system shall support endpoint detection and response through continuous threat and malware monitoring. | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-011 | Non-Functional Requirements | 4 | Security | Validated | 11 | The system shall support set up and authentication for administrative privileged actions from a standard user account. | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-012 | Non-Functional Requirements | 4 | Security | Validated | 12 | The system shall support encryption keys, and access to encryption keys, in a cloud deployment that must be controlled by the agency by using CMK on top of FIPS 140 (current stable version) validated KMS. | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-013 | Non-Functional Requirements | 4 | Security | Validated | 13 | The system shall support a minimum of 128 bit encryption, and the decryption keys must be at least 10 characters long, a mix of upper and lowercase letters, numbers, and special characters. | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-014 | Non-Functional Requirements | 4 | Security | Validated | 14 | The system shall automatically change the encryption keys when a user no longer needs access to the encrypted data. | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-015 | Non-Functional Requirements | 4 | Security | Validated | 15 | The system shall operate any add-ons in a secure government cloud at a GCC moderate level. | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-016 | Non-Functional Requirements | 4 | Security | Validated | 16 | The system shall provide immutable logs (logging that would assist in a forensic investigation in the event of a compromise or for audit by either the CJIS Audit Unit (CAU) or the CJIS Systems Agency (CSA)). | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-017 | Non-Functional Requirements | 4 | Security | Validated | 17 | The system shall ensure that any logs created with DELC data are only available to authorized Internal Users. | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-018 | Non-Functional Requirements | 4 | Security | Validated | 18 | The system shall dispose of files/ data that fall outside of the data retention policy defined by DELC. | Validated | To be defined upon vendor selection | Critical | ||
| NF-004-019 | Non-Functional Requirements | 4 | Security | Validated | 19 | The system must meet or have the ability to meet the current Statewide Information and Cyber Security Standards V1.0 or be FedRamp compliant (https://www.oregon.gov/das/OSCIO/Documents/2019StatewideInformationAndCyberSecurityStandardsV1.0.pdf) | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-001 | Non-Functional Requirements | 5 | Configuration | Validated | 1 | The system shall have the ability to configure letters, checklists, and workflows to DELC division-specific requirements. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-002 | Non-Functional Requirements | 5 | Configuration | Validated | 2 | The system shall have the ability to refund payments and generate send refunded payment notices to Users. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-003 | Non-Functional Requirements | 5 | Configuration | Validated | 3 | The system shall support all Accounting to generate transaction and balance statement for background check contract/accounting pool on monthly, quarterly, yearly frequency, and on demand. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-004 | Non-Functional Requirements | 5 | Configuration | Validated | 4 | The system shall have the ability to archive data, documents and correspondences attached to legal action in Oregon Records Management System for reference. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-005 | Non-Functional Requirements | 5 | Configuration | Validated | 5 | The system shall track and reconcile Oregon State Police bills for background checks (fingerprints and sex offender registry checks) performed to create an payment history. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-006 | Non-Functional Requirements | 5 | Configuration | Validated | 6 | The system shall reconcile Field Print bill for DELC Accounting for the fingerprinting services with the figure prints requested and processed by Field Print to maintain accuracy. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-007 | Non-Functional Requirements | 5 | Configuration | Validated | 7 | The system shall allow only Administrative Users to make configuration changes to systems that store CJI. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-008 | Non-Functional Requirements | 5 | Configuration | Validated | 8 | The system shall support self-service password reset for all Users. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-009 | Non-Functional Requirements | 5 | Configuration | Validated | 9 | The system shall allow for the creation of online portals for Internal Users, External Users, Administrative Users, and Family Users, with differing permissions and dashboard views. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-010 | Non-Functional Requirements | 5 | Configuration | Validated | 10 | The system shall allow for the configuration of External User pages, in which all pages, fields, and workflows can be customized based on the status of their background checks, license database, and/or ERDC program. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-011 | Non-Functional Requirements | 5 | Configuration | Validated | 11 | The system shall allow for the configuration of Internal Users pages, in which all pages, fields, and workflows can be customized based on the employee's role and credentials. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-012 | Non-Functional Requirements | 5 | Configuration | Validated | 12 | The system shall allow for the configuration of Family User pages, in which all pages, fields, and workflows can be customized based on the status of their enrollment in ERDC program. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-013 | Non-Functional Requirements | 5 | Configuration | Validated | 13 | The system shall allow for the configuration of context sensitive fields, with dynamic display or hiding of data fields, based on value contained in another associated data field and is configurable by Administrative Users. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-014 | Non-Functional Requirements | 5 | Configuration | Validated | 14 | The system shall allow for the configurable organization of data fields within the External Users, Internal Users, Administrative Users, and Family Users portals. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-015 | Non-Functional Requirements | 5 | Configuration | Validated | 15 | The system shall allow for the creation of custom data fields without additional code development and should be maintainable with workflow. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-016 | Non-Functional Requirements | 5 | Configuration | Validated | 16 | The system shall allow for custom fields to be named. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-017 | Non-Functional Requirements | 5 | Configuration | Validated | 17 | The system shall allow for the configuration of the data type in a custom field (to include text, URL, drop down with expected values, number, decimal, currency, pick list). | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-018 | Non-Functional Requirements | 5 | Configuration | Validated | 18 | The system shall allow Administrative Users custom fields to be configured as required fields. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-019 | Non-Functional Requirements | 5 | Configuration | Validated | 19 | The system shall allow for the assignment of custom fields to User application, status, and billing pages. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-020 | Non-Functional Requirements | 5 | Configuration | Validated | 20 | The system shall allow for the assignment of custom fields to the ERDC pages. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-021 | Non-Functional Requirements | 5 | Configuration | Validated | 21 | The system shall have the ability to perform calculations on standard and custom data fields. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-022 | Non-Functional Requirements | 5 | Configuration | Validated | 22 | The system shall display the result of any calculations for quantitative statistics on reporting screens. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-023 | Non-Functional Requirements | 5 | Configuration | Validated | 23 | The system shall allow for the dynamic display or hiding of data fields based on the selected value in another field. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-024 | Non-Functional Requirements | 5 | Configuration | Validated | 24 | The system shall allow for any activities that can be performed on a standard field to be performed on a custom field. | Validated | To be defined upon vendor selection | Critical | ||
| NF-005-025 | Non-Functional Requirements | 5 | Configuration | Validated | 25 | The system shall allow for the creation of custom data fields in the employee data entry fields for visit reports, compliance tracking, and updates to letters. | Validated | To be defined upon vendor selection | Critical | ||
| NF-006-001 | Non-Functional Requirements | 6 | Infrastructure | Validated | 1 | The system shall operate and store all data within the U.S., its possessions, and territories. | Validated | To be defined upon vendor selection | Critical | ||
| NF-006-002 | Non-Functional Requirements | 6 | Infrastructure | Validated | 2 | The system shall support a minimum of 1,000 concurrent users without instability or a degradation in performance. | Validated | To be defined upon vendor selection | Critical | ||
| NF-006-003 | Non-Functional Requirements | 6 | Infrastructure | Validated | 3 | The system shall support an uptime of 99.9% (three nines). | Validated | To be defined upon vendor selection | Critical | ||
| NF-006-004 | Non-Functional Requirements | 6 | Infrastructure | Validated | 4 | The system shall provide support from the U.S., its possessions, and territories. | Validated | To be defined upon vendor selection | Critical | ||
| NF-006-005 | Non-Functional Requirements | 6 | Infrastructure | Validated | 5 | The system shall support a transactional response time of no more than 1 second for 95% of actions. | Validated | To be defined upon vendor selection | Critical | ||
| NF-006-006 | Non-Functional Requirements | 6 | Infrastructure | Validated | 6 | The system shall provide an indicator (progress bar) of action in progress for actions with a response time greater than 5 seconds. | Validated | To be defined upon vendor selection | Critical | ||
| NF-006-007 | Non-Functional Requirements | 6 | Infrastructure | Validated | 7 | The system shall not have a reduced rate of speed during peak times of concurrent use. | Validated | To be defined upon vendor selection | Critical | ||
| NF-006-008 | Non-Functional Requirements | 6 | Infrastructure | Validated | 8 | The system shall adhere to DELC's Patch Management Policy. | Validated | To be defined upon vendor selection | Critical | ||
| NF-006-009 | Non-Functional Requirements | 6 | Infrastructure | Validated | 9 | The system shall not have a system downtime outside of the regular maintenance schedule without DELC approval 72 hours prior to the downtime. | Validated | To be defined upon vendor selection | Critical | ||
| NF-006-010 | Non-Functional Requirements | 6 | Infrastructure | Validated | 10 | The system shall be restored within the agreed Recovery Time Objective (RTO) in the event of unscheduled downtime. | Validated | To be defined upon vendor selection | Critical | ||
| NF-006-011 | Non-Functional Requirements | 6 | Infrastructure | Validated | 11 | DELC shall receive a communication from the vendor within 10 minutes of unscheduled and unplanned downtime. | Validated | To be defined upon vendor selection | Critical | ||
| NF-006-012 | Non-Functional Requirements | 6 | Infrastructure | Validated | 12 | In the event of a decommissioning of the system, the vendor must certify that the data and infrastructure is securely sanitized and/or destroyed using methods acceptable by the National Security Agency (NSA)/Central Security Service (CSS). | Validated | To be defined upon vendor selection | Critical | ||
| NF-006-013 | Non-Functional Requirements | 6 | Infrastructure | Validated | 13 | The system shall operate a COOP strategy that utilizes Cloud as the primary infrastructure and an alternative Cloud as a fallback infrastructure. | Validated | To be defined upon vendor selection | Critical | ||
| NF-006-014 | Non-Functional Requirements | 7 | Infrastructure | Validated | 14 | The system shall be capable of being served on assets owned (or instances) and controlled by DELC. | Validated | To be defined upon vendor selection | Important | ||
| NF-006-015 | Non-Functional Requirements | 8 | Infrastructure | Validated | 15 | The system shall allow an Administrative User to access the full data stored in its raw form. | Validated | To be defined upon vendor selection | Critical | ||
| NF-007-001 | Non-Functional Requirements | 7 | Regulatory | Validated | 1 | The system shall only store data that is compliant with regulatory policies set by the Oregon Government and associated agencies. | Validated | To be defined upon vendor selection | Critical | ||
| NF-008-001 | Non-Functional Requirements | 8 | Integration | Validated | 1 | The system shall utilize a RESTful API with read and write functions, preferably Oauth2 and with multiple service accounts with restricted scope and audit trail, in order to access and push data on all grants received by a User so there is traceability with all associated benefits records to use to and from external systems. | Validated | To be defined upon vendor selection | Critical | ||
| NF-008-002 | Non-Functional Requirements | 8 | Integration | Validated | 2 | The system shall utilize a RESTful API with read and write functions, preferably Oauth2 and with multiple service accounts with restricted scope and audit trail, in order to access and push data on financial transactions to use to and from external systems. | Validated | To be defined upon vendor selection | Critical | ||
| NF-008-003 | Non-Functional Requirements | 8 | Integration | Validated | 3 | The system shall utilize a RESTful API with read and write functions, preferably Oauth2 and with multiple service accounts with restricted scope and audit trail, in order to access and push data to the Oregon Records Management System to use to and from external systems. | Validated | To be defined upon vendor selection | Critical | ||
| NF-008-004 | Non-Functional Requirements | 8 | Integration | Validated | 4 | The system shall utilize a RESTful API with read and write functions, preferably Oauth2 and with multiple service accounts with restricted scope and audit trail, in order to access and push data on Users trainings records to use to and from external systems. | Validated | To be defined upon vendor selection | Critical | ||
| NF-008-005 | Non-Functional Requirements | 8 | Integration | Validated | 5 | The system shall utilize a RESTful API with read and write functions, preferably Oauth2 and with multiple service accounts with restricted scope and audit trail, in order to access and push data on Users accessible from the public to use to and from external systems. | Validated | To be defined upon vendor selection | Critical | ||
| NF-008-006 | Non-Functional Requirements | 8 | Integration | Validated | 6 | The system shall utilize a RESTful API with read and write functions, preferably Oauth2 and with multiple service accounts with restricted scope and audit trail, in order to access and push data related to quality ratings of Users to use to and from external systems. | Validated | To be defined upon vendor selection | Critical | ||
| NF-008-007 | Non-Functional Requirements | 8 | Integration | Validated | 7 | The system shall utilize a RESTful API with read and write functions, preferably Oauth2 and with multiple service accounts with restricted scope and audit trail, in order to access and push information on how to get a fingerprint and a voucher to use to and from external systems. | Validated | To be defined upon vendor selection | Critical | ||
| NF-008-008 | Non-Functional Requirements | 8 | Integration | Validated | 8 | The system shall utilize a RESTful API with read and write functions, preferably Oauth2 and with multiple service accounts with restricted scope and audit trail, in order to access and push criminal history and background check data to and from external systems. | Validated | To be defined upon vendor selection | Critical | ||
| NF-008-009 | Non-Functional Requirements | 8 | Integration | Validated | 9 | The system shall utilize a RESTful API with read and write functions, preferably Oauth2 and with multiple service accounts with restricted scope and audit trail, in order to access and push fingerprint data to and from external systems. | Validated | To be defined upon vendor selection | Critical | ||
| NF-008-010 | Non-Functional Requirements | 8 | Integration | Validated | 10 | The system shall utilize a RESTful API with read and write functions, preferably Oauth2 and with multiple service accounts with restricted scope and audit trail, in order to access and push family eligibility data for the ERDC Program to and from external systems. | Validated | To be defined upon vendor selection | Critical | ||
| NF-008-011 | Non-Functional Requirements | 8 | Integration | Validated | 11 | The system shall utilize a RESTful API with read and write functions, preferably Oauth2 and with multiple service accounts with restricted scope and audit trail, in order to access and push Users listed in the union database to and from external systems. | Validated | To be defined upon vendor selection | Critical | ||
| NF-009-001 | Non-Functional Requirements | 9 | System Administration | Validated | 1 | The system shall allow Administrative Users to access the user permissions associated with users accounts. | Validated | To be defined upon vendor selection | Critical | ||
| NF-009-002 | Non-Functional Requirements | 9 | System Administration | Validated | 2 | The system shall allow Administrative Users to reset the credentials for locked accounts so the access to this function is restricted. | Validated | To be defined upon vendor selection | Critical | ||
| NF-009-003 | Non-Functional Requirements | 9 | System Administration | Validated | 3 | The system shall support website accessibility standards as referenced at https://www.oregon.gov/pages/accessibility.aspx | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-001 | Child Care Provider Management | 10 | Process applications | Validated | 1 | The system shall create a unique account for an External User with the their email address and phone number they want to use to apply, so that they can access their information and updates online. | Validated | To be defined upon vendor selection | Critical | Applications include background checks, for a License or for the ERDC Program | |
| PM-010-002 | Child Care Provider Management | 10 | Process applications | Validated | 2 | The system shall send External Users an email and text with their account credentials for an online portal, to allow them to log in to complete required actions and view status. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-003 | Child Care Provider Management | 10 | Process applications | Validated | 3 | The system shall provide External Users the ability to change their password to maintain a secure login and access to their account. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-004 | Child Care Provider Management | 10 | Process applications | Validated | 4 | The system shall prompt returning, External Users to login so External Users do not try to make a new account every time they want to log in. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-005 | Child Care Provider Management | 10 | Process applications | Validated | 5 | The system shall allow for the External User to opt-in for paperless documentation only, so that all communications will be performed electronically. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-006 | Child Care Provider Management | 10 | Process applications | Validated | 6 | The system shall prohibit a new account to be made with the same email address and application details so duplicate accounts are not created for the same user in the system for different application types. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-007 | Child Care Provider Management | 10 | Process applications | Validated | 7 | The system shall provide External Users the ability to initiate an online application to start the background check process. | Validated | To be defined upon vendor selection | Critical | DELC currently stores the Users that pass a background check in a "Central Background Registry". | |
| PM-010-008 | Child Care Provider Management | 10 | Process applications | Validated | 8 | The system shall provide External Users the ability to initiate online applications for various license types, so they can begin the process. | Validated | To be defined upon vendor selection | Critical | License Applications include: Certified Center, Certified Family, Registered Family, and Recorded Programs. There are also License Exempt Applications | |
| PM-010-009 | Child Care Provider Management | 10 | Process applications | Validated | 9 | The system shall provide External Users the ability to initiate an online application to be a listed for the Employment Related Day Care (ERDC) program so they can receive subsidy payments. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-010 | Child Care Provider Management | 10 | Process applications | Validated | 10 | The system shall allow External Users to select the application type they are looking for so that they can begin their application. | Validated | To be defined upon vendor selection | Critical | Not all types of applications should be available to the public upon first application. | |
| PM-010-011 | Child Care Provider Management | 10 | Process applications | Validated | 11 | The system shall automatically prompt required content from the selected application so the External User fills out the data fields required. | Validated | To be defined upon vendor selection | Critical | Different application types require different fields to be included, so the system must store and reference the information on the specified application. | |
| PM-010-012 | Child Care Provider Management | 10 | Process applications | Validated | 12 | The system shall allow External Users to apply for license/facility modifications by selecting another application to fill out from a drop down menu so that they can apply online to update their status. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-013 | Child Care Provider Management | 10 | Process applications | Validated | 13 | The system shall auto populate new applications an External User begins with information from their profiles so that they do not need to duplicate manual data entries. | Validated | To be defined upon vendor selection | Critical | For example, a License User may initiate an application for change (e.g. capacity, ownership, address) in a license, so the system should pre-populate the application with data associated with the existing license. | |
| PM-010-014 | Child Care Provider Management | 10 | Process applications | Validated | 14 | The system shall provide External Users with existing accounts the ability to submit applications for other programs or licenses so that all of their information is consolidated in one account. | Validated | To be defined upon vendor selection | Important | ||
| PM-010-015 | Child Care Provider Management | 10 | Process applications | Validated | 15 | The system shall automatically populate the required fields and additional documentation requests based on the application type selected by the External User. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-016 | Child Care Provider Management | 10 | Process applications | Validated | 16 | The system shall enable External Users the ability to see the status of their applications through their online portal to provide self service capabilities and minimize the need for manual status updates. | Validated | To be defined upon vendor selection | Important | ||
| PM-010-017 | Child Care Provider Management | 10 | Process applications | Validated | 17 | The system shall prompt External Users to fill out required fields, depending on the application type, to limit follow up needed for additional information. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-018 | Child Care Provider Management | 10 | Process applications | Validated | 18 | The system shall automatically route applications to the correct DELC business unit based on the type of application submitted to decrease the need for manual assignments. | Validated | To be defined upon vendor selection | Critical | For example, if an application is a background check application, the system should alert and route the application to the background check unit based on the user role. | |
| PM-010-019 | Child Care Provider Management | 10 | Process applications | Validated | 19 | The system shall prompt External Users applying for a background check to associate their accounts to a facility name, address, and owner/administrator/license primary so the owner/administrator/license primary can see the status of their employees applications and eligibility. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-020 | Child Care Provider Management | 10 | Process applications | Validated | 20 | The system shall send the External User automatic alerts when their application status has been changed to increase visibility into the application process. | Validated | To be defined upon vendor selection | Important | ||
| PM-010-021 | Child Care Provider Management | 10 | Process applications | Validated | 21 | The system shall automatically record the date/time of all application submissions in order to track the lifecycle of applications. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-022 | Child Care Provider Management | 10 | Process applications | Validated | 22 | The system shall require an External User associated with a facility to enter and update the site information for facilities so that the information is available for Internal Users to reference. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-023 | Child Care Provider Management | 10 | Process applications | Validated | 23 | The system shall prompt a External User to enter and update the employees that are employed at their facility and the individuals that reside at the residence to add them to their record. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-024 | Child Care Provider Management | 10 | Process applications | Validated | 24 | The system shall provide the External User on a licensed facility license the ability to set user permission for individuals linked to the facility. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-025 | Child Care Provider Management | 10 | Process applications | Validated | 25 | The system shall allow External Users that started the application process on paper, to receive login credentials via email and text message so they can access their online accounts. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-026 | Child Care Provider Management | 10 | Process applications | Validated | 26 | The system shall notify an External User via email and text if their application is missing submission elements so they can finish their application. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-027 | Child Care Provider Management | 10 | Process applications | Validated | 27 | The system shall automatically identify if an application has been submitted late or timely and flag the application as timely or not in the system. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-028 | Child Care Provider Management | 10 | Process applications | Validated | 28 | The system shall notify External Users and Internal Users when an application is untimely so that they are aware of the late submission. | Validated | To be defined upon vendor selection | Important | ||
| PM-010-029 | Child Care Provider Management | 10 | Process applications | Validated | 29 | The system shall identify if an External User's application requires further review by the compliance team based on Self-attested entries. | Validated | To be defined upon vendor selection | Critical | Compliance required actions include examples like self identifying of history with: Medical Marijuana, User of Foster Care, Negative Prior History, etc. | |
| PM-010-030 | Child Care Provider Management | 10 | Process applications | Validated | 30 | The system shall allow Internal Users to complete and submit an Application on behalf of an applicant (or referencing a paper based application) and create a portal/login credentials. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-031 | Child Care Provider Management | 10 | Process applications | Validated | 31 | The system shall allow the External User to communicate with Internal Users through their online portal through direct messaging page and field so information and inquiries are consolidated. | Validated | To be defined upon vendor selection | Useful | ||
| PM-010-032 | Child Care Provider Management | 10 | Process applications | Validated | 32 | The system shall capture a communication log to maintain the communication history between the External Users and the Internal User through their online portal. | Validated | To be defined upon vendor selection | Useful | ||
| PM-010-033 | Child Care Provider Management | 10 | Process applications | Validated | 33 | The system shall allow an External User to request to withdraw an application at any time during the application process and maintain related record keeping of the history and reason. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-034 | Child Care Provider Management | 10 | Process applications | Validated | 34 | The system shall notify External Users with employees listed / household members to have employees / house hold members apply for a background check if they have yet to. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-035 | Child Care Provider Management | 10 | Process applications | Validated | 35 | The system shall allow External Users to request to voluntarily close their account(s) so the request can be reviewed by Users. | Validated | To be defined upon vendor selection | Important | ||
| PM-010-036 | Child Care Provider Management | 10 | Process applications | Validated | 36 | The system shall automatically sync training requirements to an External User's profile based on the application type so that the correct trainings are monitored for completion. | Validated | To be defined upon vendor selection | Critical | Different types of applications require different types of training requirements to be fulfilled. | |
| PM-010-037 | Child Care Provider Management | 10 | Process applications | Validated | 37 | The system shall allow Internal Users to charge or wave the fee for an application, based on DELC policies, so the correct payment amount is being collected. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-038 | Child Care Provider Management | 10 | Process applications | Validated | 38 | The system shall allow the External User to submit payments for an application through Inbound Payment Processing capability supported by major payment modes (i.e. electronic check, credit card). | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-039 | Child Care Provider Management | 10 | Process applications | Validated | 39 | The system shall provide custom calculation fields for fees to be paid for an application, based on the application type and information gathered. | Validated | To be defined upon vendor selection | Critical | The fee amount to be collected is based on multiple factors (i.e. application type, time-period, contracted rate, conditional fee waiver, etc.) | |
| PM-010-040 | Child Care Provider Management | 10 | Process applications | Validated | 40 | The system shall allow an Internal User to wave a fee for an application with a reason provided so that a record is kept and maintained. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-041 | Child Care Provider Management | 10 | Process applications | Validated | 41 | The system shall automatically populate the status of payments from Inbound Payment Processing function so the External Users and Internal Users know payment was received. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-042 | Child Care Provider Management | 10 | Process applications | Validated | 42 | The system shall send an alert to Internal Users and External Users if a payment is unable to be processed (i.e. if there is a Non-Sufficient Fund (NSF) error) | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-043 | Child Care Provider Management | 10 | Process applications | Validated | 43 | The system shall provide Internal Users access to the list of rules and statutes for charging external organizations for their Applications to verify the system calculated amount is correct. | Validated | To be defined upon vendor selection | Useful | ||
| PM-010-044 | Child Care Provider Management | 10 | Process applications | Validated | 44 | The system shall identify the user permissions an Internal User or External needs based on the information inputted and type of profile created. | Validated | To be defined upon vendor selection | Critical | ||
| PM-010-045 | Child Care Provider Management | 10 | Process applications | Validated | 45 | The system shall allow the External User to choose the language preference for their language portal so they can understand the information on the screen. |
tc={DC4E6CE1-BC8C-4226-83C6-A6B6B87F001A}: [Threaded comment]
Your version of Excel allows you to read this threaded comment; however, any edits to it will get removed if the file is opened in a newer version of Excel. Learn more: https://go.microsoft.com/fwlink/?linkid=870924
Comment:
| Does DELC have a list of languages they are expecting to have the users choose from? | Validated | To be defined upon vendor selection | Critical | At the moment, the five most commonly used languages are Russian, English, Vietnamese, Mandarin and Spanish, however the language capabilities will need to be dynamic to the changing needs of the agency. | |||||||
| PM-010-046 | Child Care Provider Management | 10 | Process applications | Validated | 46 | The system shall provide clear instructions and training for External Users on how to use the system so that they can effectively access their profiles and information. | Validated | To be defined upon vendor selection | Critical | ||
| PM-011-001 | Child Care Provider Management | 11 | Request and process documentation | Validated | 1 | The system shall prompt the External User to upload documentation based on application type to collect the inputs needed for all application processes. | Validated | To be defined upon vendor selection | Critical | ||
| PM-011-002 | Child Care Provider Management | 11 | Request and process documentation | Validated | 2 | The system shall prompt the External User to submit records of their training certificates so the system can log the training history. | Validated | To be defined upon vendor selection | Critical | ||
| PM-011-003 | Child Care Provider Management | 11 | Request and process documentation | Validated | 3 | The system shall process submitted documentation to determine if it has all of the required elements so the External User can be notified of unfulfilled submission requirements within the documentation. | Validated | To be defined upon vendor selection | Important | ||
| PM-011-004 | Child Care Provider Management | 11 | Request and process documentation | Validated | 4 | The system shall provide External Users recommendations for trainings to take to fulfill outstanding requirements based on the type of application submitted to improve access to resources. | Validated | To be defined upon vendor selection | Critical | ||
| PM-011-005 | Child Care Provider Management | 11 | Request and process documentation | Validated | 5 | The system shall allow an External User that is the facility/license owner/administrator/license primaries to request individuals to be linked to their facility for association. | Validated | To be defined upon vendor selection | Critical | ||
| PM-011-006 | Child Care Provider Management | 11 | Request and process documentation | Validated | 6 | The system shall flag a background check application as "out-of state" if the External User has lived in a different state over last 5 years. | Validated | To be defined upon vendor selection | Important | For example, background checks completed by out of state applicants are much more time / labor intensive than a standard renewal of an in state applicant. | |
| PM-011-007 | Child Care Provider Management | 11 | Request and process documentation | Validated | 7 | The system shall process External User the recorded birth dates of all of a residents living at a facility, in order to mark that residents over 18 must have completed background checks. | Validated | To be defined upon vendor selection | Critical |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .