38% of ISO 22000:2018 you already have
AS9100D:2016 already covers about 38% of ISO 22000:2018, leaving
34 of 55 controls as genuinely new work.
Already covered 7
Likely covered 14
New work 34
What is genuinely new work
Nothing in AS9100D:2016 reaches these. This is the list to scope.
10.3Update of the food safety management system
4.1Understanding the organization and its context
4.3Determining the scope of the food safety management system
4.4Food safety management system
5.2.1Establishing the food safety policy
5.2.2Communicating the food safety policy
7.1.5Externally developed elements of the food safety management system
7.4.2External communication
7.4.3Internal communication
7.5.2Creating and updating
7.5.3Control of documented information
8.5.4Hazard control plan (HACCP/OPRP plan)
8.6Updating the information specifying the PRPs and the hazard control plan
8.8Verification related to PRPs and the hazard control plan
8.8.2Analysis of results of verification activities
8.9Control of product and process nonconformities
8.9.4Handling of potentially unsafe products
9.1Monitoring, measurement, analysis and evaluation
9.3.2Management review input
9.3.3Management review output
Show the 21 you already have
10.1Nonconformity and corrective action
5.1Leadership and commitment
5.3Organizational roles, responsibilities and authorities
6.1Actions to address risks and opportunities
7.1.6Control of externally provided processes, products or services
7.5Documented information
8.1Operational planning and control
10.2Continual improvement
4.2Understanding the needs and expectations of interested parties
6.2Objectives of the food safety management system and planning to achieve them
8.2Prerequisite programmes (PRPs)
8.4Emergency preparedness and response
8.4.2Handling of emergencies and incidents
8.5.1Preliminary steps to enable hazard analysis
8.5.3Validation of control measure(s) and combinations of control measures
8.7Control of monitoring and measuring
9.1.2Analysis and evaluation
How this is calculated
Already covered means a mapping runs from a control in AS9100D:2016 to that control. Likely
covered means no direct mapping exists but both frameworks map to the same control in a third
standard. New work means neither. We keep those separate rather than adding them into one
friendlier number, because blending them would present a two-hop inference as a verified
fact.
Coverage is not symmetric.
Run it the other way and you will get a
different number; both are correct.
From 332,959 cross-framework control
mappings across 723 frameworks, 531 of them verified against
their source documents. It does not tell you that you are compliant: a mapped control means
the two standards ask for the same thing, not that you have done it.
Try another pair ยท
Today's edition