ARTAS ROADMAP STRATEGY · Edition Nº Effective date or status Author(s) Reason 1.00 08/01/2007 R....

FOUNDINGMEMBER

NETWORKMANAGERSUPPORTING EUROPEAN AVIATION

EUROCONTROL

ARTAS Roadmap StrategyATM Surveillance Tracker & ServerEdition Number: 11.00 – 16/12/2019

ARTAS-MGT-STR-01 ARTAS ROADMAP STRATEGY

Edition 11.00 of 35

Traffic Light Protocol (TLP1) Applicable Classification

Colour When should it be used?

RED

Highly sensitive, non-disclosable information. It is restricted exclusively to the persons actually participating in the information exchange and these persons must not disseminate the information outside of this exchange. Disclosure could lead to severe impacts on privacy, reputation or operations if misused.

AMBER

Sensitive information with limited disclosure. It is restricted to members of the information exchange and people within their organisations (whether direct employees, consultants, contractors or outsourced staff working for the organisation) who need to know in order to take action. Disclosure could lead to serious impacts on privacy, reputation or operations if misused.

GREEN

Normal business information. It may be shared with peers and partner organisations but it is not intended to be posted on the Web, published or broadcasted. It should state if it is copyright protected and, when applicable, sharing must comply with the copyright protection.

WHITE Public information. It is intended for public, unrestricted dissemination, publication, Web-posting or broadcasting. It should state if it is copyright protected or public domain and, when applicable, sharing must comply with the copyright protection.

1 Reference: www.first.org/tlp


Edition 11.00 of 35

Document Control Copyright notice

© 2019 The European Organisation for the Safety of Air Navigation (EUROCONTROL). This document is published by EUROCONTROL for information purposes. It may be copied in whole or in part, provided that EUROCONTROL is mentioned as the source and to the extent justified by the non-commercial use (not for sale). The information in this document may not be modified without the prior written permission from EUROCONTROL.

Document Approval

Name Position/Job Title Signature Antonio Principe

ARTAS Service Manager

Axel Werner

SRS SQS Manager

Marian Jancik

Acting ARTAS Safety & Security Expert

Distribution List Name Representing Jean Marc Duflot Surveillance Services Unit Manager Antonio Principe ARTAS Service Manager Axel Werner SRS SQS Manager ARTAS Stakeholders Stakeholders

Status, Audience and Accessibility

Status Intended for Accessible via Working Draft Internal Project Server Proposed Issue Stakeholders One Sky Team Issued General Public iCAMOS

Contact Point

Contact Person(s) Telephone Unit EUROCONTROL +32 2 729 3952 NMD/NS/SRS


Edition 11.00 of 35

Edition history

Edition Nº Effective date or status

Author(s) Reason

1.00 08/01/2007 R. Dale Creation and Issue of ARTAS Baseline Policy 2.00 07/01/2013 D. Morton Issued 3.00 23/07/2013 D. Morton Issued:

• Update to allow parameter default value modifications (CCB#45 decision - ATR1933-V8B1)

• EOD and EOD table moved to RD2 document, EMERGENCY ATR replaced by Blocking/High ATR.

4.00 05/11/2013 D. Morton Issued: • Amended Disclaimers (Section 7) and

Section 6.1.1 5.00 13/01/2014 D. Morton Issued:

• Integration of Comsoft’s comments and ATR/ACP support when a new PS is released (Section 6.2).

• Clarification (AUG-48-A-2) on the CAMOS support for old Patch Set when a new one is released.

6.00 01/04/2014 D. Morton Issued: • Amend Patch is a patch. The values in the

ARTAS Database are considered like any other ARTAS parameters. Users are responsible for their tuning.

7.00 24/02/2015 D. Morton Issued: • New naming convention, including the

UPDATE concept. • Document renamed

8.00 18/06/2015 D. Morton Issued: • Clarification on limited support period • AUG#53 approval (changed Section

4.8.3 “initial duration is of 6 months) 9.00 16/03/2018 Eurocontrol Issued:

• Added Check Point, Blocking High ATR Process between two UPDATEs and strategy for ASTERIX modifications.

• Added Emergency Patches, Check Point and Release Candidate

• Added Classes of ARTAS Functionalities and the related CAMOS support

• Changes for the Web publication 10.00 17/05/2019 Eurocontrol Issued:

• Introduction of V9.X.Y naming convention. • Approved by AUG (action AUG-64-A-2).

11.00 15/12/2019 Eurocontrol Issued: • Revisited ASTERIX Policy • Approved by AUG#66 (Correspondance)


Edition 11.00 of 35

Table of Contents

1 INTRODUCTION ...............................................................................................................................9

2 DOCUMENTATION ....................................................................................................................... 10

2.1 APPLICABLE DOCUMENTS ....................................................................................................... 10 2.2 REFERENCE DOCUMENTS ....................................................................................................... 10

3 AUDIENCE..................................................................................................................................... 10

4 DEFINITIONS ................................................................................................................................ 11

4.1 ATR & ACP ........................................................................................................................... 13 Artas Trouble Report (ATR) .............................................................................................. 13 Artas Change Proposal (ACP) .......................................................................................... 13

4.2 ARTAS VERSION ................................................................................................................ 13 ARTAS VERSION foundation date ................................................................................... 13 ARTAS VERSION end of development date..................................................................... 13 ARTAS VERSION end of support date ............................................................................. 13 ARTAS VERSION naming convention .............................................................................. 13 Drivers for creating an ARTAS VERSION ......................................................................... 14

4.3 ARTAS RELEASE ................................................................................................................ 15 ARTAS RELEASE naming convention .............................................................................. 15 ARTAS RELEASE disclaimer ............................................................................................ 16

4.4 ARTAS UPDATE .................................................................................................................. 16 ARTAS UPDATE naming convention ................................................................................ 16 APPLICABLE as from ARTAS V9 ..................................................................................... 16 ARTAS UPDATE disclaimer .............................................................................................. 17

