Tailoring ARCADIA/Capella to ECSS + ECSS-compliant document generation?

Capella
1

Hi everyone,

I’m currently working on a space project where we are trying to align our system engineering approach with the ECSS standards, while using Capella with the ARCADIA method as our main MBSE tool.

At the moment, this is still quite exploratory and not fully structured, so I’m looking for guidance and best practices.

I have two main questions:

1) Tailoring ARCADIA to ECSS

Has anyone experience with tailoring ARCADIA to better fit ECSS processes (e.g. ECSS-E-ST-10, ECSS-M-ST-10, or related standards)?

I’m especially interested in:

  • Mapping ARCADIA layers (OA, SA, LA, PA) to ECSS lifecycle phases and reviews (SRR, PDR, CDR, etc.)

  • Integrating ECSS-style requirements, verification, and traceability

  • Handling ECSS-specific artifacts like Design Definition Files (DDF) or Design Justification Files (DJF) within a Capella-based workflow

Are there any papers, guidelines, or case studies on this?

2) ECSS-compliant document generation from Capella

We’re also looking into generating ECSS-style documentation from the model (or at least semi-automating it).

Does anyone have experience with:

  • Generating structured documents aligned with ECSS deliverables

  • Maintaining consistency between model and documents (single source of truth approach)

Any pointers to literature, examples, toolchains, or real project experiences would be extremely helpful.

Thanks a lot in advance!

1 Like