Unlike other modeling environments, our approach allows the user to focus on solutions instead of technology.
Because our focus is on modeling rather than whatever the current fad in information systems might be, we understand that the role of technology is to provide you with tools to leverage your technical skills
for greater impact on your organization. Technology is not regarded as a goal unto itself but merely a means to an end.
The Modelogics' approach is simple… provide a medium that
integrates state-of-the art computer modeling capabilities with common PC desktop tools such as word processing, presentation graphics and spreadsheets. Working in a familiar Windows "look and feel"
environment, we bring together the actual technical work of your job and all the mundane but time consuming tasks associated with reporting and presenting results.
Something else we understand is that you can't force everyone with which you work and exchange data to use the same tool. That's why our architecture includes the ability to incorporate existing "models" such as
"dusty deck" Fortran codes, Excel spreadsheets, CORBA objects and others right into your own model with minimal setup. This enables collaborative
trade-study analysis that can be interactively performed with co-workers, suppliers, team partners and even customers.
Our Software, Model Engineer is a PC-based modeling toolkit (as opposed
to an application) that facilitates the building, running and analysis of custom processes and system models. It consists of two distinct parts, the modeling
tools (or infrastructure), and the application libraries, with each library aimed at a different technical discipline.
Currently there is one library for thermal systems analysis, but Model
Engineer's ability to create user defined components makes building your own library quick and easy. That means you don't have to wait on us to provide components to meet your needs… if you have the subject matter
expertise, you can build your own library in no time. In fact, you'll spend more time gathering the technical information and designing your
components than you'll spend actually creating them… which is as it should be!