4.5 ARTAS EMERGENCY PATCH ............................................................................................ 17 ARTAS EMERGENCY PATCH naming convention .......................................................... 17 ARTAS EMERGENCY PATCH disclaimer ........................................................................ 17

4.6 ARTAS VERIFICATION ACTIVITIES................................................................................... 18 ARTAS RELEASE FAT ..................................................................................................... 18 ARTAS HW FAT ................................................................................................................ 18 ARTAS UPDATE VERIFICATION PROCESS .................................................................. 18

4.7 SOLUTIONS ........................................................................................................................ 18 ARTAS SOFTWARE SOLUTION ...................................................................................... 18 ARTAS HARDWARE SOLUTION ..................................................................................... 18 ARTAS SOLUTION ........................................................................................................... 18 USER SOLUTION ............................................................................................................. 19

4.8 CAMOS SUPPORT .............................................................................................................. 19 CAMOS SUPPORT for ARTAS SOLUTION ..................................................................... 19 CAMOS SUPPORT for USER SOLUTION ....................................................................... 20

4.9 UNVERIFIED ARTEFACTS ................................................................................................. 20 Unverified patch ................................................................................................................. 20 Check point (CP) ............................................................................................................... 20 Release candidate (RC) .................................................................................................... 20

4.10 CLASSES OF ARTAS FUNCTIONALITIES & CAMOS SUPPORT ..................................... 21 Fully supported .............................................................................................................. 21 Partially supported ......................................................................................................... 22 Not supported ................................................................................................................ 22

5 ARTAS VERSIONS STRATEGY .................................................................................................. 23

5.1 LIFECYCLE OF ARTAS VERSIONS .............................................................................................. 23 Impact of a new artas version on the lifecycle of the existing one .................................... 24 ARTAS VERSION & camos support ................................................................................. 26

5.2 LIFECYCLE OF ARTAS RELEASES ....................................................................................... 27 ARTAS RELEASE & camos support ................................................................................. 28 ARTAS RELEASE FAT ..................................................................................................... 28

5.3 LIFECYCLE OF ARTAS UPDATES ......................................................................................... 28 ARTAS UPDATE & camos support ................................................................................... 29

5.4 ACP POLICY .......................................................................................................................... 31 5.5 DOCUMENTATION POLICY ........................................................................................................ 31


Edition 11.00 of 35

5.6 ARTAS DEFAULT PARAMETERS VALUES POLICY ....................................................................... 31 ARTAS PARAMETERS DISCLAIMER .............................................................................. 31

5.7 ASTERIX POLICY ................................................................................................................... 32 ATR to Accept latest edItion frames .................................................................................. 32 ATR to process amended information ............................................................................... 32 ACP to process new information ....................................................................................... 32

5.8 ARTAS HARDWARE SOLUTIONS OF ARTAS RELEASE ................................................... 32 ANNEX A ABBREVIATIONS ......................................................................................................... 35

List of Figures

Figure 1 Check Points and Release Candidates ................................................................................... 21 Figure 2 Lifecycle of an ARTAS VERSION ........................................................................................... 24 Figure 3 Lifecycle of two ARTAS VERSIONs (case 1) .......................................................................... 25 Figure 4 Lifecycle of two ARTAS VERSIONs (case 2) .......................................................................... 26 Figure 5 CAMOS Support for an ARTAS VERSION ............................................................................. 27 Figure 6 Lifecycle ARTAS RELEASEs .................................................................................................. 28 Figure 7 Lifecycle ARTAS UPDATEs .................................................................................................... 29 Figure 8 ARTAS Emergency Patches for ARTAS UPDATEs ............................................................... 30 Figure 9 ARTAS HARDWARE SOLUTIONs ......................................................................................... 33

List of Tables

Table 1 Abbreviations ........................................................................................................................ 35


Edition 11.00 of 35

INTENTIONALLY LEFT BLANK


Edition 11.00 of 35

1 INTRODUCTION

The aim of this document is to define:

• the ARTAS Roadmap Strategy

• the ARTAS Artefacts

• the CAMOS Support

• the classes of ARTAS Functionalities and the CAMOS Support associated with them All new approved ARTAS policies and/or definitions will be described in this document once presented and approved by the ARTAS Users Group (AUG). The latest edition of the ARTAS Roadmap Strategy will always be available at the following address:

https://ost.eurocontrol.int/sites/SRSPR/ARTAS/User%20Docs/REFERENCED%20DOCUMENTS/ARTAS-MGT-STR-01%20ARTAS%20ROADMAP%20STRATEGY.pdf

This document supersedes the ARTAS Version and Baseline Policy (ref. ARTAS-MGT-POL-01 V6.0).




Edition 11.00 of 35

2 DOCUMENTATION

2.1 APPLICABLE DOCUMENTS

[ADx] Reference / Edition Title

None

2.2 REFERENCE DOCUMENTS

[RDn] Reference / Edition Title

[RD1] CAMOS-SLA-RULES Rules of Application for the CAMOS Service Level Agreement

[RD2] ARTAS-MGT-STR-02 ARTAS Roadmap Strategy Appendix

[RD3] CAMOS-WA-01 CAMOS Working Arrangements

[RD4] ARTAS-RN ARTAS Release Notes

3 AUDIENCE

This document is intended for the ARTAS Users, CAMOS and its Industrial Partner2 (IP).

2 The CAMOS Industrial Partner is defined as the Company or Consortium of Companies in charge of the support and maintenance of ARTAS.


Edition 11.00 of 35

4 DEFINITIONS

The following definitions shall apply throughout this document. 1. ATR & ACP [4.1]

a) ARTAS TROUBLE REPORT (ATR) [4.1.1] b) ARTAS CHANGE PROPOSAL (ACP) [4.1.2]

