the adq adventures of lfv
DESCRIPTION
The ADQ Adventures of LFV. by Roger Li, Group Manager AIM 28th of May, Brussels. Agenda. Yesterday Today Tomorrow …and the challenges along the way. Background – up until 2009. - PowerPoint PPT PresentationTRANSCRIPT
The ADQ Adventures of LFV
byRoger Li, Group Manager AIM
28th of May, Brussels
28 May 2013
Agenda
YesterdayTodayTomorrow…and the challenges along the way
2
28 May 2013
Background – up until 2009
Low involvement from LFV in the work with drafting, reviewing and commenting the preparatory ADQ IR work due to resource constraints within the LFV AIM domain.…leading to lower awareness about ADQ IR and its impacts within LFV AIM than what could be expected.
3
28 May 2013
Background – 2010
With the actual release of the ADQ IR (73/2010) LFV AIM becomes more aware of the impact it will have on LFV and other stakeholdersADQ awareness work within LFV (mainly towards management) led by LFV AIM is initiated but the outcome of this work is rather scarce – message received but probably not understood to the full extent.No additional funding to really start preparing for ADQ
Available funding in 2010 for ADQ preparation and implementation(in % of expected total cost)
0 % 100 %
4
28 May 2013
Background – 2011
Awareness work continues within LFV (mainly towards management) led by LFV AIM but still the outcome of this work is poorADQ awareness meeting led by LFV AIM with the major airport owner Still no additional funding to really start preparing for ADQ
Available funding in 2011 for ADQ preparation and implementation(in % of expected total cost)
0 % 100 %
5
28 May 2013
Background – Q1-Q2 2012
Finally(!) LFV internal awareness work pays off and an understanding about a possible major impact on AIS operations is now on all levelsA pre-study is initiated (and funded) to:
Analyse and interpret the ADQ IR to sort out ambiguities and questionsTo further detail/explain the requirements from an LFV perspectiveCreate LFV ADQ IR implementation planInvestigate possible partnerships/cooperations for the ADQ implementationA business case to describe possible future new businesses as a result of ADQ implementationEstimate a total cost for ADQ implementation
Available funding in 2012 for ADQ prep. and implementation(in % of expected total cost)
0 % 100 %
6
28 May 2013
Background – Q3-Q4 2012
The result of the pre-study’s business case and ADQ implementation cost estimate gives LFV management the hick-ups – potentially BIG investment neededQuestions arise regarding LFV’s designationfrom the state to perform AIS(AIS open for competition or not?)Uncertainties regarding the riskthat another company can get thedesignation to perform AIS in Swedenin near future hampers full funding decision
Available funding in 2012 for ADQ prep. and implementation(in % of expected total cost)
0 % 100 %
7
28 May 2013
Background – Q1 2013
Continued uncertainties regarding AIS designation open for competition hampers full funding decisionA smaller part of funding approved to continue planning activities but no investments…meanwhile time flies…
Available funding up until Q1 2013 for ADQ prep. and implementation(in % of expected total cost)
0 % 100 %
8
28 May 2013
Background – Q2 2013
LFV decision for full funding of the ADQ IR implementationThe show can begin!
Available funding for ADQ preparation and implementation(in % of expected total cost)
0 % 100 %
9
28 May 2013
Current status
Approximately 5 Full Time Equivalents (FTE) needed for ADQ implementation from now and coming years, dealing with:
Project managementService Level Agreements (SLA)AwarenessTrainingArchitecture and requirementsQuality and Safety Management (QMS/SMS)System adaption and verificationSafety and Security IAIP Production Expertise
…but these 5 FTE need to be distributed on a larger number of individuals, 10+ “core” and 10+ “ad hoc”
10
28 May 2013
Current status – completed activities
Funding – completedImplementation plan – completedIdentification of stakeholders/information owners/data originators – completed Initial Awareness – completedDefinition of initial web portal for AIP publication requests (NOTAM not included initially) – completed
11
28 May 2013
Current status – started activities
Assignment of personnel to work in the ADQ Implementation ProjectService Level Agreements with stakeholders/information owners/data originators (focus on major actors) – started and ongoingDevelopment of initial web portal for AIP publication requests – started and ongoingIdentification of training activities – started and ongoing Survey of possible system solutions
12
28 May 2013
Planned future activities 2013
Enterprise Architecture framework definitionCurrent system survey and documentationSystem requirement specificationsUpdates of QMS, processes and routines – step 1Continued awareness activitiesInitial TrainingSafety Case
LFV will fulfil the ADQ 1st of July 2013 requirementsby 1st of January 2014 according to current plan.
13
28 May 2013
Planned activities 2014 and beyond
Procurement of system solutions and /or updates(?)Updates of QMS, processes and routines – step 2Continued awareness activitiesTraining – step 2
LFV will fulfil the ADQ 1st of July 2014 requirements by 1st of July 2015 according to current plan.LFV will fulfil the ADQ 1st of July 2017 requirements in timeaccording to current plan.
14
28 May 2013
Main challenges, so far and upcoming
DesignationFundingInformation ownershipSLA level of detailObstaclesStaff involvement in parallel with “daily production”ADQ maturity in the aviation community.
How to ensure that all information triggered by a certain event gets updated. (e.g. VOR goes down (CNS provider), procedures affected (airport) – one event but different information owners, etc…)Dependency on other stakeholders progress (or lack thereof…)
Annotation of non-ADQ-compliant information in AIP and database
15
28 May 2013
Main challenges, so far and upcoming
Separation between regulating authority (who can also be an information owner/data originator) and AIS provider achieved in theory but not 100% in practice.
AIS still doing interpretations of regulatory text instead of just publishing what is provided from the regulator. Who’s the information owner? Who approves what…?
Clean up our system architecture
16
28 May 2013
Conclusion
If everything goes as planned we’ll be late…
17
28 May 2013
Thank you!
18
28 May 2013
Back-up slides
Information ownership identification
19