Failure Category & Fault Priority Field, are BASELINE defined by Fault Definition and not modifiable on ACTUALSFault Type field, is BASELINE & ACTUAL modifiableCan IFS advise is a Parent / Child relation between Failure Category & Failure type exist ? How IFS would recommend tio uses those type of fields with Fault Definition?And finalys how to set up Fault Priority to have them reflecting a priority according to the Fault Definition?
Increased use of FD get more frequent FD need to be removed.A FD cannot be obsoleted or deleted from the CS it was created.Today the FD are renamed starting by "OBSOLETED" which is not correct for end user in the GUI. Potential solution identified are :RSTAT2 the FD? Move the FD into an unused organisation? Any other solution?
When engineering users flag N/A more than 20 A/C at same time on INITIALIZE REF DOC page generates "error message", which is in fact a "message built by IFS due to technical limitations "URL exeeded the maximum lenght".Please see attached docDoes other airlines have the same experience?If Yes, an IDEA could be raised to support a system improvement for Large fleet administration.
Hello, We have the possibility to go to a Barcode with an hyperlink with the following format:http://mtx.afklmdomain.com/maintenix/servlet/ScanBarcode?aBarcodeScan=TRFX123456789&aReturnToPage=/Do you have similar hyperlink definition to go directly to a document in the baseline?like a Refdoc, a Requirement code…? by definition the baseline documents do not have Barcodes. Thanks
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