2. ARTAS VERSION [4.2] a) ARTAS VERSION FOUNDATION DATE [4.2.1] b) ARTAS VERSION END OF DEVELOPMENT DATE [4.2.2] c) ARTAS VERSION END OF SUPPORT DATE [4.2.3] d) ARTAS VERSION NAMING CONVENTION [4.2.4] e) DRIVERS FOR CREATING A VERSION [4.2.5]

3. ARTAS RELEASE [4.3] a) ARTAS RELEASE NAMING CONVENTION [4.3.1] b) ARTAS RELEASE DISCLAIMER [4.3.2]

4. ARTAS UPDATE [4.4] a) ARTAS UPDATE NAMING CONVENTION [4.4.1] b) ARTAS UPDATE DISCLAIMER [4.4.3]

5. ARTAS EMERGENCY PATCH [4.5] a) ARTAS EMERGENCY PATCH NAMING CONVENTION [4.5.2] b) ARTAS EMERGENCY PATCH DISCLAIMER [4.5.2]

6. ARTAS VERIFICATION ACTIVITIES [4.6] a) ARTAS RELEASE FAT [4.6.1] b) ARTAS HW FAT [4.6.2] c) ARTAS UPDATE VERIFICATION PROCESS [4.6.3]

7. SOLUTIONS [4.7] a) ARTAS SOFTWARE SOLUTION [4.7.1] b) ARTAS HARDWARE SOLUTION [4.7.2] c) ARTAS SOLUTION [4.7.3] d) USER SOLUTION [4.7.4]

8. CAMOS SUPPORT FOR ARTAS SOLUTION [4.8.1] a) FULL SUPPORT [4.8.1.1] b) LIMITED SUPPORT [4.8.1.2] c) LIMITED SUPPORT PERIOD [4.8.1.3] d) NO SUPPORT [4.8.1.4]

9. CAMOS SUPPORT FOR USER SOLUTION [4.8.2]


Edition 11.00 of 35

10. UNVERIFIED ARTEFACTS [4.9] a) UNVERIFIED PATCH [4.9.1] b) CHECK POINT (CP) [4.9.2] c) RELEASE CANDIDATE (RC) [4.9.3]

11. CLASSES OF ARTAS FUNCTIONALITIES & CAMOS SUPPORT [4.10] a) FULLY SUPPORTED [4.10.1] b) PARTIALLY SUPPORTED [4.10.2] c) NOT SUPPORTED [4.10.3]


Edition 11.00 of 35

4.1 ATR & ACP

ARTAS TROUBLE REPORT (ATR) An ARTAS Trouble Report identifies a bug (e.g. error, flaw, failure or fault) which violates the ARTAS Specification or an error in the ARTAS specifications (Doc ATR).

ARTAS CHANGE PROPOSAL (ACP) An ARTAS Change Proposal is a request to add, modify or remove System functionality (e.g. increase the ARTAS capacities, new sensor type, etc.), which involves changes to the ARTAS Specification (e.g. design change, new requirements, etc.).

4.2 ARTAS VERSION

The expression ”ARTAS VERSION” is used to define the ARTAS Roadmap through three major event dates:

ARTAS VERSION FOUNDATION DATE The Foundation Date (FD) defines the start date after which CAMOS provides Full Support and when the ARTAS Community is informed of the availability of the new ARTAS VERSION.

ARTAS VERSION END OF DEVELOPMENT DATE The End of Development (EOD) defines the date after which CAMOS only provides Limited Support for an ARTAS VERSION.

ARTAS VERSION END OF SUPPORT DATE The End of Support (EOS) defines the date3 after which CAMOS provides no support for an ARTAS VERSION. Note: The current ARTAS VERSIONS and their EOD and EOS are available in [RD2]

ARTAS VERSION NAMING CONVENTION 4.2.4.1 APPLICABLE UP TO ARTAS V8B4-U2 An ARTAS VERSION will be named using 3 characters, represented by VYX

V= [V] Fixed Letter The name of each ARTAS VERSION starts with a character “V“, meaning “Version”.

Y= [digit] Major Modification

The second character “Y“ is a number indicating a major modification to the ARTAS VERSION, such as the addition of major functionality related to the main ARTAS CSCIs, namely TRK, SRS and RBR.

X= [A/B] Fixed Letter

3 After that date, CAMOS will decommission the ARTAS VERSION and the ARTAS HARDWARE SOLUTIONs and therefore will not have any means of providing any sort of support for the ARTAS VERSION.

http://en.wikipedia.org/wiki/Failure

http://en.wikipedia.org/wiki/Fault_(technology)


Edition 11.00 of 35

For the third character “X“, the letter “A” is used to indicate the 2 x 5 server solution and the letter “B” to indicate the 2 x 1 server solution. Example: ARTAS V8B 4.2.4.2 APPLICABLE AS FROM ARTAS V9 An ARTAS VERSION will be named using 2 fields, represented by VY

V= [V] Fixed Letter The name of each ARTAS VERSION starts with a character “V“, meaning “Version”.

Y= [one or two digits] Major Modification Example: ARTAS V9 or V10

DRIVERS FOR CREATING AN ARTAS VERSION A new ARTAS VERSION could be created with the introduction of major functionality impacting the main ARTAS CSCIs, namely RBR, TRK, SRV or MMS. In this case, and/or whenever deemed necessary, CAMOS and its IP will propose to the AUG/CCB forum, for approval, the creation of an ARTAS VERSION.


Edition 11.00 of 35

4.3 ARTAS RELEASE

An ARTAS RELEASE represents a formal delivery for an ARTAS VERSION made of executable software that implements both ACPs and ATRs together with the full set of ARTAS documentation. An ARTAS RELEASE is verified during a Factory Acceptance Test (FAT) and is then approved by the ARTAS community during an AUG/CCB meeting. The following list describes the possible enhancements that can form part of the ARTAS RELEASE:

o The implementation of a set of ACPs o The integration and consolidation of all ATRs solved since the previous ARTAS

