Scenario

Stakeholders and Scenarios

A scenario is an Item that stores a series of settings, actions and events that can be activated automatically. For example, a scenario can:

• Activate one or more measures.
• Activate areas or neighborhoods.
• Adjust attribute values and globals.
• Activate events.

By default, a project in the Tygron Platform always consists of at least one scenario.

When you have multiple Scenarios, for example with two different designs for your Project, you can switch between them from the ribbon bar in the editor. Currently, only one scenario can be active at the same time. Actions taken in a different scenario are reverted.

Limit Map

Scenarios can be limited to a specific part of the map by setting the 'Limit Calculation Scope' to 'Measure Neighborhoods' in the Editor. This limits calculations to only those Neighborhoods covered by measures. Using the margin attribute a margin can be added around the Neighborhoods.

Attributes

The attributes and description of an active Scenario are persistent (not reset) when stopping the testrun. This allows users to store attributes for later comparison between Scenario's.

Notes

• Scenarios are intended to become parallel planned situations

How-to's

• How to add or remove a Scenario
• How to change properties of a Scenario
• How to use a limit map in a Scenario
• How to change Events fired by a Scenario
• How to change Measures activated by a Scenario
• How to configure the available actions of a stakeholder per scenario
• How to configure an intro Cinematic for a Stakeholder and a Scenario

API Endpoints

• Api session items scenarios
• Api session event editor scenario
• Api session event editor activate testrun

---

Multi Scenario

Multi Scenario

Stakeholders • Scenarios • Zoom Levels

Editor

Current Situation • Future Design • Multi Scenario • Tools • Community