E_Solution Data and Reporting RTM.xlsx
XLSX spreadsheet 58 KB Posted
- Attached to
- DCYF Enterprise Payment Solution
- Solicitation number
- 24-DCYF-CS-081
- Issued by
- Adams County, Asotin County, Benton County, Chelan County, Clallam County, Clark County, Columbia County, Cowlitz County, Douglas County, Ferry County, Franklin County, Garfield County, Grant County, Grays Harbor County, Island County, Jefferson County, King County, Kitsap County, Kittitas County, Klickitat County, Lewis County, Lincoln County, Mason County, Okanogan County, Pacific County, Pend Oreille County, Pierce County, San Juan County, Skagit County, Skamania County, Snohomish County, Spokane County, Stevens County, Thurston County, Wahkiakum County, Walla Walla County, Whatcom County, Whitman County, Yakima County, Asotin City, Clarkston City, Clarkston Heights-Vineland CDP, West Clarkston-Highland CDP, Benton City, Chelan City, Chelan Falls CDP, Clallam Bay CDP, Lewisville CDP, Rock Island City, Pacific Beach CDP, Whidbey Island Station CDP, Mercer Island City, Pacific City, Bainbridge Island City, Kingston CDP, Kitsap Lake CDP, Kittitas City, Klickitat CDP, Okanogan City, Anderson Island CDP, Fort Lewis CDP, Fox Island CDP, Herron Island CDP, Ketron Island CDP, North Fort Lewis CDP, Raft Island CDP, Stevenson City, Hat Island CDP, Lake Stevens City, Snohomish City, Spokane City, Spokane Valley City, Puget Island CDP, Garfield Town, Yakima City, Washington
About this file
This is a Requirements Traceability Matrix (RTM) document for the Washington State Department of Children, Youth, and Families (DCYF) Enterprise Payment Solution (DEPS) project, specifically detailing the Solution Data and Reporting Requirements under RFP No. 24-DCYF-CW-081. The document outlines detailed technical requirements across four main categories: General Reporting, Querying, Visualization, and Administration & Management. The requirements focus on system capabilities for data analytics, reporting functionality, user access controls, and data management tools needed for DCYF's payment solution system.
The RTM contains 66 specific requirements marked as either "Required" or "Preferred," with vendors expected to indicate their compliance using response codes (Out of Box, Configuration, Customization, Third Party Product, Future Release, or Not Available). Key requirements include graduated access to reports based on user roles, standardized parameterized reports, data visualization capabilities, querying tools, and comprehensive data quality management features. The document emphasizes the need for scalability, data security, and compliance with departmental policies and legal requirements for data retention and expungement.
View the file
Other files
Show all 31
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
Introduction
| State of Washington Department of Children, Youth, and Families (DCYF) |
| DCYF Enterprise Payment Solution (DEPS) |
| Attachment E: Solution Data & Reporting Requirements Traceability Matrix (RTM) |
| RFP No. 24-DCYF-CW-081 |
| Introduction |
| This document captures the Data and Reporting Non-Functional Requirements for the Department of Children Youth and Families' (DCYF's) DEPS Project. This document should be used in conjunction with the List of Reports delivered by the legacy SSPS system, Functional Requirements, the Implementation and Performance Non-Functional Requirements, the Technology-related Non-Functional Requirements, and the General System Design (GSD) report which documents the principles and guidelines for the DEPS future solution architecture. |
The Data and Reporting Non-Functional Requirements document contains the following sections:
1) Introduction
2) Instructions
3) Data and Reporting Non-Functional Requirements
4) List of SSPS related Applications
Within the Data and Reporting Requirements, the requirements are categorized by area as detailed below. Each category has its own tab in this workbook. 0
| ID | Section Title | Tab # |
| D | Data and Analytics Requirement Section | # |
| D1 | General Reporting | 3 |
| D2 | Querying | 4 |
| D3 | Visualization | 5 |
| D4 | Administration & Management | 6 |
&"Arial,Regular"&A
&"Arial,Regular"&9&F &"Arial,Regular"&9&P of &N
Respondent Instructions
| State of Washington Department of Children, Youth, and Families (DCYF) |
| DCYF Enterprise Payment Solution (DEPS) |
| Attachment E: Solution Data & Reporting Requirements Traceability Matrix (RTM) |
| RFP No. 24-DCYF-CW-081 |
| Respondent Instructions |
| This workbook contains Requirements for the DEPS system. The response codes below should be used by Vendors to indicate the fit of its solution to the State Requirements specified in this workbook. |
This template must be completed and submitted as an MS Excel file as part of the response to this RFP.
| Responses | Definition |
| Response Code: Y or N -- Will this Non-Functional Requirement be met by your solution? | Indicate whether the requirement, as currently written, will be met by the Respondent's proposal. Respond Y=Yes or N=No. |
| Response Code: O, C, D, F, T, N -- How will this Non-Functional Requirement be met by your solution? | Indicate how the requirement will be met by selecting either: |
O= Out of the Box, C = Configuration, D = Customization, T = Third Party Product, F = Future Release, N = Not Available
| O = Available Out of the Box. The Requirement will be met by leveraging existing out of the box application functionality available through the Vendor's existing solution to meet DCYF's requirements. | |
| C = Configuration. Configuration means the activation, arrangement or adjustment of software features and functionality that is part of the normal set-up of the software, such as establishing parameters, fields, and workflows. | |
| D = Customization. Customization means a change or addition to software program code to update the default capabilities or extend or modify existing features and functionality. | |
| T = Third Party Product. The Requirement will be met by commercially available third party software. The Vendor will integrate these third party products into their proposed DEPS architecture. In the Vendor Response column, indicate the name of the proposed third party software vendors and products and indicate its compliance with DCYF's technology or architecture standards. | |
| F = Future Release. The Requirement will be met by a future code development update to the application functionality of the Vendor's existing solution to meet DCYF's requirements | |
| N = Not Available. Requirement cannot be met. | |
| Vendor Proposed Release Date -- By what date will this requirement be met? | If the Vendor Response Code is "F" Indicate by which date the requirement will be met. If not applicable, the Vendor may leave the cell blank. |
| Vendor Justification for Not Meeting Requirement, if applicable | If the Vendor Response Code is "N," the Vendor is required to provide an explanation for not meeting the requirement. |
| Additional Comments | Additional comments. (Not Required). The Vendor may include additional comments at their discretion. |
Do not edit this worksheet.
D1 General Reporting
| State of Washington Department of Children, Youth, and Families (DCYF) |
| DCYF Enterprise Payment Solution (DEPS) |
| Attachment E: Solution Data & Reporting Requirements Traceability Matrix (RTM) |
| RFP No. 24-DCYF-CW-081 |
General Reporting
| Req # | Requirement Description | Requirement Priority | Vendor Response: | |
| Y or N | Vendor Response: | |||
| O, C, D, T, F, N | Vendor Proposed Release Date | |||
| (If selecting F) | Vendor Justification for Not Meeting Requirement, if applicable | |||
| (If selecting N) | Additional Comments (Not Required) | |||
| D1.1 | The System will provide the ability to impose graduated access to reports based on user role and DCYF requirements/permissions to better analyze financial data. | Required | ||
| D1.2 | The System will allow retention and expungement of financial records to be configured in adherence to department policy and legal requirements, so that the records are not accessible by case managers or other look-ups associated with case management, public disclosure, etc. It is important to note that retention and expungement rules generally require the data populating these records to be retained in the DCYF database for historical reporting purposes, so there must also be a mechanism to preserve the data in the database. |
| The details of DCYF's records retention schedules are available here: https://www2.sos.wa.gov/_assets/archives/recordsmanagement/dcyf-records-retention-schedule-v.2.0-(july-2019).pdf | Required | ||
| D1.3 | The System will include an agreed set of standardized and parameterized reports. The specifics of these reports will be established during the system design and development activities as described in the Implementation and Performance Non-Functional Requirements. An initial list is provided in FR7 and FR8 tabs. | Required | |
| D1.4 | The System's standard report set will address both the need to ensure all users have a comprehensive, coherent, and streamlined information flow while using the System and that DCYF will meet all the latest DCYF Policies around State and Federal reporting requirements. | Required | |
| D1.5 | The System's reporting and business intelligence capabilities must be scalable to accommodate changes in System scale including changes in user population, transaction volume, throughput and geographical distribution while maintaining the agreed service levels. | Required | |
| D1.6 | The System will have a mechanism to share specific data (e.g. limited data sets, detailed data at the level of the payment recipient but with the data authorized as anonymous and completely de-identified, etc.) in a controllable fashion, compliant with all legal restrictions, with Federal agencies and other State and local agencies. | Required | |
| D1.7 | The System will be extensible and have a scalable data architecture incorporating State and external data as needed to support reporting. | Required | |
| D1.8 | The System will provide user-friendly and streamlined dashboards for all DCYF Workers, Administrators, and Analysts to conduct their roles. | Required | |
| D1.9 | The System will enable authorized users to create, modify and run reports from DEPS data according to defined user access roles. | Required | |
| D1.10 | The System will provide authorized users with the ability to view and generate standard reports and have pre-defined queries that users can choose from, or create a query from the data available, according to defined user access roles. The State will be able to add, remove or modify pre-defined queries. | Required | |
| D1.11 | The System will compile and display query response reports. | Required | |
| D1.12 | The System will provide authorized users with the ability to drill-down through the DEPS data behind reports, according to defined user access roles. | Required | |
| D1.13 | The System will have the capability for a user to select specific metrics and allow drilling down to view more detailed information, where available. | Required | |
| D1.14 | The System will allow the user to configure dashboard preferences and select from a list of available reports to include in the dashboards, based on access rights, roles and reporting needs. | Required | |
| D1.15 | The System will provide authorized users with ability to configure and publish dashboard reports based on user access roles. | Required | |
| D1.16 | The System will display a list of different types of pre-defined reports available to the user, based on the user’s profile and access rights. | Required | |
| D1.17 | The System will display list(s) of different types of reports available, categorized as applicable. Categories may include, but not are limited to: |
a. Administrative
b. Payment recipient based
c. Authorizations (pending, paid, cancelled, flagged)
d. Payments Issued
e. Audit Compliance
f. Fiscal Integrity (Duplicates, Error Logs)
| g. provider specific | Required | ||
| D1.18 | The System will allow the user to select a report from the list. | Required | |
| D1.19 | The System will allow the user to specify one or more applicable report parameters. Parameters may include, but are not limited to: |
a. Time period (e.g., last 30 days, previous month, previous quarter, customized date range, etc.)
b. Payment recipient characteristics (e.g., type, size, affiliation, certifications, etc.)
c. Payment Period (Month of Service in addition to the payment date range)
d. Payments By Program (CW, EL, JR, Admin)
e. Payment by Account Coding
f. Payment by Geography (e.g., zip code, region, county, etc.)
| NOTE: DCYF is open to innovative approaches to parameter selection schemes - the above examples should not constrain whatever the vendor chooses to propose as the most useful. | Required | ||
| D1.20 | The System will allow the user to add the report to a user's dashboard. | Required | |
| D1.21 | The System will display the dashboard reports. | Required | |
| D1.22 | The System will allow the user to specify any applicable parameters while viewing report output, and the System will provide the user with a view of report information based on the specified parameter. | Required | |
| D1.23 | The System will provide the ability for users to filter data and extract the filtered data (including by payment type, provider type, workflow), manipulate the extracted data, and specify the desired format and media of the output. | Required | |
| D1.24 | The System will allow the user to select the option to generate the report once the user is satisfied that all the necessary paramenters and filters have been selected. | Required | |
| D1.25 | The System will display the report on the screen, and provide the ability to export report data (e.g. to Microsoft Excel, text file with comma separated values), or print the report (e.g., PDF format or to printer), if applicable. | Required | |
| D1.26 | The System will allow authorized users with the appropriate access to save reports for future use. | Required | |
| D1.27 | The System will allow authorized users with the appropriate access to create distribution lists for reports, or similar means to sharing reports with a defined set users on a regular basis. | Required | |
| D1.28 | The System will allow authorized users with the appropriate access to save parameters to generate reports for future use and schedule saved reports to be emailed out to DCYF staff user. | Required | |
| D1.29 | The System will generate reports for all outstanding approvals within business processes (e.g., supervisor approvals, case/task assignment approvals, historical chart update approvals) that have not been reviewed by an Authorized User(s) after a pre-determined time duration (e.g., 60 days from request date). The System will send this report to Authorized User(s) for review. | Required |
&"Arial,Regular"&A
&"Arial,Regular"&9&F &"Arial,Regular"&9&P of &N
D2 Querying
| State of Washington Department of Children, Youth, and Families (DCYF) |
| DCYF Enterprise Payment Solution (DEPS) |
| Attachment E: Solution Data & Reporting Requirements Traceability Matrix (RTM) |
| RFP No. 24-DCYF-CW-081 |
Querying
| Req # | Requirement Description | Requirement Priority | Vendor Response: | |
| Y or N | Vendor Response: | |||
| O, C, D, T, F, N | Vendor Proposed Release Date | |||
| (If selecting F) | Vendor Justification for Not Meeting Requirement, if applicable | |||
| (If selecting N) | Additional Comments (Not Required) | |||
| D2.1 | The System will allow authorized users to create queries based on the data and as needed, according to defined user access roles. Querying capabilities may include, but are not limited to: |
a. Joins
b. Unions
c. Comparisons
d. Filtering
e. Conversions
f. Arithmetic functions
| g. Other basic querying functions | Required | ||
| D2.2 | The System will provide a graphical user interface for the user to create queries. | Preferred | |
| D2.3 | The System will display the data based on the queries in a selected reporting format, and allow for query results to be exported. | Required | |
| D2.4 | The System will enable an authorized user (i.e., reporting or analytic specialist) to modify or build on the initial query to further refine report results. | Required | |
| D2.5 | The System will allow a user to save the query for future use. | Required | |
| D2.6 | The System will allow a user to share the query with other users or user groups. | Preferred |
&"Arial,Regular"&A
&"Arial,Regular"&9&F &"Arial,Regular"&9&P of &N
D3 Visualization
| State of Washington Department of Children, Youth, and Families (DCYF) |
| DCYF Enterprise Payment Solution (DEPS) |
| Attachment E: Solution Data & Reporting Requirements Traceability Matrix (RTM) |
| RFP No. 24-DCYF-CW-081 |
Visualization
| Req # | Requirement Description | Requirement Priority | Vendor Response: | |
| Y or N | Vendor Response: | |||
| O, C, D, T, F, N | Vendor Proposed Release Date | |||
| (If selecting F) | Vendor Justification for Not Meeting Requirement, if applicable | |||
| (If selecting N) | Additional Comments (Not Required) | |||
| D3.1 | The System will have the ability to produce charts, graphs, etc. in order to show progress, trends, etc. and provide the option to include a variety of chart and diagram types such as: |
a) Small multiple/trellis charts - allowing for visualization of multiple dimensions
b) Sankey diagrams - depicting flows, and
| c) Network/link charts - to visually show links between data points | Required | |
| D3.2 | The System will support interactive capabilities including but not limited to: |
a) Visual selection (brushing, lasso, range, line or similar),
b) Toggling between value and percentage in charts, and
| c) Visual custom grouping (for use as a new dimension, filter or within a hierarchy) | Preferred | |
| D3.3 | The System will provide authorized users with the appropriate access with the ability to express and analyze map data, such as: |
a) automatic geocoding and rendering of data in map form
b) choropleths and map layering
| c) geospatial algorithms (e.g., for distance and route calculations) | Required | ||
| D3.4 | The System will provide the ability to maintain an overall view of a data set when users are visualizing a subset of it, either by automatically generating an interactive micro chart with a navigation window (using sliders etc.) or via fisheye magnification or similar. | Preferred | |
| D3.5 | The System will support time series animations out of the box with both slider and play/pause buttons supported. | Preferred | |
| D3.6 | The System will provide the ability for the user to view underlying data to a visualization | Required |
&"Arial,Regular"&A
&"Arial,Regular"&9&F &"Arial,Regular"&9&P of &N
D4 Administration & Management
| State of Washington Department of Children, Youth, and Families (DCYF) |
| DCYF Enterprise Payment Solution (DEPS) |
| Attachment E: Solution Data & Reporting Requirements Traceability Matrix (RTM) |
| RFP No. 24-DCYF-CW-081 |
Administration & Management
| Req # | Requirement Description | Requirement Priority | Vendor Response: | |
| Y or N | Vendor Response: | |||
| O, C, D, T, F, N | Vendor Proposed Release Date | |||
| (If selecting F) | Vendor Justification for Not Meeting Requirement, if applicable | |||
| (If selecting N) | Additional Comments (Not Required) | |||
| Data/Report Usage | ||||
| D4.1 | The System will provide administrators with the ability to track user access to various reporting objects (including, but not limited to: Dashboards, Reports, Workspaces, Dimensions, or Measures). In particular, and track features that users employ such as automated insights, charts, or search. | Required | ||
| D4.2 | The System will report detailed and summarized reporting usage data in prebuilt reports and dashboards. | Required | ||
| D4.3 | The System will enable authorized users with the appropriate access with the ability to promote business user generated analytic content (dashboards, workbooks, reports, etc.) out of personal or local development environments and into governed collaborative environments either manually, at the discretion of the user (i.e., reporting or analytic specialist), or using built in workflows. | Preferred | ||
| D4.4 | The System will maintain a comprehensive data catalog to support report development, training and system maintenance. | Required | ||
| Data Catalog | ||||
| D4.5 | The System's data catalog will include definitions of the Databases, Schemas, Tables, Data Elements, Relationships, Dashboards, Reports, Workspaces, Dimensions, and Measures. | Required | ||
| D4.6 | The System's Data Catalog will include comprehensive documentation of each Report's requirements and design, including, but not limited to: |
a. Intended audience or users of the report
b. Report purpose or goal
c. Report format/layout
d. Report data elements, including values retrieved from the DEPS database, provided by other systems, or calculated fields.
e. Selection criteria, such as filters, conditions, sorting, and grouping, whether "hard" coded or user-determined
f. Action triggering report execution, such as: User initiation, A defined schedule of event(s), such as deadlines for investigations, home visits, eligibility determinations, or financial reporting, or System-detected problems, such as missing or inconsistent data, or data not entered in specified timeframes.
g. “Drill down” features to permit users to compare regions/counties/offices/units and to view the case data comprising statistics.
h. Functions to export report/data to different formats (e.g., PDF, Excel, charts, and graphs).
i. Report distribution platform/method and specify how users will access the report
j. Report archival requirements.
| k. Requirements for a data analysis/statistical package for use by skilled analysts and researchers working with DEPS data extracts. | Required | ||
| D4.7 | The System's Data Catalog will enable authorized users to view and edit common definitions of metadata objects such as metric definitions, report descriptions and tags. | Required | |
| D4.8 | The System will generate automated inventories of analytic content including queries, reports, dashboards, selectively based and organized on the metadata available such as role and usage type. | Required | |
| D4.9 | The System will support the user community by allowing users to rate (like/dislike) or feature content, favorite/follow specific users and provide "smart' recommendation of analytic content based on user's activities. | Preferred | |
| D4.10 | The System's Data Catalog will be searchable, including but not limited to the capabilitiy to determine which reports include specified data elements and if a new report requests duplicate existing reports. | Required | |
| D4.11 | The System's Data Catalog will enable system administrators to define analytical data models with metadata objects (such as dimensional attributes, hierarchies, measures, and filters) for reuse of these objects in downstream reports. | Required | |
| D4.12 | The System's Data Catalog will manage and control versions multiple usage of such analytical data models. | Required | |
| Data Quality Support | |||
| D4.13 | The System will include Data Quality tools with the ability to profile, examine, collect statistics or informative summaries about data including, but not limited to: |
a. Data available from an existing information source, without the need to extract or move the data.
b. Data "in flight;" that is, while the data is moving (e.g., streaming or messaging).
| c. Data from potential additional sources | Required | |
| D4.14 | The System's Data Quality Tools will include, but not be limited to: |
a. A range of prebuilt analyses on individual attributes/columns/fields (e.g., minimum, maximum, frequency distributions of values and patterns, and others).
b. A range of prebuilt analyses to identify relationships, patterns, integrity gaps and duplication; for example, between and across multiple attributes/columns/fields and across tables, databases and files.
c. The ability to configure user-defined rules and execute these profiling analyses
| d. The ability to analyze and visualize trends in profiling results over time and analyze when trends in data quality metrics will exceed predefined thresholds | Required | |
| D4.15 | The System's Data Quality tools will include the ability to present profiling results in textual and other report formats, including: |
a. Prebuilt reports and scorecards for exposing profiling results.
b. Prebuilt graphical dashboards presenting profiling results
c. Ability to customize graphical and tabular presentation formats.
| d. Ad hoc and scheduled execution of profiling processes. | Required | ||
| D4.16 | The System's Data Quality tools will include the ability to develop business rules that check for specific quality issues and use these to monitor data quality issues in System databases, and files. | Required | |
| D4.17 | The System's Data Quality tools will generate alerts (e.g., email, texting or logs) if data violates monitoring rules and provide prebuilt and customizable reports that show numbers and types of monitoring results (e.g., rule violations over time). | Required | |
| D4.18 | The System's Data Quality tools will include Prebuilt processes and steps that are used to perform common quality tasks and remediating data quality issues (e.g., providing values for incomplete data, resolving conflicts of duplicate records). | Required | |
| D4.19 | The System's Data Quality tools will provide a user-friendly interface in which data stewards and other non-IT stakeholders can review and manage data quality processes and issues including issue escalation, tracking and assigning issues, and monitoring of the issue resolution. | Required |
&"Arial,Regular"&A
&"Arial,Regular"&9&F &"Arial,Regular"&9&P of &N
File details come from the government source that posted it. Updated .