The appointing party reviews the model it received under 5.7.1 for compliance with the production methods and procedures, considering its AIR (especially on branch N), the EIR (ISO 19650-3) together with the acceptance criteria it gave the lead, the delivery team's MIDP (branches M and P), the level of information need set through 5.1.6 and 5.4.4, and what was actually delivered against all of these. If the review succeeds, the model is accepted as a CDE deliverable and the appointing party either tells the lead to mark every container published (M, P) or marks them published itself (N). If it fails, the reasons are recorded, the model is rejected, and the appointing party either tells the lead to correct and resubmit (M, P) or identifies the changes and gets the previous appointing party or owner to make them, or makes them itself (N). Accepting or rejecting the model as a whole is recommended.
This control maps to 1 controls across 1 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 1 it maps to, and the evidence behind each claim, over MCP and REST.