Easier to work with hierarchical fields - WBS, Resources, Roles, Codes, EPS, OBS, and Cost Accounts.

Full path extracting and loading for all hierarchical codes makes working with these hierarchies easier in Excel. Several new fields were added including the full code path field and a field showing the level of the hierarchy. This makes building hierarchies in Excel easier and loading them into P6 less error prone. Separator definitions are now also configurable.

Allows importing of WBS with their codes (without needing the path) if they are unique across a project

WBS template fragnet loader - You can take advantage of WBS templates built in P6 within P6-Loader to copy WBS nodes, activities, resources assignments, logic, steps, and expenses from one or many templates and fill in any placeholders for activity ID and names as you generate new WBSs into your project. You can also assign UDFs and codes to WBS, activities and resource assignments while applying a template. This is like the old P3 Fragnets on steroids.

Improving the handling of spread information to allow quarterly and yearly spread extractions are back. Manual spread loading of these spread periods is not supported.

Automatically starts activities when loading resource assignment period actuals.

New UDFs to show variances and calculated values - P6-QA may report that you have activities that are overdue for updating, but are they over by 2 days or 2 months? And what is your project's critical path length index (CPLI) exactly? Now you can view these metrics right in P6 to know how close they are to your target values.

Indicators for resource assignments - P6-QA has reported you have resource assignments that are missing roles, actuals or perhaps are over budget. In this release, we've added indicator UDFs. P6-QA populates them to let you find the affected resource assignment with ease.

P6-Reporter Ready - We've added custom tables to our P6-Reporter tool that neatly arrange your P6-QA data, including all of the inspection details, so it's ready to be put into the reporting software of your choice.

P6-QA statistics can now be pushed into time-based graphics. Being able to critique different portions of your schedule to get a much better idea of the risks and timing of those risks.

Custom field copy - copy custom fields from the primary resource into the activity that holds it, or assign a value in a UDF or code based on the calendar the activity has selected. The rules are fully customizable, and it is possible to create match rules using regular expressions.

Required objects feature - check if your project has required objects based on pre-defined rules in the program, and fix the problem if possible or alert the user if that is not possible. For example, WAIT activities with a pre-defined duration and name format.

Global change feature - apply changes to project data based on pre-defined rules. For example, change the relationship type from the WAIT activity into its milestone's successors from SF to FF, once the milestone activities have reached a certain status.

Resource rate import - allow resource rates to be imported from an external system and applied as new resource rates to the resources, matching on resource codes. Shifts are taken into consideration if they are being used.

Dictionary synchronization - in some organizations you may have a project code and an activity code that must have the same values. With this feature, you can define a source code and the code values are synchronized to the target codes. The dictionaries are kept in sync, and if a value is moved in the source hierarchy, it is also moved in the target hierarchy.

As part of dictionary synchronization, it is also possible to copy the resource tree as a resource code dictionary.

Code assignment copy based on certain rules - for example, you can assign a code in the activity based on a corresponding code value in the primary resource for that activity.