The purpose of each deliverable should decide its level of information need, which covers the quality, quantity and granularity of geometric and alphanumeric information, using defined metrics applied throughout the project or asset and recorded in whichever of the OIR, PIR, AIR or EIR applies. It should be the least information that answers each requirement, other parties' needs included, and no more, since anything extra is waste. The risk that automatically imported objects push the level higher should be considered, and granularity of alphanumeric information matters as much as geometric.
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.