Evaluation rests on close cooperation between the applicant, the evaluators, the facility's project leader and the certifier, with communication in text form or by telephone and web conference for status and minor points, and every participant keeps to the timetable agreed at the outset. A kick-off meeting introduces the product, the SCAS documents that will be used and the scope intended, allowing questions from the certification body and the applicant. Where individual tests cannot reasonably be run at the facility, external resources may be used under AIS-N2 and the NESAS evaluation facility rules, coordinated with the certification body no less than four weeks ahead, with an explanation of how independence is preserved; tests on the vendor's premises must be run by one of the facility's evaluators, and remote evaluation is allowed if the facility meets the AIS-N2 and facility requirements. Where the evaluation turns up a need for supplementary documents, or errors or inconsistencies in the evidence the vendor supplied, the applicant must clarify and put them right, who must provide the resources and processes to do so; this usually means repeating evaluation steps, and resulting delays must be reported to the BSI promptly. The certifier may inspect the vendor's documents at random, attend meetings and take part in evaluation activities, and the procedure may be cancelled or ended negatively for missing or insufficient evidence or a breach of impartiality.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.