Import Project Control Tasks (PCTs) |
FAQs | Feedback |
Importing Project Control Tasks (PCTs) is intended to align the CCMS with the master schedule for a project that is generated from either a Primavera P6 or Microsoft Project schedule. The CCMS has the ability to link CCMS planned tasks to any P6 activity so that when the CCMS planned tasks are completed, it will automatically update the % complete of the activity. This enables projects to simply configure an export that generates itself on a weekly basis with updated (and more accurate) completions % for any P6 activity that is linked to completions tasks.
This tutorial will provide instructions how to import a P6 activity list in XLS format. The import view for Project Control Tasks has an import template so that the columns will map to the correct fields in the database.
Important Notes:
The process for importing Project Control Tasks (PCTs) is outlined below:
Step |
Action |
1 |
Switchboard Navigation: Configuration > Data Exchange > Imports Menu Navigation: Engineering > General Configuration > Imports Import Wizard Button. |
2 |
Select IMPORT TYPE view to import against (do not select hyperlink). The Import Type for importing a PCT list is named Project Control Tasks
Import Edit Form - Browse to File. |
3 |
Select CHOOSE FILE to browse and select a file (.xls) file to upload into the CE database. Browse to the XLS file just as if you were attaching an image to a document, it is the same concept.
After mapping the fields, the import tool will perform a “Pre-Import” validation process, where it will present the what the results will be prior to committing to the import. This is an important feature as it will allow a user to cancel the import as they identified issues if they had proceeded directly with the import. Press NEXT to map fields. Import Edit Form - Map Fields. |
4 |
When importing the PCT list a user should put in “X” in the PCT Item column, which will notify CE to create a distinct PCT ID by what is next available in the database. At a bare minimum, the XLS file should include:
The user is required to align fields of the excel sheets to the specified module being imported into.
Import Edit Form - Set Collision Behavior. |
5 |
NOTE: The collision behavior is designed to set the business rules for the instance where data already exists in the database. If a record finds a perfect match against the NAME field, then it will apply a collision behavior, where:
Pre-Import Analysis. |
6 |
The final step of the import is to review the Pre-Import Analysis. The user can get a quick synopsis of the data that will be imported. The 'Pre-Import Analysis' allows a user to look at the the data to be imported and identify any potential issues before any data is imported into the database. The 'Pre-Import Analysis' is broken into 2 sections: Pre-Import Summary: This section shows a summary of the fields affected in the import.
Pre-Import List: This section shows a list of the fields affected in the import.
Select the Next button to view the 'Pre-Import Analysis'. Note: If the user finds errors in the 'Pre-Import Analysis' they can close the Import Wizard, make the necessary changes to their data and then repeat the process up until this point. If the data is correct the user can then finish the Import. Press the Finish button to import the data. Import Log. |
7 |
READING THE IMPORT LOG (results): Each import will be summarized in the import log. Select the blue Hyperlink to load the results from any import against this import view. A user can also select the XLS icon to load the file that was processed. After importing the PCT list a user will see the PCT list created and if completion details (actual end date) is entered it will automatically assign the PCT a completion status. If a user did not put in “completed by” in the XLS it will insert the name of the person importing the XLS file. Next Training: Import Systemization |
CONFIDENTIAL - Licensed Users Only |