EASA NPA 2022-11: farewell to List of Effective Pages
EASA has recently released NPA 2022-11 for public consultation. The Agency has finally recognised that the List of Effective Pages (LEP) has become obsolete due to the widespread use of electronic documentation. Below you'll see the proposed amendments to AMC3 ORO.MLR.100(a), where LEP is removed, and a general text is added to point 0.2(b).
The hearing deadline for this NPA is 20 March 2023, and if all goes according to plan, adoption by the EU Commission and subsequent EASA Decision will be effective by 1Q2025.
At Widerøe, we stopped using LEPs in our flight ops manuals two years ago as we realised that they were rarely used and, at the same time, added unnecessary volume to our manuals. Worth mentioning the cost we had with LEPs, as our previous documentation service provider charged us per page. Nobody has ever complained about this decision, nor has it been considered a finding during audits.
The provisions of EASA NPA 2022-11 may result in less use of Web Manuals's LEP module in the near future. On the other hand, the LEP module has an interesting feature. If set by the Editor, the LEP provides the reader with a link to open the CAA's acceptance letter, provided the letter is uploaded upon publication. This is an excellent feature for traceability purposes and may be advantageous during audits. It would be, therefore, wise to add it to either the Change Log or the Revision Summary module.
Comments
Hello Bruno,
Thank you so much for this heads-up!
Would you prefer the acceptance document to be added to a standalone module or on one of the other ones?
Hi Jody,
A standalone module would be even better.
Best regards.
Hi Bruno.
We have discussed this internally, and I would like to swing one more possible solution by you.
Why put it in a module, when we can have it in the UI outside of the document.
Example click the overflow menu on a document and be able to choose to see the Signed approval.
Would this work better than a module? Then it is not limited to a page in the document.
Hi Stefan,
I believe you're mentioning the existing function below:
If yes, this is already good and we've informed our users about it. If no, then I don't know what overflow menu you're referring to.
In my proposal, I just thought it would be easy to implement it in a module since you already have the code recipe in the LEP module.
Exactly Bruno.
My thought was that this had potential to be applied across the board, also to devices.
Since the document is uploaded outside of the module, we are considering completely removing it from modules in the future, unless you tell me it absolutely needs to exist in the document itself.
Hi Stefan. No, it doesn’t need to be in the document, not for us at least.
Cheers!
Please sign in to leave a comment.