Simulation Scenarios

A simulation scenario names the assumption set a model uses. It belongs to an organization and can carry effective dates and a policy reference. The Process Owner chooses the scenario for a model before asking for validation. When the Simulation Operator runs a reviewed revision, the workflow snapshots the assumptions so the result can be read against the basis that was effective at the time.

Suppose a service team changes its arrival pattern for a seasonal period. The team can maintain a scenario for that period and link the intended model revision to it. The resulting cycle time then has context. Reviewers can distinguish a process change from a changed assumption instead of reading both as improvement in the modeled steps.

• Scope. Organization ties a scenario to the operating entity that owns the model.
• Effective basis. Effective dates and a policy reference explain when the assumptions apply.
• Mapping. Source mappings describe source and target fields, types and transformation rules by version.

Decide who can activate a scenario, how its code is assigned and what the policy reference points to. Establish an effective-date convention that prevents two scenarios from being casually treated as the same basis. Agree whether a change to an assumption calls for a new scenario, a new model revision or both. This decision is essential when the team compares results from different dates.

If external inputs are used, the team should review source-to-target mappings before relying on a run. Name the connector definition version and agree how source and target fields are checked. A transformation rule should be understandable to the person who will verify the output. The mapping record describes the intended conversion; the executed step and receipt provide the evidence of what actually happened.

Set up a scenario for a defined operating period, link it to a draft intake model and confirm the organization is the intended one. Add a source mapping for one incoming field used by that scenario. Ask the Model Designer to explain the mapping version and the rule to the Independent Reviewer.

Validate the model and record the review decision before starting a simulation. Then inspect the run, its source revision and result reference. If the policy basis changes after the run, use the preserved run trace to explain the earlier result. Do not reinterpret it using a later assumption without creating a new controlled comparison.

• Validated models awaiting simulation — Find validated models and check the separate review decision before a run.
• Model revision workboard — Compare the scenario link while moving through the model lifecycle.

Use model preparation to choose the scenario and simulation execution to check the frozen run basis.