The file's text, extracted by GovTribe without its formatting.
Instructions
Attachment B - Pricing Sheet for Maryland Workforce Exchange (MWE) System Replacement Project RFP Financial Proposal Instructions
Submit an Excel file and a signed PDF file with your Financial Proposal.
This attachment contains tabs to be completed by the Offeror.
| Instructions: |
| 1. Offerors will provide best pricing for their SaaS services. For the pricing plan, Offeror shall include their proposed cost for the duration of the contract for each contract period. This information shall be used by Contractor to complete SaaS information for O&M "Year 1", "Year 2", "Year 3", "Year 4", "Year 5" and "Option Year 1" and "Option Year 2" sheets. |
| 2. On the "Fixed Price" and "Additional Features" sheets, fill-in the green fields only (Gray fields are locked / contain formulas). |
| 3. On the "Year 1", "Year 2", "Year 3", "Year 4", "Year 5", "Option Year 1", and "Option Year 2" tabs, fill in all the green fields only (Gray fields are locked / contain formulas). |
| 4. On the "Labor Category" sheet, fill-in all labor rate fields (green fields only) , add new labor categories and hourly/monthly rates if desired at the bottom for other labor categories proposed. |
| 5. Print all sheets, fill-in the signature boxes on both sheets. |
| 6. Scan both sheets into a single .PDF file, name the file "LABOR MWE <Solicitation #> Price Proposal - <Company Name>” |
| Labor Category for Time and Materials Rates (for Work Orders only) |
| The fully loaded hourly labor rate is the actual rate the State will pay for services and must be recorded in dollars and cents. |
| Labor Rates are used in the price evaluation. They are provided in order to provide a rate for T&M Work Orders for additional work if required but not guaranteed. |
| Information provided in this Excel Workbook is for evaluation purposes only. Pricing and quantities of items do not reflect actual values that will be invoiced by the Contractor. The State at its options may chose to not purchase a particular item. |
SaaS Price Plan
| MWE SaaS Pricing Plan |
| Offerors will provide best pricing for their SaaS services. For the pricing plan, Offeror shall include: |
| Pricing for SaaS services/software licenses |
| Pricing for setup and support of environments |
| Pricing for the SLAs as defined in RFP: |
| Any volume discounts for pricing and bundles |
| Other Additional Services not mentioned |
| For items, that are zero cost or included, please be clear on that as part of the price sheet tabs. |
| Offeror MUST include price plan for their proposed SaaS solution. |
| Company Name |
| Point of Contact |
| Address |
| City, State, Zip |
| Company Tax ID # |
| Office Phone Number |
| Fax Number |
| Email Address |
| Authorized Signature |
| Printed Name |
| Title |
| Date |
Fixed Price
Total Proposed Fixed Price for LABOR MWE Design, Development and Implementation Services.
| Part 1: Software | | | |
| As part of the software project and development including all services (requirements, design, development, testing, conversion, implementation, warranty, etc.) defined in RFP to deliver projects to meet requirements in Section 2 and 3 and Attachment 5. | | | |
| Cost Item | | | Subtotal |
| ID # | Deliverable Description | Deliverable Acceptance (see Section 2.4) | Proposed Price |
| DEL: #01 | Kick-Off Meeting | The Contractor shall prepare a Kick-Off Meeting Presentation. The Kick-Off Meeting Presentation shall include, at minimum: | $ - 0 |
| | 1. Introduction | |
| | 2. Roles and responsibilities | |
| | 3. Understanding of the scope of work | |
| | 4. Timeline/schedule | |
| | 5. Anticipated risks | |
| | 6. Questions/Answers | |
| DEL: #02 | Project Management Plan and Project Schedule (Release / Sprint Plan) | Project Management Plan (PMP) and Schedule shall follow the PMP template found under the following link: https://doit.maryland.gov/SDLC/Custom/Pages/Phase03Single.aspx | $ - 0 |
| The Project Management Plan shall include an Integrated Project Schedule in MS Project format. |
| The Integrated Project Schedule shall include the following: |
| 1. Tasks; |
| 2. Start and End dates; |
| 3. Task duration; |
| 4. Resource assignments; |
| 5. Percentage complete per task; |
| 6. Planned Start; |
| 7. Planned Finish; |
| 8. Predecessors for each task |
| 9. Due dates for each project deliverable tasks defined no greater than 80 hours for a task; and |
| 10. Expectations and tasking for State or other personnel. |
| Project Communications Plan | Project Communications Plan: |
| The Project Communications Plan shall keep all stakeholders informed and involved. The Contractor shall participate in the communications activities with the stakeholders and user community. This shall include user outreach activities and contributing to periodic newsletters. |
| Risk Management Plan | Risk Management Plan: |
| The Risk Management Plan shall include the identification and mitigation of risks and issues. The Offeror will participate in the Program’s Risk Management activities and may be required to manage or mitigate risks or issues identified throughout the course of the project activities. |
| Weekly Reporting | Weekly Reporting: | |
| | Weekly reporting shall include the status of work planned versus completed, description of work accomplished for the previous/current period and plans for the next reporting period along with risk and issues registers, the status of software defects, price variances, and all deliverables for the previous and current month. | |
| PLANNING PHASE | | | |
| DEL: #03 | Transition-In Plan | The Transition-In Plan shall, at minimum: | $ - 0 |
| 1. Detail all the transition activities to initiate the project, including short-term milestones and details around personnel and other contractual resources needed for the project. |
| Data Conversion Plan | The Data Conversion Plan shall, at a minimum: |
| 1. List all legacy and target data repositories and datasets needing to be converted between new and old applications. |
| 2. Finalize design of all data fields (sources and targets) and methods to be used to populate and include in the design document. |
| 3. Complete Extract, Transform, Load (ETL) routines and validate accuracy of conversion and integration processes |
| 4. Mapping of all data elements, directionality of data flow, frequency, and other database released details describing how data repositories will exchange data in a live production environment. |
| Test Plan | The Test Plan shall: |
| 1. Identify the tasks and activities needed to be performed so that all aspects of the system are adequately tested, and that the system can be successfully implemented. |
| 2. Document the scope, content, methodology, sequence, management of, and responsibilities for test activities. |
| 3. Describe the test activities of the subsystem Integration Test, the System Test, the User Acceptance Test, and the Security Test in progressively higher levels of detail as the system is developed. |
| Training Plan | The Training Plan shall: |
| 1. Outline the objectives, needs, strategy, and curriculum to be addressed when training users on the new or enhanced information system. |
| 2. Present the activities needed to support the development of training materials, coordination of training schedules, reservation of personnel and facilities, planning for training needs, and other training-related tasks. |
| 3. Include the target audiences and topics on which training must be conducted on the list of training needs. |
| 4. Include the format of the training program, the list of topics to be covered, materials, time, space requirements, and proposed schedules. |
| User Manual | The User Manual shall: |
| 1. Contain all essential information for the user to make full use of the information system. |
| 2. Include a description of the system functions and capabilities, contingencies and alternate modes of operation, and step-by-step procedures for system access and use. |
| System Administration Manual | The System Administration Manual shall include: |
| 1. System screen shots. |
| 2. Describe the operational and administrative processes and procedures used to manage the project infrastructure and resources. |
| 3. The facility, network, equipment, and project tools, |
| 4. Facility management. |
| 5. Project IT infrastructure. |
| 6. Human resource information, and |
| 7. Travel procedures. |
| System Integration Plan | The System Integration Plan shall: |
| 1. Define the activities necessary to integrate the software units and other software systems into the MWE solution. |
| 2. Contain an overview of the system, a brief description of the major tasks involved in the integration, and the overall resources needed to support the integration effort. |
| Risk Management Plan | The Risk Management Plan shall describe the planned processes and responsibilities to routinely perform risk identification, risk analysis, risk response planning, and risk control activities throughout the life cycle of the project |
| | Risk Management Plan and Risk Log shall follow the Risk Management Plan template found under the following link: https://doit.maryland.gov/SDLC/Custom/Pages/Phase03Single.aspx. | |
| Data Conversion Plan | Data Conversion Plan shall follow the Data Conversion Plan template found under the following link: https://doit.maryland.gov/SDLC/Custom/Pages/Phase05Single.aspx. | |
| Requirements Traceability Matrix (RTM) | The Requirements Traceability Matrix shall provide the information that links requirements to their origins and traces them throughout the project life cycle. | |
| DEL: #04 | Requirements Traceability Matrix (RTM) | The Requirements Traceability Matrix shall provide the information that links requirements to their origins and traces them throughout the project life cycle. | $ - 0 |
| IMPLEMENTATION PHASE | | | |
| DEL: #05 | Custom Application Inventory Document | The Custom Application Inventory Document shall include a complete listing of custom reports, correspondence, and associated software that is required to be developed for LABOR. | $ - 0 |
| Complete inventory of custom application development requirements. |
| System Security Plan (SSP) | The System Security Plan (SSP) shall: |
| 1. Contain pertinent information about the controlled data environment. |
| 2. Identify the features and functions of a solution, including the hardware and the software installed on the system. |
| 3. Define the security measures that are or will be put in place to limit access to authorized users and systems administrators in the secure use of the system. |
| 4. Include details of processes for auditing and maintaining the system in addition to information about how to respond to security incidents that occur. |
| 5. Present a comprehensive summary of all security practices and policies that will keep State data secure. |
| 6. Contain information from those responsible for the systems that make up the data environment; including information owners, system operators, and other stakeholders. |
| System Design Document | The System Design Document shall include pertinent sections from the template available at https://doit.maryland.gov/SDLC/Pages/templates-phases.aspx. |
| | The System Design Document shall describe the system requirements, operating environment, system and subsystem architecture, files and database design, input formats, output layouts, human-machine interfaces, detailed design, processing logic, and external interfaces. | |
| DEL: #06 | Data Migration Plan | The Data Migration Plan shall be delivered to the Contract Monitor and shall include: | $ - 0 |
| 1. Methodology, |
| 2. Scope, and |
| 3. Approach for migrating data. |
| Definition of each data field visible to the user, including meta-data such as technical and display name(s), length, format, and content restrictions. Include traceability where a data field is used in multiple systems under different names. |
| Interface Control Document | The Interface Control Document (ICD) shall specify interface requirements to be met by the participating systems. It describes the concept of operations for the interface, defines the message structure and protocols which govern the interchange of data, and identifies the communication paths along which the data is expected to flow. |
| | The Interface Control Document shall include pertinent sections from the template available at https://doit.maryland.gov/SDLC/Pages/templates-phases.aspx. | |
| Delivery of MWE Configured Solution | Delivery of MWE configured solution that aligns with MWE functional and technical requirements, design specifications, configurations, and business rules identified in Appendix 5 – MWE Technical Requirements. | |
| DEL: #07 | Test Report | A Test Report shall be developed at each level of testing that records the results of testing and certifies readiness for system implementation. The Test Report shall: | $ - 0 |
| 1. Document software testing unit/module, subsystem integration, system, user acceptance, and security - as defined in the Test Plan. |
| 2. Records the results of the tests, presents the capabilities and deficiencies for review, and provides a means of assessing progression to the next stage of development or testing. |
| 3. Be created as required in the remaining phases. |
| 4. Provides a basis for assigning responsibility for deficiency correction and follow up, and for preparation of a statement of project completion. |
| Updates to: | The Contractor shall update project plans. The solution shall: |
| Data Conversion Plan | 1. Demonstrate data exchange between MWE legacy applications and Offeror hosted solution. |
| 2. Demonstrate data exchange between MWE interfaces and Offeror hosted solution. |
| Implementation Plan | Provide an update. |
| Systems Administration Manual | Provide an update. |
| Training Plan | Provide an update. |
| User Manual | Provide an update. |
| System Security Plan | Provide an update. |
| Requirements Traceability Matrix | Provide an update. |
| Test Plan | The Test Plan shall identify the tasks and activities needed to be performed so that all aspects of the system are adequately tested so that the system can be successfully implemented. The Test Plan shall: |
| 1. Document the scope, content, methodology, sequence, management, and responsibilities for test activities. |
| 2. Describe the test activities of the Integration Test, System Test, User Acceptance Test, and Security Test in progressively higher levels of detail as the system is developed. |
| 3. Describe how problems, deficiencies, modifications, and refinements identified during testing or implementation are tracked under configuration control and tested. |
| Test Results Report | The Test Results Report shall include the Contractor’s actual test results for each MWE requirement for each of the following: |
| 1. System Tests |
| 2. Integration Tests |
| 3. Security Tests |
| 4. Performance Tests |
| 5. User Acceptance Tests |
| | Each test type shall include, but is not limited to, a detailed listing of supplied input, expected results, tested results, and pass or fail, a detailed listing of failed tests, remediation plan of failed tests, percentage of passing and failing, and critical functionality unable to pass tests that jeopardize production go-live date. | |
| | Provide support for external security and penetration testing. | |
| Production Solution for User Evaluation (with accompanying system and user documentation) | The Contractor shall provide the complete MWE solution for user evaluation, which includes: | |
| | 1. Complete delivery of the production ready solution with migrated data, and all ancillary system interfaces and configurations included. | |
| | 2. Delivery of training in accordance with the Training Plan and Training Schedules. | |
| | 3. Resolving all issues during Performance Period for Acceptance. | |
| DEL: #08 | Readiness Document | The Readiness Document shall consolidate summary information regarding the current status of the solution and provide decision makers with the information necessary to make a “Go/No Go” decision for releasing a solution version to the operational environment. The Readiness Document shall include: | $ - 0 |
| | 1. A checklist listing the work products. | |
| | 2. User Acceptance Test (UAT) results. | |
| | 3. Other indicators of success measures and deliverable acceptance. | |
| Version Description Document (VDD) | The Version Description Document (VDD) shall: | |
| | 1. Track and control versions of software to be released to the test, training, and operational environments. | |
| | 2. Contain a summary of the features and contents for each version of the solution. | |
| | 3. Identify and describe the version of the software being delivered to the State, including all changes to the software since the last version of the VDD was issued. | |
| | The VDD shall contain a cover memo that summarizes on a single page the significant changes that are included in the release. | |
| Implementation Plan | The Implementation Plan shall describe the planned deployment, installation, and implementation approach. The Implementation Plan shall include the work plan, resources and budget, stakeholders, risk assessment, and quality control. | |
| | Document that includes pertinent sections from the template available at https://doit.maryland.gov/SDLC/Pages/templates-phases.aspx | |
| Problem Escalation Procedure (PEP) | The Program Escalation Procedure shall state how the Contractor will address problem situations and resolutions as they occur during the performance of the Contract. | |
| DEL: #09 | Production Solution for Deployment | The Contractor shall ensure that the MWE solution meets all requirements stated herein and has been successfully installed and tested. | $ - 0 |
| DEL: #10 | Solution Operations and Maintenance | The Contractor shall provide Operations and Maintenance support of the Solution for the duration of the Contract period. | $ - 0 |
| DEL: #11 | Training Plan | The Training Plan shall provide a high-level training strategy to describe the approach to knowledge transfer to MWE stakeholders. The Contractor shall provide, maintain, and execute against a Training Plan that guides outreach and training activities. (e.g., objectives, delivery methods, curriculums, pre-requisites, target audiences). | $ - 0 |
| | The detailed Training Plan shall be delivered to the Contract Monitor and shall include: | |
| | 1. A Training Schedule which provides a schedule of outreach and training events. | |
| | 2. Training Location(s) | |
| DEL: #12 | Administrator Training | The Contractor shall provide training for the DWDAL System Administrators to explain how the System has been configured and how best to manage it. | $ - 0 |
| DEL: #13 | End-User and Train-the-Trainer Training | The Contractor shall deliver Training Curriculum, End-User, and Train-the-Trainer sessions for LABOR assigned trainees. | $ - 0 |
| DEL: #14 | User Documentation | The Contractor shall provide user documentation to include, as a minimum: | $ - 0 |
| | 1. Maintenance procedures, | |
| | 2. Technical manuals, | |
| | 3. User manuals, | |
| | 4. Data dictionary, and | |
| | 5. Other documents available as part of the proposed system. | |
| DEL: #15 | Updates to the Project Plan, Project Schedule, and Risk Log | The Contractor shall provide monthly updates of Project Plan and Project Schedule during the Planning and Implementation Phases. | $ - 0 |
The Risk log shall be updated monthly throughout the duration of the contract term.
DEL: #16 Change Log The Change Log shall log and track change requests throughout the life of the project. Monthly updates (at a minimum), weekly updates if required. $ - 0
| CLOSEOUT PHASE | | | |
| DEL: #17 | Transition-Out Plan | The Transition–Out Plan shall include: | $ - 0 |
| 1. Critical implementation dates for transition-out activities, | |
| 2. Description of resources supporting the transition, | |
| 3. Resources that will be needed to provide transition support, | |
| 4. Updated Operating Procedures, | |
| 5. Updated Performance Reports, | |
| 6. Updated Program Trouble Report, and | |
| 7. Updated In-Process review Report. | |
| TOTAL DELIVERABLE COSTS | | $ - 0 |
| Part 2: Software as a Service (SaaS) During Project Implementation | | | |
| Software as a Service (SaaS) | | | |
| Cost Item | Actual Quantity* [A] | | |
| (Authenticated Users) | Unit Price [B] | Subtotal [C] = [A] x [B] | | |
| Total Required | | | |
| Software as a Service (SaaS) | | $ - 0 | $ - 0 |
| Conduct Training | | $ - 0 | $ - 0 |
| List other required items below | | | |
| <insert item proposed> | | $ - 0 | $ - 0 |
| <insert item proposed> | | $ - 0 | $ - 0 |
| TOTAL SaaS COST | | | $ - 0 |
| *Actual Quantity is what has been purchased from the SaaS solution for this contract. Contractor shall use its SaaS Price Plan for any changes to these amounts during the duration of the contract. | | | |
| Part 3: Software Features (Proposed Implementation Cost for Software Features) | | |
| List all proposed open source and 3rd Party Software being proposed. | | |
| Cost Item (Based on FR Section 25) | Initial Implementation Cost for Additonal Features [A] | Subtotal [C] = [A] |
| FR-25:A: N/A | N/A | |
| FR-25:B: Scan Card/biometrics | $ - 0 | $ - 0 |
| FR-25:C: Kiosks | $ - 0 | $ - 0 |
| FR-25:D: Image Scanning | $ - 0 | $ - 0 |
| FR-25:E: Participant & Emp Cust Sat | $ - 0 | $ - 0 |
| FR-25:F: Premium Emp Svcs | $ - 0 | $ - 0 |
| FR-25:G: TRA Internal or Interface | $ - 0 | $ - 0 |
| FR-25:H: TAA Petition Filing | $ - 0 | $ - 0 |
| FR-25:I: Mobile App | $ - 0 | $ - 0 |
| FR-25:J: Online User Forum | $ - 0 | $ - 0 |
| FR-25:K: SalesForce Integration | $ - 0 | $ - 0 |
| TOTAL COSTS | | $ - 0 |
| Total Fixed Price for Development and Implementation Services | $ - 0 |
| Company Name | |
| Point of Contact | |
| Address | |
| City, State, Zip | |
| Company Tax ID # | |
| Office Phone Number | |
| Fax Number | |
| Email Address | |
| Authorized Signature | |
| Printed Name | |
| Title | |
| Date | |
https://doit.maryland.gov/SDLC/Custom/Pages/Phase03Single.aspxhttps://doit.maryland.gov/SDLC/Custom/Pages/Phase03Single.aspxhttps://doit.maryland.gov/SDLC/Custom/Pages/Phase05Single.aspxhttps://doit.maryland.gov/SDLC/Pages/templates-phases.aspxhttps://doit.maryland.gov/SDLC/Pages/templates-phases.aspxhttps://doit.maryland.gov/SDLC/Pages/templates-phases.aspx Year 1 Costs
| Year 1 Costs | | | |
| Part 1: All Operations and Maintenance (O&M) Costs for Year 1 | | | |
| Please descibe all Operations and Maintenance Costs (help desk, updates, etc.) | | | |
| Description | Unit Price Per Month [A] | Unit(s) Per Month [B] | Total Annual Cost [C] |
[C] = [A] x [B] x 12
| O&M Services | $ - 0 | $ - 0 |
| Backup/Disaster Recovery | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| Total O&M Cost - Year 1 | | $ - 0 |
Part 2: SaaS Cost During O&M Year 1
| Software as a Service (SaaS) description | Unit Price Per Month [A] | Monthly User Volume [B] |
| (Authenticated Users) | Total Annual Cost [C] | | |
[C] = [A] x [B] x 12
| Total Required | | |
| Proposal is for a Statewide License for an unlimited number of users. | $ - 0 | $ - 0 |
| List other required items below | | |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| Total SaaS Cost | | $ - 0 |
| *Quantity will become acutal number of license by State. This figure is for evaluation purposes. Contractor shall use its SaaS Price Plan for actual billing during O&M period. Include all other required SaaS cost (if any beyond the license fee) to provide solution. | | |
| Total Cost for O&M Year One | | $ - 0 |
| Company Name |
| Point of Contact |
| Address |
| City, State, Zip |
| Company Tax ID # |
| Office Phone Number |
| Fax Number |
| Email Address |
| Authorized Signature |
| Printed Name |
| Title |
| Date |
Year 2 Costs
| Year 2 Costs | | | |
| Part 1: All Operations and Maintenance (O&M) Costs for Year 2 | | | |
| Please descibe all Operations and Maintenance Costs (help desk, updates, etc.) | | | |
| Description | Unit Price Per Month [A] | Unit(s) Per Month [B] | Total Annual Cost [C] |
[C] = [A] x [B] x 12
| O&M Services | $ - 0 | $ - 0 |
| Backup/Disaster Recovery | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| Total O&M Cost - Year 2 | | $ - 0 |
Part 2: SaaS Cost During O&M Year 2
| Software as a Service (SaaS) description | Unit Price Per Month [A] | Monthly User Volume [B] |
| (Authenticated Users) | Total Annual Cost [C] | | |
[C] = [A] x [B] x 12
| Total Required | | |
| Proposal is for a Statewide License for an unlimited number of users. | $ - 0 | $ - 0 |
| List other required items below | | |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| Total SaaS Cost | | $ - 0 |
| *Quantity will become acutal number of license by State. This figure is for evaluation purposes. Contractor shall use its SaaS Price Plan for actual billing during O&M period. Include all other required SaaS cost (if any beyond the license fee) to provide solution. | | |
| Total Cost for O&M Year Two | | $ - 0 |
| Company Name |
| Point of Contact |
| Address |
| City, State, Zip |
| Company Tax ID # |
| Office Phone Number |
| Fax Number |
| Email Address |
| Authorized Signature |
| Printed Name |
| Title |
| Date |
Year 3 Costs
| Year 3 Costs | | | |
| Part 1: All Operations and Maintenance (O&M) Costs for Year 3 | | | |
| Please descibe all Operations and Maintenance Costs (help desk, updates, etc.) | | | |
| Description | Unit Price Per Month [A] | Unit(s) Per Month [B] | Total Annual Cost [C] |
[C] = [A] x [B] x 12
| O&M Services | $ - 0 | $ - 0 |
| Backup/Disaster Recovery | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| Total O&M Cost - Year 3 | | $ - 0 |
Part 2: SaaS Cost During O&M Year 3
| Software as a Service (SaaS) description | Unit Price Per Month [A] | Monthly User Volume [B] |
| (Authenticated Users) | Total Annual Cost [C] | | |
[C] = [A] x [B] x 12
| Total Required | | |
| Proposal is for a Statewide License for an unlimited number of users. | $ - 0 | $ - 0 |
| List other required items below | | |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| Total SaaS Cost | | $ - 0 |
| *Quantity will become acutal number of license by State. This figure is for evaluation purposes. Contractor shall use its SaaS Price Plan for actual billing during O&M period. Include all other required SaaS cost (if any beyond the license fee) to provide solution. | | |
| Total Cost for O&M Year Three | | $ - 0 |
| Company Name |
| Point of Contact |
| Address |
| City, State, Zip |
| Company Tax ID # |
| Office Phone Number |
| Fax Number |
| Email Address |
| Authorized Signature |
| Printed Name |
| Title |
| Date |
Year 4 Costs
| Year 4 Costs | | | |
| Part 1: All Operations and Maintenance (O&M) Costs for Year 4 | | | |
| Please descibe all Operations and Maintenance Costs (help desk, updates, etc.) | | | |
| Description | Unit Price Per Month [A] | Unit(s) Per Month [B] | Total Annual Cost [C] |
[C] = [A] x [B] x 12
| O&M Services | $ - 0 | $ - 0 |
| Backup/Disaster Recovery | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| Total O&M Cost - Year 4 | | $ - 0 |
Part 2: SaaS Cost During O&M Year 4
| Software as a Service (SaaS) description | Unit Price Per Month [A] | Monthly User Volume [B] |
| (Authenticated Users) | Total Annual Cost [C] | | |
[C] = [A] x [B] x 12
| Total Required | | |
| Proposal is for a Statewide License for an unlimited number of users. | $ - 0 | $ - 0 |
| List other required items below | | |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| Total SaaS Cost | | $ - 0 |
| *Quantity will become acutal number of license by State. This figure is for evaluation purposes. Contractor shall use its SaaS Price Plan for actual billing during O&M period. Include all other required SaaS cost (if any beyond the license fee) to provide solution. | | |
| Total Cost for O&M Year Four | | $ - 0 |
| Company Name |
| Point of Contact |
| Address |
| City, State, Zip |
| Company Tax ID # |
| Office Phone Number |
| Fax Number |
| Email Address |
| Authorized Signature |
| Printed Name |
| Title |
| Date |
Year 5 Costs
| Year 5 Costs | | | |
| Part 1: All Operations and Maintenance (O&M) Costs for Year 5 | | | |
| Please descibe all Operations and Maintenance Costs (help desk, updates, etc.) | | | |
| Description | Unit Price Per Month [A] | Unit(s) Per Month [B] | Total Annual Cost [C] |
[C] = [A] x [B] x 12
| O&M Services | $ - 0 | $ - 0 |
| Backup/Disaster Recovery | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| Total O&M Cost - Year 5 | | $ - 0 |
| Part 2: SaaS Cost During O&M Year 5 | | |
| Software as a Service (SaaS) description | Unit Price Per Month [A] | Monthly User Volume [B] |
| (Authenticated Users) | Total Annual Cost [C] | | |
[C] = [A] x [B] x 12
| Total Required | | |
| Proposal is for a Statewide License for an unlimited number of users. | $ - 0 | $ - 0 |
| List other required items below | | |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| Total SaaS Cost | | $ - 0 |
| *Quantity will become acutal number of license by State. This figure is for evaluation purposes. Contractor shall use its SaaS Price Plan for actual billing during O&M period. Include all other required SaaS cost (if any beyond the license fee) to provide solution. | | |
| Total Cost for O&M Year Five | $ - 0 |
| Company Name | |
| Point of Contact | |
| Address | |
| City, State, Zip | |
| Company Tax ID # | |
| Office Phone Number | |
| Fax Number | |
| Email Address | |
| Authorized Signature | |
| Printed Name | |
| Title | |
| Date | |
Additional Features Additional Services
| Part 1: Additional Features (Implementation Cost for Software Features) | | | | | | | | |
| Provide pricing for additional features including cost to implement for State | | | | | | | | |
| Additional Features | List implementation Cost for Software Features below | List Annual (12 Months x Monthly Rate) for Cost of Software Features for all users | | | | | | |
| | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 | Option Year 1 | Option Year 2 |
| FR-25:A: N/A | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| FR-25:B: Scan Card/biometrics (2500 cards) | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| FR-25:C: Kiosks (Per kiosk) | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| FR-25:D: Image Scanning | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| FR-25:E: Participant & Emp Cust Sat | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| FR-25:F: Premium Emp Svcs | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| FR-25:G: TRA Internal or Interface | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| FR-25:H: TAA Petition Filing | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| FR-25: I: Mobile App | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| FR-25:J: Online User Forum | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| FR-25:K: Salesforce Integration | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Total Cost | | | | | | | $ - 0 | |
Part 2: Environments
| Environment | | List Annual (12 Months x Monthly Rate) for Each Environment | | | | | | |
| Setup Cost | Year 1 | Year 2 | Year 3 | Year 4 | Year 5 | Option Year 1 | Option Year 2 |
| Development | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Testing | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Training | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Quality Assurance | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Production | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Total Cost | | | | | | | $ - 0 | |
| Total | $ - 0 |
| Company Name | |
| Point of Contact | |
| Address | |
| City, State, Zip | |
| Company Tax ID # | |
| Office Phone Number | |
| Fax Number | |
| Email Address | |
| Authorized Signature | |
| Printed Name | |
| Title | |
| Date | |
Attachment F - DLLR MWE Price Sheet &A
Option Year 1
| Option Year 1 Costs | | | |
| Part 1: All Operations and Maintenance (O&M) Cost for Option Year 1 | | | |
| Please descibe all Operations and Maintenance Costs (help desk, updates, etc.) | | | |
| Description | Unit Price Per Month [A] | Unit(s) Per Month [B] | Total Annual Cost [C] |
[C] = [A] x [B] x 12
| O&M Services | $ - 0 | $ - 0 |
| Backup/Disaster Recovery | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| Total O&M Cost - Option Year 1 | | $ - 0 |
| Part 2: SaaS Cost for Option Year 1 | | |
| Software as a Service (SaaS) description | Unit Price Per Month [A] | Monthly User Volume [B] |
| (Authenticated Users) | Total Annual Cost [C] | | |
[C] = [A] x [B] x 12
| Total Required | | |
| Proposal is for a Statewide License for an unlimited number of users. | $ - 0 | $ - 0 |
| List other required items below | | |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| Total SaaS Cost | | $ - 0 |
| *Quantity will become acutal number of license by State. This figure is for evaluation purposes. Contractor shall use its SaaS Price Plan for actual billing during O&M period. Include all other required SaaS cost (if any beyond the license fee) to provide solution. | | |
| Total Cost for Option Year 1 | | $ - 0 |
| Company Name | | |
| Point of Contact | | |
| Address | | |
| City, State, Zip | | |
| Company Tax ID # | | |
| Office Phone Number | | |
| Fax Number | | |
| Email Address | | |
| Authorized Signature | | |
| Printed Name | | |
| Title | | |
| Date | | |
Option Year 2
| Option Year 2 Costs | | | |
| Part 1: All Operations and Maintenance (O&M) Cost for Option Year 2 | | | |
| Please descibe all Operations and Maintenance Costs (help desk, updates, etc.) | | | |
| Description | Unit Price Per Month [A] | Unit(s) Per Month [B] | Total Annual Cost |
[C] = [A] x [B] x 12 [C]
| O&M Services | $ - 0 | $ - 0 |
| Backup/Disaster Recovery | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| Total O&M Cost - Option Year 2 | | $ - 0 |
| Part 2: SaaS Cost for Option Year 2 | | |
| Software as a Service (SaaS) description | Unit Price Per Month [A] | Monthly User Volume [B] |
| (Authenticated Users) | Total Annual Cost [C] | | |
[C] = [A] x [B] x 12
| Total Required | | |
| Proposal is for a Statewide License for an unlimited number of users. | $ - 0 | $ - 0 |
| List other required items below | | |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| <Insert description> | $ - 0 | $ - 0 |
| Total SaaS Cost | | $ - 0 |
| *Quantity will become acutal number of license by State. This figure is for evaluation purposes. Contractor shall use its SaaS Price Plan for actual billing during O&M period. Include all other required SaaS cost (if any beyond the license fee) to provide solution. | | |
| Total Cost for Option Year 2 | | $ - 0 |
| Company Name | | |
| Point of Contact | | |
| Address | | |
| City, State, Zip | | |
| Company Tax ID # | | |
| Office Phone Number | | |
| Fax Number | | |
| Email Address | | |
| Authorized Signature | | |
| Printed Name | | |
| Title | | |
| Date | | |
Labor Category
| The positions below will become “active” at the State’s discretion, in consultation with the Contractor. |
| Offerors shall take note that these positions and associated rates will be used for all Work Orders. |
| Staff Position (Labor Category) | Year One | Year Two | Year Three | Year Four | Year Five | Optional Year 1 | Optional Year 2 |
| Fully Loaded Hourly Rate | Fully Loaded Hourly Rate | Fully Loaded Hourly Rate | Fully Loaded Hourly Rate | Fully Loaded Hourly Rate | Fully Loaded Hourly Rate | Fully Loaded Hourly Rate |
| Program Manager | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Application Architect | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Computer Software/Integration Analyst (Senior) | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Applications Programmer | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Database Management Specialist (Senior) | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Subject Matter Expert | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Testing Specialist | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| Training Specialist/Instructor | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 | $ - 0 |
| *Use information provided in SaaS Price Plan to populate this information |
| Company Name |
| Point of Contact |
| Address |
| City, State, Zip |
| Company Tax ID # |
| Office Phone Number |
| Fax Number |
| Email Address |
| Authorized Signature |
| Printed Name |
| Title |
| Date |
Total Evaluated Price MWE Price Proposal
Total Fixed Price $ - 0
| Total Price for O&M Year 1 | $ - 0 |
| Total Price for O&M Year 2 | $ - 0 |
| Total Price for O&M Year 3 | $ - 0 |
| Total Price for O&M Year 4 | $ - 0 |
| Total Price for O&M Year 5 | $ - 0 |
| Total Price for Option Year 1 | $ - 0 |
| Total Price for Option Year 2 | $ - 0 |
| Total Price for Additional Features | $ - 0 |
| Total Evaluated Price | $ - 0 |
| Company Name |
| Point of Contact |
| Address |
| City, State, Zip |
| Company Tax ID # |
| Office Phone Number |
| Fax Number |
| Email Address |
| Authorized Signature |
| Printed Name |
| Title |
| Date |