Framework overlap

Does AS9100D cover ISO 55001:2014?

You hold AS9100D and have been told to do ISO 55001:2014. Here is how much overlaps, control by control.

95% of ISO 55001:2014 you already have

AS9100D already covers about 95% of ISO 55001:2014, leaving 1 of 21 controls as genuinely new work.

Already covered 10 Likely covered 10 New work 1

What is genuinely new work

Nothing in AS9100D reaches these. This is the list to scope.

5.2
Policy
Show the 20 you already have
10.1
Nonconformity and corrective action
10.3
Continual improvement
4.1
Understanding the organization and its context
5.1
Leadership and commitment
5.3
Organizational roles, responsibilities and authorities
7.6
Documented information
8.1
Operational planning and control
9.1
Monitoring, measurement, analysis and evaluation
9.2
Internal audit
9.3
Management review
10.2
Preventive action
4.2
Understanding the needs and expectations of stakeholders
4.3
Determining the scope of the asset management system
4.4
Asset management system
6.1
Actions to address risks and opportunities for the asset management system
6.2
Asset management objectives and planning to achieve them
7.2
Competence
7.4
Communication
8.2
Management of change
8.3
Outsourcing

How this is calculated

Already covered means a mapping runs from a control in AS9100D 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