You can use data from (import) P6 or Microsoft Project in Unifier project, including creating or managing activity, activity schedules, dependencies, and resource assignments.
Note: If you select multiple activity sheet or System Activity Sheet, then import options will not be seen.
You also have the ability to import project schedules that are maintained in P6 or Microsoft Project (.mpp or .xml) in the manual activity sheets. You can create a project schedule in Unifier (manual activity sheet) and bring data by way of importing a Microsoft Project file (.mpp). After a successful import, you can see that all of the activities, their dependencies, and assignments are created in a new activity sheet.
You can create a project schedule in Unifier (a manual activity sheet) and bring data by way of importing a P6 (.xml). After a successful import, you can see that all of the activities, their dependencies, and assignments are created in a new activity sheet.
The imported data can be further used in the earned value calculations, cash flow management, and so forth.
For the manual activity sheets, Unifier supports:
- Integrating with P6 or Microsoft Project to be able to import activities and related data to a specified activity sheet.
- Adding new activities in an activity sheet, through P6 or Microsoft Project import, with no additional setups.
- Synchronizing matching activities, through P6 or Microsoft Project import.
- Integrating with P6 or Microsoft Project out of the box (OOB), without any data mapping.
- Importing activity schedules, dependencies, and resource assignments, through P6 or Microsoft Project import.
- Updating the activities that are created, through P6 or Microsoft Project import.
When you access the Activity Sheets log (Activity Sheet node> Activity Sheets log), you can click the Actions toolbar option and get data from P6 or Microsoft Project import.
- Actions > Import > From P6 XML
- Actions > Import > From Microsoft Project
You can export the XML version of an existing Unifier project schedule (of an activity sheet) into other sources, such as MS project or P6 schedules.
The options above are available for the users who have the Create permission, at the activity sheet node level.
Note: The gear menu displays the same options, for any selected activity sheet.
The History tab contains the details for any import that you have initiated.
After a successful import, a new activity sheet will be created.
The import will remove any existing data in the activity sheet. Only activities for the selected activity sheet will be removed. The WBS associated to the activity sheet will not be removed.
The following file formats are supported, for the file upload:
- Microsoft Project (2007/2010/2013/2016/2019) schedule (.mpp format)
- P6 schedule (.xml format)
The following objects are supported:
- Activity Sheet properties
The project schedule start date and calendar. If there is no calendar, then the default project or shell calendar is used, and the earliest start date (across all of the activities in the sheet) will be the project schedule start date.
- Activity Sheet
The activity attributes (uuu_P6 elements only), Dependencies (Predecessors and Successors), and Resource Assignments (units and costs).
- WBS Sheet
All of the WBS attributes (WBS Code, WBS Name, and other default mapped attributes).
- Master Rate Sheet:
Resources/Roles (along with calendars). The Resource ID and Name/Role ID and Name, Currency, Calendar, Default Units/time, type of resource, and standard rates.
You can modify an existing activity sheet data only if you have the Edit permission.
The following data from the source file will be copied into an activity sheet:
- Activity Sheet properties
- Activity details
For Not Started, In Progress, and Completed activities: All uuu_P6 activity data elements and other system defined data elements like uuu_successor, uuu_predecessor, and so forth.
For In Progress and Completed activities: The uuu_P6percentcomplete will be updated.
- WBS Summaries
Project WBS Sheet will be updated with the Summary tasks as WBS items, if no data exists.
- Dependencies
All the relationships between the activities will be retained during the import. Those dependencies will be imported as successors and predecessors.
- Assigned Resources/Roles
Master Rate Sheet will be updated with adding new resources and roles.
- Resource Assignments
All the Resources/Roles assigned in the project schedule will be imported, along with units and costs. All activities will show the rolled-up costs and units when there are assignments.
In case of errors, Unifier aborts the importing process. The History tab will contain details about failed or successful imports.
Import Activities by way of Microsoft Project
Activities are uniquely identified within one Microsoft Project file by the Unique ID (<UID>). The following applies when importing activities from Microsoft Project:
- New activities inserted
- A new activity row will be created for each <UID>
- The <ID> will be copied into Activity ID (uuu_P6ActivityID)
- The <Name> will be the Activity Name (uuu_P6ActivityName).
- The Unique ID (<UID>) will be copied from the corresponding Microsoft Project activities.
- All other default (mapped) elements will be copied into the new activity.
- Dependencies of new activities
- Dependencies will be added for the new activities (if dependencies exist) using elements within the PredecessorLink tags.
- WBS summaries for new activities
- The WBS will be identified using the hierarchy provided within the <WBS> tag in the .xml file.
- This is WBS Code field in the source (the .mpp file for each activity in the Advanced tab).
- All the summary tasks (in .mpp file) will be created as WBS in project WBS Sheet, if they do not exist.
- Resource assignments for new activities
- When a new activity is created, all assignments for that activity will be created. If the resource does not exist (resource ID does not exist), then a new resource will be created in Master Rate Sheet, with resource name from Microsoft Project as resource ID and Name. If the resource exists and matches the source, then the resource will not be updated, and the existing resource will be assigned to the activity. If the resource exists but does not match the resource (resource ID is different from the ID in the source Microsoft Project file), then you must create a new resource with resource ID and Name identical to the source file.
Also, when importing the project schedule by using Microsoft Project (.mpp), for:
- Activities with start date earlier than the project schedule start date:
The project schedule start date will show the earliest start date across all the activities and the activities will be imported according to the schedule specified in the import file. In case the project schedule start date is selected (from shell attribute), then Unifier displays: Import has failed as activities have <label of uuu_P6start> earlier than project schedule start date for the selected Activity Sheet. This takes place when importing the project schedule with activities earlier than project start date. Similarly, when the required field values are missing in the source Microsoft Project file, then Unifier displays: Could not add Activity <Activity ID> as <Field1> is required.
- WBS Code import:
The summary tasks in Microsoft Project will be imported as a WBS summaries into the project WBS Sheet. All of the summaries with hierarchy will be imported as a WBS hierarchies into the Project WBS Sheet. Only the WBS Code and the Name will be populated for the WBS Summaries.
Note: Ensure that you add a new WBS Code and associate the activity, or task, with the existing WBS Code if there is an existing WBS Code (with the same WBS name but different WBS code), when importing the summary tasks as WBS codes.
If the WBS Code exists in the project WBS Sheet, then create an activity with the WBS Picker populating the WBS Code. The Used By field, in the project WBS Sheet, will be populated with Activity Sheet that the WBS Code is associated with. Similarly, when the required fields are missing in the source Microsoft Project file Unifier displays the message: Could not add WBS <WBS Code> as <Field1> is required.
- Resources that do not exist in the Master Rate Sheet in Unifier:
Unifier matches the resources by resource name, in the Master Rate Sheet.
If the resource is not found in the Master Rate Sheet, then the resources will be added with the resource ID and Name because the resource name (from the Microsoft Project), and the source are selected as user-defined (User Defined).
If the resource already exists in the Master Rate Sheet with the same name, but the ID does not match, then you must create a new resource.
The default values will be used for the resources that you create.
If the resource has a required field that is not available in the source Microsoft Project file, then Unifier displays the message: Could not add resource <Resource ID> as <Field1> is required.
- Roles:
The Microsoft project resource assignment does not specify a role.
- Project calendar in the Microsoft Project does not match with the Activity Sheet:
Use the project schedule calendar that is selected for the Activity Sheet. All of the imported activities will be adjusted based on the calendar in the project schedule start date.
- Resource calendar in the Microsoft Project does not match with any calendars available in Standards and Libraries:
Use the company calendar for the resources that have calendar that do not match. All of the imported resource assignments will be adjusted to the company calendar.
- Currencies and formats:
All costs will be converted to the shell currency, from the source file, for the activities and assignments.
- Constraints and dependencies:
The import process will match the dependencies based on the connected activities. If a dependency is matched, then all properties of the dependency will be updated from the Microsoft Project file, based the mapping described earlier. Activities will be moved to retain the new dependency values. By default, all of the activities will have the "As Soon As Possible" constraint even if there are different constraints set for the activities.
- Impact on milestone activities:
You can import the milestone activities into the activity sheet. All the activities that are created as milestone will have activity type selected as: Start Milestone.
- Required fields not part of Import file:
If there are any required elements in the activity attributes, and the imported file does not have any values for the required elements, Unifier will display the following message in the History tab, and the import will fail: <field name> is a required field in activity details. Or <field name> is a required field in WBS details.
Note: The above condition applies to all of the required elements (in the WBS Sheet and Master Rate Sheet) when importing the WBS Summaries and Resources.
- Rollback on error:
The various conditions (such as resources are not matched or no data for mandatory fields) described above can cause the import process to abort. In such cases, all of the changes made in the project schedule, by the import, will be reverted.
The errors and warnings will be reported in the History tab (log) for various miscellaneous conditions such as: Activities with start date that is beyond the project start date, and the activity sheet has "From Shell" attribute that is selected for project start date.
You can import the schedule irrespective of the status of the activity sheet.