Critical Path Methods
Critical Path Methods
Critical Path Methods
U.S. Department
of Veterans Affairs
Facilities Management
design
DECEMBER 2012
Version 1.0
December 1, 2012
2.
3.
INTRODUCTION .................................................................................................. 3
1.1.
1.2.
1.3.
Introduction ................................................................................................................. 9
2.2.
2.3.
Assumptions .............................................................................................................10
2.4.
2.5.
2.6.
Deliverables ..............................................................................................................12
3.1.1
3.1.2
3.1.3
3.1.4
Design .......................................................................................................................14
Procurement .............................................................................................................15
Construction .............................................................................................................15
Activation Planning/Beneficial Occupancy...........................................................16
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
Volume I - 1
Version 1.0
December 1, 2012
3.10
3.11
3.12
Narrative Report.......................................................................................................24
3.13
3.14
5.
6.
EXHIBITS ........................................................................................................... 28
Exhibit I.1. Level 1 Schedule for a Typical VAMC Project ...................................................29
Exhibit I.2. Level 2 Schedule for a Typical SD-1 VAMC Project ........................................30
Exhibit I.3. Level 2 Schedule for a Typical Construction Phase in VAMC Project...........31
Exhibit I.4. Level 3 Schedule for a Typical SD-1 VAMC Project ........................................33
Exhibit I.5. Level 4 Schedule (60-day look ahead) for a Typical SD-1 VAMC Project ....39
Exhibit I.6. Sample Phasing Narrative for a Typical VAMC Project ...................................45
Exhibit I.7. Cost Projection S-Curve for a Typical Design Phase in VAMC Project ........51
Exhibit I.8. Sample Outline for a Schedule Narrative Report ..............................................52
Exhibit I.9. Longest Path for a Typical Design Phase in VAMC Project............................53
Exhibit I.10. Schedule Impact Analysis Sample Change Order Fragnet .........................59
Volume I - 2
Version 1.0
December 1, 2012
1. INTRODUCTION
1.1.
Volume I - 3
Version 1.0
December 1, 2012
the A/E with a set of approaches, techniques and methods that have been proven over
time as acceptable.
It is also recognized that these guidelines cannot cover every situation one may
encounter when creating schedules, reviewing schedules or analyzing changes or
delays. These guidelines may serve as a starting point for analyzing these unique
situations.
This document is solely intended as a guide, it is not intended to dictate means and
methods. The A/E is responsible to develop the means and methods and correlate with
the VA requirements.
1.2.
Applicable Documents
Document Location
http://www.cfm.va.gov/contract/ae/
aesubmaj/
http://www.cfm.va.gov/til/dManual/
http://www.cfm.va.gov/til/spec/
Refer to http://www.pmi.org/
Volume I - 4
1.3.
Version 1.0
December 1, 2012
Activity or
Event:
Activity,
Controlling:
Activity, Critical:
Activity ID:
Activity Network
Diagram:
A/E:
Architect/Engineer.
Bar Chart:
Calendar Day:
Completion
Date, Contract:
Completion
Date,
Scheduled:
Constraint:
Critical Path:
The Longest Path through the project network that determines the
project duration.
Critical Path
Method (CPM):
Volume I - 5
Version 1.0
December 1, 2012
The first day in the initial or baseline schedule and the first day for
performance of the work remaining in the Monthly Schedule
Update or Revised Schedule. (May also by defined as the date
from which a schedule is calculated).
Duration,
Original:
Duration,
Remaining:
Float, Free:
The amount of time an activity can be delayed and not delay its
successor(s).
Float, Total:
The amount of time an activity can be delayed and not delay the
project completion date.
Fragnet
Holidays:
Version 1.0
December 1, 2012
considered to be a holiday.
Longest Path:
Milestone:
Narrative
Report:
Open End:
Predecessor:
Relationship:
Relationships
between
Activities:
a. Finish to Start - The successor activity can begin only when the
predecessor completes.
b. Finish to Finish - The finish of the successor activity depends
on the finish of the predecessor.
c. Start to Start - The start of the successor activity depends on
the start of the predecessor.
d. Start to Finish - The successor activity cannot finish until the
current activity starts.
Schedule:
Schedule,
Baseline:
Successor:
Version 1.0
December 1, 2012
by its predecessor.
TIL:
Work
Breakdown
Structure (WBS):
Working
Schedule:
Work Package:
Volume I - 8
2.
SCHEDULING METHOD
2.1.
Introduction
Version 1.0
December 1, 2012
Scheduling methods provide the framework within which schedule models are
developed. Critical Path Method (CPM) is the VAs chosen methodology for developing
project schedules.
In accordance with PG 18-15, the Architect/Engineer (A/E) shall furnish and maintain an
Integrated Project Master Schedule (IPMS) utilizing a computer based network analysis
scheduling software. The IPMS shall be prepared using the precedence diagramming
method (PDM) and shall depict the major phases of the project. The IPMS will provide a
summary level schedule for the Procurement, Construction, and Activation phases of
the project. The A/E will expand the level of detail for the Design Phase to show in detail
how the A/E plans to execute the design.
The A/E shall develop a logic-based network of design activities with empirically derived
durations for execution in a realistic and practical manner, in order to establish a
meaningful critical path. There must not be any open ends other than the project start
and finish milestones. Constraints must be restricted to those that represent external or
internal conditions that cannot be feasibly accomplished with activity logic.
The A/E shall also identify and assign resources to the design schedule activities.
2.2.
Scheduling Software
The A/E shall propose to the VA, a scheduling tool that is capable of assembling the
schedule model and providing the means of adjusting various parameters and
components that are typical in a modeling process. It shall be capable of producing the
reports required by the VA contract documents. The proposed scheduling tool shall
have the capability to:
Select the type of relationship (such as finish-to-start or finish-to-finish)
Add lags between activities (applied only on an exception basis)
Apply resources and use that information along with resource availability to
adjust the scheduling of activities
Add start and finish constraints
Capture a specific schedule as a baseline or target schedule
Compare the most recent schedule against the previous one or against a target
or baseline to identify and quantify trends or variances
Define longest path activities
Volume I - 9
2.3.
Version 1.0
December 1, 2012
Assumptions
During development of the IPMS, the A/E shall identify any necessary assumptions and
document those assumptions properly. Typical assumptions for a VAMC project may
include:
Normal workday involves an 8-hour shift, Monday through Friday excluding major
holidays.
Allow 45 Calendar Days after receipt of NTP for the A/E to submit a complete
CPM Schedule.
Value Engineering occurs at the end of submission milestones.
The final CPM schedule in its original form shall contain no contract modifications
or changes which may have been incurred during the final CPM schedule
development period and shall reflect the entire contract duration as defined in the
bid documents.
All permits will be obtained prior to the Notice-To-Proceed.
The VA Medical Center will provide input during each phase of the design.
No single design activity shall exceed 20 work days, except for which the Project
Manager and/or the Contracting Officer may approve the showing of a longer
duration.
The A/E will adequately plan his/her work according to the sequence of design
provided in the contract documents and prosecute the work in a continuous
fashion.
2.4.
In developing a schedule, at a minimum, the A/E shall adapt the following best
practices:
Clearly define activities supported by specific quantity and scope.
Provide good logic based on realistic sequence of work agreed by A/E team.
Do not use negative lags. (See VA NAS Specification).
Do not use a finish to start relationship with a lag. Instead, an activity must be
added to represent actual scope of work.
A project shall have one beginning and one end except for multiple phased
projects. All activities shall have a predecessor and successor except the
projects start and finish milestones. No open ends will be permitted.
Durations of work activities shall not exceed the update cycle (20 work days).
Longer durations may be used provided there is quantitative means for
measuring progress.
Volume I - 10
Version 1.0
December 1, 2012
2.5.
Risk Analysis
The A/E shall conduct the schedule risk analysis (SRA) based on the detailed design
activities, identifying major schedule risk areas and recommended risk mitigation plans.
The risk analysis shall be conducted by a person or firm skilled in developing schedule
risk analysis based on the (PDM) CPM schedule techniques for major projects,
preferably in the major health care related projects. The cost of this service shall be
included in the A/Es proposal.
The Contracting Officer has the right to approve or disapprove the person or firm
designated to perform the risk analysis. The risk analysis exercise shall be performed or
updated during each design phase as defined in VA PG 18-15 or as directed by the VA
Contracting Officer.
According to VA PG 18-15, the A/E shall provide for the VA review and comment, the
Risk Management Plan (risk register, recommendations for addressing major risks,
mitigation plans, and other related documents) included in the Manual for Preparation of
Risk Management Plan for Medical Center Project which is a supplement to this
guideline.
As depicted in Table 2 of the RMP, the schedule risk analysis is required over a period
of time throughout the different phases (Pre-Design, Schematic Design, Design
Development and Construction Documents) of the project.
Volume I - 11
2.6.
Version 1.0
December 1, 2012
Deliverables
VA PG 18-15 requires multiple submissions of the CPM schedule over a period of time
that evolves throughout the project. These deliverables are in addition to the monthly
schedule updates that the A/E shall submit in accordance with the VA A/E scheduling
specification section 01 32 16.01. The below table identifies the phases and the level of
detail in which the A/E shall submit the CPM schedules for the VA review and comment:
IPMS Deliverable
Design Phase
Pre-Design
Volume I - 12
Design Phase
Construction Documents
(CD-1)
Version 1.0
December 1, 2012
IPMS Deliverable
Updated Project Master Schedule and Detailed
Design Schedule.
Updated Schedule Risk Analysis.
Phasing narrative, plans on reduced site plans
and diagram marked on full size drawings for VA
review.
Updated Project Master Schedule and Detailed
Design Schedule.
Updated Schedule Risk Analysis.
Updated Phasing narrative, diagram and plans on
reduced site plans marked on full drawings for VA
review.
Updated Project Master Schedule and Detailed
Design Schedule with increased detail.
Updated Schedule Risk Analysis with increased
detail in new risks and mitigation plan.
Updated Phasing narrative and Phasing diagram.
Full-size contract drawings for the CPM phasing
plans.
Updated Project Master Schedule with increased
detail.
Updated Schedule Risk Analysis identifying new
risks and mitigation actions, particularly in
construction areas.
Updated Phasing Narrative and Phasing Diagram.
Full-size contract drawings for the CPM phasing
plans.
Table 2 (Continued)
Volume I - 13
Version 1.0
December 1, 2012
3.1
The A/E shall review and fully understand the projects scope documents. These
documents provide the background, information and understanding needed to develop
the IPMS. The goal of this process is to ascertain that all aspects of the project scope
have been adequately defined and captured in the IPMS.
The A/E shall identify and proactively communicate with the entire project stakeholders,
identify all the potential risks involved in each phase of the project, from Pre-Design to
Activation. The A/E shall also understand the constraints such as zoning requirements
and permitting (environmental).
The IPMS shall depict the complete life cycle of the VA project. A typical VA project life
cycle is as follows:
3.1.1 Design
This phase contains the sequence of design activities as detailed in the A/E
specifications from Notice-To-Proceed (NTP) to the Design Review Meeting in the
Construction Documents (CD1) phase. It also encompasses the minimum submission
requirements for the detailed design phase of the Integrated Project Master Schedule
(IPMS). This phase captures one conceptual submission, two schematic Design (SD1
and SD2) submissions, two Design Development (DD1 and DD2) submissions and two
Construction Documents (CD1 and CD2) submissions. The A/E will be responsible for
preparing a detailed design schedule for the project. Refer to Exhibit I.1 depicting a
Volume I - 14
Version 1.0
December 1, 2012
Level 1 Project Master Schedule. A complete sample of IPMS is available on the VAs
Technical Information Library.
3.1.2
Procurement
This phase occurs when a typical VAMC project formally transitions from design
preparation into construction mobilization. This phase includes the bidding and award
processes. The projects schedule and budget are finalized in this phase. Typical
milestone activities included in this phase are in the following sequence:
Construction Bid Document Printed
Construction Package Advertised
Necessary Addenda Issued
Bids Received and Tabulated
Analysis of Low Bid and Bidders Qualifications
VA Award Construction Contract
Contractor Furnish Bonds and Insurance
Contractor Executed and Certified by VA
Construction Notice To Proceed
3.1.3
Construction
The construction phase presents the actual physical construction of the project. The A/E
shall develop a preliminary construction schedule for the purpose of construction
phasing and duration. The A/E shall define project constraints, requirements of
stakeholders, operation and facility requirements. The A/E shall come up with the
construction phasing in collaboration with the VA. The proposed schedule of the
construction phase is expected to be a Level 2 schedule in the IPMS. It commences
with the issuance of the Construction Notice to Proceed, followed by mobilization of the
General Contractor to the site, then the physical construction, commissioning of building
systems and finally ends with activities associated with Substantial Completion.
According to VA PG 18-15, during the Pre-Design phase, the A/E in collaboration with
the VA and all the project stakeholders shall develop an outline of phasing requirements
including anticipated overall construction schedule, considerations that influence
phasing, anticipated duration of each phase of construction and a narrative establishing
users vision, goals, and desired image. In this preliminary phase, major milestones for
the construction schedule shall be discussed by the project stakeholders.
The A/E shall provide a written narrative to outline phasing requirements and sequence
for the construction schedule. The A/E shall justify the phasing and construction
Volume I - 15
Version 1.0
December 1, 2012
duration suggested. The phasing shall be supported by enough details including trade
activities, long lead items and VAMC operational requirements.
All areas of the project included in Construction shall be identified as part of a phase.
Each phase description shall include constraints particular to that phase, what other
phases must precede it, other contractors working in that phase, and any VA
moves/relocation which must precede the start of the phase or phases. If equipment
and other removable items require storage and relocation by the VA, these
requirements shall be listed in the phasing narrative. Special phasing constraints which
may be common to the project during construction should be listed at the end of the
narrative and not within each individual phase description.
The A/E shall provide a written list of systems divided by technical discipline, including
temporary systems by phase. Additionally, the A/E shall develop a phasing diagram
using CPM that shows the sequence and interdependencies of phases within the
project.
As the design progresses from pre-design through construction documents, the A/E is
responsible to submit an increased level of detail of the construction schedule during
each phase. Exhibit I.6 is a sample of a phasing narrative for a typical VAMC project.
3.1.4
The A/E shall communicate with the project stakeholders to understand the complete
requirements of a VAMC facility. In this phase, VA medical equipment is installed and
activated and the owners personnel are recruited, trained and mobilized to run the
hospital operation.
The Activation phase is very critical to the completion of the project as this is when the
beneficial occupancy is achieved and the VAMC or other facilities are ready for veterans
use. The VA activation planning phase should commence at the end of Schematic
Design (SD-2) phase and should be in parallel with the design and construction phases,
overlapping the tail end of construction as necessary.
3.2
The A/E shall assign a unique name and identification number to identify the specific
project and each version of the schedule shall have a unique version number or ID. This
is essential to allow the proper archiving of project schedules and audit processes.
Volume I - 16
3.3
Version 1.0
December 1, 2012
The Integrated Project Master Schedule WBS encompasses the entire project at Level
1. Subsequently, Level 2 of the WBS subdivides the project into major phases that
comprise Design, Procurement, Construction and Activation. Level 3 subdivides each of
the major work items into work packages as follows:
Pre-Design, Schematic Design SD1 & 2, Design Development DD1 & DD2 and
Construction Documents CD1. Level 4 of the WBS shows the twenty seven (27)
different design elements. Level 5 of the WBS breaks down the design elements into
specific work activities.
The A/E shall develop the WBS to capture the complete project scope in accordance
with VA PG 18-15. A typical VA project WBS is as follows:
WBS Level
Title
Project
II
III
IV
Description
The Project (e.g. VA IPMS)
Major Phase
Work Package
Activity
Version 1.0
December 1, 2012
Version 1.0
December 1, 2012
capturing and documenting actual field costs. These include not only base contract
work, but also changes, problems, and areas of potential disputes. Such schedules can
also aid in capturing manpower data and measuring labor productivity.
3.4
Milestones are key events or significant points in time during the life of a project. Once
the A/E has a feel for the overall scope of the project, he or she can begin to determine
the projects major and minor milestones. Milestones should have zero duration and be
used as the bench marks to measure progress against.
They can also reflect the start and finish points for various project events or conditions
and/or identify external constraints or interim deliverables. At a minimum the detailed
design schedule, developed by the A/E shall contain start and finish milestones
culminating to each design phase (Pre-Design, SD1, SD2, DD1, DD2, and CD1). This
will facilitate tracking of the A/E progress for each contractual deliverable.
3.5
The A/E shall determine, in conjunction with the project team, the work periods which
need to be selected for the design phase of the project. These work periods may be
different for specific activities or portions of the project including resources. The A/E
shall consider the following prior to establishing a calendar:
The proposed number of working days in a week
The number of hours to be worked each day
Any periods of scheduled overtime work or non-working time (e.g. shutdowns)
The holidays to be observed during the life of the contract (by day, month, and
year)
All of these elements play a major role in determining the number and structure of the
project calendars required for the IPMS. The use of multiple calendars introduces
significant complexity to the calculation of float and the critical path. However, while
scheduling is simplified by the use of a single calendar, the A/E shall be cognizant that
one calendar may not suffice for effectively managing the project.
The A/E shall utilize project calendars which are adequate and reasonable to perform
the scope of work, based on normal working times. The project calendar then may be
used as the primary or default calendar for the project. A limited number of customized
calendars may then be used for areas of the project requiring different working times.
Volume I - 19
Version 1.0
December 1, 2012
The sample IPMS includes a 5-day work week calendar w/holidays for all activities in
the detailed design schedule and 7-day workweek calendar with no holidays for the
summary level construction activities.
3.6
Activity Identification/Coding
The A/E shall assign unique number to each activity/event with numbers ranging from 1
to 99998 only for the activity identification. The A/E shall utilize software where once the
activity ID is created, it will not change due to the addition or deletion of activities, this is
paramount to guarantee the traceability of the schedule
The CPM schedule activities should be generally coded in such a way to reflect
disciplines, phase or location of the work. The A/E shall develop a coding structure to
facilitate the selection and sorting of the schedule data, and to facilitate the
development and maintenance of the IPMS, as well as meeting the project reporting
requirements. A well designed coding structure is also very helpful in analyzing project
performance data by facilitating aggregation selection and sorting to highlight trends
and anomalies.
The IPMS shall be categorized and the activities/events coded as listed below:
RESP: Responsibility determines the party responsible for the activity as shown below:
Architect
Mechanical Engineer
Fire Protection Engineer
Electrical Engineer
Veteran Affairs
Other Government Agencies
AREA: The A/E shall use this code to assign design element coding such as
Architectural, HVAC, Fire Protection, and other related design element coding.
PHASE: The A/E shall use this code to divide the items of work into different phases
within the Project such as Pre-Design, Schematic, Design Development, and other
project phases.
3.7
Activity Definition
The A/E, in conjunction with the project team members responsible to perform the work
of the project, should create the list of activities that will need to be performed to
complete the project. The Sample IMPS includes activities related to the design
submission requirements for VAMC Major New Facilities, Additions and Renovation as
detailed in PG 18-15.
Volume I - 20
Version 1.0
December 1, 2012
The A/E shall consider the following to break down the scope of work into manageable
activities for the detailed schedule of the design, procurement and activation:
The A/E shall show a concise description of the work represented by the
activity/event (35 characters or less including spaces preferred).
The A/E shall describe work activities/events clearly, so the work is readily
identifiable for assessment of completion. Activities/events labeled start,
continue, or completion, are not specific and will not be permitted. Lead and
lag time activities will not be acceptable.
The A/E shall designate a single entity that shall be responsible for performing
the activity. This does not preclude the idea that multiple resources may be
required to accomplish the activity, but it does require that a single entity is
responsible for its performance. That person should be the same one who will
report progress on the activity (Performance Responsibility).
Duration of activities/events shall be in work days.
Activities/events shall have cost assigned to them. Cost shall not exceed $99,999
per activity.
The A/E shall show activities/events for work for each discipline.
Each activity/event on the computer-produced schedule shall contain as a
minimum, but not limited to, activity/event ID, duration, predecessor and
successor relationships, area code, trade code, description, budget amount,
early start date, early finish date, late start date, late finish date and total float.
Work activity/event relationships shall be restricted to finish-to-start and start-tostart without lead or lag constraints (Exception allowed with approval).
The A/E shall break up the work into activities/events of duration no longer than
20 work days each, except for which the Project Manager and/or the Contracting
Officer may approve the showing of a longer duration (long, continuous design
activities and procurement activities where a single work item such as fabricating
and delivering/shipping a component to a remote site).
The A/E shall adhere to the VA NAS specification for A/E design.
For the summary level construction schedule, the A/E shall break down the schedule
into the proposed phasing plan. The A/E shall assign reasonable durations to the
activities and assign a 5-day work week calendar to each construction activity contained
in the IPMS.
When complete, the A/E shall confirm that the activity list in the IPMS shall describe
100% of the work required to complete the project in its entirety, although the
construction element of the IPMS will be developed at a summary level until the time for
that work draws nearer.
Volume I - 21
3.8
Version 1.0
December 1, 2012
Activity Sequencing
The A/E shall show on the CPM Schedule the sequence and interdependence of work
activities/events required for complete performance of all items of work. For instance, in
the design component of the IPMS, the A/E shall depict in sequence the relationship
between A/E submittals, VA Approval, Peer Reviews, Design Review meetings, and
other required work activities/events.
Work activity/event relationships shall be restricted to finish-to-start and start-to-start
with no lag constraints. Activity/event date constraints not required by the contract will
not be accepted unless submitted to and approved by the Contracting Officer.
The A/E shall make a separate written detailed request to the Contracting Officer
identifying these date constraints and secure the Contracting Officers written approval
before incorporating them into the CPM Schedule. The Contracting Officers separate
approval of the CPM Schedule shall not excuse the A/E of this requirement (See NAS
Specification).
In the construction phase of the IPMS, the A/E shall depict in sequence the
interdependencies among the construction phasing from the issuance of the
Construction Notice-To-Proceed all the way through Project close out activities. This
shall include constraints particular to each phase, what other phases must precede it,
other contractors working in that phase, and any VA moves/relocation which must
precede the start of the phase or phases.
3.9
The A/E shall define the activities/events first, and then the A/E shall tie the
activities/events logically into the overall schedule sequence and then the A/E shall
focus on how long it will take to accomplish the work. The A/E shall use the following
guidelines in estimating activity durations for design, procurement and activation:
Expert judgment guided by historical information.
Analogous estimating based on experience on similar projects.
Parametric estimating based on formulas describing relationships among project
parameters and time.
Use of simulations to develop distributions of probable duration of each activity
Consider each activity/event independently.
Skip around the network when assigning duration estimates to specific activities.
Avoid following a path of activities all the way through the network and to the
end.
Volume I - 22
Version 1.0
December 1, 2012
Activity duration shall be in work days based on physical work content. Example:
Complete SD-2 foundation design, 50 drawings (1,000 man-hours, 20 days with
4 structural designers).
The A/E shall break up the work into activities/events of duration no longer than
twenty (20) work days, except for the construction schedule and for which the
Project Manager and/or the Contracting Officer may approve the showing of a
longer duration. Exceptions to this rule are procurement activities, certain
approvals, concrete curing, and so on.
In order to estimate duration for the construction and activation phases of the IPMS,
the A/E shall coordinate with the VA and the project stakeholders. The A/E shall assign
reasonable durations to each component of the construction phasing in the IPMS. The
A/E shall take into consideration physical conditions, safety requirements, and any
labor agreements that may be in effect. The activity duration for the Level 2
construction schedule shall be in calendar days with the timescale showing months and
years.
Volume I - 23
Version 1.0
December 1, 2012
Version 1.0
December 1, 2012
The final CPM Schedule in its original form shall contain no contract modifications or
changes which may have occurred during the final CPM Schedule development period
and shall reflect the entire contract duration as defined in the bid documents.
The A/E, VA and key stakeholders shall be actively involved in reviewing the results of
the initial scheduling process. The review shall consider the analyzed project end date,
milestone completion dates and resource requirements to determine the acceptability of
the schedule.
These iterations continue until an acceptable project schedule is developed, one that all
of the relevant project stakeholders can agree with.
Volume I - 25
Version 1.0
December 1, 2012
Logic, time and cost data for change orders, and supplemental agreements that
are to be incorporated into the CPM schedule.
With each invoice, the A/E shall submit an updated schedule and the following reports,
for review and approval, to the Project Manager:
1. Detailed Design Schedule, including Critical Path (Longest Path),
2. Cost Earned Report as basis for the Invoice,
3. Sixty (60) day look Ahead/Hot list report,
4. Update Schedule Narrative that explains all the changes performed to the
schedule.
Volume I - 26
Version 1.0
December 1, 2012
5. CHANGE ORDERS
The IPMS in its original form shall contain no contract modifications or changes which
may have been incurred during the final CPM schedule development period and shall
reflect the entire contract duration as defined in the bid documents. These
changes/delays shall be entered at the first update after the final CPM schedule has
been approved.
The A/E should provide their requests for time extension for contract time as a result of
contract changes/delays in the design phase after the first schedule update. The time
extension must be supported by CPM data and analysis, justification narrative, related
documents and etc for VA approval.
The A/E shall submit each request for a change in the contract completion date to the
VA in accordance with the provisions specified under Article, FAR 52.243 -4 (Changes),
VAAR 852.236 88 (Changes Supplements). The A/E shall include, as a part of each
change order proposal, a fragnet showing all CPM logic revisions, duration (in work
days) changes, and design cost changes, for work in question and its relationship to
other activities on the approved CPM schedule (See Exhibit I.10 as a reference). All
delays due to non-work activities/events such as RFIs, weather, strikes, and similar
non-work activities/events shall be analyzed on a month by month basis.
Volume I - 27
Version 1.0
December 1, 2012
6. EXHIBITS
Exhibit I.1. Level 1 Schedule for a Typical VAMC Project
Exhibit I.2. Level 2 Schedule for a Typical SD-1 VAMC Project
Exhibit I.3. Level 2 Schedule for a Typical Construction Phase in VAMC Project
Exhibit I.4. Level 3 Schedule for a Typical SD-1 VAMC Project
Exhibit I.5. Level 4 Schedule (60-day look ahead) for a Typical SD-1 VAMC Project
Exhibit I.6. Sample Phasing Narrative for a Typical VAMC Project
Exhibit I.7. Cost Projection S-Curve for a Typical Design Phase in VAMC Project
Exhibit I.8. Sample Outline for a Schedule Narrative Report
Exhibit I.9. Longest Path for a Typical Design Phase in VAMC Project
Exhibit I.10. Schedule Impact Analysis Sample Change Order Fragnet
Volume I - 28
Version 1.0
December 1, 2012
EXHIBIT I.1
Volume I - 29
Version 1.0
December 1, 2012
EXHIBIT I.2
Volume I - 30
Version 1.0
December 1, 2012
EXHIBIT I.3
Volume I - 31
Version 1.0
December 1, 2012
EXHIBIT I.3
Volume I - 32
Version 1.0
December 1, 2012
EXHIBIT I.4
Volume I - 33
Version 1.0
December 1, 2012
EXHIBIT I.4
Volume I - 34
Version 1.0
December 1, 2012
EXHIBIT I.4
Volume I - 35
Version 1.0
December 1, 2012
EXHIBIT I.4
Volume I - 36
Version 1.0
December 1, 2012
EXHIBIT I.4
Volume I - 37
Version 1.0
December 1, 2012
EXHIBIT I.4
Volume I - 38
Version 1.0
December 1, 2012
EXHIBIT I.5
Volume I - 39
Version 1.0
December 1, 2012
EXHIBIT I.5
Volume I - 40
Version 1.0
December 1, 2012
EXHIBIT I.5
Volume I - 41
Version 1.0
December 1, 2012
EXHIBIT I.5
Volume I - 42
Version 1.0
December 1, 2012
EXHIBIT I.5
Volume I - 43
Version 1.0
December 1, 2012
EXHIBIT I.5
Volume I - 44
Version 1.0
December 1, 2012
EXHIBIT I.6
Volume I - 45
Version 1.0
December 1, 2012
EXHIBIT I.6
Volume I - 46
Version 1.0
December 1, 2012
EXHIBIT I.6
Volume I - 47
Version 1.0
December 1, 2012
EXHIBIT I.6
PHASING PLAN
Volume I - 48
Version 1.0
December 1, 2012
EXHIBIT I.6
Volume I - 49
Version 1.0
December 1, 2012
EXHIBIT I.6
Volume I - 50
Version 1.0
December 1, 2012
EXHIBIT I.7
Volume I - 51
Version 1.0
December 1, 2012
EXHIBIT I.8
Volume I - 52
Version 1.0
December 1, 2012
EXHIBIT I.9
Volume I - 53
Version 1.0
December 1, 2012
EXHIBIT I.9
Volume I - 54
Version 1.0
December 1, 2012
EXHIBIT I.9
Volume I - 55
Version 1.0
December 1, 2012
EXHIBIT I.9
Volume I - 56
Version 1.0
December 1, 2012
EXHIBIT I.9
Volume I - 57
Version 1.0
December 1, 2012
EXHIBIT I.9
Volume I - 58
Version 1.0
December 1, 2012
EXHIBIT I.10
Volume I - 59