ARAIM - Revision history

Gema.Cueto: /* ARAIM Recommendations */

2021-05-21T11:35:22Z

ARAIM Recommendations

← Older revision		Revision as of 11:35, 21 May 2021
Line 54:		Line 54:

	==ARAIM Recommendations==		==ARAIM Recommendations==
	As implemented currently in ~~aircrafts~~, Receiver Autonomous Integrity Monitoring (RAIM) only supports lateral navigation. In order to cover vertical guidance, Advanced RAIM (ARAIM) techniques were recommended to include<ref name="GEAS_II"></ref>:		As implemented currently in aircraft, Receiver Autonomous Integrity Monitoring (RAIM) only supports lateral navigation. In order to cover vertical guidance, Advanced RAIM (ARAIM) techniques were recommended to include<ref name="GEAS_II"></ref>:
	*Frequency diversity (e.g. using dual frequency measurements on L1/L5 for GPS),		*Frequency diversity (e.g. using dual frequency measurements on L1/L5 for GPS),
	*Geometry diversity (e.g. using as many GNSS constellation as possible in order to reach the required levels of satellite availability),		*Geometry diversity (e.g. using as many GNSS constellation as possible in order to reach the required levels of satellite availability),

Filipe.Pelica: Included editor logo.

2014-09-18T17:10:58Z

Included editor logo.

← Older revision		Revision as of 17:10, 18 September 2014
Line 4:		Line 4:
	\|Level=Basic		\|Level=Basic
	\|YearOfPublication=2011		\|YearOfPublication=2011
			\|Logo=GMV
	\|Title={{PAGENAME}}		\|Title={{PAGENAME}}
	}}		}}

Carlos.Lopez at 11:18, 23 February 2012

2012-02-23T11:18:10Z

← Older revision		Revision as of 11:18, 23 February 2012
Line 1:		Line 1:
	{{Article Infobox2		{{Article Infobox2
	\|Category=Fundamentals		\|Category=Fundamentals
	\|~~Authors~~=GMV		\|Editors=GMV
	\|Level=Basic		\|Level=Basic
	\|YearOfPublication=2011		\|YearOfPublication=2011
	~~\|Logo=GMV~~
	\|Title={{PAGENAME}}		\|Title={{PAGENAME}}
	}}		}}

Rui.Pereira at 17:51, 8 November 2011

2011-11-08T17:51:38Z

← Older revision		Revision as of 17:51, 8 November 2011
Line 1:		Line 1:
	{{Article Infobox2		{{Article Infobox2
	\|Category=Fundamentals		\|Category=Fundamentals
	~~\|Title={{PAGENAME}}~~
	\|Authors=GMV		\|Authors=GMV
	\|Level=Basic		\|Level=Basic
	\|YearOfPublication=2011		\|YearOfPublication=2011
	\|Logo=GMV		\|Logo=GMV
			\|Title={{PAGENAME}}
	}}		}}

	As traditional RAIM techniques continue evolving to cope with different requirements and tailored to different applications, the GNSS Evolutionary Architecture Study (GEAS) panel has proposed an Advanced RAIM technique able to guarantee LPV-200 operation worldwide, up to 2030 timeframe (i.e. excluding GPS III effort).		As traditional RAIM techniques continue evolving to cope with different requirements and tailored to different applications, the GNSS Evolutionary Architecture Study (GEAS) panel has proposed an Advanced RAIM technique able to guarantee LPV-200 operation worldwide, up to 2030 timeframe (i.e. excluding GPS III effort).

Line 100:		Line 99:
	==Related articles==		==Related articles==
	*[[Integrity]]		*[[Integrity]]
	*[[~~Work in Progress:~~RAIM\|RAIM]]		*[[RAIM\|RAIM]]
	*[[~~Work in Progress:~~RAIM Fundamentals\|RAIM Fundamentals]]		*[[RAIM Fundamentals\|RAIM Fundamentals]]
	*[[~~Work in Progress:~~RAIM Algorithms\|RAIM Algorithms]]		*[[RAIM Algorithms\|RAIM Algorithms]]

Rui.Pereira: moved Work in Progress:ARAIM to ARAIM

2011-07-29T22:23:20Z

moved Work in Progress:ARAIM to ARAIM

← Older revision	Revision as of 22:23, 29 July 2011
(No difference)

Teresa.Ferreira: /* ARAIM Rationale */

2011-07-23T14:11:23Z