RELEASE o The adoption of a new O.S. o The integration of a new release of the Middleware o The integration of a new release of COTS/OTS o The integration of a new release of libraries

The following list describes ARTAS deliverables related to the ARTAS RELEASE: o The ARTAS system o The full ARTAS set of documentation o Quality and Safety evidence o SWAL3 Safety Folder o Declaration of Suitability of Use

ARTAS RELEASE NAMING CONVENTION 4.3.1.1 APPLICABLE UP TO ARTAS V8B4-U2 For the ARTAS RELEASE, the following naming convention applies:

<ARTAS VERSION><ARTAS RELEASE-id> where RELEASE-id is a digit representing the release number of the ARTAS VERSION. Note: When the first ARTAS RELEASE of an ARTAS VERSION is issued (i.e. at the Foundation Date), its name is <ARTAS VERSION>0 Example: V8B0, V8B1, V8B2, etc. are the names of the first, second and third RELEASES of ARTAS VERSION V8B. 4.3.1.2 APPLICABLE AS FROM ARTAS V9 For the ARTAS RELEASE, the following naming convention applies:

<ARTAS VERSION>.<ARTAS RELEASE-id> where RELEASE-id is a digit representing the release number of the ARTAS VERSION. Note: When the first ARTAS RELEASE of an ARTAS VERSION is issued (i.e. at the Foundation Date), its name is <ARTAS VERSION>.<ARTAS RELEASE-id>.0


Edition 11.00 of 35

Example: V9.0.0, V9.1.0 V9.2.0, etc. are the names of the first, second and third RELEASES of ARTAS VERSION V9.

ARTAS RELEASE DISCLAIMER ARTAS Users are solely responsible for the validation of the ARTAS RELEASE in their own operational environment. ARTAS Users undertake to deploy the ARTAS RELEASE under their full responsibility. EUROCONTROL shall therefore under no circumstances be liable for any loss, expense, damage or problems of any kind arising from the use of the ARTAS RELEASE.

4.4 ARTAS UPDATE

An ARTAS UPDATE consolidates and delivers a bundle of executable software and a subset of documentation updates (related to its ATR and ACP content) for an ARTAS RELEASE. An ARTAS UPDATE undergoes a set of regression tests executed, at various levels, by both CAMOS and its Industrial Partner, but does not undergo a FAT and is then approved by the ARTAS community during an AUG/CCB meeting. ARTAS UPDATEs are delivered to the ARTAS Users during the Support (Full + Limited) period of the corresponding ARTAS RELEASE. The following list describes the possible enhancements that can form part of the ARTAS UPDATE:

o The implementation of a few ACPs o The implementation of ATRs

The following list describes ARTAS deliverables related to the ARTAS UPDATE: o A subset of the executable software of the ARTAS system o A subset of the parameter configuration files of the ARTAS system o A subset of the ARTAS documentation o Quality and Safety evidence for the implemented ATRs/ACPs

ARTAS UPDATE NAMING CONVENTION 4.4.1.1 APPLICABLE UP TO ARTAS V8B4-U2 For the ARTAS UPDATE, the following naming convention applies:

<ARTAS RELEASE>-U<UPDATE-id> where UPDATE-id is a digit representing the update number of an ARTAS RELEASE preceded by the letter “U” Example: V8B4-U2 is the second UPDATE of ARTAS V8B4.

APPLICABLE as from ARTAS V9 For the ARTAS UPDATE, the following naming convention applies:

<ARTAS RELEASE>.<UPDATE-id> where UPDATE-id is a digit representing the update number of an ARTAS RELEASE.


Edition 11.00 of 35

Example: V9.0.2 is the second UPDATE of ARTAS V9.0.0.

ARTAS UPDATE DISCLAIMER ARTAS Users are solely responsible for the validation of the ARTAS UPDATE in their own operational environment. ARTAS Users undertake to deploy the ARTAS UPDATE under their full responsibility. Therefore EUROCONTROL shall under no circumstances be liable for any loss, expense, damage or problems of any kind arising from the use of the ARTAS UPDATE.

4.5 ARTAS EMERGENCY PATCH

Once an ARTAS UPDATE is released, CAMOS provides fixes on top of the UPDATE only for BLOCKING and SAFETY/CRITICAL ATRs. In such cases, the originator is responsible for the verification and validation of the fixes. When the fix for the ATR is approved by the Originator, it can be used by other ARTAS Users whose system might also be impacted, provided that the final user verifies and validates it before its operational deployment. To optimise CAMOS resources, fixes for a set of ATRs are bundled together in the so-called ARTAS EMERGENCY PATCH (EP). Once verified, the EPs are made available to the ARTAS community as described in [RD3]. Furthermore, the fixes described above will be integrated into the next UPDATE and, at that time, fully verified by CAMOS and its IP. EMERGENCY PATCHES are cumulative.

ARTAS EMERGENCY PATCH NAMING CONVENTION 4.5.1.1 APPLICABLE AS FROM ARTAS V9 For the EMERGENCY PATCH of any ARTAS VERSION RELEASE UPDATE, the following naming convention applies:

<ARTAS VERSION RELEASE UPDATE>.<EP-id> where EP-id is a number representing the emergency patch number of the ARTAS UPDATE. Example: V9.0.2.3 is the third Emergency Patch of ARTAS V9.0.2.

ARTAS EMERGENCY PATCH DISCLAIMER ARTAS Users are solely responsible for the verification and validation of the ARTAS EMERGENCY PATCH of an ARTAS UPDATE in their own operational environment. ARTAS Users undertake to deploy the ARTAS EMERGENCY PATCH under their full responsibility. EUROCONTROL shall therefore under no circumstances be liable for any loss, expense, damage or problem of any kind arising from the use of the ARTAS EMERGENCY PATCH.


Edition 11.00 of 35

4.6 ARTAS VERIFICATION ACTIVITIES

