Components of Optima

Optima is a modular software solution. It consists of several interacting components. A typical installation of Optima includes:

• Network model

  The network model contains information about the demand and supply of the traffic network.

  When installing Optima, the network model is uploaded to the Optima database. The model is provided in the following set of files:

  • Files (.net, .dmd, .xml) containing the simulation model.
  • Files (.net, .dmd, .xml) containing the current model (optional).
  • Files PositiveArcs.bin and ReroutingData.bin containing the turning probabilities applied to manage re-routing events (optional).
  • Additional project-specific .sql or .backup files (optional). If these files exist, they must be applied on the database after the tprb.sql or .backup file.

• Database

  PostgreSQL ver. 17.4 DB, containing:

  • The network model.
  • The data collected in the monitored area.

• Optima application server

  WildFly application server (Java-based). WildFly was previously known as JBoss application server.

• An optional number of proprietary components

  • Java components (Windows and Linux server): Java back-end components.
  • .NET components (Windows server only): .NET back end components.
  • JavaScript components (Client browser): front-end components.

• Optima Micro

  The network models contain information about demand and supply for the micro simulation subnetworks.

  Micro simulation subnetworks, in PTV Vissim format, are copied with all complementary files to the respective machines, as listed:

  • Folders representing the different day types.
  • Subfolders representing the different micro simulation subnetworks.
  • Files (.inpx, .bew, .weg, .sig, .nodes) containing the micro simulation models, demand, path choices and accompanying files (for example, signal controller files).