|
|
Complete oneiro-platform for business simulations – the COBS platform My business simulations utilise a platform that consists of assemblies of standard routines that provide a basic framework that is used to encapsulate the simulation model and its database. |
Here I explore and describe my simulation architecture showing the software that is common to a range of business simulations (simulation platform elements - green), the software that is used by a specific business simulation (simulation specific elements - grey) and the interface components (input, display & printout - purple).
|
|
|
Standard platform elements Simulation Manager |
Simulation specific elements Simulation Model |
Each simulation type has a different simulation manager that manages the business simulation and provides the interface with the user. Each of these have different processing cycles but consist of the same components.
There are several simulation managers that address simulation design needs comprehensively.
For the Tutor Mediated shell, one computer and printer is needed for each group of between two and eight teams of four or five participants. The Direct Use, Planning, Decision Support, Negotiation and Analysis shells require one computer (and, depending on the simulation, a printer) for each team of three to five participants.
Although each simulation has a different simulation manager that manages the business simulation all simulation managers have the same user interface (Desk Top). This means that once a trainer is familiar with one business simulation he or she will find it easy to use another.
This controls the content, style and timing of reports. The report to be displayed and/or printed is selected by the Simulation Manager based of the Control File. The data for the reports are derived from the Parameter Database and the report structure is set by the Reporting Database, After creation, the report is transferred to the Display/Printing Engine for output.
The Decision Entry Engine is used by the Simulation Manager to enter decisions. The Control File and the Reporting Database define the timing, content and form of the data entry screens.
After entry is confirmed, the Decision Entry Engine uses routines in the Simulation Model to check the data for illegal, unusual and problematic values. Depending on the simulation, a copy of the decisions is passed to the Reporting Engine for display or printing.
My platform has a context sensitive, hypertext help system to help with the program, advise on the current task, explain the current display and provide an online Manual. The Help Engine chooses and displays data from the Help Database when requested by the Simulation Manager.
This controls the way reports are output to the microcomputer's screen and to the printer. Specifically, it controls the font size of the display and the way rows and columns are displayed. (These options are set in the Control File.)
This file provides data used by the Simulation Manager to define which hypertext help is to be used to support program use and what texts are to be used for the user interface. Depending on the type of simulation these are pre-set and must not be changed.
This file provides the text used by the Simulation Manager. A single text file serves all simulations that use the same Simulation Shell. By placing the text data in a file it is possible to provide the simulation in languages other than English.
The simulation model and the data that drive it are the only parts of the business simulation that need to be programmed. The simulation model consists of several sections that are used by the simulation manager.
This consists of the data that controls the operation of the business simulation. It defines the reports used, the decisions to be made, font sizes etc. By having several Control Files the designer can provide several versions of the simulation to address different training needs, trainer skills or market segments.
This database stores the parameters and data used by the simulation model. The database structure is based on experience developing sixty-five simulations and is appropriate for over ninety-five percent of simulations. However, for very complex simulations, it is possible to incorporate additional databases.
Storing parameters and data in a file allows different terminology, languages and situations to be made available very quickly and inexpensively.
As simulation takes place, the data in the parameters database is fully journalised. So, it is always possible to return to an earlier period and rerun the business simulation from there (to correct entry mistake or to explore different strategies).
This database stores the data defining the simulations reports and decision templates used by the Reporting Engine to produce output. A comprehensive range of report structures is available that cover all normal needs. However, for very complex business simulations custom reports can be used. Storing reports and decisions templates in a file means that no time is spent programming these and different versions of a simulation can be provided with a different set of decisions and results.
This database stores qualitative comments and their associated parameters. These are used to comment on decisions, results, leak information to other teams and list strengths and weaknesses.
This database serves two purposes. It stores the basic help with the use of the Simulation Platform and, optionally, an online manual and explanations of reports and terms. The database has full hypertext capabilities and is used by the Hypertext Help Engine to provide context sensitive help about how to use the software, the current task, explanations of report content and comments to stimulate thought. Besides text, the help database can play sounds and display pictures.
Most recent update:11/05/12
Hall Marketing, Studio 11, Colman's Wharf, 45 Morris Road, London E14 6PA,
ENGLAND
Phone +44 (0)20 7537 2982 E-mail jeremyhall@simulations.co.uk