Attachment_1_-_Pricing_Proposal.xlsx
XLSX spreadsheet 100 KB Posted
- Attached to
- Enterprise Asset Management - Software & Implementation State and local contract opportunity
- Solicitation number
- RFP 26-0007
- Issued by
- Maricopa County, Phoenix City, Arizona
About this file
This document is a Pricing Proposal spreadsheet (Attachment 1) for the City of Phoenix's Enterprise Asset Management System Request for Proposal (RFP 26-0007). The RFP seeks a comprehensive Enterprise Asset Management (EAM) software and implementation solution for multiple municipal departments, with a planned contract start date of May 1, 2026, and a total contract duration of 5 years. The proposal template requires offerors to complete detailed worksheets covering implementation costs, support services, software licensing, cost assumptions, and optional value-added services, with all figures to be submitted in USD and whole dollars.
The pricing workbook is designed to capture a holistic view of the project's financial aspects, including one-time implementation costs, ongoing support and maintenance expenses, and software licensing fees across different environments. The City expects a comprehensive solution that includes project management, enterprise analysis, solution development, testing, training, go-live support, and post-implementation transition, with a pool of approximately three full-time equivalent (FTE) resources to support ongoing system enhancements and IT initiatives. The proposal emphasizes that the total bid cost is a firm fixed price, and any shifts in the contract start date will not affect the overall pricing, with the expectation that offerors will provide their most competitive and comprehensive pricing structure.
View the file
Other files for this state and local contract opportunity
Show all 50
Enterprise Asset Management - Software & Implementation has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
1. Instructions
Project: RFP 26-0007 - Enterprise Asset Management System Pricing Proposal
| Response Instructions | |
| Company Name: | <Offeror Company Name Here> |
| This template provides a structured approach for proposing the costs associated with delivering the Time and Labor System Solution requirements. Offerors must fill out all applicable worksheets and cells as described by the template and individual worksheet instructions. This template is the formal Cost Proposal for the Offeror's proposal. The Offeror warrants that all costs associated with the services as requested in this RFP are included in this workbook. |
Offeror must complete the Cost Proposal with the expected cost rate based on the anticipated contract start date as stated in the RFP. However, should the contract start date shift for any reason, the City expects the Offeror to honor the costs as stated in their Cost Proposal. The total bid cost is a firm fixed price proposal, and the determination of the contract start date will not affect the total bid price. The Offeror should prepare a cost proposal to reflect the best available pricing to meet the requested scope of services. The City and the Offeror will establish a payment schedule.
This workbook contains cost information required for submission of a proposal for the services in this RFP. The worksheets within this response template are listed below.
All worksheets must be completed. Any proposals that do not provide complete cost information may be excluded from the competitive field.
All costs to deliver the Offeror's full proposal must be included in this workbook. This includes all associated travel expenses
- Cells requiring Offeror data entry are highlighted in light blue to indicate which cells are available for data entry
- Cells that contain titles and formulas are marked in dark gray highlight
- Cells that are not applicable are marked in black highlight
- Do NOT add, edit, or adjust cells unless specifically requested to do so
- It is the Offeror's responsibility to validate the integrity of the Cost Workbook formulas and links
Key Assumptions:
- Offerors must abide by the deadlines detailed in the RFP
- All figures should be in USD and whole dollars
- Implementation is expected to occur up to year 2, with support and maintenance costs occurring after each implementation phase
- Proposals to include costs for a total of 5 years
DO NOTHING ON THIS SHEET.
| Table of Contents | ||
| ID # | Worksheet | Descriptions |
| 1 | Instructions | Instructions and Table of Contents |
| 2 | Total Cost Summary | Summarizes Offeror's total proposed costs |
| 3 | Implementation | Worksheet for Offeror to itemize the implementation services project costs |
| 4 | Support | Worksheet for Offeror to itemize application maintenance and operations costs |
| 5 | Software | Worksheet for Offeror to itemize all one-time and ongoing packaged software costs |
| 6 | Cost Assumptions | Worksheet for Offeror to itemize all assumptions upon which its pricing is dependent |
| 7 | Value-Added Services | Worksheet for Offeror to provide costs associated with any value-added services or solution capabilities beyond the features/requirements detailed in this RFP. This section will not be scored as part of the Cost Proposal |
2. Total Cost Summary Total Cost Summary
The costs recorded on this Total Cost Summary worksheet are automatically calculated using the information entered into worksheets 3. Implementation, 4. Support, and 5. Software. It is Offeror's responsibility to ensure that the costs reflect the full proposal cost for the services outlined in this RFP. Components such as data warehouse, document management, etc. should be included in the Cost Proposal.
Instructions: do NOT edit this sheet. Prior to submission, confirm all costs reflect the proposal cost total.
Total Cost Summary
| Description | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 | Total |
| Implementation | $ - 0 | $ - 0 | ||||
| Support | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Software | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Total Costs | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
&"Arial Black,Regular"&9Phoenix Municipal Court Request for Proposal Attachment F - Cost Workbook
3. Implementation
Implementation Costs
All tasks associated with the implementation services and deliverables described in response to RFP Scope of Work Section 3.9 - Implementation Services and proposed by Offeror shall be included per year (12-month period) for that service, based on Offeror's implementation plan described in response to RFP Scope of Work Section ----.
Note: the information displayed in the cells of this worksheet may be altered. It is the responsibility of Offeror to ensure the spreadsheet calculations are correct. All costs must be fully inclusive.
Instructions: enter costs for existing services in the light-blue cells. If a service will be provided by a third party, notate that as such in the Cost Assumptions tab and cost out that service as its own separate line item. Adjust labels in the white cells as needed. Insert additional rows as necessary where noted to record additional services.
The worksheet allows for one implementation phase. Offerors may add additional rows to correspond with their anticipated implementation plan. All figures should be in USD and whole dollars.
Solution Implementation
| # | Phase | Implementation Services | Total |
| 1 | One | Project Management | |
| 2 | One | Enterprise Analysis and Design | |
| 3 | One | Solution Development and Configuration | |
| 4 | One | Testing | |
| 5 | One | Training and Knowledge Transfer | |
| 6 | One | Production Go-Live and Hypercare | |
| 7 | One | Post Go-Live and Transition to Support | |
| Add additional rows/deliverables as required | |||
| Total Implementation Costs Phase I | $ - 0 |
&"Arial Black,Regular"&9Phoenix Municipal Court
Attachment F - Cost Workbook
3. Implementation
Implementation Costs
All tasks associated with the implementation services and deliverables described in response to RFP Scope of Work Section 7.10 - Implementation Services and proposed by Offeror shall be included per year (12-month period) for that service, based on Offeror's implementation plan described in response to RFP Scope of Work Section.
Note: the information displayed in the cells of this worksheet may be altered. It is the responsibility of Offeror to ensure the spreadsheet calculations are correct. All costs must be fully inclusive.
Instructions: enter costs for existing services in the light-blue cells. If a service will be provided by a third party, notate that as such in the Cost Assumptions tab and cost out that service as its own separate line item. Adjust labels in the white cells as needed. Insert additional rows as necessary where noted to record additional services.
The worksheet allows for one implementation phase. Offerors may add additional rows to correspond with their anticipated implementation plan. All figures should be in USD and whole dollars.
Phase I - Solution Implementation
| # | Project Phase | Milestone # | Deliverable | Project % | Anticipated Cost |
| 1 | Project Management | 1.1 | Project Management Plan | $ - 0 | |
| 1.2 | Change Control Plan | $ - 0 | |||
| 1.3 | Integrated Change Management Plan | $ - 0 | |||
| 1.4 | Quality Management Plan | $ - 0 | |||
| 1.5 | Resource Management Plan | $ - 0 | |||
| 1.6 | Communication Plan | $ - 0 | |||
| 1.7 | Deliverable Management Strategy | $ - 0 | |||
| 1.8 | Requirements Analysis and Management Plan | $ - 0 | |||
| 1.9 | Ongoing Project Management Cost - Weekly Reports | $ - 0 | |||
| 1.10 | Ongoing Project Management Cost - Monthly Reports | $ - 0 | |||
| Project Mangement Phase Total | ERROR:#DIV/0! | $ - 0 | |||
| Discovery and Requirements Validation | 2.1 | Validated Requirements Document | $ - 0 | ||
| 2.2 | Updated and approved Requirements Traceability Matrix (RTM) | $ - 0 | |||
| 2.3 | Fit Gap Analysis Report | $ - 0 | |||
| 2.4 | System Design Document: 1. Detailed solution specifications and workflows;2. Inventory of required reports, integrations, and analytics; 3. System Architecture Document clearly documents the proposed technology environment and integrations; | $ - 0 | |||
| Discovery and Requirements ValidationTotal | ERROR:#DIV/0! | $ - 0 | |||
| 3 | Solution Development and Configuration | 3.1 | Configured EAM System Modules | $ - 0 | |
| 3.2 | Workflow Diagrams and Automation Scripts | $ - 0 | |||
| 3.3 | Technical Design Document | ||||
| 3.4 | Integration and Interface Specifications | $ - 0 | |||
| 3.5 | Standard Reports and Dashboards | $ - 0 | |||
| Solution Development and Configuration Total | ERROR:#DIV/0! | $ - 0 | |||
| 4 | Testing | 4.1 | Testing Plan | $ - 0 | |
| 4.2 | Integration Testing Completion | ||||
| 4.3 | Test Scripts and Test Cases | ||||
| 4.4 | UAT Plan and Completion Results | ||||
| 4.5 | Performance and Load Testing Completion | ||||
| 4.6 | Secuirty and Accessibility Test Completion | $ - 0 | |||
| 4.7 | Riinal Testing Summary Report | $ - 0 | |||
| Testing Total | ERROR:#DIV/0! | $ - 0 | |||
| 5 | Training and Knowledge Transfer | 5.1 | Training Strategy and Plan | $ - 0 | |
| 5.2 | Training Needs Assessment Report | $ - 0 | |||
| 5.3 | Knowledge Transfer Plan | $ - 0 | |||
| 5.4 | Training Completion Report | $ - 0 | |||
| Training and Knowledge Transfer Total | ERROR:#DIV/0! | $ - 0 | |||
| 6 | Production Go-Live and Hypercare | 6.1 | Operational Readiness Review | $ - 0 | |
| 6.2 | Final As Built System Documentation | ||||
| 6.3 | Final Technical Documentation | ||||
| 6.4 | Cutover Plan and Schedule | ||||
| 6.5 | Cutover Completion Report | $ - 0 | |||
| Production Go-Live and Hypercare Total | ERROR:#DIV/0! | $ - 0 | |||
| 7 | Post Go-Live and Transition to Support | 7.1 | First live date has been achieved | $ - 0 | |
| Organizational Change Management Total | ERROR:#DIV/0! | $ - 0 | |||
| Organizational Change Management | 8.1 | Organizational Change Management Plan | $ - 0 | ||
| 8.2 | Impact and Readiness Assessment | $ - 0 | |||
| 8.3 | Stakeholder Engagement | $ - 0 | |||
| 8.4 | Change Support and Tracking | $ - 0 | |||
| ERROR:#DIV/0! | $ - 0 | ||||
| Add additional rows/deliverables as required |
$ - 0
Total Implementation Costs Phase I ERROR:#DIV/0! $ - 0
&"Arial Black,Regular"&9Phoenix Municipal Court
Attachment F - Cost Workbook
4. Support
Production Support Costs
Offeror will provide costs for all post-implementation and production services inclusive of all tasks and deliverables required for maintenance and operation of the new applications as described in RFP Scope of Work Section 7.11 Post Go-Live and Transition to Support and 7.12 Maintenance and Support Requirements.
For the purposes of this pricing worksheet, the scope of 'Support' should be assumed to include:
• Incident and defect triage;
• Defect and incident analysis and reporting;
• Provision of ‘break fix’ service for software, configuration, interface and data issues;
• Patch and Upgrades;
• Enhancements;
• Support for required changes to implement T&L operational functionality;
• A pool of hours (approx. three (3) FTEs) to support ongoing system enhancement and implementation of City IT initiatives
Note: The information displayed in the cells of this worksheet may be altered. It is the responsibility of the Offeror to ensure the spreadsheet calculations are correct. All costs must be fully inclusive.
Instructions: Enter annual costs for all support services in the light-blue cells. Insert additional rows as necessary, where noted in the Offeror's implementation plan. Ensure the calculations in the Total column (gray cells) carry through to the Total column for rows added. You may not delete rows once added. All figures should be in USD and whole dollars.
Post Implementation and Production Support Services
| Support Services | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 | Total |
| Managed Services Support | $ - 0 | |||||
| On-Going Production Support (Post Implementation) | $ - 0 | |||||
| Add additional rows/deliverables as required | $ - 0 | |||||
| ` | $ - 0 | |||||
| $ - 0 | ||||||
| $ - 0 | ||||||
| $ - 0 | ||||||
| $ - 0 | ||||||
| $ - 0 | ||||||
| Post Implementation and Production Support Services Costs Total | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
&"Arial Black,Regular"&9Phoenix Municipal Court
Attachment F - Cost Workbook
5. Software
Software Costs
Offeror will provide any and all costs for software which Offeror's solution will leverage to meet the requirements of this RFP. Costs shall include any licensing necessary to cover all environments (e.g., development, test, training, production, etc.). All costs associated with the purchase, delivery, installation, inspection, licenses, and production of the Software components shall be loaded into the Software Cost.
In the Software Specification table below, Offeror shall list the proposed software manufacturer, brand name, module name, and version number for the items being proposed.
It is the responsibility of Offeror to ensure spreadsheet calculations are correct.
Instructions: Enter all one-time and ongoing software costs for each fiscal year by item. Insert additional rows as necessary where noted. Ensure the calculations in the Total column (gray cells) carry through to the Total column for rows added. You may not delete rows once added. All figures should be in USD and whole dollars.
Software/Hosting Costs
| Item # | Software Item | Per Unit Cost | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 | Total Item Cost |
| 1 | Item 1 | $ - 0 | ||||||
| 2 | Item 2 | $ - 0 | ||||||
| 3 | Item 3 | $ - 0 | ||||||
| 4 | Item 4 | $ - 0 | ||||||
| Add additional rows/deliverables as required | $ - 0 | |||||||
| Total Software Cost | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
Software Specifications
| Item # | Software Item | Environment (e.g. Development, Test, Training, Production) | Manufacturer | License Type (e.g. enterprise, per user, per server) | Brand Name | Module Name | Version Number | Software Type | Detailed Description (e.g. functionality, purpose) | Operating System | Earliest Proposed Purchase Date |
| 1 | Item 1 | ||||||||||
| 2 | Item 2 | ||||||||||
| 3 | Item 3 | ||||||||||
| 4 | Item 4 | ||||||||||
| Add additional rows/deliverables as required |
&"Arial Black,Regular"&9Phoenix Municipal Court
Attachment F - Cost Workbook
6. Cost Assumptions
Cost Assumptions
Offeror must state all assumptions upon which its pricing is determined. Assumptions shall not conflict with the terms and conditions or mandatory requirements of this RFP, and shall not change the requested scope of the RFP as described in the proposal. Offeror must provide a clear understanding to the City of the cost impact to the City if any assumption is determined to be invalid; The City may use these values in consideration of the Cost Proposal.
Instructions: Complete the table below using as many rows as needed. Offeror shall provide a list of all business, economic, legal, programmatic, or practical assumptions that underlie Offeror's response to this RFP along with the associated rationale. Clearly describe the location of the references to the RFP and/or proposal, description of the assumption, rationale for the need of the assumption, and the cost impact to the City should the assumption be invalid. Insert additional rows as needed.
Cost Assumptions
| Item # | Proposal Section, Page, Paragraph | Description | Rationale | Cost Impact if the Assumption is Invalid |
| 1 | ||||
| 2 | ||||
| 3 | ||||
| 4 | ` | |||
| 5 | ||||
| 6 | ||||
| 7 | ||||
| 8 | ||||
| 9 | ||||
| 10 | ||||
| 11 | ||||
| 12 | ||||
| 13 | ||||
| 14 | ||||
| 15 |
&"Arial Black,Regular"&9Phoenix Municipal Court
Attachment F - Cost Workbook
7. Value-Added Services
Value-Added Services and Features
Offeror is invited to propose value-added services and/or features that may be deemed beneficial to the ongoing improvement of Enterprise Asset Management System, both near-term and long-term.
Offeror will provide costs for any proposed value-added services and/or features, but these costs will not be included in the Total Cost Summary. Costs for value-added services and/or optional features will not be scored, but are informational for citywide departments.
It is the responsibility of Offeror to ensure spreadsheet calculations are correct. All costs must be fully inclusive.
Instructions: Enter original and annual costs for all value-added services and/or features proposed. Insert additional rows as necessary where noted if Offeror suggests more than five services and/or features. Ensure the calculations in the Total column (gray cells) carry through to the Total column for rows added. You may not delete rows once added. All figures should be in USD and whole dollars.
Value-Added Services
| Description | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 | Total |
| Value-added Services or Feature #1 | $ - 0 | |||||
| Value-added Services or Feature #2 | $ - 0 | |||||
| Value-added Services or Feature #3 | $ - 0 | |||||
| Value-added Services or Feature #4 | $ - 0 | |||||
| Value-added Services or Feature #5 | $ - 0 | |||||
| Add additional rows/deliverables as required | $ - 0 | |||||
| Value-Added Services and Features Total Cost | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Optional Features/Hardware | ||
| Description | Unit of Measure | Unit Price |
| Add additional rows/deliverables as required | |
| Value-Added Services and Features Total Cost | $ - 0 |
&"Arial Black,Regular"&9Phoenix Municipal Court
Attachment F - Cost Workbook
Data Validation
| Hosting Environment Size |
| Small |
| Medium |
| Large |
image1.png
File details come from the government source that posted it. Updated .