ࡱ > V X U l ܥh c e po l P 8 8 8 8 8 8 8 D | | | | | " R | C f f | | | | K X b 8 g l | | 8 8 | 8 | 8 | t#| | 8 8 8 8 TITLE \* MERGEFORMAT ATNP Configuration Control Board (CCB) Procedures Document SUMMARY This document contains the structure and principles of operation of the ATNP CCB created by ATNP/2. It also contains as the appendices, the detailed procedures to be followed to participate in the ATN Panel Configuration Control Board change control process, based on a simple use of electronic tools. REVISION HISTORY SectionDateIssueReason for Change30 January 1997Issue 1.0Document Creation03 MARCH 1997Issue 1.1Interim CCB Amendments04 March 1997Issue 1.2Output of CCB1-2 meeting12 March 1997ICAO 1.1Phuket Final REFERENCES [1] ATNP/2 Meeting Report on Item 5 of the agenda [2] ATNP/2 WP 29: ATN SARPs Defect Reporting and Configuration Management after ATNP/2 [3] ATNP/2 WP 66 : Continuous Validation [4] WG2/WP66 - ATNP Configuration Control Board (CCB) Procedures Document [5] ATN Interim CCB- First meeting 28-30 January 1997 TABLE OF CONTENTS TOC \o "1-3" 1. Introduction GOTOBUTTON _Toc382169994 PAGEREF _Toc382169994 5 2. Scope and Purpose of this Document GOTOBUTTON _Toc382169995 PAGEREF _Toc382169995 5 3. Role of the CCB GOTOBUTTON _Toc382169996 PAGEREF _Toc382169996 5 4. Structure of the CCB GOTOBUTTON _Toc382169997 PAGEREF _Toc382169997 6 5. Method of operation GOTOBUTTON _Toc382169998 PAGEREF _Toc382169998 7 APPENDIX A: DETAILED CCB PROCEDURES GOTOBUTTON _Toc382169999 PAGEREF _Toc382169999 8 1. Introduction GOTOBUTTON _Toc382170000 PAGEREF _Toc382170000 8 1.1. Communication GOTOBUTTON _Toc382170001 PAGEREF _Toc382170001 8 1.2. Voting GOTOBUTTON _Toc382170002 PAGEREF _Toc382170002 8 1.3. Change Archive GOTOBUTTON _Toc382170003 PAGEREF _Toc382170003 9 1.4. Engineering Versions of the SARPs GOTOBUTTON _Toc382170004 PAGEREF _Toc382170004 9 2. Change Control Process Flow GOTOBUTTON _Toc382170005 PAGEREF _Toc382170005 9 2.1. PDR Review Process GOTOBUTTON _Toc382170006 PAGEREF _Toc382170006 11 2.2. PDR Resolution Process GOTOBUTTON _Toc382170007 PAGEREF _Toc382170007 11 2.3 PDR Decision Process GOTOBUTTON _Toc382170008 PAGEREF _Toc382170008 11 2.4 ICAO Coordination GOTOBUTTON _Toc382170009 PAGEREF _Toc382170009 12 3. ATNP CCB Report Forms GOTOBUTTON _Toc382170010 PAGEREF _Toc382170010 12 3.1. Proposed Defect Reports GOTOBUTTON _Toc382170011 PAGEREF _Toc382170011 12 3.1.1. PDR proposal GOTOBUTTON _Toc382170012 PAGEREF _Toc382170012 12 3.1.2 PDR Form GOTOBUTTON _Toc382170013 PAGEREF _Toc382170013 13 3.1.3. PDR Form Legend GOTOBUTTON _Toc382170014 PAGEREF _Toc382170014 14 3.x Voting Formats (TO BE ADDRESSED AND COMPLETED BY THE CCB) GOTOBUTTON _Toc382170015 PAGEREF _Toc382170015 15 APPENDIX B: Process for Maintenance of the Engineering Versions of the SARPs GOTOBUTTON _Toc382170016 PAGEREF _Toc382170016 16 1. Introduction GOTOBUTTON _Toc382170017 PAGEREF _Toc382170017 16 1.1. The Engineering Versions of the SARPs GOTOBUTTON _Toc382170018 PAGEREF _Toc382170018 16 2. Document Maintenance Process Flow GOTOBUTTON _Toc382170019 PAGEREF _Toc382170019 16 2.1 Step 1 GOTOBUTTON _Toc382170020 PAGEREF _Toc382170020 16 2.2 Step 2 GOTOBUTTON _Toc382170021 PAGEREF _Toc382170021 16 2.3 Step 3 GOTOBUTTON _Toc382170022 PAGEREF _Toc382170022 16 2.4 Step 4 GOTOBUTTON _Toc382170023 PAGEREF _Toc382170023 16 2.5 Step 5 GOTOBUTTON _Toc382170024 PAGEREF _Toc382170024 17 2.6 Step 6 GOTOBUTTON _Toc382170025 PAGEREF _Toc382170025 17 2.7 Step 7 GOTOBUTTON _Toc382170026 PAGEREF _Toc382170026 17 2.8 Step 8 GOTOBUTTON _Toc382170027 PAGEREF _Toc382170027 17 2.9 Steps 9 - 12 GOTOBUTTON _Toc382170028 PAGEREF _Toc382170028 17 1. Introduction The ATN SARPs have been considered by ATNP/2 as being in a mature enough state to be included in ICAO ANNEX 10. However, they will still be subject to corrections even when the ATN is implemented and operational on a large scale. A new process for the identification and proposing of amendments of the SARPs has been proposed to ICAO (ATNP/2 recommendation 3/2) which would provide an effective defect resolution mechanism and allow ATN implementors to be aware of the proposed changes in the SARPs as soon as they have been agreed by ATNP, without waiting for the process of modification and publication of the ICAO SARPs to be completed. This process is based on the creation of an ATNP CCB (Configuration Control Board), which will manage the configuration of all the ATN SARPs, and ensure that they are correctly and efficiently resolved when defects are found. The CCB will also be responsible for providing to ICAO, via the Secretariat, all the change proposals in an appropriate format. The Secretariat will process the amendments in the normal manner. 2. Scope and Purpose of this Document This document describes the role, structure and mode of operation of the ATNP Configuration Control Board (CCB). It is based on the decisions made at ATNP/2 and described in the ATNP/2 meeting report on item 5 of the agenda. Appendix A of this document contains detailed procedures for the ATNP Configuration Control Board (CCB) change control process. It is be based on the use of electronic tools such as mailing lists and an electronic archive. Appendix A also defines the format to be used for submission, and resolution, of Proposed Defect Reports (PDRs), and defines the electronic mail procedures to be used for the exchange of these messages among the active members of the ATNP CCB, Working Groups and Sub-Groups. Appendix B details the process for maintaining the Engineering Version of the SARPs. 3. Role of the CCB The CCB will only address defects reported on SARPs and Guidance Materiel (GM) that have been approved by the ATN Panel for submission to ICAO, and those SARPs and GM that have been adopted by ICAO. NOTE 1: DEFECT: A standard, recommended practice, or statement of information in the ATN SARPs which, if not corrected, will prevent the system from working properly or prevent the system from meeting its stated operational requirements NOTE 2: Draft ATN SARPs and GM that are being revised through the work program of the ATNP working groups will be the responsibility of the applicable working groups The objective of the CCB is to provide a means to coordinate the impact of State implementations on the ATN SARPs. The base ATN SARPs came from ATNP/2 and future revisions will serve to define the migration path to later versions of the ATN.PDRs may fall inter alia into the following categories: 1. Implementation hardships resulting from schedule and/or cost; 2. The ATN SARPs overspecify what is actually required to achieve interoperability or the requirement is stated in such a way that they may unnecessarily constrain implementations; 3. Ambiguities exist in the SARPs such that different interpretations will result in different implementations that are not interoperable; 4. Interoperability discrepancies are discovered that were not detected as part of the initial validation process. During the process of Validation, Implementation and Operation of the ATN SARPs, PDRs will be submitted to the ATNP CCB by members of the different ATNP Working Groups and Sub-Groups, by the ICAO Secretariat, by States, by Organizations or by Industry. The role of the CCB will be to manage each PDR concerning the ATN SARPs and agree on the changes, if any, to be made to the SARPs in order to address the PDR. Resolutions to PDRs could differ depending on the implementation status (schedule) of particular States/Organizations which could result in an interim fix to be followed by a permanent fix. For example, it may be desirable to provide a procedural fix to a PDR because the problem was discovered too late in the schedule to proceed any other way at this time but the long term fix could be a technical change for future modifications or new builds at a later point in time. The CCB will send, on a regular basis, proposed modifications (in hard copy) to ICAO through the ICAO Secretariat. Once ICAO has adopted the modifications, the ICAO Secretariat will update the current version of the SARPs and distribute the amendments. Furthermore, the CCB maintains a version of the ATN SARPs which will track the CCB approved changes in the full text of the ATN SARPs. This Engineering Version of the ATN SARPs will be a CCB working tool which will include all CCB approved modifications change-barred against the current ICAO master version. The Engineering Version of the ATN SARPs and GM will be updated in accordance with the procedures in Appendix B of this document. 4. Structure of the CCB The CCB will comprise a CCB Chair, one Subject Matter Expert (SME) for each SARPs Sub-Volume (Sections 1-5 of Appendix A to the SARPs), and any ATN Panel Members (or designated representative) who wish to be involved. NOTE: An ATN Panel member (or designated representative) will indicate either ACTIVE PARTICIPATION status or OBSERVER status when identifying his/her interest in participating in the CCB. The CCB Chair shall be the interface between the CCB and ICAO. The Chair will coordinate the CCB process and maintain an archive. An SME is a technical expert for a Sub-Volume and acts as the interface between the CCB and an open group of technical experts wishing to be involved in the resolution of PDRs. The SMEs coordinate the technical debates among experts and report the results to the CCB.The SME for each Sub-Volume will be proposed by the WG responsible for the Sub-Volume in question, e.g. WG2 will propose the SME for Sub Volume 5. The WG and CCB will establish a set of procedures (within the context of the SME role as defined in this document) defining the relationship between the SME and the WG in resolving defects submitted to the CCB. These procedures should not unduly delay the CCB process as defined in this document. 5. Method of operation The following points outline the method of operation of the CCB (Appendix A details the process): The CCB bases its work on the latest official ICAO Version of the SARPs as well as any new SARPs and GM materiel that has been approved by the ATN Panel for submission to ICAO. Each PDR submitted to the CCB must reference the official version or the ATNP approved SARPs and GM. The CCB receives PDRs by e-mail to a predefined address. The CCB accepts the PDR, rejects the PDR, or forwards the PDR to the appropriate WGs. If the PDR has been accepted by the CCB, the CCB Chairman designates one (even if several Sub-Volumes are concerned) responsible SME for the PDR resolution. The PDR is resolved under the responsibility of the designated SME, who, with the help of his/her team of technical experts, produces a recommended action for CCB approval. If the CCB does not agree to the change, the PDR is returned to the SME. The CCB sends its agreed changes to the SARPs to ICAO. The CCB Chair is responsible for archiving the changes. The CCB will keep the ATN community informed as to the status of proposed ATN related amendments. The process will be progressed using e-mail discussion and, if consensus cannot be reached, voting. In very difficult PDRs it may be necessary to resolve the problem at a CCB meeting. CCB meetings should be held over one or two days at the end of the WGs meetings (i.e. every 3 or 4 months) so as not to require additional travel and to make use of an existing ATNP mode of operation. It is expected that the CCB is equal in duration to the Panel. APPENDIX A: DETAILED CCB PROCEDURES This appendix provides the detailed procedures of the ATNP CCB. 1. Introduction 1.1. Communication The preferred method of communication within the CCB processes is INTERNET e-mail. Other methods, at the call of the CCB Chair, will be used if E-mail is not available. Mailing lists will be set up and maintained, most with open subscription. The mailing lists will be: ccb_chair : maintained by the CCB Chair, this list will only include the CCB Members and will be used for CCB level communication and voting and for the initial submission of a PDR. ccb_list : maintained by the CCB Chair, this list will be used to disseminate all CCB decisions. 5 specialist lists : one maintained by each SME, will be used to progress the resolution of submitted PDRs. All messages will use the predefined format (para 3.1.2) to progress between the formal stages of the procedures. Free format messages will be used for discussion within any stage. The predefined message uses are described in the relevant sections below. When e-mail exchange does not produce a decision, the PDR will be tabled at the next CCB meeting where a decision will be made. 1.2. Voting The normal method of resolution of PDRs will be by consensus of the members of the CCB. If consensus cannot be reached then resolution will be by voting. The CCB will make decisions at two stages: - the initial consideration of the PDR status; -consideration of a SMEs recommended action regarding a PDR. (An SME may implement a voting procedure within his/her team for the progression of PDRs but such a process is not covered within this document.) Only one CCB vote per State or International Organization will be permitted and the Chair does not vote. NOTE: In extraordinary circumstances when the chairman is the only representative of a particular state/IO and provisions have not been made for that particular State/IO to exercise their right to fully participate in the operation of the CCB process, the chairman will be granted a vote. At the initial PDR review stage, each CCB member shall vote (using a predefined message format) to either Reject, Forward, Accept or Abstain. At the SME recommended action stage, each CCB member shall vote (using a predefined message format) to either Agree or Not-Agree with the SME proposal regarding the PDR resolution or to Abstain from a decision. If the CCB does not agree with the SME proposal, the PDR will continue to stay in the PROPOSED status. If the CCB agrees with the SME proposal, the PDR will move into the RESOLVED, REJECTED, FORWARDED, or WITHDRAWN status depending on the particular proposal contained in the recommendation of the SME (see section 2.3 and figure 1). In general, ATNP CCB meetings will take place at the end of a session of the WGs meetings. However, when considered necessary by the CCB Chair, an extraordinary CCB meeting may be convened for review of outstanding PDRs. 1.3. Change Archive The CCB Chair shall maintain an Archive which includes a database of the submitted PDRs and their status. PDRs shall be assigned unique numbers to enable full traceability. In order to advise CCB Members and any interested party of the status of the PDR archive, a report will be created periodically by the CCB Chair and will be distributed to the ccb_list mailing list. This report will also be archived on the ATNP CCB Change Management (CM) system for ftp retrieval by interested parties. The period at which these reports will be issued may vary depending on CCB activity, but will not be shorter than 1 week and not longer than 1 month. 1.4. Engineering Versions of the SARPs The CCB will maintain a working version of the SARPs which have all of the CCB approved changes incorporated and change-barred against the current ICAO master version. This shall be called the Engineering Version. The Engineering Version of a Sub-volume will be maintained by the SME. 2. Change Control Process Flow The CCB uses the procedure shown in Figure 1 to record, process, and trace all PDRs which are received in the context of the CNS/ATM-1 Package implementation and operation. EMBED PowerPoint.Show.8 Figure 1. ATNP CCB Process 2.1. PDR Review Process In order to ensure that PDRs submitted to the CCB are relatively mature, it is recommended that the proposed defect report be first discussed among members of the atn-internet-technical or atnp_wg3 mailing lists. Each PDR should be sent to the ccb_chair mailing list in the pre-defined e-mail format (3.1.2) with a title that an idea of the content of the PDR. The CCB has the authority to refuse a PDR which is not presented on the mandatory form described in para 3.1.3, with the fields appropriately filled in. The CCB Chair will allocate a unique PDR number and then coordinate the CCB discussion and resolution on the PDR. There are four possible results at this stage of the process: The CCB can decide that the PDR does not present a Defect. The CCB Chair will archive it as a REJECTED defect, and inform the author that the PDR has been rejected and why. The CCB can decide the PDR presents a defect, but not one that requires immediate resolution, (in effect a proposal for enhancing the SARPs). The CCB Chair will archive it as FORWARDED and forward the PDR to the Rapporteur(s) of the concerned Working Group(s) for their future work. The CCB can decide the PDR presents a defect that requires immediate resolution. The CCB Chair will archive it as ACCEPTED and assign responsibility for its resolution to one SME. The author can decide that s/he does not wish to pursue the PDR . The CCB Chair will archive it as a WITHDRAWN defect and remove it from consideration The CCB Chair will post the PDR and decision to the ccb_list e-mail list. 2.2. PDR Resolution Process After the receipt of an ACCEPTED PDR, the SME is in charge of preparing (with the help of the technical experts of his/her team) a proposed solution for the CCB. Each SME will determine the actual working methodology of the team but generally it will consist of a discussion period followed by a consensus (or if necessary a vote) on the solution for the PDR. The SME will then submit this proposed resolution to the CCB. The SME recommendation to the CCB will be in the predefined message format (3.1.2) and be sent to the ccb_chair e-mail list. The PDR will be archived as PROPOSED. 2.3 PDR Decision Process The CCB shall reach consensus (or vote if necessary) upon the SME proposal, using predefined message formats. If the CCB does not agree with the proposal: the SME shall be given the reasons and asked to develop an alternative proposal. If the CCB agrees with the proposal the action is dependent upon the proposal: if the recommendation was FORWARD, the PDR is archived as FORWARDED and forwarded to the relevant WG(s) for their future work. if the recommendation was RESOLVE, the PDR is archived as RESOLVED, the relevant Engineering Version document is updated and an amendment to the SARPs is sent to ICAO in the approved manner. if the recommendation was REJECT, the PDR is archived as REJECTED .NOTE: The author can decide that s/he does not wish to pursue the PDR . The CCB Chair will archive it as a WITHDRAWN defect and remove it from consideration. 2.4 ICAO Coordination Periodically, typically every four months, the CCB Chair will ask the SME to print the Engineering Version of the full SARPs. The CCB Chair will send a hard copy of the CCB accepted changes to the Panel Secretary for inclusion in the ICAO amendment process. The Panel Secretary shall report the ANC decisions back to the CCB Chair and provide the CCB Chair with the master ICAO Version (soft copy) of the adopted Amendments to Annex 10 related to ATN. 3. ATNP CCB Report Forms Forms to be used for the ATNP CCB Configuration Management process are contained in the following sections. NOTE: The format of the messages must be strictly followed to enable automated processing of the PDRs and resolution reports 3.1. Proposed Defect Reports 3.1.1. PDR proposal An ATNP CCB PDR proposal message, when submitted to the CCB, shall have the format described in the following sub-sections. 3.1.1.1. TO Address This should be sent to the ccb_chair list. 3.1.1.2. SUBJECT Field PDR: