Dear all,
I’m new to Arcadia/Capella and am trying to use it to model an existing particle accelerator using Capella 7.0.1. The model would be used for the following purposes:
- Identify functional chains (creating/managing unique tags for each functional chain occurrence. These tags are intended to be included on the labels of the physical devices involved in the functional chain)
- Support change management
- Support issue handling
I would therefore like to do it bottom-up and start with the Product Architecture. The system is build of many repeating sections of only few types, each section type containing the same physical elements and having the same beviour/functions. Therefore, I would like to model each section type only once (and be allowed to make changes to those models which are automatically reflected in the parts). In another view I would like to show the full system will all occurrences of these sections and how they are physically connected to each other.
I managed to setup a project with the “allow reuse of components” property set, but I’m a bit lost in which diagram to use for what (hence it’s more of a modeling approach question, rather than a tool question). For example: If I create a PCBD, I can create new “child” Node PCs, but the link “Contained in” is not available. Instead, it’s now “Create part”. However, while I would like to focus in this diagram on the component breakdown, not the part instantiation.
Similar, I would like to be able to make a PAB on a component (i.e., section type) to model the physical and flow ports. But it seems I can only include parts in a PAB.
Am I trying to do something Arcadia is not suitable for, or am I using the wrong approach? Some general guidance on how to model a system like this would be appreciated. The example’s I’ve found online so far seem to focus more on the single/few occurrence situation.
Thanks in advance,
Sebastiaan