Exhibit E - Price Quote_posted.docx
DOCX document 18 KB Posted
- Attached to
- RFQ One ODA Core CRM & Licensing
- Solicitation number
- S-DASOBO-00016964
- Issued by
- Oregon
About this file
This is a pricing exhibit for the Oregon Department of Administrative Services' Request for Quote for the OneODA Core CRM & Licensing Solution implementation project. The document outlines the pricing structure for deliverables across six primary categories: Project Management Deliverables (project plans, schedules, RAID logs, and status reports), UX/UI Deliverables (personas, wireframes, prototypes, and visual designs), Environment Management (configuration and management of development and deployment environments), Technical Deliverables (solution architecture, design documentation, integration specifications, workflow automation, reporting, security, custom development, data migration, and reconciliation), Testing Deliverables (test plans, scripts, defect reports, and readiness assessments), and Deployment Deliverables (cutover plans, rollback procedures, deployment checklists, IT staff training materials, support documentation, and transition artifacts). Proposers must submit a descriptive schedule of services with pricing for each deliverable category.
The contract will establish fixed-price deliverables based on pricing submitted by proposers. All deliverables must support successful implementation, deployment, transition, and operational readiness of the OneODA CRM & Licensing Solution and are subject to ODA review and approval. The agency will evaluate deliverables for alignment with approved requirements, project objectives, operational readiness expectations, and applicable governance standards. Final acceptance criteria, review timelines, revision processes, and signoff procedures will be established during project planning and governance activities.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Exhibit D - OneODA CRM Licensing Oracle Tables_posted.xlsx | XLSX spreadsheet | |
| Exhibit B - CRM Licensing High-level Solution Requirements_posted.xlsx | XLSX spreadsheet | |
| S-DASOBO-00016964.RFQ CRM and Licensing.posted.docx | DOCX document | |
| Exhibit A - Scope of Work_posted.docx | DOCX document | |
| Exhibit C - OneODA CRM Licensing System Integrations_posted.xlsx | XLSX spreadsheet |
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
Exhibit E
PRICING
Please attach a descriptive schedule of service.
| Deliverable Category |
| Examples |
| Price |
| Project Management Deliverables |
| Project plans, schedules, RAID logs, status reports |
| UX/UI Deliverables |
| Personas, wireframes, prototypes, visual designs |
| Environment Management |
| Configuration and management of environments used for development and deployment of solution. |
| Technical Deliverables |
| Solution architecture, design documentation, integration specs, configuration documentation, workflow automation, reporting, security, custom development, data migration mapping and plans, reconciliation results |
| Testing Deliverables |
| Test plans, scripts, defect reports, readiness assessments |
| Deployment Deliverables |
| Cutover plans, rollback procedures, deployment checklists, ODA IT staff training materials, support documentation, knowledge transfer artifacts, transition plan |
Total
The Proposer should provide pricing for the Deliverable Categories above. The Contract will have fixed price Deliverables established based on the pricing provided by the Proposers.
The Contractor shall provide deliverables necessary to support successful implementation, deployment, transition, and operational readiness of the OneODA CRM & Licensing Solution. Deliverables shall be subject to ODA review and approval. ODA will review deliverables for alignment with approved requirements, project objectives, operational readiness expectations, and applicable governance standards. Final acceptance criteria, review timelines, revision processes, and signoff procedures shall be established during project planning and governance activities.
File details come from the government source that posted it. Updated .