phpVMS 7 has a few fundamental differences from the old version, on how schedules and flights are handled.

One or more airlines needs to be created. Users choose and airline on registration.

Airports can be added to the system, and optionally selected as hubs. When users register, they select a home hub.

An unlimited number of fares can be added, and then fares are attached to subfleets, therefor, all of these fares are then applied to any aircraft in that subfleet. These include examples of "First Class", "Economy", etc. You can add as many or as few as you want. Fares include:

  • Capacity - how many seats this fare class holds
  • Price - the amount a ticket in this fare class costs
  • Cost - the amount it costs for a ticket; this is the amount it costs you to run a single seat

In order to facilitate not needing multiple fares of the same type, but with different capacity/costs/price, when a fare it assigned to a subfleet, those properties can be changed on a per-subfleet basis.

In phpVMS 7, aircraft are now organized into units of subfleets. Subfleet examples may include 744-GE, where you can handle any number of Boeing 747's with GE engines. This mimics real-world operations.

  • Subfleets have a name, type and a fuel type. The name and type are arbitrary, and just convention to your VA. Here's an example for Continental Airlines
  • Any number of aircraft can be assigned
  • Any number of fares can be assigned, and the properties overridden.
  • Any number of subfleets can be assigned to a flight

Schedules have been renamed to "flights". A flight consists of:

  • An airline
  • Flight number
  • Departure airport
  • Arrival airport
  • Any number of subfleets

Flight numbers do not need to be unique, however, if a duplicate flight number is found, the creation/edit will fail, and a route code or leg must be provided in order for it to work properly.