Project · Creator and maintainer
SystemGraph
Modelling a system as a typed component graph so cost, efficiency, availability, and fault trees come from one topology.
Updated
Context
A complex electrical system is analysed several times over, for cost, for efficiency, for availability, for safety, and each analysis is usually built on its own private copy of the architecture.
Constraint
When the topology lives separately inside each analysis, a change to the system updates some of them and not others. The fault tree and the cost model then describe two different products, and nothing in the process notices.
Contribution
I built SystemGraph, which models a system as a physical component graph with typed attributes such as cost, efficiency, reliability, and failure rates, and runs availability, efficiency, cost, fault-tree, and Pareto analysis across that single topology.
Approach
The representation is git-friendly and text-based, so architecture changes are reviewable as diffs, and the analyses are pure Python with no proprietary simulator licence in the dependency chain.
Outcome
One architecture feeds every analysis, so a change to the system reaches the safety case and the cost case at the same time.
Evidence
The work is held in a private repository containing the graph model and the analysis implementations.