How can we merge our own operating procedures with the EASA content?
Answer
This can be done in many, many ways.
At the one extreme – a very basic example, you can simply edit the XML file in Microsoft Word, adding or removing content as needed (note there would be legal waivers involved here!).
Maintaining this solution when newer versions of the eRules are published would be entirely manual, and risky too.
At the other extreme, you could import the EASA XML eRules into your preferred component-based content management solution (CCMS) – and then use the components as integrated components in you own solution.
This could involve just referencing the components from your proprietary components – or even cloning the EASA components for customisation.
In case of the use of a CCMS, it would normally be possible to automate the updating the content as new releases are released by EASA.