Additional Questions - MWE RFI Responses.pdf
PDF 67 KB Posted
- Attached to
- RFI - Maryland Workforce Exchange (MWE) SaaS
- Solicitation number
- BPM053906
- Issued by
- Maryland
About this file
This document contains responses to general and technical questions submitted during the Request for Information (RFI) phase for the Maryland Workforce Exchange (MWE) SaaS modernization initiative, issued by the Maryland Department of Labor, Division of Workforce Development and Adult Learning (DWDAL). The RFI seeks vendor information regarding solutions capable of delivering essential services to support MWE while enhancing current functions and meeting U.S. Department of Labor and state administrative requirements. The primary objective is to gather information on available options, costs, and opportunities for maintaining one comprehensive workforce system in a SaaS environment as the current vendor contract concludes. The State intends to procure a vendor-hosted SaaS solution that will support full labor exchange functions, WIOA compliance, federal reporting, RESEA, Apprenticeship, Case Management, and custom grant programs across all 13 local workforce boards, with custom workflow capabilities for each board. No specific response deadline, due date, site visit, or bidder's conference information is provided in this document.
The State expects the replacement system to support all historical data migration from the current 1.65 terabyte SQL environment, including data for all user groups, programs, and document files. The solution must comply with SOC 2 Type II certification requirements and all applicable federal and state security standards, with formal procurement specifications to detail required certifications and hosting standards. Integration with existing systems including MDUI, DHR, Salesforce, and Big Interview will utilize current API capabilities. The solution must accommodate multiple languages, including manual Spanish translation and built-in Google Translate for additional languages, and will require usability testing, federal compliance validation, and data migration testing prior to go-live. Federal workforce funding has been identified as the funding source, though no specific budget amount is detailed in this document. The State will provide appropriate technical documentation during later procurement stages consistent with procurement rules and security requirements, and data access activities will be defined if procurement moves forward.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Final - Maryland Workforce Exchange (MWE) - SaaS RFI.pdf | ||
| Cover Page - Addendum 2.pdf | ||
| Tata Responses.pdf | ||
| Team Cyquent Responses.pdf | ||
| Empyra Responses.pdf | ||
| Amendment #1 - Changes to RFI Information - Section 1.2 and 1.3.docx | DOCX document |
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
General Questions
1. Could the DOL clarify its primary objectives for modernizing Maryland Workforce Exchange?
Response:
The primary purpose of the RFI is to gather information. Our current vendor contract is ending, and this RFI is intended to collect details on available options, costs, and opportunities while maintaining one comprehensive workforce system in a SaaS environment.
2. Will responses to this RFI influence future technical or functional requirements for a potential procurement?
Response:
This collected information may have some influence on a future procurement. However, whatever information is used will be general and not specific to the information collected.
3. Is there a projected budget or funding source identified for system replacement or enhancement?
Response:
Federal workforce funding.
Technical Architecture and Security Questions
1. Section 3.4(a) references a “vendor-hosted” solution. Will Maryland consider hybrid or state-hosted SaaS options if they meet compliance standards?
Response:
Maryland wishes to have a vendor-hosted SaaS solution.
2. Are there specific cloud environments preferred or mandated for hosting (e.g., AWS GovCloud, Azure Gov, Google Gov)?
Response:
The State expects vendors to meet all applicable federal and State security standards. Any formal procurement would specify the required certifications and hosting standards.
3. Does MD Labor require FedRAMP, StateRAMP, or SOC 2 Type II certification at go-live?
Response:
SOC 2 Type II is required. See RFI Section 3.5.
4. Will integration require real-time APIs or batch file exchanges for existing systems such as MDUI, DHR, Salesforce, and Big Interview?
Response:
Currently, APIs are utilized for integration with UI BEACON and Big Interview.
5. Will the State provide technical documentation or data dictionaries for current integrations and database schemas to support migration planning?
Response:
If a procurement occurs, the State would provide appropriate technical documentation during later stages of the process, consistent with procurement rules and security requirements.
Data and Migration Questions
1. How much historical data is expected to be migrated from the current 1.65 TB SQL environment?
Response:
All historical data for all user groups, programs, and document files would be expected to be included in the migration.
2. Is Maryland conducting or planning a data quality assessment before migration?
Response:
If data migration from the current vendor to a new vendor were to occur, data quality activities would be defined and reviewed prior to, during, and after migration.
3. Will vendors have access to anonymized datasets or samples for proof-of-concept or migration planning?
Response:
Data access activities would be defined if a procurement moves forward.
Functional and Reporting Capabilities
1. Will the replacement system need to support custom workflows for each of the 13 local workforce boards?
Response:
Yes. Any future SaaS solution would be expected to support full labor exchange functions, WIOA, federal reporting, RESEA, Apprenticeship, Case Management, and custom grant programs across all 13 local workforce boards.
2. Are there expectations for predictive analytics, AI-driven job matching, or performance dashboards?
Response:
The reference to AI-powered solutions reflects interest in understanding available marketplace capabilities. No AI-driven features are required at this time. The current vendor provides data reports, predictive performance reports, requested extracts, and SQL for data review.
3. Should the solution accommodate other workforce-related programs not currently listed (e.g., apprenticeship expansion, reentry services)?
Response:
Yes. Apprenticeship, RESEA, local programs, and reentry services are required.
Accessibility and User Experience Questions
1. Beyond English and Spanish, does Maryland anticipate additional language requirements for translation?
Response:
Yes. The current system includes manual Spanish translation and built-in Google Translate for additional languages.
2. Will usability testing or human-centered design validation be required as part of implementation?
Response:
Yes. Usability testing, federal compliance validation, and data migration testing would all be conducted and verified prior to go-live/implementation.
File details come from the government source that posted it. Updated .