Why Simulation Engine is Needed

After changing an existing template - when a template has been set up, deployed and budgeted to, and then changes are made to that template’s design / set up. The Simulation Engine will save each template’s data based on the new structure without having to open and save each template individually. For example, Budget Admin user changes a formula in a Calculation row of an existing template and needs the new formula results stored in the database.

After seeding a new scenario - when seeding data from one scenario to another scenario, as soon as a template is opened the seeded data is pulled into the template but it will not be available for reporting until the template is saved. Once the template has been saved the seeded will be available for reporting.

After changing the value of a Global Field - when a template has rows driven by Global Fields, changes to those values need to be “processed” at the individual template level. The Simulation Engine will save each template’s data based on the updated Global Field values without having to open and save each template individually.

Large HR batches - when processing a large amount of employees an alternative solution would be to schedule a Simulation Engine process

Template drivers – when you have templates that drive other templates, using the Simulation Engine may be useful in pushing updates from one group of templates to others.

The Simulation Engine should NOT be run when users are budgeting!

Plan Scenario - to trigger the Intelligent Seeding functionality. Admin users must schedule a simulation engine process to ensure all the data is transposed properly. In addition, Admin users must select the Enable Subline Processing setting and then run a simulation process. This is to ensure that the process runs for Main lines and Sublines together, when the process is run for the first time.