Note: The Airport Info Portlet, which is the front end for the AirportPlan entity, is meant to provide airport information per airport.
The data is fed from the Airport corner tool. This upload is an automatic process, run by each airport unit.
The AirportPlan folder holds all the issued Airport Plan documents:
General
A single General tab contains all the AirportPlan edition parameters:
Airport
This is where you will either type in the name of the relevant Airport (note the autotype feature - see below what shows up as you type in L - I - P ...) ...
... or drag and drop an item from the Airport list:
Season
Airport Plans are seasonal- unlike ACC Plans which are yearly.
Select the season (SUMMER or WINTER) from the Season pull-down menu, then type in (or use the up and down arrows) next to the Year field to indicate the period for which the plan is valid:
ACC Image
This is where you will drag and drop the image (or more exactly, the image name as is appears in the File Resources tree), to be published on the NOP.
ATCFM Events Comments
This first text area is reserved for ATFCM Events Comments.
Overview
This is where you place the text to appear in the Overview section of the ACC Plan.
Planned Capacity - Enhancement Measures
Place in this other text area the relevant content to be published.
Prospects
This panel contains two elements, Table and Comments.
The Table is a 5 columns x 4 rows one, which you can use freely.
Data are fed manually monthly, rows and columns labels are editable and should be adapted at the start of the year when creating a new ACCPlan:
| Target Delay per Flight (min) | Forecast Delay per Flight (min) | Actual Average En-route Delay per Flight (min) | |
| Year | Data | Data | Data |
| Year | Data | Data | Data |
| Year | Data | Data | Data |
The Comments text area is there for you to enter additional comments to the Prospects panel.
Actual Traffic - Delay Follow-up
This is another Table - Comments group.
This table is automatically updated by a monthly PFR file upload. It is can however be edited, following a decision to adapt the content. The table structure is however not editable.
When completed, this is how this table is rendered in the NOP:
Lastly, the Keywords and Display Period are to be completed in the same way you would do for any WIND entity - please see here for details about the Keywords and here for details about the Display Period.