User Guide

• A new project with an earlier due date deletes a modified object.
• An instant change deletes a modified object.
• An existing earlier project that creates the modified object is rescheduled for a later date, or is deleted.
• Space Conflict - A resource conflict occurs when a project attempts to consume resources that are physically
impossible to consume, such as two assets in the same physical space. The user interface attempts to avoid
letting this happen but in special circumstances it is possible through project reorganization or deletion of
project actions.
These conflicts occur when:
• A new project with an earlier due date adds an object into a reserved space.
• An instant change adds an object into a reserved space.
• An existing, earlier project that makes the space available is rescheduled for a later date, or is deleted.
NOTE: The application detects conflicts in projects when you perform any of the following actions: move a project, delete a project,
delete a task or use the undo option.
NOTE: In rare circumstances, a shelf space may remain visible in future projects even though it was deleted prior to that project's due
date. This "phantom" shelf space is the result of deleting the shelf space prior to the project task that relies on its existence, thus
producing a hard conflict. For example, consider adding a shelf space to a rack in the current floor plan. If this shelf space is modified in
a future project by moving it, the move becomes dependent on the existence of the shelf space prior to its move. Deleting the shelf
space from the current plan will trigger a hard conflict when the project is revalidated. The user is then presented with a current plan
that has an empty rack position and a future project that still indicates the existence of a shelf space in the rack but with a hard conflict.
In order to avoid this problem, which may result in a project conflict that cannot be resolved, it is advised that shelf spaces not be
moved or modified in future projects.
NOTE: When an asset is placed in a rack in a project, any projects created earlier on the calendar cannot utilize that rack space. To
make the same space available for prior projects, you must remove the task in project details that added the asset, rather than simply
deleting it from the rack view of that project. Deleting an asset in a project that also adds the asset creates two tasks: one to add and
another to delete. Therefore, any project that tries to use what appears to be an open rack space will encounter a hard conflict.
Conflict revalidation
When a project is committed and conflicts occur, the conflicts must be resolved and the project revalidated for a
new commit. You must have planner rights to resolve conflicts and revalidate projects.
NOTE: A project reviewer can click the Revalidate button to refresh a project, making sure the project is current.
It is assumed that the executor committing the tasks where conflicts occurred notified the planner of the status
and advised that the conflicts be resolved and revalidated before the project is committed.
To revalidate conflicts:
1. Select the project with conflicts and select Project Properties.
2. Open the tasks tab to view the conflicts.
3. Adjust project tasks to resolve conflicts.
4. Open the Status tab and click Revalidate to update the project.
5. If no other conflicts are listed, the project can be committed.
Chapter 13: Planning 127