A Baseline is a comparison reference, it can be a contractual approved baseline, the original or an approved revision, it can also be a reference to a “what if” reference job looking into possible alternatives to recover your schedule, it can be a non contractual baseline as for example your prior update as to compare progress between updates.
In MS Project all baseline data is stored in the same project file contrary to other software, but you can save every update as a separate file, and you should. You have to be careful about your baselines; MS Project is tricky if you make an update of your job and then have to add an approved baseline with a data date prior to your last update as you can only add to baselines your current job. You can copy and paste data from two versions of your job so you can get Baseline Data transferred this way, time consuming but can be done.
Member for
17 years 3 months
Member for17 years3 months
Submitted by Samer Zawaydeh on Wed, 2010-02-24 11:13
The is the definition stated in the Standard Practice Standard for Scheduling issued by the Project Management Institute:
Baseline: The approved time phased plan (for a project, a work breakdown structure component, a work package, or a schedule activity), plus or minus approved project scope, cost, schedule, and technical changes. Generally refers to the current baseline, but may refer to the original or some other baseline. Usually used with a modifier(e.g. cost baseline, schedule baseline, performance measurement baseline, technical baseline).
In short, it is what the Engineer approves at the start of the project.
As in all software a "baseline" is a snapshot of the programme held in a different file which will underly the tasks and show the differences when changes are made.
In delay analysis the Baseline is the original contract programme before events are impacted.
Member for
21 years 8 monthsRE: No Subject Specified
A Baseline is a comparison reference, it can be a contractual approved baseline, the original or an approved revision, it can also be a reference to a “what if” reference job looking into possible alternatives to recover your schedule, it can be a non contractual baseline as for example your prior update as to compare progress between updates.
In MS Project all baseline data is stored in the same project file contrary to other software, but you can save every update as a separate file, and you should. You have to be careful about your baselines; MS Project is tricky if you make an update of your job and then have to add an approved baseline with a data date prior to your last update as you can only add to baselines your current job. You can copy and paste data from two versions of your job so you can get Baseline Data transferred this way, time consuming but can be done.
Member for
17 years 3 monthsRE: No Subject Specified
Dear frederick,
The is the definition stated in the Standard Practice Standard for Scheduling issued by the Project Management Institute:
Baseline: The approved time phased plan (for a project, a work breakdown structure component, a work package, or a schedule activity), plus or minus approved project scope, cost, schedule, and technical changes. Generally refers to the current baseline, but may refer to the original or some other baseline. Usually used with a modifier(e.g. cost baseline, schedule baseline, performance measurement baseline, technical baseline).
In short, it is what the Engineer approves at the start of the project.
With kind regards,
Samer
Member for
19 years 10 monthsRE: No Subject Specified
Hi Frederick
As in all software a "baseline" is a snapshot of the programme held in a different file which will underly the tasks and show the differences when changes are made.
In delay analysis the Baseline is the original contract programme before events are impacted.
Best regards
Mike Testro