Form BB - FMIS Technical Response.xlsx
XLSX spreadsheet 14 KB Posted
- Solicitation number
- BD-19-1206-40000-40000-38457
- Issued by
- Massachusetts
About this file
This document is a Bidder Technical Response Requirement for RFP 88N-19 issued by the Massachusetts Bay Transportation Authority (MBTA). The RFP is seeking a fuel management software solution for MBTA's buses and non-revenue vehicles. The requirements cover the bidder's experience, system platform, hardware, data management, reporting, security, integration, and implementation details. Key requirements include managing and accounting for all fuel and fluid dispensing, providing real-time visibility of all fueling and maintenance events, and integrating with the MBTA's existing maintenance and monitoring systems.
The RFP does not provide details on pricing terms, set-asides, incumbent vendors, funding sources, or contract duration. However, it does indicate that the MBTA is interested in a future add-on capability for fuel/gas leak detection, which would be considered beyond the scope of this RFP.
View the file
Other files
Show all 32
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
Sheet1
| RFP 88N-19 FORM BB Bidder Technical Response | Requirement Description | Bidder Response (click bottom right cell for drop down selection) | Bidder's Written Response |
| 1 | Describe your experience implementing similar fuel management software solutions with public transit or other organizations similar in scope and scale to this project? Provide 3 examples including references with contact information. | ||
| 2 | On what platform is your software built? | ||
| 3 | Provide the list of manufacturers of your preferred mobile and static hardware, which includes user hardware interfaces, model types used for an implementation of this scale, and why it would best benefit the MBTA. | ||
| 4 | Is redundant data retained by your orgnization for risk mitigation purposes? If so, how and where is it stored, and what are the customer's retention period options? | ||
| 5 | At a high level, explain how your system controls, reports and accounts for all commodities dispensed though the FMS system. For buses, these are fuel (either CNG or diesel) and non-fuel (transmission fluid, oil, DEF, antifreeze, and windshield wash solution). For non-revenue vehicles, this is only fuel (either gasoline or diesel). | ||
| 6 | Provide a mapping stream with FMS hardware point of service visuals from the delivery of bulk commodity storage & measurements, through bus driver return of vehicle at completion of shift. Include "If/Then" scenarios. | ||
| 7 | Does the system have the ability to provide daily reports on each vehicle’s fluid transactions both by specific vehicle and summary roll up reports (real-time dashboards and reporting)? Expand on system dashboard and reporting capabilities. | ||
| 8 | Can the software system display fueling operations by fueler, by bus, daily - providing vehicle number, the number of vehicles fueled with date/time stamp? | ||
| 9 | Although currently not included in the requirements, the MBTA is interested in learning if your platform offers a bolt on solution for fuel/gass leak detection? If so, it would only be considered a future add-on beyond this RFP. | ||
| 10 | How does your solution migrate, and integrate all data collected into the MBTA’s Maintenance Control Repository System (MCRS2), EAM/maintenance system, Samsara engine and mileage monitoring system, and Veeder-Root system? | ||
| 11 | How does your solution manage, securely control, account for and report in real-time all storage and dispensing of fuels, fluids, electric, mobile and static commodities, and maintenance requests for transit buses and other sources of transportation operated by the MBTA? | ||
| 12 | How are vehicles identified and validated prior to its receiving a commodity, the expected volume and service request notifications? What physical hardware and software security controls are in place? Use a fuel lane task as an example. | ||
| 13 | What are the system security levels of employee access, methods of accessing the system (including biometrics) and, explain how the initialization and authorization process works using a fuel lane task example. | ||
| 14 | Does your solution have the capability to group master data with similar type vehicles sharing common requirements? If so, how? | ||
| 15 | Does your solution have the capability to create algorithms for commodity consumption that can be evaluated in real time to trigger notifications e.g. excessive fuel consumption for miles traveled, including creating dispensing limits? If so, How is it accomplished? | ||
| 17 | Does your technology provide computations of fuel and mileage traveled to assist management prevent and monitor under fueling and over fueling? Is it editable? | ||
| 18 | What system technology is used to measure bulk storage commodities? What inputs to the software are required (if any) and how is it identified when fluid/fuel measuring device (re)calibration is needed? Will the software solution send immediate alerts for low fuel/fluid levels? | ||
| 19 | Does the FMS have a functionality that will allow MBTA to set system rules that fuel, oil, coolant, DEF and ATF type and volume can be limited and controlled by MBTA master data, asset and asset groupings? If so, does the functionality compare the most recently dispensed volume to an active in-process dispensing? Does it record and report those variances? | ||
| 20 | Does the system provide real time visibility of every fueling and maintenance event, including system requested and scheduled events by vehicle, by MBTA location? If so, describe the format(s) by which it is displayed to management. | ||
| 21 | Does the solution have the functionality for data capture of variants such as off site gas/diesel dispensing (ParaTransit vehicles)? If so, explain how this is accomplished. | ||
| 22 | Does the FMS have a method of checks and balances by which system reported events require employee reconciliation for final disposition? If so, describe the method and process. | ||
| 23 | Specific to non-revenue vehicles, does the FMS offer employee key-fob access for transaction authorizations? If so, can it be integrated by vehicle groupings, by location, by employee? | ||
| 24 | Does the FMS provide daily reports that details transaction information by employee, by time, location, vehicle, commodity, if there was a dispensing exception, and summarizes the data? If so, is it trackable in real-time via dashboards? | ||
| 25 | Does the FMS allow for fuel station and maintenance center employees to communicate via system hardware user interfaces? If so, describe the functionality, and if the event is included in the captured data. | ||
| 26 | Does the Fuel Controller System send reports on the fuel island equipment status? If so, is it confgurable to report the status 1x-4x/day if so desired? | ||
| 27 | In the event the Fuel Management System cannot properly dispense fuel or a commodity, explain the process necessary to follow placing the System into By-Pass (local) mode. | ||
| 28 | If a Fuel Island Controller is placed into By-Pass (local) mode is this information immediately reported to the MBTA to identify the Fuel Island(s) in By-Pass (local) Mode? Is the information saved on the server? | ||
| 29 | What are the power requirements for a system of this scale, and contingency plans to insure 24/7/365 continuity? | ||
| 30 | Explain your warranty, maintenance (supported components) and service programs including 24/7/365 (remote and onsite) support. How does your service program distinguish itself from others? | ||
| 31 | Describe in detail your license structure by user, mobile/static hardware, administrators, general users, pumps, annual maintenance components to suppport, and ongoing firmware/software updates. | ||
| 32 | Provide details of implementation plan including the coordinated efforts between key vendor personnel and MBTA, testing, MBTA user training, support, and projected timelines through completion. |
File details come from the government source that posted it. Updated .