ESBD_371873_1723662576765_Attachment E. Pricing Workbook.xlsx
XLSX spreadsheet 65 KB Posted
- Attached to
- Legacy Systems Replacement Project
- Solicitation number
- 452-24-BLC020
- Issued by
- Travis County, Austin City, Texas
About this file
This document is an Attachment E. Pricing Workbook for a Request for Offer (RFO) issued by the Texas Department of Licensing and Regulation (TDLR) for the Regulatory Applications Modernization Project (RAMP). The RFO is for the replacement of TDLR's legacy licensing systems.
The Pricing Workbook contains multiple worksheets for the Offeror to detail their proposed pricing, including labor rates, implementation services, ongoing software costs, and cost assumptions. The implementation services worksheet lists 30 deliverables the Offeror must provide, with costs, quantities, and expected delivery dates. The ongoing software costs worksheet covers costs for the implementation period as well as the first 5 years of production, including any licensing, hosting, maintenance, and support. The Offeror is required to provide detailed cost assumptions that underpin their pricing.
View the file
Other files
Show 40 more
50 files listed here. See the rest on GovTribe.
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
Title Page
| Texas Department of Licensing and Regulation (TDLR) |
| Replacement of Legacy Licensing Systems Replacement Project |
| Attachment E. Pricing Workbook |
ToC
| Attachment E. Pricing Workbook | |
| Table of Contents | |
| Offeror: | [Insert Offeror Name] |
| Worksheet Title / Hyperlink | Description |
| Instructions | Instructions for completing Pricing Workbook. |
| 1. Total Cost Summary | Worksheet to display a summary of the total proposed costs. THIS WILL AUTOPOPULATE FROM OTHER TABS. No changes needed. |
| 2. Labor Rates | Worksheet for itemizing hourly rate structures for proposed project personnel. |
| 3. Implementation Services | Worksheet for one-time implementation project costs. |
| 4. Ongoing Software Costs | Worksheet for ongoing costs on an annual basis |
| 5. Cost Assumptions | Worksheet for Offeror to itemize all assumptions upon which its pricing is dependent. |
TREC & TALCB
Regulatory Applications Modernization Project (RAMP) RFO No. 329-22-0499 Attachment F. Pricing Workbook
&P
Insert Offeror Name here
PLEASE NOTE:
1. The Offeror Name in the space provided in light-green highlight will populate across all other worksheets.
2. Cells requiring Offeror / Option data entry are marked in light-green highlight to clearly indicate which cells are available for data entry as indicated above left.
3. Cells that contain titles and formulas are marked in gray highlight.
4. Cells that are not applicable are marked in black highlight.
5. It is the Offeror's responsibility to ensure the integrity of the Pricing Workbook formulas and links.
Instructions
| Attachment F: Pricing Workbook |
| Instructions |
| [Insert Offeror Name] |
| Please refer to RFO's SOW "Scope of Work" (Section 2.0) for details describing the services and scope of the system implementation services, and maintenance support and operations services to be provided and priced in accordance with this Pricing Workbook. Section 13 - Pricing Workbook (4.2.2.13) in the RFO also contains instructions for this workbook. | |
| 1. | This Microsoft Excel Pricing Workbook contains multiple worksheets designed to provide an understanding of the costing model used by the Offeror. Use of this Pricing Workbook is essential to the Proposal evaluation, and it is essential that the Offeror use this form in preparing its pricing response to this SOW. |
Each worksheet within the workbook is designed to elicit specific pricing information related to the requirements of this SOW. If the Offeror's typical pricing model does not normally charge for a specific element provided within this workbook, then please provide a statement in the "Cost Assumptions" regarding the Offeror methodology for charging for that element (e.g., not applicable, no additional charge). Notes on completing each worksheet can be found at the bottom of the tables.
| 2. | The worksheet labeled TOC (Table of Contents) contains brief descriptions of each spreadsheet, as well as convenient one-click navigation of the Pricing Workbook. Offerors must enter the Offeror Name; this will populate the title of the remaining worksheets. The numbered worksheets are described below: |
| 3. | The Total Cost Summary worksheet calculates total costs based on the data entered into worksheets Tab 3 and 4. Offerors do not need to enter data into this worksheet. Costs for deliverables listed in Tab 3 are shown as one-time costs totaled by deliverable grouping and are not calculated by year. |
| 4. | The Labor Rates worksheet contains tables corresponding to each grouping of deliverables. The tables list the titles of personnel that could be assigned responsibilities in completing the deliverables for the grouping (e.g., Project Management deliverables). |
| 5. | The Implementation Services worksheet provides a table listing the deliverables. The Offeror will enter the cost, quantity, and expected delivery date of each deliverable in that deliverable row. If the Offerror expects to deliver multiple iterations of a deliverable, input each expected delviery date into the date column. All requested implementation deliverables must be offered. Offerors may add additional deliverables as deemed necessary by inserting rows into the worksheet at the bottom of the list currently in each table. In this case, the associated formulas must be copied into column D for that deliverable. Payments will be made using a deliverables-based approach and the deliverable review and approval process described in SOW "Payment Milestones and Invoice Deliverables" Section. |
| 6. | The Ongoing Software Costs worksheet is designed to elicit the pricing of ongoing costs for any licensing, hosting, maintenance, support and operations services throughout the implementation of the project as well as for the first five years of production. Only include hosting costs if you are proposing a SaaS Solution. If you are proposing a DCS-hosted Solution, do not provide any costs as TDLR will obtain pricing from the DCS program based on the infrastructure and/or computing information provided in the Offeror's Technical proposal |
| 7. | In the Cost Assumptions worksheet, the Offeror is required to state all assumptions upon which its pricing is being determined. Insert as many lines as necessary to ensure all concerns are accurately expressed. Assumptions shall not conflict with the Terms and Conditions or Requirements of this SOW. The Offeror must provide details pertaining to the assumptions, expectations, and/or performance parameters that have been used as the basis for the pricing. |
| 8. | Additional notes and instructions may be provided at the bottom of each worksheet tab. |
This Pricing Workbook shall be completed and be provided separately from the rest of the Offeror's Proposal.
TREC & TALCB
Regulatory Applications Modernization Project (RAMP) RFO No. 329-22-0499 Attachment F. Pricing Workbook
&P
1. Total Cost Summary
| Attachment E. Pricing Workbook | THESE CELLS WILL AUTOPOPULATE - DO NOT MAKE CHANGES |
| Total Cost Summary | |
| [Insert Offeror Name] |
| Total Cost Summary: New Licensing System Project (NLS) | |
| Description | Total |
One-time Costs
| Implementation Services | $0.00 |
| Ongoing Software Costs (5 Years) | $0.00 |
| Subtotal | $0.00 |
Regulatory Applications Modernization Project (RAMP) RFO No. 329-22-0499
&P
2. Labor Rates
| Attachment E. Pricing Workbook | ||
| Labor Rates | ||
| [Insert Offeror Name] | ||
| Staff Position | Hourly Rate | Offeror or Subcontractor Name |
| Lead Solution Architect | ||
| Business Analyst/Function Lead | ||
| Change Management Lead | ||
| Comm./Network Specialist | ||
| Database Administrator | ||
| Database Designer | ||
| Help Desk Specialist | ||
| Hardware Specialist | ||
| Operations Lead/Manager | ||
| Project Director | ||
| Project Manager | ||
| Programmer | ||
| Quality Assurance Manager | ||
| Security Systems Engineer | ||
| Systems Administrator | ||
| Information Security Manager | ||
| Technical Lead | ||
| Technical Writer | ||
| Test Lead/Manager | ||
| Tester | ||
| Training Lead/Manager | ||
| Training Specialist | ||
| Other (specify) | ||
| Other (specify) | ||
| Other (specify) | ||
| Other (specify) | ||
| Other (specify) | ||
| Other (specify) | ||
| Other (specify) | ||
| Other (specify) | ||
| Other (specify) | ||
| Composite Rate |
Regulatory Applications Modernization Project (RAMP) RFO No. 329-22-0499
&P
3. Implementation Services
| Attachment E. Pricing Workbook |
| Implementation Services |
| [Insert Offeror Name] |
| NLS Implementation | Instructions | ||||
| 1 | Weekly Status Reports are project management deliverables that will not be invoiced separately. Project management costs should be built in to deliverable costs. | ||||
| ID | Description | Quantity | Total |
One-time
| Costs | Delivery Date | |||
| MM/YY | 2 | Input the quantity, price, and expected date of delivery of each deliverable. If the Offeror is proposing multiple iterations of the solution to be implemented, then there will be multiple versions of the relevant deliverables.If you plan to deliver multiple iterations of a deliverable, input each expected delivery date. | ||
| 1 | Project Management Plan | $0 | ||
| 2 | Project Deployment Plan | $0 | ||
| 3 | Baseline Project Schedule | $0 | ||
| 4 | Deliverable Expectations Document(s) | $0 | ||
| 5 | Validated Requirements Traceability Matrices (Technical and Functional) | $0 | ||
| 6 | Conceptual Design Documentation | $0 | ||
| 7 | Interface Specification Document | $0 | ||
| 8 | Report Specification Document | $0 | ||
| 9 | Solution Implementation Plan (Security Plan, Disaster Recovery and Business Continuity Plan, Infrastructure Services Plan, Communication Protocols) | $0 | ||
| 10 | Cutover Plan | $0 | ||
| 11 | Data Conversion Plan | $0 | ||
| 12 | Data Quality Assessment Report | $0 | ||
| 13 | Data Mapping and Conversion | $0 | ||
| 14 | Test Plan | $0 | ||
| 15 | Test Scripts for System Testing and UAT | $0 | ||
| 16 | System Test Results | $0 | ||
| 17 | UAT Results | $0 | ||
| 18 | Training Plan | $0 | ||
| 19 | Training Curriculum and Materials | $0 | ||
| 20 | Training Completion Report | $0 | ||
| 21 | Go-Live Readiness Report & Updated Artifacts | $0 | ||
| 22 | Final Technical Documentation | $0 | ||
| 23 | Final As-Built Configuration Documentation | $0 | ||
| 24 | Cutover Completion Report | $0 | ||
| 25 | Updated Cutover Plan and Final Cutover Plan/Schedule | $0 | ||
| 26 | Project Closeout Report | $0 | ||
| 27 | Monthly Production Support Templates | $0 | ||
| 28 | System Support & Warranty | $0 | ||
| 29 | Annual Disaster Recovery Test | $0 | ||
| 30 | Release Documentation | $0 | ||
| Total Deliverables Cost | 0 | $0 |
Regulatory Applications Modernization Project (RAMP) RFO No. 329-22-0499
&P
4. Ongoing Software Costs
| Attachment E. Pricing Workbook |
| [Insert Offeror Name] |
| Annual/Ongoing Costs | ||||
| NLS Implementation (assume 500 internal TDLR users) | ||||
| ID | Description | Date (MM/YY - MM/YY) | Unit Price | Price |
| 1 | Costs - Implementation Period | $0 | ||
| 2 | Costs - Implementation Period | $0 | ||
| 3 | Costs - Implementation Period | $0 | ||
| 4 | Costs - Production - Insert Cost Type, such as Software Name and/or Module | $0 | ||
| 5 | Costs - Production - Insert Cost Type, such as Software Name and/or Module | $0 | ||
| 6 | Costs - Production - Insert Cost Type, such as Software Name and/or Module | $0 | ||
| 7 | Costs - Production - Insert Cost Type, such as Software Name and/or Module | $0 | ||
| 8 | Costs - Production - Insert Cost Type, such as Software Name and/or Module | $0 | ||
| Other (specify) - insert rows as needed | $0 | |||
| System Cost Subtotal | $0 | |||
| Notes | ||||
| 1 | Offeror should include any annual/ ongoing costs such as licensing costs, support and maintenance costs, hosting, etc in Column D "Unit Price". These must be ITEMIZED by software name, including any modules within a software package. Include the delivery date (MM/YY) for each cost item. | |||
| 2 | Offerors may insert additional rows for price, as needed. New rows should be added prior to Row 15 to preserve price calculation formulas. | |||
| 3 | Annual / Ongoing Costs must not exceed a 5 year total cost of ownership. For example, if you propose 2 years of implementation costs, you would include 3 years of production services for a total cost value of 5 years. You would NOT include 2 years of implementation costs plus 5 separate total years of production costs. | |||
| 4 | Only include hosting costs if you are proposing a SaaS Solution |
TREC & TALCB
Regulatory Applications Modernization Project (RAMP) RFO No. 329-22-0499
&P
5. Cost Assumptions
| Attachment E. Pricing Workbook | ||||
| Cost Assumptions | ||||
| [Insert Offeror Name] | ||||
| Item # | Proposal Section, Page, Paragraph | Description | Rationale | Cost Impact if the Assumption Turns Out Not to be Valid |
| 1 | ||||
| 2 | ||||
| 3 | ||||
| 4 | ||||
| 5 | ||||
| 6 | ||||
| 7 | ||||
| 8 | ||||
| 9 | ||||
| 10 | ||||
| 11 | ||||
| 12 | ||||
| 13 | ||||
| 14 | ||||
| 15 | ||||
| 16 | ||||
| 17 | ||||
| 18 | ||||
| 19 | ||||
| 20 | ||||
| Notes | ||||
| 1 | The Offeror is required to state all assumptions upon which its pricing is being determined. Assumptions that have no cost impact need not be specified here and should only be listed in the appropriate section of the Proposal. | |||
| 2 | Insert as many lines as necessary to ensure all concerns are accurately expressed. Assumptions shall not conflict with the Terms and Conditions or Requirements of this SOW. | |||
| 3 | Offeror must respond to all deliverables outlined in Tab 3. Offers must identify any optional deliverables, if any, in this tab. |
TREC & TALCB
Regulatory Applications Modernization Project (RAMP) RFO No. 329-22-0499
&P
File details come from the government source that posted it. Updated .