 |
| Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | FileType | xsn | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.2 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.3 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.4 | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /blogs/cm/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /blogs/cm/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogs/cm/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogs/cm/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
| Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | FileType | xsn | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.2 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.3 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.4 | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /blogs/cm/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /blogs/cm/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogs/cm/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogs/cm/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
| Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | FileType | xsn | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.2 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.3 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.4 | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /blogs/cm/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /blogs/cm/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogs/cm/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogs/cm/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
|
 |
|
|
|
|
|
|
|
11/14/2011
Construction Claims happen all the time, but not all are equal in approach, compensation, type of impact, etc. Having a solid foundation on the project schedule specifications and requirements should absolutely be a "must have". Included in those specifications should be acknowledgement of the approach of how construction claims will address excusable days against the project completion outside the contractor's control. An agreement between all parties regarding the approach to be taken will be one less hurdle to overcome when/if a potential claim occurs. There are several methods or approaches to address excusable days in claims. An analysis of the as-built schedule, windows analysis, and time impact analysis are just a few of the approaches used in the construction arena. In any case in benefits both the owner and contractor to be clear on this matter up front.
7/13/2011"There is more than one way to skin a cat", is an odd notion but is a good way to figuratively explain the approach multiple users may take to update a schedule in Primavera. While there is a multitude of ways to perform a status update, this post is focusing on Primavera and the inherent option of creating a reflection. A reflection is an option that can be chosen at the Projects menu.
This method was recently brought to my attention by a co-worker. Upon creation the reflection appears no different than a copy of the schedule, except that the tiny folder icon in the Projects menu now shows a Question Mark over the folder. User(s) would then open the reflection and perform the status updates in the schedule as they normally would.
The unique difference in a reflection is the options associated with the updates and how they will be translated back to the Baseline, or Active, project line. Once users are ready to merge the reflection back with the Active project, which is chosen from the Projects menu, the user can then determine what updates will be included and what is to become of the reflection itself. This approach may have particular value when updates are performed in a team environment and the controller of the master file needs to understand the changes that are being made. As with most Primavera function users need to beware of the vast number of variables that should be considered, especially when working in a team environment.
4/21/2011Constraints can obviously have a significant impact on a schedule. Many scheduling applications include constraints such as start on, finish on, start on or before, etc. Though these constraints can lead to disagreements that are often a side effect of poor communication, there are other constraining factors to consider that prevent scheduling issues.
Constraining factors such as manpower, space, resources, material, weather, funding allocation, and many more are realistic constraints to consider in your approach to creating a schedule. However, these types of constraints are not as easily included in your scheduling software like those mentioned in the paragraph above. Some system settings are available, but much of the factoring for these constraints is in good general Project Management and planning practices. This is why the software application is just a tool to the scheduler, and does not replace the craft of a scheduler.
3/21/2011
One of the values of using a Project Portfolio Management system like Primavera is being able to display time phased distribution of budgetary data. Knowing how much and when a budget is consumed over the life of a project is valuable information. In a world that is becoming increasingly drawn in to frequent monitoring of project performance, the need for budgetary information like this is eagerly desired. However, the accuracy of that information is just as important.
Depending on the software used there are multiple ways of recording cost whether it is budgeted, actual, at completion, or other types. That cost data can also further be broken down into Material, Labor, Equipment, and others depending on the application used. Realizing the relationship between all those components of cost is important to how data is represented.
An example of the importance in understanding the relationships between cost components was realized in a report I created that returned value on At Completion Cost and Budgeted Cost. The problem initially noticed was that my Budgeted Cost did not equal my At Completion Cost for the Project, when they should have. When the budget was contractually modified on an activity I obviously knew that the budgeted cost for that activity had to be changed. However, depending on the settings it is important to note that the At Completion Cost may or may not change to be the same as your budgeted cost. If your settings permit you to change one while not changing the other you can quickly get into accuracy issues, like what was happening in my case.
An immediate solution is to make sure your reports pass the sanity test. A more long term solution is to educate yourself in your particular application or find somebody who is. 9/13/2010
When you think of construction management in scheduling and the progression of work there is typically a flow of isolated events. If Design is included then the process typically starts there, if it is not then it may start in Submittals and approvals. Successor activities might be procurement, fabrication, delivery, and installation.
Depending on how a sequence of activities is represented it is important to isolate the work appropriately. For example, there is a distinct difference of who and what is occurring in submission and approval of work activities. Yet, I have seen many schedules where the submission and approval activities are included on one activity. If the preparation of a submission is experiencing delays, it is best to know that the submission is causing delays and not an activity that combines both the submission and approval as one. 8/26/2010Recently 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. 7/28/2010
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.
7/8/2010Float 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. 5/27/2010For 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. 5/12/2010
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.
| Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XsnLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | FileType | xsn | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.2 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.3 | 255 | | Edit in Browser | /_layouts/images/icxddoc.gif | /blogs/cm/_layouts/formserver.aspx?XmlLocation={ItemUrl}&OpenIn=Browser | 0x0 | 0x1 | ProgId | InfoPath.Document.4 | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /blogs/cm/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsx | 255 | | View in Web Browser | /_layouts/images/ichtmxls.gif | /blogs/cm/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&DefaultItemOpen=1 | 0x0 | 0x1 | FileType | xlsb | 255 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogs/cm/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsx | 256 | | Snapshot in Excel | /_layouts/images/ewr134.gif | /blogs/cm/_layouts/xlviewer.aspx?listguid={ListId}&itemid={ItemId}&Snapshot=1 | 0x0 | 0x1 | FileType | xlsb | 256 |
|
|
|
|
|
|
|
|