Graham - Omniscope supports multi-variate scenario modelling via Variables (assumption values not part of the data set) which can be incorporated into Formulae fields and manipulated using devices by end users, including free Viewer users. Among many other choices, there is the option to create Logic Choice Variables which are Boolean, in other words 1 or 0 displayed as True/False radio buttons which end users can toggle. Currently, if you create a Logic Choice Variable, you can use it as a 'switch' to multiply any formula or expression by either 1 or 0. The Idea of replacing the end user display of Logic Choice Variables with a checkbox would save a lot of space, and large numbers of these switches could also be displayed to end users by enabling Variable control devices to display in the Device View adjacent to the Table View, rather than only the Sidebar.

However, there is another aspect of scenario modelling using Variables and Formula fields/columns. Omniscope formulae/variables are not the same as spreadsheets, which permit arbitrary row and even cell references in formulae. The above approach works only if the end user is manipulating calculations/values that affect entire columns/fields, NOT individual cells. This approach can be used to manage sets of rows, but only if a flag column/field is used to classify each row/record and this flag referred to in the formula bearing the switch Variable.

Another way to do simulations involving changing subsets of rows IN or OUT and re-calculating across selected Subsets is to use Named Queries and Content View to display summary formula which react to the end users' choice of scenarios/row subsets by selecting different pre-defined Named Queries that filter out various subsets of rows. Named Queries are currently accessible from the View Toolbar Subset and Queries drop-down, but as an Idea could also be displayed from a Devices View if the Main Toolbar is to be hidden.

If you want to pre-define multiple scenarios of cell-level input values, with no pattern in terms of either columns or rows, you can do this by using multiple input sources, and allowing the end user to change between the tabular input scenarios using the DataManager Input Switch. An idea would be to expand the concept of the Switch to multiple input scenari and expose the Switch to even free Viewer users on the Sidebar and Device View to enable them to manage multiple scenari involving pre-defined cell level changes to the values.

Finally, if you want the end users themselves to be able to make arbitrary changes to un-protected values at cell level, you can do this two ways. If the audience who need this option is relatively small, you can simply activate their free Viewers to upgrade them to Desktop Editions and they can make local edits directly in the Table View. If the audience that needs to submit new values for re-calculation and optimisation is large, a Web Services architecture that uses the Omniscope Web View to display an input form, with a 'round trip' of posting the changed inputs, re-calculating centrally and refreshing the remote data set for display in the local Omniscope is also an option.