Articles in Category: Emerald Tools - Primavera Add-Ons

New releases, case studies and more From Our Development Team And Consultants

Is the P6-QA tool only relevant during your planning phase? Absolutely not!

Something we are asked is whether our P6-QA Tool is useful through-out the life cycle of your projects. Its use throughout the planning phase is obvious, of course; it helps with schedule development. Even after you’ve planned out your work though, the QA tool can help while you’re executing your plans. Let us examine a couple examples of how.

Keep in mind - it is beneficial to equip your team with the best tools for the job! Work Smarter, Not Harder!

Scenario 1

During the execution of our schedule, our team loads found work using P6-Loader. Our team didn’t omit any information required by the P6-Loader template. That’s definitely a good start, but just doing that isn’t checking specific schedule quality. The P6-QA tool removes the burden of manual schedule and business process analysis by automatically identifying deficiencies in Primavera P6 schedules based on scheduling best practices, industry standards such as the Defense Contract Management Agency’s (DCMA) 14-point assessment, and user introduced business process requirements.

Your schedule requires the ability to conduct its designated tasks. You are probably wondering 'what tasks'? For example, our schedule needs to reflect the execution plan, contain regular updates and provide the basis for project schedule reports.

Where does the P6-QA tool fit in? You might think you’re done after updating your schedule, but are your updates complete and correct? All execution schedules require regular updates and then analysis after the updates. Imagine having to manually review your updates every day. You’d lose a lot of valuable time! The P6-QA Tool can assist with finding errors that can occur in the information uploaded to your schedule and the information entered in updates.

Imagine that during the update process, someone accidentally enters an incorrect completion date on an activity - this date is past the data date.

In the P6-QA Tool, the negative float would automatically be flagged by DCMA07 in the P6-QA Tool, Negative Float Check.

Another update entry is a logic change required by a change in the execution plan for a couple of work packages. The change is not entered correctly, and therefore when the logic is entered it produces negative float in the schedule.

The logic entered produces negative float in the schedule.

In the P6-QA Tool, the incorrect completion date would be automatically flagged by DCMA09a in the P6-QA Tool, Actual Date (s) After Project DD check.

Here’s a project level display example:

Activity level example:

The desk top icons make locating activities you need to address quick and easy. You can sort, filter and use the icons in group and sort to create detailed layouts making identification of the checks to revisit expeditious.

Another one of our tools, the P6-Loader, creates reports in the project notebook. Some examples of report information from the two checks that did not pass the criteria are below. The report contains all the checks that have passed and failed.

We looked at a couple of the list of DCMA checks the P6-QA Tool runs - there are plenty of other checks as well. The list below contains Business Process Validations run in the P6-QA Tool. These are some common issues, quickly highlighted by P6-QA Tool.

Scenario 2

Say your schedule is not progressing as planned - we need to create a couple of potential mitigation plans (what if scenarios). With the P6-QA tool, you can create copies of your schedule and test them with your proposed fixes. Once you’ve done this, you can address the findings to increase schedule quality maintenance. You set the parameters around the checks.

Above is a display of the parameter settings for the two checks we visited in scenario 1. (We used defaults to run scenario 1.) Being able to set your own parameters means you check your specific requirements, not a preset list of parameters you need to sort through later for applicability.

As you can see, the P6-QA tool remains relevant during your entire project. Empower your team with the best tools for the job with Emerald’s P6-QA tool.

Client Experiences #2 - No More Outdated Software

We've all worked with frustrating, outdated software. It's a pain to try and get everything to work the way you want it to, and the task is usually just too important or time-sensitive to take a break from. Everyone knows where that leads - yelling, cursing, or just slouching down in your chair in defeat, bested by technology once again.

During March 2016, our client decided that they were done working through this frustration. They wanted to update their data entry, schedule updating, and reporting processes so that they could streamline more effectively and remove these hassles from their everyday life. In addition to this, the refinery was looking for a way to develop a more effective cost control method for their turnarounds. Their current software just wasn't cutting it anymore. So they came to Emerald Associates for assistance - and luckily, we knew just the right programs to meet their needs.

Using P6-Loader, TAPS, EP-Datawarehouse and EP-Dashboard, Emerald Associates was able to give our client the software they deserved. No more despairing over yet another system crash or panicking over the disappearance of important data - now they had software that they could work with.