ARTAS RELEASE FAT A Factory Acceptance Test (FAT) is conducted on a complete and integrated system in order to verify the system's compliance with the specified system requirements. Testing establishes that the functions are fulfilling their intended requirements and that any modifications made have not resulted in an unacceptable regression to the existing functional performance. A set of FAT documentation is prepared to support the FAT activity as indicated in the FAT Plan (FATP).

ARTAS HW FAT A Hardware FAT is a FAT conducted on a complete and integrated ARTAS RELEASE and or ARTAS UPDATE, mainly to validate an additional ARTAS HARDWARE SOLUTION for a specific ARTAS RELEASE and/or ARTAS UPDATE. In the context of HW FAT, a few ATRs and/or ACPs (e.g. new O.S. to support the new hardware solution) could be integrated. Although reduced testing is carried out (compared to the magnitude of tests of an ARTAS VERSION RELEASE FAT), evidence is provided that the new hardware and limited modifications are fulfilling their intended requirements and that such modifications have not resulted in an unacceptable regression to the existing functional performance.

ARTAS UPDATE VERIFICATION PROCESS The ARTAS UPDATEs undergo to a verification process which is conducted on a complete and integrated system in order to verify the system's compliance with the specified system requirements. Testing establishes that the functions are fulfilling their intended requirements and that any modifications made have not resulted in an unacceptable regression to the existing functional performance. A set of documentation is prepared to support the UPDATE verification activity as indicated in the UPDATE Test Plan (UTP).

4.7 SOLUTIONS

ARTAS SOFTWARE SOLUTION The ARTAS SOFTWARE SOLUTION (SS) of an ARTAS RELEASE or an ARTAS UPDATE is the set of software (i.e. O.S. and CSCIs) making ARTAS and identified in the Release Notes.

ARTAS HARDWARE SOLUTION The ARTAS HARDWARE SOLUTION (HS) of an ARTAS RELEASE or an ARTAS UPDATE is a hardware (i.e. a server/computer) supporting ARTAS execution and identified in the Release Notes.

ARTAS SOLUTION


Edition 11.00 of 35

The ARTAS SOLUTION (AS) is combination of an ARTAS SOFTWARE SOLUTION and one of its ARTAS HARDWARE SOLUTIONs.

USER SOLUTION The USER SOLUTION (US) is a solution derived from an ARTAS SOLUTION but where some changes (e.g. additional software, modification to the provided software, different hardware, different Operative System, different O.S. configuration, virtualisation) are applied by the user.

4.8 CAMOS SUPPORT

CAMOS SUPPORT FOR ARTAS SOLUTION 4.8.1.1 FULL SUPPORT With Full Support, CAMOS provides changes for:

• Accepted ATRs according to their priority

• ACPs agreed by the AUG Governance 4.8.1.2 LIMITED SUPPORT With Limited Support, CAMOS only provides changes for requests related to operational systems for:

• Blocking/High ATRs for which a work-around is not available

• Safety/Critical ACPs for which a work-around is not available. 4.8.1.3 LIMITED SUPPORT PERIOD The Limited Support Period is the period of time during which CAMOS provides LIMITED SUPPORT for an ARTAS RELEASE (e.g. RLn). The Limited Support Period starts on the date when CAMOS announces the availability of a new ARTAS RELEASE (RLn+1) to the ARTAS Community, and its initial duration is at least 6 months.

a) During the Limited Support Period, the ARTAS Users shall verify the new ARTAS RELEASE (RLn+1)

b) At the end of the Limited Support Period, if no blocking issue exists, the Limited Support Period for the ARTAS RELEASE (RLn) is terminated.

c) At the end of the Limited Support Period, if blocking issues are still unresolved, the Limited Support Period for the ARTAS RELEASE (RLn) is extended for an additional period of 3 months (and the process restarts from point a)).

4.8.1.4 NO SUPPORT With NO SUPPORT, CAMOS processes requests for trouble reports in line with the following procedure:

a. The ATR is submitted on an ARTAS VERSION (e.g. Vy) after its EOS. In this case, CAMOS checks whether the problem is affecting the most recent ARTAS UPDATE (e.g. UPm of RLn+2) of the most recent ARTAS VERSION (e.g. Vy+2) and, if


Edition 11.00 of 35

needed, provides a fix for the ATR only on top of it (i.e. on top of the most recent ARTAS UPDATE of the most recent ARTAS VERSION).

b. The ATR is submitted on an ARTAS RELEASE (e.g. RLn) when its LIMITED SUPPORT PERIOD is terminated. In this case, CAMOS checks whether the problem is affecting the most recent ARTAS UPDATE (e.g. UPm) of the most recent ARTAS RELEASE (e.g. RLn+2) of the same ARTAS VERSION and, if needed, provides a fix for the ATR only on top of it (i.e. on top of the most recent ARTAS UPDATE of the most recent ARTAS RELEASE of the same ARTAS VERSION e.g. on top of UPm of RLn+2).

c. The ATR is submitted on an ARTAS UPDATE (UPm) when, as a minimum, the ARTAS UPDATE (UPm+1) is released. In this case, CAMOS checks whether the problem is affecting the most recent ARTAS UPDATE (e.g. UPm+3) of the same ARTAS RELEASE (e.g. RLn) and, if needed, provides a fix for the ATR only on top of it (i.e. on top of the most recent ARTAS UPDATE of the same ARTAS RELEASE, e.g. on top of UPm+3 of RLn).

CAMOS SUPPORT FOR USER SOLUTION When a user adopts a USER SOLUTION, they shall declare to CAMOS the referenced ARTAS SOLUTION and indicate the applied changes both at SW and HW level. For the USER SOLUTION, CAMOS provides:

• The same level of Support as for the ARTAS SOLUTION for problems which are reproducible on the referenced ARTAS SOLUTION.

• Limited Help (e.g. suggestions concerning configuration adaptations, different procedural steps, general advice on possible solutions for the problem) for problems which are not reproducible on the referenced ARTAS SOLUTION.

