Attachment B - Form C Bidder s Price Response.xlsx
XLSX spreadsheet 98 KB Posted
- Attached to
- RFP 252F-24 Bridge Management System
- Solicitation number
- BD-24-1206-40000-40000-111953
- Issued by
- Suffolk County, Massachusetts
About this file
This is a pricing submittal form and instructions document for an MBTA (Massachusetts Bay Transportation Authority) procurement, specifically labeled as "Attachment B - Form C Bidder's Price Response." The document outlines a project implementation timeline starting July 1 with pricing periods spanning from FY25 through FY30. The pricing submission template is divided into two main phases: a Developmental Phase and an Operational Phase & Delivery of Services. The implementation components include system design, configuration, technical development, data migration, testing, and user training.
The pricing structure requires firm fixed pricing for implementation and scalable subscription pricing for SaaS solutions post-implementation. Pricing must be valid for 180 calendar days from submission and include all charges, third-party fees, and associated costs. The pricing spreadsheet breaks down costs into categories including Configuration & Implementation costs and Post Implementation costs covering maintenance, 24/7 technical support, software licensing, hosting services, and system updates. Vendors must disclose pricing assumptions, volume-based pricing, and any potential transition costs if the work needs to be transferred to MBTA or another vendor in the future. The document requires hourly rates for transition support and specifies that any software licensing costs must be pre-negotiated and final.
View the file
Other files
Show all 23
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
Instruction
| Pricing Datasheet |
| General Instruction |
| 1. Submit all pricing data in the Excel Pricing Submittal spreadsheet provided in the appendix xx. Altered formats or blank data will be considered incomplete and may be eliminated from further consideration. |
| 2. The Supplier's pricing proposal must include all charges of any kind associated with the Solution. Pricing must include all third party fees. MBTA will not be liable for any fees or charges for the Solution that is not set forth in the Excel Pricing Submittal. Any attempt to add these fees to submitted pricing will not be considered. |
| 3. For the implementation of the solution, the Supplier must be willing and able to successfully provide firm fixed pricing and scalable subscription pricing if proposing a SaaS solution after implementation. |
| 4. Pricing information supplied with a proposal must be valid for at least 180 calendar days from the submission date. If the Supplier is reserving the option to withdraw the pricing during that period, it must state so clearly in its proposal. |
| 5. MBTA requests that each Supplier provide detailed pricing for each of the pricing methods set forth. Pricing must be comprehensive. Additional information and backup detail should be attached as appropriate. Any scheduled price change must be identified, and actual new prices and proposed effective dates must be stated. |
| 6. The supplier shall disclose pricing assumptions where possible. For example, if unit price is based on a certain volume, that assumption should be indicated. The supplier shall clearly identify any discount targets/ranges available. |
| 7. The format for submitting price data is contained in Appendix xx of the RFP and will be submitted as a sealed and separate volume. |
| Specific Instruction on Completing the Price Spreadsheet |
| 1. Complete the pricing schedule using the PRICE tab contained in this Attachment located in the Appendix xx. |
| 2. Assume July 1 start date for the project. It is MBTA's intent to implement the proposed solution swiftly and without sacrifice to quality. Pricing must reflect the time frames identified in this RFP. Pricing should reflect an implementation schedule that, in the Offeror's judgment, provides the best balance between rapid implementation and transition to sustainment operations. |
| 3. If there are licensing issues associated with the use of the developed product, bidders will identify the specifics of such licenses in their proposal and the associated costs. Likewise, if the vendor is proposing a specific piece of software for which license fees must be paid, and the vendor intends to pass that costs along to MBTA, the vendor will address in narrative form, the negotiated price and relative prices associated with the specific licenses which are required. MBTA expects that any such costs would have been negotiated by the bidder in advance of the proposal and that such costs will be final. |
| 4. Should there be costs associated with any future transition of work from the winning bidder to MBTA or to another vendor, regardless of the time of such transition, the bidder will identify such costs in their proposal and provide narrative language regarding how that transition will be affected. The vendor will also provide, along with this proposal, a transition plan should such transition be affected by the agency. The transition plan will be updated annually on the date of original award. |
| 5. Bidders will provide, as part of their proposal and as noted in the Pricing volume, an hourly rate for any support which might be required in the transition of this contract to internal MBTA resources, or to another vendor, hereafter referenced as such or as “authorized user.” |
Pricing Datasheet
| PRICE SUBMISSION | Developmental Phase | Operational Phase & Delivery of Services | ||||||
| FY 25 | FY25 | FY26 | FY27 | FY28 | FY29 | FY30 | Total | |
| July 1 - Sept 30 | Oct 1 -Dec 31 | Jan 1 - June 30 | July 1 - June 30 | July 1 - June 30 | July 1 - June 30 | July 1 - June 30 | ||
| Configuration & Implementation | $ - 0 | $ - 0 | $ - 0 | |||||
| System Design | $ - 0 | $ - 0 | $ - 0 | |||||
| Technical & API Development | $ - 0 | $ - 0 | $ - 0 | |||||
| Data Migration | $ - 0 | $ - 0 | $ - 0 | |||||
| Internal Testing | $ - 0 | $ - 0 | $ - 0 | |||||
| User Acceptance Testing | $ - 0 | $ - 0 | $ - 0 | |||||
| User Training | $ - 0 | $ - 0 | $ - 0 | |||||
| Operations & Maintenance | $ - 0 | $ - 0 | $ - 0 | |||||
| Sub-Total Configuration & Implemention | $ - 0 | $ - 0 | $ - 0 | |||||
| Post Implementation | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | ||
| Maintenance & Operation | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | ||
| 24/7 Technical Support | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | ||
| Software Licensing | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | ||
| Hosting Services | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | ||
| System Updates | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | ||
| Others | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | ||
| Sub-Total Post Implementation | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
Combined Total $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 $ - 0 image1.jpeg
File details come from the government source that posted it. Updated .