Asset digital thread from requirements to operation
Traces requirements and acceptance evidence into operations and controlled configuration changes. Original worked design example; adapt responsibilities, thresholds and assumptions to your system.
What this template contains
- Graph
- Directed
- Edges
- 11
- Source
- 25 lines
Make it your own.
digraph G {
graph [rankdir=LR, bgcolor="transparent", pad="0.3", nodesep="0.45", ranksep="0.8"];
node [shape=box, style="rounded,filled", fillcolor="#edf4fa", color="#47728d", fontname="Arial", fontsize=12, margin="0.14"];
edge [color="#64748b", fontname="Arial", fontsize=10];
req [label="Owner requirements"];
design [label="Design model"];
spec [label="Performance specification"];
build [label="Construction records"];
test [label="Commissioning evidence"];
asset [label="Asset register"];
ops [label="Maintenance system"];
sensor [label="Condition observations"];
change [label="Controlled change"];
req -> design [label="constrains"];
req -> spec [label="defines criteria"];
design -> build [label="issued information"];
spec -> test [label="acceptance basis"];
build -> test [label="as-built evidence"];
test -> asset [label="accepted configuration"];
asset -> ops [label="maintainable assets"];
sensor -> ops [label="condition signal"];
ops -> change [label="improvement request"];
change -> design [label="approved revision"];
change -> asset [label="configuration update"];
}