Thanks to Emerald's P6-Loader, our client was able to drastically cut down on the amount of time they spent poring over data. Automatic schedule updates went from taking hours to a matter of minutes, and custom dashboards and green-ups could now be created and automatically updated using EP-Datawarehouse and EP-Dashboard. This made the whole process move a lot smoother and much faster. Our client drastically reduced their need for manual entry, cutting down on errors and saving yet more time. The P6-Loader was a big step up from their previous way of managing things, not to mention significantly faster and far less likely to be tear-inducing.

This client still uses P6-Loader, TAPS, EP-Datawarehouse and EP-Dashboard to this day. No more outdated software for them - from now on, it's smooth sailing.

P6-QA in the Real World

Before becoming an implementation specialist at Emerald Associates, I was a project manager and P6 administrator in a state government transportation agency for several years. I was responsible for managing 50-60 Primavera P6-EPPM (Web) project schedules and monitoring them to schedule completion. These projects were for the engineering and design of highway projects including tasks such as road maintenance, new road construction, bridge maintenance, and signals upgrades.

Plan Development - Kick-off meeting

To put together the project's plans, we started with a kick-off meeting to verify the full scope. These projects typically ranged from 500-1500 tasks and ran for 24 to 60 months depending on funding each year and priority. At the kick-off meetings, with a hard copy template schedule in hand, each department head would discuss their role in the project and request adjustments to the schedule accordingly. As the project manager during these meetings, I took note of any deletions, additions, relationship changes, duration changes, etc. required to the schedule and with some project teams we made the changes directly in P6-EPPM in a Reflection Project. The schedule changes from the kick-off meetings ranged from minor to significant. Once I made the changes to the project schedule, a 'final' draft was sent to all the team members who participated in the kick-off meeting so we could get comments and approvals in time for our submission deadlines. If no comments or changes were made, the 'final' draft schedule was accepted and the project moved ahead.

Monthly Updating

Progress on the projects was done on an ongoing basis, with scheduling being done nightly. Project updates including scope changes, adding new tasks, removing unnecessary tasks, and rearranging tasks that needed logic changes were done when needed, via email from the initiating department. I would make changes on a Reflection Project and send the new schedule out for approval, if the float remained positive. If the changes caused the project to fall behind or if a large setback was identified, a schedule review meeting would be held with all the main players in the project. At the meeting, the key players in the schedule's creation and project manager would all gather and review the schedule for the project. Changes would be done on the fly in a Reflection Project and re-scheduled during the meeting, when possible. If many significant schedule changes needed to be made I would note these changes and complete them after the meeting so we didn't waste time during the meeting itself and I'd send out the new schedule for the project team to review and approve again.

Now theoretically the project schedule should have been fully reviewed by everyone involved. Unfortunately, this was not always the case and errors were commonly found within the updated schedule as the project progressed. There were a few reasons for this: Sometimes as a result of the dissolution of various activities, one activity would be 'overloaded' with unnecessary relationships and odd relationship types, often to the same activities, which would impact the schedule calculations. Also, periodically, there were problems with added activities that may have had relationships that were not added or added incorrectly or perhaps a duration was added incorrectly. Sometimes, a new activity ID would be entered incorrectly without notice. In essence, there were any number of things that could have negatively impacted our schedule quality. If only I had a tool available to check the nuances of the schedule for me and flag them, so I would know where to look. Little did I know there was a tool out there that would have saved me countless hours reviewing and analyzing this schedule.

If I had had the P6-QA tool to help in analyzing my schedule after changes were made and before the schedule was sent out, I could have sent out a schedule that would have automatically been checked for logic, logic types, missing codes on the activities, activity ID format and other business process checks that we could have created specifically for our needs. The use of P6-QA would have cut down the time it took me to send out revised schedules from several days to less than one.

Having P6-QA there to act as my safety net on the project changes as they were made would have been extremely helpful to ensure the changes made sense and did not negatively impact other parts of the schedule. I could have run the P6-QA check while everyone was in the meeting, let it pinpoint possible problems, and then discuss those issues with the team immediately. This alone would have saved me multiple e-mails back and forth after I analyzed the schedule after the team meeting.

I am positive buying P6-QA would not only save any company time and money, it would help them produce quality P6 schedules.

P6-Scrubber - Keep Your P6 Clean!

Are you importing schedules into scrubbing databases, taking out all the unwanted data you don't want to pollute your production database, re-exporting the schedule and then importing it into the database where it should have gone in the first place?

