ARTAS Roadmap Strategy. ARTAS Reference No.: ARTAS-MGT-STR-01 Edition Number: 9.00 Edition Date: 16/03/2018 Status: Issued Classification:

Transcription

1 ARTAS Reference No.: ARTAS-MGT-STR-01 Edition Number: 9.00 Edition Date: 16/03/2018 Status: Issued Classification: TLP: AMBER Author: EUROCONTROL Intended For: Stakeholders

2 Traffic Light Protocol (TLP 1 ) Applicable Classification Colour RED AMBER GREEN WHITE When should it be used? 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. 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. 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. 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: Edition 9.00 Page 2 of 34

3

4 /04/2014 D. Morton Issued /01/2015 A. Principe New naming convention, including the UPDATE concept /01/2015 D. Morton Review /01/2015 A. Principe Change of the name of the document /01/2015 P. Gomord Review /01/2015 D. Morton Review(2) /02/2015 A. Principe Integration of the PG and DM comments /02/2015 D. Morton Proposed Issue /02/2015 D. Morton Issued /06/2015 A. Principe Clarification on limited support period /06/2015 D. Morton Review /06/2015 D. Morton & A. Principe Review /06/2015 A. Principe Review /06/2015 A. Principe AUG#53 approval (changed Section initial duration is of 3 6 months) /06/2015 D. Morton Issued /01/2016 A. Principe Added Check Point, Blocking High ATR Process between two UPDATEs and strategy for ASTERIX modifications /02/2016 D. Morton Review /03/2017 A. Principe Added Emergency Patches, Check Point and Release Candidate /04/2017 A. Principe Added Classes of ARTAS Functionalities and the related CAMOS support /06/2017 A. Principe Review prior to AUG# /06/2017 A. Werner Review /10/2017 A. Principe Changes approved by the AUG /10/2017 A. Principe Addressing AS' comments/review and applied changes for the Web publication /11/2017 A. Principe Added the TLP section /03/2018 Eurocontrol Issued Distribution List Name Antonio Principe ARTAS Users ARTAS Staff COMSOFT Staff Representing ARTAS Service Manager Stakeholders ARTAS Industrial Partners 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 NMD/NS/SRS Edition 9.00 Page 4 of 34

5 Table of Contents 1 INTRODUCTION DOCUMENTATION APPLICABLE DOCUMENTS REFERENCE DOCUMENTS AUDIENCE DEFINITIONS ATR & ACP Artas Trouble Report (ATR) Artas Change Proposal (ACP) ARTAS VERSION ARTAS VERSION foundation date ARTAS VERSION end of development date ARTAS VERSION end of support date ARTAS VERSION naming convention Drivers for creating a version ARTAS VERSION RELEASE ARTAS VERSION RELEASE naming convention ARTAS VERSION RELEASE disclaimer ARTAS VERSION RELEASE UPDATE ARTAS VERSION RELEASE UPDATE naming convention ARTAS VERSION RELEASE UPDATE disclaimer EMERGENCY PATCH ARTAS emergency patch disclaimer ARTAS FAT ARTAS VERSION RELEASE FAT ARTAS VERSION RELEASE HW FAT HARDWARE SOLUTIONS SUPPORTED HARDWARE SOLUTION USER HARDWARE SOLUTION CAMOS SUPPORT Full support limited support Limited support period no support UNVERIFIED ARTEFACTS Unverified patch Check point (CP) Release candidate (RC) CLASSES OF ARTAS FUNCTIONALITIES & CAMOS SUPPORT Fully supported Partially supported Not supported ARTAS VERSIONS STRATEGY LIFECYCLE OF ARTAS VERSIONS Impact of a new artas version on the lifecycle of the existing one ARTAS VERSION & camos support LIFECYCLE OF ARTAS VERSION RELEASES ARTAS VERSION RELEASE & camos support ARTAS VERSION RELEASE FAT LIFECYCLE OF ARTAS VERSION RELEASE UPDATES ARTAS VERSION RELEASE UPDATE & camos support ACP POLICY DOCUMENTATION POLICY ARTAS DEFAULT PARAMETERS VALUES POLICY ARTAS PARAMETERS DISCLAIMER Edition 9.00 Page 5 of 34

