Attachment K - Traceability Matrix.xlsx
XLSX spreadsheet 139 KB Posted
- Attached to
- FL WINS Customer Portal
- Solicitation number
- ITN-07176
- Issued by
- Leon County, Florida
About this file
This document is the Florida WINS (Workforce Innovation and Opportunity Network Solutions) Requirements Traceability Matrix (RTM), which captures the epic-level requirements needed to help vendors design a high-level solution for the FL WINS Customer Portal project. The RTM is intended to provide guidance on the functionality and capabilities required, while allowing vendors to determine the specific implementation details. The RTM covers requirements across the Portal, Integrated Data Solution, and Customer 360 components of the FL WINS solution. Key requirements include providing customers with a service wizard, common intake form, career navigation tools, notification features, and secure access and data management capabilities. The RTM is aligned with the master service blueprint and future state customer journey phases.
The RTM also includes technical requirements to ensure the FL WINS solution complies with Florida statutes, including provisions related to cloud hosting, security, data governance, and analytics and reporting. The technical requirements cover areas such as infrastructure performance and availability, data provisioning and transformation, identity and access management, and business intelligence and analytics. The solution is intended to serve all Floridians seeking workforce services, with a focus on integrating data and functionality across the Department of Children and Families, Department of Education, CareerSource Florida, and other workforce agency partners.
View the file
Other files
Show all 24
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
Instructions Attachment K - FL WINS Requirements Traceability
Functional FL WINS Requirements Traceability Matrix The FL WINS Requirements Traceability Matrix (RTM) captures epic-level requirements needed to help vendors design a high-level solution. The RTM is not intended to provide lower-level requirements in order to allow future solution vendors to determine how the functionality will be implemented at their discretion. Each requirement listed in the RTM is tied to a capability and a feature to group requirements based on the areas of functionality the requirement is associated with. Solution vendors will elaborate on the feature-level requirements to identify lower-level requirements that fit their solution and delivery methodology. To reference a representative visualization of the future FL WINS solution, please see section 5 of the Target Operating Model (TOM) to view potential solution wireframes. Note, the wireframes in the TOM are not the solution for FL WINS but a visualized representation of a portion of the components and features that will make the Master Service Blueprint possible. This RTM is a living 'document', for reference,For reference, the Master Service Blueprint can be found in section 2 of the TOM.
| ID | |
| Abhinav Chawla: Unique ID number used to identify the item in the RTM. | ReqID |
| Abhinav Chawla: Unique identifier for each requirement, identifying which component it belongs to and the requirement number. | Solution Component |
| Abhinav Chawla: Identifies application area in the solution. Includes Portal, Integrated Data Solution, and Customer 360. | Priority |
| Abhinav Chawla: Provides a mechanism to identify if the requirement is a ‘Must-Have' or ‘Nice-to-Have' | Capability |
| Abhinav Chawla: Capabilities are units of functionality broken down from the Solution Components to address the major pain points identified through discovery. | Feature |
| Abhinav Chawla: Features are smaller units of functionality that are nested within capabilities. | Requirement Type |
| Abhinav Chawla: Identifies if the Requirement is Technical or Functional in nature | Journey Phase |
| Abhinav Chawla: Identifies the future state journey phase attached to the solution, aligned to the master service blueprint. | Implementation Phase |
| Abhinav Chawla: Identifies the implementation phase for an iterative approach | Requirement |
| Abhinav Chawla: Captures how a product, system, or service must behave to fulfill a specific customer need | Evidence |
| Abhinav Chawla: Provides traceability to the identification of the pain point that led to the creation of the requirement | Legislation |
| Abhinav Chawla: Provides traceability to applicable Florida Statutes or Program's Authority | Requirement is met by: |
| Schaffer, Jacquelyn: Reference Tab #1 for instructions | Explanation or Comments |
Schaffer, Jacquelyn: Reference Tab #1 for instructions
| 103 | REQ-C360-03 | Customer 360 | Nice to Have | Analytics | Risk Indicator | Functional | Across Phases | Phase 4 | The customer 360 portal shall provide agency staff with the customer's risk score which illustrates the customer's potential for misuse of programs and/or services | This requirement was created to address staff needs to identify cases of potential risk, as heard in the Art of the Possible sessions. | F.S. 445.009; 445.010; 445.011 |
| 104 | REQ-C360-04 | Customer 360 | Nice to Have | Analytics | Risk Indicator | Functional | Across Phases | Phase 4 | The agency staff's manager shall be able to view case worker's risk score based on assigned roles | This requirement was created to address staff needs to identify cases of potential risk, as heard in the Art of the Possible sessions. | F.S. 445.009; 445.010; 445.011 |
| 105 | REQ-C360-05 | Customer 360 | Nice to Have | Analytics | Need Scoring | Functional | Across Phases | Phase 5 | The customer 360 portal shall provide agency staff with the customer's need score which illustrates the customer's potential risk of falling into severe circumstances such as hunger or homelessness | This requirement was created to address staff needs to identify customers in need of wrap-around services, as heard in the Art of the Possible sessions. | F.S. 445.009; 445.010; 445.011 |
| 106 | REQ-C360-06 | Customer 360 | Must Have | Cross Program Data View | Notification Center | Functional | Across Phases | Phase 2 | The customer 360 portal shall have the ability to send notification messages to the customer dashboard, the customer 360 view as well as send a push notification to the existing case management system. | This requirement was created to address staff communication with customers selecting between receiving notifications through the dashboard, texts, and emails, as heard in the Art of the Possible sessions. | F.S. 445.009; 445.010; 445.011 |
| 107 | REQ-C360-07 | Customer 360 | Nice to Have | Cross Program Data View | Notification Center | Functional | Across Phases | Phase 2 | The customer 360 portal shall have shared calendar view for agency staff by location | This requirement was created to allow because agency staff need to communicate their availability to customers through the portal, as heard in the Art of the Possible sessions and documented in Robert and Maryanne's To-Be journeys. | F.S. 445.009; 445.010; 445.011 |
| 108 | REQ-C360-08 | Customer 360 | Must Have | Profile | Notification Center | Functional | Across Phases | Phase 5 | The customer 360 portal shall provide a shared notes feature for cross-agency staff communication | This requirement was created to allow because agency staff need to communicate notes about their customers with other agency staff in order to provide appropriate services, as documented in Robert's To-Be journey. | F.S. 445.009; 445.010; 445.011 |
| 109 | REQ-C360-09 | Customer 360 | Nice to Have | Common Intake Form | Pre-populate information | Functional | Application/Eligibility | Phase 2 | The customer 360 portal shall allow the agency staff to scan a paper application and any supporting documentationelectronically populate the common intake form without needing to manually enter information | This requirement was created to address agency resource consumption by manually entering customer information as heard in the Art of the Possible sessions, DCF programmatic validation sessions, and DCF ride along sessions. | F.S. 445.009; 445.010; 445.011 |
| 110 | REQ-C360-10 | Customer 360 | Must Have | Cross Program Data View | Profile View | Functional | Across Phases | Phase 2 | The customer 360 portal shall have the ability for agency staff to view customer profile data | This requirement was created because agency staff need secure access to information to serve their customers, as heard in Art of the Possible sessions and agency validation sessions. | F.S. 445.009; 445.010; 445.011 |
| 111 | REQ-C360-11 | Customer 360 | Nice to Have | Cross Program Data View | Program View | Functional | Across Phases | Phase 2 | The customer 360 portal shall provide agency staff with a view into a customer's current programs by status | The requirement was created to address the agency staff's need to track customer actions to take for current programs they are participating in, as documented in the Art of the Possible sessions and Cindy's To-Be journey. | F.S. 445.010; F.S. 445.011(1)(a) |
| 112 | REQ-C360-12 | Customer 360 | Nice to Have | Recommendation Engine | Referrals | Functional | Across Phases | Phase 3 | The customer 360 portal shall provide agency staff with ability to suggest additional services and programs | This requirement was created to address the agency staff's need to identify services across agencies their customer may benefit from, as heard in the Art of the Possible sessions. | F.S. 445.011(1)(a) |
| 113 | REQ-C360-13 | Customer 360 | Must Have | Recommendation Engine | Referrals | Functional | Across Phases | Phase 3 | The customer 360 portal shall allow agency staff to submit electronic referrals to different programs across different agencies | This requirement was created to address the agency staff's need to refer customers to services across agencies, as heard in the Art of the Possible sessions and documented in Robert and Maryanne's To-Be journeys. | F.S. 445.010 |
| 114 | REQ-C360-14 | Customer 360 | Must Have | Service Catalog | Resource Hub | Functional | Across Phases | Phase 2 | The customer 360 portal shall provide agency staff with optimized searchability and access to program and service information, including eligibility criteria and information requirements for all the programs under FL WINS | This requirement was created to address the agency staff's need to identify services across agencies their customer may benefit from, as heard in the Art of the Possible sessions. | F.S. 445.010 |
| 115 | REQ-C360-15 | Customer 360 | Nice to Have | Cross Program Data View | Scheduling Tool | Functional | Across Phases | Phase 3 | The customer 360 portal shall have the ability to allow agency staff to schedule, update, and cancel new appointments with their assigned customers | This requirement was created to accommodate agency staff to easily coordinate and attend appointments, as heard in ride along sessions and documented in Maryanne, Robert, and Vince's To-Be Journey. | F.S. 445.009; 445.010; 445.011 |
| 116 | REQ-C360-16 | Customer 360 | Must Have | Profile | Service History | Functional | Across Phases | Phase 2 | The customer 360 portal shall provide a view into a 'activity history' section for assigned customers | The requirement was created to address the agency staff's need to track customer activity on the portal, as documented in the Art of the Possible sessions. | F.S. 445.009; 445.010; 445.011 |
| 117 | REQ-C360-17 | Customer 360 | Nice to Have | Profile | Service History | Functional | Across Phases | Phase 2 | The customer 360 portal shall provide agency staff with access to a customer's service history | The requirement was created to address the agency staff's need to track customer service history across agencies, as documented in the Art of the Possible sessions. | F.S. 445.010; 445.011(1)(a) |
| 100 | REQ-P-100 | Portal | Nice to Have | Dashboard | Scheduling Tool | Functional | Application/Eligibility | Phase 4 | The portal shall have the ability to allow customers to cancel, update, and schedule a new appointment selecting from available time slots with the assigned agency staff and other relevant individuals | This requirement was created to accommodate customers and agency staff to easily coordinate and attend appointments, as heard in ride along sessions and documented in Cindy, Robert, and Maryanne's To-Be Journey. | F.S. 445.009; 445.010; 445.011 |
| REQ-P-101 | Portal | Nice to Have | Service Wizard | Core Service Wizard | Functional | Service Discovery | Phase 1 | The service wizard shall implement dynamic questioning to adapt and personalize questions based on user responses, preferences, and newly acquired information, enhancing engagement and improving accuracy of potentially eligible programs/services. | Based on Gartner's experience, this is a common feature in wizard functionality | F.S. 445.009; 445.010; 445.011 | |
| REQ-P-102 | Portal | Must Have | Common Intake Form | Paper Application | Functional | Application/Eligibility | Phase 2 | The portal shall allow customers to submit the common intake form to the appropriate workforce partner agency system depending on the programs/services. | This requirement was created to match the technical requirement REQ-DS-15. | F.S. 445.009; 445.010; 445.011 | |
| 33 | REQ-P-33 | Portal | Nice to Have | Virtual Assistant | FAQs | Functional | Application/Eligibility | Phase 1 | The portal shall provide a virtual assistant to respond to frequently asked questions | This requirement was created to provide customers with an alternative channel to receive support and answer questions they may have, as heard in Art of the Possible sessions and the CareerSource Florida Jacksonville ride along session. | F.S. 445.009; 445.010; 445.011 |
| 34 | REQ-P-34 | Portal | Nice to Have | Virtual Assistant | Live Chat | Functional | Application/Eligibility | Phase 2 | The portal shall provide an automated chatbot to allow customer to connect to a live representative | This requirement was created to provide customers with an alternative channel to receive support and answer questions they may have, as heard in Art of the Possible sessions and the CareerSource Florida Jacksonville ride along session. | F.S. 445.009; 445.010; 445.011 |
| 35 | REQ-P-35 | Portal | Nice to Have | Virtual Assistant | Personalized Experience | Functional | Application/Eligibility | Phase 3 | The portal shall allow for a customer's selection preference of live vs chat bot assistance | This requirement was created to provide customers to select their preference for receiving support via live chat or chatbot, as heard in Art of the Possible sessions and the CareerSource Florida Jacksonville ride along session. | F.S. 445.009; 445.010; 445.011 |
| 36 | REQ-P-36 | Portal | Nice to Have | Service Catalog | Location Finder | Functional | Application/Eligibility | Phase 1 | The customer dashboard shall have a 'around me' tool section to allow customers to search for nearby physical locations of LWDB/CSF offices | This requirement was created to assist customers in locating physical CareerSource Florida locations near them, as documented in Adrian's To-Be Journey. | F.S. 445.009; 445.010; 445.011 |
| 37 | REQ-P-37 | Portal | Nice to Have | Service Catalog | Location Finder | Functional | Application/Eligibility | Phase 1 | The customer dashboard shall have a 'around me' tool section to allow customers to search for nearby jobs | This requirement was created to assist customers in locating jobs near them, as documented in Adrian's To-Be Journey. | F.S. 445.011(1)(b)1-2 |
| 38 | REQ-P-38 | Portal | Nice to Have | Service Catalog | Location Finder | Functional | Application/Eligibility | Phase 1 | The customer dashboard shall have a 'around me' tool section to allow customers to search for nearby classes | This requirement was created to assist customers in locating classes near them, as documented in Adrian's To-Be Journey. | F.S. 445.011(1)(b)3 |
| 39 | REQ-P-39 | Portal | Nice to Have | Service Catalog | Location Finder | Functional | Application/Eligibility | Phase 1 | The customer dashboard shall have a 'around me' tool section to allow customers to search for nearby colleges | This requirement was created to assist customers in locating colleges near them, as documented in Adrian's To-Be Journey. | F.S. 445.011(1)(b)3 |
| 40 | REQ-P-40 | Portal | Nice to Have | Service Catalog | Location Finder | Functional | Application/Eligibility | Phase 1 | The customer dashboard shall have a 'around me' tool section to allow customers to search for nearby in-demand fields and skills | This requirement was created to assist customers in locating in-demand fields and skills near them, as documented in Adrian's To-Be Journey. | F.S. 445.011(1)(b)1-2 |
| 41 | REQ-P-41 | Portal | Nice to Have | Service Catalog | Location Finder | Functional | Application/Eligibility | Phase 1 | The customer dashboard shall have a 'around me' tool section to allow customers to search for nearby board locations | This requirement was created to assist customers in locating boards near them, as documented in Adrian's To-Be Journey. | F.S. 445.011(1)(b)3 |
| 42 | REQ-P-42 | Portal | Must Have | Service Catalog | Resource Hub | Functional | Plan Creation | Phase 1 | The portal shall contain knowledge management capability to enable customers to access relevant information and articles that contain programs and services. | This requirement was created because customers have identified a need for an efficient way to search for information about programs and services, as documented in Maryanne the Mother's To-Be Journey. | F.S. 445.009(1)(c) |
| 43 | REQ-P-43 | Portal | Nice to Have | Service Catalog | Resource Hub | Functional | Plan Creation | Phase 1 | The portal shall include search capability that allows customers to find support groups or similar community organization | This requirement was created because customers have identified a need for an efficient way to search for support groups to connect with other customers on a similar journey, as heard in the Art of the Possible sessions. | F.S. 445.011(1)(b)3 |
| 44 | REQ-P-44 | Portal | Must Have | Service Wizard | Core Service Wizard | Functional | Service Discovery | Phase 1 | The service wizard shall have a basic information section | This requirement was created because customers need to identify programs and services they may be eligible for without applying for them, as heard in the Art of the Possible sessions and documented in the Adrian's To-Be Journeys. | F.S. 445.009; 445.010; 445.011 |
| 45 | REQ-P-45 | Portal | Must Have | Service Wizard | Core Service Wizard | Functional | Service Discovery | Phase 1 | The service wizard shall have a financial information section | This requirement was created because customers need to identify programs and services they may be eligible for without applying for them, as heard in the Art of the Possible sessions and documented in the Adrian's To-Be Journeys. | F.S. 445.011(1)(a)1-2 |
| 46 | REQ-P-46 | Portal | Must Have | Service Wizard | Core Service Wizard | Functional | Service Discovery | Phase 1 | The service wizard shall have a goals section | This requirement was created because customers need to identify programs and services they may be eligible for without applying for them, as heard in the Art of the Possible sessions and documented in the Adrian's To-Be Journeys. | F.S. 445.009(1)(b) |
| 47 | REQ-P-47 | Portal | Must Have | Service Wizard | Core Service Wizard | Functional | Service Discovery | Phase 1 | The service wizard shall have a challenges section to indicate challenges may prevent a customer's successful outcome. | This requirement was created because customers need to identify programs and services they may be eligible for without applying for them, as heard in the Art of the Possible sessions and documented in the Adrian's To-Be Journeys. | F.S. 445.009; 445.010; 445.011 |
| 48 | REQ-P-48 | Portal | Must Have | Service Wizard | Core Service Wizard | Functional | Service Discovery | Phase 1 | The service wizard shall have a results section listing programs and services the customer may be eligible for. | This requirement was created because customers need to identify programs and services they may be eligible for without applying for them, as heard in the Art of the Possible sessions and documented in the Adrian's To-Be Journeys. | F.S. 445.009(9)(b) |
| 49 | REQ-P-49 | Portal | Must Have | Service Wizard | Core Service Wizard | Functional | Service Discovery | Phase 1 | The service wizard shall provide the customer with links to all the services from the Service Catalog they qualify for with associated success outcomes on the results page | This requirement was created because customers need to identify programs and services they may be eligible for without applying for them, as heard in the Art of the Possible sessions and documented in the Adrian's To-Be Journeys. | F.S. 445.009(9)(b) |
| 50 | REQ-P-50 |
tc={996E1E82-20B6-46F9-A370-2F4352020C03}: [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:
Included Gartner 'new' requirement for being anonymously Abhinav Chawla: Identifies if the Requirement is Technical or Functional in nature Abhinav Chawla: Identifies the future state journey phase attached to the solution, aligned to the master service blueprint.
Abhinav Chawla: Identifies the implementation phase for an iterative approach Abhinav Chawla: Captures how a product, system, or service must behave to fulfill a specific customer need Abhinav Chawla: Provides traceability to the identification of the pain point that led to the creation of the requirement Abhinav Chawla: Provides traceability to applicable Florida Statutes or Program's Authority Schaffer, Jacquelyn: Reference Tab #1 for instructions Schaffer, Jacquelyn: Reference Tab #1 for instructions
| Portal | Must Have | Service Wizard | Core Service Wizard | Functional | Service Discovery | Phase 1 | The customer shall be able to navigate to the qualified services information page without saving the results, being accessible anonymously | This requirement was created because customers need to identify programs and services they may be eligible for without applying for them, as heard in the Art of the Possible sessions and documented in the Adrian's To-Be Journeys. | F.S. 445.009; 445.010; 445.011 | |||
| 51 | REQ-P-51 | Portal | Nice to Have | Service Wizard | Core Service Wizard | Functional | Service Discovery | Phase 1 | The customer shall have the ability to view the results of the service match send the results of the of the service match to him/herself (via. Text, email and or QR code) | This requirement was created because customers need to identify programs and services they may be eligible for without applying for them, as heard in the Art of the Possible sessions and documented in the Adrian's To-Be Journeys. | F.S. 445.009; 445.010; 445.011 | |
| 52 | REQ-P-52 | Portal | Nice to Have | Service Wizard | QR Code Generator | Functional | Service Discovery | Phase 1 | The QR code shall be deactivated after 30 days from the date customer went through service match | This requirement was created to protect customer information accessible through the QR code, as heard in the Art of the Possible sessions and Adrian's To-Be Journey. | F.S. 445.009; 445.010; 445.011 | |
| 53 | REQ-P-53 | Portal | Nice to Have | Service Wizard | QR Code Generator | Functional | Service Discovery | Phase 2 | The agency staff shall have the ability to scan the QR code to populate the common intake form for the customer | This requirement was created to address agency resource consumption by manually entering customer information as heard in the Art of the Possible sessions and documented in Adrian's To-Be Journey. | F.S. 445.009; 445.010; 445.011 | |
| 54 | REQ-P-54 | Portal | Nice to Have | Benefit forecasting tool | Benefits estimator | Functional | Application/Eligibility | Phase 1 | The customer dashboard shall have a benefits estimator section estimating amount of benefits based on federal guidelines | This requirement was created to address the customers inability to estimate their future benefits before applying as heard in the Art of the Possible sessions and documented in Adrian's To-Be Journey. | F.S. 445.011(1)(a) | |
| 55 | REQ-P-55 | Portal | Must Have | Career Navigator | Career Plan | Functional | Application/Eligibility | Phase 3 | The portal shall have the ability to track progress towards stated customer goals within the profile | The requirement was created to address the customer's need to track their actions to take to meet their goals, as documented in Cindy's To-Be Journeys. | F.S. 445.009; 445.010; 445.011 | |
| 56 | REQ-P-56 | Portal | Nice to Have | Career Navigator | Career Wizard | Functional | Service Discovery | Phase 1 | The portal shall have an integrated career aptitude assessment for customers to anonymously help find careers that matches their skills, or be compatible with Workforce Partner existing or future career aptitude assessment solutions. | The requirement was created to address the customer's need to identify careers that match their skills and interests prior to applying to jobs or training, as documented in Art of the Possible sessions and Willie's To-Be Journeys. | F.S. 445.011(1)(b)1 | |
| 57 | REQ-P-57 | Portal | Must Have | Career Navigator | Career Wizard | Functional | Application/Eligibility | Phase 2 | The portal shall allow the customers to save their Career Aptitude assessment in the Career Navigator results in their profile and view any historic data related to assessments. | The requirement was created to address the customer's need to save careers that match their skills and interests prior to applying to jobs or training, as documented in Art of the Possible sessions and Willie's To-Be Journeys. | F.S. 445.011(1)(b)1 | |
| 58 | REQ-P-58 | Portal | Must Have | Career Navigator | Career Plan | Functional | Plan Creation | Phase 5 | The portal shall have a career plan builder utilizing a questionnaire that allows Customers to generate a custom plan with milestones, based on their interests and goals. | The requirement was created to address the customer's need of understanding requirements and milestones for their desired career path, as heard in the Art of the Possible sessions. | ||
| Possible implementation opportunities include a questionnaire which captures the customer's level of engagement and interest in pursuing different types of careers, then building a corresponding roadmap to include requirements and milestones to achieve their goal. | F.S. 445.009(1)(b) | |||||||||||
| 59 | REQ-P-59 | Portal | Nice to Have | Career Navigator | Find a Job | Functional | Application/Eligibility | Phase 1 | The portal shall display data (such as number of people currently working, unemployment rate, average salary, remote workers, Veteran Preference, etc.) about in-demand jobs from EmployFlorida | This requirement was created to address the customer's need to efficiently search for in demand jobs and relay the information, as documented in Adrian's To-Be Journeys. | F.S. 445.011(1)(b)1-2 | |
| 60 | REQ-P-60 | Portal | Nice to Have | Career Navigator | Find a Job | Functional | Service Discovery | Phase 2 | The portal shall allow customers to save jobs to a list for future reference | This requirement was created to address the customer's need to efficiently search for in demand jobs and save the information, as documented in Adrian's To-Be Journeys. | F.S. 445.011(1)(b)1-2 | |
| 61 | REQ-P-61 | Portal | Must Have | Common Intake Form | Ability to Save | Functional | Application/Eligibility | Phase 2 | The common intake form shall have a save feature to capture information entered and return to it at a later time | This requirement was created to address the customer's need of reducing duplicate data entry across multiple applications when applying for programs and services, as heard in the DCF discovery sessions, ride along sessions, and Art of the Possible Sessions. Customers spend significant time filling out the same basic information on different applications. The process is frustrating and confusing. | F.S. 445.010(1)(g) | |
| 62 | REQ-P-62 | Portal | Must Have | Common Intake Form | Categories of Information | Functional | Application/Eligibility | Phase 2 | The common intake form shall have a profile information section with mandatory and optional fields clearly marked. | This requirement was created to address the customer's need of reducing duplicate data entry across multiple applications when applying for programs and services, as heard in the DCF discovery sessions, ride along sessions, and Art of the Possible Sessions. Customers spend significant time filling out the same basic information on different applications. The process is frustrating and confusing. | F.S. 445.011(1)(a) | |
| 63 | REQ-P-63 | Portal | Must Have | Common Intake Form | Categories of Information | Functional | Application/Eligibility | Phase 2 | The common intake form shall have a education information section with mandatory and optional fields clearly marked. | This requirement was created to address the customer's need of reducing duplicate data entry across multiple applications when applying for programs and services, as heard in the DCF discovery sessions, ride along sessions, and Art of the Possible Sessions. Customers spend significant time filling out the same basic information on different applications. The process is frustrating and confusing. | F.S. 445.011(1)(a) | |
| 64 | REQ-P-64 | Portal | Nice to Have | Common Intake Form | Categories of Information | Functional | Application/Eligibility | Phase 2 | The common intake form shall have a work experience section with mandatory and optional fields clearly marked. | This requirement was created to address the customer's need of reducing duplicate data entry across multiple applications when applying for programs and services, as heard in the DCF discovery sessions, ride along sessions, and Art of the Possible Sessions. Customers spend significant time filling out the same basic information on different applications. The process is frustrating and confusing. | F.S. 445.011(1)(a) | |
| 65 | REQ-P-65 | Portal | Must Have | Common Intake Form | Categories of Information | Functional | Application/Eligibility | Phase 2 | The common intake form shall have a financial information section with mandatory and optional fields clearly marked. | This requirement was created to address the customer's need of reducing duplicate data entry across multiple applications when applying for programs and services, as heard in the DCF discovery sessions, ride along sessions, and Art of the Possible Sessions. Customers spend significant time filling out the same basic information on different applications. The process is frustrating and confusing. | F.S. 445.011(1)(a) | |
| 66 | REQ-P-66 | Portal | Nice to Have | Common Intake Form | Categories of Information | Functional | Application/Eligibility | Phase 2 | The common intake form shall have a medical information section with mandatory and optional fields clearly marked. | This requirement was created to address the customer's need of reducing duplicate data entry across multiple applications when applying for programs and services, as heard in the DCF discovery sessions, ride along sessions, and Art of the Possible Sessions. Customers spend significant time filling out the same basic information on different applications. The process is frustrating and confusing. | F.S. 445.011(1)(a) | |
| 67 | REQ-P-67 | Portal | Nice to Have | Common Intake Form | Categories of Information | Functional | Application/Eligibility | Phase 2 | The common intake form shall have a workforce goals section with mandatory and optional fields clearly marked. | This requirement was created to address the customer's need of reducing duplicate data entry across multiple applications when applying for programs and services, as heard in the DCF discovery sessions, ride along sessions, and Art of the Possible Sessions. Customers spend significant time filling out the same basic information on different applications. The process is frustrating and confusing. | F.S. 445.011(1)(a) | |
| 68 | REQ-P-68 | Portal | Must Have | Common Intake Form | Categories of Information | Functional | Application/Eligibility | Phase 2 | The common intake form shall have a supporting documentation section. | This requirement was created to address the customer's need of reducing duplicate document submission across multiple systems when applying for programs and services, as heard in the DCF discovery sessions, ride along sessions, and Art of the Possible Sessions. | F.S. 445.011(1)(a) | |
| 69 | REQ-P-69 | Portal | Must Have | Common Intake Form | Categories of Information | Functional | Application/Eligibility | Phase 2 | The common intake form shall provide content explaining the importance of optional fields which will help customer expedite their application process and provide additional benefit eligibility | This requirement was created to address the customer's need of reducing data requests and touchpoints with agency staff, as heard in the DCF discovery sessions, ride along sessions, and Art of the Possible Sessions. | F.S. 445.010(2) | |
| 70 | REQ-P-70 | Portal | Nice to Have | Common Intake Form | Categories of Information | Functional | Application/Eligibility | Phase 2 | The common intake form shall have a criminal record section providing only information that would be public record | This requirement was created to address the customer's need of providing information to inform staff of potential impact to eligibility due to justice involvement, as heard in the DCF discovery sessions, ride along sessions, and Art of the Possible Sessions. | F.S. 445.010(2) | |
| 71 | REQ-P-71 | Portal | Nice to Have | Common Intake Form | Dynamic Questioning | Functional | Application/Eligibility | Phase 2 | The common intake form shall implement dynamic questioning to adapt and personalize questions based on user responses, preferences, and newly acquired information, enhancing engagement and improving data collection accuracy | This requirement was created to address the customer's need of reducing the amount of questions not applicable to their application, as heard in the Art of the Possible Sessions. | F.S. 445.009(6)(a)2 | |
| 72 | REQ-P-72 | Portal | Must Have | Common Intake Form | Electronic Signature | Functional | Application/Eligibility | Phase 2 | The common intake form shall have a declaration section, meaning I certify the information is factual and complete. | This requirement was created to address the customer's need of reducing duplicate data entry across multiple applications when applying for programs and services, as heard in the DCF discovery sessions, ride along sessions, and Art of the Possible Sessions. | F.S. 445.010(2) | |
| 73 | REQ-P-73 | Portal | Must Have | Common Intake Form | Electronic Signature | Functional | Application/Eligibility - Plan Creation | Phase 2 | The portal shall allow the customers to electronically sign documents | This requirement was created to address the customer's need of signing electronically rather than providing physical copies of their signature, as heard in the CareerSource Florida ride along sessions. | F.S. 445.009; 445.010; 445.011 | |
| 74 | REQ-P-74 | Portal | Must Have | Common Intake Form | Offline Application | Functional | Application/Eligibility | Phase 2 | The common intake form shall have an offline version that customers can download, complete and upload to the portal to submit to the appropriate workforce partner agency's in-scope system. | This requirement was created to address customer's connectivity issues, as documented in Adrian's To-Be Journey. | F.S. 445.010(1)(g) | |
| 75 | REQ-P-75 | Portal | Nice to Have | Common Intake Form | Paper Application | Functional | Application/Eligibility | Phase 2 | The common intake form shall have a paper application format designed with a user-friendly layout, clear instructions, and sufficient space for customers to provide all necessary information legibly | This requirement was created to address customer's resource needs, as heard in the Art of the Possible sessions. | F.S. 445.009; 445.010; 445.011 | |
| 76 | REQ-P-76 | Portal | Nice to Have | Common Intake Form | Paper Application | Functional | Application/Eligibility | Phase 2 | The paper application shall include a checklist of required documents and be easily accessible to all potential customers, ensuring inclusivity and ease of completion | This requirement was created to address customer's resource needs, as heard in the Art of the Possible sessions. | F.S. 445.009; 445.010; 445.011 | |
| 77 | REQ-P-77 | Portal | Nice to Have | Common Intake Form | Pre-populate information | Functional | Application/Eligibility | Phase 2 | The common intake form shall be able to be prepopulated with previously submitted customer information that exists in the data solution. | This requirement was created to address agency resource consumption by manually entering customer information, as heard in the DCF programmatic validation sessions, DCF ride along sessions, and Art of the Possible sessions. | F.S. 445.010 | |
| 78 | REQ-P-78 | Portal | Must Have | IAM/Profile | User Profile | Functional | Application/Eligibility | Phase 2 | The portal shall provide a user-friendly interface for customers to create their profiles | This requirement was created to increase engagement with the solution, as documented in the To-Be Journeys. | F.S. 445.009; 445.010; 445.011 | |
| 79 | REQ-P-79 | Portal | Must Have | IAM/Profile | User Profile | Functional | Application/Eligibility | Phase 2 | The portal shall allow the customer to update their login password, reset login password, and allow them to deactivate/close their account | This requirement was created to address the customer's need to reset their password without assistance, as heard in the Art of the Possible sessions. | F.S. 445.009; 445.010; 445.011 | |
| 80 | REQ-P-80 | Portal | Must Have | IAM/Profile | User Profile | Functional | Application/Eligibility | Phase 2 | The portal shall have the ability for customer to view, edit, and print their profile information | This requirement was created to address the customer's need to manage their profile without assistance, as heard in the Art of the Possible sessions. | F.S. 445.009; 445.010; 445.011 | |
| 81 | REQ-P-81 | Portal | Must Have | IAM/Profile | User Profile | Functional | Application/Eligibility | Phase 2 | The portal shall allow a verified third party to submit an application on customer's behalf | This requirement was created to address the customer's need to manage their profile while seeking assistance, as heard in the Art of the Possible sessions. | F.S. 445.009; 445.010; 445.011 | |
| 82 | REQ-P-82 | Portal | Must Have | IAM/Profile | Notification Center | Functional | Application/Eligibility | Phase 2 | The portal shall periodically prompt customers to review and update personal information | This requirement was created to address the customer's need to manage their profile without assistance, as documented in Willie's To-Be Journey. | F.S. 445.009; 445.010; 445.011 | |
| 83 | REQ-P-83 | Portal | Must Have | IAM/Profile | User Profile | Functional | Application/Eligibility | Phase 2 | The portal shall provide the ability to capture user's consent to data sharing | This requirement was created to address the customer's need to share information across agencies, as documented in Adrian's To-Be Journey. | F.S. 445.010(2) | |
| 84 | REQ-P-84 | Portal | Nice to Have | Dashboard | Claim Activity | Functional | Application/Eligibility | Phase 4 | The customer dashboard shall allow the customer to view claim activity | This requirement was created to address the customer's need to view their claim activity, as documented in the Art of the Possible Session. | F.S. 445.009(1)(j) | |
| 85 | REQ-P-85 | Portal | Nice to Have | Dashboard | Service History | Functional | Application/Eligibility | Phase 4 | The customer dashboard shall allow the customer to view their service history | This requirement was created to address the customer's need to view their service history, as documented in the Art of the Possible Session. | F.S. 445.009(1)(j) | |
| 86 | REQ-P-86 | Portal | Must Have | Dashboard | Communication Preferences | Functional | Application/Eligibility | Phase 3 | The portal shall have the ability for a customer to select and update communication preferences in their profile online | This requirement was created to address the customer's need to view their claim activity, as documented in the Art of the Possible Session. | F.S. 445.009; 445.010; 445.011 | |
| 87 | REQ-P-87 | Portal | Must Have | Dashboard | Communication Preferences | Functional | Application/Eligibility | Phase 3 | The portal shall have the ability for a customer to call the support desk and upon successful identity verification, select and update communication preferences in their profile | This requirement was created because customers may miss important notifications because they are unable to select their communication preference. Customers would benefit from the opportunity to select between texts, emails, phone, or mail. | F.S. 445.009; 445.010; 445.011 | |
| 88 | REQ-P-88 | Portal | Must Have | Dashboard | Communication Preferences | Functional | Application/Eligibility | Phase 3 | The portal shall have the ability for a customer to opt-out of notifications | This requirement was created because customers may not want to receive notifications, as documented in the TO-Be journeys. | F.S. 445.009; 445.010; 445.011 | |
| 89 | REQ-P-89 | Portal | Must Have | Dashboard | Communication Preferences | Functional | Application/Eligibility | Phase 3 | The portal shall have the ability to send and receive notification messages to the customer dashboard, email, and text | This requirement was created because customers would benefit from the opportunity to select between receiving notifications through the dashboard, texts, and emails, as heard in the Art of the Possible sessions. | F.S. 445.009; 445.010; 445.011 | |
| 90 | REQ-P-90 | Portal | Nice to Have | Dashboard | Cumulative benefits | Functional | Application/Eligibility | Phase 4 | The customer dashboard shall have a benefits calculator section to allow for personalized calculation of benefits for enrolled program | This requirement was created to address the customers inability to track their current benefits, as heard in the Art of the Possible sessions and documented in Adrian's To-Be Journey. | F.S. 445.011(1)(a) | |
| 91 | REQ-P-91 | Portal | Must Have | Dashboard | Document Center | Functional | Application/Eligibility | Phase 4 | The portal shall have the ability to upload, remove and send documents to specific programs | This requirement was created to address the customer's need of reducing duplicate document submission across multiple systems when applying for programs and services, as heard in the DCF discovery sessions, ride along sessions, and Art of the Possible Sessions. | F.S. 445.010 | |
| 92 | REQ-P-92 | Portal | Nice to Have | Dashboard | Notification Center | Functional | Application/Eligibility | Phase 3 | The portal shall have an announcement section to allow customers to view any new notification since the last time they had logged on and take action on that task | This requirement was created because customers may miss important updates from the last time they logged on, as heard in the Art of the Possible sessions. | F.S. 445.009; 445.010; 445.011 | |
| 93 | REQ-P-93 | Portal | Nice to Have | Dashboard | Notification Center | Functional | Application/Eligibility | Phase 3 | The portal shall have an announcement section that prompts customers to update/validate their plans if their last login was more than 90 days | This requirement was created to address the customer's need to manage their profile without assistance, as documented in the Art of the Possible sessions. This will also allow for validation of the information on their profile. | F.S. 445.010(1)(f) | |
| 94 | REQ-P-94 | Portal | Nice to Have | Dashboard | Notification Center | Functional | Application/Eligibility | Phase 3 | The portal shall allow the customer to land on their profile page upon clicking the update/validate personal information notification | This requirement was created to address the customer's need to manage their profile without assistance, as documented in the Art of the Possible sessions. This will also allow for validation of the information on their profile. | F.S. 445.009; 445.010; 445.011 | |
| 95 | REQ-P-95 | Portal | Nice to Have | Dashboard | Notification Center | Functional | Application/Eligibility | Phase 4 | The portal shall allow the customer to take actions on their pending tasks as outlined in notifications | This requirement was created to address the customer's need to manage their profile without assistance, as documented in the Art of the Possible sessions. | F.S. 445.009; 445.010; 445.011 | |
| 96 | REQ-P-96 | Portal | Must Have | Dashboard | Program At A Glance Tile | Functional | Application/Eligibility | Phase 3 | The portal shall prompt users with a list of documents needed to complete their application | This requirement was created to address the customer's need of reducing data requests and touchpoints with agency staff, as heard in the DCF discovery sessions, ride along sessions, and Art of the Possible Sessions. | F.S. 445.009; 445.010; 445.011 | |
| 97 | REQ-P-97 | Portal | Must Have | Dashboard | Program At A Glance Tile | Functional | Application/Eligibility | Phase 3 | The customer dashboard shall display a pathway or a process step indicator, visually representing their progress and current status within the process for in-scope programs | The requirement was created to address the customer's need to track their actions to take for current programs they are participating in, as documented in the Art of the Possible sessions. | F.S. 445.009; 445.010; 445.011 | |
| 98 | REQ-P-98 | Portal | Must Have | Dashboard | Program At A Glance Tile | Functional | Application/Eligibility | Phase 3 | The portal shall have a personalized list of action items for the customers | The requirement was created to address the customer's need to track their actions to take for current programs they are participating in, as documented in the Art of the Possible sessions. | F.S. 445.009; 445.010; 445.011 | |
| 99 | REQ-P-99 | Portal | Nice to Have | Dashboard | Scheduling Tool | Functional | Application/Eligibility | Phase 3 | The portal shall allow customers to view their scheduled meetings in a calendar view | This requirement was created to accommodate customers and agency staff to easily coordinate and attend appointments, as heard in ride along sessions and documented in Cindy, Robert, and Maryanne's To-Be Journey. | F.S. 445.009; 445.010; 445.011 |
must
Technical FL WINS Requirements Traceability Matrix The FL WINS Requirements Traceability Matrix (RTM) captures epic-level requirements needed to help vendors design a high-level solution. The RTM is not intended to provide lower-level requirements in order to allow future solution vendors to determine how the functionality will be implemented at their discretion. Each requirement listed in the RTM is tied to a capability and a feature to group requirements based on the areas of functionality the requirement is associated with. Solution vendors will elaborate on the feature-level requirements to identify lower-level requirements that fit their solution and delivery methodology. To reference a representative visualization of the future FL WINS solution, please see section 5 of the Target Operating Model (TOM) to view potential solution wireframes. Note, the wireframes in the TOM are not the solution for FL WINS but a visualized representation of a portion of the components and features that will make the Master Service Blueprint possible. This RTM is a living 'document'. For reference, the Master Service Blueprint can be found in section 2 of the TOM.
| ReqID | |
| Abhinav Chawla: Unique identifier for each requirement, identifying which component it belongs to and the requirement number. | Solution Component |
| Abhinav Chawla: Identifies application area in the solution. Includes Portal, Integrated Data Solution, and Customer 360. | Priority |
| Abhinav Chawla: Provides a mechanism to identify if the requirement is a ‘Must-Have' or ‘Nice-to-Have' | Capability |
| Abhinav Chawla: Capabilities are units of functionality broken down from the Solution Components to address the major pain points identified through discovery. | Feature |
| Abhinav Chawla: Features are smaller units of functionality that are nested within capabilities. | Requirement Type |
| Abhinav Chawla: Identifies if the Requirement is Technical or Functional in nature | Journey Phase |
| Abhinav Chawla: Identifies the future state journey phase attached to the solution, aligned to the master service blueprint. | Implementation Phase |
| Abhinav Chawla: Identifies the implementation phase for an iterative approach | Requirement |
| Abhinav Chawla: Captures how a product, system, or service must behave to fulfill a specific customer need | Evidence |
| Abhinav Chawla: Provides traceability to the identification of the pain point that led to the creation of the requirement | Legislation |
| Abhinav Chawla: Provides traceability to applicable Florida Statutes or Program's Authority | Requirement is met by: |
| Schaffer, Jacquelyn: Reference tab #1 for instructions | Explanation or Comments |
Schaffer, Jacquelyn: Reference Tab #1 for instructions
| REQ-P-11 | Portal | Nice to Have | Modularity | Low Code | Technical | Across Phases | Phase 1 | The portal shall provide low code capability to allow for rapid changes due to legislative requirements | This requirement was created to accommodate any programmatic policy changes to online forms used to apply for programs and workforce services. | F.S. 282 |
| REQ-DS-01 | Data Solution | Must Have | Security | Compliance | Technical | Across Phases | Phase 1 | The data solution shall, at all times, be compliant with all Florida Statutes throughout the implementation, operation and maintenance of the FL WINS solution | This requirement was created in compliance with Florida Statute Chapter 501 - CONSUMER PROTECTION, Title XXXIII - REGULATION OF TRADE, COMMERCE, INVESTMENTS, AND SOLICITATIONS, at all times. | F.S. 501 Title XXXIII |
| REQ-P-05 | Portal | Must Have | Infrastructure | Performance | Technical | Across Phases | Phase 1 | The portal shall be designed and configured to accommodate at least X concurrent customers and a significant increase in traffic at Y% growth annually, with the ability to scale both vertically and horizontally, where vertically is by scaling the existing resources and horizontally is by adding additional resources | This requirement was created in compliance with Florida Statute Chapter 282 - COMMUNICATIONS AND DATA PROCESSING (Part I, II, III) , Title XIX - PUBLIC BUSINESS. | F.S. 282 Part I, II, III |
| REQ-DS-02 | Data Solution | Must Have | Data Protection | Disaster Recovery | Technical | Across Phases | Phase 1 | The data solution shall provide capability for disaster recovery as outlined in chapter 282 - COMMUNICATIONS AND DATA PROCESSING (Part I, II, III), Title XIX - PUBLIC BUSINESS (Florida Statute) | This requirement was created in compliance with Florida Statute Chapter 282 - COMMUNICATIONS AND DATA PROCESSING (Part I, II, III) , Title XIX - PUBLIC BUSINESS. | F.S. 282 Part I, II, III |
| REQ-P-06 | Portal | Must Have | Infrastructure | Performance | Technical | Across Phases | Phase 1 | The solution's user facing components shall maintain a consistently (>90%) low latency level, with a maximum allowable round trip latency of 200 milliseconds for all critical user interactions and features as defined by the business (e.g., common intake form). | This requirement was created in compliance with Florida Statute Chapter 282 - COMMUNICATIONS AND DATA PROCESSING (Part I, II, III) , Title XIX - PUBLIC BUSINESS. | F.S. 282 Part I, II, III |
| REQ-P-01 | Portal | Must Have | Infrastructure | Availability | Technical | Across Phases | Phase 1 | The portal shall maintain a minimum availability of 99.9% during the standard operating hours as defined by the business, excluding scheduled maintenance windows. | This requirement was created in compliance with Florida Statute Chapter 282 - COMMUNICATIONS AND DATA PROCESSING (Part I, II, III) , Title XIX - PUBLIC BUSINESS. | F.S. 282 Part I, II, III |
| REQ-P-02 | Portal | Must Have | Infrastructure | Availability | Technical | Across Phases | Phase 2 | The common intake form shall maintain a minimum availability of 99.9% during the standard operating hours as defined by the business, excluding scheduled maintenance windows. | This requirement was created in compliance with Florida Statute Chapter 282 - COMMUNICATIONS AND DATA PROCESSING (Part I, II, III) , Title XIX - PUBLIC BUSINESS. | F.S. 282 Part I, II, III |
| REQ-P-03 | Portal | Must Have | Infrastructure | Hosting | Technical | Across Phases | Phase 1 | The data solution shall as necessary comply to Florida's Cloud First Policy as outlined in chapter 282 - COMMUNICATIONS AND DATA PROCESSING (Part I, II, III), Title XIX - PUBLIC BUSINESS (Florida Statute) | This requirement was created in compliance with Florida Statute Chapter 282 - COMMUNICATIONS AND DATA PROCESSING (Part I, II, III) , Title XIX - PUBLIC BUSINESS. | F.S. 282 Part I, II, III |
60GG-4, cloud computing, F.A.C.
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 .