Tata Responses.pdf
PDF 115 KB Posted
- Attached to
- RFI - Maryland Workforce Exchange (MWE) SaaS
- Solicitation number
- BPM053906
- Issued by
- Maryland
About this file
This document contains responses from Tata Consultancy Services to a Request for Information (RFI) issued by the Maryland Department of Labor's Division of Workforce Development and Adult Learning regarding the Maryland Workforce Exchange (MWE) Software-as-a-Service solution. The State is seeking a fully developed Commercial Off-The-Shelf (COTS) SaaS solution to replace its current workforce management system upon contract expiration in December 2028. The requested solution must integrate with existing systems including the MD BEACON unemployment system and Interview Skills Vendor through bi-directional data exchange, while also incorporating job posting data from the American Labor Exchange and web-scraped postings. The system must support all US Department of Labor federal reporting requirements for Titles I and III, ETPL, and Apprenticeship programs, and accommodate case management for Title I, III, TAA, JVSG, WARN, Apprenticeship, ETPL, RESEA, claimant profiling, and locally defined grants. The vendor is responsible for providing the complete technology stack including front-end, back-end, database, hosting, security, and testing environments, with any necessary customizations completed prior to go-live.
The State does not anticipate significant system pain points but is conducting this RFI to explore comparable integrated SaaS solutions with proven performance and federal compliance records. Key requirements include support for skills and interest assessments, WorkKeys, and individual employment plans; stock database reports and executive-level reporting with SQL tools and Power BI integration; single sign-on integration; support for multiple languages beyond the current manual Spanish and Google Translate approach; and AI-supported solutions operating as closed systems to protect Personally Identifiable Information. The State seeks continued federal compliance and reporting, a fully developed single system with all necessary components, and continuous vendor-provided technological improvements. The current system provider was switched in 2011, with the last major upgrade completed in September 2025. No specific budget parameters were provided in the RFI response, and the State indicated it does not intend to "build" a system but rather implement a pre-developed solution with customization capabilities.
View the file
Other files
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
MARYLAND DEPARTMENT OF LABOR REQUEST FOR INFORMATION (RFI)
MARYLAND WORKFORCE EXCHANGE (MWE) SOFTWARE-AS-A-SERVICE (SAAS)
WORKFORCE RFI - BPM053906
Tata Consultancy Services - Questions & Responses
1. Can the State describe the pain points of your legacy system and what you expect to be changed?
o There are no significant pain points with the current system. This RFI is being issued due to the end of the current contract, and the State is exploring comparable integrated SaaS solutions with a proven record of performance and federal compliance.
2. Please describe your current technology stack.
o The current technology stack is provided entirely by the vendor. The SaaS solution includes Front-End, Back-End, Database, Hosting, Integration with the UI system and Interview vendor, Reporting, Security, and Testing/Development environments.
3. Please provide a technology description of the solutions with which your new workforce system will interact or integrate.
o Integration is currently with:
MD BEACON unemployment system
Interview skills vendor
4. How many internal users did you have in the most recent year data is available?
What is the period you are identifying?
o See RFI Section 2.2.3
5. How many external users did you have in the most recent year data is available?
What is the period you are identifying?
o The volume provided in the RFI is based on Fiscal Year 2024.
6. How much legacy data will be transferred to the new system? What is your annual growth rate for data retained?
o See RFI Section 2.2.3 (Database/SQL/Backups).
7. How many individual concurrent users do you have on average?
o See RFI Section 2.2.3
8. What is your budget for this project?
o Not applicable.
9. Please provide your expectations regarding time from contract to production once the RFP is issued.
o The SaaS solution must be fully developed and ready to deploy by the end of the current contract in December 2028. Any necessary customizations will be completed prior to go-live. Maryland does not intend to “build” a system to meet the RFI requirements.
10. Does the State expect to retain any existing processes and/or tools that will be integrated or interfaced with the new solution? If yes, please describe those systems and the technology associated and indicate if they are bi-directional.
• BEACON Unemployment System: Bi-directional exchange of claimant data.
• Interview Skills Vendor: Bi-directional exchange of completed modules and recorded services.
11. Does the State have relationships with job posting and posting concentration organizations which you will prefer to continue? If yes, please provide the name and technology to be interfaced.
• Job posting data from the American Labor Exchange. Additional postings are scraped from the internet using vendor-provided technology.
12. Is the state seeking a COTS solution or a full custom solution?
• Maryland is seeking a COTS SaaS solution that is fully developed and customizable to client specifications. Maryland does not wish to build or integrate multiple systems or platforms.
13. Does the state have a preferred support model?
• See RFI Section 3.3.5
14. Is there a preference for host platform?
• The vendor is responsible for providing the hosting platform.
15. What user groups, in addition to those listed, are you/would you consider adding?
• The user groups are covered in the RFI.
16. What guardrails does the Agency expect to be placed around artificial intelligence–supported solutions?
• While specific guardrails are not yet defined, any AI-supported solution must operate as a closed system to ensure the protection of Personally Identifiable Information (PII).
17. Please provide a list of assessments the State currently uses and their purpose.
Will any of these be desired in the new solution?
• See RFI Section 3.3, i:
o Skills and interest assessments o WorkKeys o Individual employment plans
18. Is there a preference for reporting tools?
• The system must support all USDOL federal reporting requirements for Titles I, III, ETPL, and Apprenticeship.
• Database reports for case management and executive-level reports should be stock reports available to staff to run as needed.
• SQL tools and Power BI integration are preferred.
• Document management be added under reporting tools for data element validation/monitoring
19. Can the State provide relationship diagrams for all stakeholders in your workforce system?
• See RFI Section 2.2.2
20. Please provide a list of current paper-based processes. If any will be retained, please indicate.
• Not applicable.
21. What languages do you expect to be available in the new solution?
• See RFI Section 3.4, C. The current system has manually translated Spanish and other languages via Google Translate.
22. Please share desired user workflow diagrams if such documents have been created.
• Vendor should provide system workflow for a comprehensive system including Labor Exchange, LMI, ETPL, and WIOA case management.
23. What legacy system workarounds exist today?
• Not applicable; the State does not currently identify specific workarounds.
24. Does the State use single sign-on for the legacy workforce solution?
• Yes, single sign-on is used in integration with the MD BEACON unemployment system.
25. What program rulesets are to be integrated with the State's new system in addition to WP, WIOA, etc. (i.e., JSVG, TAA, SNAP, RESEA…)?
• The system will case-manage and federally report on: Title I, III, TAA, JVSG, WARN, Apprenticeship, ETPL, RESEA, claimant profiling, and locally defined grants.
26. Thinking of your current processes, can you share the areas where you would like to see better automation to improve outcomes and deficiencies?
• The current system is meeting these needs effectively.
27. When was the last time the State switched providers for these services, and when was the last major upgrade to your current system?
• System provider was switched in 2011.
• The last major upgrade to the current system was September 2025.
28. What are the top three operational objectives/outcomes that you would like to see improved with a new solution?
• Continued federal compliance and reporting
• Continued use of a single, fully developed system with all necessary components
• Continuous vendor-provided improvements in technology, including AI when available
29. Thinking of your employees' use of the current system, what would make their lives easier?
• Case management projected performance snapshots
• AI assistance for routine tasks and data insights
30. Do you have data-sharing agreements with other Maryland State Agencies?
• Yes, with:
o MD WIOA partners o Unemployment Insurance o MLDS
File details come from the government source that posted it. Updated .