6 5.7 ASTERIX POLICY ASTERIX backward modifications ASTERIX non-backward modifications SUPPORTED HARDWARE SOLUTIONS Supported HARDWARE SOLUTIONS of AN ARTAS VERSION RELEASE USER HARDWARE SOLUTION ANNEX A ABBREVIATIONS List of Figures Figure 1 Check Points and Release Candidates Figure 2 Lifecycle of an ARTAS VERSION Figure 3 Lifecycle of two ARTAS VERSIONS (case 1) Figure 4 Lifecycle of two ARTAS VERSIONS (case 2) Figure 5 CAMOS Support for an ARTAS VERSION Figure 6 Lifecycle ARTAS VERSION RELEASES Figure 7 Lifecycle ARTAS VERSION RELEASE UPDATES Figure 8 Emergency Patches for ARTAS VERSION RELEASE UPDATES Figure 9 Supported Hardware Solutions None List of Tables Edition 9.00 Page 6 of 34

7 INTENTIONALLY LEFT BLANK Edition 9.00 Page 7 of 34

8

9 1 INTRODUCTION The aim of this document is to define: the 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 will always be available at the following address: ENTS/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 9.00 Page 9 of 34

10 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-VERSION-EOD-EOSdates_and_Supported Hardware Solutions [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 Partner 2 (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 9.00 Page 10 of 34

11 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 VERSION RELEASE [4.3] a) ARTAS VERSION RELEASE NAMING CONVENTION [4.3.1] b) ARTAS VERSION RELEASE DISCLAIMER [4.3.2] 4. ARTAS VERSION RELEASE UPDATE [4.4] a) ARTAS VERSION RELEASE UPDATE NAMING CONVENTION [4.4.1] b) ARTAS VERSION RELEASE UPDATE DISCLAIMER [4.4.2] 5. EMERGENCY PATCH [4.5] a) EMERGENCY PATCH DISCLAIMER [4.5.1] 6. ARTAS FAT [4.6] a) ARTAS VERSION RELEASE FAT [4.6.1] b) ARTAS VERSION RELEASE HW FAT [4.6.2] 7. HARDWARE SOLUTIONS [4.7] a) SUPPORTED HARDWARE SOLUTION [4.7.1] b) USER HARDWARE SOLUTION [4.7.2] 8. CAMOS SUPPORT [4.8] a) FULL SUPPORT [4.8.1] b) LIMITED SUPPORT [4.8.2] c) LIMITED SUPPORT PERIOD [4.8.3] d) NO SUPPORT [4.8.4] 9. UNVERIFIED ARTEFACTS [4.9] a) UNVERIFIED PATCH [4.9.1] b) CHECK POINT (CP) [4.9.2] c) RELEASE CANDIDATE (RC) [4.9.3] 10. CLASSES OF ARTAS FUNCTIONALITIES & CAMOS SUPPORT [4.10] Edition 9.00 Page 11 of 34

12 a) FULLY SUPPORTED [4.10.1] b) PARTIALLY SUPPORTED [4.10.2] c) NOT SUPPORTED [4.10.3] Edition 9.00 Page 12 of 34

13 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 date 3 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 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 Supported Hardware Solutions and therefore will not have any means of providing any sort of support for the ARTAS VERSION. Edition 9.00 Page 13 of 34

14 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 DRIVERS FOR CREATING A 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 9.00 Page 14 of 34

15 4.3 ARTAS VERSION RELEASE An ARTAS VERSION RELEASE represents a formal delivery of executable software that implements both ACPs and ATRs together with the full set of ARTAS documentation. An ARTAS VERSION 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 VERSION RELEASE: o o o o o o The implementation of a set of ACPs The integration and consolidation of all ATRs solved since the previous ARTAS VERSION RELEASE The adoption of a new O.S. The integration of a new release of the Middleware The integration of a new release of COTS/OTS The integration of a new release of libraries The following list describes ARTAS deliverables related to the ARTAS VERSION RELEASE: o o o o o The ARTAS system The full ARTAS set of documentation Quality and Safety evidence SWAL3 Safety Folder Declaration of Suitability of Use ARTAS VERSION RELEASE NAMING CONVENTION For the ARTAS VERSION RELEASE, the following naming convention applies: <ARTAS VERSION><ARTAS VERSION RELEASE-id> where RELEASE-id is a digit representing the release number of the ARTAS VERSION. Note: When the first ARTAS VERSION 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 ARTAS VERSION RELEASE DISCLAIMER ARTAS Users are solely responsible for the validation of the ARTAS VERSION RELEASE in their own operational environment. ARTAS Users undertake to deploy the ARTAS VERSION 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 VERSION RELEASE. 4.4 ARTAS VERSION RELEASE UPDATE Edition 9.00 Page 15 of 34

