Implementation Waves
Group associations into waves for phased go-live, set go-dark and go-live dates, and use the wave detail page as the hub for a cohort's progress.
Overview
A wave is a named group of associations organized for phased go-live within a branch migration. One branch migration typically has several waves. Waves carry the go-dark and go-live dates and are the unit of go-live sign-off. This is Phase 4 of the process.
Waves are planned by Implementation and the branch together: the branch provides wave preferences — which associations belong in which wave — and Implementation plans the go-dark and go-live dates.
Manage them at Setup → Implementation Waves, and view the branch's associations at Setup → Portfolio.
Waves do not gate ingestion
Ingestion is branch-wide. Source data is ingested for the whole branch as it becomes available, regardless of how associations are grouped into waves. Waves organize go-live, not ingestion, so you can plan and adjust them in parallel with ingestion.
Creating a wave
- Go to Setup → Implementation Waves and create a wave.
- Give it a name, an optional description, a go-dark date, and a go-live date.
Plan waves so each is a manageable cohort, allow buffer time between them for issue resolution, and set go-live dates that account for standardization, review, and validation time.
Assigning associations
Assign associations to a wave in either of two ways:
- Individual — use the Map to Wave dialog from the Portfolio table.
- Bulk — use the Add Associations dialog (multi-select) on the wave detail page.
An association belongs to a wave so that its go-live can be planned and signed off as part of that cohort.
The wave detail page
The wave detail page is the hub for a wave's progress. It shows:
- The association roster for the wave.
- The wave's go-dark and go-live dates.
- Onboarding progress across the wave.
- The cross-entity validation roll-up (see Validation).
- The go-live sign-off section (see Migration Tracking & Sign-off).
Working a wave as a cohort
Most app surfaces — the Review grids, the Validation panels, and the Standardization mapping grids — can be filtered by wave. That means a wave's data can be worked and inspected together throughout the process, from standardization through validation to the final go-live decision.
Related
- Standardization — map the wave's source codes to standards.
- Review — spot-check the wave's data quality.
- Validation — validate each association and review cross-entity panels.
- Migration Tracking & Sign-off — the two-party go-live gate.
Field Mapping Notes
Record what source data exists for every entity and field, so the ingestion team knows what to transform and gaps surface early.
Data Availability & Configuration
Confirm each entity has been ingested, see its migration state, and view each association's ingested billing and delinquency configuration.