Your browser does not support JavaScript! Skip to main content
Free 30-day trial DO-178C Handbook RapiCoupling Preview DO-178C Multicore Training Multicore Resources
Rapita Systems
 

Industry leading verification tools

Rapita Verification Suite (RVS)

RapiTest - Functional testing for critical software RapiCover - Low-overhead coverage analysis for critical software RapiTime - In-depth execution time analysis for critical software RapiTask - RTOS scheduling visualization RapiCoverZero - Zero-footprint coverage analysis RapiTimeZero - Zero-footprint timing analysis RapiTaskZero - Zero-footprint event-level scheduling analysis RVS Qualification Kits - Tool qualification for DO-178 B/C and ISO 26262 projects RapiCouplingPreview - DCCC analysis

Multicore Verification

MACH178 - Multicore Avionics Certification for High-integrity DO-178C projects MACH178 Foundations - Lay the groundwork for A(M)C 20-193 compliance Multicore Timing Solution - Solving the challenges of multicore timing analysis RapiDaemon - Analyze interference in multicore systems

Other

RTBx - The ultimate data logging solution Sim68020 - Simulation for the Motorola 68020 microprocessor

RVS Software Policy

Software licensing Product life cycle policy RVS Assurance issue policy RVS development roadmap

Industry leading verification services

Engineering Services

V&V Services Data Coupling & Control Coupling Object code verification Qualification Training Consultancy Tool Integration Support

Latest from Rapita HQ

Latest news

Rapita partners with Asterios Technologies to deliver solutions in multicore certification
SAIF Autonomy to use RVS to verify their groundbreaking AI platform
RVS 3.22 Launched
Hybrid electric pioneers, Ascendance, join Rapita Systems Trailblazer Partnership Program
View News

Latest from the Rapita blog

What does AMACC Rev B mean for multicore certification?
How emulation can reduce avionics verification costs: Sim68020
Multicore timing analysis: to instrument or not to instrument
How to certify multicore processors - what is everyone asking?
View Blog

Latest discovery pages

Military Drone Certifying Unmanned Aircraft Systems
control_tower DO-278A Guidance: Introduction to RTCA DO-278 approval
Picture of a car ISO 26262
DCCC Image Data Coupling & Control Coupling
View Discovery pages

Upcoming events

IEEE SMC-IT/SCC 2025
2025-07-28
DASC 2025
2025-09-14
DO-178C Multicore In-person Training (Fort Worth, TX)
2025-10-01
DO-178C Multicore In-person Training (Toulouse)
2025-11-04
View Events

Technical resources for industry professionals

Latest White papers

Mitigation of interference in multicore processors for A(M)C 20-193
Sysgo WP
Developing DO-178C and ED-12C-certifiable multicore software
DO178C Handbook
Efficient Verification Through the DO-178C Life Cycle
View White papers

Latest Videos

Requirements traceability with RapiTest and Polarion ALM
How to make AI safe in autonomous systems with SAIF
Rapita Systems - Safety Through Quality
Simulation for the Motorola 68020 microprocessor with Sim68020
View Videos

Latest Case studies

GMV case study front cover
GMV verify ISO26262 automotive software with RVS
Kappa: Verifying Airborne Video Systems for Air-to-Air Refueling using RVS
Supporting DanLaw with unit testing and code coverage analysis for automotive software
View Case studies

Other Resources

 Webinars

 Brochures

 Product briefs

 Technical notes

 Research projects

 Multicore resources

Discover Rapita

Who we are

The company menu

  • About us
  • Customers
  • Locations
  • Partners & Distributors
  • Research projects
  • Contact us
  • Careers
  • Working at Rapita

Industries

  Civil Aviation (DO-178C)   Automotive (ISO 26262)   Military & Defense   Space

US office

+1 248-957-9801
info@rapitasystems.com Rapita Systems, Inc., 41131 Vincenti Ct., Novi, MI 48375, USA

UK office

+44 (0)1904 413945
info@rapitasystems.com Rapita Systems Ltd., Atlas House, Osbaldwick Link Road, York, YO10 3JB, UK

Spain office

+34 93 351 02 05
info@rapitasystems.com Rapita Systems S.L., Parc UPC, Edificio K2M, c/ Jordi Girona, 1-3, Barcelona 08034, Spain
Back to Top Contact Us

What does AMACC Rev B mean for multicore certification?

Sam Thompson, Daniel Wright
2025-07-07

The U.S. Army Combat Capabilities Development Command released a new version (Rev B) of AMACC, the Army Military Airworthiness Certification Criteria, in November 2024.

While the document presents the airworthiness criteria for US Army aircraft, there are some great lessons from the guidance that can be applied to multicore certification in a wider context, including A(M)C 20-193, and we thought we'd share them. 

A handy to-do list for multicore certification

The most striking difference between AMACC Rev B and A(M)C 20-193 is the level of detail given in the guidance. 

