FASTI PROGRAMME PROGRAMME MANAGEMENT PLAN

Size: px
Start display at page:

Download "FASTI PROGRAMME PROGRAMME MANAGEMENT PLAN"

Transcription

1 EUROCONTROL FASTI PROGRAMME PROGRAMME MANAGEMENT PLAN Reference: FAS-A-AA-1000-PMP Status: Final Version Edition No: 1.0 Date: Manager(s) Christopher Brain Visa : Sponsor and Head SPR BD Robert Stewart Visa: Support Terry Schroeyens BPS Endorsement:

2

3 DOCUMENT CONTROL Copyright notice 2002 European Organisation for the Safety of Air Navigation (EUROCONTROL). All rights reserved. Member States of the Organisation are entitled to use and reproduce this document for internal and non-commercial purpose under their vested tasks. Any disclosure to third parties shall be subject to prior written permission of EUROCONTROL. Edition history Edition Nº Date and Status Draft C Brain Author(s) Reason First Draft based on EPMP C Brain Head SPR Review C Brain Head SPR Final Review Acknowledgements Name Location Filename and Path P:\EATM\DAP\BD_SPR\FASTI\PM Documents\PMP\FAS-1000-PMP-1.00.doc Final 1.00 Page i FAS-1000-PMP-1.00.doc

4 TABLE OF CONTENTS DOCUMENT CONTROL...i Copyright notice...i Edition history...i Acknowledgements...i TABLE OF CONTENTS...ii 1. INTRODUCTION Context Objective Purpose Scope Key Enablers Trajectory Prediction (TP) and Human Machine Interface (HMI) Document structure and evolution Document Scope Document organisation Evolution of the document and change control Applicable documents and standards Definitions, abbreviations and acronyms ORGANISATION OF FASTI FASTI Target External Organisation of FASTI Lifecycle Overall Strategy Top Down Approach Bottom up Approach Stakeholder Roles...12 Final 1.00 Page ii FAS-1000-PMP-1.00.doc0

5 2.5 FASTI and the Military FASTI RACI ANSP s and the Programme Pioneers Developers Newcomers FASTI and the Pioneers FASTI and the Developers FASTI and the Newcomers Organisational structure of the Programme Internal Organisation of Programme...17 Programme Management...17 Business Case...17 Awareness and Communication...17 Operational Implementation...17 Safety and Regulatory Requirements...18 Human Factors...18 ATS Systems Roles and responsibilities Organisation Of Associated Parties External contracts MANAGERIAL ASPECTS Assumptions, dependencies and constraints Reporting structure of Project Managing and control mechanisms Contract management Procurement Risk Management Data Base Human resources management...20 Final 1.00 Page iii FAS-1000-PMP-1.00.doc

6 3.8 Stakeholder sign-off Close out procedure for Project TECHNICAL ASPECTS Methods, tools and techniques Documentation Support functions within Project Data management Configuration management Additional procedures for the conduct of work WORK PACKAGES AND SCHEDULE Work breakdown structure for FASTI Work Package Descriptions Programme Management Operational Implementation ATS Systems Business Case Safety and Regulatory Requirements Awareness and Communication Human Factors Schedule REFERENCES ANNEXES ANNEX A: Budget ANNEX B: FASTI Schedule and Main Deliverables ANNEX C: FASTI Groups Terms of Reference ANNEX D: FASTI Risk Management Overview...47 Final 1.00 Page iv FAS-1000-PMP-1.00.doc0

7 Figure 2-1 Organisation...9 Figure 2-5 Programme Phases and Lifecycle...10 Figure 2-2 FASTI Implementation Strategy and Key Stakeholders...13 Figure 2-3 ANSP s and the Programme...16 Figure 2-4 Work Packages...17 Figure FASTI WBS - Overview...23 Figure 5-2 ATS Systems Sub-workpackages...28 Final 1.00 Page v FAS-1000-PMP-1.00.doc

8 1. INTRODUCTION 1.1 Context The need for system support tools for air traffic controllers has never been greater. The development and validation of controller tools across Europe has been fragmented and uncoordinated leading to a diversity in system development and operational philosophies at both ANSP and industry level. The forecast growth in air traffic, the drive for safety improvements and cost efficiencies, means that the time is now right for a greater focus on the implementation of controller system support to meet the needs of the airspace user. Classical methods of providing operational improvements all have their finite limit. New initiatives are necessary. The fundamental tasks, roles, responsibilities and working methods of controllers have not changed in the last thirty years. The First ATC Support Tools Implementation (FASTI) Programme aims at highlighting the need for the co-ordinated implementation and rapid deployment of an initial set of controller support tools. The programme will address short and medium term requirements but will also enable the introduction of further automation in ATC in the longer term. Industry has a key role to play in directly contributing to FASTI and in upgrading, developing and delivering ATC systems to Air Navigation Service Providers (ANSP s) that meet the objective and aims of the programme. The programme is consistent with the objectives of the Single European Sky initiative. It will make a significant contribution in securing the baseline for SESAR by contributing to the ATM Master Plan and ensuring its scope features on the SESAR implementation roadmap. 1.2 Objective The objective of the programme is to co-ordinate the implementation and deployment of controller tools and system support, as required, across ECAC by 2012 in a harmonised way The programme also derives from the following ECIP Objectives: ATC03 - Implement automated ground to ground co-ordination ATC12 - Provide automated support for conflict detection 1.3 Purpose The programme aims to: Increase sector capacity, flight efficiency and maintain or improve safety to meet forecast airspace user demand. Provide implementation support to ANSP s, ATC Regulators and Industry in order to harmonise and expedite the deployment of controller automated system support. Establish appropriate controller system support capabilities and performance levels across the European ATM Network Final 1.00 Page 6 FAS-1000-PMP-1.00.doc0

