The organization should put in place an incident management structure that carries out the tasks the incident objectives call for, with five basic functions: command (authority and control, objectives, structure and responsibilities, requesting resources and releasing them); planning (gathering and assessing incident information and intelligence and sharing it promptly, status reports covering the resources and staff assigned, and preparing and recording the incident action plan); operations (tactical objectives, reducing hazards, protecting people, property and the environment, bringing the incident under control and handing over to recovery); logistics (support and resources for the incident, facilities, transport, supplies, maintenance of equipment, fuel, food and medical care for incident staff, and communications and IT support); and finance and administration (procurement, compensation and claims, time and costs, which in a small incident may not need a function of its own). At every level of incident management it should consider the functions of planning, of operations, of logistics and of finance and administration, and define and document the minimum number of staff needed to start incident management straight away and keep it running without a break.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.