ARAIM Rationale

← Older revision		Revision as of 14:11, 23 July 2011
Line 65:		Line 65:
	==ARAIM Rationale==		==ARAIM Rationale==
	The main reasons for which conventional RAIM techniques are considered not adequate for LPV-200 operations are:		The main reasons for which conventional RAIM techniques are considered not adequate for LPV-200 operations are:
	*Design assurance level required (severe-major/hazardous for LPV-200 and only major for LNAV)		*Design assurance level required (severe-major/hazardous for LPV-200 and only major for LNAV),
	*Alert limits for LPV-200 are smaller when compared to LNAV’s		*Alert limits for LPV-200 are smaller when compared to LNAV’s,
	*Multiple faults should now be considered for LPV-200		*Multiple faults should now be considered for LPV-200,
	*LPV-200 operations have more stringent accuracy requirements		*LPV-200 operations have more stringent accuracy requirements.

	For these reasons, GEAS proposed a modified RAIM algorithm called Advanced RAIM – ARAIM which is based on the following assumptions:		For these reasons, GEAS proposed a modified RAIM algorithm called Advanced RAIM – ARAIM which is based on the following assumptions:
	*Satellite ranging error characteristics: instead of being assumed as zero mean Gaussian (conventional RAIM), now the biases are also considered, contributing as a sum of biased Gaussian distributed quantities.		*Satellite ranging error characteristics: instead of being assumed as zero mean Gaussian (conventional RAIM), now the biases are also considered, contributing as a sum of biased Gaussian distributed quantities.
	*Satellite Integrity Failure Models: the integrity failure rate is assumed to be 10<sup>-5</sup>/hour/satellite (instead of 10<sup>-4</sup>/hour/satellite) and that the GPS Control Segment informs the user within one hour of the fault onset. It is further assumed that the rate of faults causing multiple simultaneous satellite integrity failures is 1.3x10<sup>-8</sup>/approach.		*Satellite Integrity Failure Models: the integrity failure rate is assumed to be 10<sup>-5</sup>/hour/satellite (instead of 10<sup>-4</sup>/hour/satellite) and that the GPS Control Segment informs the user within one hour of the fault onset. It is further assumed that the rate of faults causing multiple simultaneous satellite integrity failures is 1.3x10<sup>-8</sup>/approach.
	*<math>P_{HMI}</math> requirement is now allocated to three cases: fault-free, single fault and multiple faults (in conventional RAIM, it was allocated equally among the first two cases)		*<math>P_{HMI}</math> requirement is now allocated to three cases: fault-free, single fault and multiple faults (in conventional RAIM, it was allocated equally among the first two cases).


	==ARAIM Concept==		==ARAIM Concept==

Teresa.Ferreira: /* ARAIM Recommendations */

2011-07-23T14:10:49Z

ARAIM Recommendations

← Older revision		Revision as of 14:10, 23 July 2011
Line 56:		Line 56:
	==ARAIM Recommendations==		==ARAIM Recommendations==
	As implemented currently in aircrafts, Receiver Autonomous Integrity Monitoring (RAIM) only supports lateral navigation. In order to cover vertical guidance, Advanced RAIM (ARAIM) techniques were recommended to include<ref name="GEAS_II"></ref>:		As implemented currently in aircrafts, Receiver Autonomous Integrity Monitoring (RAIM) only supports lateral navigation. In order to cover vertical guidance, Advanced RAIM (ARAIM) techniques were recommended to include<ref name="GEAS_II"></ref>:
	*Frequency diversity (e.g. using dual frequency measurements on L1/L5 for GPS)		*Frequency diversity (e.g. using dual frequency measurements on L1/L5 for GPS),
	*Geometry diversity (e.g. using as many GNSS constellation as possible in order to reach the required levels of satellite availability)		*Geometry diversity (e.g. using as many GNSS constellation as possible in order to reach the required levels of satellite availability),
	*Use of an Integrity Support Message (ISM) that would convey safety assertions associated with each of the core GNSS to the sovereign responsible for a given airspace		*Use of an Integrity Support Message (ISM) that would convey safety assertions associated with each of the core GNSS to the sovereign responsible for a given airspace,
	*less likely threats to GNSS such as faults in the Earth Orientation Parameters (EOP) or any fault related to the generation of the ISM		*less likely threats to GNSS such as faults in the Earth Orientation Parameters (EOP) or any fault related to the generation of the ISM.

	The GEAS report <ref name="GEAS_II"></ref>stated that worldwide vertical guidance based on ARAIM is feasible using a joint constellation of 24 Galileo satellites and 21 GPS satellites. This finding provides relief from a major concern for aviation (since only 21 operational GPS satellites were guaranteed by the DoD and that Galileo might run into some budgetary constraints).		The GEAS report <ref name="GEAS_II"></ref>stated that worldwide vertical guidance based on ARAIM is feasible using a joint constellation of 24 Galileo satellites and 21 GPS satellites. This finding provides relief from a major concern for aviation (since only 21 operational GPS satellites were guaranteed by the DoD and that Galileo might run into some budgetary constraints).

