Skip to main content

Construction Management Blog

Go Search
Home
About Us
Services
Careers
Locations
Partners
CM Blog
  

Other Blogs
There are no items in this list.
Primavera Export/ Import Helpful Fact
Recently I found the need to do some mass changes in durations that I could not accomplish with a Global Change in the Primavera software. So I decided to export the data to an XLS file, edit that file, and then import back to the Primavera schedule. After my first attempt I realized the Remaining Duration Values I edited did not import correctly. After retrying the process another 3 times, I realized something else had to be wrong.
 
What I found out is that you have to pay close attention to all the data you are exporting/ importing. Though I changed my Remaining Durations, I also had imported/ exported my Finish Dates. Though I imported my Finish Dates I did not edit them, and their unchanged values overrides the changes I made to Remaining Durations. The simple fix in my case was to no longer Import/ Export the Finish Dates and adjust only the Remaining Durations as before.
Resource planning

Some customers may require that a schedule not be resource constrained in an effort to see how long a project will take if resources aren't a constraining factor. Whether a schedule is resource constrained or not resource allocation can be a hindrance. There are plenty of issues when it comes to resources constraints such as, space, shifts, scheduling resources with real time factors.

 

For now I will focus primarily on space. One thing a scheduler can do to ensure proper space scheduling for resources is code activities with a space (or location) value and also code with a number of resources at a given time. When analyzing the data a scheduler can then analyze who will be where and when.

 

Misrepresenting Activity Float
Float is a quick indicator in scheduling to see how an activity is peforming in relation to other activities. In many cases it is best if the float is calculated off of a project completion date. Because float represents how long an activity can be delayed until it impacts either another activity or contraint, the float values can be hard to understand without knowing all constraints used in a schedule. Another point of confusion is that schedules that are scheduled to fninish ahead of a required schedule completion date can show negative activity float values, again depending on whether or not constraints are used and if they are being satisifed.
 
Some customers require that constraints be omiited from the schedule. This is a clear approach to use so that all float values reference the same thing, being the required completion date. Because schedules are seen by more than schedulers, reducing this confusion can go a long way to be building confidence in the integrity of the schedule by people other than schedulers.
Cost loading in Primavera 6 & 7
For those of you using Primavera 6 or 7 you have probably noticed that cost loading is different that how done in Primavera 3.1. Cost loading can be accomplished at the resrouce level. However, there are also other options, such as, loading through expenses. Loding through expenses can provide limitations. One of the big ones is that because expenses are not resource loaded it behaves differently and you don't have the ability to review spread data like you would if the costs were loaded at the resource level.
 
There can be a lot of time associated with cost loading a schedule. In one case with a client of mine the contractor schedule is meant to communicate with the customer's project management system. Howevever, the project management system is set up to read cost resource loading only. The basic point is that you need to make sure you understand the ramifications of how you cost load and make sure you choose the most appropriate method before beginning.
What Primavera doesn't do
Primavera, like other scheduling software, does a good job of recording known data, projecting data based upon recorded factors, and supplying users with other scheduling data based on known factors recorded in the software.
 
What Primavera doesn't necessarily do is provide a performance indicator based upon the analysis across multiple schedule submissions simultaneously. Depending on your scheduling software there may be a cost or schedule performance indicator but that is still compared at a singular point against a plan.
 
My company, Management Solutions LLC, is in process of developing a system to address Project Performance over the life of the project. Ultimately the system will measure the project not only against one planned point such as a Baseline, but it will measure the performance based upon all scheduled submissions and multiple periods of time.
Activity Calendars

When using Primavera (or similar) software it is always important to be cognizant of the type of activity calendars you are using. For a particular project I am working on the Government is entitled a specific review period, which can be affected by more than setting the Original Duration.  Because the specific activity can be set up with different working days (meaning days are predetermined as to whether they are considering to be included in the actual duration or excluded), it is important to always note what type of activity calendar is being used and what should be assigned to each activity.

Claims Analysis III

I am continuing on with the topic from my last 2 posts, Claims Analysis. The perspective used is that you are representing the client/ customer and are reviewing a claim from the contractor in regards to delay or cost claims. The focus of this post is on what information should be used/searched in your review.

 

  1. Search for "As Awarded" documentation to understand contract and scope of work.
  2. Search for a schedule that was current in the period when the claim was issued.
  3. Search for as-built schedule history related to the claim.
  4. Review daily reports, payment history, and contract modification history.

 

Claims Analysis II
I am continuing on with the topic from my last post, Claims Analysis. The perspective used is that you are representing the client/ customer and are reviewing a claim from the contractor in regards to delay or cost claims. The focus of this post is on a checklist to use when reviewing claims documentation form the contractor.
 
  1. Has the claim been defined?
  2. Has the cause and justification for the claim been provided?
  3. Has a sub-network or fragnet schedule been provided as part of a claim package?
  4. Has a modification code been added in the contractor's structure to isolate within schedule
  5. Can you determine what phase or stage the project the claim was generated?
  6. Has sufficient information been provided?
Claims Analysis I
Recently I attended an all day training event with my company Management Solutions and we discussed many important aspects of scheduling and support of Project and Construction Management. One of the topics we discussed was claims analysis. As a scheduler, interpretation to who is responsibile for delays is probably the most common and appropriate claim analyzed. Below are a few of the general personal objectives we discussed when performing a Claims Analysis.
  • Have a clear understanding of what contractual basis the claim has been made
  • Urgency of response needed by your supervising body
  • Obtain technical experts
  • Have an open mind and serach for facts & the truth
  • Maintain a fair attitude, and refrain from bias
  • Document your fidnings and opinions that will withstand detailed cross-examination
The Procedural Need For Addressing Impacts

Because many construction schedules are very large it is difficult to understand all changes made by somebody other than yourself. To an individual that doesn’t get caught up in the details they may only consider monitoring a few details of the schedule. The problem with that approach is that much could be going on behind that scene that has significant implications.

 

In order to achieve a good analysis or understanding between sequential schedule submissions you need to have a process for communicating changes. Certain scheduling software has features, such as Fragnets, that allow users the ability to communicate potential impacts before being integrated into the schedule. Fragnets, or whatever method used, can help all parties understand potential implication before affecting the Baseline schedule.

 

The next step is implementing a procedure for issuing a document explaining the change before including in the Baseline schedule. The final step is enforcing that step consistently.

1 - 10 Next

 ‭(Hidden)‬ Admin Links