The file's text, extracted by GovTribe without its formatting.
RFP - Pricing Detail Worksheet
| Aeronautics Program Management System RFP |
| Attachment B - Pricing Detail |
| Mandatory Pricing Details: This attachment serves as the Pricing Details Worksheet for this Request for Proposal document. Pricing Details are expected to represent a Vendor Hosted solution. Be sure to complete all applicable sections below to accurately reflect Vendor's pricing for a vendor hosted delivery model. This worksheet specifies charges, fees, rates, and costs for software, licensing, hosting, implementation, enhancements, and other specified costs. |
For any specific pricing clarification please refer to Section F.6 in the RFP.
Note: If there are any desirable elements the Vendor identified as C2 in Attachment A, corresponding pricing should be included in the Optional pricing below. It will be included in the overall proposal cost used in the pricing scoring.
| Offeror Name: | | |
| Offeror Address: | | |
| Initial Term | Total Cost of Ownership |
(TCO)
| Mandatory SaaS & Implementation Pricing Details | | | | Implementation | Production | | | | | | | | | | |
| | | | Implementation | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | |
| AGENCY USER SUBSCRIPTION/LICENSE COSTS | | | | | | | | | | | | | | | |
| User Subscription/License Fees (2) (Insert lines, descriptions, quantities as needed). Pricing should reflect two rates: (1) block of 175 monthly users subscription licenses (2) additional user licensing rates based on future additional license allocations. | | | | | | | | | | | | | | | |
| If the license/subscription rate changes yearly, NOTE that in the Rate (E17 &/or 18) and then in each year change the calculation to the yearly rate * # of user licenses. | | | | | | | | | | | | | | | |
| IF license/subscription is NOT per user but a flat fee, REMOVE the calculations within cells in Row 17 and enter flat rate. | | | | | | | | | | | | | | | |
| NOTE: User subscriptions/licensing should be transferable by Agency administrators; i.e.,staffing based on agency needs. Agency reserves the right to procure additional licenses as needed and pricing should reflect this rate. | | | | | | | | | | | | | | | |
| If Offeror provides block rates for additional users, identify the quantity and rate for each block. | | | | | | | | | | | | | | | |
| QTY: | | | | | | | | | | | | | | |
| | | Rate: | | | | | | | | | | | | |
| 175 | User license | $ - 0 | | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| 1 | Additional user | $ - 0 | | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| 1 | Addl Block Rate | | | | | | | | | | | | | |
| IMPLEMENTATION COSTS |
| Detail any implementation costs for SaaS solution (Insert lines, descriptions, quantities as needed) |
| QTY: | Hourly: | Or enter rate for each as applicable: | | |
| $ - 0 | Implementation | $ - 0 | $ - 0 |
| $ - 0 | Consulting | $ - 0 | $ - 0 |
| $ - 0 | Configuration | $ - 0 | $ - 0 |
| $ - 0 | Conversion | $ - 0 | $ - 0 |
| $ - 0 | Integration | $ - 0 | $ - 0 |
| $ - 0 | Testing | $ - 0 | $ - 0 |
| $ - 0 | Training | $ - 0 | $ - 0 |
| $ - 0 | Support | $ - 0 | $ - 0 |
| $ - 0 | Reports | $ - 0 | $ - 0 |
| | Other - ___________ | $ - 0 | |
| $ - 0 | Other - ___________ | $ - 0 | $ - 0 |
| IDOT Specific Enhancements/Development Costs | | | | | | | | | | | | | | | |
| If hourly rate changes per year NOTE that in the hourly rate (D40 comment as variable) and then in each year change calculation to 500 * hourly rate. | | | | | | | | | | | | | | | |
| QTY: | IDOT Specific enhancements (4) | | | | | | | | | | | | | |
| Hours: | 500 | | Hourly Rate | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| | (Assume 500 hours/year after implementation) | | | | | | | | | | | | | |
| C2 DESIRABLE ELEMENTS COSTS |
| Include the ID Code from Attachment A of desirable element with a C2 response code. Detail the work and cost associated with each element identified as C2 response code. Add implementation costs and any out year costs as necessary. Insert additional rows if needed. . It is up to the vendor to decide the worth of these requirements and they may be included in the contract negotiation for deliverables, cost, etc. |
| Desirable Element | Implementation | | | | | | | | | | | |
| $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Total Base Solution - Production Years | | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Total Base Solution - Implementation | $ - 0 | | | | | | | | | | Implementation | $ - 0 |
| Mandatory SaaS & Implementation Pricing Details | | | | | | | | | | | Grand Totoal | $ - 0 |
| (2) User Subscription/License fees. Include rate for additional users. If tier or sliding scale model, then please include the tier or scale models details. |
| (3) If specific cost breakdowns by role, team member, activity, etc. were used in determining costs, attach those specific cost breakdowns to Attachment B. |
| (4) IDOT Specific Enhancements are related to items that IDOT request be implemented to system to address IDOT processes or Illinois statutory changes that are implemented after system is moved into production. |