Email
Like
Liked ×
Save
Private Content
Embed
Loading embed code…
We have emailed the verification/download link to "".
Login to your email and click the link to download the file directly.

To request the link at a different email address, update it here. Close
Validation messages. Success message. Fail message.

Check your bulk/spam folders if you can't find our mail.
Loading

+ Follow

Sesar Atc Global Sesar Strategies

by SESAR Joint Undertaking

1,130 views

SESAR Strategies presented at ATC Global (Amsterdam)

Accessibility

View text version

Upload Details

Uploaded via SlideShare as Microsoft PowerPoint

Usage Rights

File a copyright complaint

1 Embed 4

http://www.slideshare.net

Statistics

Likes: 0
Downloads: 31
Comments: 0
Embed Views: 4
Views on SlideShare: 1,126
Total Views: 1,130

Ops concept pilots; Step1 – make use of flight management system capabilities to fly profiles constrained by time RNP and new procedures from ATC like point merge in the context data link usage of time parameters increased predictability in runway management and airport surface and gate management Step2 User defined trajectory from AOC and FMS is a core information input to ATC FDPS Wider usage of RNP and adapted ATC procedures Aircraft systems starts being an active information node of the ATM system Mil operations are seen as any other traffic with individual clearances all through their missions ASAS applications are becoming standard procedure in different phases of flight as determined by performance Step 3 AOC fully integrated into the ATM system and FMS procedures are standard in guiding individual traffic and traffic flows weather information are up to date and always available based on aircraft being a weather sensor noo de ATCO´s Step 1 - Initial extra workload in communication over datalink whilst for example planning tools and AMAN systems become smarter and household work shifts New procedures requires training and system upgrades different to the planned under the current paradigm FMS procedures are introduced and ASAS applications for some flight phases better predictability on TWR Runway operations and more links with ground airside operations Step2 Trajectories starts to be interchanged between air and ground FDPS giving a more accurate tracking with better planning and execution tools in and across centres continous training on new procedures and in some places together with pilots where procedures are interlinked new recruitment criterions are coming into place Remote towers in operations in low dense areas and some features find its way in to more dense tower operations ASAS applications becomes standard in certain environments CWP´s get more generic allowing for more precise validation training and more flexible to allow for better mobility and sharing of responsibilities of ATCO´s Network operations move closer to AOC/FOC planning of operations whilst traditional flow planning happens regionally and locally as a result of more accurate and up to date information Step3 Information systems are available giving upto date information with aircraft and pilots as nodes of the system Virtual centres although physically separate builds the case for FAB´s to develop
The technology developments in SESAR should deliver a capability which is directly derived from operational requirements and support the delivery of a performance benefit to the overall system. No technical developments should progress without a clear link to the capability it will deliver and the subsequent benefit (related to the KPAs). Maturity of technical developments must be matched to parallel operational developments in order to deliver benefit so coordinated packaging of ops and tech is vital. We need to adopt an evolutionary approach to the system developments, mapped to the storyboard steps, with the legacy system constraints being more significant in the first step, and moving towards a more Service Oriented Approach as we move through to step 3. The aim is to be ready to implement these systems, together with procedures in a way that will deliver.
The use of an Enterprise Architecture view of the European ATM system will provide a common reference for developments, which are linked as required to the operational elements to deliver the required services. New technologies will be deployable as part of a harmonised and interoperable technical architecture whilst providing scalable technical solutions that are cost-effective and can be enhanced to meet future needs through deployment of new applications . Interoperability is an important target of the SESAR system developments, but it should not be misunderstood as implying that we insist on exactly the same solutions to be applied everywhere when a more flexible approach to achieving interoperability could be adopted (on the basis of performance and interface definition). This approach will allow deployment of an adaptable and scalable solution to the ATM system, which can be equally applied across a wide range of airborne platforms, airspace users, airports and ANSPs (including the Military) and permit regional solutions in the framework of the overall target concept. There are of course areas where interoperability can only be achieved through the adoption of common standards at a global level. For example, the implementation of air-to-air exchanges to enable ASAS applications and collision avoidance safety-nets require global harmonisation of both the equipment and procedures to ensure the safe and efficient implementation of these concepts. System decomposition and design will also impact on interoperability and the level at which we apply standards (on both performance and interface). Regulatory responsibilities will still impose a level of system decomposition and standardisation. Effective use (and generation) of information, in the right place at the right time is at the heart of the SWIM concept which will support SESAR .
In this wider framework within the programme individual technical system projects will work. Technical development activities will be based on traceable requirements from ‘client’ operational projects and through the architectural service view. Development of new CNS technologies will aim to increase capability and reduce cost while providing the capabilities needed to enable the new concepts and to maximise airspace and airport efficiency. Intelligent use of existing technology, core technology developments from other industry sectors and where possible COTS components tailored into a configuration meeting the needs of aviation, including safety and security. Achieving verification of technical developments and supporting the integrated validation of technology and procedures is of utmost importance. Development of prototypes to support this is at the heart of system level projects. {leads into V&V slides that follow}

Sesar Atc Global Sesar Strategies Presentation Transcript

Roll out of the SESAR Strategies Michael Standar SESAR FORUM 9 th March 2010
SESAR Strategies
- Operational
- System
- Validation and Verification
- Conclusions
Concept 1 / 2
- Designing to Performance
- Operationally Enabling a Service Approach
- Incremental Design - Story Board Steps
- Time Based Operations (Service level 2)
- Trajectory based Operations (Service Level 3)
- Performance Based Operations (Service Level 4)
Concept 2 / 2
- SESAR Road Map
- Clear identification of dependencies
- Clarity on ATM Partners transition path
- No “one-size-fits- all”
System 1 / 3
- Needs and Requirements:
- Systems requirements driven by Service Approach and defined needs.
- Incremental view of necessary system changes based on each Story Board Step.
- SESAR Road Map approach
System 2 / 3
- The Approach and Solution:
- A Single European Architecture as the reference for system developments.
- Traceability from technical system developments to the delivery of tangible benefits.
- Interoperability achieved through performance and interface requirements.
- Standardisation where needed.
- Scalability and flexibility in the approach to meet local needs (complexity and specificity).
- Information is “key”
System 3 / 3
- Programme and project responsibilities:
- Specific system projects build to requirements and verify developments
- Intelligent use of existing technology combined with new developments.
- Provision of prototypes must support validation through operational projects.
- Consolidation projects take system-level view to ensure consistency within the specific domain and support the technical architecture in WP B.
Validation & Verification 1 / 2
Validation &Verification 2 / 2
- Keys to Successful Validation and Verification:
Summary
- Performance Based
- Incremental View - Story Board Steps
- SESAR Road Map - Value Added Packages
- Single European Architecture Reference
- System Interoperability, Scalability, Flexibility
- Built to requirements & verified
- Maturity: iterative prototyping to trials cycles
- Validation close to deployment
- Working Together

Sesar Atc Global Sesar Strategies

by SESAR Joint Undertaking

Accessibility

Upload Details

Usage Rights

1 Embed 4

Statistics

Sesar Atc Global Sesar Strategies Presentation Transcript

Let LinkedIn power your SlideShare experience

Let LinkedIn power your SlideShare experience

Customize SlideShare content based on your interests

Keep up to date when your LinkedIn contacts post on SlideShare