9 Act as an enabler for future implementation of automated support to ATC currently under development 1.4 Scope The Programme will include the following controller tools and system support within its initial scope: o Medium Term Conflict Detection (MTCD) o o Monitoring Aids (MONA) System Supported Co-ordination (SYSCO) Key Enablers Trajectory Prediction (TP) and Human Machine Interface (HMI) TP is outside the scope of the programme but is identified as a key enabler being a core function of the Flight Data Processing System (FDPS). The programme will however specify TP performance requirements e.g. availability, integrity and continuity and the relationship between functioning of a tool and the various concepts of use will be described as part of the programme guidance material. HMI that enables easy access to flight data and the input of ATC clearances by controllers, thus permitting trajectory update, is also a key enabler for the functioning of future tools. HMI requirements and implementation guidance, associated with the programme scope, will also feature as part of the programme deliverable 1.5 Document structure and evolution Document Scope This document primarily covers the detailed aims, objective and plans for the initial implementation and pre-implementation validation phase (2005 to 2008) of the programme. The following phases are described at high level in terms of deliverables and budget required and will be subject to go/no go decisions by Eurocontrol Directors and stakeholders Document organisation Parent Documents The FASTI Programme contributes to the fulfilment of the strategic actions contained in the following documents: The ATM Strategy for the Years 2000+, The Operational Requirements and Data Processing Strategy. Subsidiary Documents The management, operational and technical aspects of the FASTI Programme will be defined in the FASTI deliverables to be produced according to the planning described below. Final 1.00 Page 7 FAS-1000-PMP-1.00.doc

10 1.5.3 Evolution of the document and change control The document will be updated according to the plan described in the programme schedule provided below and included in the Eurocontrol PMS. Any significant changes to the planned work (e.g. timescales, deliverables and organisation) shall be subject to approval from the Programme Manager and consultation with the Programme Steering Group. In the event of a large number of changes, a new PMP may be re-issued. 1.6 Applicable documents and standards This PMP is fully compliant with the guidance provided by the EATM Management Handbook. 1.7 Definitions, abbreviations and acronyms EPMP OFG PM PMP PSG PSO SRRFG TBP WP WPL Executive (external use) Operational Focus Group Programme Manager Programme Steering Group Programme Support Office Safety Regulatory Requirements Focus Group To Be Provided Work Package Work Package Leader 2. ORGANISATION OF FASTI 2.1 FASTI Target The programme and its stakeholders have to commit to and achieve the following: Successfully implement FASTI capability at controller working positions across Europe 2.2 External Organisation of FASTI The FASTI Programme is an integral part of the consultation and decision making structure of the Eurocontrol Agency. Final 1.00 Page 8 FAS-1000-PMP-1.00.doc0

11 Commission/ General Assembly Provisional Council Director General EATM SBU Director s Meeting FASTI PSG FASTI OFG Operational Focus Group FASTI SRRFG Safety and Regulatory Requirements Focus Group Figure 2-1 Organisation The Terms of Reference for the FASTI Stakeholder Groups (i.e. PSG, OFG) are provided at Annex C to this document. The SRRFG will start during Lifecycle The FASTI programme follows the EATM lifecycle as defined in the EATM Management Handbook. Final 1.00 Page 9 FAS-1000-PMP-1.00.doc

12 Initial Implementation and OPS Validation 2009 Implementation and OPS Planning Implementation and Co-ordination Figure 2-2 Programme Phases and Lifecycle The programme initial implementation and operational validation phase ensures an extra reality check on proposed solutions by undertaking simulations or trials to verify and refine implementation issues, specifications, procedures and the preliminary Safety Case as well as enhance the Business Case. The programme will profit from the experience gained by a number of ANSP s who plan to implement some FASTI capability from 2007 onwards. Full programme support will be given to these initiatives. The programme implementation and operations planning phase will provide a detailed understanding of all the practicalities of successful implementation and will produce a final co-ordinated implementation plan for ECAC. Commitment for implementation (i.e. agreed ECIP objectives) is obtained in this step with LCIP objectives developed accordingly. The programme implementation coordination phase is the last phase of a programme. FASTI working with EUROCONTROL s SIS/BD will co-ordinate activities such as: regional safety assessments, detailed design, development, or customisation of standard products, integration of the components, testing, publications, education, training procedures and final deployment to full operations The start of each phase is subject to a management go/no-go decision based on the deliverables produced in the previous phase and in consultation with the major stakeholders. In order to ensure that the timescales for implementation are as short as possible the programme will aim to take advantage of local stakeholder initiatives through close coordination and cooperation. The involvement of industry in all three phases of the programme is essential to ensure timely and harmonised implementation. The end of the programme in 2012 represents the date where final implementation across ECAC will be completed. Final 1.00 Page 10 FAS-1000-PMP-1.00.doc0

13 2.4 Overall Strategy The programme strategy for implementation will be based on a dual approach; top down and bottom up (see Figure 2-2). FASTI is applicable to ECAC States where traffic levels and complexity range from low to high. The implementation of FASTI is expected to take place in en-route and extended TMA airspace managed by Area Control Centre s (ACC s) where full surveillance is available Top Down Approach The top down approach will ensure that the programme is performance driven. During the pre-implementation phase of FASTI targets levels of performance will be identified and agreed with stakeholders in order that real improvements can be achieved, and eventually measured. Examples where performance targets may be set are as follows: Sector capacity declare expected increases Lower ANSP cost limit the need for re-sectorisation Improved service to users Safety identify number incidents that could have been prevented by FASTI capability, and/ or maintain the present number incidents whilst more traffic Efficiency use operational staff in different ways The overall effect of individual ANSP implementations will also have to be assessed across the background of the ATM Network. In the majority of cases it will be important for adjacent ACC s to have similar performance levels, following FASTI implementation, to avoid the interface becoming the bottleneck. The harmonisation of procedures and operational practices at these interfaces will be essential to achieve full benefit from the implementation of controller tools and system support Bottom up Approach The bottom up approach will fulfil the need for filling the gaps which has been identified during the consultation phase of the programme. There is a need to address this missing work to ensure successful pan-european FASTI implementation. Examples of existing gaps are as follows: Concepts of use for ATC tools and system support Safety requirements Operational requirements Performance requirements for tools and enablers New ATC procedures and practices Resolution of human factors issues Training and transition planning Business case FASTI will act as a focal point for the re-use of existing expertise in order to produce guidance material and highlight best practice for use by the wider European ATM community. Final 1.00 Page 11 FAS-1000-PMP-1.00.doc