16 An ARTAS VERSION RELEASE 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 VERSION RELEASE. An ARTAS VERSION RELEASE UPDATE undergoes a set of regression tests executed, at various levels, by both CAMOS and its Industrial Partner, but does not undergo a FAT. ARTAS VERSION RELEASE UPDATES are delivered to the ARTAS Users during the Support (Full + Limited) period of the corresponding ARTAS VERSION RELEASE. The following list describes the possible enhancements that can form part of the ARTAS VERSION RELEASE UPDATE: o o The implementation of a few ACPs The implementation of ATRs The following list describes ARTAS deliverables related to the ARTAS VERSION RELEASE UPDATE: o o o o A subset of the executable software of the ARTAS system A subset of the parameter configuration files of the ARTAS system A subset of the ARTAS documentation Quality and Safety evidence for the implemented ATRs/ACPs ARTAS VERSION RELEASE UPDATE NAMING CONVENTION For the ARTAS VERSION RELEASE UPDATE, the following naming convention applies: <ARTAS VERSION RELEASE>-U<UPDATE-id> where UPDATE-id is a digit representing the update number of an ARTAS VERSION RELEASE preceded by the letter U Example: V8B2-U2 is the second UPDATE of ARTAS V8B ARTAS VERSION RELEASE UPDATE DISCLAIMER ARTAS Users are solely responsible for the validation of the ARTAS VERSION RELEASE UPDATE in their own operational environment. ARTAS Users undertake to deploy the ARTAS VERSION RELEASE 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 VERSION RELEASE UPDATE. 4.5 EMERGENCY PATCH Once an ARTAS VERSION RELEASE 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 EMERGENCY PATCH (EP). Once verified, the EPs are made available to the ARTAS community as described in [RD3]. Edition 9.00 Page 16 of 34

17 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 DISCLAIMER ARTAS Users are solely responsible for the verification and validation of the EMERGENCY PATCH of an ARTAS VERSION RELEASE 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 9.00 Page 17 of 34

18 4.6 ARTAS FAT ARTAS VERSION 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 ARTAS VERSION RELEASE HW FAT A Hardware FAT is a FAT conducted on a complete and integrated ARTAS VERSION RELEASE, mainly to validate an additional Supported Hardware Solution for a specific ARTAS VERSION RELEASE. 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. 4.7 HARDWARE SOLUTIONS SUPPORTED HARDWARE SOLUTION A Supported Hardware Solution (HS) of an ARTAS VERSION RELEASE is a hardware solution (i.e. a server/computer) validated via an ACP, perhaps during the FAT activities of the ARTAS VERSION RELEASE USER HARDWARE SOLUTION A User Hardware Solution (UHS) of an ARTAS VERSION RELEASE is a hardware solution different to the Supported Hardware Solutions of the ARTAS VERSION RELEASE. 4.8 CAMOS SUPPORT FULL SUPPORT With Full Support, CAMOS provides changes for: Accepted ATRs according to their priority ACPs agreed by the AUG Governance 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 Edition 9.00 Page 18 of 34

