User Guide

• A history tab which shows a time stamp of all changes on the selected date and a count of actions for that
time.
• A project search tags tab where you can search for groups of projects.
• A current state button that takes you back to the current floor plan and out of project or history mode and
returns the calendar to the current date.
• Click on the month/year bar at the top of the calendar to view all projects or history for the entire month.
• If you hover over a calendar date containing projects, a tool tip shows project information for that specific
date.
• If you click on a date in the past, an alert message opens stating that the current floor plan did not exist on
the selected date.
Project Status
Conflicts are the result of exceeding capacity limits in space, heat, weight and power between projects. In each
metric, it is determined whether the conflict is soft or hard. You are alerted when your changes conflict with
changes already planned.
For example, two projects may both plan to use the same space in a rack for two different assets. Some conflicts
are minor enough that the project may be committed without adjustment. This is referred to as a soft conflict. If a
conflict is severe enough that the project cannot be committed, such as contradicting the current floor plan, it is
in a state of hard conflict.
Soft conflicts
Change Conflict - When the preconditions of a project change, the project is in change conflict. The
precondition of a change is its original value. For example, if a change changes the name of rack Sal to Hal, the
precondition for this change is that the name of the rack is Sal. This is an error checking mechanism, which helps
you coordinate your changes and not accidentally overwrite one another.
A project goes into change conflict when:
• A new project with an earlier due date makes a conflicting change.
• An instant change is made that causes previously saved project actions to become invalid due to that
projects preconditions.
• An existing earlier project with a required change is rescheduled for a later date, or is deleted.
Resource Conflict - If a project increases the consumption of power, heat or weight resources and this increase
causes consumption to exceed capacity, the project is in resource conflict. This is an error checking mechanism,
which helps you coordinate your changes and how those changes consume resources.
NOTE: When adding racks to a plan in a project that have a default weight set to zero in plan properties, a soft conflict will be detected
since the rack has inherent weight when empty. It is recommended that the default weight capacity setting in plan properties set to
exceed the weight of an empty rack in order to avoid this conflict.
Hard conflicts
• Existence Conflict - An existence conflict occurs when the precondition requires the existence of an object
that no longer exists.
These conflicts occur when:
126 Data Center Planner Installer/User Guide