4.9 UNVERIFIED ARTEFACTS

UNVERIFIED PATCH A subset of the executable software of the ARTAS System which fixes the bugs described in an ATR (or addresses a request for changes in an ACP) that has not yet been verified (i.e. tested, approved and released) by CAMOS is called an Unverified Patch.

CHECK POINT (CP) A set of executable software for the full ARTAS System, made available by CAMOS prior to an official release, is called a CHECK POINT (CP). As such, a CHECK POINT is not verified (i.e. tested, approved and released) by CAMOS. CHECK POINTS are made available to the ARTAS Users only to allow them to execute an earlier evaluation of a new ARTAS VERSION RELEASE and to report any identified issues. Figure 1 below shows the concept of a CP for an ARTAS VERSION RELEASE.

RELEASE CANDIDATE (RC) A RELEASE CANDIDATE (RC) is a CHECK POINT related to the image of the software at the time of the FAT activities (i.e. pre-FAT, FAT and post-FAT).


Edition 11.00 of 35

RELEASE CANDIDATES are made available to the ARTAS User only to allow them to execute an earlier evaluation of a new ARTAS VERSION RELEASE and to report any identified issues. Figure 1 below shows the concept of an RC for an ARTAS VERSION RELEASE.

Figure 1 Check Points and Release Candidates

4.10 CLASSES OF ARTAS FUNCTIONALITIES & CAMOS SUPPORT

The following section describes the classes of ARTAS Functionalities. For each of these classes, the associated CAMOS Support and CAMOS recommendations or suggestions for the ARTAS Users are shown. This characterisation of classes of ARTAS Functionalities is intended to minimise any ambiguities in terms of the ARTAS Specification, Users’ expectations and CAMOS support. Hereafter the ARTAS functionalities are divided into the following three classes:

1. FULLY SUPPORTED 2. PARTIALLY SUPPORTED 3. NOT SUPPORTED

FULLY SUPPORTED All ARTAS functionalities belong to this class, except for those listed in 4.10.2 or 4.10.3.


Edition 11.00 of 35

The class could be divided into two subclasses: 1. NOMINAL CAPACITY

This subclass groups all functionalities except for the ‘To Be Validated’ functionalities of the FULLY SUPPORTED class.

2. TO BE VALIDATED This subclass groups new functionalities introduced with complex ACPs and those functionalities with no or limited operational feedback. Users planning to use these functionalities are recommended to undergo a wider verification and validation phase prior to deploying their ARTAS system operationally.

CAMOS provides FULL SUPPORT, as described in 4.8.1.1, for these functionalities. The list of these functionalities is in the applicable ARTAS Release Notes ([RD4]).

PARTIALLY SUPPORTED The functionalities of this class are divided into the following two subclasses:

1. DEPRECATED This subclass refers to all ARTAS functionalities which CAMOS and the AUG have agreed to decommission and which are therefore subject to no further improvements. Example: The functionalities related to ASTERIX CAT 030 are deprecated in V8B4. Users of Deprecated functionality are advised to plan the replacement of such functionalities prior to their removal from ARTAS.

2. NON-NOMINAL CAPACITY This subclass refers to ARTAS functionalities when used above their nominal capacity. The nominal capacity of the ARTAS system is tested during Factory Acceptance Tests; however, the system behaviour depends on so many other factors (i.e. HW, sensor/service environment, tuning) that CAMOS cannot ensure that similar results are achievable in all possible environments. Users planning to use ARTAS in a configuration that goes beyond its nominal capacity (as identified in ARTAS Release Notes - [RD4]) are advised to plan a wider verification and validation phase prior to deploying ARTAS operationally.

CAMOS provides only LIMITED SUPPORT, as described in 4.8.1.2, for ATRs and NO SUPPORT, as described in 4.8.1.4, for ACPs related to the functionalities of this class. The list of these functionalities is in the applicable ARTAS Release Notes ([RD4]).

NOT SUPPORTED The functionalities of this class are divided into the following two subclasses:

1. TO BE REMOVED This subclass refers to all ARTAS functionalities that CAMOS and the AUG have decided to remove from ARTAS.

2. PENDING DECISION This subclass refers to the ARTAS functionalities that for some reason have not yet reached the appropriate level of maturity for operational use.


Edition 11.00 of 35

The functionalities stay in this class until CAMOS and the AUG decide whether to remove or finalise them. ARTAS users are not recommended to use any of the functionalities belonging to these subclasses with their operational systems.

CAMOS provides NO SUPPORT, as described in 4.8.1.4, for these functionalities. The list of these functionalities is in the applicable ARTAS Release Notes ([RD4]).

5 ARTAS VERSIONS STRATEGY

The following sections describe the strategy for the ARTAS VERSION as from V8B onwards.

5.1 LIFECYCLE OF ARTAS VERSIONS

At the time of the Foundation Date, CAMOS will announce the earliest EOD and EOS of an ARTAS VERSION at the AUG/CCB forum. The EOD of each ARTAS VERSION will be set no earlier than its Foundation Date + 4.5 years. The EOS date of any ARTAS VERSION is by default equal to the EOD date of the ARTAS VERSION + 2.5 years4. However, CAMOS might propose to postpone the EOD of an ARTAS VERSION in order to extend its life. When such an extension is deemed necessary and advantageous for the ARTAS community, CAMOS will propose it for approval during the AUG/CCB forum. Changes to the EOD date of an ARTAS VERSION shall be announced to the AUG/CCB forum at least 1 year before the ARTAS VERSION reaches the already agreed EOD. Figure 2 Lifecycle of an ARTAS VERSION presents the lifecycle of an ARTAS VERSION.

4 In the 2.5 years between the EOD and EOS dates, the users of the ARTAS VERSION are expected to migrate to a new ARTAS VERSION.


Edition 11.00 of 35