19 Safety/Critical ACPs for which a work-around is not available LIMITED SUPPORT PERIOD The Limited Support Period is the period of time during which CAMOS provides LIMITED SUPPORT for an ARTAS VERSION RELEASE (e.g. RL n ). The Limited Support Period starts on the date when CAMOS announces the availability of a new ARTAS VERSION RELEASE (RL n+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 VERSION RELEASE (RL n+1 ) b) At the end of the Limited Support Period, if no blocking issue exists, the Limited Support Period for the ARTAS VERSION RELEASE (RL n ) is terminated. c) At the end of the Limited Support Period, if blocking issues are still unresolved, the Limited Support Period for the ARTAS VERSION RELEASE (RL n ) is extended for an additional period of 3 months (and the process restarts from point a)) NO SUPPORT With NO SUPPORT, CAMOS processes requests for trouble reports in line with the following procedure: a. The ATR is opened on an ARTAS VERSION (e.g. V y ) after its EOS. In this case, CAMOS checks whether the problem is affecting the most recent ARTAS VERSION RELEASE UPDATE (e.g. UP m of RL n+2 ) of the most recent ARTAS VERSION (e.g. V y+2 ) and, if needed, provides a fix for the ATR only on top of it (i.e. on top of the most recent ARTAS VERSION RELEASE UPDATE of the most recent ARTAS VERSION). b. The ATR is opened on an ARTAS VERSION RELEASE (e.g. RL n ) when its LIMITED SUPPORT PERIOD is terminated. In this case, CAMOS checks whether the problem is affecting the most recent ARTAS VERSION RELEASE UPDATE (e.g. UP m ) of the most recent ARTAS VERSION RELEASE (e.g. RL n+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 VERSION RELEASE UPDATE of the most recent ARTAS VERSION RELEASE of the same ARTAS VERSION e.g. on top of UP m of RL n+2 ). c. The ATR is opened on an ARTAS VERSION RELEASE UPDATE (UP m ) when, as a minimum, the ARTAS VERSION RELEASE UPDATE (UP m+1 ) is released. In this case, CAMOS checks whether the problem is affecting the most recent ARTAS VERSION RELEASE UPDATE (e.g. UP m+3 ) of the same ARTAS VERSION RELEASE (e.g. RL n ) and, if needed, provides a fix for the ATR only on top of it (i.e. on top of the most recent ARTAS VERSION RELEASE UPDATE of the same ARTAS VERSION RELEASE, e.g. on top of UP m+3 of RL n ). 4.9 UNVERIFIED ARTEFACTS UNVERIFIED PATCH Edition 9.00 Page 19 of 34

20 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). 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 Edition 9.00 Page 20 of 34

21 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 or 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 for these functionalities described in As from ARTAS V8B4, 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 maximum 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. Edition 9.00 Page 21 of 34

22 Users planning to use ARTAS in a configuration that goes beyond its nominal capacity (e.g. more than 30 sensors / 4000 Tracks / 2000 inputs/s) are advised to plan a wider verification and validation phase prior to deploying ARTAS operationally. CAMOS provides only limited support for ATRs and no support for ACPs related to the functionalities of this class. As from ARTAS V8B4, 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. 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.4, for these functionalities. As from ARTAS V8B4, 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 years. The EOS date of any ARTAS VERSION is by default equal to the EOD date of the ARTAS VERSION years 4. 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 9.00 Page 22 of 34

23 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. 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 V n+1 ) sets the EOD and EOS dates of the existing ARTAS VERSION (ARTAS V n ). Where the ARTAS V n+1 is made available when the ARTAS V n 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 V n are: ARTAS V n EOD date is set at the Foundation Date of ARTAS V n+1 ARTAS V n EOS date is set at the Foundation Date of ARTAS V n years. Edition 9.00 Page 23 of 34

24 Figure 3 Lifecycle of two ARTAS VERSIONS (case 1) Where the ARTAS V n+1 is made available before ARTAS V n 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 V n remain unchanged: ARTAS V n EOD date is set at the Foundation Date of ARTAS V n years ARTAS V n EOS date is set at the Foundation Date of ARTAS V n years. Edition 9.00 Page 24 of 34

25 Figure 4 Lifecycle of two ARTAS VERSIONS (case 2) ARTAS VERSION & CAMOS SUPPORT For an ARTAS VERSION, CAMOS provides: Full Support 5 up to the EOD date Limited Support 5 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 VERSION RELEASESs and ARTAS VERSION RELEASE UPDATES should also be considered. Edition 9.00 Page 25 of 34

26 6 Figure 5 CAMOS Support for an ARTAS VERSION 5.2 LIFECYCLE OF ARTAS VERSION RELEASES The number of ARTAS VERSION 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 VERSION RELEASES are made available, on average, every 18/24 months (see Figure 6 Lifecycle ARTAS VERSION RELEASES). Full Support for at least 4.5 years plus 2.5 years of Limited Support Edition 9.00 Page 26 of 34

