The project organization should identify what information it needs, set up a documented information management system, and identify internal and external information sources, managing information with the needs of the project organization and of the originating organization in mind. Processes should be set up that define controls for preparing, collecting, identifying, classifying, updating, distributing, filing, storing, protecting and retrieving information, and for its retention period and disposal. Documented information should record the conditions at the time an activity was recorded, so its validity and relevance can be checked before other projects use it. Information security should be appropriate, covering confidentiality, availability and integrity. Information should be relevant to recipients, clearly presented and distributed strictly on schedule. Every agreement affecting project performance, informal ones included, should be formally documented. Meeting rules and guidelines should suit the type of meeting; agendas should go out in advance and name for each item whose attendance is needed; minutes should record decisions, open issues and agreed actions with due dates and owners, and reach relevant stakeholders within an agreed time. Data, information and knowledge should be used by the project organization in setting and meeting its objectives, and managers in the originating organization and in the project organization should assess the benefit gained from using information so its management can be improved (clause 8). Simplicity should be the aim for the information management system.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.