14 2.4.3 Stakeholder Roles The key stakeholders of the FASTI Programme are ANSP s and their controllers, airspace users, Industry - ATC system manufacturers, ATC Regulators and the European Commission - Single European Sky (SES) team. The role of each key stakeholder is explained below Airspace Users Airspace users with their requirements for access to the airspace, predictability of operation and demands for lower operating costs will drive the performance aspects of the programme and its implementation strategy. They will verify benefits achieved following implementation by ANSP s ANSP s The implementation of FASTI capability by ANSP s is essential to the success of the programme. In order to facilitate this process FASTI will assist ANSP s by helping to reduce risk and potentially lower costs through co-ordination, the sharing of best practice, cooperation, collaboration and harmonisation. ANSP s will be able to demonstrate to their customers, the airspace users, that they are striving to achieve early benefits and satisfy user requirements through participation in FASTI. The need to establish a baseline from which FASTI operational improvements can be subsequently measured is essential in the interests of both the ANSP and the programme ATC Regulators ATC Regulators will provide the operational approval for new systems and operations. Early involvement in FASTI will permit an understanding of the technical, operational and safety requirements associated with such implementation. This will lead to reduce risk and potential costs savings during the final approval process Industry Industry has a key role to play by providing their lessons learnt from current implementations. They will be directly involved by upgrading, developing and delivering ATC systems to ANSP s that meet the aims and objective of the programme SES The European Commission and its Single European Sky (SES) team have an important role in finally determining the need for regulation associated with the programme and potentially providing incentives to expedite the deployment of FASTI capability across its Member States. FASTI will secure the baseline for SESAR and will form an important foundation for the implementation of future automated support to ATC in common with SES objectives. Final 1.00 Page 12 FAS-1000-PMP-1.00.doc0

15 Top Down Performance Driven Airspace Users Benefits Requirements ANSP s ATC Regulators Industry Potential Regulation Incentives SES objectives achieved SES Bottom Up Filling the Gaps Figure 2-3 FASTI Implementation Strategy and Key Stakeholders 2.5 FASTI and the Military Where a fully integrated civil/military ATC service is provided by one ATSU the provision of FASTI capability is a relatively simple task. Where dual service exists in the same airspace the military and civilian ATSU s should have the same capabilities in order to ensure that both sides have a consistent picture of air traffic within the same airspace. Final 1.00 Page 13 FAS-1000-PMP-1.00.doc

16 2.6 FASTI RACI Eurocontrol FASTI PM Airspace users ANSP s ATC Regulators Industry IFATCA SES and SESAR Military Programme Management A C C C C I C C Business Case A C C C C C C C Awareness & Communication A I I I I I I I Operational Implementation A C R R R I I R ATS Systems A I R C R I I R Safety and Regulatory Requirements A R R R R C R R Human Factors A I C C C C I C Table 1 - RACI The table above provides an analysis of stakeholder involvement in the programme as follows: R - Responsible A - Accountable C - Consulted I - Informed 2.7 ANSP s and the Programme The programme will co-ordinate the implementation conducted by ANSP s and Industry, providing implementation support where appropriate. During the programme consultation phase it has been identified, in the context of FASTI, that participating ANSP s can be divided into the following three groups (see figure 2-3): Pioneers Developers Newcomers Final 1.00 Page 14 FAS-1000-PMP-1.00.doc0

17 2.7.1 Pioneers The Pioneers are those ANSP s that have either: (i) (ii) Implemented some elements of FASTI which are in operational daily use or Procured new ATC systems which have included some elements of FASTI but which are not being fully exploited operationally Developers The Developers are those ANSP s who have conducted R&D and validation of elements of FASTI, over a number of years and who are now engaged in pre-implementation activities Newcomers The Newcomers are those ANSP s who are either: (i) (ii) Considering the implementation of FASTI capability in the procurement of a new systems or system upgrade or Have not yet considered implementing FASTI capability FASTI and the Pioneers FASTI will capture those lesson learnt in current implementations for the benefit of the European ATM community. Where requested by the ANSP, the programme will help to identify where improvements can be made to achieve full potential of pioneer implementations. This may be achieved in the following five steps: Establishing with the ANSP clear aims and objectives for the implementation of FASTI capability Making an assessments from an operational, technical and business perspective of the current implementation to determine the delta to achieve improvement Support ANPS s in the validation of potential solutions through studies and simulations Provide support to the ANSP and Industry to achieve successful upgrades in the shortest possible timescale and at best cost. Investigate the need for incentives to expedite deployment of improvements Final 1.00 Page 15 FAS-1000-PMP-1.00.doc

18 2.7.5 FASTI and the Developers FASTI will aim to capture R&D and validation results conducted by ANSP s and combine them with previous results obtained by the EUROCONTROL Agency for the benefit of the wider European ATM community. Expertise found amongst the Developers can be re-used to solve outstanding implementation issues. The programme will support the Developers by helping to promote their achievements, identify opportunities for co-funding implementation activities of mutual benefit by forming partnerships and co-ordinate the exchange of information and experience. FASTI support will also aim to minimise risk to planned implementation plans and timescales FASTI and the Newcomers The FASTI deliverables in the form of requirements and guidance material should considerably enhance the chances of successful implementation by the Newcomers. They will profit from all the lessons learnt from the Pioneers and Developers which will permit expeditions deployment of FASTI capability at lower risk and cost across ECAC. For those Newcomers that have not considered implementing FASTI capability support to CBA, operational and technical advice will be provided by FASTI on a strategic basis. In some cases a decision not to implement FASTI capability may be the outcome of an assessment thus saving ANSP s time and cost. FASTI Objective, Aims Scope ANSP s Pioneers Programme Capture lessons learnt and where necessary offer assistance to achieve full exploitation of existing implementations. Developers Make use of expertise to resolve implementation issues, help promote achievements, facilitate exchange of experience and provide support Newcomers Provide full implementation support Implement yes or no Increase sector productivity and improve ATM Network =Implementation of FASTI capability on Controller Working Positions Figure 2-4 ANSP s and the Programme Final 1.00 Page 16 FAS-1000-PMP-1.00.doc0