27 Figure 6 Lifecycle ARTAS VERSION RELEASES ARTAS VERSION RELEASE & CAMOS SUPPORT For an ARTAS VERSION RELEASE (RL n ), CAMOS provides: Full Support 7 up to the date when CAMOS announces the availability of a new ARTAS VERSION RELEASE (RL n+1 ) to the ARTAS Community. Limited Support 7 only for a Limited Support Period (see 4.8.3) from the date when CAMOS announces the availability of a new ARTAS VERSION RELEASE (RL n+1 ) to the ARTAS Community. No Support when the Limited Support Period is terminated ARTAS VERSION RELEASE FAT A FAT is executed for each ARTAS VERSION RELEASE of an ARTAS VERSION. 5.3 LIFECYCLE OF ARTAS VERSION RELEASE UPDATES The number of ARTAS VERSION RELEASE UPDATES of an ARTAS VERSION RELEASE depends on the life cycle of the ARTAS VERSION RELEASE (18/24 months) and on the number, complexity and severity of the ATRs opened by the ARTAS Users over this period 7 CAMOS SUPPORT for ARTAS VERSION and ARTAS VERSION RELEASE UPDATEs to be considered too. Edition 9.00 Page 27 of 34

28 of time. On average, 3/4 of ARTAS VERSION RELEASE UPDATES are scheduled for an ARTAS VERSION RELEASE (see Figure 7 Lifecycle ARTAS VERSION RELEASE UPDATES). Figure 7 Lifecycle ARTAS VERSION RELEASE UPDATES ARTAS VERSION RELEASE UPDATE & CAMOS SUPPORT For an ARTAS VERSION RELEASE UPDATE (UP n ), CAMOS provides: Full Support 8 up to the date when CAMOS announces the availability of a new ARTAS VERSION RELEASE UPDATE (UP n+1 ) to the ARTAS Community. No Support when the new ARTAS VERSION RELEASE UPDATE (UP n+1 ) is released. In general, the CAMOS Full Support mentioned above provides fixes for ATRs/ACPs only on top of the latest ARTAS VERSION RELEASE UPDATE in the form of EMERGENCY PATCHES (4.5). 8 CAMOS SUPPORT for ARTAS VERSION and ARTAS VERSION RELEASE UPDATES should also be considered. Edition 9.00 Page 28 of 34

29 Figure 8 Emergency Patches for ARTAS VERSION RELEASE UPDATES Edition 9.00 Page 29 of 34