Do you have required specifications your contractors need to follow for their schedules, but have a hard time knowing whether those details are missing or incorrect until you've already imported them?

Do you want to ensure you are not importing POBS tables and corrupted RISKTYPE tables?

That's a lot of quality assurance to do! Maintaining your corporate data standards for dashboarding and reporting can be a full time job, especially when project teams have their own coding structures and requirements for their P6 Environment.

Don't worry; there's relief. Emerald has developed a new tool that will do all that work for you! We are now introducing the* P6-Scrubber.*

The P6-Scrubber is a configurable tool that resides outside your P6 environment, so you can run your XER files through it to vet them for your specific criteria prior to importing it to your P6 database. You can decide whether you want to keep or remove data at the global, project, and activity levels. We provide a clean import file once the P6-Scrubber is finished, as well as a convenient report of the data that was analyzed. You can give feedback to your contractors about their schedules in minutes before you import their file into P6.

Once the scrubbed file is imported to P6, the P6-Scrubber also flags projects and activities with the results it has found. We also put the results report in a notebook, so you can see the analysis P6-Scrubber did without opening a separate report.

Using the new P6-Scrubber tool will save your team loads of time and help keep your P6 environment clean!

EP-Dashboard - Tracking Found Work on Turnarounds Made Easy

While working on a turnaround project where our client was using our EP-datawarehouse and EP-dashboard tools for the first time, we were already showing them green up reports, inspection summary reports, performance curves and productivity curves, but had been tweaking them to fit their needs during the turnaround, which was quite beneficial to their team.

I was providing assistance to the turnaround team and started entering Additional Work Requests (AWR’s) as they came in from the AWR manager. The process required several steps during its life and we found a dashboard would be helpful in keeping track of the process, since we were getting questions about where AWR's were in the process. An AWR entered the process when it was received from the field personnel, assigned a number and entered into a master spreadsheet by the AWR manager. The spreadsheet listed several pieces of information, but the information we needed for the dashboard was the AWR#, Date Submitted, Approval Status, and the Description.

When the AWR was approved, it was sent to the schedulers to enter a placeholder into the schedule. After the placeholder was entered, a planner would enter the necessary activities and resources for the AWR. The activities would then be started and completed just like an original activity.

My IT colleague was able to use data from the master Excel spreadsheets and data that was snapshotted daily using the EP-datawarehouse from P6 to create the EP-dashboard below. The dashboard shows the AWR’s by project and using the snapshot data, indicates whether the AWR had been approved, if the placeholder activity was entered in P6, if the AWR had been planned and if so, if the activities had been started and/or completed. The creation of the dashboard took less than a day.

By using this newly created dashboard, we quickly discovered there were errors in several projects, where the AWR numbering schema did not match the project it was entered into.

We were able to correct all the errors concerning AWR’s that had previously existed, sometimes for over a year, within a day. We were not only able to create an extremely helpful dashboard, but we also improved the data integrity of the projects.

Tracking Mandatory Codes via P6-QA

These reports require specific activity code assignments, and sometimes those are missing! Assigning these this is time consuming and frustrating. But don't worry, help is available... With the P6-QA tool!

One of the numerous features available in the P6-QA tool is quickly checking a specific set of mandatory activity codes in P6 Schedules, producing quick results to know which files as well as activities in the files are missing the mandatory activity code assignments. Mandatory activity codes in the P6-QA Tool can now be set at the global or project level. In previous versions of the P6-QA Tool the Mandatory Codes check could only be used on Global Activity Codes. Quickly ensuring the mandatory codes are assigned helps ensure reports issued are correct.

Thinking this is difficult to set up/use? No catch, the process is easy.


First Step: Login to P6.

Set up the required codes as Mandatory codes in the P6-QA Tool. Sound difficult? Not at all! The activity codes that are assigned as Mandatory simply need (*) added to the end of each activity code.

Let’s have a look at a small example.

We have one Global Activity Code set up as Mandatory (above).

We have two Project Level Mandatory Codes set up (above).

We have assigned some of the Mandatory Codes to some activities above. We need to run the P6-QA tool.

Above is the project file this example is using – the QA-P6-QA Last Run Date has been cleared to run the P6-QA Tool. Note the QA-CL – No Mandatory Code and the QA-CL- No Mandatory Global Code columns. These will be populated to indicate at the project level the status of the two checks. Our example is running just one project file – you can set up a QA – Frequency (see column above) for the P6-QA Tool to run on each file or manually run single or specific groups of P6 project files.

