[SystemSafety] COTS display certification

Tom Ferrell tom at faaconsulting.com
Fri Jul 29 14:55:36 CEST 2016


I would note that the issue of safety associated with aeronautical data including information produced by or consumed by air traffic control systems on the ground and flight management/terrain avoidance applications onboard aircraft is addressed in a couple of different RTCA publications.  Of particular relevance to this discussion is DO-200B, Standards for Aeronautical Data.  It is primarily a process document.  The document is built around a couple of key concepts:

1.	Data Quality Characteristics - these include: accuracy, resolution, assurance level, traceability, timeliness, completeness, and format
2.	Data chain elements - these include: origination, transmission, preparation, application integration, and end-use

The document also discusses a general data processing model which further refines the data preparation, transmission, and application integration phases and includes guidance on how data gets received, assembled for use, translated (e.g., normalization, coordinate conversion), selected, formatted, and subsequently distributed for the next step in the data chain.

Data is divided into three assurance levels with more controls and verification steps expected as you move up in level.  These levels are designated critical, essential, and routine.  A mapping between these levels and the corresponding computing infrastructure created for airborne systems using DO-178C or for ground systems created using DO-278A is also provided.



-----Original Message-----
From: systemsafety [mailto:systemsafety-bounces at lists.techfak.uni-bielefeld.de] On Behalf Of Martyn Thomas
Sent: Friday, July 29, 2016 7:16 AM
To: systemsafety at lists.techfak.uni-bielefeld.de
Subject: Re: [SystemSafety] COTS display certification

It also has a great Appendix describing accidents that had erroneous data as one causal factor. I recommend reading it.

Martyn

On 29/07/2016 12:12, paul_e.bennett at topmail.co.uk wrote:
> On 29/07/2016 at 11:44 AM, "Peter Bernard Ladkin" <ladkin at rvs.uni-bielefeld.de> wrote:
>>
>> So what's right and wrong with the Data Safety document? 
>> http://scsc.org.uk/p130 There has been zero discussion of it here.
>>
> That document is thought provoking and, while it may not be a perfect 
> guide, it does get one thinking about data and its integrity while you 
> are designing your overall system architecture then on down into the 
> nitty-gritty detail. It may be a worthwhile beginning to having a 
> standard on Data Integrity that can be merged into the Safety and 
> Security Standards
>
> Regards
>
> Paul E. Bennett IEng MIET
> Systems Engineer
>

_______________________________________________
The System Safety Mailing List
systemsafety at TechFak.Uni-Bielefeld.DE


More information about the systemsafety mailing list