Scenario 2 · a Microsoft Project file, Full mode

The same Microsoft Project file, Full mode: the Standard engine's options, critical paths, deadlines, splits, and where it stops.

Full mode opens every menu. The badge says Standard: the engine that opens Microsoft Project files. Filter, Critical only: 31 of 1,673 activities are critical now, drawn in red.

The Advanced block is greyed: this engine does not use it. Its options: hours per day and week, splits, honoured constraints, and the slack that counts as critical.

Critical means slack at or under a threshold. Set it to 2 days: more turns red. Schedule, and the near-critical tasks join in: 113 of 1,673 are critical now.

A day is 8 hours, a week 40: durations like 1.0d, 3.0d and 6.0d count in those days. An inspection's Type is Milestone: one point in time. Standard has just that one milestone type.

A summary row rolls up its children: from 15 Sep to 30 Sep, the span of its tasks. Deadline 29 Sep on Skim Coat Walls never moves it; the finish past it shows as float -1.0d.

Set data date asks Save as first: the edits so far become a PC.o Schedule, the file stays. Type the new data date, 19 Sep, tick Update progress as planned, and press Apply.

Split in-progress tasks is on: Mold Inspection, 50 percent done, has its rest from the data date on. The four Move toggles are off here: completed or remaining parts, back or forward to the status date.

The Standard engine behaves similarly to Microsoft Project in its calendar hours, single milestone, summary rows and splits. Manually scheduled, ticked on Drywall Ceiling, gives it its own start and finish: both 26 Sep.

On Standard, Details is a pop-up: Details view set to Follow engine gives this layout. Where it stops: XER and P6 XML are greyed, because those files are written from the Advanced engine.

Next in the Guide: a P6 file, Simple mode, and the look-ahead hand-off.

Taken from the video’s English captions.