If you wish to contribute or participate in the discussions about articles you are invited to contact the Editor

EGNOS Performances: Difference between revisions

From Navipedia
Jump to navigation Jump to search
(First upload with images)
No edit summary
Line 7: Line 7:
|Logo=GMV
|Logo=GMV
}}
}}
EGNOS [[GNSS Performances|perfformances]] are issually described in terms of [[Accuracy|accuracy]], [[Integrity|integrity]], [[Availability|availability]] and [[Continuity|continuity]].


 
==EGNOS Performances Requirements==
==EGNOS Performances==
The performances required to EGNOS as per the EGNOS Mission Requirement Document<ref name="EGNOS MRD">EGNOS Mission Requirements Document, version 2.0, 8th May 2006, Galileo Joint Undertaking</ref> are presented in the following table.
The performances required to EGNOS as per the EGNOS Mission Requirement Document<ref name="EGNOS MRD">EGNOS Mission Requirements Document, version 2.0, 8th May 2006, Galileo Joint Undertaking</ref> are presented in the following table.


Line 61: Line 61:
| align="center" | 99%
| align="center" | 99%
|}
|}
<gallery>
Image:EGNOS_performances_ECAC_FIR96.png‎‎
Image:EGNOS_performances_ECAC_land_masses.png‎
</gallery>
==Monitoring of EGNOS Performances==
EGNOS performances are being monitored continuously by several entities, such as [http://egnos-user-support.essp-sas.eu/egnos_ops/ ESSP] and [http://www.egnos-pro.esa.int/IMAGEtech/imagetech_realtime.html ESA].


[[File:EGNOS_performances_ECAC_FIR96.png‎‎|300px|thumb|none]][[File:EGNOS_performances_ECAC_land_masses.png‎‎|300px||thumb|none]]


EGNOS performances are being monitored continuously by several entities, such as [http://egnos-user-support.essp-sas.eu/egnos_ops/ ESSP] and [http://www.egnos-pro.esa.int/IMAGEtech/imagetech_realtime.html ESA].
==Typical Performances==
Early 2011, the performances provided by EGNOS are presented in next figure – for day 7th Feb. 2011, considered to be a representative day. The actual EGNOS messages have been taken from the [ftp://ems.estec.esa.int/ EGNOS Message Server]. Plots are provided by the [http://eclayr.gmv.com/ eclayr tool].
Early 2011, the performances provided by EGNOS are presented in next figures – for day 7th Feb. 2011, considered to be a representative day. The actual EGNOS messages have been taken from the [ftp://ems.estec.esa.int/ EGNOS Message Server]. Plots are provided by the [http://eclayr.gmv.com/ eclayr tool].


==AVAILABILITY==
====Availability====
[[File:EGNOS_performances_availability.png‎‎|100px|EGNOS typical availability|left|thumb]]
[[File:EGNOS_performances_availability.png‎‎|100px|EGNOS typical availability|left|thumb]]
EGNOS availability map is provided in next figure together with the iso-lines of availability compliance to APV-I service level availability requirements (i.e., HPL < 40 m and VPL < 50 m). The period of analysis corresponds to one day with the inner iso-line delimiting the user locations where a service level over 99% availability is achieved.
EGNOS availability map is provided in next figure together with the iso-lines of availability compliance to APV-I service level availability requirements (i.e., HPL < 40 m and VPL < 50 m). The period of analysis corresponds to one day with the inner iso-line delimiting the user locations where a service level over 99% availability is achieved.


==CONTINUITY==
====Continuity====
[[File:EGNOS_performances_continuity.png‎‎|100px|EGNOS typical continuity|left|thumb]]
[[File:EGNOS_performances_continuity.png‎‎|100px|EGNOS typical continuity|left|thumb]]
EGNOS continuity map is provided in next figure together with the iso-lines of continuity risk compliance to APV-I service level. The continuity risk is computed as the probability of having a continuity event (Protection Levels > Alarm Limits) during the period [T0, T0 + 15 sec] provided that the service was available at T0 (Protection Levels < Alarm Limits). The inner iso-line – 1e-4 - delimits the user locations which did not have a single continuity event during the analyzed day.
EGNOS continuity map is provided in next figure together with the iso-lines of continuity risk compliance to APV-I service level. The continuity risk is computed as the probability of having a continuity event (Protection Levels > Alarm Limits) during the period [T0, T0 + 15 sec] provided that the service was available at T0 (Protection Levels < Alarm Limits). The inner iso-line – 1e-4 - delimits the user locations which did not have a single continuity event during the analyzed day.


==ACCURACY==
====Accuracy====
[[File:EGNOS_performances_accuracy.png‎‎|100px|EGNOS typical accuracy|left|thumb]]
[[File:EGNOS_performances_accuracy.png‎‎|100px|EGNOS typical accuracy|left|thumb]]
EGNOS vertical accuracy map is provided in next figure together with the iso-lines of 95% Vertical Position Error – meters -. Users inside the inner iso-line had a vertical accuracy below 2 m (95%) for the analyzed day.
EGNOS vertical accuracy map is provided in next figure together with the iso-lines of 95% Vertical Position Error – meters -. Users inside the inner iso-line had a vertical accuracy below 2 m (95%) for the analyzed day.


==INTEGRITY==
====Integrity====
[[File:EGNOS_performances_integrity.png‎‎|100px|EGNOS typical integrity|left|thumb]]
[[File:EGNOS_performances_integrity.png‎‎|100px|EGNOS typical integrity|left|thumb]]
EGNOS vertical integrity margins are provided in next figure as maximum Vertical Safety index map (maximum ratio between the vertical user error and the vertical user protection level). All values are under one meaning that no integrity failures at user level were been observed.
EGNOS vertical integrity margins are provided in next figure as maximum Vertical Safety index map (maximum ratio between the vertical user error and the vertical user protection level). All values are under one meaning that no integrity failures at user level were been observed.

Revision as of 17:17, 30 March 2011


EGNOSEGNOS
Title EGNOS Performances
Author(s) GMV.
Level Basic
Year of Publication 2011
Logo GMV.png

EGNOS perfformances are issually described in terms of accuracy, integrity, availability and continuity.

EGNOS Performances Requirements

The performances required to EGNOS as per the EGNOS Mission Requirement Document[1] are presented in the following table.

Service Service Coverage Accuracy (95%) Integrity Continuity Availability
Lateral Vertical HAL VAL TTA Integrity Risk
Open Service EU25 States (plus Norway and Switzerland) land masses 3m 4m - - - - - 99%
SoL En-route and NPA FIRs of ECAC 96 220m - 556m - 10s 1e-7/hour 1e-5/hour 99.9%
SoL APV-I Land Masses of ECAC 96 16m 20m 40m 50m 6s 2e-7/150s 8e-6/15s 99%

Monitoring of EGNOS Performances

EGNOS performances are being monitored continuously by several entities, such as ESSP and ESA.


Typical Performances

Early 2011, the performances provided by EGNOS are presented in next figures – for day 7th Feb. 2011, considered to be a representative day. The actual EGNOS messages have been taken from the EGNOS Message Server. Plots are provided by the eclayr tool.

Availability

EGNOS typical availability

EGNOS availability map is provided in next figure together with the iso-lines of availability compliance to APV-I service level availability requirements (i.e., HPL < 40 m and VPL < 50 m). The period of analysis corresponds to one day with the inner iso-line delimiting the user locations where a service level over 99% availability is achieved.

Continuity

EGNOS typical continuity

EGNOS continuity map is provided in next figure together with the iso-lines of continuity risk compliance to APV-I service level. The continuity risk is computed as the probability of having a continuity event (Protection Levels > Alarm Limits) during the period [T0, T0 + 15 sec] provided that the service was available at T0 (Protection Levels < Alarm Limits). The inner iso-line – 1e-4 - delimits the user locations which did not have a single continuity event during the analyzed day.

Accuracy

EGNOS typical accuracy

EGNOS vertical accuracy map is provided in next figure together with the iso-lines of 95% Vertical Position Error – meters -. Users inside the inner iso-line had a vertical accuracy below 2 m (95%) for the analyzed day.

Integrity

EGNOS typical integrity

EGNOS vertical integrity margins are provided in next figure as maximum Vertical Safety index map (maximum ratio between the vertical user error and the vertical user protection level). All values are under one meaning that no integrity failures at user level were been observed.

Notes

References

  1. ^ EGNOS Mission Requirements Document, version 2.0, 8th May 2006, Galileo Joint Undertaking