Automotive suppliers in Germany face two pressures at once: software volume per vehicle keeps rising, and OEMs expect demonstrated process capability, usually assessed against Automotive SPICE. A remote engineering team can add capacity, but only if its work fits into the supplier's assessed process. If it does not, the next ASPICE assessment will find gaps in traceability, configuration management or review evidence, and these gaps are attributed to you, not to the external team. The good news is that ASPICE describes outcomes and work products, not locations. A remote team that works inside your process, with your tools and your definitions, can contribute to the same capability level as an internal team. This analysis covers how to set that up.

The numbers behind the capacity problem

The pressure is visible in the industry's own figures. According to the VDA, the German automotive industry spent 59.4 billion euros on research and development in 2024, including its sites abroad, 2 percent more than in the previous year. Over the same period, average employment fell by 5.3 percent to around 732,000 in 2025. More engineering work is being carried by fewer people. The IT labour market does not absorb the gap easily: Bitkom counted 79,000 unfilled IT positions in Germany in its September 2026 study, and 97 percent of companies with IT roles reported difficulty filling them. On the supply side, NASSCOM estimates that India's technology industry employed 5.8 million people in fiscal year 2025 and generated 55.7 billion US dollars in engineering, research and development revenue. The capacity exists. The question this analysis answers is how to use it without weakening your assessed process.

What ASPICE expects

Automotive SPICE version 4.0 was published in late 2023. It added process groups for hardware engineering, machine learning engineering and validation, and updated generic practices. For software work, the processes most affected by an external team are:

  • SWE.1 to SWE.6: software requirements analysis, architectural design, detailed design and unit construction, unit verification, integration and integration verification, and software verification.
  • SUP.1 quality assurance, SUP.8 configuration management, SUP.9 problem resolution management, SUP.10 change request management.
  • MAN.3 project management.
  • On the customer side, ACQ.4 supplier monitoring, which applies to how you monitor the external team.

Many OEMs expect capability level 2 for the processes in the assessment scope, meaning work is planned, monitored and adjusted, and work products are managed. Level 2 is where external teams most often cause problems, because planning and work product control cross organisational boundaries.

Mapping work to the remote team

ASPICE processSupplier (your organisation)Remote team
SWE.1 RequirementsOwns, derives from system requirementsReviews for consistency and testability
SWE.2 ArchitectureOwns, approvesDrafts component-level architecture within the agreed scope
SWE.3 Detailed design and unit constructionReviewsProduces
SWE.4 Unit verificationDefines strategy and criteriaProduces tests, static analysis, coverage
SWE.5 IntegrationOwns integration strategyIntegrates in CI, produces SIL results
SWE.6 Software verificationOwns, approves resultsAutomates and executes
SUP.8 Configuration managementOwns system and baselinesWorks inside it
SUP.9 and SUP.10Owns processesExecutes within them

The rule is the same as in other regulated domains: decisions, baselines and approvals stay with you, the remote team produces work products and the evidence of how they were made. Bidirectional traceability, from requirements through architecture and code to tests, must be maintained in your tool, not reconstructed from the external team's records.

AUTOSAR: what splits well

AUTOSAR Classic and AUTOSAR Adaptive have different characteristics for remote work.

  • Application software components (Classic). Well suited. Components can be developed against the RTE interface, tested in model-in-the-loop and software-in-the-loop environments, and integrated in CI.
  • Basic software configuration (Classic). Feasible, but dependent on access to the commercial configuration toolchain and its licences, and on the ECU extract from the system description. Clarify licence terms for remote users early.
  • Adaptive applications. Well suited. Service-oriented applications on POSIX-based platforms can be developed and tested largely on standard hardware or virtual targets.
  • Hardware bring-up, timing analysis on target, HIL testing. Requires hardware. Keep on site, or provide a remotely accessible HIL setup with scheduling and logging.

Functional safety and cybersecurity interfaces

If the software has an ASIL under ISO 26262, the external team's work is part of a distributed development. ISO 26262-8 expects a development interface agreement (DIA) that defines responsibilities for safety activities and work products between the parties. Even if your organisation keeps all safety decisions, the DIA should record which work products the external team produces and how they are verified.

Cybersecurity follows a similar logic. UN Regulation No. 155 has applied to all new vehicles registered in the EU since July 2024 and requires the vehicle manufacturer to manage cyber risks across the supply chain. In practice OEMs pass requirements derived from ISO/SAE 21434 to their suppliers, and you pass the relevant parts on to the remote team: secure coding rules, vulnerability management, and a cybersecurity interface agreement that clarifies responsibilities.

Making ACQ.4 work in practice

Supplier monitoring is easiest when it uses the same data as your internal project management:

  1. Joint planning in your project tool, with the remote team's work packages visible in the same backlog.
  2. Work product reviews performed by your engineers on a defined sample, recorded in your review tool.
  3. Metrics agreed in advance: review findings per work product, defect escape rate after integration, adherence to baseline schedule.
  4. Regular joint reviews, documented with decisions and actions.
  5. Escalation path and change request handling defined in the contract.

Gaps assessors typically find with external teams

  • Unit verification results exist in the external team's CI but are not linked to the baseline in your configuration management.
  • Review records are informal chat approvals rather than documented reviews with findings.
  • Changes requested informally by your engineers bypass SUP.10 and appear in code without a change request.
  • The external team's plan is a separate spreadsheet, so MAN.3 evidence is split across two systems.

Each of these is avoidable by setting up tool access and process training in the first sprint, before productive work starts.

Contract structure

Under a Werkvertrag, the Leistungsbeschreibung should list the ASPICE work products to be delivered per release (for example software detailed design, unit verification results, integration verification results), the tools in which they are created, and the acceptance criteria. Acceptance (BGB §640) then rests on complete work products, which is exactly what an assessor will look for later.

Assessment readiness checklist

  • Remote team trained on your process descriptions, with training records.
  • All work products stored in your configuration management system.
  • Traceability links created by the remote team as they work, not at the end.
  • Review evidence for remote work products, performed and recorded.
  • DIA and cybersecurity interface agreement signed where applicable.
  • ACQ.4 monitoring records available.

This article is general information and not legal advice. Contractual and regulatory obligations depend on your OEM agreements and should be reviewed by qualified advisors.

ASPICE rewards suppliers whose external capacity is indistinguishable, in its evidence, from internal capacity. niogod™ pods are built to work inside your assessed process under a Werkvertrag with Abnahme per sprint, with a German-speaking Projektleiter facing your project and quality leads and a Senior Consultant accountable for work product completeness, following our 72-hour protocol. If an assessment or a new SOP sits on your roadmap for next year, it is a conversation worth having early.

Talk to niogod™

Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.

Book consultation
← All insights