Hierarchical requirements baselining for automotive SPICE compliance

ALM PTC Codebeamer
, , , , , , , ,
1

Automotive suppliers implementing ASPICE CL3+ processes face significant compliance tracking challenges with multi-level baseline management and impact analysis automation. Our organization recently completed a successful implementation using codebeamer ALM cb-24 that addresses these challenges through hierarchical requirements baselining with full traceability and automated SPICE export capabilities.

Challenge Context: We needed to baseline requirements across 4 hierarchy levels (System → Subsystem → Component → Module) while maintaining full traceability to test cases, work products, and change requests. Manual baselining was causing audit failure risk due to inconsistent versioning and broken trace links after baseline creation.

The multi-level baseline structure required capturing dependencies across hierarchy levels, so when we baseline System Requirements v2.0, all child subsystem and component requirements needed to be baselined atomically. Our initial API automation attempts failed because we couldn’t properly handle the cascade:

<baseline name="SYS_REQ_v2.0" scope="hierarchical">
  <item id="SYS-001" version="3"/>
  <!-- Child items not captured -->
</baseline>

This resulted in compliance tracking gaps and audit findings. How we solved it using cb-24’s enhanced baseline capabilities is detailed below.

2

For SPICE export, are you using the standard XML export format or did you customize it? Our auditors require specific formatting and metadata that doesn’t quite match codebeamer’s default export structure. We’ve been post-processing the XML with XSLT transformations, but it feels fragile.

3

We’re implementing a similar solution for ISO 26262 compliance. One question about the API automation - how do you handle baseline creation permissions and approval workflows? In our organization, only specific roles can create official baselines, and they require manager approval before being finalized. Does cb-24 support workflow-controlled baseline creation, or did you implement that logic externally?

4

Impact analysis is automated through cb-24’s baseline comparison API combined with traceability queries. When creating a new baseline, we first run a comparison against the previous baseline to identify changed items. Then we execute a trace query starting from those changed requirements, following all outgoing trace links (satisfies, verifies, depends-on) to find impacted items. This generates an impact analysis report that feeds directly into our change control board review process. The entire workflow is automated via REST API and takes about 30 seconds for a project with 2000+ requirements.