资源描述
September 2005October 14th 2009Advanced AIRMANTM Administrator TrainingOctober 14th, 2009Customer Services - Flight & Ground Information ServicesPresented byAIRMAN SupportCustomer Support Services AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 2AIRMAN General Overview : Agenda AIRMAN Chain of Communication Data Quality Analysis AIRMAN Installation Logs AIRMAN Services AIRMAN Application Logs Most Frequent Processing Issues AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 3AIRMAN Chain of CommunicationDSPGround reception toolDBAIRMANEastCare Filtering ScriptChina EasternVHF/SATCOMADCC Datalink Information and Ground Processing System AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 4Aircraft Pre-requisites (1/3) ACARS datalink activated:The aircraft needs to communicate with the ground (HF / VHF / SATCOM). Customization of the AOC database: Activation of OOOI, Real time failures & warnings and PFR automatic transmission. To be requested by the airline to the AOC supplier (Honeywell or Rockwell Collins). Customization of the ACMS database: Activation of desired reports automatic transmission via data-link. To be requested by the airline to the ACMS supplier. AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 5Aircraft Pre-requisites (2/3)FormatRequirementSourceMessage nameMessage TypePFRPost Flight ReportCMSMandatoryRawOOOIOUT / OFF / ON / IN ReportsATSU/AOCMandatoryRaw Standard ARINC620* RTF/RTWReal Time Failure / Real Time WarningFWS/CMSOptionalRawAll Standard ACMS Reportse.g.Engine cruise reportEngine take-off reportEngine gas path reportEngine start reportEngine run-up reportLoad reportACMSOptionalRaw AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 6Aircraft Pre-requisites (3/3)FaultFWSACARS/ ATSUCMSExample system monitored by Built In Test Equipment (BITE)List of Fault occurrencesavailable on MCDU (Post Flight)ECAM warning and Local Indication(Warning)Fault: System anomaly recorded by the BITE Not degrading Airworthiness of aircraftWarning; System anomaly that degrades the Airworthiness of the aircraftFWS: Flight Warning SystemCMS: Central Maintenance SystemCFDS: Centralized Fault Display SystemMCDU: Multipurpose Control & Display UnitExample: Real Time Faults and Warnings AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 7Datalink ProviderDatalink: Connection between an end-system on-board an aircraft and an end-system on ground (VHF, SATCOM, )Datalink Service Provider (DSP): Operates a network of Remote Ground Stations (RGSs) located at airports and other sites in order to provide VHF, HF and SATCOM coverage in the areas where the aircraft fly.E.g.: SITA (www.sita.aero/default.htm), ARINC (), ADCC (China: Aviation Data Communications Company )Request DSPs to:- Re-route messages to the airline (OOOI, PFRs, ACMS, RTF & RTW)- Re-route the messages to Airbus (Recommended):- Speeds up the data quality analysis phase- Saves time when analyzing flight issues in AIRMAN- Benefit from monitoring by RCSM & Airbus AOG center AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 8Ground Reception ToolGround Reception Tool (GRT): A ground application which receives the ACARS messages from the DSP server, and transfers them to AIRMANE.g.: Aircom Server, OPCenter / FTP access, Hermes, Two options:1.The GRT re-routes the data directly to the AIRMAN Feeding Folder, as received from the aircraft2.The data goes through intermediate scripts and folders before being dumped in the AIRMAN Feeding FolderAIRMAN requires ASCII raw formats as transmitted by the Service Provider from aircraft to ground, without adding, modifying or removal of any character. AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 9AIRMAN General Overview : Agenda AIRMAN Chain of Communication Data Quality Analysis AIRMAN Installation Logs AIRMAN Services AIRMAN Application Logs Most Frequent Processing Issues AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 10Data Quality Analysis (1/2)Objective:4 Ensure the aircraft send the correct and complete data sequence to AIRMAN.4 Ensure no messages get altered or lost on ground before reaching AIRMAN. Requirements:4 List of aircraft to be analyzed.4 One week of data. Raw text messages in the same format as received from the DSP (ADCC). In the same sequence as sent by the aircraft. AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 11Data Quality Analysis (2/2) Aircraft data pre-requisites: Mandatory data shall be available for all flights.4 OOOI: OUT, OFF, ON and IN.4 PFR: Post Flight Reports. Data shall be received in the correct sequence.OUT OFF ON PFR IN Each message shall be in a separate text file. Data shall be sent to AIRMAN in real time.4If the system date is changed by the ground reception tool, make sure there is at least a 2 seconds difference between a message, and the following one for the same aircraft. Data shall be in the same ASCII format as received by the Data Service Provider = ARINC 620 Specification. Data should contain all necessary information: Aircraft registration number, Flight number, departure and arrival airports and times, AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 12AIRMAN General Overview : Agenda AIRMAN Chain of Communication Data Quality Analysis AIRMAN Installation Logs AIRMAN Services AIRMAN Application Logs Most Frequent Processing Issues AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 13AIRMAN Installation Logs (1/3)Successful InstallationFailed Installation AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 14AIRMAN Installation Logs (2/3)AIRMAN Installation done.Summary of installed componentsWarnings AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 15AIRMAN Installation Logs (3/3)ERRORS AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 16AIRMAN General Overview : Agenda AIRMAN Chain of Communication Data Quality Analysis AIRMAN Installation Logs AIRMAN Services AIRMAN Application Logs Most Frequent Processing Issues AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 17AIRMAN Windows Services AIRMAN Amarta & ABC modules run as Windows Services- Amarta:Started from the Services window and stopped from AIRMAN- ABC: Started and Stopped from the Services window AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 18AIRMAN General Overview : Agenda AIRMAN Chain of Communication Data Quality Analysis AIRMAN Installation Logs AIRMAN Services AIRMAN Application Logs Most Frequent Processing Issues AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 19AIRMAN LogsFour types of AIRMAN “logs” are generated by AIRMAN when processing data:1.Amarta logsGenerated automatically when Amarta processes the messages2.Inter Site Export filesGenerated by Amarta periodically or on request = amarta Configuration window3.AIRMAN aircraft dump eventsGenerated on request = AdvancedData Quality AnalysisDump of aircraft events4.ABC logsGenerated automatically when ABC processes messages AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 20Amarta LogsAmarta general logs (AmaTR.Log):Describes the Amarta general behavior: Start, Stop, Service errorsNormal behaviorOracle connection error AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 21Amarta LogsAmarta daily logs (AmaTr_RTT_yyyymmdd.log):Details all processing errors reported by AmartaMessage unknown in the AIRMAN KBMissing flight for a PFRNote: These logs are used for internal investigation by the support team. AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 22Inter Site Export Files Export files generated on request, or automatically, containing an image of what was processed by Amarta(AmaTR_ICAO_OracleDB_OracleUser_yyyymmdd_hhmm.ise)Can be used to:4 Investigate rejected messages4 Re-import the data in a new system for investigationACARS Message contentError, if any! AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 23AIRMAN Aircraft Dump Events (1/3) Amarta “log files” generated on request, containing a summary of what was processed by Amarta(events_dump_AircraftImmatriculation_yyyymmddhhmmssmsmsms.txt)A/C IDEvent DateMessagesFlight NumberDep AirportArr AirportSending timeReception timeProcessing statusShould always be in this sequence: TFOPIShould not change within a flightShould stay coherent within a flight. The following flight shall depart from the previous flight arrival stationShould be _OK, RT_OK, DC_OK or DA_OK AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 24AIRMAN Aircraft Dump Events (2/3)Examples of problematic dumps:- Spurious MessagesSpurious OUT (ex: The aircraft is moved form gate to gate)- Missing MessagesMissing PFR AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 25AIRMAN Aircraft Dump Events (3/3)- Flight Number Change- Incoherent airportsFlight Number ChangeIncoherent Arrival airport AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 26ABC LogsABC daily logs (ABC_yyyymmdd.log):Details all processes launched by ABCXML Export launchedNormal behaviorABC general logs (ABC.Log):Describes the ABC general behavior: Start, Stop, Service errors AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 27AIRMAN General Overview : Agenda AIRMAN Chain of Communication Data Quality Analysis AIRMAN Installation Logs AIRMAN Services AIRMAN Application Logs Most Frequent Processing Issues AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 28Most Frequent Processing IssuesCommon errors that occur when processing ACARS messages in AIRMAN:1.Wrong message sequence:Sequence should be : OUT OFF ON PFR - IN.2.Spurious Messages.3.Missing Messages.4.Incoherent airports:a.Wrong departure airport.b.Wrong arrival airport.5.Flight number change.6.Wrong or updated OOOI format.7.Unknown Airports in AIRMAN KB. AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.August 2007 AIRMAN Technical PresentationPage 29 AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.This document and all information contained herein is the sole property of AIRBUS S.A.S. No intellectual property rights are granted by the delivery of this document or the disclosure of its content. This document shall not be reproduced or disclosed to a third party without the express written consent of AIRBUS S.A.S. This document and its content shall not be used for any purpose other than that for which it is supplied.The statements made herein do not constitute an offer. They are based on the mentioned assumptions and are expressed in good faith. Where the supporting grounds for these statements are not shown, AIRBUS S.A.S. will be pleased to explain the basis thereof.AIRBUS, its logo, A300, A310, A318, A319, A320, A321, A330, A340, A350, A380, A400M are registered trademarks.
展开阅读全文