1 / 7

Multi-Stage Event Planning Status Type for Air Traffic Management

This code pattern enables the exchange of various planned values in different stages of event planning, such as scheduled, estimated, and target values. It provides guidelines for using different specialization codes and attributes for accurate event status tracking.

roland
Télécharger la présentation

Multi-Stage Event Planning Status Type for Air Traffic Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CodeEventPlanningStatusType Qualification of the planning stage where the information is coming from. In ATM, information exchanges do not only contain the best known planned value. They can contain several values coming from different planning stages such as the scheduled value, the estimated one and the target one.

  2. How its works? • All specializations share the same code list and attribute eventPlanningStatus • Name of temporality attribute shall be free but can basically capture • Time(no prescribed data types) • Duration (no prescribed data types) • Classes from this pattern can be instantiated in various ways, e.g. • Take-off • With eventPlanningStatus = ‘ACTUAL’ • Time = <value> • Taxi-out • With eventPlanningStatus= Estimated • Duration = <value>

  3. AIRM Constraint: • For example, a certain flight during certain life period in time shall have only ONE instance of data-entity ‘Taxi-Out’ with combinations of attribute eventPlanningstatus = ESTIMTED and period, i.e, only one EXOT. • Each PlanningStatusEntity including all its specializations shall-have at-most-one unique instance with eventPlanningstatus equal-to one-of-the values of 'CodeEventPlanningStatusType' in closed time interval between StatusTemporalEntity.startEntityLifeTime and StatusTemporalEntity.endEntityLifeTime

  4. How to use it • Specialise from PlanningStatusEntity • Attributes can be expressed as: • time – meaning that is event happening at certain time of type “Date Time” • period – meaning that is event happening at certain time of type “TM_Duration”

  5. TM_Duration Date Time

More Related