Please enable JavaScript.
Coggle requires JavaScript to display documents.
Testing ETOPS Reliability Report
15-3-2017, Roy ten Have
Last update: 11…
Testing ETOPS Reliability Report
15-3-2017, Roy ten Have
Last update: 11-4-2017
Last execution: 20-6-2017
-
Advice
The report functions according to requirements and FDD (showing cycles made during either Non-ETOPS and ETOPS 120) while not showing any non-required capability changes.
Note: The timestamp shown relates to the received usage record and increase in cycle.
No open bugs, all testcases executed with a positive result.
Risks
:check: R01 - Not all required ETOPS changes are visible in the report (only no ETOPS and ETOPS 120)
:check: R02 - Risk that the report shows all capability changes / too much 'changes'. (i.e. Capability change from ETOPS180 to ETOPS180)
Test Goals
:check: T02 - ETOPS Report shows every cycle for a/c with a ETOPS degredation (ETOPS 120 and No ETOPS)
:check: T03 - ETOPS Report shows all data from the previous 2 months (i.e. running the report in april shows complete february and march)
:check: T01 - ETOPS Report creates for KL a seperate report (xls) per assembly type: B787, B777 and A330
Zoom Out
The purpose of the ETOPS reliability details report is to enable Engineering to quickly find the deferred fault in Maintenix that resulted in a degradation of the ETOPS capability of an aircraft. This information is used to report to the authorities
-