Exhibit_18_-_Instructions_for_Integrated_Project_Schedule.docx

Exhibit 18 – Instructions for Integrated Project Schedule

Purpose This Exhibit evaluates the Bidder’s ability to develop and maintain a comprehensive, executable Integrated Project Schedule (IPS) that governs all activities across implementation, transition, and operational readiness. The IPS shall serve as the authoritative schedule for delivery and shall reflect a realistic, dependency-driven approach to achieving all project milestones.

general instructions

· Page Limit: Not applicable (schedule artifact)

· Format: Excel

· The IPS shall be submitted as a standalone attachment

· Supporting narrative (if provided) shall not exceed 2 pages

· The schedule must be sufficiently detailed to demonstrate sequencing, dependencies, and resource alignment

· High-level timelines or summary graphics alone will not be considered responsive

Response expectations The Bidder shall provide an Integrated Project Schedule that includes:

· Project Phases and Structure The IPS shall reflect all phases of delivery, including:

· Design, Development, and Implementation (DDI Stages 1–5)

· Technology Transition (TT)

· Maintenance and Operations (M&O) onboarding

Include:

· Clear phase boundaries and transitions

· Major workstreams aligned to each phase

· Logical sequencing of activities across phases

· Key deliverables and sub deliverables

· Milestones and Key Events The IPS shall include all major milestones, including at a minimum:

· CMS approvals and certification milestones (e.g., ATC)

· Data migration and validation milestones

· Integration readiness milestones (CMS, issuers, OKEPs)

· User Acceptance Testing (UAT) completion

· Operational readiness and go/no-go decision points

· Open Enrollment (OE) readiness

· Production go-live and stabilization milestones

· Dependencies and Critical Path The IPS shall clearly identify:

· Task dependencies across workstreams and phases

· External dependencies (e.g., CMS, issuers, OKEPs, State inputs)

· Critical path activities and schedule drivers

· Assumptions related to dependencies and timing

· Resource and Staffing Alignment The IPS shall demonstrate alignment between scheduled activities and proposed staffing.

Include:

· Resource assignments or role-based allocations to major tasks

· Alignment with the proposed staffing model across DDI, TT, and M&O

· Identification of peak resource periods

· Integration and EDE Coordination Activities The IPS shall include activities required to support coordination across the EDE ecosystem.

Include:

· Integration development and testing with CMS, FDSH, issuers, and OKEPs

· Partner onboarding and certification activities

· Cross-entity testing and validation activities

· Coordination milestones with external stakeholders

· Testing and Release Activities The IPS shall include:

· Testing phases (functional, integration, UAT, performance)

· Environment readiness and promotion activities

· Release planning and deployment milestones

· Defect resolution cycles and validation checkpoints

· Transition and Migration Activities (FFM to SBE) The IPS shall include activities required to transition from the Federally Facilitated Marketplace (FFM) to the State-Based Exchange (SBE).

Include:

· Data extraction, transformation, and migration activities

· Coordination with CMS and external partners

· Handling of in-flight transactions

· Validation and reconciliation activities

· Cutover planning and execution

· Operational Readiness and Stabilization The IPS shall include:

· Operational readiness validation activities

· Service center and operations activation

· Training and knowledge transfer activities

· Hypercare and stabilization period

· Transition to steady-state operations

REQUIRED ARTIFACTS

The Bidder shall include:

· Excel version of the schedule (required)

2 | Page image1.png