19 2.8 Organisational structure of the Programme Internal Organisation of Programme Programme Manager Programme Support Office Business Case WPL Awareness & Communication WPL Operational Implementation WPL Safety & Regulatory Requirements WPL ATS Systems WPL Human Factors WPL Figure 2-5 Work Packages Programme Management A, Implementation Plan, stakeholder commitment through the ECIP process is required. There may also be a requirement to develop a regulation strategy to ensure expeditious and harmonised deployment of FASTI capability across Europe. Business Case The creation of a FASTI Business Case is required to identify both the pan-european and national level impact of FASTI. Case studies will enable other stakeholders re-use the methodology for their own implementation cases. Awareness and Communication Need to raise general awareness of automated support to ATC amongst the stakeholder community. Operational Implementation An ATC Manual will be created which will contain guidance material for the following: Concepts of operations ATC procedures Cross sector-boundary use Cross centre-boundary use Final 1.00 Page 17 FAS-1000-PMP-1.00.doc

20 Civil/military operations Safety and Regulatory Requirements A FASTI Safety Assessment, which will derive safety requirements, will be conducted encompassing the scope of the programme targeted at the Safety Regulation Commission (SRC) review and recognition. Human Factors A Human Factors Case and subsequent lines of action to determine training needs, upgrade paths, adoption, adaptation, fall back, failure, human resources and liability issues will be developed. ATS Systems FASTI Operational Requirements will be developed. ATS system implementation guidelines will cover topics essential to enable successful implementation e.g. HMI principles, tools integration, trajectory prediction and interoperability requirements Roles and responsibilities The roles and responsibilities for the EATM Directors, Heads of Business Division and the Programme Manager are defined in the EATM Management Handbook. Work Package Leader (WPL) The main role of a WPL is to proactively support the objectives of the FASTI Programme by managing a FASTI Work Package to achieve its objectives on time and to budget. Detailed responsibilities are to: Manage the WP in accordance with the relevant EATM processes. This includes to produce a planning for the work package tasks/projects identifying all deliverables, milestones, required resources and quality of assurance approach; Support the establishment and maintenance an effective network of internal and external stakeholders and other professionals in order to share knowledge and ideas; Support the FASTI staff management activities by providing inputs to recruitment, staff planning and the staff development processes; Manage the budget assigned to the WP, including launching and management of contracts, budget planning and providing budget progress reports to support the performance checkpoints; Manage the staff assigned to the WP ensuring progress and provide performance reports to the Programme Manager; Provide reports to and receive advice from the FASTI Steering and Focus Groups, and provide periodic reports to other stakeholders; Contribute to FASTI projects by offering professional advice and reference material in order to find solutions to problems; Final 1.00 Page 18 FAS-1000-PMP-1.00.doc0

21 Programme Support Office EUROCONTROL will establish a Programme Support Office (PSO) to support the Programme. The PSO will be set up under the responsibility of the Programme Manager who will delegate the day-to-day operations to the Programme Managers Assistant. The Programme Managers Assistant has responsibilities for the establishment and maintenance of the Programme and Project Management Plans and their subsidiary Plans (Risk Management, Procurement, Budget etc.) as well as monitoring the Programme progress against the agreed baseline. The PSO shall also coordinate projects that require the participation of several Work Packages (e.g. validation projects). The PSO will ensure that Stakeholders plans are integrated into the overall Programme Organisation Of Associated Parties No organisation of associated parties has been defined for FASTI External contracts All external contracts shall be recorded and keep updated in the Eurocontrol Project Management System (PMS). Final 1.00 Page 19 FAS-1000-PMP-1.00.doc

22 3. MANAGERIAL ASPECTS 3.1 Assumptions, dependencies and constraints Given the large scope of the programme, all FASTI assumptions, dependencies and constraints are provided in the work package descriptions. 3.2 Reporting structure of Project EATM Management Handbook procedures apply. 3.3 Managing and control mechanisms The FASTI management and control mechanism are defined in the management work package description. 3.4 Contract management Standard Agency procedures apply. 3.5 Procurement Standard Agency procedures apply. 3.6 Risk Management Data Base A FASTI risk register is kept up-to-date and stored in: P:\ProgrammeDocuments\RISK 3.7 Human resources management EATM Management Handbook procedures apply. 3.8 Stakeholder sign-off EATM Management Handbook procedures apply. 3.9 Close out procedure for Project EATM Management Handbook procedures apply. Final 1.00 Page 20 FAS-1000-PMP-1.00.doc0

23 4. TECHNICAL ASPECTS 4.1 Methods, tools and techniques This information is provided in the work package descriptions. 4.2 Documentation This information is provided in the work package descriptions. 4.3 Support functions within Project Data management The FASTI data is stored in three places: 1. A shared drive 2. Several OneSky extranet groups 3. The FASTI website Configuration management The FASTI Configuration Items are identified in the workpackage descriptions provided below and in the Eurocontrol PMS FASTI Reference Identification The FASTI Deliverable reference numbers will be composed as follows: Work package Identification Deliverable Acronym Edition Number Work package Identification FASTI Workpackages Identification codes are detailed below: Workpackage Name Programme Management Operational Implementation ATS Systems Safety and Regulatory Business Case Awareness and Communication Human Factors Workpackage Identification PM OI AS SR BC AC HF Deliverable Acronym This will be composed of up to 5 characters. For example: PMP for the Programme Management Plan. Final 1.00 Page 21 FAS-1000-PMP-1.00.doc

