Attachment 2 - Functional and Technical Requirements.xlsx
XLSX spreadsheet 54 KB Posted
- Attached to
- RFP 117-26 Workforce Scheduling & HOS Compliance Software and Implementation Support Services
- Solicitation number
- BD-27-1206-40000-40000-132456
- Issued by
- Massachusetts
About this file
This is a Functional and Technical Requirements document for RFP 117-26, issued by the Massachusetts Bay Transportation Authority (MBTA), outlining specifications for a Workforce Scheduling and Hours of Service (HOS) Compliance Software solution. The RFP encompasses 127 requirements distributed across seven functional areas: Core Workforce Scheduling (43 requirements), Hours of Service & Fatigue Management (17 requirements), Time, Attendance, and Reconciliation (14 requirements), Maintenance & Field Workforce Management (11 requirements), Employee Self-Service & Mobile Workforce (17 requirements), Reporting, Analytics, and Compliance (19 requirements), and General and Technical capabilities (6 requirements). The requirements address critical operational needs including rotating and fixed schedule creation, shift swaps, overtime management, fatigue violation monitoring, real-time time and attendance tracking, maintenance workforce coordination, mobile employee functionality, and comprehensive compliance dashboards. Most requirements are designated as Critical, with select training and certification management features marked as Desired.
Vendors responding to the RFP must indicate their compliance with each requirement using standardized response indicators: Standard (S) for features available in current software releases, Future (F) for capabilities in planned releases with specified version and availability timing, Customization (C) for features requiring custom modifications with associated costs documented in Attachment 3, Third Party (T) for capabilities requiring third-party system integration with vendor identification and costs, or No (N) for features that cannot be provided. Respondents are encouraged to provide additional comments demonstrating system capability. All customization and third-party integration costs must be included in the Cost Worksheet, and third-party vendors must respond using the same indicators with clear notation of their involvement.
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
TOC and Instructions
| Table of Contents | |||
| Tab No. | Functional Area | Functional Area Description | Number of Requirements |
| 1 | Core Workforce Scheduling | Includes capabilities for creating and managing workforce schedules, assignments, vacancies, overtime, staffing rules, training schedules, and operational staffing coordination. | 43 |
| 2 | Hours of Service (HOS) & Fatigue Management | Includes capabilities for applying and monitoring work-hour, rest-period, fatigue, eligibility, exemption, and override rules for HOS compliance. | 17 |
| 3 | Time, Attendance, and Reconciliation | Includes capabilities for capturing, reviewing, correcting, and reconciling employee time and attendance and preparing approved work records for downstream payroll processing. | 14 |
| 4 | Maintenance & Field Workforce Management | Includes capabilities for scheduling and assigning geographically distributed maintenance and field workforces, including planned and unplanned work, outages, call-outs, emergency response, and mobile field assignments. | 11 |
| 5 | Employee Self-Service & Mobile Workforce | Includes self-service and mobile capabilities for employees and supervisors to view schedules, submit and respond to requests, receive notifications, complete workforce actions, and access relevant workforce information. | 17 |
| 6 | Reporting, Analytics, and Compliance | Includes capabilities for operational visibility and dashboards, compliance and exception reporting, and workforce analytics, trends, and forecasting. | 19 |
| 7 | General and Technical | Includes enterprise-wide technical, architecture, security, administration, accessibility, performance, and SaaS platform requirements applicable to the proposed solution. | 6 |
| Total Requirements: | 127 |
| Response and Criticality Definitions | ||
| Indicator | Definition | Instruction |
| S | Standard: Feature/Function is included in the current software release and will be implemented by the planned phase go-live date as part of the proposal from Vendors in accordance with agreed-upon configuration planning with the MBTA. | Respondents are encouraged, but not required, to provide additional information in the Comments column to further demonstrate the system’s ability to meet the requirement. |
| F | Future: Feature/Function will be available in a future software release available to the MBTA at which point it will be implemented in accordance with agreed-upon configuration planning with the MBTA. | If a response indicator of “F” is provided for a requirement that will be met in a future software release, the Respondent shall indicate the planned release version, as well as the time the release will be generally available. |
| C | Customization: Feature/Function is not included in the current software release and is not planned to be a part of a future software release. However, this feature could be provided with custom modifications. All related customization costs should be indicated in Attachment 3 – Cost Worksheet. | If a response indicator of “C” is provided for a requirement that will be met through a custom modification, the Respondent shall indicate the cost of such a modification. |
| T | Third Party: Feature/Function is not included in the current software release and is not planned to be a part of a future software release. However, this feature could be provided with integration with a third-party system. This system should be specified. | If a response indicator of “T” is provided for a requirement that will be met by integration with a third-party system, the Respondent shall identify this third-party system and include a cost proposal to secure this system. If the third-party system is a part of the proposal, the third-party shall respond to the appropriate requirements using the “S”/”C”/”T”/”N” response indicators with a clear notation that the responses are provided by the third-party. |
| N | No: Feature/Function cannot be provided. | N/A |
RFP #117-26 Workforce Scheduling & HOS Compliance Software&"Arial,Bold" Functional and Technical Requirements&"Arial,Regular"&12
MBTA
Table of Contents Instructions &P of &N Attachment 2
1. Core Workforce Scheduling
| Indicator | Definition | Instruction |
| S | Standard: Feature/Function is included in the current software release and will be implemented by the planned phase go-live date as part of the proposal from Vendors in accordance with agreed-upon configuration planning with the MBTA. | Respondents are encouraged, but not required, to provide additional information in the Comments column to further demonstrate the system’s ability to meet the requirement. |
| F | Future: Feature/Function will be available in a future software release available to the MBTA at which point it will be implemented in accordance with agreed-upon configuration planning with the MBTA. | If a response indicator of “F” is provided for a requirement that will be met in a future software release, the Respondent shall indicate the planned release version, as well as the time the release will be generally available. |
| C | Customization: Feature/Function is not included in the current software release and is not planned to be a part of a future software release. However, this feature could be provided with custom modifications. All related customization costs should be indicated in Attachment 3 – Cost Worksheet. | If a response indicator of “C” is provided for a requirement that will be met through a custom modification, the Respondent shall indicate the cost of such a modification. |
| T | Third Party: Feature/Function is not included in the current software release and is not planned to be a part of a future software release. However, this feature could be provided with integration with a third-party system. This system should be specified. | If a response indicator of “T” is provided for a requirement that will be met by integration with a third-party system, the Respondent shall identify this third-party system and include a cost proposal to secure this system. If the third-party system is a part of the proposal, the third-party shall respond to the appropriate requirements using the “S”/”C”/”T”/”N” response indicators with a clear notation that the responses are provided by the third-party. |
| N | No: Feature/Function cannot be provided. | N/A |
| Core Workforce Scheduling |
Includes capabilities for creating and managing workforce schedules, assignments, vacancies, overtime, staffing rules, training schedules, and operational staffing coordination.
| Req # | Description of Requirement | Criticality | Response | Comments |
| Shift Scheduling | ||||
| CWS.1 | The system has the ability to create and manage rotating schedules. | Critical | ||
| CWS.2 | The system has the ability to create and manage fixed schedules. | Critical | ||
| CWS.3 | The system has the ability to create and manage split shifts. | Critical | ||
| CWS.4 | The system has the ability to create and manage overlapping shifts. | Critical | ||
| CWS.5 | The system has the ability to create and manage relief assignments. | Critical | ||
| CWS.6 | The system has the ability to define and manage relief duty types (e.g., vacation relief used to cover work for employees on vacation). | Critical | ||
| CWS.7 | The system has the ability to define and manage cover or standby duties used to cover vacant work. | Critical | ||
| CWS.8 | The system has the ability to identify, track, and manage schedule vacancies. | Critical | ||
| CWS.9 | The system has the ability to publish schedules in real time. | Critical | ||
| CWS.10 | The system has the ability to manage company- and employee-initiated shift swaps. | Critical | ||
| CWS.11 | The system has the ability to manage duty swaps and configure the maximum number of swaps permitted within a company-defined period. | Critical | ||
| CWS.12 | The system has the ability to assign overtime through configurable workflows. | Critical | ||
| CWS.13 | The system has the ability to support schedule handoff logging (i.e., approval of schedule development). | Critical | ||
| Operational Coordination | ||||
| CWS.14 | The system has the ability to generate alerts when staffing shortages are identified. | Critical | ||
| CWS.15 | The system has the ability to notify appropriate users when minimum workstation or location staffing levels are not met. | Critical | ||
| CWS.16 | The system has the ability to coordinate staffing for unplanned incidents or events. | Critical | ||
| CWS.17 | The system has the ability to coordinate staffing for planned incidents or events. | Critical | ||
| CWS.18 | The system has the ability to reassign employees to jobs or tasks through configurable workflows. | Critical | ||
| Assignment Rules | ||||
| CWS.19 | The system has the ability to apply seniority rules when making workforce assignments. | Critical | ||
| CWS.20 | The system has the ability to apply qualification requirements when making workforce assignments. | Critical | ||
| CWS.21 | The system has the ability to apply employee classification rules when making workforce assignments. | Critical | ||
| CWS.22 | The system has the ability to configure and apply labor agreement rules to workforce scheduling and assignments. | Critical | ||
| CWS.23 | The system has the ability to configure assignment-prioritization rules. | Critical | ||
| CWS.24 | The system has the ability to configure and enforce minimum and maximum staffing thresholds by department, day/time, location, workstation, activity, and other applicable organizational criteria. | Critical | ||
| CWS.25 | The system has the ability to create and manage configurable schedule templates. | Critical | ||
| CWS.26 | The system has the ability to track employee availability. | Critical | ||
| CWS.27 | The system has the ability to manage scheduling exceptions through configurable workflows. | Critical | ||
| CWS.28 | The system has the ability to track prior project shift assignments and use assignment history to inform future assignments while applying applicable labor agreement rules. | Critical | ||
| CWS.29 | The system has the ability to track assignment types by employee and use assignment history to inform future assignments while applying applicable labor agreement rules. | Critical | ||
| CWS.30 | The system has the ability to configure rules that generate recommended assignments while applying applicable labor agreement rules (e.g., recommending an eligible employee with the least overtime for the week). | Critical | ||
| CWS.31 | The system has the ability to track employee scheduling preferences while applying applicable labor agreement rules (e.g., weekends, overnights, overtime opportunities). | Critical | ||
| Overtime Management | ||||
| CWS.32 | The system has the ability to submit, route, and approve or deny overtime requests using configurable workflows that capture justification and estimated hours. | Critical | ||
| CWS.33 | The system has the ability to configure overtime approval routing based on organizational rules, employee role, location, department, or other applicable criteria. | Critical | ||
| CWS.34 | The system has the ability to track the status of overtime requests (e.g., submitted, approved, denied, cancelled) and maintain an audit history. | Critical | ||
| CWS.35 | The system has the ability to assign an approval code and record the reason for each overtime assignment. | Critical | ||
| Training & Certification Management | ||||
| CWS.36 | The system has the ability to schedule instructors, trainees, classrooms, and equipment simultaneously. | Desired | ||
| CWS.37 | The system has the ability to enroll eligible employees in training sessions based on qualifications, seniority, prerequisites, or other applicable rules. | Critical | ||
| CWS.38 | The system has the ability to manage classroom capacity and waitlists. | Desired | ||
| CWS.39 | The system has the ability to track employee attendance and training completion. | Desired | ||
| CWS.40 | The system has the ability to prevent assignment of employees whose required certifications or prerequisite training have expired. | Critical | ||
| CWS.41 | The system has the ability to maintain employee certification and recertification records. | Desired | ||
| CWS.42 | The system has the ability to notify employees and supervisors of upcoming required training or certification renewals. | Desired | ||
| CWS.43 | The system has the ability to coordinate employee work schedules with scheduled training events. | Desired |
RFP #117-26 Workforce Scheduling & HOS Compliance Software&"Arial,Bold"
MBTA
Core Workforce Scheduling &P of &N Attachment 2
2. HOS & Fatigue Management
| Indicator | Definition | Instruction |
| S | Standard: Feature/Function is included in the current software release and will be implemented by the planned phase go-live date as part of the proposal from Vendors in accordance with agreed-upon configuration planning with the MBTA. | Respondents are encouraged, but not required, to provide additional information in the Comments column to further demonstrate the system’s ability to meet the requirement. |
| F | Future: Feature/Function will be available in a future software release available to the MBTA at which point it will be implemented in accordance with agreed-upon configuration planning with the MBTA. | If a response indicator of “F” is provided for a requirement that will be met in a future software release, the Respondent shall indicate the planned release version, as well as the time the release will be generally available. |
| C | Customization: Feature/Function is not included in the current software release and is not planned to be a part of a future software release. However, this feature could be provided with custom modifications. All related customization costs should be indicated in Attachment 3 – Cost Worksheet. | If a response indicator of “C” is provided for a requirement that will be met through a custom modification, the Respondent shall indicate the cost of such a modification. |
| T | Third Party: Feature/Function is not included in the current software release and is not planned to be a part of a future software release. However, this feature could be provided with integration with a third-party system. This system should be specified. | If a response indicator of “T” is provided for a requirement that will be met by integration with a third-party system, the Respondent shall identify this third-party system and include a cost proposal to secure this system. If the third-party system is a part of the proposal, the third-party shall respond to the appropriate requirements using the “S”/”C”/”T”/”N” response indicators with a clear notation that the responses are provided by the third-party. |
| N | No: Feature/Function cannot be provided. | N/A |
| Hours of Service (HOS) & Fatigue Management |
Includes capabilities for applying and monitoring work-hour, rest-period, fatigue, eligibility, exemption, and override rules for HOS compliance.
| Req # | Description of Requirement | Criticality | Response | Comments |
| Hours of Service (HOS) Rules | ||||
| HOS.1 | The system has the ability to configure HOS rules by department. | Critical | ||
| HOS.2 | The system has the ability to configure HOS rules by union and/or collective bargaining agreement. | Critical | ||
| HOS.3 | The system has the ability to validate employee eligibility prior to assignment. | Critical | ||
| HOS.4 | The system has the ability to enforce minimum rest periods. | Critical | ||
| HOS.5 | The system has the ability to identify fatigue violations in real time. | Critical | ||
| HOS.6 | The system has the ability to manage fatigue exemptions through configurable workflows. | Critical | ||
| HOS.7 | The system has the ability to configure and apply overtime eligibility rules. | Critical | ||
| HOS.8 | The system has the ability to apply and track paid forced-rest periods where required to satisfy rest-time rules. | Critical | ||
| HOS.9 | The system has the ability to distinguish a potential violation from a confirmed violations. | Critical | ||
| HOS.10 | The system has the ability to identify the fatigue rule that triggered the violation. | Critical | ||
| HOS.11 | The system has the ability to process supervisor overrides through configurable workflows. | Critical | ||
| HOS.12 | The system has the ability to record the explanation (or disposition) for fatigue violation exemptions. | Critical | ||
| HOS.13 | The system has the ability to record the employee, department, assignment, and timing (e.g., violation extent) details for a fatigue violation. | Critical | ||
| HOS.14 | The system has the ability to maintain an audit history of compliance overrides. | Critical | ||
| HOS.15 | The system has the ability to collect and record employee fatigue attestations, including applicable overtime limitations. | Critical | ||
| Compliance Monitoring | ||||
| HOS.16 | The system has the ability to aggregate employee work hours across multiple job classifications, positions, temporary changes, and assignments when evaluating HOS compliance. | Critical | ||
| HOS.17 | The system has the ability to apply fatigue-management rest-period and work-hour restrictions regardless of the employee's current assignment, classification, or temporary position, with authorized override capability. | Critical |
RFP #117-26 Workforce Scheduling & HOS Compliance Software&"Arial,Bold"
MBTA
HOS & Fatigue Management &P of &N Attachment 2
3. Time, Attnd & Reconciliation
| Indicator | Definition | Instruction |
| S | Standard: Feature/Function is included in the current software release and will be implemented by the planned phase go-live date as part of the proposal from Vendors in accordance with agreed-upon configuration planning with the MBTA. | Respondents are encouraged, but not required, to provide additional information in the Comments column to further demonstrate the system’s ability to meet the requirement. |
| F | Future: Feature/Function will be available in a future software release available to the MBTA at which point it will be implemented in accordance with agreed-upon configuration planning with the MBTA. | If a response indicator of “F” is provided for a requirement that will be met in a future software release, the Respondent shall indicate the planned release version, as well as the time the release will be generally available. |
| C | Customization: Feature/Function is not included in the current software release and is not planned to be a part of a future software release. However, this feature could be provided with custom modifications. All related customization costs should be indicated in Attachment 3 – Cost Worksheet. | If a response indicator of “C” is provided for a requirement that will be met through a custom modification, the Respondent shall indicate the cost of such a modification. |
| T | Third Party: Feature/Function is not included in the current software release and is not planned to be a part of a future software release. However, this feature could be provided with integration with a third-party system. This system should be specified. | If a response indicator of “T” is provided for a requirement that will be met by integration with a third-party system, the Respondent shall identify this third-party system and include a cost proposal to secure this system. If the third-party system is a part of the proposal, the third-party shall respond to the appropriate requirements using the “S”/”C”/”T”/”N” response indicators with a clear notation that the responses are provided by the third-party. |
| N | No: Feature/Function cannot be provided. | N/A |
| Time, Attendance, and Reconciliation |
Includes capabilities for capturing, reviewing, correcting, and reconciling employee time and attendance and preparing approved work records for downstream payroll processing.
| Req # | Description of Requirement | Criticality | Response | Comments |
| Time Reconciliation | ||||
| TAR.1 | The system has the ability to reconcile scheduled hours against actual hours worked. | Critical | ||
| TAR.2 | The system has the ability to capture employee clock-in and clock-out events in real time (e.g., web, mobile, kiosk, or other native methods). | Critical | ||
| TAR.3 | The system has the ability to allow authorized users to record or correct employee clock-in and clock-out events. | Critical | ||
| TAR.4 | The system has the ability to identify and resolve missed punches through configurable workflows. | Critical | ||
| TAR.5 | The system has the ability to reconcile leave records, including sick, personal, and vacation leave. | Critical | ||
| TAR.6 | The system has the ability to prepare approved employee work records for payroll processing. | Critical | ||
| TAR.7 | The system has the ability to identify discrepancies between scheduled and paid hours. | Critical | ||
| Exceptions Management | ||||
| TAR.8 | The system has the ability to manage time and attendance exceptions through configurable workflows. | Critical | ||
| TAR.9 | The system has the ability to generate role-based alerts for unresolved time discrepancies. | Critical | ||
| TAR.10 | The system has the ability to route time and attendance exceptions to role-based review queues. | Critical | ||
| TAR.11 | The system has the ability to allow authorized users to correct payroll exceptions through role-based workflows. | Critical | ||
| TAR.12 | The system has the ability to display actual hours worked in real time. | Critical | ||
| TAR.13 | The system has the ability to track and reconcile actual hours worked across multiple job classifications, positions, and temporary assignments. | Critical | ||
| TAR.14 | The system has the ability to display hours worked by employee, position, assignment, and temporary classification while maintaining aggregate employee work-hour totals. | Critical |
RFP #117-26 Workforce Scheduling & HOS Compliance Software&"Arial,Bold"
MBTA
Time, Attendance, & Reconciliation &P of &N Attachment 2
4. Maint. & Field Wrkfc Mgmt
| Indicator | Definition | Instruction |
| S | Standard: Feature/Function is included in the current software release and will be implemented by the planned phase go-live date as part of the proposal from Vendors in accordance with agreed-upon configuration planning with the MBTA. | Respondents are encouraged, but not required, to provide additional information in the Comments column to further demonstrate the system’s ability to meet the requirement. |
| F | Future: Feature/Function will be available in a future software release available to the MBTA at which point it will be implemented in accordance with agreed-upon configuration planning with the MBTA. | If a response indicator of “F” is provided for a requirement that will be met in a future software release, the Respondent shall indicate the planned release version, as well as the time the release will be generally available. |
| C | Customization: Feature/Function is not included in the current software release and is not planned to be a part of a future software release. However, this feature could be provided with custom modifications. All related customization costs should be indicated in Attachment 3 – Cost Worksheet. | If a response indicator of “C” is provided for a requirement that will be met through a custom modification, the Respondent shall indicate the cost of such a modification. |
| T | Third Party: Feature/Function is not included in the current software release and is not planned to be a part of a future software release. However, this feature could be provided with integration with a third-party system. This system should be specified. | If a response indicator of “T” is provided for a requirement that will be met by integration with a third-party system, the Respondent shall identify this third-party system and include a cost proposal to secure this system. If the third-party system is a part of the proposal, the third-party shall respond to the appropriate requirements using the “S”/”C”/”T”/”N” response indicators with a clear notation that the responses are provided by the third-party. |
| N | No: Feature/Function cannot be provided. | N/A |
| Maintenance & Field Workforce Management |
Includes capabilities for scheduling and assigning geographically distributed maintenance and field workforces, including planned and unplanned work, outages, call-outs, emergency response, and mobile field assignments.
| Req # | Description of Requirement | Criticality | Response | Comments |
| Maintenance Workforce | ||||
| MFW.1 | The system has the ability to schedule maintenance and field workforces using configurable organizational and geographic dimensions, including facility, line/section, station, location, crew/shop, railyard, and other applicable work locations. | Critical | ||
| MFW.2 | The system has the ability to schedule planned maintenance work. | Critical | ||
| MFW.3 | The system has the ability to schedule reactive/unplanned maintenance. | Critical | ||
| MFW.4 | The system has the ability to provide visibility into contractor workforce availability and assignments. | Critical | ||
| MFW.5 | The system has the ability to manage maintenance call-outs through configurable workflows (e.g., employee call-outs for scheduled maintenance activities). | Critical | ||
| Field Operations | ||||
| MFW.6 | The system has the ability to assign geographically distributed crews to field or maintenance work. | Critical | ||
| MFW.7 | The system has the ability to schedule crew resources for planned outages and closures. | Critical | ||
| MFW.8 | The system has the ability to schedule crews for emergency response. | Critical | ||
| MFW.9 | The system has the ability to send field notifications related to assignments, outages, and emergencies. | Critical | ||
| MFW.10 | The system has the ability to create, assign, and update mobile field assignments. | Critical | ||
| MFW.11 | The system has the ability to schedule mandatory tasks to specific resources with required completion dates and track completion status. | Critical |
RFP #117-26 Workforce Scheduling & HOS Compliance Software&"Arial,Bold"
MBTA
Maintenance & Field Workforce Management &P of &N Attachment 2
5. ESS & Mobile Workforce
| Indicator | Definition | Instruction |
| S | Standard: Feature/Function is included in the current software release and will be implemented by the planned phase go-live date as part of the proposal from Vendors in accordance with agreed-upon configuration planning with the MBTA. | Respondents are encouraged, but not required, to provide additional information in the Comments column to further demonstrate the system’s ability to meet the requirement. |
| F | Future: Feature/Function will be available in a future software release available to the MBTA at which point it will be implemented in accordance with agreed-upon configuration planning with the MBTA. | If a response indicator of “F” is provided for a requirement that will be met in a future software release, the Respondent shall indicate the planned release version, as well as the time the release will be generally available. |
| C | Customization: Feature/Function is not included in the current software release and is not planned to be a part of a future software release. However, this feature could be provided with custom modifications. All related customization costs should be indicated in Attachment 3 – Cost Worksheet. | If a response indicator of “C” is provided for a requirement that will be met through a custom modification, the Respondent shall indicate the cost of such a modification. |
| T | Third Party: Feature/Function is not included in the current software release and is not planned to be a part of a future software release. However, this feature could be provided with integration with a third-party system. This system should be specified. | If a response indicator of “T” is provided for a requirement that will be met by integration with a third-party system, the Respondent shall identify this third-party system and include a cost proposal to secure this system. If the third-party system is a part of the proposal, the third-party shall respond to the appropriate requirements using the “S”/”C”/”T”/”N” response indicators with a clear notation that the responses are provided by the third-party. |
| N | No: Feature/Function cannot be provided. | N/A |
| Employee Self-Service (ESS) & Mobile Workforce |
Includes self-service and mobile capabilities for employees and supervisors to view schedules, submit and respond to requests, receive notifications, complete workforce actions, and access relevant workforce information.
| Req # | Description of Requirement | Criticality | Response | Comments |
| Employee Self-Service | ||||
| ESS.1 | The system has the ability to allow employees to view schedules on mobile devices. | Critical | ||
| ESS.2 | The system has the ability to allow eligible employees to bid on shifts through mobile functionality. | Critical | ||
| ESS.3 | The system has the ability to allow employees to submit leave requests through mobile functionality. | Critical | ||
| ESS.4 | The system has the ability to allow employees to submit shift-swap requests through mobile functionality. | Critical | ||
| ESS.5 | The system has the ability to allow employees to enter or update availability information (e.g., overtime availability preferences). | Critical | ||
| ESS.6 | The system has the ability to notify employees of available shifts or overtime opportunities and, where applicable, allow eligible employees to respond or bid. | Critical | ||
| ESS.7 | The system has the ability to display assigned training schedules to employees. | Critical | ||
| ESS.8 | The system has the ability to notify employees of upcoming training sessions and schedule changes. | Critical | ||
| ESS.9 | The system has the ability to allow eligible employees to register for available training sessions subject to prerequisites, capacity, and supervisor approval rules. | Critical | ||
| ESS.10 | The system has the ability to allow supervisors to approve or deny employee training requests. | Critical | ||
| ESS.11 | The system has the ability to display employee certifications and upcoming renewal requirements. | Critical | ||
| ESS.12 | The system has the ability to record employee acknowledgments of training notifications, safety bulletins, or operational communications. | Critical | ||
| ESS.13 | The system has the ability to display an employee's training history and certification transcript. | Critical | ||
| Mobile Operations | ||||
| ESS.14 | The system has the ability to deliver configurable notifications to mobile devices. | Critical | ||
| ESS.15 | The system has the ability to allow employees to complete required workforce attestations through mobile and/or employee self-service functionality. | Critical | ||
| ESS.16 | The system has the ability to allow supervisors to review and complete approvals through mobile functionality. | Critical | ||
| ESS.17 | The system has the ability to provide offline access to designated mobile functions and synchronize applicable data when connectivity is restored. | Critical |
RFP #117-26 Workforce Scheduling & HOS Compliance Software&"Arial,Bold"
MBTA
ESS & Mobile Workforce &P of &N Attachment 2
6. Reporting & Analytics
| Indicator | Definition | Instruction |
| S | Standard: Feature/Function is included in the current software release and will be implemented by the planned phase go-live date as part of the proposal from Vendors in accordance with agreed-upon configuration planning with the MBTA. | Respondents are encouraged, but not required, to provide additional information in the Comments column to further demonstrate the system’s ability to meet the requirement. |
| F | Future: Feature/Function will be available in a future software release available to the MBTA at which point it will be implemented in accordance with agreed-upon configuration planning with the MBTA. | If a response indicator of “F” is provided for a requirement that will be met in a future software release, the Respondent shall indicate the planned release version, as well as the time the release will be generally available. |
| C | Customization: Feature/Function is not included in the current software release and is not planned to be a part of a future software release. However, this feature could be provided with custom modifications. All related customization costs should be indicated in Attachment 3 – Cost Worksheet. | If a response indicator of “C” is provided for a requirement that will be met through a custom modification, the Respondent shall indicate the cost of such a modification. |
| T | Third Party: Feature/Function is not included in the current software release and is not planned to be a part of a future software release. However, this feature could be provided with integration with a third-party system. This system should be specified. | If a response indicator of “T” is provided for a requirement that will be met by integration with a third-party system, the Respondent shall identify this third-party system and include a cost proposal to secure this system. If the third-party system is a part of the proposal, the third-party shall respond to the appropriate requirements using the “S”/”C”/”T”/”N” response indicators with a clear notation that the responses are provided by the third-party. |
| N | No: Feature/Function cannot be provided. | N/A |
| Reporting, Analytics, and Compliance |
Includes capabilities for operational visibility and dashboards, compliance and exception reporting, and workforce analytics, trends, and forecasting.
| Req # | Description of Requirement | Criticality | Response | Comments |
| Operational Visibility & Dashboards | ||||
| RAC.1 | The system has the ability to display enterprise-level staffing dashboards. | Critical | ||
| RAC.2 | The system has the ability to display department-level staffing dashboards. | Critical | ||
| RAC.3 | The system has the ability to display workforce availability in real time. | Critical | ||
| RAC.4 | The system has the ability to display command-center operational views. | Critical | ||
| RAC.5 | The system has the ability to track the number of active employees on shift by workstation or location. | Critical | ||
| RAC.6 | The system has the ability to display operational heatmaps. | Desired | ||
| RAC.7 | The system has the ability to generate staffing-level reports by workstation or location. | Critical | ||
| RAC.8 | The system has the ability to allow authorized users to configure KPI dashboards. | Critical | ||
| Compliance & Exception Reporting | ||||
| RAC.9 | The system has the ability to display real-time compliance dashboards. | Critical | ||
| RAC.10 | The system has the ability to display HOS compliance dashboards. | Critical | ||
| RAC.11 | The system has the ability to generate fatigue-violation reports. | Critical | ||
| RAC.12 | The system has the ability to generate payroll reports. | Critical | ||
| RAC.13 | The system has the ability to identify and report discrepancies between employee clock-in/clock-out locations and assigned work locations. | Critical | ||
| RAC.14 | The system has the ability to generate compliance reports by department. | Critical | ||
| RAC.15 | The system has the ability to report on the employee, department, assignment, and timing (e.g., violation extent) details for a fatigue violation. | Critical | ||
| Analytics, Trends, and Forecasting | ||||
| RAC.16 | The system has the ability to analyze and report overtime utilization and trends. | Critical | ||
| RAC.17 | The system has the ability to generate staffing forecasts and related analytics. | Critical | ||
| RAC.18 | The system has the ability to analyze fatigue trends. | Critical | ||
| RAC.19 | The system has the ability to analyze staffing trends. | Critical |
RFP #117-26 Workforce Scheduling & HOS Compliance Software&"Arial,Bold" Functional and Technical Requirements&"Arial,Regular"&12
MBTA
Reporting, Analytics, and Compliance &P of &N Attachment 2
7. General and Technical
| Indicator | Definition | Instruction |
| S | Standard: Feature/Function is included in the current software release and will be implemented by the planned phase go-live date as part of the proposal from Vendors in accordance with agreed-upon configuration planning with the MBTA. | Respondents are encouraged, but not required, to provide additional information in the Comments column to further demonstrate the system’s ability to meet the requirement. |
| F | Future: Feature/Function will be available in a future software release available to the MBTA at which point it will be implemented in accordance with agreed-upon configuration planning with the MBTA. | If a response indicator of “F” is provided for a requirement that will be met in a future software release, the Respondent shall indicate the planned release version, as well as the time the release will be generally available. |
| C | Customization: Feature/Function is not included in the current software release and is not planned to be a part of a future software release. However, this feature could be provided with custom modifications. All related customization costs should be indicated in Attachment 3 – Cost Worksheet. | If a response indicator of “C” is provided for a requirement that will be met through a custom modification, the Respondent shall indicate the cost of such a modification. |
| T | Third Party: Feature/Function is not included in the current software release and is not planned to be a part of a future software release. However, this feature could be provided with integration with a third-party system. This system should be specified. | If a response indicator of “T” is provided for a requirement that will be met by integration with a third-party system, the Respondent shall identify this third-party system and include a cost proposal to secure this system. If the third-party system is a part of the proposal, the third-party shall respond to the appropriate requirements using the “S”/”C”/”T”/”N” response indicators with a clear notation that the responses are provided by the third-party. |
| N | No: Feature/Function cannot be provided. | N/A |
| General and Technical |
Includes enterprise-wide technical, architecture, security, administration, accessibility, performance, and SaaS platform requirements applicable to the proposed solution.
| Req # | Description of Requirement | Criticality | Response | Comments |
| General | ||||
| GT.1 | The system has the ability to support import and export using commonly used and industry-standard data formats (identify support formats in comments column). | Critical | ||
| GT.2 | The system has the ability to support APIs (Application Programming Interfaces) and/or real-time data event feeds for third-party system integration (identify what is out of the box in the comments column). | Critical | ||
| GT.3 | The system has the ability to provide a library of standard reports (i.e., "canned" reports). | Critical | ||
| GT.4 | The system has the ability to create an auditable log of all activity completed on the system (identify activities captured and data for each activity in the comments section or other attachment). | Critical | ||
| GT.5 | The system has the ability to support Role-Based Access Control (RBAC). | Critical | ||
| GT.6 | The system has the ability to support touch screen for mobile functionality. | Critical |
| RFP #117-26 | &"Arial,Bold"&12Workforce Scheduling & HOS Compliance Software |
| Functional and Technical Requirements | MBTA |
General & Technical &P of &N Attachment 2
File details come from the government source that posted it. Updated .