Primavera has three Scheduling Options to choose from when you are scheduling your project. Retained Logic is the default scheduling option. When you are building a Baseline, the default option works fine. But things change when you start updating your project, activities start getting delayed and do not get executed as planned. You then have to make a decision on whether you want to continue using Retained logic or choose Progress Override or Actual Dates as your Scheduling Option. A lot has been discussed over the internet forums on which option is the best for a project and Retained Logic has won with an overwhelming majority. But I have a different opinion.
From Amit Parmar em www.theprimaverablog.com
Tips and considerations about project management and control using Primavera P6 and other information for application mastering.
Wednesday, March 25, 2015
Is Retained Logic the best Scheduling Option in Primavera?
Monday, March 9, 2015
Using Physical and Duration Percent Complete Types In Primavera P6
If you are looking for a quick way to update the progress of work on your Primavera P6 schedule or you want to describe the progress of work that has a non-uniform production rate, then you should become familiar with the different Percent Complete Types offered in Oracle Primavera P6.
Here we will start with the situation where you already have a schedule and associated baseline. There is demand for accurate, weekly updates on your project and you need an efficient and accurate way of modeling activity progress. This is where the different Percent Complete Types in Primavera P6 come in rather handy.…
See the article on the Tensix Consulting blog site.
A useful exercise would be to take the example schedule used in this article and provide weekly updates to it, comparing your results to those in this article.
Wednesday, February 25, 2015
Tracking Costs in Primavera P6
Do you know how to track schedule costs in Primavera P6? Most of us are familiar with the process of updating and tracking schedule activity progress from a time standpoint, but what about the cost of those activities? Well, Primavera P6 has features available for keeping track of the cost of labor, equipment, and material resources. It is also possible to track the cost of project specific expenses.
This article describes the process of tracking the cost of labor resources on a project. It considers a schedule where all activities are on the critical path, so a delay in any activity will result both an increased activity cost and project management cost.
See the rest of the post in Tensix Blog here
Friday, February 6, 2015
Planned dates in Primavera P6
Primavera P6 has quite a few date fields that are often misunderstood. Perhaps no date field is stranger than the “planned” date. To begin with, there will always be a Planned Start and a Planned Finish date associated with every activity. In a schedule with no progress (or what we would traditionally call the “baseline” if P6 did not use this designation for target schedules) the following is always true:
- Planned Start = Start
- Planned Finish = Finish
Once progress is recorded, however, all bets are off. The planned dates will not reflect actual dates, for example. Primavera P6 shows actual dates in the Start and Finish columns, making it easy to see which activities have progress (take that, Microsoft Project!) without having to add the Actual Start and Actual Finish columns. Space is always at a premium in a printout so not having to add the actual columns is a nice benefit.
Here is where it gets interesting. Changing the Planned Start or Planned Finish date on an activity with no progress will change the Start and Finish dates and likewise move the bar in the Gantt Chart. The rules are:
- Changing the Planned Start changes the Start date, even if the Planned Start is beforethe original Start date
- Changing the Planned Finish moves the Finish date and changes the Original Duration to match
- Changing the Planned Start and Planned Finish will move the Start and Finish dates accordingly
- No other activities are affected by changes to the Planned dates of an activity
None of this will happen, however, if the “Schedule automatically when a change affects date” scheduling option is selected. This is because scheduling the project wipes out the changes made to the Planned dates. These are not constraints, after all. The logic was never modified. Which may seem like Planned dates are a cruel trick.
Well, we create logic for a reason. Moving bars around is not scheduling. Logic is supposed to drive dates. A few constraints are okay – although some owners are adamant about having none – as long as they do not cause an interruption to the critical path. Postponing the start of a critical activity would obviously make no sense.
Thursday, January 8, 2015
Using Level of Effort (LOE) Activities in Primavera P6
Level of Effort (LOE) activities are typically used to define effort that in and of itself doesn’t generate a deliverable, but does incur labor/costs to the project. Items such as management, security or safety are ongoing and require resources but are not on the critical path. These overhead costs are usually not immaterial. Overhead efforts can span part of the project, or the entire life-cycle. They are also associated with other activities in the project.Modeling these efforts and cost individually by assigning resources to every activity is prohibitive. So how does one easily define the effort of these tasks throughout the life-cycle of the project? Well, Primavera P6 has a Level of Effort activity type to help you model this type of work in a low-maintenance way, and one that does not interfere with the critical path.
Read More in TenSix
Friday, December 26, 2014
Applying Hard Constraints to a Schedule in Primavera P6
When do you apply hard or soft constraints in Primavera P6? This is a question I had recently while working with a client and while there are no hard and fast rules as project specific circumstances can differ, here are some guidelines that may help. Many times the project schedule is influenced by certain constraints on the project. These constraints can be contractual, external, or internal.
Tuesday, December 23, 2014
BIM Implementation and Project Controls
As current regulations require BIM implementation for every public sector construction and infrastructure project from 2016 onwards[1]designers, contractors and supply chains in the industry wil l need to move on fast from their current ways of working and adapt to achieve compliance with the upcoming legislation. The policy is however, not a punitive one for the industry. It is a progressive plan to significantly improve industry efficiency, from the project management stage in design and construction to the subsequent operational management of the asset during its lifetime.