30 5.4 ACP POLICY ACPs should be grouped and made available with an ARTAS VERSION 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 VERSION RELEASE. Whenever deemed necessary, ACP(s) can be delivered in an ARTAS VERSION RELEASE UPDATE. In order to avoid jeopardising the stability of the behaviour of an existing ARTAS VERSION RELEASE (RL n ) or ARTAS VERSION RELEASE UPDATE (UP n ), whenever feasible the ACPs implemented in a new ARTAS VERSION RELEASE (RL n+1 ) or ARTAS VERSION RELEASE UPDATE (UP n+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 VERSION RELEASE of an ARTAS VERSION (e.g. V8B0, V8B1, V8B2, etc.). A reduced set of only the updated documents will be produced and made available at each ARTAS VERSION RELEASE UPDATE of an ARTAS VERSION RELEASE (e.g. V8B3-U2, V8B3-U3, 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 VERSION 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 9.00 Page 30 of 34

31 5.7 ASTERIX POLICY To keep ARTAS compatible with the latest updates of the supported ASTERIX categories, CAMOS proceeds according to the following two approaches, depending on the backward compatibility of the ASTERIX changes: ASTERIX BACKWARD MODIFICATIONS Whenever a new edition of an ASTERIX category containing only backward-compatible changes is approved by the ASTERIX Community, CAMOS creates an ATR to implement those changes for ARTAS to accept frames of the latest edition of the ASTERIX category. The ATR will be integrated in the next planned ARTAS VERSION RELEASE or ARTAS VERSION RELEASE UPDATE. Furthermore, CAMOS will also create an ACP to define how ARTAS has to process and use the information conveyed through the new/modified items of the new edition of the ARTAS category. The newly opened ACP will be processed according to CAMOS resource availability and the priority defined by the AUG ASTERIX NON-BACKWARD MODIFICATIONS Whenever a new edition of an ASTERIX category containing at least one non-backward compatible change is approved by the ASTERIX Community, CAMOS will open an ACP to define how ARTAS has to process and use the information conveyed through the new/modified items of the new edition of the ARTAS category. The newly opened ACP will be processed according to CAMOS resource availability and the priority defined by the AUG. 5.8 SUPPORTED HARDWARE SOLUTIONS SUPPORTED HARDWARE SOLUTIONS OF AN ARTAS VERSION RELEASE Each ARTAS VERSION RELEASE is to be hosted on a hardware solution. CAMOS defines the Supported Hardware Solutions (HS) for running an ARTAS VERSION RELEASE. Any ARTAS VERSION RELEASE will have at least two Supported Hardware Solutions, namely HS i, and HS i+1. Whenever possible, in order to reduce the cost of frequent hardware changes, CAMOS will make use of the Supported Hardware Solutions of the existing ARTAS VERSION RELEASE with a new ARTAS VERSION RELEASE of the same ARTAS VERSION. Furthermore, additional Supported Hardware Solutions (namely HS i+2 and HS i+3 ) could be introduced with a new ARTAS VERSION RELEASE of the same ARTAS VERSION. In this case, the new ARTAS VERSION RELEASE will have 4 Supported Hardware Solutions (namely HS i, HS i+1, HS i+2 and HS i+3 ) (see Figure 9 Supported Hardware Solution). Edition 9.00 Page 31 of 34

32 Figure 9 Supported Hardware Solutions Edition 9.00 Page 32 of 34

33 SUPPORTED HARDWARE SOLUTIONS & CAMOS SUPPORT CAMOS only provides Full Support 9 for problems related to the Supported Hardware Solutions of the ARTAS VERSION RELEASES SUPPORTED HARDWARE SOLUTIONS VS ARTAS TESTS ATRs and ACPs are tested only on the most recent Supported Hardware Solutions of an ARTAS VERSION RELEASE. Users who want CAMOS and its IP to execute the test of a resolved ATR/ACP on a different Supported Hardware Solution have to make the appropriate request when opening the ATR/ACP. During the FAT of an ARTAS VERSION RELEASE, ATRs and ACPs will be tested on the 2 most recent Supported Hardware Solutions. During the system test phase (of the FAT), the tests will be executed on the Supported Hardware Solution HS j (HS j+1 ). The same test will be executed on the Supported Hardware Solution HS j+1 (HS j ) during the pre-fat or FAT. Users may request CAMOS and its IP to adopt a different Supported Hardware Solution during the FAT USER HARDWARE SOLUTION When a user adopts a User Hardware Solution for an ARTAS VERSION RELEASE, they shall declare to CAMOS the reference Supported Hardware Solution of their User Hardware Solution USER HARDWARE SOLUTIONS & CAMOS SUPPORT For User Hardware Solutions of an ARTAS VERSION RELEASE, CAMOS provides: Full Support for problems which are reproducible on the reference Supported Hardware 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 reference Supported Hardware Solution. 9 CAMOS SUPPORT for ARTAS VERSIONS, ARTAS VERSION RELEASES and ARTAS VERSION RELEASE UPDATES should also be considered. Edition 9.00 Page 33 of 34

34 Annex A Abbreviations The following abbreviations are used throughout the document. ACP ANSP ARTAS ATR AUG CCB COTS CAMOS CVS DOC EC EOD EOL EOS FAT HS HW LAN NA O.S. OL OTS SLA STDR SW WAM ARTAS Change Proposal Air Navigation Service Provider EUROCONTROL ATM SuRveillance Tracker And Server ARTAS Trouble Report ARTAS User Group Configuration Control Board Commercial Off The Shelf. Centralised ARTAS Maintenance and Operational Support Concurrent Versions System ARTAS documentation EUROCONTROL End Of Development (EC) End Of Life End Of Support (EC) Factory Acceptance Test Supported Hardware Solution Hardware Local Area Network National Administration(s) Operating System Oracle Linux Off The Shelf Service Level Agreement System Test Description & Result Software Wide Area Multilateration Edition 9.00 Page 34 of 34