In 2020, we will start the Project Controls course again. In addition to a good foundation and learning a planning tool (Tooling), this course consists of four specialisations: Cost, Risk, Information and Claim. In 2019, several enthusiastic participants from different companies started the course.
For 2020, we want to grow and improve as much as we did last year. In the new year, you can start our training again on 3 February 2020, in order to be able to complete the entire training within 3 months. Of course it is also possible to follow the specializations more spread over the whole year.
Our specialisations and other modules can also be followed separately. Click here for all our training dates. Do you have any questions about our training courses or do you have doubts about which courses are best for you? You can always contact us.
Gert Truyens explains what the different levels of change are, what they mean and how you can deal with them.
Managing change will always be a challenge in projects. Its importance cannot be overestimated in order to successfully deliver projects. Messing up will have huge implications in a claim-oriented environment. Still we see many project teams struggling with organizing and following a proper change management process.
A first step which proved to be of great help, is differentiating between several levels of change. To do this, we start by defining 5 levels on which projects are managed.
After following the tooling courses Oracle Primavera P6 Professional (P6) and Microsoft Project (MSP) one will identify differences between MSP and P6 on the following topics: milestones, adding activities (tasks in MSP), use of constraints, levelling, baselines, lags and relations. This blog will elaborate on the difference of using the “As Late As Possible” constraints in MSP and P6. It is essential to reckon this difference since it has a significant influence on the schedule.
Microsoft Project is a planning tool with which, besides planning on time, resources can also be allocated to activities. In this blog we will briefly discuss how Microsoft Project deals with the concepts Units and Peak and how different resource fields are calculated.
Primavera is a wonderful tool but sometimes it’s calculations give weird results. For instance when filling in durations of an activity, you might’ve encountered a problem similar to the ones below:
- Your activity duration is showing as 5 days but it starts on the 1st and already ends the 4th
- Your units/time is showing 8h/d but Primavera is actually calculating with 12h/d
What is going on? Well it’s probably something to do with your hours per Time period settings.
There is more to showing THE Critical Path in Primavera than your project manager can imagine. Primavera allows you to change certain settings to define the criticality of activities: you can define a threshold value for total float, or choose for the longest path instead of a total float-based critical path.