24 Edition Number The basic form of the edition number is: Edition = N.X for a Configuration item in released state where N is the major number and X the amendment number. Edition = N. XY for a Configuration item in working mode where N is the major number, X the amendment number and Y the draft issue Storage and Archiving All items subjected to configuration control must be approved and authorised before it is accepted into configuration control by the Configuration Librarian. Each workpackage description below defines the approval procedure for each deliverable under configuration control. The Programme Managers Assistant will assume the role of the FASTI Configuration Librarian and will store and archive all items following the EATM Management Handbook Guidelines Additional procedures for the conduct of work None defined so far. Final 1.00 Page 22 FAS-1000-PMP-1.00.doc0

25 5. WORK PACKAGES AND SCHEDULE 5.1 Work breakdown structure for FASTI Programme Management Plan Safety Considerations 2006 FASTI Concept of Use FASTI Baseline Survey FASTI Demonstrator FASTI Safety Plan HF Action Plan FASTI Business Case 06 ECIP Objectives Operational Services and Environment Description Pioneer Systems Assessments FASTI 1 Real-Time Simulation Report FASTI 1 Fast-Time Simulation FASTI Operational Requirements 2007 ATC Manual FASTI Implementation Guidelines FASTI Performance Requirements Safety Assessment Safety Requirements FASTI Systems Manual ESSAR 6 Guidance Material IANS Training Course Incentives Strategy FASTI 2 Real-Time Simulation Report 2008 Draft Implementation Plan ATC Procedures SES Draft Regulatory Material FASTI Business Case 08 FASTI Master Plan FASTI 3 Real-Time Simulation Report Figure FASTI WBS - Overview Final 1.00 Page 23 FAS-1000-PMP-1.00.doc

26 5.2 Work Package Descriptions Programme Management Work Package Leader: Chris Brain Workpackage Programme Management Objective Coordinate the implementation and deployment of controller tools and system support, as required, across ECAC by Inputs Delegated authority from EATM Directors. Relevant procedures and guidelines from the EATMP Management Handbook. Relevant deliverables from the ATS domain and other relevant projects. Active participation of Programme Steering Group and Focus Groups representatives, and individuals supporting work package completion. Allocated budget. Stakeholder plans and progress reports. Tasks and Approach Programme management WP will track programme progress according to the baseline specified in the making changes as necessary. Input from the Programme Steering Group will also provide guidance and support to the management of the Programme and may effect the baseline. The development of an Implementation Plan, ECIP Objectives and stakeholder commitment will be conducted within this WP. Outputs and Milestones Progress reports highlighting progress and main issues to Directors (bi-monthly) and external working arrangements as required. Stakeholder Commitment. Equipped ATS units Resources Programme Manager Programme Management Assistant Administrative support Meetings: PSG and Focus Groups Meetings, monthly internal co-ordination meetings. Detailed budget and resources are provided in Annex Operational Implementation Workpackage Operational Implementation Work Package Leader: Bogdan Petricel Final 1.00 Page 24 FAS-1000-PMP-1.00.doc0

27 Objective The main objective of the Operational implementation workpackage is to produce guidance material to support the operational implementation of the controller s tools considered by the programme (i.e. MTCD, MONA, SYSCO). The main deliverable of this work package will take the form of an operations manual (ATC Manual of Operations) and it will be derived from inputs with respect to the operational requirements, system requirements, concept of operations, human factor and safety case. The guidelines resulting from this process will be validated through generic and local validation experiments e.g. real and fast time simulations & trials. Inputs Relevant procedures and guidelines from the EATMP Management Handbook. Active participation of Programme Steering Group and Operational Focus Group (OFG) representatives, and individuals supporting work package completion. Allocated budget & resources Stakeholder plans and progress reports. Operational Requirements (Operational Requirements Document for EATCHIP Phase III ATM Added Functions Volume1: Monitoring Aids Edition 2.0; Operational Requirements Document for EATCHIP Phase III ATM Added Functions - Volume 5 MTCD Edition 2.0) OLDI Standard (EUROCONTROL Standard Document for On-Line Data Interchange (OLDI) Edition 3.0) Generic and local validation process results ECIP Objectives LCIP Objectives Technical feasibility and constraints from the ATS Systems workpackage Operational and technical feasibility and constraints from the Human factor and Safety Case Implementation plan Tasks and Approach The tasks in this WP are: Provide operational input to permit update and consolidation of the operational requirements for the proposed controllers tools (i.e. MTCD and MONA) To produce and update the FASTI Concept of Operations document To produce the Operational Services and Environment Description documents (OSED) as an internal deliverable to be used as an input in the validation work as well as for the ATS Systems WP To produce the FASTI ATC Manual of Operations To co-ordinate and lead the operational validation work for the proposed package of controller s tools To provide operational support at the stakeholder level for the FASTI package implementation (operational advice to pioneer systems) To provide inputs and expertise in the Human Factor and Safety case development To provide operational input and expertise into the Business Case To establish the consensus on the proposed deliverables with the programme stakeholders via the OFG working group and PSG approval group To provide support to the educational process at the EUROCONTROL level (support for training requirements and concepts of use both at a transition and ab-initio level, provision of package demonstrations) To provide operational support to the other FASTI work packages Final 1.00 Page 25 FAS-1000-PMP-1.00.doc