Above the specific tolerance fields have been included, which can be set for these two checks. You control the specific conditions flagged in the P6-QA Tool and at which level.

The layout above is grouping by activity type, showing the activity codes and their assignments from the P6-QA Tool check.

The user can filter/group and sort on the mandatory activity code values right in the activities tab to produce a quick layout that directs them to the issues to facilitate quick correction. Use your specific project codes to create a layout that works for your business. Don’t forget – save your layout/reuse. This is a simple example of 3 mandatory codes - set up the codes you require as mandatory - a few or many more.

CAPPS – Tracking Variance to Plan - Introduction

When updates are done from remote locations, it is sometimes hard to know if the scope of work is on track or not. In P6 we have the idea of variances against a baseline, but sometimes it is even more practical to compare variances against the current schedule or the last update.

CAPPS - Variances Can Help a Lot

Variance to planned schedule information is updated/stored in P6 when you use CAPPS to update your project.

Frequently projects need to display variance to plan on completed activities in meetings and on reports progressively as the activities are completed. This information provides not only status, but can also assist in addressing continuous improvement during the project.

The information provided in P6 after a CAPPS schedule update contains both variances and flags, making it easier to see how the activities are doing for the non-P6 expert. The flags provide a very visual capture of the status, and can also be used for sorting and filtering as can the specific variances.

We will walk through a simple update using CAPPS and view the date variance information generated by CAPPS.

First we login to CAPPS to enter our updates. We've entered a round of updates below:

We click ‘Save Progress’ and the Progress Update Status and send them into P6 CAPPS Holding buckets.

Back in P6 we run the CAPPS Approval Process and can hold back any tasks we want to validate. 

Once the CAPPS approval process is complete (PASS), in the activity tab in P6 we can view the updated date information with the Start Date, Finish Date Variances and Variance Flags. These elements can be used in P6 layouts as you can see above as well as in P6 reports.

The above layout is a very simple example displaying only completed activities where either the Start Variance Flag or Finish Variance Flag are not displaying the green check. In a large project, the user can add in a date qualifier to see only the activities closed for example, in the last update along with other filter elements such as a specific Variance Flag, a negative start variance, or a negative finish variance. The user can add additional coding to the filter and in the layout to group, sort, and filter the information to produce a very useful and informative layout.

Don’t forget that you can also filter and create a layout to display any activities which started early or finished early – or both. There are additional variances captured using CAPPS to provide easy access to additional project variance to plan information on items such as duration, labor units and expenses.

Are You Tracking Activities Completed Late? P6-QA Tool Can Help With That Task!

Wondering how exactly? After your updates have been entered into your schedule, run the P6-QA Tool. This tool performs many checks, including one to track Activities Completed Late.

Let’s have a look at a small example. We have entered updates in our sample schedule.

Now we run the P6-QA Tool by simply clearing the QA-P6-QA Last Run Date column and refreshing.

Once the P6-QA is finished running the QA-P6-QA Last Run Date column is populated as well as the QA-ST – Act: Compl Finished Late column indicator.

