Indiana APS Aug 2021

Open folder in Drive ↗

• {"name":"Project Kick off","start_month":1,"end_month":1}
• {"name":"System Design and Development","start_month":null,"end_month":3}
• {"name":"Sprint 1-5","start_month":4,"end_month":8}
• {"name":"System Testing","start_month":null,"end_month":9}
• {"name":"User Acceptance Testing / Data Migration","start_month":null,"end_month":11}
• {"name":"Roll Out","start_month":null,"end_month":12}

• {"name":"Project Kick off","value":195000}
• {"name":"System Design and Development","value":36000}
• {"name":"Sprint 1","value":36000}
• {"name":"Sprint 2","value":36000}
• {"name":"Sprint 3","value":36000}
• {"name":"Sprint 4","value":36000}
• {"name":"Sprint 5","value":36000}
• {"name":"System Testing","value":36000}
• {"name":"User Acceptance Testing","value":36000}
• {"name":"Data Migration","value":48000}
• {"name":"Roll Out","value":64000}

agencycounties_or_officeslicense_valuenon_opportunity_reasonsaas_valuethird_party_valueuser_countuser_count_notevalue_by_yearwarranty_value

Two competing files existed: 'APS RFS - Pricing Model.xlsx' (a milestone/deliverable cost-proposal template matching the agency's RFS format, chosen as primary per the 'Pricing' naming rule) and 'Indiana APS Implementation Plan' (a separate Google Sheet with a role-level staffing grid whose price total, $1,134,672, does NOT match the chosen file's $989,996 -- recorded as a variant). Company='Prime' in the Implementation Plan's staffing rows is literally the placeholder text used in that sheet (not a real firm name) for four US-based roles; those roles were NOT Cardinality itself, so 'Prime' is recorded as prime and 'Cardinality' as an implied subcontractor providing the India-based roles, though the actual prime firm's name is not stated anywhere in the sheet. hours_basis_per_month=168 derived the same way as Guam (Price = Total person-months x Rate x 168, internally consistent across all rows) -- not an explicitly labeled cell. Software/Hosting Fees section spans 2 fiscal years (Year 1 + Year 2) while the DDI milestone schedule spans only 12 months and M&O is only 12 months, so contract_term_months=24 reflects the software-cost horizon rather than a stated single 'contract term' figure.