While the objectives in AMACC Rev B are very similar to those in A(M)C 20-193, the former doesn’t just list high-level objectives, it clearly lists activities too. 

A(M)C 20-193 specifies 9 high-level objectives and expects you to fill in the blanks of how to meet them. AMACC Rev B, meanwhile, presents no fewer than 163 individual requirements imposed on a wide range of deliverables for multicore certification. This enumeration of detailed requirements provides a concrete to-do list for certification, and as an added bonus, the guidance specifies where each part of each activity should be documented.

AMACC Rev B has tabular actionable activities
AMACC Rev B includes a table-based representation of activities, clearly identifying in which document each activity should be documented (Source: AMACC Rev B)

This detailed approach should be much easier for organizations to follow than the low-detail approach in A(M)C 20-193, especially for organizations new to the complexities of multicore certification.

The detailed breakdown of activities in AMACC Rev B is very similar to that in the planning documents in MACH178 Foundations, which also includes procedures for meeting objectives, as well as handy checklists, templates and white papers to support multicore certification.

Making things clear

The level of detail provided in AMACC Rev B helps in other ways too. There’s a lot of nuance in A(M)C 20-193, which may not be apparent the first time you read it. For example, A(M)C 20-193’s MCP_Resource_Usage_4 objective requires that multicore mitigations are planned for, verified and reviewed, but it only does so implicitly.

This could easily be missed on a first read through the document and a first draft of multicore planning documents. This should be picked up at SOI#1, but if it’s missed, more effort may be needed to update plans after the certification milestone.

Another example of how AMACC Rev B makes things clear relates to identifying interference channels. A(M)C 20-193 only specifies that this is needed at DALs A and B (MCP_Resource_Usage_3 objective), and not at DAL C. However, identifying interference channels is required to be able to characterize the impact of interference on hosted software, which is required for DAL C (MCP_Software_1). While this isn’t a contradiction – the impact is that you’ll need to identify channels but not need to include documentation of them in your submission – the guidance can confusing on this point.

The additional clarity in AMACC Rev B really helps reduce ambiguity and should ultimately lead to more efficient certifications. This is obviously a good thing, and that’s why we provided more clarity wherever possible when developing MACH178 Foundations, breaking down each objective into a list of sub-objectives that are individually actionable, and identifying where each should be documented in a DO-178C process.

MACH178 Foundations
MACH178 Foundations includes guidance for developing A(M)C 20-193 certification evidence activities, breaking the objectives down into a list of actionable activities

Conclusion

Fundamentally, there is a huge overlap in the multicore objectives of A(M)C 20-193 and AMACC Rev B, but the latter is presented in a way that’s much easier to follow. An itemized list of requirements, presented clearly along with expectations on where evidence is to be documented, can all help provide clarity on what’s needed and when, even to an organization new to multicore certification.

If you’re beginning to plan for A(M)C 20-193 certification, it may be a good idea to review the objectives and expand them into a list of activities reminiscent of that presented in AMACC Rev B. Or you could just use MACH178 Foundations, in which we’ve done that for you already, as well as providing templates and checklists for each activity.

DO-178C webinars

DO178C webinars

White papers


Mitigation of interference in multicore processors for A(M)C 20-193
Sysgo WP
Developing DO-178C and ED-12C-certifiable multicore software
DO178C Handbook
Efficient Verification Through the DO-178C Life Cycle

A Commercial Solution for Safety-Critical Multicore Timing Analysis
  • Solutions
    • Rapita Verification Suite
    • RapiTest
    • RapiCover
    • RapiTime
    • RapiTask
    • MACH178

    • Verification and Validation Services
    • Qualification
    • Training
    • Integration
  • Latest
  • Latest menu

    • News
    • Blog
    • Events
    • Videos
  • Downloads
  • Downloads menu

    • Brochures
    • Webinars
    • White Papers
    • Case Studies
    • Product briefs
    • Technical notes
    • Software licensing
  • Company
  • Company menu

    • About Rapita
    • Careers
    • Customers
    • Distributors
    • Industries
    • Locations
    • Partners
    • Research projects
    • Contact
  • Discover
    • Multicore Timing Analysis
    • Embedded Software Testing Tools
    • Worst Case Execution Time
    • WCET Tools
    • Code coverage for Ada, C & C++
    • MC/DC Coverage
    • Verifying additional code for DO-178C
    • Timing analysis (WCET) & Code coverage for MATLAB® Simulink®
    • Data Coupling & Control Coupling
    • Aerospace Software Testing
    • DO-178C
    • Meeting DO-178C Objectives
    • AC 20-193 and AMC 20-193
    • Meeting A(M)C 20-193 Objectives
    • Certifying eVTOL
    • Certifying UAS

All materials © Rapita Systems Ltd. 2025 - All rights reserved | Privacy information | Trademark notice Subscribe to our newsletter