Framework overlap

Does AS9100D cover ASIS SPC.1-2009?

You hold AS9100D and have been told to do ASIS SPC.1-2009. Here is how much overlaps, control by control.

29% of ASIS SPC.1-2009 you already have

AS9100D already covers about 29% of ASIS SPC.1-2009, leaving 30 of 42 controls as genuinely new work.

Already covered 2 Likely covered 10 New work 30

What is genuinely new work

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

4.3.3
Objectives and Programs
4.4.3
Communication and Warning
4.4.4
Documentation
4.4.5
Operational Control
4.4.6
Prevention and Mitigation
4.4.9
Mutual Aid and Cooperation
4.5.1
Performance Monitoring and Measurement
4.5.2
Evaluation of Compliance
4.5.3
Corrective and Preventive Action
4.5.4
Control of Records
4.6.1
Management Review Process
4.6.2
Review Input
4.6.3
Review Output
SPC1-4.1
Resilience Management System Scope
SPC1-4.2
Resilience Policy
SPC1-4.3.1
Risk Assessment and Impact Analysis
SPC1-4.3.2
Legal and Other Requirements
SPC1-4.3.3
Objectives and Targets
SPC1-4.3.4
Resilience Programs
SPC1-4.4.1
Resources, Roles, Responsibility, and Authority
SPC1-4.4.3
Communication and Warning
SPC1-4.4.4
Documentation
SPC1-4.4.5
Control of Documents
SPC1-4.4.6
Operational Control
SPC1-4.4.7
Incident Prevention, Preparedness, and Response
SPC1-4.4.8
Business Continuity and Recovery
SPC1-4.5.1
Monitoring and Measurement
SPC1-4.5.2
Evaluation of Compliance
SPC1-4.5.3
Exercises and Testing
SPC1-4.5.5
Records
Show the 12 you already have
4.3.1
Risk Assessment and Impact Analysis
4.4.1
Resources, Roles, Responsibility, and Authority
4.3.2
Legal and Other Requirements
4.4.2
Competence, Training, and Awareness
4.4.7
Emergency and Incident Response
4.4.8
Business Continuity and Recovery
4.5.5
Internal Audit
SPC1-4.4.2
Competence, Training, and Awareness
SPC1-4.5.4
Nonconformity, Corrective and Preventive Action
SPC1-4.5.6
Internal Audit
SPC1-4.6
Management Review
SPC1-A.1
Continual Improvement

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