The following chapters describe the exchange of data between PLANTA project and PLANTA pulse when using the hybrid planning method. For a description of the principles of working with PLANTA Hybrid, please click here.
Synchronization from PLANTA project to PLANTA pulse
Information
The synchronization of planned data from PLANTA project (tasks) to PLANTA pulse is initially done via the Synchronize button in the Attributes/parameters area of the Project Core Data module.
Changes can be synchronized via the button in the Schedule module or via the Synchronize button in the Task module.
Details
The following data is initially synchronized from PLANTAprojectto PLANTApulse:
selected task (name)
project of the selected task (functional ID and name)
manager of the project
resource assignment of the selected task (name and code of the respective persons)
Calculated dates of the selected task
If you change particular data of a task which is already synchronized with PLANTA pulse, you have to reinitiate synchronization manually in order for the changes to be transmitted to PLANTApulse. Changes made to the data listed above are transmitted and changed in PLANTApulseas well.
As a result, only tasks which have not yet been synchronized will be displayed.
Click on Synchronize.
Once the synchronization is completed, a message is displayed which informs you on whether the synchronization was completed successfully or whether problems have occurred.
If errors were reported after completion of the synchronization, all transactions which have not run through will be displayed in the Pending Configurations module (PLANTA link). By opening the log file on the required transaction, you can track closely which errors have occurred.
If synchronization was completed successfully, open PLANTA pulse and log-on with the user which corresponds to the project manager in PLANTA project or to one of the resources assigned to the synchronized task, depending on whether you want to continue your planning with pulse or simply view the data.
Restrictions
Only projects can be synchronized with PLANTA pulse. Ideas, proposals, and programs cannot be synchronized.
As soon as at least one task has been synchronized with PLANTA pulse, the External system parameter can no longer be set to empty or be changed to another external system. The user is informed by a respective message.
(Master) milestones and summary tasks can no longer be synchronized with PLANTA pulse. If the user tries to convert a task synchronized with PLANTA pulse into a (master) milestone or a summary task, a respective message will be displayed.
If a task has been synchronized with PLANTA pulse, this cannot be undone.
Projects/tasks which are synchronized with PLANTA pulse (and exist in PLANTA pulse) cannot be deleted in PLANTA project. The user is informed by a respective message.
The resource assignment and the loads of a synchronized task, which have already been synchronized as well, cannot be deleted either. You can only delete resource assignments which have not been synchronized yet.
Only person resource assignments can be synchronized with PLANTA pulse. Departments, skills, material or cost resources cannot be synchronized.
A project manager must be assigned to the project and he/she must have already been synchronized with PLANTA pulse as a user. If a synchronized project manager is missing, a message will be displayed and the synchronization will not be started.
Effects of Synchronization
Effects in PLANTA pulse
A project corresponding to the PLANTA project project has been created automatically.
The name of the project in pulse contains the functional ID of the respective project from project.
The project name from project is displayed in the Description field in pulse.
The key of the new project in pulse is independent of the technical ID in project. A dedicated pulse key will be generated. Both keys are linked in the background to identify their affiliation for the update procedure.
The project contains a board which corresponds to the task which you have synchronized from PLANTA project before.
The name of the task is also the name of the new board.
The key of the board in pulse is independent of the technical ID of the task in project. A dedicated pulse key will be generated. Both keys are linked in the background to identify their affiliation for the update procedure.
The board already contains default lists (adopted from a stored template) which can be renamed or deleted if necessary. New lists can be created as well.
In the PLANTA customizer master data, default lists are defined as listbox values in listbox category 00000422.
If there are resource assignments on the synchronized task, they are also automatically copied to PLANTA pulse as board members.
If one of these resources is defined as Person responsible for the task in project, the resource automatically receives administrator rights for the respective board in PLANTA pulse.
The manager of the respective project in PLANTA project automatically becomes a board member, even if he/she is not assigned to the task as a resource. He/she automatically receives administrator rights for the respective board in PLANTA pulse.
Resources which are not assigned to the task or which are no project managers do not automatically become board members and cannot access the board in PLANTA pulse. This also applies to multi-project managers, persons responsible for the task, and resources which have synchronized the task, provided that they are not assigned to the task. These resources can, however, be invited to the board by the board administrators and hence become members with access to the board.
The calculated dates of the task from PLANTA project have been applied as start and due date for the respective board in PLANTA pulse.
A board which was created in this way is always set to "private" by default.
Effects in PLANTA project
For tasks which are already synchronized with PLANTA pulse, the number of cards which exist on the respective pulse board and the number of currently pending cards will be displayed in the Number pending/all cards field next to the task name in the schedule.
A traffic light is stored on the field which causes the number to be displayed in red if there are are overdue cards (due date lies in the past).
A link is stored on the field via which the Task module can be opened to view the PLANTA pulse cards in the PLANTA pulse area.
You can now view the PLANTA pulse boards of the project in the pulse Boards module which will be displayed in the Project panel as soon as a project has been synchronized with PLANTA pulse.
Synchronize Changes
Procedure
To send changes to PLANTA pulse (e.g. new task names or resource assignments), synchronization must be triggered again.
Click on the Synchronize button in the PLANTA pulse area.
If the synchronization is triggered in the Task module, not only the task is sent to PLANTA pulse but also possible changes made to the rest of the project.
Resynchronization from PLANTA pulse to PLANTA project
Information
Resynchronization from PLANTA pulse to PLANTA project takes place automatically. The following data is resynchronized:
Board member data
If new members have been added to a board in PLANTA pulse which is synchronized with PLANTA project, they will automatically be transmitted to PLANTA project as well and will automatically be assigned to the respective task as resource assignments, provided that
a user exists in PLANTA project which has the same e-mail address as the new board member in PLANTA pulseand
this user exists in PLANTA project as a resource the ID of which equates to that of the user.
The deletion of members of synchronized boards is not transmitted to PLANTA project.
