|
|
|
Whether you are a simulation developer, user, or manager, there are
many benefits to using FLAMES. Click
above to view a If you have trouble viewing, download Adobe's Flash Player. |
|
| ||
|
FLAMES® is the only commercially available simulation framework that provides open-architecture support specifically for constructive simulations and that addresses all aspects of constructive simulation development and use. For developers of this type of simulation, no other product even comes close to FLAMES.
If your current simulation is in need of an overhaul or you don't yet have a simulation that will meet your requirements, you've come to the right place. With FLAMES, you can get more capability than you think is possible in less time and at a lower cost than you ever expected.
Here are just a few of the reasons to use FLAMES:
FLAMES solves the hard problems facing designers of reusable, object-oriented simulations. FLAMES defines the right classes at the right granularity and establishes the right relationships between the classes to form a working, complex system. The FLAMES design has been proven in dozens of simulations in over a decade of continuous use. If you use FLAMES, you essentially eliminate the design phase of your development effort, and your design will be right – the first time.
Much of the software required by nearly every simulation is already present in FLAMES. You don’t have to write it, test it, or debug it. Just as important, the software you will have to write – the model software – will be easier to write, because you will be working with a religiously object-oriented system with the right classes already defined. Plus, you’ll have abundant examples and Ternion technical support. You’ll even have documentation. (Imagine that!)
Ternion maintains FLAMES. We fix the bugs (we had one once), we add new features, and we keep it current with the latest operating systems. You only have to maintain and enhance your model code. But that’s not all. Because your models will be developed according to FLAMES’ standards, you’ll be able to change them with little or no effect on other models, and you’ll be able to plug in new models with virtually no integration effort.
The models you develop for one FLAMES-based application can usually be reused in another – without modification. Use your models over and over again in multiple projects. Share your models with other FLAMES users – across the hall or across the ocean – without having to share your source code. Establish model reuse repositories that work and eliminate redundant software development efforts.
Breathe new life into that conglomeration of antiquated spaghetti code that others call a simulation. Re-host the models and algorithms you still like onto the mature, proven framework provided by FLAMES. A re-hosting effort will probably cost you less than it costs to maintain your legacy software for just one year, and you’ll recoup that investment ten-fold in the years to come.
How many man-hours are required to build a scenario for your simulation? How many people does it take to execute the simulation? How many times do you have to run it to get the results you want (or to finish without crashing)? How long does it take to process the results? You might be able to pay for a FLAMES license a hundred times just from the savings you would derive from using a FLAMES-based simulation.
How much is it worth to you to get a simulation that works – one that does exactly what you need it to do when you need it? Put it another way: How much is it costing you to not have the simulation you need? Can you afford not to use FLAMES?