Developed during planning, the federation strategy explains how the information model is split into sets of information containers (by functional, spatial or geometric views). In detailed planning it is worked up into information container breakdown structures that show how containers relate and how interfaces are managed; these are set for different purposes and scaled to complexity, and are updated as task teams are appointed and as work moves between asset management and delivery. Containers are linked to task teams, with each container given to a single task team. The strategy is agreed jointly, owned by people who grasp the strategic approach, and shared with every organization, taking into account the security consequences of circulating it.
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.