A Schedule Sheet under Unifier Schedule Manager supports the following objects. For more information, refer to the Unifier User Guide, Unifier Administration Guide, and Unifier uDesigner User Guide.
- Activities
- Resource Assignments
- Activity Dependencies (Successors and Predecessors) along with relationship (Start to Finish, Finish to Start, etc.) and lag information.
- Association of an activity with a cost code (CBS Code) from Unifier Cost Manager.
Integration with P6 involves creation, modification and association of these objects automatically through Web Services calls.
As of the current Unifier release, integration with P6 Server supports the following information for each object.
- Activities: All elements including User Defined Fields.
- Resource Assignments: All elements including User Defined Fields and Unit of Measure
- Activity Dependencies: Based on Activity Dependencies option
- Association with Cost Codes: Unifier uses special logic as part of integration to build CBS Code to match with Unifier CBS Code or Cost Codes under Cost Manager. Refer to Associate CBS Codes with Activities section in this document.
To create and update these objects as part of Integration, the user must first create a data mapping relationship between data elements of Unifier and Data Elements of P6. The following section explains Data Mapping concepts and how to create one.
Apart from data mapping, Unifier should also know how to identify Activities and Resources that are coming from Primavera Project. This is to allow Unifier to support update web service method. Unifier currently supports two ways to identify an Activity and one way to identify a Resource.
An Activity can be identified by a GUID. Each activity in Primavera Project has a GUID. This GUID will be stored when an activity is created in Unifier and can be used later as part of update process.
The second way to identify an activity is through Activity ID. Each activity in Primavera Project has an Activity ID. This ID will be stored when an activity is created and will be used later as part of update process.
Resources are identified by their name. Each resource in Primavera Project has a name and this will be stored when a resource assignment is created in Unifier.