Issues for Surveillance Manager Revision Task Force
To comment on any of these issues, send email to surveillance-ftf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.
List of issues (green=resolved, yellow=pending Board vote, red=unresolved)
Issue 4807: Change name of standard because it addresses only a subset of the RFP
Issue 4811: Issue surveillance FTF: Plot Ages
Issue 4812: Issue surveillance FTF: Last measured Mode C
Issue 4813: Surveillance FTF issue : used full floating point value for Plot ages.
Issue 4814: latitude and longitude for Calculated Track Position
Issue 4815: removal of the initial 10 pages
Issue 5336: Suppress union and empty field
Issue 5337: suppress type range to broaden the scope of the interface
Issue 5676: I030/080 - ARTAS Track Status
Issue 5677: The local track number (I030/270) is missing
Issue 5678: Missing track quality (I030/090)
Issue 5679: Missing radar-reported position (I030/360)
Issue 5680: Field I030/180 - Velocity
Issue 5681: Add reference to the Transportation architecture White Paper
Issue 4807: Change name of standard because it addresses only a subset of the RFP (surveillance-ftf)
Click here for this issue's archive.
Source: THALES (Mr. Emmanuel Fuchs, elfuchs(at)club-internet.fr)
Nature: Uncategorized Issue
Severity:
Summary:
Proposed name: Surveillance User Interface.1.
Resolution: Change name to Surveillance User Interface.1.
Revised Text: Replace on front page title with Surveillance User Interface.1.
Actions taken:
January 17, 2002: receive dissue
February 14, 2003: closed issue
Issue 4811: Issue surveillance FTF: Plot Ages (surveillance-ftf)
Click here for this issue's archive.
Source: THALES (Mr. Emmanuel Fuchs, elfuchs(at)club-internet.fr)
Nature: Uncategorized Issue
Severity:
Summary: In order to support Short Term Conflict Alert the track informatioin need Plot Ages
Proposed solution : Addition of I030/290 - Plot Ages
Resolution: Addition of I030/290 - Plot Ages
Revised Text: Page number are document dtc/02-07-02, Final Adopted Specification Publication
Page 3.2 insert a new line in the data item table. I30/290 PLOT AGE
Page 3.6 insert
I30/290 : PLOT AGE
Definition : A set of plot related ages.
typedef float Duration;
typedef Duration SecondDuration;
struct PlotAge
{
SecondDuration modeA_age;
SecondDuration modeC_age;
};
in 3.2.1.11 I30 Track insert the field
PlotAge Plot_Age; // I030/290 Issue 4811
In 4, change IDL source
Actions taken:
January 22, 2002: received issue
February 14, 2003: closed issue
Issue 4812: Issue surveillance FTF: Last measured Mode C (surveillance-ftf)
Click here for this issue's archive.
Source: THALES (Mr. Emmanuel Fuchs, elfuchs(at)club-internet.fr)
Nature: Uncategorized Issue
Severity:
Summary: 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
Resolution: Addition of I030/140 - Last measured Mode C
Revised Text: Page 3.2 insert a new line in the data item table.
Page 3.6 insert
I30/140 : LAST MEASURED MODE C
Definition : Mode C code of the last nearest neighbour plot containing a Mode C and used to update the track.
typedef boolean Is_valid_Mode_C_code;
typedef boolean Is_garbled_information;
struct LastMesuredModeC
{
boolean Is_valid_Mode_C_code;
boolean Is_garbled_information;
Feet Mode_C
};
in 3.2.1.11 I30 Track insert the field
LastMesuredModeC last_mesured_mode_C; // I030/140 Issue 4812
In 4, change IDL source
Actions taken:
January 22, 2002: received issue
February 14, 2003: closed issue
Issue 4813: Surveillance FTF issue : used full floating point value for Plot ages. (surveillance-ftf)
Click here for this issue's archive.
Source: THALES (Mr. Emmanuel Fuchs, elfuchs(at)club-internet.fr)
Nature: Uncategorized Issue
Severity:
Summary: 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.
Resolution: Used full floating point value for Plot ages define in Issue 4811.
Revised Text: Confer issue 4811
Actions taken:
January 22, 2002: received issue
February 14, 2003: closed issue
Issue 4814: latitude and longitude for Calculated Track Position (surveillance-ftf)
Click here for this issue's archive.
Source: THALES (Mr. Emmanuel Fuchs, elfuchs(at)club-internet.fr)
Nature: Uncategorized Issue
Severity:
Summary: 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
Resolution: Use latitude and longitude for Calculated Track Position
Revised Text: Page 3.2 suppress I30/100 replace Cartesian by LatLong.
Page 3.4 suppress I3O/100
Page 3.4 insert
// LAT LONG COORDINATES
typedef SFloat Azimuths;
typedef Azimuths LatAzimuths;
typedef Azimuths LongAzimuths;
enum Hemisphere {
NORTH,
SOUTH
};
enum LatLongDirection {
EAST,
WEST
};
struct Latitude {
Hemisphere lat_hemis;
LatAzimuths lat_azim;
};
struct Longitude {
LatLongDirection long_dir;
LongAzimuths long_azim;
};
// 2D Position in a LAT/LONG coordinates system
struct LatLong2DPosition {
Latitude latit;
Longitude longit;
};
in 3.2.1.11 I30 Track suppress the field I3O/100 and insert
LatLong2DPosition latlong_position; // Issue 4814
In 4, change IDL source
Actions taken:
January 24, 2002: received issue
February 14, 2003: closed issue
Issue 4815: removal of the initial 10 pages (surveillance-ftf)
Click here for this issue's archive.
Source: THALES (Mr. Emmanuel Fuchs, elfuchs(at)club-internet.fr)
Nature: Uncategorized Issue
Severity:
Summary: 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,
Resolution: Clean up and removal of the initial 10 pages describing the specification
Revised Text: Suppress pages1.1 to 2.5.
Already done for the Final Adopted Specification Publication.
On page 3.1 suppress reference to initial 10 pages
Actions taken:
January 24, 2002: received issue
February 14, 2003: closed issue
Issue 5336: Suppress union and empty field (surveillance-ftf)
Click here for this issue's archive.
Source: THALES (Mr. Emmanuel Fuchs, elfuchs(at)club-internet.fr)
Nature: Uncategorized Issue
Severity:
Summary: 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.
Resolution: To suppress union and empty field
Revised Text:
Actions taken:
June 6, 2002: received issue
February 14, 2003: closed issue
Discussion: Already done for the Final Adopted Specification Publication
Issue 5337: suppress type range to broaden the scope of the interface (surveillance-ftf)
Click here for this issue's archive.
Source: THALES (Mr. Emmanuel Fuchs, elfuchs(at)club-internet.fr)
Nature: Uncategorized Issue
Severity:
Summary: 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.
Resolution: To use unconstrained IDL type.
Revised Text: Suppress type range in page 3.2, 3.3, 3.4, 3.5, 3.6
In 4, change IDL source
Actions taken:
June 6, 2002: received issue
February 14, 2003: closed issue
Issue 5676: I030/080 - ARTAS Track Status (surveillance-ftf)
Click here for this issue's archive.
Source: THALES (Mr. Emmanuel Fuchs, elfuchs(at)club-internet.fr)
Nature: Uncategorized Issue
Severity:
Summary: 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.
Resolution: Add IDL field in Track Status specifying how the altitude profile is coasting
Revised Text: On page 3.4 insert in TrackStatus :
boolean is_coasted_apart_from_lateral_trac;
In 4, change IDL source
Actions taken:
October 7, 2002: received issue
February 14, 2003: closed issue
Issue 5677: The local track number (I030/270) is missing (surveillance-ftf)
Click here for this issue's archive.
Source: THALES (Mr. Emmanuel Fuchs, elfuchs(at)club-internet.fr)
Nature: Uncategorized Issue
Severity:
Summary: Proposed solution : to add field I030/270 : local track number
Resolution: to add field I030/270: local track number
Revised Text: Page 3.2 insert a new line in the data item table I30/270 LOCAL TRACK
Page 3.6 insert
I30/270 : LOCAL TRACK
Definition : The local track number is a value representing a unique reference to a track record within the track data-base of a radar local tracker.
typedef unsigned long Natural;
typedef Natural LocalTrackNumber;
in 3.2.1.11 I30
insert in struct RadarTrack the field
LocalTrackNumber local_track_number; // I030/270 Issue 5677
I
In 4, change IDL source
Actions taken:
October 7, 2002: received issue
February 14, 2003: closed issue
Issue 5678: Missing track quality (I030/090) (surveillance-ftf)
Click here for this issue's archive.
Source: THALES (Mr. Emmanuel Fuchs, elfuchs(at)club-internet.fr)
Nature: Uncategorized Issue
Severity:
Summary: Proposed solution: to add field I030/090
Resolution: see above
Revised Text: Page 3.2 insert a new line in the data item table. I30/90 TRACK QUALITY
Page 3.6 insert
I30/90 TRACK QUALITY
Definition : track quality.
unsigned short track_quality;
In 4, change IDL source
Actions taken:
October 7, 2002: received issue
February 14, 2003: closed issue
Discussion: The field was missing in the summary table but was present in the track structure.
Add field I030/090 in the summary table.
Issue 5679: Missing radar-reported position (I030/360) (surveillance-ftf)
Click here for this issue's archive.
Source: THALES (Mr. Emmanuel Fuchs, elfuchs(at)club-internet.fr)
Nature: Uncategorized Issue
Severity:
Summary: Proposed solution: to add field I030/360
Resolution: The field reported position (I030/360) is missing
Revised Text: Page 3.2 insert a new line in the data item table. I30/360 MESURED POSITION
Page 3.6 insert
I30/360 MESURED POSITION
Definition : Mesured position of an aircraft
struct MesuredPositon
{
Miles Rho;
Azimuths Theata;
};
in 3.2.1.11 I30 Track insert the field
MesuredPosition Mesured_Position; // I030/360 Issue 5679
In 4, change IDL source
Actions taken:
October 7, 2002: received issue
February 14, 2003: closed issue
Issue 5680: Field I030/180 - Velocity (surveillance-ftf)
Click here for this issue's archive.
Source: THALES (Mr. Emmanuel Fuchs, elfuchs(at)club-internet.fr)
Nature: Uncategorized Issue
Severity:
Summary: 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.
Resolution: see above
Revised Text: On page 3.7 add
velocity-heading component is relative to True North
In 4, change IDL source
Actions taken:
October 7, 2002: received issue
February 14, 2003: closed issue
Discussion: Make precise in the specification that the velocity-heading component is relative to True North
Issue 5681: Add reference to the Transportation architecture White Paper (surveillance-ftf)
Click here for this issue's archive.
Source: THALES (Mr. Emmanuel Fuchs, elfuchs(at)club-internet.fr)
Nature: Uncategorized Issue
Severity:
Summary: 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
Resolution: Add reference to the Transportation architecture White Paper
Revised Text: Refer to the Transportation architecture White Paper to set the context for the scope of the submission
Revised Text:
On page 2.1 insert:
This document refers to the CORBA ATC architecture white paper. The context of this specification is relative to ATC components identified in the CORBA ATC architecture reference model.
This specification is a subset of the Surveillance Manager Interface, it represents the basic client interface. Enhanced client interfaces along with server side interfaces will be addressed in future specifications.
Actions taken:
October 7, 2002: received issue
February 14, 2003: closed issue