28 The FASTI Operations work will include both the drafting and preparatory phase of the guideline documentation required for implementation as well as the provision of support and co-ordination of the operational validation activities. Using the operational requirements and the previous validation work (RTS and trials) provided by the ATC Domain as an input, the FASTI Operations WP will deliver the Concept of Operations Document, and, as an internal deliverable, the FASTI Operation Services and Environmental Description (OSED). Having as a main objective the production of validated implementation guidelines (through the ATC Manual of Operations) the FASTI Ops WP will undertake the task of supporting and co-ordinating the operational validation work. This will ensure the provision of consolidated and validated requirements with respect to methods of working, human machine interface issues, system requirements and safety issues which will be used as the main input into the FASTI ATC Manual of Operations document the main deliverable of the work package. The following principles have been used to define the main WP milestones: Existence of previous domain work with respect to the proposed implementation package The need for validation preparation and execution Stakeholders consultation and approval process of deliverables Available resources Outputs and Milestones See Annex B Resources Work Package Leader Programme Management support Administrative support Expert support (ATS Systems WP, Safety & Regulations WP, Human Factors WP etc.) Meetings: FASTI OFG working group, FASTI PSG, internal FASTI Team meetings Final 1.00 Page 26 FAS-1000-PMP-1.00.doc0

29 5.2.3 ATS Systems Workpackage: ATS Systems Work Package Leader: Stephen Morton Objective The objective of the ATS Systems work package is to produce guidance material that can be used by ANSPs and system providers in the procurement and development respectively of controller tools. Guidance material will take the form of operational requirements derived from the operational services and environment description, supplemented with information on implementation options and feedback from validation. The objective of the guidance material, from the point of view of the ANSP, is to provide assistance in identifying the capabilities of the controller tools required to support a chosen concept and working method, and the required performance of the supporting ATM system (flight data processing, trajectory prediction, etc). Assistance is also provided in the tuning of the controller tools by means of variable system parameters. As an important principle, the maturity of each capability is given, in terms of results obtained from validation exercises, to facilitate the choice of capabilities to maximize the ANSP s return on investment. From the point of view of the ATM systems supplier, the aim of the guidance material is to assist in the development of controller tools as part of an integrated ATM system. The description is intended to provide sufficient detail to specify unambiguously the required capabilities and to allow the reader to take maximum benefit of the various validation activities performed, without unnecessarily constraining the system design. Inputs Operational Concept (WP) Operational Services and Environment Description (WP) EATM Operational Requirements for Added Functions, Volume 1 (MONA) EATM Operational Requirements for Added Functions, Volume 5 (MTCD) Validation results EATM, ifacts, ERATO, Gate-to-Gate, etc Tasks and Approach Generic operational requirements were developed for MTCD and accompanying tools in the framework of EATCHIP at the end of the 90s, since when some initial commercial implementations have been derived. In addition, certain core-area ANSPs have developed the requirements further for their own environment and have performed exercises to validate their requirements. The principal on which the FASTI programme is based is one of pooling the experience already gained in MTCD development, thereby allowing each ANSP to take advantage of the experience pool to develop their own implementation, and then to feed their experience back into the pool. As such, FASTI guidance material will be developed primarily via a bottom-up process of collating available experience to document the current state of the art, using this as a basis for assisting ANSPs in the definition of their own concept and requirements, and feeding their experience back into the guidance material. Results of real-time and fast-time simulations performed under workpackage x will also be fed into the guidance material. This will be performed through the sub-work packages 1 Produce ATC Systems Document, and 2 MTCD Implementation and Validation Support. See Figure 5.1 Final 1.00 Page 27 FAS-1000-PMP-1.00.doc

30 EATCHIP/ EATM/ ASA Operational Requirements DSNA ERATO NATS FACTS DFS JANE/ VAFORIT EUROCONTROL PROVE / ACE ANSP Commercial System Workpackage x.x - Real-Time and Fast- Time Simulations Workpackage x.1 Produce ATC Systems Manual Workpackage x.x Operational Services and Environment Description (OSED) ATC Systems Baseline Workpackage x.2 MTCD Implementation and Validation Support Pioneer Systems Assessment FASTI Operational Requirements FASTI ATC Systems Document FASTI Implementation Guidelines FASTI Host System Performance Requirements Pioneer Validation Report Figure 5-2 ATS Systems Sub-workpackages WPx.1 - Produce ATC Systems Manual The ATC Systems Baseline Survey The work package will initially perform an analysis of the current state of implementation of the EATM operational requirements in Eurocontrol and other validation and [pre-] operational systems. The aim of this analysis is to assess the maturity of the requirements and to identify differences in each implementation s interpretation of the requirements. Differences between the implementations will be further analysed to determine whether they are simply alternative solutions to a common requirement, or whether they are solutions applicable to a particular context/environment. The analysis will also identify implemented and validated features that do not derive from the EATM operational requirements (gaps). The results of the analysis will be documented in deliverable xxx1, ATC Systems Baseline Survey. Final 1.00 Page 28 FAS-1000-PMP-1.00.doc0

31 Pre-operational systems that have been identified as contributors to the FASTI ATC System Baseline Survey comprise the DSNA ERATO system and the NATS ifacts system. FASTI team members will work with DSNA and NATS counterparts to document each system s operational concept in terms of: The operational goals of the MTCD implementation and quantified [target/achieved] benefit; Particular features of the operational environment (traffic types and flows, letters of agreement, proximity of military traffic, etc); Operational roles and working method; Supporting tools specifications; Feedback from validation and issues remaining to be solved. This is likely to require in the region of 8 man-days effort from each of DSNA and NATS. An equivalent activity will be performed on the EATM validation system (ERIS), focussing on the trials performed at Malmo, Rome and Maastricht in the context of the Automated Support to ATS Programme and on applicable simulations in the EC Gate to Gate Programme. Assumed that Ops team will try to make sense of the operational concepts and will derive flavours applicable to certain environments or timeframes. The specifications of each system analysed will be merged into the ATC Systems Baseline, identifying common, core capabilities, and variable capabilities that depend on a particular variation of the operational concept. Where considered useful, examples of implementations will be given to illustrate possible approaches to achieving an operational requirement. The ATC Systems Baseline shall also indicate the maturity of the requirements and the remaining issues to be solved. FASTI ATC System s Document The ATC System s Document shall be a comprehensive set of guidelines for the procurement and implementation of the FASTI controller tools, comprising operational requirements, performance requirements of the host system, and implementation guidelines. Once the OSED has reached a sufficient level of maturity, a top-down derivation of operational requirements from the service descriptions will be performed. Operational requirements shall cover MTCD, system-supported coordination and transfer, and monitoring aids. Where met by current implementations, the requirement specification will be obtained from the deliverable, ATC Systems Baseline ; otherwise, new requirements, requiring validation, will be specified. The requirements specification, together with implementation and validation information, will be documented in deliverable, FASTI Operational Requirements. The operational requirements shall cover solely the functionality of the ATC tools identified above. However, the tools themselves demand a certain level of capability of the underlying host ATC system, primarily in the calculation of flight trajectories, surveillance and tracking. These shall be documented in the form of performance requirements in deliverable xxx, FASTI Host System Performance Requirements. Whilst the operational requirements shall be implementation-independent, allowing flexibility in the design of a solution, implementation guidelines shall describe best practices, benefiting from the experience gained from the current implementations. Best practices will cover diverse aspects such as HMI techniques, parameter tuning, algorithmic choices, and performance trade-offs. Final 1.00 Page 29 FAS-1000-PMP-1.00.doc

