Unifier receives the integrated data, from P6, and uses the data for the following Cost modules:
- Cost Sheet
- Cash Flow
- Earned Value (EV)
As a part of integration, you can capture the "summarized" P6 data within the Cost modules and view the information in a columnar and comparative format, for example, Cost Sheet columns, Cash Flow Curves, and Earned Value Curves). In addition, the Reporting functionality within Unifier enables you to create "User-Defined" or "Custom" reports using the "summarized" P6 data.
Prerequisites for a Successful Integration
- Use CBS type Shells to use Unifier cost modules with data integrated from P6.
- Use the system Data Element
uuu_int_schedule_typewithin the Integration -> Detail section of Shell attribute form definition. - Create and Publish P6 Data Sources to pull P6 data into Cost Sheet.
- Create Shell instances corresponding to each P6 Schedule that needs to be integrated with Unifier by following these instructions:
- Each Shell instance must have the same ‘Shell Number’ as the corresponding P6 Project ID.
- To bring the P6 internal Project id to Unifier, you need to add the P6 Internal Project ID field (
uuu_int_internal_proj_id) to the Attribute form and the Integration Detail form (Company Workspace > Admin mode > uDesigner > Shell Manager > Integration > Detail) - Create or use separate Shell Templates for Duration Based and Resource or Cost Loaded integrated Shells in Unifier because the Cost Sheet for Duration Based schedules will not contain columns rolling up from P6 Summary Sheets (when the other two types of schedules will have columns rolling up from P6 Summary Sheets)
- Include the following in the Role attribute form, if the integration will be Resource or Cost Loaded:
uuu_role_imported_from_p6uuu_role_type, uuu_role_iduuu_role_uom
- For correct cost calculations in Resource Loaded schedules, update all imported roles with Rate values.
- If you create Unifier Roles via integration, include the Roles above the Data Elements (DEs) in the integration detail section in uDesigner Role attribute design.
- For Resource Loaded or Cost Loaded schedules:
- (Recommended) Do not change or update the ID of Roles created via integration manually because when you create Roles via integration the Role ID is used as the identifier by means of which the integration interface maps the P6 Resource to Unifier Role.
- If you want to integrate the CBS codes with P6, do the following:
- Include
uuu_cost_imported_from_p6anduuu_int_hidden_from_p6in the CBS attribute form - Define the default CBS segment values within Data Structure Setup -> Data Definitions -> Cost Codes
- Include
- If you want to create Cost Codes for a Shell using the P6 CBS structure, ensure that the Cost Sheet structure in P6 is Tree.
- Do not include Unifier Cost Code separators (“-”, “.”,) in P6 CBS Codes if you are creating Cost Codes in Unifier using P6 data.
- When working with P6 data sources or Cost Sheet columns:
- You can create or publish P6 data sources via integration and when the "Send Summary data" integration is used.
- You can add published P6 data sources, as columns, in Cost Sheet Templates, only.
- If you create P6 data sources via integration, and not manually, then you can add columns to Cost Sheet after the "Send Summary data to Unifier" is used, only.
- If you create P6 data sources manually, and not via integration, then create or publish P6 data sources by:
- Creating or publishing one P6 Data Source called "Current Schedule." This datasource is used by the system to define the "Type" of all Master Summary sheets (Summary sheets which contain summary data from the main P6 project which is integrated with Unifier).
- Creating or publishing all "Baseline Type" values defined within P6 Enterprise Data as P6 Data Sources in Unifier.
- Once you created or published the P6 data sources, you can use the P6 data sources to create columns in the Cost Sheet Template and push the information to the Shell instances.