Attachment B Pricing Proposal.xlsx
XLSX spreadsheet 15 KB Posted
- Attached to
- Services Doc2384785615 Multimodal Automated Traffic Signal Performance Measure (ATSPM) System
- Solicitation number
- Doc2384785615
- Issued by
- Oregon
About this file
This is a Pricing Proposal form (Attachment B) for RFP T011189/K22531 submitted to the Portland Bureau of Transportation (PBOT) in Oregon for the Multimodal Automated Traffic Signal Performance Measure (ATSPM) System project. The proposal template is structured to capture labor costs across eight primary task categories: Project Management, Technology Recommendations, Open Source ATSPM Software Installation, Custom Software Development, System Testing and Acceptance, Deployment, System Training, and Warranty Maintenance & Support. Bidders are instructed to populate green-highlighted cells with staffing hours and rates for a Project Manager and up to three additional staff members, rename subtasks as needed, and adjust formulas to reflect added rows and columns. The template includes provisions for calculating loaded hourly rates per staff member and total costs per task, with a contingency percentage line item.
The pricing proposal accommodates both warranty and post-warranty maintenance and support costs, with optional post-warranty years extending through Year 7. Bidders must provide total project costs with subtotals and contingency calculations, and the template automatically computes cumulative labor expenses based on hours submitted and hourly rates entered. The form requires detailed cost breakdowns by task and staff category, enabling PBOT to evaluate proposals on a standardized basis. No specific budget ceiling, funding source, or payment terms are indicated within this template document.
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
rfp_pricing_proposal
| PRICING PROPOSAL | ||||||
| T011189 / K22531 Multimodal Automated Traffic Signal Performance Measure System | ||||||
| INSTRUCTIONS | ||||||
| 1. Cells that should be filled are highlighted green. | ||||||
| 2. Rename subtasks and add rows as needed. | ||||||
| 3. Rename staff and add columns as needed. | ||||||
| 4. Verify that total equations include added rows and columns. | ||||||
| PROJECT COSTS | Project Manager | Staff 1 | Staff 2 | Staff 3 | Hours Per Task | Cost Per Task |
| 1. Project Management | 0 | 0 | 0 | 0 | 0 | $ - 0 |
| Subtask 1.1 | 0 | 0 | 0 | 0 | ||
| Subtask 1.2 | 0 | 0 | 0 | 0 | ||
| 2. Technology Recommendations | 0 | 0 | 0 | 0 | 0 | $ - 0 |
| Subtask 2.1 | 0 | 0 | 0 | 0 | ||
| Subtask 2.2 | 0 | 0 | 0 | 0 | ||
| 3. Open Source ATSPM Software Installation | 0 | 0 | 0 | 0 | 0 | $ - 0 |
| Subtask 3.1 | 0 | 0 | 0 | 0 | ||
| Subtask 3.2 | 0 | 0 | 0 | 0 | ||
| 4. Custom Software Development | 0 | 0 | 0 | 0 | 0 | $ - 0 |
| Subtask 4.1 | 0 | 0 | 0 | 0 | ||
| Subtask 4.2 | 0 | 0 | 0 | 0 | ||
| 5. System Testing and Acceptance | 0 | 0 | 0 | 0 | 0 | $ - 0 |
| Subtask 5.1 | 0 | 0 | 0 | 0 | ||
| Subtask 5.2 | 0 | 0 | 0 | 0 | ||
| 6. Deployment | 0 | 0 | 0 | 0 | 0 | $ - 0 |
| Subtask 6.1 | 0 | 0 | 0 | 0 | ||
| Subtask 6.2 | 0 | 0 | 0 | 0 | ||
| 7. System Training | 0 | 0 | 0 | 0 | 0 | $ - 0 |
| Subtask 7.1 | 0 | 0 | 0 | 0 | ||
| Subtask 7.2 | 0 | 0 | 0 | 0 | ||
| 8. Warranty Maintenance & Support | $ - 0 | |||||
| Year 1 | $ - 0 | |||||
| Year 2 | $ - 0 | |||||
| Loaded Hourly Rate | $ - 0 | $ - 0 | $ - 0 | $ - 0 | ||
| Hours Per Staff | 0 | 0 | 0 | 0 | ||
| Cost Per Staff | $ - 0 | $ - 0 | $ - 0 | $ - 0 | ||
| Subtotal | 0 | $ - 0 | ||||
| Contingency | 0% | $ - 0 | ||||
| POST-WARRANTY MAINTENANCE & SUPPORT (OPTIONAL) | TOTAL COST | TOTAL COST | $ - 0 | |||
| Year 3 | $ - 0 | |||||
| Year 4 | $ - 0 | |||||
| Year 5 | $ - 0 | |||||
| Year 6 | $ - 0 | |||||
| Year 7 | $ - 0 |
_x000D_&1#&"Aptos"&10&K000000 Confidential Content
File details come from the government source that posted it. Updated .