32 WPx.2 - MTCD Implementation and Validation Support Implementations of the EATMP MTCD requirement have been available in commercial systems for some time and have been delivered to a number of ANSPs. However, in all but exceptional cases, the MTCD function is not used operationally due to deficiencies in the MTCD function or supporting host system, and/or the lack of a concept of use. The objective of this work package is to identify and remedy the deficiencies in the existing MTCD implementations such that they are brought into operational service and deliver benefit. This will be achieved by assessing a number of candidate systems, making recommendations for improvements, and validating the upgraded capability by means of simulations or live trials. Candidate systems shall be considered as recently-delivered commercial systems containing an MTCD function. It is intended that only a single instance of a system from a particular supplier need be chosen, as the recommendations made for one ANSP s version of a product should be applicable to other ANSPs using the same product-line. The FASTI programme shall provide communication of recommendations between the users of a particular product line in order to facilitate the formulation of common upgrade requirements by the product user-groups. Results of these validation exercises shall also be fed back to the FASTI ATC Systems Document produced in WPx.1. Outputs and Milestones See Annex B Resources Work Package Leader Programme Management support Administrative support Expert support (Ops Implementation WP, Safety & Regulatory WP, Human Factors WP etc.) Meetings: FASTI OFG working group, FASTI PSG, internal FASTI Team meetings Final 1.00 Page 30 FAS-1000-PMP-1.00.doc0

33 5.2.4 Business Case Workpackage: Business Case Work Package Leader: Sven Fraenkel Objective The main objective is to produce a series of Business Cases that can be used by ANSP s to support the acquisition and implementation of FASTI operational functionalities. The ANSP s will be categorised by their respective development/implementation status (Pioneers, Developer, Newcomers) and airspace density and complexity function. The initial Business Case shall be based upon the ASA-FASTI CBA study results from 2005 conducted by Helios (UK), reviewed and augmented by the content of the present work package to cover the strategic fit at both European and ANSP s levels, the strategic case, ANSP s unit cost data, Environment considerations, Operational and Technical feasibilities, Human and Social acceptability, Safety case dependencies in terms of cost, planning and regulatory obligations, Validation Objectives and Plans to support expected benefits figures. Inputs European Model for Strategic ATM Investment Analysis ( EMOSIA) guidelines and six-step process EMOSIA Generic Model EMOSIA ANSP model EUROCONTROL Standard Inputs for CBA s EUROCONTROL Performance Review Reports ; PRR 6 (07/2003)& PRR 8(04/2005) ATM Cost effectiveness, 2002 Benchmarking Study ACE Study (05/2004) EUROCONTROL STATFOR 05/2005 Active participation of Programme Steering Group representatives and individuals supporting work package completion Allocated budget and resources ANSP s developments plans, implementation plans and progress reports Generic and local validation process results Technical feasibility and constraints from the ATS Systems work package Operational and technical feasibility and constraints from the Human Factor and Safety Case Approach and Tasks The tasks in this work package are: To build and consolidate the European Strategic Fit To build and consolidate ANSP s CBA models according to airspace complexity and implementation plans Analyses ANSP s respective FASTI functionalities deployment scenario s and to correlate them with the European Strategic fit. Define Validation objectives and plans supporting CBA expected benefits Conduct sensitivity analysis s on models with quantitative outputs Integrate Safety Case work outputs to provide cost data on infrastructure overhead costs related to FASTI. ( operational system reliability factor, built-in redundancy requirements, software maintenance...) to counter elements like loss of situation awareness and recovery time /failure Integrate ATS Systems work outputs to provide technical feasibility and cost data on ANSP s respective unit infrastructure cost Final 1.00 Page 31 FAS-1000-PMP-1.00.doc

34 Integrate Operational Implementation work output to support cost /benefit data Risk Analysis in terms of FASTI program planning versus Safety Case availability for major elements like TP s, technical, operational and regulatory dependencies Analyse the Human and social acceptability ; ATCO s comfort factor gained by FASTI tools, etc Analyse environment considerations Provide cost-benefits data on competing implementation programmes providing higher or earlier ROI s Output and milestones See Annex B Resources Work Package Leader Programme Management Support Administrative Support Budget to conduct BP breakdown studies and consolidations ( validation objectives, sensitivity analysis, ANSP s models simulations,etc) Expert Support ( ATS Systems, Safety & Regulation, Programme Management Support, etc) Final 1.00 Page 32 FAS-1000-PMP-1.00.doc0

