Equivalence: The Core Concept of Modeling

The most important thing to remember in carrying out your projects is that modeling is fundamentally about equivalence. In other words, your objective is to build a model that is equivalent to a real system, existing or proposed. However, equivalent is a subjective term which must be defined more precisely. Clearly, equivalence means that your model behaves in some sense like the real system. Nevertheless, for practical reasons, models are usually limited to representing only certain aspects of the system of interest. Therefore, it is up to you to define equivalence for your modeling project, with the following objectives in mind:

  • The model must answer the questions of interest – You want to use the model to help you study a particular set of issues. You need to define those issues clearly before you start your modeling effort. Knowing which questions are important will allow you to exercise good judgement in including or omitting certain features in your model. The answers you obtain from your model and their utility are the ultimate benchmark of your modeling effort’s success.
  • The model should have the desired level of accuracy – Your model’s accuracy can probably not be perfect, but you need to have a notion of whether you are making simplifications in your model to the point where the answers it provides will no longer be useful. Depending on the types of actions you will take as a result of your model’s predictions, you should determine how conservative you want to be with respect to simplifications.
  • The model should support validation – When designing a model, you should have a plan for building confidence in the results it produces.
  • Your model should accommodate the necessary range of operating conditions – Usually, the system of interest, and therefore the model, is subjected to a range of different stimuli. For a network model, this may mean increased application traffic, or new application patterns, for example. If you know the range of conditions you want to study, consider how to ensure your model will maintain its validity throughout that range.

So equivalence is really a function of what you want the model to help you accomplish. As you make each modeling choice, such as which component to use from the model library, you need to ask yourself if this choice could disturb the equivalence which you have achieved so far, or if it enhances it. Even if it does in some sense lessen the equivalence between your model and your system, does it achieve another benefit for you that is worthwhile, such as reduced simulation run times? And then finally, can you measure the relative loss or gain of equivalence to help you determine if it is acceptable?

The important point is that good modeling practitioners do not necessarily have precise answers to all of these questions, but they keep these issues in the forefront of their minds as they make modeling choices. This is something you should do as well as you consider various approaches to representing your system as a model.