Example - Long term planning

Owned by POROSNICU Eduard
2020 Sept 07

For example, the planning of a military exercise event may take place well in advance of the effective date. When the first details, even not very precise, about the event are known, an Event feature can be encoded. This can eventually refer to the concerned airspace, etc. as shown on the following diagram:


ToDo - redo diagram - The coloring of the attributes is misleading. We should have one color for unchanged attributes, one for changed ones, and probably also one for new ones?

As the planning progresses, further details about the event become available. In the final stage, the necessary Airspace TEMPDELTA (airspace allocation) is also encoded and it includes a reference back to the Event to which it belongs, as shown on the diagram below.

Questions (from Google Docs) from Wolfgang Scheucher

  • Shouldn’t also the Event be updated? At least the revision attribute?
  • The attribute “levels” is part of the TEMPDELTA even if it is not changed compared to the BASELINE. Is this on purpose?
  • Why is the Military usage linked to the Event? Shouldn’t it be the whole TimeSlice?
  • Is the concerned Airspace the TEMPDELTA Airspace or the FIR were the airspace is located in?
    • POROSNICU Eduard As far as I remember the eASM document from which this example was taken, the concerned Airspace is the FIR where the active airspace is located. To be checked and the diagram should be corrected. It looks like a circular relation for the moment, which is not correct.