35 5.2.5 Safety and Regulatory Requirements Workpackage: Safety and Regulatory Requirements Work Package Leader: Predrag Terzioski Objective The objective of the Safety and Regulatory Requirements is to produce safety requirements and prepare input material to support regulation process related to FASTI Implementation..Scope The scope of this WP is to: Show, via means of a Preliminary Safety Case, that the FASTI Concept is acceptably safe in principle i.e. subject to complete and correct implementation; Ensure that the safety responsibilities of the FASTI Programme and the other Stakeholders are fully specified and delineated in respect of Concept development; Ensure that the safety responsibilities of the FASTI Programme and the other Stakeholders are fully specified and delineated in respect of implementation; Ensure that guidance is provided to the Stakeholders on how to discharge their safety responsibilities during Concept development, sufficient to ensure the safety of the Concept; Ensure that guidance is provided to the Stakeholders on how to discharge their safety responsibilities during implementation, sufficient to ensure the complete, correct and consistent implementation of the Concept; Decide the degree and extent of the guidance to be provided (i.e. what is sufficient ), including the development of common procedures etc; Prepare material in form of safety case and regulatory requirements to support FASTI implementation Tasks and Approach Develop safety case- following the Eurocontrol SMS process enhanced by stakeholders and operational input through the SFG and OFG Prepare Regulatory framework for Capacity Enhancing Tools- trough the SES framework and coordination with SRU and EC Support regulators- through provision of guidelines and advice for regulating implementation and use of enhanced controllers tools. Developing performance criteria and appropriate measurement tools for the licensing of systems and OPS procedures Assist OI WPL to prepare simulation specifications from safety viewpoint Ops advice to Pioneer systems Contribute to human factors and business cases- trough integration of related safety requirements Assist PM Inputs EUROCONTROL SMS Process Final 1.00 Page 33 FAS-1000-PMP-1.00.doc

36 Output and milestones See Annex B Resources Work Package Leader Programme Management support Administrative support Expert support (Safety & Regulatory) Meetings: FASTI SRRFG, FASTI OFG, FASTI PSG, internal FASTI Team Final 1.00 Page 34 FAS-1000-PMP-1.00.doc0

37 5.2.6 Awareness and Communication Workpackage: Awareness and Communication Work Package Leader: Frank Riquet Objective Manage FASTI Technical Communications and support-develop relations with programme stakeholders. Inputs WP Leaders and stakeholders time / contributions and designated actions. Concept of use Validations/Trials and Simulations Operational support Approach and Tasks -Position FASTI in EURO-ANSPs implementation developments; -Structure programme communications internally and towards partners (e.g. Ops groups/industry,controllers, etc); -Develop dynamic information on programme deliverables; -Organise events and demos centred on operations and implementations; -Information coordination; -brochures/web info review and guidance; -Events participation; -Direct stakeholders actions. Verify quality via programme reviews and direct stakeholder consultations Output and milestones See Annex B Resources Work Package Leader Programme Management support Administrative support Website support Meetings: FASTI Stakeholders, FASTI OFG, FASTI PSG, internal FASTI Team Final 1.00 Page 35 FAS-1000-PMP-1.00.doc

38 5.2.7 Human Factors Workpackage: Human Factors Work Package Leader: Una Mellett Objective The objective of this WP is to: Carry out a Human Factors Case and develop requirements and guidelines for Human Factors in FASTI Implementation. Liaise with IANS in developing training material for FASTI * The guidelines will be integrated as a chapter in the ATC Manual. Inputs Operational Implementation Focus Group Safety and Regulation ATS Systems Simulations Findings for MTCD simulations Lessons Learned from ANSPs IANS to determine training needs and develop material Approach and Tasks The approach is to carry out a Human Factors Case which involves: Stage 1: Fact Finding and Human Factors Issue Analysis (HFIA) Stage 2: Human Factors Integration (Action Plan) Stage 3: Monitoring and Action Plan Realisation including the development of requirements and guidelines on integrating HF in FASTI Implementation **Stage 1 will be carried out in conjunction with the Safety Case Process as FASTI programme provides an opportunity to see how to link the safety case and HF case Tasks are as follows; To scope and understand the FASTI context. To plan and organise the HF Issue Analysis Workshop** To facilitate the HF Issue Analysis Workshop To produce an HF Action Plan To co-ordinate the HF Actions To liaise/co-ordinate with IANS on the development of training material To produce requirements and guidelines for FASTI Implementation Outputs and Milestones See Annex B Resources Workpackage Leader. Operational and Technical, Training and Safety, HF Experts. Administrative support. Meetings Final 1.00 Page 36 FAS-1000-PMP-1.00.doc0

39 5.3 Schedule See Annex B 6. REFERENCES Document Name EATM Management Handbook Reference 11e23d d886c10002a5f907f0.html Final 1.00 Page 37 FAS-1000-PMP-1.00.doc

40 7. ANNEXES Final 1.00 Page 38 FAS-1000-PMP-1.00.doc0

41 7.1 ANNEX A: Budget Activity Preimplementation & Operations Validation Implementation & Operations Planning Implementation Co-ordination ALL ACTIVITIES Expenditures FASTI Programme Total FTE KEUR FTE KEUR FTE KEUR FTE KEUR FTE KEUR FTE KEUR FTE KEUR FTE KEUR FTE KEUR GEN S.E. effort Ex effort As effort Sec effort Total effort = Staff Related Expend Operating Expenditure Investment Total activity GEN S.E. effort Ex effort As effort Sec effort Total effort = Staff Related Expend Operating Expenditure Investment Total activity GEN S.E. effort Ex effort As effort Sec effort Total effort = Staff Related Expend Operating Expenditure Investment Total activity Total effort = Staff Related Expend Operating Expenditure Investment TOTAL Final 1.00 Page 39 FAS-1000-PMP-1.00.doc

42 7.2 ANNEX B: FASTI Schedule and Main Deliverables Final 1.00 Page 40 FAS-1000-PMP-1.00.doc0

43 Final 1.00 Page 41 FAS-1000-PMP-1.00.doc

44 Final 1.00 Page 42 FAS-1000-PMP-1.00.doc0

45 Final 1.00 Page 43 FAS-1000-PMP-1.00.doc