Unmapped Rows in Vision Plans

The Planning grid displays the different levels of a project, the project, phases, and tasks, which are collectively referred to as the Work Breakdown Structure (WBS). Each WBS element must contain an identifier, which is how the project maps to a plan.

A Vision plan may contain elements, including resource assignments, that do not follow Vision Navigator plan rules. In Navigator, this can result in amounts on lower levels (rows) of the WBS not summing to match what is shown on higher-level WBS rows. This can happen if plan level rows other than those mapped to the project's WBS rows cannot be shown. However, when the plan is viewed in Vision, the amounts match what is shown for the higher-level WBS rows in the Planning grid in Vision Navigator.

Resources that are not assigned to the project's lowest WBS level could be excluded. In this situation, the Plan State Indicator includes the following message and a tooltip to alert you to the situation:

This message can also serve as an alert that there are conditions that will prevent you from changing this Vision plan to a Vision Navigator plan.

Some of the potential errors include:

• The Vision plan's phase or task rows are not mapped to the project's phase or task rows.
• The Vision plan includes Labor Code rows.
• Resource assignments are not at the lowest level of the WBS.
• The Vision plan has Cost or Billing as the Budget Type.
• A resource was assigned more than one time to the same WBS row.