Skip to main content
Eptura Knowledge Center

Publish the Phase to Live

When the Scenario Plan is completed, you can publish the Scenario Plan and this will update the Live VBS data. The Push a Phase will implement for the Phase at a Team level, Neighborhood level, and/or Unallocated Spaces. The blocking and data changed in the Team, Neighborhood, and/or Space forms will be updated too.

Important Prerequisites


Before you publish need you to consider the following.

Review the Team Moves

  • As you complete the Scenario, review the Scenario Team Moves and be mindful of the changes that flow through from the Live VBS data and the changes that do not flow through Live VBS data. This is detailed in Review the Scenario Move Plan Summary and the article describes when to use the Synchronize Phase.

Synchronize Phase

  1. How active are your Scenario Planners in applying reactive changes in the Live VBS.
  2. When was the Scenario created? Is the Scenario a day old, a week old, a month old, or even older. If the Scenario is old (this is for you to determine) then it will be out-of-sync with the Live VBS and it will have the potential to override the Live VBS data

For details on the different situations and the outcome of the sync from the Live VBS data, refer to the article Synchronize Phase from the Live VBS.

Scenario Security

Users require the secured action Scenario Plan - Publish Plan for the Publish icon to be enabled.  
 
If you require the access, then contact your System Administrator. For information on how to add secured actions to a role, refer to Manage User Roles.

Publish a Phase


When you have completed the prerequisites above and are ready to publish, all it takes is one click of the Publish a Phase icon and then head on over to the Live VBS to see the changes.

If you are new to Scenarios and want to visualize what will happen to the Live VBS when you Publish a Phase, then review the following examples:

Currently, in your Scenario Move Plan you only have one phase.

  1. Click the Scenario Move Plan clipboard_e575992991b2b6ff09ef9b2f9a3b6d57d.png icon.
  2. Select the phase.
  3. Click the Publish this Phase clipboard_e5ac7d68fd8c3e353e0fea0c4ccfa8b75.png icon. 

clipboard_e7eefb633dd7187c7bc905f4a4ab7866a.png

This Publish Phase 1 dialog displays.

This contains the warning "Consider synchronizing the Scenario Plan before publishing this phase."

clipboard_ec27c1424ccb96f34b0442c16f081c43e.png

4. Click the OK button.

The Scenario Plan data is published into the Live VBS data.

Review the VBS and then update Occupancy

Now you can go to the Block and Stack (VBS) to view the changes and then consider how you will update the occupancy in the Live VBS.

In regards to occupancy this will depend on if the team is fixed or flexible and the following will occur:

Fixed Teams

Fixed Teams have people assigned to desks, and the occupancy data is contained and reflected within the Scenario VBS, including vacant and retained desks. For Fixed Teams, Scenarios do not specifically manage the moving of people.

After the Scenario Plan is published, the moving of the people in Fixed Teams from their assigned desks is completed from either:

  • manually in the VBS or in bulk using the Occupancy Import
  • the Business updates the occupancy manually via Workplace
  • using a BOS Move Plan

Flexible Teams

For Flexible Teams, the people are classified as being part of the team’s identity.

After the Scenario Plan is published, the people will be moved. The exception to this is where you have a person who is sitting in an anchor desk (a fixed person within a Flexible team). They will need to be moved individually after the Scenario Plan has been published, this can be completed from either:

  • manually in the VBS
  • the Business updates the occupancy manually via Workplace
  • using a BOS Move Plan