Ways to eliminate, reduce, share, transfer or accept risks, and plans for exploiting opportunities, should preferably rest on known technologies or past-experience data. Risks accepted deliberately should be identified and the reasons recorded. Whenever someone proposes a solution to a risk, it should be confirmed that carrying it out will not bring unwanted effects or new risks and that the residual risk is dealt with. Contingencies for managing risk that are placed in the schedule or budget should be identified and kept separate. Particular attention should go to solutions for possible risks from interactions (in activities, processes and products or services) linking the project organization with the originating organization and with stakeholders.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.