SuperWave-XER | Settings

Checking your session...

Project: Select or create a project

ProjectVersion

Data DateNot read yet

Evidence detailsChecking

Project IDNot assignedData Date sourceLoading the accepted schedule date.Checking effective role and scopeBounded evidence only · original schedule source remains protected

Evidence boundary: observed inputs support bounded derived views; unsupported conclusions remain withheld.

Configuration contractCompare each saved rule with its draft independently

Direction can be stated as stricter, unchanged, or looser. Finding counts require a new Schedule Health run.

No synthetic
Pressure score

Project controls

Settings that shape the review

Pick the active project, confirm the date basis, then tune DCMA and Directed EV targets before schedulers run Schedule Health.

Saved

Active projectLoading projects...

Date basisRanked native date

DCMA profileDefault targets

Directed EV15 / 20 pp

Workspace presentationSection priority comes from effective account permissions; display density remains a personal preference.

loading role

Permissions change access. Presentation composition only reorders and discloses authorized content.

Review role and permissions

1. Project contextRules are shared by project owner/admin; personal viewing choices stay local.

ProjectActivity focusDate basisSample limit

Choose a project to load its dates and target rates.

Where these controls are used

Project settings feed bounded review surfaces; they do not recalculate results until those surfaces run.

Project dates→Date GateDCMA rules→Schedule HealthEV scope→PerformanceConfirmed targets→Milestones

2. Project dates and alignmentThese are commitments, not values inferred from uploaded files.

Contracted substantial completionContract/internal milestones

3. Project DCMA targetsOne row per DCMA-14 check, laid out like P6's Check Schedule dialog. Every target is on screen, beside the check it decides and the value it ships with.

16 of 16 rows on

DCMA-14 check targets for this project
DCMA #	Check	Over	Pass when	Ships with
1	Missing logicActivities missing predecessors or successors		%	< 5%
2	LeadsRelationships with a lag duration of less than 0		%	< 1%
3.1	Positive lagsOwner concern #2Relationships with a positive lag duration		%	< 5%
3.2	Long lagsOwner concern #2Relationships with a lag duration greater than	h	%	< 5% · over 352 h
4	Relationship typesThe majority of the relationships should be Finish to Start		%	> 90%
5.1	Hard constraintsOwner concernConstraints that prevent activities from being moved		%	< 1%
5.2	Soft constraintsOwner concernConstraints that do not prevent activities from being moved		%	< 5%
6	High floatOwner concern #1Activities with total float greater than	h	%	< 1% · over 352 h
7	Negative floatActivities with a total float less than 0		%	< 1%
8	High durationActivities that have a remaining duration greater than	h	%	< 5% · over 352 h
9	Invalid datesActivities with Invalid progress dates		%	< 1%
10	Resources / costActivities that do not have an expense or resource assigned		%	< 1%
11	Missed tasksActivities scheduled to finish later than the project baseline		%	< 5%
12	Critical path testDelays an activity on the critical path and checks the project finish moves with itContinuity only asks whether the driving chain is unbroken, which it always is; keep it only if this project's reporting depends on the previous verdicts.			Perturbation
13	Critical path length indexHow much float the critical path has against the time left to the finishGraded against the CPLI band the report states, not a project target		≥ 0.95 fixed band	No project target
14	Baseline execution indexTasks finished against the tasks the baseline planned to finish by the data date			> 0.95

3.1 The boxed number is the DCMA-14 check. P6 splits check 3 into 3.1 and 3.2, and check 5 into 5.1 and 5.2. Untick a row to switch that check off for this project; a check that is off is not run, and is not a pass.

Choose a project to see how its targets compare with the ones P6 ships.

See the checks these targets decide

High float and high duration default to 352h at 8h/day. This page controls project targets; it does not create certification claims.

Threshold comparisonCompare each draft target with the value loaded for this project.

Browser preview

No finding forecast. A threshold can be stricter, unchanged, or looser. Only a new Schedule Health run can measure findings.

Run Schedule Health

4. Directed EV 14.1 effort gapProject-specific triage lines for effort/adherence review.

Talk-now threshold (pp) Quietly-ahead threshold (pp)

These labels guide review conversations only; they do not change backend earned-value math.

Project settings loadedChange a field to preview unsaved settings.

Choose a project to load its dates and DCMA targets.

Review status and evidence steps

Decision roadmapEvidence readiness, not project progress

Steps update from visible page evidence. Blocked and withheld states name the boundary; no completion percentage is inferred.

Checking evidence

01Choose the projectNot started
02Trace downstream dependenciesNot started
03Compare each ruleNot started
04Save a precise receiptNot started

Discussion questions and talking points

Discussion guideQuestions and talking points

Observed → derived → withheld remains explicit. These talking points stay tied to the selected evidence; they are not an unrestricted database question box.

configuration preview not finding prediction

Observed selected source valuesDerived visible inputs and formulaWithheld unsupported or unavailable

Current context

Unavailable context remains explicitly not supplied.

Discussion talking point

Using only selected Settings evidence, answer: What targets and dates govern this project? Cite fields or sections from project key, saved value, draft value, rule direction, downstream consumer; separate observed from derived and name missing support.

This talking point preserves the page’s evidence and authority boundary.

Settings

Settings content

Settings that shape the review