|
Re: FMECA [message #1833002 is a reply to message #1832995] |
Wed, 30 September 2020 13:12 |
Jean-Luc Voirin Messages: 8 Registered: February 2020 |
Junior Member |
|
|
Here are some suggestions that might or not apply to your context:
First you can define specific properties for any model element, either using PropertyValues, or via developing a new extension viewpoint in Capella. This way, you could consider defining failure modes on physical components or links, reliability or failure rates figures, and if needed compute resulting reliability figures for example.
Second, you can use the advanced definition of modes & states in Arcadia: for example,
- defining failure configurations that list components failing in one given situation
- defining state machines describing the dynamic evolution of failures
- defining mode machines describing the expected behaviour of the system, functions and functional chains expected to be available in these modes
- defining dynamic failure and recovery scenarios that would describe time-related transitions between modes, between states, and triggers/consequences of each of them
- then confront failure states and behavioural modes and their consequences, by comparing related configuration contents (given that for example, if a physical resource node component fails, then functions that are implemented by behavioural components hosted by the component are likely no more available)
More on this is described in Arcadia book, chapter 14. System Supervision, States and Modes
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04144 seconds