MarAlder
commented
3 years ago A brief overview of the current activities is given below. As I said, it is mostly in the very experimental stage. However, we will only get further if we compare the results and continue to work together on an official solution.
Geometric instantiation of systems
A proposal for the geometric description of systems comes mainly from Airbus DS which is used in the Agile 4.0 project. These are initially predefined via systemElements under vehicles in the form of geometric and mass-specific properties and then linked via their uID in the actual aircraft/model/systems/genericSystems/genericSystem. A geometric transformation then takes place here.
System graphs
This proposal is driven by the Imothep project. It is in a very early status and contains some approaches which are untypical for CPACS. However, it's good to learn from every example which illustrates the needs of modeling unconventional system architectures. It adds vehicle independent systemAssumptions which are very generic definitions (basically just string and double values) linked by the system elements.
The proposal additionally adds systemArchitectures allowing to connect the geometric system components to complex graphs.
Another new feature are trajectory-specific descriptions of system components. A new analysis node systemTrajectory is introduced for this purpose. This references the standard trajectory node and supplements it with vectors that describe certain properties of individual system components along the trajectory.
Breakdown of nominal loads
A breakdown of nominal system loads is proposed from the EXACT project. This is based on the mass breakdown and describes the nominal loads broken down into individual system components.
Breakdown of system offtakes based on ATA chapters
A proposel from the AVACON project describes system offtakes with respect to ATA chapters. The originial proposal adds this information to the trajectory element directly. However, to be more flexible I moved the content to the systemAnalyses node.
Work on system definitions has been conducted in different projects, e.g. Avacon, Agile 4.0, Exact or Imothep.
Although testing of these definitions needs to continue in practice, the various approaches should be brought together into a common schema file to ensure that the developments go into the same direction.
The work in progress can be followed in the systems branch (also see network visualization) and I'll try to frequently update the corresponding online documentation.