In order to support Short Term Conflict Alert the track informatioin need Plot Ages

Proposed solution : Addition of I030/290 - Plot Ages

Addition of I030/290 - Plot Ages

Proposed name: Surveillance User Interface.1.

Change name to Surveillance User Interface.1.

Clean up and removal of the initial 10 pages describing the specification plan;

Proposed solution : Clean up and removal of the initial 10 pages describing the specification
plan,

Clean up and removal of the initial 10 pages describing the specification

Calculated Track Position - this should be in latitude
and longitude to support retrieving track information without having to
define a special set of adaptation of the system plane

Proposed solution : Use latitude and longitude for Calculated Track Position

Use latitude and longitude for Calculated Track Position

the units utilized should not limit the scope of the
interface, so Plot ages should not be limited to be from 0 to 64
seconds and should contain a full floating point value (even negative values
would make sense in the case one wanted to request smoothed data instead of filtered data for
calculation of some bias values).

Solution proposed : used full floating point value for Plot ages.

Used full floating point value for Plot ages define in Issue 4811.

A new issue for surveillance manager FTF.
In order to support Short Term Conflict Alert the track informatioin need Last measured Mode C.

Proposed solution : Addition of I030/140 - Last measured Mode C

Addition of I030/140 - Last measured Mode C

Proposed solution : to add field I030/270 : local track number

to add field I030/270: local track number

It impossible to know when the altitude profile is coasting apart from
the lateral track.

Proposed solution : Add IDL field in Track Status specifying how the
altitude profile is coasting.

Add IDL field in Track Status specifying how the altitude profile is coasting

Proposed solution: to add field I030/360

The field reported position (I030/360) is missing

Proposed solution: to add field I030/090

see above

Ranges were defined to map exactly asterix field. It is better to enable any unit range by using
unbounded unit type.

Proposed solution: to use unconstrained IDL type.

To use unconstrained IDL type.

It was request by the AB to remove union and drop empty field. This field lay out was used in Avenue
to reproduce the asterix field lay out.

In IDL it is useless.

Proposed solution : to suppress union and empty field.

To suppress union and empty field

Refer to the Transportation architecture White Paper to set the context
for the scope of the submission

Proposed solution: Refer to the Transportation architecture White Paper
to set the context for the scope of the submission

Add reference to the Transportation architecture White Paper

Field I030/180 - Velocity - Should be stipulated that the velocity
heading component is relative to True North.

Proposed solution: precise in the specification that the velocity
heading component is relative to True North.

see above