Figure 2 Lifecycle of an ARTAS VERSION

IMPACT OF A NEW ARTAS VERSION ON THE LIFECYCLE OF THE EXISTING ONE

The creation of a new ARTAS VERSION (ARTAS Vn+1) sets the EOD and EOS dates of the existing ARTAS VERSION (ARTAS Vn). Where the ARTAS Vn+1 is made available when the ARTAS Vn has already been available for more than 4.5 years (see points 1 and 2 in Figure 3 Lifecycle of two ARTAS VERSIONs (case 1)), the EOD and EOS dates of ARTAS Vn are:

• ARTAS Vn EOD date is set at the Foundation Date of ARTAS Vn+1

• ARTAS Vn EOS date is set at the Foundation Date of ARTAS Vn+1 + 2.5 years.


Edition 11.00 of 35

Figure 3 Lifecycle of two ARTAS VERSIONs (case 1)

Where the ARTAS Vn+1 is made available before ARTAS Vn has reached the minimum support of 4.5 years (see points 1 and 2 in Figure 4 Lifecycle of two ARTAS VERSIONs (case 2)), the EOD and EOS dates of ARTAS Vn remain unchanged:

• ARTAS Vn EOD date is set at the Foundation Date of ARTAS Vn + 4.5 years

• ARTAS Vn EOS date is set at the Foundation Date of ARTAS Vn + 2.5 years.


Edition 11.00 of 35

Figure 4 Lifecycle of two ARTAS VERSIONs (case 2)

ARTAS VERSION & CAMOS SUPPORT For an ARTAS VERSION, CAMOS provides:

• Full Support5 up to the EOD date

• Limited Support5 during the period between the EOD and EOS dates

• No Support after the EOS date (please refer to Figure 5 CAMOS Support for an ARTAS VERSION)

5 CAMOS SUPPORT for ARTAS RELEASEs and ARTAS UPDATEs should also be considered.


Edition 11.00 of 35

6∗Figure 5 CAMOS Support for an ARTAS VERSION

5.2 LIFECYCLE OF ARTAS RELEASES

The number of ARTAS RELEASEs (RL) of an ARTAS VERSION depends on the EOD date of the ARTAS VERSION. To minimise the number of changes to the operational sites and to achieve a sort of convergence for those sites, ARTAS RELEASEs are made available, on average, every 18/24 months (see Figure 6 Lifecycle ARTAS RELEASE).

∗Full Support for at least 4.5 years plus 2.5 years of Limited Support


Edition 11.00 of 35

Figure 6 Lifecycle ARTAS RELEASEs

ARTAS RELEASE & CAMOS SUPPORT For an ARTAS RELEASE (RLn), CAMOS provides:

• Full Support7 up to the date when CAMOS announces the availability of a new ARTAS RELEASE (RLn+1) to the ARTAS Community.

• Limited Support7 only for a Limited Support Period (see 4.8.1.3) from the date when CAMOS announces the availability of a new ARTAS RELEASE (RLn+1) to the ARTAS Community.

• No Support when the Limited Support Period is terminated.

ARTAS RELEASE FAT A FAT is executed for each ARTAS RELEASE of an ARTAS VERSION.

5.3 LIFECYCLE OF ARTAS UPDATES

The number of ARTAS UPDATE of an ARTAS RELEASE depends on the life cycle of the ARTAS RELEASE (18/24 months) and on the number, complexity and severity of the ATRs

7 CAMOS SUPPORT for ARTAS VERSION and ARTAS VERSION RELEASE UPDATEs to be considered too.


Edition 11.00 of 35

opened by the ARTAS Users over this period of time. On average, 3/4 of ARTAS UPDATEs are scheduled for an ARTAS RELEASE (see Figure 7 Lifecycle ARTAS UPDATE).

Figure 7 Lifecycle ARTAS UPDATEs

ARTAS UPDATE & CAMOS SUPPORT For an ARTAS UPDATE (UPn), CAMOS provides:

• Full Support8 up to the date when CAMOS announces the availability of a new ARTAS UPDATE (UPn+1) to the ARTAS Community.

• Limited Support8 only for a Limited Support Period (see 4.8.1.3) from the date when CAMOS announces the availability of a new ARTAS UPDATE (UPn+1) to the ARTAS Community.

• No Support when the Limited Support Period is terminated. In general, the CAMOS Full Support mentioned above provides fixes for ATRs/ACPs only on top of the latest ARTAS UPDATE in the form of ARTAS EMERGENCY PATCHES (4.5).

8 CAMOS SUPPORT for ARTAS VERSION and ARTAS RELEASE should also be considered.


Edition 11.00 of 35

Figure 8 ARTAS Emergency Patches for ARTAS UPDATEs


Edition 11.00 of 35

5.4 ACP POLICY

ACPs should be grouped and made available with an ARTAS RELEASE. The ARTAS Users Group and the Configuration Control Board define the list of ACPs that will form the bundle of ACPs of an ARTAS RELEASE. Whenever deemed necessary, ACP(s) can be delivered in an ARTAS UPDATE. In order to avoid jeopardising the stability of the behaviour of an existing ARTAS RELEASE (RLn) or ARTAS UPDATE (UPn), whenever feasible the ACPs implemented in a new ARTAS RELEASE (RLn+1) or ARTAS UPDATE (UPn+1) will be developed with a turn ON/OFF parameter (OFF by default).

5.5 DOCUMENTATION POLICY

A complete set of documentation will be produced and made available at each ARTAS RELEASE of an ARTAS VERSION (e.g. V9.0.0, V9.1.0, V10.0.0, etc.). A reduced set of only the updated documents will be produced and made available at each ARTAS UPDATE of an ARTAS RELEASE (e.g. V9.1.1, V10.0.2, etc.).

5.6 ARTAS DEFAULT PARAMETERS VALUES POLICY