In the Activities tab the layout (below) is showing the QA-ST – Act: Compl Finished Late column as well as the QA-ST – Activity Completed columns. Each is populated with the icon produced by the check run.
(Note that you control the QA-ST – Act: Compl Finished Late – TG# and QA-ST – Act: Compl Finished Late – Wt% columns by populating the tolerances you want to use in the check and overall calculation.)

The user can use the indicators for the checks directly in layouts in the activities tab to display, group, sort and filter as required to produce a useful layout.

Layouts can include filters/grouping based on the check results along with activity counts to make layout reports easier to digest and summarize. (Above layout is filtered on only the Completed activities finished late.) Create layouts to track activities completed/activities completed late, and after each update simply run the P6-QA Tool, review the results and distribute the information.

The P6-QA Tool runs a large number of checks providing a variety of quick, visual feedback on the results. You are in control – settings for checks can the same for all projects/different for each project or a mix in between. Provide your team with the P6-QA Tool and work smarter, not harder!

P6 Tools – Part of Your Company Digital Transformation?

Hearing a lot about ‘digital transformation’ lately? Digital transformation can be defined as the acceleration of business activities, processes, competencies and models to fully leverage the changes and opportunities of digital technologies and their impact in a strategic and prioritized way.

What elements are included in your Digital Transformation plan? Can your team afford to ignore new technological advancements? Planning a strategic and prioritized path forward to fully leverage changes and opportunities in digital technology can have a very positive return on investment. The Digital Transformation for a company varies from company to company and can be a large project encompassing many different elements depending on said company and its current state.

Here's an example of leveraging changes and opportunities new technologies can provide. Say your team uses Primavera P6 for Project Management, yet doesn't use P6-Loader, P6-QA Tool, CAPPS or TAPS (barcode updating), and P6-Calculator for any efficiency gains, are you getting the best out of the tool. In many surveys conducted over the years by Oracle and Primavera, P6 is highly underutilized with 100% of clients using P6 for scheduling, 60-70% for resource management and only 30-40% for cost management and earned value analysis.

Emerald Associates specifically designed our productivity tools to address pain points users commonly encounter when using P6 so you can do better managing your projects and get more out of the project team;


The P6-Loader automates manual data entry through the secure import and export of most data elements between Primavera P6 and Microsoft Excel.

The P6-Loader allows for the controlled extract and upload of data at the global and project level and eases the challenge of manipulating your project data by leveraging the spreadsheet functionality of Excel.

The P6-Loader goes above and beyond the built-in import and export functionality in Primavera P6. It has also become a desired replacement for the outdated Primavera SDK (Software Development Kit). Now, with version 4 being cloud enabled, it is quickly becoming a desired tool to help with migrating to the cloud efficiently. With close to 1 Billion of transactions pushed through the system, it is making teams worldwide more productive.


Emerald’s P6-QA tool removes the burden of manual schedule and business process analysis by automatically identifying deficiencies in Primavera P6 schedules based on scheduling best practices, industry standards, and user introduced business process requirements.

The P6-QA tool is unlike other third party Primavera schedule validation tool because it seamlessly integrates directly into Primavera P6 itself, allowing for the improvement of project management skills and scheduling quality in real-time. The P6-QA tool can be run at a preset interval such as weekly or monthly, or on an as-needed frequency to maximize your P6 schedulers’ ability to self-critique and ensure effective quality control.

When your resident engineering team is your frontline reviewers, this tool makes their role much easier and more efficient saving you a lot of time getting your contractors schedules reviewed, critiqued and hopefully approved so you know if the project is still on track without an expensive team doing a lot of analysis. When you are reviewing schedules every few weeks on a project this is significant in time savings as well as the time freed up to address any issues on the project.


CAPPS is our tool that lets the remote users and likely non P6-Experts to get the project updates into P6 from wherever they are and whenever they have a moment. This means waiting for updates once a month is a thing of the past. Taking 2 weeks every month to get your portfolio updated is a thing of the past. Real-time statusing is doable with variances and deviations able to be highlighting and interjected into the schedule as they are happening making your forecasting, change management and claims avoidance mush more effective.


TAPS, or the Turnaround Progressing System, uses barcode scanning technology to eliminate the need for lengthy manual data entry when updating your Oracle Primavera P6 schedules. Simply use a barcode scanner to find, start, update or cancel any activity within the schedule in two quick scans.

With TAPS, status updates can be done 75% faster while increasing your team's accuracy, since there's no chance of manual data entry errors. The first scan finds the task and the second scan starts, finishes, and statuses the task with any of the percent complete types available in Primavera P6.

The progressing flexibility along with the ability to calculate and report Earned Value at the resource assignment level makes TAPS a strategic enhancement for all Primavera P6 users.


The P6-Calculator performs calculations that are traditionally unavailable in Primavera P6.

P6-Calculator automatically performs calculations on data in P6 to present information to users that would otherwise be difficult for them to see, improving visibility and digestibility of complex P6 data and enabling better decision making.

All of the above tools are available on the Oracle Cloud Marketplace.

This is just one small example of an opportunity to leverage the changes and opportunities of digital technologies and claim the positive rewards of their impact. Help your team work smarter, not harder by empowering your team with the best tools!

Deviation Requests (DRs) – How are you handling them?

Are your deviation requests and approvals an entirely manual process? Do you have an easy electronic cross reference between activities in your schedule and specific Deviation Requests?

CAPPS – Take Center Stage!

A new feature in CAPPS is the ability to request a deviation against an activity id/submit it for approval, have a DR number assigned/tracked, and also have the DR approved (or rejected) right in CAPPS (with the information stored in P6). Requesting the DR, adding the DR number to the activity in P6 and the approval process using CAPPS with the information stored in P6 makes reporting on DRs and related activity statuses very quick and easy.

Only the users with ‘Approver’ security on their logins will be able to login to CAPPS and ‘approve’ items. To approve an item they must also be the Approver assigned to the submission.

Let’s look at how this works:

First log in to enter updates in CAPPS, then go through the update tabs and enter all the updates required for activity status, resource status, expenses, steps, predecessors & successors. The new feature we want to look at is in the Deviation Requests / Approval tab. You can request a Deviation for an activity here (below).

Enter the DR Type/select DR Req; then Save Progress to go to the Progress Update Status window below – When you see the screen below, your information has been sent to P6.

To make sure everything was entered correctly, go into P6 and go to the Project tab running the P6C – CAPPS Approval process. (Go is selected to run to process manually)

The Approver can enter the DR Number and any applicable comments in P6. When the Approver logs back into CAPPS and clicks to check the Approve box in the Deviation Requests/Approval Tab, then Saved Progress, CAPPS's approval is run in P6.

Now the activity details reflect the approval. The approval can be submitted at the same time as the DR Number and Comments, they do not need to be separate.

With CAPPS you can update information quickly, easily, and stop fighting with reconciliation of DRs/the activities they pertain to and activity status. It's all in your project schedule. You can set up filters/layouts and reports on this information as required to support your business processes.

Saying Goodbye to Expedition 8.5 and Hello to Unifier - Part 2

A Case Study From A Technical Perspective

Alberta’s Capital Health was a big user of Expedition from the 1990’s through to 2010. They had hundreds of projects that were sitting on a Sybase SQL-Anywhere server that needed to be retired but they needed to have easy access to the documents related to these health care projects.


Emerald solved their problem using the PCM-Archiver. This PCM add-on tool automates the extraction process of all projects and documents, and in this case, ultimately saved the client approximately 140 hours of computing work. For a more in-depth understanding of this project and its results please refer to Part 1 of Saying Goodbye to Expedition 8.5 and Hello to Unifier. In Part 2 we are going to explore a more technical perspective including some of the bumps we experienced along the way of extracting 1,213,318 documents, generating 1,123,318 Excel files, generating links for 39,384 attachments and generating 91,236 PDF files!

Save 5 Minutes Every Time You Cancel an Activity in Primavera P6

Whenever we have a client that is interested in TAPS, we always get the question about how an activity is updated to reflect that it has been cancelled. So, how does TAPS cancel activities?


Cancelled work is work that you have decided not to perform. Typically the turnaround (TA) team doesn’t want to delete the activity because that would change the baseline hours. On the other hand, they also don’t want to progress the activity which would earn hours.

The Fastest Way to Cancel Activities in Primavera P6

Automate the Process of Updating Cancelled Activities in Primavera P6 with our Barcode Updating Technology

When planning a turnaround project you want to make sure you include all the tasks that will happen and even those that might happen. This is a great strategy in the planning phase because during the actual turnaround, you don't have time to add all of the “potential” activities that become necessary.


Now the dilemma becomes, how to cancel the tasks that your team doesn't need after all.


You could process the updates for cancelled activities using manual data entry, dealing with logic, manhours, and baselines, but if you handle a lot of these it becomes time consuming, tedious and frustrating. Lets face it, during a Turnaround that is just not a good idea. You might think that dissolving is good enough, but is it?


IT Program Management with Primavera P6

An Example of P6 Mentoring, Coaching and Working Sessions

Primavera P6 Coaching


We have been working with a client using Primavera P6 for a large multi-year, multi-sprint IT project to revamp their customer loyalty program and overall customer experience. The team has been using P6-EPPM and have been aggressively putting together schedules for each key component of the program from infrastructure, to ERP, to integration testing and deployment.


This team is in large part new to P6, and they have been fighting to produce an overall program plan that has a continuous critical path so they can answer the usual question “when are we going to be done?”.


Getting Roles Onto Your Master Primavera P6 Plan - First you Have to Find Them

Do you find it tedious and time consuming to locate the resource assignments with missing roles?


When you are building up your schedule it is easy to miss assigning roles to resources, especially if you did not use roles at first and are introducing them after the fact. Another common scenario is when you are importing contractors' P6 schedules and are merging them into your turnaround plan or a large capital program where you are reporting both on resources as well as roles for trades and discipline rollups.