A list of terms, keywords, abbreviations, and acronyms used in reporting system.
01. ASR (As Received)
Refers to ‘source data’. Used in the context of the source of data, documents, information, etc. for the purpose of forensic scheduling, forensic accounting, and variation analysis.
02. As-Planned
A project schedule that depicts planned values of start and finish dates for activities or work packages.
Also referred to as ‘planned’, as in planned scope, planned schedule, planned cost. May also be referred to as ‘baseline’, as in baseline scope, baseline schedule, and baseline cost. Also, see BSV (baseline schedule version) below.
03. Baseline
A set of clearly defined reference values for a project.
In project management, the word ‘baseline’ can be used to describe reference values for the project’s scope (i.e. baseline scope), for the project’s time (i.e. baseline schedule), and for the project’s cost (i.e. baseline cost).
04. As-Built
A project schedule which depicts actual values of start and finish dates for activities or work packages. The effects of variation events, change instances, and other impacts may also be reflected in the as-built schedule.
Also referred to as ‘actual’, as in actual scope, actual schedule, actual cost.
05. CPM
Critical Path Method, a method for project scheduling
06. Fragnet
A partial or fragmentary network. A fragnet may be understood as a small portion of a schedule network.
07. Data Date (DD)
The progress point, or the ‘as-of date’ for progress reporting of activities in a project schedule. Also referred to as the status date or cut-off date.
08. Publish Date
The date when the schedule was run and updated irrespective of the data date in the schedule.
09. P/C
Planned or Contractual date used as a notation in dates
10. cd for CD
Calendar Day
11. wd or WD
Work Day, as defined by calendar(s) in a project’s schedule settings.
12. Windows
Periods of time in which the project schedule is reviewed
13. GC
General Conditions refers to the General Conditions sections of the Contract Documents
14. SGC or SC
Supplementary General Conditions (or sometimes Supplementary Conditions) refers to the Supplementary General Conditions sections of the Contract Documents
15. EOT
Extension of Time
16. REA
Request for Equitable Adjustment
17. MS100 Reporting System (Stoneboy)
A modular reporting framework having 100 standardized data points (milestones) that are used to capture, and report the beginning or end of important steps in a project’s life cycle.
18. MSpec (Stoneboy)
Modular Specifications for Scheduling, Contact Administration, Variation Analysis and Claims Management developed by Stoneboy
Data Formats
Data format for Microsoft Project software. May also refer to a standalone project schedule file created in Microsoft Project. MPP is an abbreviation for Microsoft Project Plan.
Data format for Oracle Primavera P6 software. May also refer to a standalone project schedule file created in Oracle Primavera P6. XER is an abbreviation for eXport Eagle Ray, Primavera’s proprietary data export format.
Types of Duration in Scheduling
The as-planned duration, or budgeted duration for an activity or work package as per the baseline schedule version. Also referred to as as-planned duration, or planned duration.
The actual duration for an activity or work package at a given time reference.
The total working time from the actual start date to the actual finish date for a completed activity or work package, or the total working time from the actual start date to the data date for in-progress activity or work package.
The remaining duration for an activity or work package at a given time reference.
The total working time from the remaining start date to the remaining finish date for an activity or work package.
The total working time from the current start date to the current finish date for an activity or work package. It is a combination of the actual duration and remaining duration for an activity or work package at a given time reference.
Schedule Version
An umbrella term for a schedule submission such as a baseline schedule, a schedule update, a recovery schedule, or a scenario planning schedule.
A baseline schedule version. Commonly referred to as ‘baseline’. Also referred to as as-planned schedule version or planned schedule version.
May refer to an approved baseline schedule version. An approved baseline schedule version may be the first approved version, a subsequent version, or the latest approved version of the project schedule. A project’s progress may be tracked to multiple baseline schedule versions.
A current schedule version. The latest published schedule version. Used in the context of forensic scheduling, and time variation analysis.
Last Schedule Version
Alphanumeric Naming Convention is a convenient format to monitor the number of schedule submissions, schedule version history, and version control – as well as, to obtain a snapshot of the project’s performance for every schedule submission. As part of the schedule version history, the source of schedule submissions is also tracked.
Alphanumeric Naming Convention (also Schedule File Name Convention)
Alphanumeric Naming Convention is a convenient format to monitor the number of schedule submissions, schedule version history, and version control – as well as, to obtain a snapshot of the project’s performance for every schedule submission. As part of the schedule version history, the source of schedule submissions is also tracked.
Variation
A ‘cause’ for variation.
A ‘cause’ which makes an activity or work package to experience an exception or exclusion from its baseline scope, baseline schedule, and/ or baseline cost.
Such ‘cause’ may be a delay or an impact; a change; an event, a milestone, or an activity; which may trigger a scope variation, a time variation, and/ or a cost variation.
Used in the context of Causation – causes and effects of variation(s) on activities and work packages in a project.
| No. | Head 1 | Head 2 |
|---|---|---|
| 01 | Variation Any difference between the circumstances and/ or content of the contract work as carried out, compared with the circumstances and/ or content under which the work is described in the contract documents as required to be or intended to have been carried out.
| Variation Analysis (Stoneboy) Scope Variation from baseline scope, |
| 02 | SV (Scope Variation ) (Stoneboy) Scope variation can mean an increase in scope (additional scope of work, extra work), or a decrease in scope (scope reduction). | SVA (Scope Variation Analysis) (Stoneboy) Assessment of approved or involuntary changes in the project scope. Assessment of scope variations from the baseline scope. |
| 02 | TV (Time Variation ) (Stoneboy) Time variation may refer to an increase in time (delay), or a decrease in time (schedule gain). Also see Delay, and Critical Delay. | TVA (Time Variation Analysis ) (Stoneboy) |
| 02 | CV (Cost Variation) (Stoneboy) Cost variation may refer to an increase in cost (i.e. cost overrun due to changes, delays, etc.), or a decrease in cost (cost reduction). Cost Variation may include additional direct cost, indirect cost, overhead cost, cumulative cost impact of variation events, and project administration. | CVA (Cost Variation Analysis) (Stoneboy) Analysis of baseline cost versus actual/ as-built / at completion cost over a period of time. Identification, assessment, quantification, and summarization of approved and/or involuntary changes in the project budget. |
A type of time variation for an activity or work package prior to its start. The difference between the actual or forecast start date, and the late start date of the baseline schedule for an activity or work package.
A negative value of SDV means a schedule gain (an earlier start as compared to baseline schedule), and a positive value of SDV means a delay.
SDV is identified as a delay, but it does not necessarily qualify as a critical delay. Also see FDV, Gap, and Odex.
A type of time variation for an activity or work package prior to its finish. The difference between the late finish date of the baseline schedule, and the actual or forecast finish date for an activity or work package.
A negative value of FDV means a schedule gain (an earlier finish as compared to baseline schedule), and a positive value of FDV means a delay.
FDV is identified as a delay, but it does not necessarily qualify as a critical delay. Also see Gap, SDV, and Odex.
A type of delay for an activity or work package before its start. It is the duration of unplanned inactivity between the actual finish of a driving predecessor activity, and the actual start of a driven successor activity.
Gap is different than Lag (the amount of planned wait time between two activities). Gap specifically scrutinizes periods of unplanned inactivity between two actualized activities.
Gap may or may not be concurrent with SDV.
Gap is identified as a delay, but it does not necessarily qualify as a critical delay. Also see SDV, FDV, and Odex.
Original Duration Variation, or Original Duration Extension.
An overrun of the original, as planned, or budgeted duration of an activity.
Odex is usually concurrent with FDV. Also see Gap, SDV, and FDV.
Delay
The applicable value of the impact from an activity’s critical delay towards the critical delay for the project completion milestone (or other project milestones). In simpler terms, the portion of critical delay of activity contributes towards the total critical delay.
A calculation for applicable critical delay may take into account factors such as the origin of delay (primary, or carryover delay), out-of-sequence work, intermittent work, concurrent delays, the primacy of delay, and other considerations for CPM network calculations, etc.
Applicable critical delay may also be referred to as adjusted critical delay, network adjusted critical delay, applicable critical delay, etc.
A time variation becomes a critical delay when an activity consumes its entire initially available total float. A value of critical delay can be computed for every activity for which the initially available total float has been consumed.
Usually, an activity with a critical delay will transmit a partial, or at times the full impact, of a time variation on the completion of the project completion milestone (or other project milestones) within a stipulated time period.
Total critical delay is typically defined as the value of time variation for the project completion milestone (or other project milestones).
Delay may be defined as a time variation from the baseline (or as-planned) allocated time for an activity. A time variation may be identified at the start, during the progress, or at the completion of an individual activity.
A time variation or delay in an activity (at its start, progress, or completion) may not impact the project completion milestone (or other project milestones) within a stipulated time period.
A time variation which brings forward the project completion milestone (or other project milestones). Antonym of critical delay.
A situation where a project may be subject to two or more time variations at the same time (or even in the same timeline).
The causes of time variations may be apportionable to different parties (the owner’s team, or the contractor’s team, etc.); or the causes may be apportionable to the same party.
Delays which may be deemed foreseeable or within the contractor’s control, or may otherwise be apportionable to the contractor are categorized as Non-Excusable Delays.
Typically, for Non-Excusable delays, neither extension of time, nor compensation for damages can be sought by the contractor.
Delays that may be deemed unforeseeable, and beyond the control of the contractor are categorized as Excusable Delays.
Excusable delays are further divided into the following:
- Excusable Only Delay (or Excusable-Non Compensable)
For Excusable only delays (or Excusable Non-Compensable), the contractor may seek an extension of time as per their entitlement as defined by relevant contract sections.
An act or neglect on the part of the Owner / Consultant deemed excusable only delays for which an extension of time can be sought by the contractor as per the contractual entitlements.
Strikes, lock-outs, fire, unusual delay by common carriers, force majeure, or by a cause beyond the Contractor’s control are deemed excusable only delays for which an extension of time can generally be sought by the contractor.
- Compensable Delay (or Excusable-Compensable)
For qualifying Compensable delays (or Excusable-Compensable), the contractor may be eligible to seek both extension of time, as well as compensation for damages as per their entitlement as defined by relevant contract sections.
Generally, Compensability results in the non-liability of the contractor.
Certain acts, events or circumstances beyond the control of the parties.
Extended actual finish date of critical activity that due to fault of Contractor which is not limited to the following:
- Insufficient resources (Manpower and Equipment) required for a particular period
- Rework due to poor workmanship and improper protection of completed tasks.
- Poor Planning resulting in out-of-sequence phasing of work leading to inefficiency
- Poor construction methods and techniques resulting in rework and inefficiency.
- Performance that is below the target rate of production as per the baseline schedule without a valid reason.
- Negligence in Safety
- Delay in purchasing and delivery of required materials
- Failure to adhere to Contractual requirements
Delay Analysis Methodology
A methodology and technique in analyzing time variation events that forecasts or predicts a delay’s effect on a project’s completion date.
Review, and analyses of schedule versions over periods of time. In this methodology, schedule progress is compared between periods of time or windows. The duration of Windows can be defined based on specific project reporting requirements.
Also see Variation Analysis, Time Variation Analysis (TVA).
Review, and analyses of schedule versions over periods of time. In this methodology, schedule progress is compared between periods of time or windows. The duration of Windows can be defined based on specific project reporting requirements.
Also see Variation Analysis, Time Variation Analysis (TVA).
The Impacted As-Planned (IAP) delay analysis methodology involves the insertion of delay events (time variation) into a baseline schedule to determine the hypothetical impact of such events.
This methodology involves the creation of an impacted as-planned schedule or impacted schedule by modifying the baseline schedule to include new activities and logic to represent time variation. The difference between the project completion milestones in the baseline schedule, and the impacted schedule provides the value of total critical delay.
This methodology is simple and does not require an as-built schedule. However, it is considered a hypothetical model as it does not take into account actual/ as-built schedule data.
The As-Planned vs As-Built (APAB) delay analysis methodology is a retrospective methodology for schedule delay analysis. This methodology involves comparing the baseline schedule with the as-built schedule (or a schedule that reflects progress through a particular point in time).
APAB is sometimes also referred to as the Planned vs Actual methodology.
As-Built Critical Path (ABCP) delay analysis methodology
As-Built Critical Path (ABCP) delay analysis methodology
0 Comments