Attachment D - Lot 2 Pricing.xlsx
XLSX spreadsheet 52 KB Posted
- Attached to
- Migration Services
- Solicitation number
- 5400029942
- Issued by
- Richland County, South Carolina
About this file
Summary: Attachment D - Lot 2 Pricing Schedule
This document is a pricing worksheet for Solicitation 5400029942, issued by the State Department of Administration, Office of Technology & Information Services, for migration services under Lot 2 (Shared Service Adoption and Migration - Technical Implementations). Vendors must propose comprehensive technical implementation services including planning and design, inventory assessment, security and compliance work, Active Directory and Entra ID integration, support planning, domain consolidation, email migration, SharePoint and Teams implementation, OneDrive migration, security and compliance implementation, decommissioning, and post-migration support. The pricing structure is organized by six agency size bands based on user counts: Band 1 (1-25 users), Band 2 (26-100 users), Band 3 (101-500 users), Band 4 (501-1,500 users), Band 5 (1,501-4,000 users), and Band 6 (4,001+ users). Vendors must price fixed-price modules for each band, core unit prices for scalable items (users, mailboxes, endpoints, servers, SharePoint sites, Teams, OneDrive accounts, repositories, and other infrastructure components), and data migration costs based on gigabytes or terabytes migrated. The document does not specify response dates, due dates, site visits, or award dates.
Pricing terms require all costs to be fully burdened and to exclude hardware, software, subscriptions, cloud consumption, licenses, and third-party tools unless separately procured or approved by the State. Band 6 pricing shall be calculated as the Band 5 base price plus incremental unit prices for quantities exceeding Band 5 baselines. Vendors must also price workstream additions (such as Entra ID configuration, Exchange Online migration, Teams migration, decommissioning, and endpoint protection), complexity modifiers (applicable to regulated data, multiple tenants, legacy applications, high data volumes, and other factors, capped at 35% cumulative adjustment unless approved), and post-migration support for up to twelve months, including hypercare, stabilization, and transition support. Vendors must disclose all assumptions, exclusions, exceptions, dependencies, and minimum charges in the Assumptions worksheet, and payment must be tied to accepted deliverables, completed milestones, validated migrations, and accepted documentation. No incumbent vendor or set-asides are identified in this pricing document, and no specific funding amounts or sources are stated.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment E - Lot 3 Pricing.xlsx | XLSX spreadsheet | |
| Solicitation.docx | DOCX document | |
| Attachment C - Lot 1 Pricing.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
1 Instructions
| Solicitation 5400029942 | ||||
| Migration Services - Dept of Admin, Office of Technology & Information Services | ||||
| Attachment D - Lot 2 Pricing Schedule - Instructions to Offerors | ||||
| This workbook is intended to be completed by vendors proposing technical implementation services for Shared Service Adoption and Migration projects. Yellow cells are intended for vendor response. Vendors must choose a response from the options provided in the endor Response Column. If an Offeror selects "Exception Taken" as the Vendor Response, the Offeror shall provide a complete explanation in the Vendor Comments field. Failure to provide a complete explanation may result in the State treating the selection as "nonresponsive" or as taking no exception, at the State's discretion. mulas or calculated values. | ||||
| Item | Instruction | Vendor Response Required | Vendor Response | Comments |
| 1 | Complete all yellow response cells. Do not delete rows, columns, formulas, or worksheets. | Vendor must comply | ||
| 2 | All pricing shall be fully burdened unless otherwise stated in the solicitation or work order. | Confirm Yes/No | ||
| 3 | Prices shall exclude hardware, software, subscriptions, cloud consumption, licensing, and third-party tools unless separately procured or authorized by the State. | Confirm Yes/No | ||
| 4 | Fixed-price modules apply to standard planning, design, setup, validation, documentation, and closeout work. | Acknowledge | ||
| 5 | Unit prices apply to user, mailbox, endpoint, domain, server, site, Team, repository, printer, and other scalable quantities. | Acknowledge | ||
| 6 | Data migration prices apply to migrated or processed GB/TB for email, SharePoint, Teams, OneDrive, file shares, archives, eDiscovery, and DLP-sensitive data. | Acknowledge | ||
| 7 | Complexity modifiers require written State approval and may not be applied automatically. | Acknowledge | ||
| 8 | Hourly labor rates are for approved change orders, optional services, unusual work, and emergency support only unless the State expressly authorizes time-and-materials work. | Acknowledge | ||
| 9 | Payment should be tied to accepted deliverables, completed implementation milestones, validated migrations, and accepted documentation. | Acknowledge | ||
| 10 | Vendor shall disclose all assumptions, exclusions, exceptions, dependencies, minimum charges, and price escalators in the Assumptions tab. | Acknowledge | ||
| Scope basis: Lot 2 Shared Service Adoption and Migration - Technical Implementations, including planning/design, inventory/assessment, security/compliance, AD/Entra integration, support planning, domain consolidation, email, SharePoint, Teams, OneDrive, security/compliance implementation, decommissioning, and post-migration support. |
2 Size Baselines
| Agency Size Bands and Baseline Quantities | |||||||
| This sheet defines agency size by band and provides the relative sizes for the 6 bands defined. Offerors will use these definitions in succeeding worksheets to price their services. Band 5 and Band 6 are defined equally for size. Band 6 efforts shall be priced using the Band 5 base price plus the awarded unit prices for individual items above the Band 5 baseline. For example, an agnecy with 4,325 mailboxes would be priced using the fixed price for a Band 5 agencie plus the individual pricing for 325 additional users, mailboxes, etc. | |||||||
| Band | Agency Size | User Count | Typical Use | Pricing Approach | Column1 | Vendor Notes | Vendor Notes2 |
| Band 1 | Micro | 1-25 | Small boards, commissions, offices | Fixed band pricing | |||
| Band 2 | Small | 26-100 | Small agencies | Fixed band pricing | |||
| Band 3 | Medium | 101-500 | Typical agency | Fixed band pricing | |||
| Band 4 | Large | 501-1,500 | Large agency | Fixed band pricing | |||
| Band 5 | Very Large | 1,501-4,000 | Enterprise agency | Fixed band pricing | |||
| Band 6 | Mega / Enterprise | 4,001+ | Largest agencies or multi-agency projects | Band 5 + incremental unit prices | |||
| Baseline Item | Band 1 | Band 2 | Band 3 | Band 4 | Band 5 | Band 6 Treatment | Vendor Notes |
| Users | 25 | 100 | 500 | 1500 | 4000 | Band 5 + units | |
| Mailboxes | 30 | 125 | 625 | 1875 | 5000 | Band 5 + units | |
| Endpoints | 35 | 150 | 750 | 2250 | 6000 | Band 5 + units | |
| Mobile devices | 10 | 50 | 250 | 750 | 2000 | Band 5 + units | |
| Physical locations | 1 | 2 | 5 | 15 | 30 | Band 5 + units | |
| Servers | 3 | 10 | 40 | 125 | 300 | Band 5 + units | |
| Applications | 5 | 15 | 50 | 150 | 300 | Band 5 + units | |
| AD forests | 1 | 1 | 2 | 3 | 5 | Band 5 + units | |
| AD domains | 1 | 2 | 4 | 8 | 15 | Band 5 + units | |
| M365 tenants | 1 | 1 | 2 | 4 | 8 | Band 5 + units | |
| SharePoint sites | 5 | 20 | 100 | 300 | 750 | Band 5 + units | |
| Teams | 5 | 20 | 100 | 300 | 750 | Band 5 + units | |
| OneDrive accounts | 25 | 100 | 500 | 1500 | 4000 | Band 5 + units | |
| Network file repositories | 3 | 10 | 30 | 100 | 250 | Band 5 + units | |
| Printers / print queues | 3 | 15 | 75 | 250 | 600 | Band 5 + units | |
| DNS zones | 2 | 5 | 15 | 40 | 100 | Band 5 + units | |
| DHCP scopes | 2 | 5 | 15 | 40 | 100 | Band 5 + units | |
| Compliance frameworks | 1 | 1 | 2 | 3 | 4 | Band 5 + units | |
| Third-party integrations | 3 | 8 | 25 | 75 | 150 | Band 5 + units |
3 Base Fixed Prices
| Base Fixed-Price Modules by Agency Band |
| The pricing matrix below mirrors the phases and activities in the Lot 2 lifecycle. Offerors shall comple the blank pricing cells for each band. This pricing fixes a baseline quantity (See Sheet 2) for each component of the Lot 1 lifecycle. Band 6 efforts shall be priced using the Band 5 base price plus the awarded unit prices for users, endpoints, mailboxes, SharePoint sites, Active Directory forests, and other applicable units above the Band 5 baseline.Offerors will price incremental units above the baseline quantities supplied here in Sheet 4. This pricing model avoids unfair pricing where a 50-user agency and a 50-user agency both fall into the same project type, but have drastically different asset and user counts. Vendor shall enter firm fixed prices for standard technical implementation modules by agency size band. Band 6 may be priced as Band 5 plus incremental units unless the State requests a separate fixed price. |
| Module | Description | Band 1 Price | Band 2 Price | Band 3 Price | Band 4 Price | Band 5 Price | Band 6 Formula/Price | Included Assumptions | Vendor Notes |
| 0 | Mobilization, kickoff, project setup, stakeholder identification | Includes initial project setup, communications cadence, and project logistics | |||||||
| B | Communication plan and stakeholder engagement plan | Includes notification channels, approval process, points of contact | |||||||
| C | Inventory and technical assessment package | Includes baseline inventory coordination and assessment documentation | |||||||
| D | Formal design document | Includes scalable design for AD, Entra, M365, MDM, DNS/DHCP, certificate, EPP, DLP | |||||||
| E | Support plan, SLOs, escalation processes, help desk workflow | Includes support model and support-process documentation | |||||||
| F | Migration runbook and cutover plan | Includes technical sequencing, rollback plan, validation steps | |||||||
| G | Pilot migration setup and execution | Includes pilot group preparation, execution, validation, defect remediation planning | |||||||
| H | Testing and validation plan | Includes UAT approach and technical acceptance criteria | |||||||
| I | Training plan and standard training materials | Includes standard user-facing training content and IT staff orientation | |||||||
| J | Final documentation and closeout package | Includes final architecture, runbooks, final state, lessons learned, handoff documentation |
4 Core Unit Pricing
| Core Unit Pricing for Technical Implementation | ||||
| Offerors shall use this worksheet to show their per unit pricing for the items in "Unit". This pricing will be constitute the pricing for additional units above the baseline Band pricing in Sheet 3. This level of specificity is required to keep pricing fair between efforts of differing size. For example, a small agency of 15 individuals may have upwards of 30 mailboxes when group and special use mailboxes are counted. Vendor shall provide fully burdened unit prices for each scalable implementation item. These unit prices govern quantities above baseline and work-order-specific quantities. | ||||
| Unit | Description | Additional Unit Price | Unit Basis | Vendor Notes |
| Per user | General implementation impact, user mapping, account transition, support readiness | Individual user | ||
| Per user account | AD/Entra account mapping, conflict resolution, synchronization validation | Each account | ||
| Per mailbox | Mailbox, calendar, contacts, rules, aliases, and validation | Each mailbox | ||
| Per shared mailbox | Shared mailbox migration and validation | Each shared mailbox | ||
| Per distribution group | Distribution list/group migration, mapping, validation | Each group | ||
| Per Microsoft 365 Group | Group, membership, site association, and policy mapping | Each group | ||
| Per guest account | Guest account mapping, policy configuration, validation | Each guest account | ||
| Per endpoint | Workstation/laptop/tablet endpoint configuration or migration support | Each endpoint | ||
| Per mobile device | iOS/Android MDM enrollment, validation, and support | Each mobile device | ||
| Per server | Physical, Hyper-V, or Broadcom/VMware server migration | Each server | ||
| Per application dependency | AD, LDAP, Kerberos, SSO, service account, or integration dependency | Each dependency | ||
| Per physical location | Site-specific coordination, DNS/DHCP/print/network support | Each location | ||
| Per domain | Custom domain transfer, verification, DNS updates, validation | Each domain | ||
| Per AD forest | Forest-level assessment, trust, synchronization, and consolidation tasks | Each forest | ||
| Per AD domain | Domain-level configuration, mapping, GPO, OU, policy, synchronization work | Each domain | ||
| Per domain controller | DC planning, configuration, validation, or field-office support | Each DC | ||
| Per DNS zone | DNS review, authoring, update, and validation | Each zone | ||
| Per DHCP scope | DHCP update, validation, issue resolution | Each scope | ||
| Per certificate service item | Certificate validation, troubleshooting, coordination | Each item | ||
| Per printer / print queue | Printer mapping, queue validation, configuration support | Each printer/queue | ||
| Per SharePoint site | Site migration, permissions, validation, URL/link updates | Each site | ||
| Per Teams team | Team, channel, files, apps, policies, validation | Each Team | ||
| Per OneDrive account | OneDrive migration, sync validation, user confirmation | Each account | ||
| Per file repository | Shared drive or data repository migration | Each repository | ||
| Per third-party integration | Reintegration, validation, and coordination | Each integration | ||
| Per Power Platform artifact | Power App, Power Automate flow, Power BI workspace/report, or related artifact | Each artifact |
5 Data Migration
| Data Migration Pricing | |||||
| Vendor shall provide pricing for data movement, processing, validation, and migration-related remediation. Use both object-based and data-volume pricing where applicable. | |||||
| Data Type | Pricing Unit | Unit Price | Data Validation Included | Assumed Tooling | Vendor Notes |
| Mailbox data | Per GB migrated | ||||
| Mailbox data | Per TB migrated | ||||
| SharePoint Online data | Per GB migrated | ||||
| SharePoint Online data | Per TB migrated | ||||
| Teams files and related SharePoint data | Per GB migrated | ||||
| Teams files and related SharePoint data | Per TB migrated | ||||
| OneDrive data | Per GB migrated | ||||
| OneDrive data | Per TB migrated | ||||
| Network file share data | Per GB migrated | ||||
| Network file share data | Per TB migrated | ||||
| Archive / retention data | Per GB processed | ||||
| Archive / retention data | Per TB processed | ||||
| Litigation hold / eDiscovery data | Per GB configured or migrated | ||||
| DLP-sensitive data repository | Per repository or per TB |
6 Workstream Additions
| Workstream Implementation Additions | |||||
| The Lot 2 scope is organized by specific technical implementations, but it is within the scope of the services that additional tasks may be required to successfully execute the implementations in a work order. The pricing schedule should reflect that. The items below are anticipated workstreams that may occur in any migration or consolidation effort. Offerors shall price technical implementation workstreams that may be selected independently in a work order. Offerors shall identify identify whether the price is fixed or unit-based. | |||||
| Workstream | Description | Fixed Price | Unit Price | Unit Basis | Vendor Notes |
| Entra ID configuration | Vanity domains, managed domains, users, conditional access, enterprise apps | ||||
| Entra Connect configuration | On-prem AD to cloud synchronization | ||||
| AD trust implementation | Forest/domain trust configuration and validation | ||||
| AD consolidation | OU, GPO, password policy, security groups, distribution groups | ||||
| Legacy LDAP/Kerberos application support | Legacy app dependency remediation support | ||||
| M365 tenant baseline configuration | Exchange, SharePoint, Teams, OneDrive, Groups, policies | ||||
| Exchange Online migration package | Mailbox migration and Exchange validation | ||||
| SharePoint migration package | Site/library/list/content migration | ||||
| Teams migration package | Teams/channels/files/apps/settings | ||||
| OneDrive migration package | User data and client configuration | ||||
| Power Platform migration support | Power Apps, Power Automate, Power BI, Flows | ||||
| Dynamics 365 migration support | Environment and integration support | ||||
| MDM / Intune implementation | MDM, app policies, configuration profiles, patching integration | ||||
| Apple Business Manager implementation | ABM merge, iCloud service accounts, validation | ||||
| Endpoint protection implementation | EPP migration, configuration, automatic updates, validation | ||||
| DLP implementation | DLP configuration across cloud and network boundaries | ||||
| Audit logging and monitoring implementation | Logs, alerts, monitoring validation | ||||
| DNS/DHCP/certificate services implementation | DNS records, DHCP scopes, certificate validation | ||||
| Printer services implementation | Network printer mapping and print service validation | ||||
| Decommissioning package | Source tenant, service, repository, and legacy service retirement |
7 Complexity
| Complexity Modifiers |
| It is anticipated that the various migration and consolidation efforts will have differing complexities based on specific agency requirements. This sheet identifies the most common of those complexities. Offerors shall supply the percentage modifier they will employ for each item. These percentage modifiers will apply against the baseline fixed prices in Sheet 3. However, Offerors shall be aware that, unless expressly approved in the work order approved through the Secondary Competition process (See Attachment A), cumulative complexity adjustments shall not exceed 35% of the applicable base fixed price.Complexity modifiers are not automatic. Vendor shall propose percentage adjustments and describe objective triggers. Application requires written State approval. The solicitation may cap cumulative modifiers. |
| Modifier | Trigger | Proposed % | Maximum % | Applies To | Required Documentation | Vendor Notes |
| Regulated data | CJIS, IRS Pub. 1075, HIPAA, PCI-DSS, ARC-AMPE, MARS-E, or similar | 20% | Affected modules/workstreams | Identify applicable framework and affected systems/data | ||
| Multiple tenants | More than one M365 tenant in scope | 20% | Tenant-related workstreams | List tenants and workloads | ||
| Multiple AD forests/domains | Multiple forests, domains, trusts, or hybrid dependencies | 25% | Identity and domain workstreams | List domains/forests and dependencies | ||
| Legacy application dependency | LDAP, Kerberos, hardcoded domains, unsupported apps | 25% | Application/dependency workstreams | Application inventory and dependency map | ||
| High data volume | Data volume exceeds baseline by more than 50% | 20% | Data migration workstreams | Identify applicable data sets and data inventory. | ||
| High permission complexity | Nonstandard permissions, broken inheritance, sensitive repositories | 20% | Data and collaboration workstreams | Identify environments and describe requirements and activities | ||
| High downtime sensitivity | 24x7, public safety, health, revenue, or citizen-facing operations | 25% | Cutover/migration workstreams | Identify environments and provide justification | ||
| Geographic complexity | More than 10 locations or sites needing local support | 15% | Location-dependent workstreams | Idenfity locations and dependencies | ||
| Compressed schedule | State-approved accelerated schedule | 25% | Affected modules/workstreams | Identify requirements and provide pricing justification | ||
| Significant remediation | Unsupported, misconfigured, undocumented, or insecure environment | 30% | Affected modules/workstreams | Identify vulnerabilities, risks, and anticipated activities. | ||
| After-hours cutovers | Required evening, weekend, or holiday migration windows | 20% | Cutover/migration workstreams | Identify environments and anticipated timelines for each. |
8 Post Migration
| Post-Migration Support Pricing |
| Vendor shall price hypercare, stabilization, and support augmentation for up to 12 months following final migration and consolidation. Pricing should distinguish migration-related support from permanent managed services. |
| Support Model | Description | Monthly Price | Daily Price | Hourly Price | Coverage/Assumptions | Vendor Notes |
| Monthly support - Band 1 | Up to 25 users | |||||
| Monthly support - Band 2 | 26-100 users | |||||
| Monthly support - Band 3 | 101-500 users | |||||
| Monthly support - Band 4 | 501-1,500 users | |||||
| Monthly support - Band 5 | 1,501-4,000 users | |||||
| Monthly support - Band 6 | 4,001+ users; Band 5 + per-user/resource units | |||||
| Onsite technician | Daily onsite technical support | |||||
| Remote support technician | Remote technical support | |||||
| Tier 2 support engineer | Escalated support | |||||
| Identity/M365 engineer | Specialized post-migration troubleshooting | |||||
| Security/compliance engineer | Post-migration security or compliance remediation | |||||
| First 30 days hypercare | Intensive support immediately after cutover | |||||
| Months 2-3 stabilization | Stabilization support after hypercare | |||||
| Months 4-12 transition support | Steady-state transition and escalated support |
9 Support SLAs
| Support Service Levels and Coverage Pricing |
| Vendor shall price support coverage options applicable to migration-related implementation and post-migration support. The State may select coverage levels by work order. |
| Support Level | Coverage | Monthly Price | Cutover Price | Hourly Price | Included Response Commitments | Vendor Notes |
| Standard business hours | Monday-Friday, excluding State holidays | |||||
| Extended business hours | Early morning/evening support | |||||
| Cutover support | Nights/weekends during approved cutovers | |||||
| 24x7 critical support | Critical incident support only | |||||
| Onsite support | Named onsite support resources | |||||
| Remote support | Remote support desk and technical escalation | |||||
| Priority 1 incident | Critical outage or failed cutover support | |||||
| Priority 2 incident | Material degradation or user-impacting issue | |||||
| Priority 3 incident | Non-critical defect or service request |
10 Labor Rates
| Labor Category Rate Card | |||||
| Fixed pricing as laid out in the prior sheets is the method that is used for pricing on this contract. However, the State requires Offerors to provide the fully burdened hourly rates for the personnel types indicated in the Resource Category column to account for approved change orders, optional services, unusual work, emergency support, or where the State expressly authorizes time-and-materials work. Offerors may only invoice for these services when formally approved in writing by the State. | |||||
| Resource Category | Description | Hourly Rate | Minimum Qualifications | Onsite/Remote Rate Difference | Vendor Notes |
| Technical Program Manager | Overall technical implementation leadership | ||||
| Technical Project Manager | Workstream scheduling, coordination, reporting | ||||
| Solution Architect | Overall migration/consolidation architecture | ||||
| Identity Architect | AD, Entra ID, Entra Connect, IAM, SSO | ||||
| M365 Architect | Exchange, SharePoint, Teams, OneDrive, tenant services | ||||
| Exchange Engineer | Mailbox migration and Exchange Online configuration | ||||
| SharePoint Engineer | SharePoint migration, permissions, workflows | ||||
| Teams Engineer | Teams migration, policies, channels, apps | ||||
| OneDrive Engineer | OneDrive migration and sync validation | ||||
| Server Engineer | Physical, Hyper-V, Broadcom/VMware migration | ||||
| Network Engineer | DNS, DHCP, firewall coordination, certificates | ||||
| Endpoint Engineer | Workstation, laptop, tablet, image/configuration support | ||||
| MDM / Intune Engineer | Mobile device, Intune, ABM, app policies | ||||
| Cybersecurity Engineer | EPP, DLP, monitoring, audit, vulnerability remediation | ||||
| GRC / Compliance Specialist | CJIS, IRS 1075, PCI-DSS, HIPAA, SCDIS-200 | ||||
| Data Migration Specialist | File shares, repositories, storage, data validation | ||||
| Power Platform Specialist | Power Apps, Power Automate, Power BI, Flows | ||||
| Dynamics 365 Specialist | Dynamics environment and integration support | ||||
| Help Desk / Support Technician | Migration-related user and endpoint support | ||||
| Trainer / Change Enablement Specialist | Training, user communications, adoption support | ||||
| Technical Writer | Documentation, runbooks, final-state architecture |
11 Eval Scenarios
| Evaluation Pricing Scenarios |
| Vendor shall enter the total proposed price for each scenario using the awarded pricing schedule proposed in this workbook. The weighted evaluated total calculates automatically. Scenario details are illustrative and may be adjusted by the State before release. |
| Input | Scenario A Micro | Scenario B Small | Scenario C Medium | Scenario D Large | Scenario E Very Large | Scenario F Mega | Notes |
| Users | 20 | 80 | 350 | 1200 | 3500 | 6000 | Affected users |
| Mailboxes | 25 | 100 | 425 | 1500 | 4500 | 7500 | Includes shared as estimated |
| Endpoints | 25 | 120 | 500 | 1800 | 5000 | 8500 | Workstations/laptops/tablets |
| Mobile devices | 5 | 30 | 150 | 600 | 1500 | 2500 | iOS/Android devices |
| Locations | 1 | 2 | 5 | 15 | 30 | 50 | Physical sites |
| Servers | 1 | 5 | 25 | 90 | 250 | 500 | Physical/virtual servers |
| AD domains | 1 | 1 | 2 | 5 | 10 | 20 | In-scope AD domains |
| M365 tenants | 1 | 1 | 2 | 3 | 6 | 10 | In-scope tenants |
| SharePoint sites | 3 | 15 | 75 | 250 | 650 | 1200 | Sites/site collections |
| Teams | 3 | 15 | 75 | 250 | 650 | 1200 | Teams objects |
| OneDrive accounts | 20 | 80 | 350 | 1200 | 3500 | 6000 | OneDrive accounts |
| Data volume TB | 1 | 5 | 25 | 100 | 350 | 750 | Estimated total migrated data |
| Compliance complexity | None | IRS Publication 1075 | CJIS and IRS | Multiple frameworks (>2) | Multiple + high complexity | Multiple + 24x7 | Pricing shall reflect stated complexity |
| Scenario | Weight | Vendor Scenario Price | Weighted Price | Pricing Notes / Crosswalk to Workbook | State Evaluation Notes | ||
| Scenario A Micro | 10% | $0.00 | |||||
| Scenario B Small | 15% | $0.00 | |||||
| Scenario C Medium | 25% | $0.00 | |||||
| Scenario D Large | 25% | $0.00 | |||||
| Scenario E Very Large | 15% | $0.00 | |||||
| Scenario F Mega | 10% | $0.00 | |||||
| Weighted Evaluated Total | 100% | $0.00 |
12 Work Order Formula
| Work Order Pricing Formula and Build-Up Template |
| This tab provides a standard build-up format for pricing work orders. Vendors may use this template to show how fixed modules, workstreams, unit quantities, data volume, modifiers, support, and optional services were applied. |
| Pricing Component | Quantity | Unit / Basis | Unit Price | Subtotal | Source Tab / Reference | Vendor Notes |
| Base Fixed-Price Modules | Fixed module subtotal | $0.00 | 3 Base Fixed Prices | |||
| Workstream Implementation Adders | Fixed/unit subtotal | $0.00 | 6 Workstream Adders | |||
| Core Unit Prices | Units as applicable | $0.00 | 4 Core Unit Pricing | |||
| Data-Volume Charges | GB/TB as applicable | $0.00 | 5 Data Migration | |||
| Approved Complexity Modifiers | % applied to approved subtotal | $0.00 | 7 Complexity | |||
| Post-Migration Support | Months/days/hours | $0.00 | 8 Post Migration | |||
| Support SLA Coverage | Months/cutover/hours | $0.00 | 9 Support SLAs | |||
| Approved Optional Services | Hours/units | $0.00 | 10 Labor Rates | |||
| Other State-Approved Charges | Describe basis | $0.00 | Assumptions/Work Order | |||
| Total Proposed Work Order Price | $0.00 | |||||
| Suggested formula: Total Work Order Price = Base Fixed-Price Modules + Workstream Additions + Unit Prices + Data-Volume Charges + Approved Complexity Modifiers + Post-Migration Support + Approved Optional Services. For Band 6, use Band 5 base plus incremental unit prices above Band 5 baselines unless otherwise authorized. |
13 Assumptions
| Vendor Assumptions, Exceptions, and Clarifications | |||||
| Vendor shall disclose all assumptions, exclusions, exceptions, dependencies, minimum charges, escalation terms, proposed deviations, and clarifications. Failure to disclose assumptions may result in the State treating the price as unconditional. The State will accept or decline Offeror assumptions, exceptions, and clarifications at its own discretion. Offerors must determine on their own if they wish to claim assumptions, exceptions, or clarifications since the State may deem Offeror proposals unresponsive as a result. | |||||
| Item # | Category | Assumption / Exception / Clarification | Pricing Impact | Applies To | Vendor Notes |
| 1 | |||||
| 2 | |||||
| 3 | |||||
| 4 | |||||
| 5 | |||||
| 6 | |||||
| 7 | |||||
| 8 | |||||
| 9 | |||||
| 10 | |||||
| 11 | |||||
| 12 | |||||
| 13 | |||||
| 14 | |||||
| 15 | |||||
| 16 | |||||
| 17 | |||||
| 18 | |||||
| 19 | |||||
| 20 | |||||
| 21 | |||||
| 22 | |||||
| 23 | |||||
| 24 | |||||
| 25 | |||||
| 26 | |||||
| 27 | |||||
| 28 | |||||
| 29 | |||||
| 30 |
File details come from the government source that posted it. Updated .