TRANSCRIPTEvery word of the video, as text.
Read the transcript
The engine gives you dates; PC.o's analysis tells you what they mean. Here, how edits reach the reports, and how a baseline keeps the promise.
On an upload, Run analysis asks to Save as first. The upload stays; the copy is yours. Run analysis re-runs PC.o's analysis on the current dates. The schedule's reports are overwritten on their next run.
The flash says Analysis queued. It appears on the Files page when done: patience, then Files. The copy now has its own analysis. Its row menu offers Analysis, separate from the upload's.
Edit again and the pill says the analysis is behind: run on one revision, the schedule at another. On the Files page the word is Out of date; hover it and the tooltip names both revisions.
Schedule options, Analysis reruns, sets when it reruns: on demand, when the editing session ends, or never automatically. Tools, Compare Schedules: the upload is the Target, the copy the Update, as with any two schedules.
Activity Comparison Information counts one activity added. The rest of the dashboard has an entry of its own. Schedule, Baselines: another schedule, or this one, pinned at a revision. The copy starts with As uploaded.
Pick this schedule, call it Contract baseline, press Add: pin before you change. Nothing is copied. Both now sit in the list; the radio picks the active one, and None switches the strip off.
The strip under the bar keeps the baseline while the bar moves on. The chip names which. View, Columns: choose the Baseline preset.
The grid gains Baseline start and finish, the two variances, and Baseline TF: the schedule against the pin. Views, Bar styles: Baseline bars makes the strip follow the active baseline.
Export with a baseline, and PC.o asks whose planned dates go in the file: the baseline's, or this schedule's own.
That was analysis and baselines. Next in the Guide: scheduling that survives the site, from the article.
Taken from the video’s English captions.