15 templates
Reliability block diagram templates
Reliability block diagrams with the reliability actually computed: series, parallel, k-out-of-n and standby arrangements over blocks carrying R, MTBF or failure rate, evaluated to system reliability, MTTF and availability at a chosen mission time. Redundancy that buys nothing shows up as a branch that moves the system number by a rounding error — which is the entire point of drawing one.
RBD — Data-Centre Power Train
Utility feed backed by a cold-standby generator pair, 2N UPS strings and 2-of-3 PDUs, computing annual system reliability, MTTF and availability for the rack busway.
ArchitectureRBD — Fly-by-Wire Pitch Channel
Triplex air data, duplex flight control computers and two independent hydraulic-plus-actuator lanes over a year of utilisation, ranking which redundancy actually moves the loss-of-pitch-control number.
Risk & ReliabilityRBD — Subsea Multiphase Boosting Station
Six-month intervention window for a subsea boosting station: shared umbilical, dual control modules and two full VSD-plus-pump trains, with repair times set by vessel mobilisation.
Operations & OpsRBD — GEO Ku-Band Payload
Ten-year design life of a geostationary communications payload: cold-standby receiver, 3-of-4 travelling-wave tube amplifiers, output multiplexer and a cross-strapped TT&C transponder pair.
Scientific PlotsRBD — Hospital Medical Oxygen Supply
HTM 02-01 style piped oxygen supply with a warm-standby chain from VIE to reserve vessel to emergency cylinder manifold, plus duplicated alarm panels, computing annual supply reliability.
Risk & ReliabilityRBD — 25 kV Rail Traction Chain
Six-month traction availability for a regional line: grid supply point, paralleled feeder substations, overhead line, pantograph and a 3-of-4 traction converter group on the unit.
Operations & OpsRBD — Offshore Wind Turbine Drivetrain
Annual reliability and availability of an offshore turbine drivetrain, where the 2-of-3 pitch group and the array cable's 60-day repair time pull the numbers in opposite directions.
Operations & OpsRBD — Dual-Carrier WAN Path
One-month SLA window on a payments WAN path: two independent edge-router-plus-carrier legs with an LTE bearer, a firewall cluster, core fabric and anycast DNS.
ArchitectureRBD — Autonomous Vehicle Perception Chain
Five hundred operating hours of an AV safety chain: redundant supplies, a 2-of-3 sensor vote in which the camera slot is itself a pair, hot-standby perception compute and dual brake actuation.
Risk & ReliabilityRBD — Municipal Water Treatment Works
Annual potable-output reliability of a treatment works: 3-of-4 raw water pumps, duplicated filter trains, UV, and a warm-standby chlorine dosing pair with an explicit dormancy factor.
Operations & OpsRBD — Earth Observation Payload Chain
Five-year mission reliability for an optical imaging smallsat, chaining a cold-standby computer pair, redundant reaction wheels flown four-of-five and a duplex X-band downlink behind a single-string telescope.
ArchitectureRBD — Potable Water Pumping Station
Annual availability of a district pumping station with a two-of-three duty pump set, showing the 11 kV incomer as the weakest block on site and the rising main as an unavoidable series element.
Operations & OpsRBD — Radiotherapy Treatment Chain
One year of a linear accelerator bunker treated as a delivery chain, where the magnetron, multileaf collimator and single treatment couch are strictly in series behind a duplex record-and-verify system.
Risk & ReliabilityAvailability model — payments API across three AZs
Reliability block diagram of a regional payments API — Route 53, ALB, 2-of-3 AZ stacks, Aurora storage with a hot-standby writer and a third-party card processor — solving to 99.938% steady-state availability and naming the ALB and the processor as the two blocks that cap it.
Operations & OpsAvailability budget — regional API against a 99.99 % monthly SLO
Reliability block diagram of a three-AZ regional payments API stated in MTBF and MTTR, computing composite availability against a 99.99 % monthly SLO and ranking which block owns the failure — the arithmetic an SRE or architect must show before committing to an availability target.
Architecture