In order to guarantee an optimum default configuration for ARTAS, CAMOS might modify the default values of selected ARTAS offline parameters with ARTAS RELEASEs. The optimum default configuration should reflect the most “advanced” operational configurations, minimise the tuning complexity and maximise the system reliability. An offline parameter default value may only be modified when the modification is expected to benefit most of the Users and when positive field experience is available for the new default value. To support and facilitate CAMOS activities and to share the benefits of the implemented tunings, ARTAS Users are asked to identify the expected benefits for changed parameters; this can be done through comments in the “site” folder parameter files or a presentation at CCB level.

ARTAS PARAMETERS DISCLAIMER ARTAS Users are solely responsible for the tuning activity (basic or fine) of the ARTAS parameters (including those defined in the ARTAS database/dataset). EUROCONTROL shall therefore under no circumstances be liable for any loss, expense, damage or problems of any kind arising from the use of the tuning activity of the ARTAS parameters. Furthermore, any problems identified during the tuning of the ARTAS parameters will be classified as low/medium priority.


Edition 11.00 of 35

5.7 ASTERIX POLICY

To keep ARTAS compatible with the latest approved ASTERIX editions, CAMOS proceeds according to the following approach for the operationally supported ASTERIX categories. The ATR and ACP used to keep ARTAS compatible with the latest approved ASTERIX editions (ref. 5.7.1, 5.7.2, 5.7.3) will be processed according to CAMOS resource availability and the priority defined by the AUG.

ATR TO ACCEPT LATEST EDITION FRAMES Whenever a new edition is approved by the ASTERIX Community, CAMOS will use an ATR for ARTAS to accept frames of the latest edition of the ASTERIX category. This ATR is not meant to process new and/or amended information.

ATR TO PROCESS AMENDED INFORMATION Whenever a new edition approved by the ASTERIX Community contains amended information that has an impact on an existing feature correctness, CAMOS will use an ATR for ARTAS to process the amended information and maintain the existing feature correctness. This ATR is not meant to process new information.

ACP TO PROCESS NEW INFORMATION Whenever a new edition approved by the ASTERIX Community contains new information, CAMOS will use an ACP for ARTAS to process the new information in order to extend ARTAS features.

5.8 ARTAS HARDWARE SOLUTIONS OF ARTAS RELEASE

Each ARTAS RELEASE is to be hosted on a hardware solution. CAMOS defines the ARTAS HARDWARE SOLUTIONs (HS) for running an ARTAS RELEASE. Any ARTAS RELEASE will have at least two ARTAS HARDWARE SOLUTIONs, namely HSi, and HSi+1. Whenever possible, in order to reduce the cost of frequent hardware changes, CAMOS will make use of the ARTAS HARDWARE SOLUTIONs of the existing ARTAS VERSION RELEASE with a new ARTAS RELEASE of the same ARTAS VERSION. Furthermore, additional ARTAS HARDWARE SOLUTIONs (namely HSi+2 and HSi+3) could be introduced with a new ARTAS RELEASE of the same ARTAS VERSION. In this case, the new ARTAS RELEASE will have 4 ARTAS HARDWARE SOLUTIONs (namely HSi, HSi+1, HSi+2 and HSi+3) (see Figure 9 ARTAS HARDWARE SOLUTION).


Edition 11.00 of 35

Figure 9 ARTAS HARDWARE SOLUTIONs


Edition 11.00 of 35

5.8.1.1 ARTAS HARDWARE SOLUTIONS VS ARTAS TESTS ATRs and ACPs are tested only on the most recent ARTAS HARDWARE SOLUTIONs of an ARTAS RELEASE. Users who want CAMOS and its IP to execute the test of a resolved ATR/ACP on a different ARTAS HARDWARE SOLUTION have to make the appropriate request when opening the ATR/ACP. During the FAT of an ARTAS RELEASE, ATRs and ACPs will be tested on the 2 most recent ARTAS HARDWARE SOLUTIONs. During the system test phase (of the FAT), the tests will be executed on the ARTAS HARDWARE SOLUTION HSj (HSj+1). The same test will be executed on the ARTAS HARDWARE SOLUTION HSj+1 (HSj) during the pre-FAT or FAT. Users may request CAMOS and its IP to adopt a different ARTAS HARDWARE SOLUTION during the FAT.


Edition 11.00 of 35

Annex A Abbreviations

The following abbreviations are used throughout the document.

ACP ARTAS Change Proposal ANSP Air Navigation Service Provider

ARTAS EUROCONTROL ATM SuRveillance Tracker And Server

ATR ARTAS Trouble Report AUG ARTAS User Group CCB Configuration Control Board COTS Commercial Off The Shelf.

CAMOS Centralised ARTAS Maintenance and Operational Support

CVS Concurrent Versions System DOC ARTAS documentation EC EUROCONTROL EOD End Of Development (EC) EOL End Of Life EOS End Of Support (EC) FAT Factory Acceptance Test HS ARTAS HARDWARE SOLUTION HW Hardware LAN Local Area Network NA National Administration(s) O.S. Operating System OL Oracle Linux OTS Off The Shelf SLA Service Level Agreement STDR System Test Description & Result SW Software WAM Wide Area Multilateration

Table 1 Abbreviations

EUROCONTROL

SUPPORTING EUROPEAN AVIATION

© EUROCONTROL - December 2019

This document is published by EUROCONTROL for information purposes. It may be copied in whole or in part, provided that EUROCONTROL

is mentioned as the source and it is not used for commercial purposes (i.e. for financial gain). The information in this document may not

be modified without prior written permission from EUROCONTROL.

www.eurocontrol.int

SUPPORTING EUROPEAN AVIATIONEUROCONTROL

ARTAS ROADMAP STRATEGY · Edition Nº Effective date or status Author(s) Reason 1.00 08/01/2007 R....

Documents

Transcript of ARTAS ROADMAP STRATEGY · Edition Nº Effective date or status Author(s) Reason 1.00 08/01/2007 R....