Teresa.Ferreira at 14:09, 23 July 2011

2011-07-23T14:09:53Z

Rui.Pereira at 17:02, 30 June 2011

2011-06-30T17:02:54Z

Rui.Pereira at 17:01, 30 June 2011

2011-06-30T17:01:16Z

← Older revision		Revision as of 17:01, 30 June 2011
Line 16:		Line 16:
	In its report of 2010<ref name="GEAS_II"> Phase II of the GNSS Evolutionary Architecture Study, February 2010 </ref>, the GNSS Evolutionary Architecture Study (GEAS) panel recommends a path to achieve worldwide LPV-200 capability for air navigation.		In its report of 2010<ref name="GEAS_II"> Phase II of the GNSS Evolutionary Architecture Study, February 2010 </ref>, the GNSS Evolutionary Architecture Study (GEAS) panel recommends a path to achieve worldwide LPV-200 capability for air navigation.
	For that purpose, the following challenges are identified:		For that purpose, the following challenges are identified:
	*Faults: usually reflected as satellite clocks run-off or upload of faulty navigation data (observed about 3 times/ year for GPS)		*Faults: usually reflected as satellite clocks run-off or upload of faulty navigation data (observed about 3 times/year for GPS)
	*Rare normal conditions: general space weather conditions (e.g. ionospheric anomalies) that introduce Hazardous Misleading Information (HMI)		*Rare normal conditions: general space weather conditions (e.g. ionospheric anomalies) that introduce Hazardous Misleading Information (HMI)
	*Constellation weakness: too few satellites are well positioned for navigation purposes		*Constellation weakness: too few satellites are well positioned for navigation purposes
