The applicant proposes the means of compliance in the PHAC. Submission of the PHAC, the verification plan and any other data requested should happen when design changes still have little programme effect; authority issues on planning are resolved; agreement on the PHAC is obtained; and liaison continues through the design and certification cycle with issues resolved promptly. Where the airframer or another customer handles liaison, the relationship is set out in the PHAC and contact goes through the applicant, who ensures data reaches the authority; where embedded items come from subcontractors, the plan says which data they supply. The PHAC and verification plan may sit inside the top-level certification plan.
This control maps to 2 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.