The following is a continuation of the storyboard on a modeling interface started on 2/14/2011 and provides examples of the second and third requirements:
- Select or create prebuilt models to drive the calculations
- Select and configure specific processes within the selected model
This allows the budget preparer to forecast and plan in a flexible user interface and allow them to change parameters and drivers of the model rules.

Click the thumbnail to enlarge image
- This box identifies all the rules to be run associated with the models.
- This line highlights the rules currently being edited
- This area sets both the calculation method and the parameters that drive the method
- The segments area identifies the scope of the calculation.
In this example the rule will be run for the for all the children under “applications” product segment.
In addition to a rules based approach to modeling, the system also needs to provide a template/spreadsheet based mini-model approach because many calculations can be cumbersome to construct using a rules based modeling approach but can be expressed rather easily in a spreadsheet model. The combination of the rules based approach and the mini-model approach support both macro and micro modeling.
An example of macro modeling would be adjusting sales by 10% up or down for a given division because of changing economic conditions and applying that change proportionately across the existing customers/product lines.
An example of micro modeling would be to adjust all the cost components (COGS) of products that leverage silver in the manufacturing process because of commodity price changes in silver (adjusting PPV).
Think of a mini-model approach as typical cost calculations you have in an Excel spreadsheet for a particular product or product line and imagine the ability to run this Excel spreadsheet against every product and save the results back to the database. Furthermore, imagine you have done that, didn’t like the results and which to rerun with different parameters.
This mini-model approach requires:
- The ability to create an Excel like model that is database driven to maintain referential integrity.
- The ability to assign an individual product, customer, or budget entities to a particular template for processing.
- The ability to create a processing sequence out of these individual assignments of product, customer or budget entity and Excel like template.
- The ability to run the process in the context of other macro business rules.