Line 24:		Line 24:
	The following Table identifies the challenges tackled by the different single frequency technologies.		The following Table identifies the challenges tackled by the different single frequency technologies.

			{\| class="wikitable"
			\|+Vulnerability Matrix
	{\| ~~border="1" align="center" cellpadding="5" style~~="~~text-align: center; font-size: 11px;~~"
	\|+~~align="bottom" style="font-size:12px;"\|~~Vulnerability Matrix.
	\|-		\|-
	! Constellation/ challenge \|\|Fault\|\|Rare Normal\|\|Constellation Weakness\|\|RFI		!Constellation/challenge
			!Fault
			!Rare Normal
			!Constellation Weakness
			!RFI
	\|-		\|-
	~~\| '''~~RAIM \|\| detect \|\| detect \|\| most vulnerable (>27 sat)\|\| vulnerable		!RAIM
			\|align="center"\|detect
			\|align="center"\|detect
			\|align="center"\|most vulnerable (>27 sat)
			\|align="center"\|vulnerable
	\|-		\|-
	~~\| '''~~GBAS~~'''~~ \|\| detect \|\| detect \|\| vulnerable (> 23 sat)\|\| vulnerable		!GBAS
			\|align="center"\|detect
			\|align="center"\|detect
			\|align="center"\|vulnerable (> 23 sat)
			\|align="center"\|vulnerable
	\|-		\|-
	~~\| '''~~SBAS~~'''~~ \|\| detect \|\| detect \|\| vulnerable (> 23 sat)\|\| vulnerable		!SBAS
			\|align="center"\|detect
			\|align="center"\|detect
			\|align="center"\|vulnerable (> 23 sat)
			\|align="center"\|vulnerable
	\|}		\|}

Line 45:		Line 59:
	==ARAIM Recommendations==		==ARAIM Recommendations==
	As implemented currently in aircrafts, Receiver Autonomous Integrity Monitoring (RAIM) only supports lateral navigation. In order to cover vertical guidance, Advanced RAIM (ARAIM) techniques were recommended to include<ref name="GEAS_II"></ref>:		As implemented currently in aircrafts, Receiver Autonomous Integrity Monitoring (RAIM) only supports lateral navigation. In order to cover vertical guidance, Advanced RAIM (ARAIM) techniques were recommended to include<ref name="GEAS_II"></ref>:
	*Frequency diversity (e.g. using dual frequency measurements on L1/ L5 for GPS)		*Frequency diversity (e.g. using dual frequency measurements on L1/L5 for GPS)
	*Geometry diversity (e.g. using as many GNSS constellation as possible in order to reach the required levels of satellite availability)		*Geometry diversity (e.g. using as many GNSS constellation as possible in order to reach the required levels of satellite availability)
	*Use of an Integrity Support Message (ISM) that would convey safety assertions associated with each of the core GNSS to the sovereign responsible for a given airspace		*Use of an Integrity Support Message (ISM) that would convey safety assertions associated with each of the core GNSS to the sovereign responsible for a given airspace
Line 63:		Line 77:
	For these reasons, GEAS proposed a modified RAIM algorithm called Advanced RAIM – ARAIM which is based on the following assumptions:		For these reasons, GEAS proposed a modified RAIM algorithm called Advanced RAIM – ARAIM which is based on the following assumptions:
	*Satellite ranging error characteristics: instead of being assumed as zero mean Gaussian (conventional RAIM), now the biases are also considered, contributing as a sum of biased Gaussian distributed quantities.		*Satellite ranging error characteristics: instead of being assumed as zero mean Gaussian (conventional RAIM), now the biases are also considered, contributing as a sum of biased Gaussian distributed quantities.
	*Satellite Integrity Failure Models: the integrity failure rate is assumed to be 10-5/ hour/ satellite (instead of 10-4/ hour/ satellite) and that the GPS Control Segment informs the user within one hour of the fault onset. It is further assumed that the rate of faults causing multiple simultaneous satellite integrity failures is 1.3x10-8/ approach.		*Satellite Integrity Failure Models: the integrity failure rate is assumed to be 10<sup>-5</sup>/hour/satellite (instead of 10<sup>-4</sup>/hour/satellite) and that the GPS Control Segment informs the user within one hour of the fault onset. It is further assumed that the rate of faults causing multiple simultaneous satellite integrity failures is 1.3x10<sup>-8</sup>/approach.
	*<math>P_{HMI}</math> requirement is now allocated to three cases: fault-free, single fault and multiple faults (in conventional RAIM, it was allocated equally among the first two cases)		*<math>P_{HMI}</math> requirement is now allocated to three cases: fault-free, single fault and multiple faults (in conventional RAIM, it was allocated equally among the first two cases)

Line 77:		Line 91:


	Furthermore, it is recommended that the approving authority provides additional information on the overbounding distributions (both for nominal conditions and expected un-faulted ~~behaviour~~):		Furthermore, it is recommended that the approving authority provides additional information on the overbounding distributions (both for nominal conditions and expected un-faulted behavior):
	*URA term describing the overbounding portion of the distribution that can be root sum squared with the other error overbounding distributions		*URA term describing the overbounding portion of the distribution that can be root sum squared with the other error overbounding distributions
	*URA term to contribute to the overbounding bias value		*URA term to contribute to the overbounding bias value
Line 94:		Line 108:
	==Related articles==		==Related articles==
	*[[Integrity]]		*[[Integrity]]
	*[[RAIM]]		*[[Work in Progress:RAIM\|RAIM]]
	*[[RAIM Fundamentals]]		*[[Work in Progress:RAIM Fundamentals\|RAIM Fundamentals]]
	*[[RAIM Algorithms]]		*[[Work in Progress:RAIM Algorithms\|RAIM Algorithms]]

← Older revision		Revision as of 14:09, 23 July 2011
Line 14:		Line 14:
	In its report of 2010<ref name="GEAS_II"> Phase II of the GNSS Evolutionary Architecture Study, February 2010 </ref>, the GNSS Evolutionary Architecture Study (GEAS) panel recommends a path to achieve worldwide LPV-200 capability for air navigation.		In its report of 2010<ref name="GEAS_II"> Phase II of the GNSS Evolutionary Architecture Study, February 2010 </ref>, the GNSS Evolutionary Architecture Study (GEAS) panel recommends a path to achieve worldwide LPV-200 capability for air navigation.
	For that purpose, the following challenges are identified:		For that purpose, the following challenges are identified:
	*Faults: usually reflected as satellite clocks run-off or upload of faulty navigation data (observed about 3 times/year for GPS)		*Faults: usually reflected as satellite clocks run-off or upload of faulty navigation data (observed about 3 times/year for GPS),
	*Rare normal conditions: general space weather conditions (e.g. ionospheric anomalies) that introduce Hazardous Misleading Information (HMI)		*Rare normal conditions: general space weather conditions (e.g. ionospheric anomalies) that introduce Hazardous Misleading Information (HMI),
	*Constellation weakness: too few satellites are well positioned for navigation purposes		*Constellation weakness: too few satellites are well positioned for navigation purposes,
	*Radio Frequency Interference (RFI): intentional or not, may lead to GNSS blockage		*Radio Frequency Interference (RFI): intentional or not, may lead to GNSS blockage.

	The following Table identifies the challenges tackled by the different single frequency technologies.		The following Table identifies the challenges tackled by the different single frequency technologies.
Line 50:		Line 50:

	Improving these systems to dual frequency would:		Improving these systems to dual frequency would:
	*Tackle rare normal conditions		*Tackle rare normal conditions,
	*Tackle most of unintentional RFI (~~intentional RFI is easily upgraded~~)~~, since DMEs are less felt at low altitudes~~		*Tackle most of unintentional RFI, such as those caused by DME (Distance Measuring Equipment).


Line 80:		Line 80:

	The computation of Protection Levels (PL) for ARAIM considers the following contributions:		The computation of Protection Levels (PL) for ARAIM considers the following contributions:
	*Contributions of the pseudo-range residuals scaled to the position domain, weighed by a K factor that contains the Probability of Hazardous Misleading Information - P(HMI)		*Contributions of the pseudo-range residuals scaled to the position domain, weighed by a K factor that contains the Probability of Hazardous Misleading Information - P(HMI),
	*Contributions of the bias terms		*Contributions of the bias terms,
	*Contribution from the nominal conditions defined by the continuity/ accuracy requirements		*Contribution from the nominal conditions defined by the continuity/ accuracy requirements.

	Furthermore, it is recommended that the approving authority provides additional information on the overbounding distributions (both for nominal conditions and expected un-faulted behavior):		Furthermore, it is recommended that the approving authority provides additional information on the overbounding distributions (both for nominal conditions and expected un-faulted behavior):
	*URA term describing the overbounding portion of the distribution that can be root sum squared with the other error overbounding distributions		*URA (User Range Accuracy) term describing the overbounding portion of the distribution that can be root sum squared with the other error overbounding distributions,
	*URA term to contribute to the overbounding bias value		*URA term to contribute to the overbounding bias value,
	*Constant value independent of URA		*Constant value independent of URA.

	Finally, ARAIM is considered available if:		Finally, ARAIM is considered available if:
Line 93:		Line 93:

	where:		where:
	*<math>VPL=max[VPL_0,max(VPL_n )] <= VAL</math>		*<math>VPL=max[VPL_0,max(VPL_n )] <= VAL</math>,
	*VPL is the Vertical Protection Level		*VPL is the Vertical Protection Level,
	*VAL is the Vertical Alert Limit		*VAL is the Vertical Alert Limit,
	*n represents the VPL computed by excluding the <math>n^{th}</math> measurement		*n represents the VPL computed by excluding the <math>n^{th}</math> measurement.

← Older revision		Revision as of 17:02, 30 June 2011
Line 7:		Line 7:
	\|Logo=GMV		\|Logo=GMV
	}}		}}



	As traditional RAIM techniques continue evolving to cope with different requirements and tailored to different applications, the GNSS Evolutionary Architecture Study (GEAS) panel has proposed an Advanced RAIM technique able to guarantee LPV-200 operation worldwide, up to 2030 timeframe (i.e. excluding GPS III effort).		As traditional RAIM techniques continue evolving to cope with different requirements and tailored to different applications, the GNSS Evolutionary Architecture Study (GEAS) panel has proposed an Advanced RAIM technique able to guarantee LPV-200 operation worldwide, up to 2030 timeframe (i.e. excluding GPS III effort).
Line 20:		Line 18:
	*Constellation weakness: too few satellites are well positioned for navigation purposes		*Constellation weakness: too few satellites are well positioned for navigation purposes
	*Radio Frequency Interference (RFI): intentional or not, may lead to GNSS blockage		*Radio Frequency Interference (RFI): intentional or not, may lead to GNSS blockage


	The following Table identifies the challenges tackled by the different single frequency technologies.		The following Table identifies the challenges tackled by the different single frequency technologies.
Line 63:		Line 60:
	*Use of an Integrity Support Message (ISM) that would convey safety assertions associated with each of the core GNSS to the sovereign responsible for a given airspace		*Use of an Integrity Support Message (ISM) that would convey safety assertions associated with each of the core GNSS to the sovereign responsible for a given airspace
	*less likely threats to GNSS such as faults in the Earth Orientation Parameters (EOP) or any fault related to the generation of the ISM		*less likely threats to GNSS such as faults in the Earth Orientation Parameters (EOP) or any fault related to the generation of the ISM


	The GEAS report <ref name="GEAS_II"></ref>stated that worldwide vertical guidance based on ARAIM is feasible using a joint constellation of 24 Galileo satellites and 21 GPS satellites. This finding provides relief from a major concern for aviation (since only 21 operational GPS satellites were guaranteed by the DoD and that Galileo might run into some budgetary constraints).		The GEAS report <ref name="GEAS_II"></ref>stated that worldwide vertical guidance based on ARAIM is feasible using a joint constellation of 24 Galileo satellites and 21 GPS satellites. This finding provides relief from a major concern for aviation (since only 21 operational GPS satellites were guaranteed by the DoD and that Galileo might run into some budgetary constraints).
Line 73:		Line 69:
	*Multiple faults should now be considered for LPV-200		*Multiple faults should now be considered for LPV-200
	*LPV-200 operations have more stringent accuracy requirements		*LPV-200 operations have more stringent accuracy requirements


	For these reasons, GEAS proposed a modified RAIM algorithm called Advanced RAIM – ARAIM which is based on the following assumptions:		For these reasons, GEAS proposed a modified RAIM algorithm called Advanced RAIM – ARAIM which is based on the following assumptions:
Line 83:		Line 78:
	==ARAIM Concept==		==ARAIM Concept==
	The Advanced RAIM (ARAIM) technique is based on the Solution Separation Method<ref>Blanch, J., Ene, A., Walter, T., Enge, P. “An Optimized Multiple Solution Separation RAIM Algorithm for Vertical Guidance”. Proceedings of the ION GNSS 2007, Fort Worth, TX, September 2007.</ref><ref>Lee2, Y.C. and McLaughlin, M. P., “Feasibility Analysis of RAIM to Provide LPV 200 Approaches with Future GPS,” in Proceedings of ION GNSS-2007, Fort Worth, TX, September 2007</ref>.		The Advanced RAIM (ARAIM) technique is based on the Solution Separation Method<ref>Blanch, J., Ene, A., Walter, T., Enge, P. “An Optimized Multiple Solution Separation RAIM Algorithm for Vertical Guidance”. Proceedings of the ION GNSS 2007, Fort Worth, TX, September 2007.</ref><ref>Lee2, Y.C. and McLaughlin, M. P., “Feasibility Analysis of RAIM to Provide LPV 200 Approaches with Future GPS,” in Proceedings of ION GNSS-2007, Fort Worth, TX, September 2007</ref>.


	The computation of Protection Levels (PL) for ARAIM considers the following contributions:		The computation of Protection Levels (PL) for ARAIM considers the following contributions:
Line 89:		Line 83:
	*Contributions of the bias terms		*Contributions of the bias terms
	*Contribution from the nominal conditions defined by the continuity/ accuracy requirements		*Contribution from the nominal conditions defined by the continuity/ accuracy requirements


	Furthermore, it is recommended that the approving authority provides additional information on the overbounding distributions (both for nominal conditions and expected un-faulted behavior):		Furthermore, it is recommended that the approving authority provides additional information on the overbounding distributions (both for nominal conditions and expected un-faulted behavior):
Line 95:		Line 88:
	*URA term to contribute to the overbounding bias value		*URA term to contribute to the overbounding bias value
	*Constant value independent of URA		*Constant value independent of URA


	Finally, ARAIM is considered available if:		Finally, ARAIM is considered available if:
Line 105:		Line 97:
	*VAL is the Vertical Alert Limit		*VAL is the Vertical Alert Limit
	*n represents the VPL computed by excluding the <math>n^{th}</math> measurement		*n represents the VPL computed by excluding the <math>n^{th}</math> measurement


	==Related articles==		==Related articles==