Documente Academic
Documente Profesional
Documente Cultură
FEASIBILITY STUDY
Feasibility Study
Safety Case
Version history
Author of
Version Date of Issue Reason for update
changes
00.16 23/01/2008 Version for PMO review SAF WG
00.17 25/01/2008 FAB CE document format CPMO
Update according to comments received +
00.18 15/02/2008 SAF WG
proposed issue
00.19 18/02/2008 Update according to comments received SAF WG
00.20 26/02/2008 Update according to OPS comments received SAF WG
00.90 26/02/2008 Proposed issue for FAB CE SG approval CPMO
00.92 07/03/2008 Tracked version before release CPMO
01.00 07/03/2008 Released issue CPMO
Distribution List
1 INTRODUCTION ..................................................................................................................... 6
1.1 PURPOSE AND SCOPE ........................................................................................................ 6
1.2 LIMITATION ........................................................................................................................ 6
1.3 LIST OF REFERENCES ......................................................................................................... 7
2 SAFETY ARGUMENT............................................................................................................. 8
2.1 BACKGROUND .................................................................................................................... 8
2.2 HIGH LEVEL SAFETY ARGUMENT......................................................................................... 8
2.3 TOP LEVEL CLAIM .............................................................................................................. 9
4 CONCLUSION....................................................................................................................... 16
Executive Summary
The FAB CE Feasibility Study Safety Case is the deliverable within WP 6.2.1 (DEL1) as
defined by the Safety Working Group (SAF WG) Work Breakdown Structure (WBS,
document number FAB-WBS-3-00-03).
Information contained in this document is intended to assist other FAB CE working groups
and also the developments of Master Plan and Cost benefit Analysis (CBA).
The FAB CE FS Safety Case reports on the performed safety assessment related activities
and appropriate conclusions. This document also proposes the high-level structure of safety
argument to be built during next stages of the FAB CE project.
Concerning the OPS concept, the dynamicity was considered as more demanding in terms of
time for the safety assessments being performed as well as for the mitigation means to be
applied in the FAB CE operations phase.
Fourteen hazard areas were identified as well as proposed mitigation measures. These
proposed mitigation measures (or their equivalents/alternatives) have to be applied during
the next stages of the FAB CE project.
Due to early stage of the project, the lists of hazard areas and proposed mitigation means
presented in this report are not to be considered as the final ones.
All the information contained in lists mentioned above is consolidated outcome of the
workshop with OPS and TEC experts and reflect the current stage of the FAB CE Feasibility
Study project and deliverables available at the moment of analyses conducted.
From the safety point of view, there have been no blocking factors identified concerning the
feasibility of FAB CE considering that:
1 Introduction
1.1 Purpose and Scope
The FAB CE Feasibility Study Safety Case is the deliverable within WP 6.2.1 (DEL1) as
defined by the Safety Working Group (SAF WG) Work Breakdown Structure [2].
Information contained in this document is intended to assist other FAB CE working groups
and also the developments of Master Plan and Cost benefit Analysis (CBA).
This document will support the FAB CE Feasibility Study project from the safety perspective
in compliance with SES Regulation (EC) No 551/2004 article 5.
Note:
In general, a Safety Case gives the evidence that, in the context of the operational
environment and the known limitations and shortcomings, the system (as defined in a known
build state) meets its Safety Requirements. However, as specified in Eurocontrol guidance
documentation (e.g. Safety Case training documentation and the SCDM [8]), it is necessary
to have a phased approach to the development of the Safety Case commensurate with the
major development milestones of the system, e.g.:
• Feasibility
• Project Definition
• Procurement
• Installation and Commissioning
• Transition
• Etc.
The production of the Safety Case could be supported by splitting the Safety case into a
number of parts or by successive iterations of the Safety Case.
The input for this document has been the draft document Safety Considerations [9] issued by
SAF WG.
The FAB CE Feasibility Study Safety Case provides the report on safety considerations,
based on FAB CE documents that have been available at the FAB CE “feasibility study”
project stage.
Note: SAF WG performed also an analysis on how the FAB CE introduction impacts the
safety management systems (SMSs) within the FAB CE area. This is documented in a
separate document (DEL 2: FAB CE Safety Management Roadmap [10]).
1.2 Limitation
This document is based on the other WGs representatives’ inputs during the 7th SAF-WG
session which includes the content of deliverables and papers. Additionally, experience and
expertise of participating ANSPs were used.
As all the deliverables in the feasibility study stage are of high level, this document can only
highlight hazards related to the FAB CE operations as defined today, and propose possible
related mitigation means. It raises questions that need to be answered in the implementation
phases of the project. For the decision makers, it provides just basic information about
safety-related issues that the FAB CE operations introduce.
2 Safety Argument
2.1 Background
SAF_WG agreed to use the Goal Structured Notation (GSN, defined by SCDM [8]) to present
high level safety argument. This technique links a top level claim about the safety of FAB CE
operations to a structured set of arguments and supporting evidence. The main arguments
follow the FAB CE lifecycle:
1. Concept
4. Operational Service
This technique will be used further within safety assessment activities during the next stages
of FAB CE project. It includes further development of the tree given in the chapter 2.2 High
Level Safety Argument.
The structures of Arg1, 2, 3 and 4 shall be provided in the later stages of the project based
on a SCDM guidance.
Safety considerations provided in this document cover partly the substructure of Arg1, as far
as possible at the FS stage.
Note: At the feasibility study stage, one of the means to fulfil the sub-argument Arg1 is the
implementation of all the mitigation measures proposed (or the implementation of equivalent
ones) in safety considerations.
Cr001 (Criteria)
Acceptably safe means:
a) Risk no greater (and preferably
lower) than current operations
A001 (Assumption)
Current operations are
acceptably safe
J001 (Justification)
FAB CE is a response to SES
regulations and to operational
A002: FAB CE Concept and business needs of 7 CE
Elements will be gradually ANSPs.
implemented as an evolution of
the current operations avoiding
radical changes of operational Arg0 (Argument)
paradigm.
Operating the FAB CE is
acceptably safe
It is based on the assumption the current ATM system has its own weaknesses and
strengths. FAB CE, when implemented, is expected to support the strengths and decrease
the effects of weaknesses. Additionally, FAB CE will introduce new issues, bringing both new
strengths and new weaknesses. All these have to be analysed.
“FAB CE as implemented shall maintain and where possible improve the current level of
safety in the FAB CE airspace”.
Using expert knowledge of the participating ANSPs, the issues related to the FAB CE
implementation were identified and filled in the summarised table.
The results of this analysis are documented in Appendix 2: Safety Issues Indicated.
The changes were identified based on the domains listed in the questionnaire used already
for initial safety issues analysis.
Only the changes that the FAB CE target scenarios implementation (the static and dynamic
scenarios) will induce were taken into consideration. There was no comparison to other
scenarios defined within the FAB CE Feasibility Study project.
The list of changes identified is documented in the Appendix 3: List of Changes identified.
3.5.1 General
At the Zagreb meeting (26-27 Nov 2007), the hazards related to the listed changes were
identified and feasible mitigation means were proposed.
In line with the changes identification (see section 3.4), hazards related to the FAB CE target
OPS scenarios (dynamic and static) were identified. In the process, the dynamicity was
considered as more demanding in terms of time for the safety assessments being performed
as well as for the mitigation means to be applied in the FAB CE operations phase. More
written procedures shall be necessary for preparation of the dynamic scenario.
Note: Hazard areas are used for the identification of unintended consequences of certain
presumed operational arrangements that are required for FAB.CE The causes were
considered and some foreseeable mitigation actions were proposed in order to highlight the
possible tasks for establishing and maintaining the safety of the FAB CE target scenarios.
Note: The hazards identified will NOT cover all the hazard areas to be considered in FAB CE
operation. Also hazards related to transition phases of FAB CE implementation are not
considered.
Note: The hazards which may occur in scenarios without FAB CE implementation are not
listed and shall be covered by the SMS of the individual ANSPs.
• People;
• Equipment
• Procedure (including airspace design).
Note: The grouping respects the approach considering that the ATM functional system has
its people, procedure and equipment elements.
MIT-H-PE-1-2
Regular use of all sector configuration
MIT-H-PE-1-3
Reduce number of configurations
MIT-H-PE-2-2
Noise reduction infrastructure
H-PE-3 HF fatigue (over/under load) MIT-H-PE-3-1
Optimise sector utilisation
Note: There will always be over/under
load sector in every configuraton
H-PE-4 Tactical staffing of the sectors MIT-H-PE-4-1
Proper rostering scheme
H-PE-5 LoA confusion of staff with complex MIT-H-PE-5-1
configuration Tools to handle procedures from LoAs
MIT-H-PE-5-2
Translation process from LoA → OPS
Proc create simple process
MIT-H-PE-5-3
Same DFL across the FAB CE area
H-PE- COM (language) problem: MIT-H-PE-6.0-1
6.1 Maintenance English as common language
H-PE- COM (language) problem: MIT-H-PE-6.0-1
6.2 OPS ↔ foreign TEC English as common language
H-PE- COM (language) problem: MIT-H-PE-6.0-1
6.3 MIL or VFR ↔ ATCO NATO/MIL standards
H-PE- COM (language) problem: MIT-H-PE-6.0-1
6.4 MIL/MIL communication, ATCO may NATO/MIL standards
not be aware
MIT-H-EQ-3-2
Common SMC
MIT-H-EQ-4-2
Shared environment
H-EQ-5 Different safety nets implementation MIT-H-EQ-5-1
Functionality and the behaviour
consistent
MIT-H-EQ-5-2
Define usage of safety NETS
H-EQ-6 Different technology influenced MIT-H-EQ-6-1
services Assess impact on other ANSPs
MIT-H-PR-2-2
Common training sessions
MIT-H-PR-2-3
English as common language
See Appendix 4: Hazards Identification and Proposed Mitigation for further details.
4 Conclusion
From the safety point of view, there have been no blocking factors identified
concerning the feasibility of FAB CE considering that:
Appendix 1: Questionnaire
Component Element Sub-element Description Work Well Area for Improvements Area of concerns
Component Element Sub-element Description Work Well Area for Improvements Area of concerns
Collapse/de-collapse functions
Own/Ext. Staff
Maintenance
Level of efficiency
IFR/VFR Mix
Schedule/Non schedule
Environment Traffic Main flows
Yearly traffic
Monthly distribution/seasonal peak
Delegation of airspace
Airspace
Adjacent TMAs
People Relationship with staff of adjacent units
Current Interfaces OLDI
Equipment COM data
Others
LoAs (with adjacent units)
Procedures
Working Methods/Practices
Airbases
TSAs
Military Areas CBAs
Airspace
Current Users Others
Requirements Coordination Procedures
Level of military activities
Flight testing
Other users
Others
Component Element Sub-element Description Work Well Area for Improvements Area of concerns
system Power supply
Other
Expected information:
Description as concise as possible, give figures and/or address only safety related aspects
Work Well Y or N
Area for Improvements list areas without explanation
Area of Concerns list areas without explanation
3 Airspace Collapse/De-collapse philosophy Sectorisation planning manual has to be in place, a tool can help for
decision making.
7 Roster Shifts changes should be taken into account within the FAB area
(communicated to adjacent centres, co-ordinated at FAB level).
Security issue.
Voice A/G
Monitoring of frequencies could be introduced (not just a quality
issue, also external influences).
11 Quality
RCOM architecture has to be analysed and optimised (quality and
coverage as well), and to be a subject of safety assessment.
COM External services.
12 Data
Interoperability issues (harmonisation, common standards for data
exchange protocols within the FAB).
See ID 12
Dynamic:
Current
Number Increased number of sectors controlled by a specific ACC, the
scenario
total number being the same
Component Element Sub-element Change Identification Hazard Consequence Mitigation Assumptions Safety Benefits Notes
Component Element Sub-element Change Identification Hazard Consequence Mitigation Assumptions Safety Benefits Notes
Implementation of new routing
structure should be assessed
against safety.
Component Element Sub-element Change Identification Hazard Consequence Mitigation Assumptions Safety Benefits Notes
Assessment of new
General hazard: technology implementation
ADS N/A use of different SURV and impact on other providers
Other SUR means technology by different ANSPs
Common ADS-B policy?
Component Element Sub-element Change Identification Hazard Consequence Mitigation Assumptions Safety Benefits Notes
Level of efficiency Coordination of maintenance
Inability to provide ATS fro Controllers might not fully
pilots speaking national understand VFR pilots'
Harmonization of airspace
Note: Language issue - national language; communication. According to WBS FAB covers Not common in current
IFR/VFR Mix classification in dynamic
languages used Airspace classification in Provision of ATS is not the whole controlled airspace. practice in ACCs
scenario.
dynamic scenario might according to airspace
probably not common. classification.
extended direct
Main flows
Main flow might be shifted to routing
Sufficient training for ATCOs.
Yearly traffic another sector.
Monthly distribution/seasonal peak
As a prerequisite: OLDI
Delegation of airspace
Airspace standard shall be applied
Adjacent TMAs
People Relationship with staff of adjacent units
Change of current partners
OLDI Final solution not decided.
Equipment COM data (potentially dynamic)
Others
Current Interfaces
LoAs (with adjacent units)
A lot of information:
distribution to different users,
Procedures various TMAs, ACCs, other
Ensuring relevant information Single source of data reduce
Working Methods/Practices users. Good management of
exchange the inconsistencies.
information requirement
(update, availability,
correctness, distribution...)
GENERAL NOTES
Change of interfaces, data
flows...
Airbases Harmonisation of handling with
OAT flights
Flight testing
Other users
Others
Component Element Sub-element Change Identification Hazard Consequence Mitigation Assumptions Safety Benefits Notes
system Power supply
Other