Source XER
Ontario_Community_College_current.xer
CPP
Critical Path PartnersForensic schedule analysis
DWG · CAB-29R03 / SHEET A-00
Collapsed As-Built · MIP 3.8 · Subtractive
Collapsed As-Built / But-For Analysis
Collapsed As-Built Dashboard Ontario Community College - B2 (Demo Data) · AACE RP 29R-03 §3.8 (Modeled / Subtractive / Single Simulation)
Dual-Method Status
AGREE
Gap 4.8% · methods converge ≤5%
Impact (wd)
20 wd
Events
3
Method
MIP 3.8
Anchor check: the schedule’s stored finish and the CPM-recomputed finish agree (2026-09-30).
As-Built Finish
2026-09-30
post-impact actual
But-For Finish
2026-09-01
cumulative subtractive (counterfactual date)
Cumulative Impact
20wd
working days · subtractive (MIP 3.8)
Events Analyzed
3
delay events in pass
Findings
Removing all 3 delay events from the as-built network pulls the project finish from 2026-09-30 to 2026-09-01, attributing 20 working days to the events analyzed. The removals act on the driving chain A4180 → A4190 → A4240; the collapse sequence at A-03 shows the finish stepping as each event is removed. The result is dual-method validated: the MIP 3.3 windows analysis reports 21 wd against this report's 20 wd, a gap of 4.8% (AGREE).
A-01
Methodology
AACE RP 29R-03 §3.8 · Modeled / Subtractive / Single SimulationMethod
For each documented delay event, the as-built network is cloned, the event's impact removed (by either shorten, reducing affected activity durations, or remove, deleting the affected activities and their TASKPRED edges), and the CPM forward pass re-run. The resulting project finish is the but-for [event] date. The differential between the as-built finish and the but-for finish is the event's attributed impact under the Modeled / Subtractive method.
Configuration. Default removal method is shorten (a per-event override applies when an event specifies its own removal_method). Contractor filter: No, every event in the input list contributes to the cumulative pass.
Default Removal
shorten
Contractor Filter
No
Base Schedule
Single
Method
MIP 3.8
Modeled
Subtractive
Single Simulation
Subtractive
Single Simulation
29R-03 §3.8
Basis of measurementHow to read the numbers in this report
Day unit
Working days
Every day count in this deliverable is in working days. No calendar-day figure is displayed. Where a contract clause is quoted verbatim in calendar days, the computed equivalent is given in working days alongside.
Calendar
Standard
Deltas are counted on the activity's own P6 calendar via work_day_delta. Where no project calendar is available the documented fallback is Monday to Friday with no holidays, and that fallback is disclosed on the affected figure.
Date fields read
P6 Start and Finish columns only
Scheduling mode as read
retained logic (SCHEDOPTIONS sched_retained_logic=Y)
A positive number is working days attributed to the removed event
Convention: event-attribution: impact = as-built finish - but-for finish (positive = working days attributed to the removed event)
Impact is computed one way only: as-built finish minus but-for finish, counted in working days on the stated calendar. Removing a delay pulls the but-for finish earlier, so a genuine impact is always positive. A negative value would mean the removal pushed the finish later, which flags a modeling error, not time recovered.
Citations
- AACE RP 29R-03, Forensic Schedule Analysis Recommended Practice, §3.8 Modeled/Subtractive/Single Simulation (Collapsed As-Built / But-For), §3.9 Modeled/Subtractive/Multiple Base.
- SCL Delay & Disruption Protocol, 2nd ed., §11.5: TIA (forward) vs Collapsed As-Built (backward).
- Wickwire et al., Construction Scheduling, 4th ed., Ch. 10: But-For analysis; dual-method convergence as evidence of method reliability.
- Bramble & Callahan, Construction Delay Claims, 4th ed., §9.05: Collapsed As-Built methodology; practitioner-consensus dual-method convergence cut-offs.
Input-uncertainty caveat
The subtractive method is sensitive to the input impact_days values. A ±20% input uncertainty on the per-event impact durations can swing the cumulative result by a similar amount. CPP practice (not an AACE 29R-03 §3.8 requirement) is to run a schedule risk analysis (Monte Carlo with duration uncertainty distributions) against the input durations and report the P50 ± P90 range alongside the deterministic figures shown here. This dashboard reports a deterministic point estimate; opposing counsel should be expected to attack the input uncertainty on cross-examination. See the schedule-risk-analysis skill output for the corresponding probabilistic envelope.
Concurrent-Delay Caveat
When two delays affect the project simultaneously on overlapping paths, the subtractive method (this skill) and windows analysis (forensic-delay-analysis MIP 3.3) can produce different attribution. The cumulative pass treats all delays as additive; if the project has concurrent owner-vs-contractor delays or two parallel critical chains, run a concurrent-delay analysis (forensic-delay-analysis windows method, AACE 29R-03 §3.3) and reconcile against the output below. Dual-method gaps >10% are a strong signal that concurrent delays are present.
A-02
Per-Event Subtractive Pass
clone · remove impact · re-run forward passFor each delay event below, the as-built network was cloned, the event's impact removed using the indicated method, and the CPM forward pass re-run. The resulting "but-for" finish and computed impact are shown.
A-02Subtractive register, all events listed
3 events, all listedExport CSV
| Event ID | Name | Affected Activities | Removal | As-Built Finish | But-For Finish | Impact (wd) | Responsible | Contractor? |
|---|---|---|---|---|---|---|---|---|
| E1 | AHJ / commissioning-agent hold on MEP and elevator commissioning | A4180 | shorten | 2026-09-30 | 2026-09-23 | 5 wd | Owner | N |
| E2 | Owner-directed re-sequence of integrated systems testing | A4190 | shorten | 2026-09-30 | 2026-09-23 | 5 wd | Owner | N |
| E3 | Contractor punch-list and deficiency re-work | A4240 | shorten | 2026-09-30 | 2026-09-16 | 10 wd | Contractor | Y |
Removal Basis & Finish-Driver Disclosure , all events listed
For each event: the duration removed and the basis used, plus what drives the but-for finish. A completed activity whose finish is on or before the data date cannot pull a successor whose start is pinned at the data-date floor, so the impact can legitimately be 0 even when a duration was removed. That sensitivity is disclosed below.
E1 · AHJ / commissioning-agent hold on MEP and elevator commissioning
Duration removed & basis: A4180: 15.0d→10.0d on CPM duration_days
Finish driver after removal: But-for finish is driven by activity 'A4240' via the live driving chain. The removed duration sits on that chain, so the collapse pulled the finish from 2026-09-30 to 2026-09-23.
E2 · Owner-directed re-sequence of integrated systems testing
Duration removed & basis: A4190: 10.0d→5.0d on CPM duration_days
Finish driver after removal: But-for finish is driven by activity 'A4240' via the live driving chain. The removed duration sits on that chain, so the collapse pulled the finish from 2026-09-30 to 2026-09-23.
E3 · Contractor punch-list and deficiency re-work
Duration removed & basis: A4240: 11.0d→1.0d on CPM duration_days
Finish driver after removal: But-for finish is driven by activity 'A4240' via the live driving chain. The removed duration sits on that chain, so the collapse pulled the finish from 2026-09-30 to 2026-09-16.
A-03
Cumulative Roll-Up
all events removed together · single subtractive passAs-Built Finish
2026-09-30
post-impact actual
Cumulative But-For Finish
2026-09-01
all events removed
Cumulative Impact (Subtractive)
20 wd
as-built minus but-for (working days)
Collapse Sequence · Finish StepsA4180 → A4190 → A4240
As-built finish (all delays in) Finish after each additional removal
Each row removes one more event, in input order, and re-runs the CPM; the final row is the cumulative but-for finish. Marker position is scaled in working days from the as-built finish. The per-event register at A-02 removes each event alone, so its but-for dates legitimately differ from these progressive steps when events share the driving chain.
Per-Event Impact DistributionE1 → E3
Largest single-event impact Subordinate impactE1 = 5 wd · E2 = 5 wd · E3 = 10 wd
Bars are scaled to the largest single-event impact; bar length is relative, not an absolute magnitude of delay.
A-04
Dual-Method Gap
MIP 3.3 (Windows) vs MIP 3.8 (Subtractive)Convergence StatusAGREE · 4.8% GAPThreshold≤ 5%
MIP 3.3 (Windows)
21 wd
observational dynamic (working days)
MIP 3.8 (Collapsed As-Built / Subtractive)
20 wd
modeled subtractive (working days)
Gap (Δ)
1 wd
windows minus subtractive (working days)
Gap %
4.8%
of windows result
AGREE
Both methods converge within the 5% practitioner-consensus tolerance. The forensic conclusion is dual-method validated.
Thresholds: AGREE ≤ 5% · WARN 5-15% · INVESTIGATE > 15%. Bands are forensic-engineering practitioner consensus per Bramble & Callahan §9.05 and Wickwire et al. Ch. 10. They are NOT codified numeric cut-offs in AACE RP 29R-03 (which permits more than one method in §5 but describes no cross-check and publishes no numeric tolerance percentages).
A-05
Diagnostics & Warnings
68 diagnostics · 7 detectors, all listed68 diagnostics across 7 detector codes. The triage strip below states, per detector, what its findings mean for the reliability of the but-for result; the full registers follow, grouped by detector, every entry listed.
| Detector | ALERT | WARN | INFO | What it means for the but-for result |
|---|---|---|---|---|
| cpm/out-of-sequence | 11 | 0 | 0 | Work progressed out of logic order, so the as-built chain the removal walks may not be the chain the work actually followed; the removed duration can land on the wrong path. |
| cpm/post-data-date-actual | 0 | 41 | 0 | Actual dates are recorded after the data date, so the as-built network is partly forward-looking and the finish the collapse measures against may rest on unstatused work. |
| cpm/constraint-noop | 0 | 7 | 0 | A date constraint affected (or failed to affect) the pass as noted. A constrained date can hold the but-for finish in place and mask logic-driven movement. |
| cpm/constraint-applied | 0 | 3 | 0 | A date constraint affected (or failed to affect) the pass as noted. A constrained date can hold the but-for finish in place and mask logic-driven movement. |
| cpm/completed-succ-skipped-in-backward | 0 | 0 | 4 | Backward-pass float through completed chains is not meaningful; the forward-pass but-for finish is unaffected. |
| collapsed-calendar-basis | 0 | 0 | 1 | States which calendar the working-day figures are counted on (or that it had to be guessed). A different calendar changes working-day magnitudes, not the but-for dates themselves. |
| collapsed-schedule-options | 0 | 0 | 1 | States the P6 scheduling mode and relationship-lag calendar every CPM pass ran under, and how they were read from the export (SCHEDOPTIONS row, or the P6 default when the export omits it). Informational; a different mode or lag calendar would move the computed dates. |
cpm/out-of-sequence · 11 entries, all listed
ALERT
cpm/out-of-sequence
Activity A2290 is complete but 1 predecessor(s) have no actual_start (retained-logic anomaly): A2220
ALERT
cpm/out-of-sequence
Activity A1130 started 2025-08-26 but 1 predecessor(s) started AFTER it (retained-logic anomaly): A1100.2 (started 2025-08-28)
ALERT
cpm/out-of-sequence
Activity A1630 started 2025-05-28 but 1 predecessor(s) started AFTER it (retained-logic anomaly): A1050 (started 2025-06-16)
ALERT
cpm/out-of-sequence
Activity A1110 started 2025-08-01 but 1 predecessor(s) started AFTER it (retained-logic anomaly): A1100.2 (started 2025-08-28)
ALERT
cpm/out-of-sequence
Activity A1480 started 2025-07-22 but 1 predecessor(s) started AFTER it (retained-logic anomaly): A1360.2 (started 2025-08-25)
ALERT
cpm/out-of-sequence
Activity A1490 started 2025-07-22 but 1 predecessor(s) started AFTER it (retained-logic anomaly): A1370,1 (started 2025-08-08)
ALERT
cpm/out-of-sequence
Activity A2510 started 2025-08-22 but 1 predecessor(s) started AFTER it (retained-logic anomaly): A1100.2 (started 2025-08-28)
ALERT
cpm/out-of-sequence
Activity A2520 started 2025-08-11 but 1 predecessor(s) started AFTER it (retained-logic anomaly): A2510 (started 2025-08-22)
ALERT
cpm/out-of-sequence
Activity A2530 is complete but 1 predecessor(s) have no actual_start (retained-logic anomaly): A5230
ALERT
cpm/out-of-sequence
Activity A2530 started 2025-08-11 but 3 predecessor(s) started AFTER it (retained-logic anomaly): A5220 (started 2025-08-28), A2550x (started 2025-08-21), A2490x (started 2025-08-14)
ALERT
cpm/out-of-sequence
Activity A2600 started 2025-08-15 but 1 predecessor(s) started AFTER it (retained-logic anomaly): A5250 (started 2025-09-04)
cpm/post-data-date-actual · 41 entries, all listed
WARN
cpm/post-data-date-actual
Activity A4340 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A3960 (started 2025-07-07)
WARN
cpm/post-data-date-actual
Activity A3960 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A3920 (started 2025-07-04)
WARN
cpm/post-data-date-actual
Activity A1130 has 2 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A1100.1 (started 2025-08-08), A1100.2 (started 2025-08-28)
WARN
cpm/post-data-date-actual
Activity A1680 has 2 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A1100.1 (started 2025-08-08), A1100.2 (started 2025-08-28)
WARN
cpm/post-data-date-actual
Activity A1110 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A1100.2 (started 2025-08-28)
WARN
cpm/post-data-date-actual
Activity A1480 has 2 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A1360.1 (started 2025-07-22), A1360.2 (started 2025-08-25)
WARN
cpm/post-data-date-actual
Activity A1490 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A1370,1 (started 2025-08-08)
WARN
cpm/post-data-date-actual
Activity A1500 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A12380.1 (started 2025-07-22)
WARN
cpm/post-data-date-actual
Activity A2150 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A1580 (started 2025-08-01)
WARN
cpm/post-data-date-actual
Activity A2160 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A1570 (started 2025-07-11)
WARN
cpm/post-data-date-actual
Activity A1360.2 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A1360.1 (started 2025-07-22)
WARN
cpm/post-data-date-actual
Activity A1470.1 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A1470 (started 2025-07-15)
WARN
cpm/post-data-date-actual
Activity A1480.1 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A1480 (started 2025-07-22)
WARN
cpm/post-data-date-actual
Activity A1540.1 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A1540 (started 2025-07-11)
WARN
cpm/post-data-date-actual
Activity A3930 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A4340 (started 2025-07-14)
WARN
cpm/post-data-date-actual
Activity A4410 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A4390 (started 2025-08-11)
WARN
cpm/post-data-date-actual
Activity A2430x has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2420x (started 2025-07-14)
WARN
cpm/post-data-date-actual
Activity A2440x has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2430x (started 2025-07-15)
WARN
cpm/post-data-date-actual
Activity A2470x has 2 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2440x (started 2025-07-25), A2460x (started 2025-07-24)
WARN
cpm/post-data-date-actual
Activity A2490x has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2480x (started 2025-08-13)
WARN
cpm/post-data-date-actual
Activity A2460x has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2450x (started 2025-07-18)
WARN
cpm/post-data-date-actual
Activity A2480x has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2470x (started 2025-08-08)
WARN
cpm/post-data-date-actual
Activity A1100.2 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A1100.1 (started 2025-08-08)
WARN
cpm/post-data-date-actual
Activity A2370 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A5070 (started 2025-07-14)
WARN
cpm/post-data-date-actual
Activity A2380 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2370 (started 2025-07-16)
WARN
cpm/post-data-date-actual
Activity A2390 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2370 (started 2025-07-16)
WARN
cpm/post-data-date-actual
Activity A2400 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2390 (started 2025-07-22)
WARN
cpm/post-data-date-actual
Activity A2410 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2400 (started 2025-07-23)
WARN
cpm/post-data-date-actual
Activity A2420 has 3 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2380 (started 2025-07-23), A2410 (started 2025-07-24), A1660 (started 2025-07-03)
WARN
cpm/post-data-date-actual
Activity A2430 has 2 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2400 (started 2025-07-23), A1660 (started 2025-07-03)
WARN
cpm/post-data-date-actual
Activity A2450 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2430 (started 2025-07-23)
WARN
cpm/post-data-date-actual
Activity A2460 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2450 (started 2025-07-23)
WARN
cpm/post-data-date-actual
Activity A2470 has 3 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2430 (started 2025-07-23), A2450 (started 2025-07-23), A2460 (started 2025-07-25)
WARN
cpm/post-data-date-actual
Activity A2490 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2470 (started 2025-07-28)
WARN
cpm/post-data-date-actual
Activity A2500 has 2 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2470 (started 2025-07-28), A2490 (started 2025-07-28)
WARN
cpm/post-data-date-actual
Activity A2510 has 2 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A1100.1 (started 2025-08-08), A1100.2 (started 2025-08-28)
WARN
cpm/post-data-date-actual
Activity A2520 has 2 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2500 (started 2025-07-29), A2510 (started 2025-08-22)
WARN
cpm/post-data-date-actual
Activity A5220 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2520 (started 2025-08-11)
WARN
cpm/post-data-date-actual
Activity A2530 has 5 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2520 (started 2025-08-11), A5220 (started 2025-08-28), A2550x (started 2025-08-21), A2520x (started 2025-07-31), A2490x (started 2025-08-14)
WARN
cpm/post-data-date-actual
Activity A5250 has 1 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A2530 (started 2025-08-11)
WARN
cpm/post-data-date-actual
Activity A2600 has 2 predecessor(s) with actual_start AFTER the data_date (2025-07-01). Actuals after the schedule update window are a retroactive-edit signature: A5250 (started 2025-09-04), A2530 (started 2025-08-11)
cpm/constraint-noop · 7 entries, all listed
WARN
cpm/constraint-noop
SNET on A2550x suppressed by actual_start (P6 forward-pass semantics: a recorded actual start governs ES)
WARN
cpm/constraint-noop
SNET on A2140 suppressed by actual_start (P6 forward-pass semantics: a recorded actual start governs ES)
WARN
cpm/constraint-noop
SNET on 2170 suppressed by actual_start (P6 forward-pass semantics: a recorded actual start governs ES)
WARN
cpm/constraint-noop
SNET on A2160 suppressed by actual_start (P6 forward-pass semantics: a recorded actual start governs ES)
WARN
cpm/constraint-noop
SNET on A2150 suppressed by actual_start (P6 forward-pass semantics: a recorded actual start governs ES)
WARN
cpm/constraint-noop
SNET on A2190 suppressed by actual_start (P6 forward-pass semantics: a recorded actual start governs ES)
WARN
cpm/constraint-noop
SNET on A2420 suppressed by actual_start (P6 forward-pass semantics: a recorded actual start governs ES)
cpm/constraint-applied · 3 entries, all listed
WARN
cpm/constraint-applied
SNET on A2560x pushes ES from 2025-07-02 to 2025-08-18
WARN
cpm/constraint-applied
SNET on A3850 pushes ES from 2025-09-08 to 2025-09-10
WARN
cpm/constraint-applied
SNET on A2770 pushes ES from 2025-12-29 to 2026-04-13
cpm/completed-succ-skipped-in-backward · 4 entries, all listed
INFO
cpm/completed-succ-skipped-in-backward
A5230: 1 completed successor(s) skipped in backward propagation (retained-logic semantics; completed activities do not pull predecessor LF backward through historical dates).
INFO
cpm/completed-succ-skipped-in-backward
A1360.2: 1 completed successor(s) skipped in backward propagation (retained-logic semantics; completed activities do not pull predecessor LF backward through historical dates).
INFO
cpm/completed-succ-skipped-in-backward
A2220: 1 completed successor(s) skipped in backward propagation (retained-logic semantics; completed activities do not pull predecessor LF backward through historical dates).
INFO
cpm/completed-succ-skipped-in-backward
A2550x: 1 completed successor(s) skipped in backward propagation (retained-logic semantics; completed activities do not pull predecessor LF backward through historical dates).
collapsed-calendar-basis · 1 entry, all listed
INFO
collapsed-calendar-basis
Working-day figures (impact_workdays_collapsed, cumulative_impact_workdays and the dual-method gap) are stated on calendar 'Standard', resolved from PROJECT.clndr_id. The file carries 1 calendar(s).
collapsed-schedule-options · 1 entry, all listed
INFO
collapsed-schedule-options
CPM passes run under scheduling mode 'retained_logic' (SCHEDOPTIONS sched_retained_logic=Y) with relationship lag on 'rcal_Predecessor' (SCHEDOPTIONS sched_calendar_on_relationship_lag=rcal_Predecessor).
Generated
2026-09-09
Source XER
Ontario_Community_College_current.xer
Data date
2025-07-01
Calendar
Standard
Method
AACE 29R-03 §3.8
Standards
SCL §11.5 · Wickwire Ch.10 · Bramble & Callahan §9.05
Input files: Ontario_Community_College_current.xer SHA-256 7ed1cd8309b1752af74ec9c8d2fa11fbc9a58d4e065630a2589809ed3780ca10
Collapsed As-Built / But-For Analysis · AACE RP 29R-03 §3.8 (Modeled/Subtractive/Single Simulation) · Generated 2026-09-09 · Engine cpm-engine v2.9.43Reproducible · AACE 29R-03 §3.8 / SCL §11.5