DC Solutions · Calculator · Critical spares

Critical spares readiness for data-center M&E equipment

Which spare parts to stock, how many and where: FMECA criticality, supply readiness, newsvendor stock level, two-echelon allocation, supplier risk, last-time-buy and Kraljic sourcing, for one part or a fleet. RZEngine computes every module in your browser.

engine RZEngine spares · analysis SP-000000-001 · created — · scenario Production DC (Base Case)

DC Solutions → Calculator → Critical spares

Workflow Overview — how the 27 modules connect (analytical → operating engine → supply chain → reference)
ANALYTICAL OPERATING ENGINE SUPPLY CHAIN REFERENCE M1 · Criticality FMECA M2 · Readiness Gauge M3 · Optimal Stock Q* M4 · MEIO 2-Echelon M4b · Hub Positioning M5 · Supplier Risk M6 · LTB / DMSMS M7 · Kraljic Matrix M8 · Monte-Carlo M9 · Sensitivity Surfaces M10 · 5-Yr Projection M11 · MEIO Optimizer OE-A · Daily PM Ops OE-B · Supplier Scorecard OE-C · Negotiation Strategy OE-D · Contract Checklist OE-E · Process Improvement OE-F · Meeting Intelligence OE-G · Stakeholder Strategy OE-H · EOL Response Plan OE-I · Ambiguity Solver OE-J · STAR Story Builder SC-1 · Lane & Mode Planner SC-2 · Supply-Chain Risk Map SC-3 · Disruption Scenario SC-4 · Logistics Cost & Expedite REF-1 · Parts Catalog REF-2 · Catalog Analytics REF-3 · Fleet & Portfolio

Analysis summary

select a row to open its module
Criticality Tier ⓘ
—
M1 · FMECA
Readiness % ⓘ
—
M2 · Gauge
Rec. Stock Q* ⓘ
—
M3 · Newsvendor
Fleet Readiness ⓘ
—
M4 · MEIO/Hub
Supplier Risk ⓘ
—
M5 · Composite
EOL Exposure ⓘ
—
M6 · DMSMS
Sourcing Quad. ⓘ
—
M7 · Kraljic
P(Stockout) ⓘ
Run →
M8 · Monte-Carlo
Q: Which spares are so critical that a stockout causes downtime?
FMECA-style scoring of failure-impact × frequency × detection difficulty across your installed fleet.
Output: Criticality tier (VITAL / ESSENTIAL / DESIRABLE) + Risk Priority Number (RPN) + fleet expected failures per year.
Use when: deciding stocking policy, assigning supplier criticality tier, prioritising CBM inspection frequency, or justifying capital allocation.

Inputs

  • λ failure rate
  • Severity (1–10)
  • Detectability (1–10)
  • Installed base
  • Redundancy
  • Qualified alternates
→

Computation

  • RPN = sev × det × (λ×10)
  • Eff. severity w/ redundancy
  • Fleet failures/yr = λ × n
  • Marginal-utility tier
→

Outputs

  • Criticality tier
  • RPN score
  • Fleet exp. failures/yr
  • Stocking decision
→
FMECA + RCM Criticality Inputs
These are typical industry defaults — adjust to your fleet's actual failure history.
Criticality Number Cm
—
FMECA-style composite score (higher = more critical)
— —
Risk Priority Number ⓘ
—
Effective Severity ⓘ
—
Fleet Exp. Failures/yr ⓘ
—
Alternates Factor ⓘ
—
ⓘ How criticality is computed

Simplified FMECA Criticality Number: Cm = (S_eff/10) × (D/10) × λ × N × (oh/8760) where S_eff is severity reduced by redundancy buffer, D is detectability, λ is annual failure rate, N is installed base, and oh/8760 normalises to fraction of year (annual basis → oh=8760 → factor=1).

Risk Priority Number (RPN): RPN = S_eff × D × (λ×10) — analogous to FMEA RPN = Severity × Occurrence × Detection.

Tier thresholds: VITAL Cm ≥ 0.5; ESSENTIAL 0.1–0.5; DESIRABLE <0.1. Decision: VITAL → STOCK + DUAL-SOURCE; ESSENTIAL → STOCK; DESIRABLE → DON'T STOCK (review).

Ref: MIL-STD-1629A FMECA; Quality-One FMECA guide.

Score Drivers
Q: Will the part arrive at the site before it is needed?
Calculates confirmed supply coverage against required quantity, weighted by PO confidence, and flags date-slack risks.
Output: Readiness % (RED / YELLOW / GREEN) + date slack (days) + supply confidence score + risk flags + priority actions.
Use when: tracking an active PO, preparing for a maintenance window, generating a weekly readiness report, or escalating a late supplier commit.

Inputs

  • Required qty
  • On-hand inventory
  • Open PO qty + conf.
  • Lead time & σ
  • Commit / need date
  • Planning horizon
→

Computation

  • Confirmed supply = OH + PO × conf
  • Readiness % = confirmed ÷ required
  • Date slack = need − commit
  • LT / horizon ratio
→

Outputs

  • Readiness % + RAG
  • Date slack (days)
  • Risk flag list
  • Recommended actions
→
Spare Readiness Inputs
Readiness %
—
—
Confirmed Supply ⓘ
—
Gap ⓘ
—
Date Slack (days) ⓘ
—
LT / Horizon ⓘ
—
Risk Flags
Recommended Actions
    ⓘ How readiness is computed

    Readiness% = min(100, confirmedSupply / required × 100)

    confirmedSupply = onHand + (PO qty if commit date ≤ need date AND commit is confirmed). If no confirmed commit, PO qty counts as 50% confidence. Status: RED if <80% or commit after need; YELLOW if 80–99%; GREEN if ≥100% with slack ≥7 days.

    Q: How many units should I hold in stock to balance over-stocking cost vs stockout risk?
    Newsvendor / critical-ratio model with optional Poisson mode for slow-moving parts — finds Q* that minimises total annual cost.
    Output: Optimal stock Q*, critical ratio CR, total annual cost curve, under-stock vs over-stock cost breakdown.
    Use when: setting safety stock policy, reviewing annual stocking levels, justifying a budget increase for spares, or evaluating Poisson vs Normal demand models.

    Inputs

    • Unit cost ($)
    • Under-stock cost/event
    • Annual demand μ
    • Demand σ
    • Carrying rate (%)
    • Poisson toggle
    →

    Computation

    • CR = Cu ÷ (Cu + Co)
    • Q* = Φ¹(CR) if Normal
    • Q* = Poisson inverse CDF
    • Annual cost per Q
    →

    Outputs

    • Optimal Q*
    • Critical ratio CR
    • Total annual cost
    • Cost breakdown chart
    →
    Optimal Stock Level Inputs
    Optimal Stock Recommendation
    Newsvendor Q* ⓘ
    —
    Safety Stock SS ⓘ
    —
    Reorder Point ROP ⓘ
    —
    Critical Ratio CR ⓘ
    —
    Fill Rate Achieved ⓘ
    —
    Total Annual Cost ⓘ
    —
    Days of Cover at Q* ⓘ
    —
    Annual Carrying $ at Q* ⓘ
    —
    Expected Stockouts/yr ⓘ
    —
    Poisson Stockout Probability
    Total Cost vs Stock Qty
    ⓘ Newsvendor + Fill-Rate methodology — units & formulas

    Unit conversion: All inputs use annual units (μ in units/yr, σD in units/yr, lead time L in weeks). Internally: L_yr = L_wk / 52; σ_L_yr = σ_L_wk / 52.

    Demand during lead time: μ_LT = μ_annual × (L/52)  |  σ_LT = √((L/52)×σ_D² + μ_annual²×(σ_L/52)²) — combines demand variability and lead-time variability.

    Critical ratio: CR = Cu / (Cu + Co) where Cu = under-stock cost per stockout event; Co = carrying cost over part life = carryRate × unitCost × partLife. For critical DC spares Cu ≫ Co, pushing CR close to 1 and Q* higher.

    Newsvendor Q*: Q* = max(0, ⌈μ_LT + Φ⁻¹(CR) × σ_LT⌉) where Φ⁻¹ is the inverse normal CDF (Beasley-Springer-Moro rational approximation, verified: Φ⁻¹(0.975)=1.96, Φ⁻¹(0.99)=2.326).

    Safety stock (fill-rate target): SS = max(0, ⌈Φ⁻¹(FR) × σ_LT⌉). Reorder Point: ROP = ⌈μ_LT + SS⌉.

    Poisson mode (slow movers, demand <5 units/yr): λ_LT = λ_annual × (L/52); P(stockout at level S) = 1 − Σ_{k=0}^{S−1} e^{−λ_LT} λ_LT^k/k!. Falls back to normal approx for λ_LT > 200. Ref: Sherbrooke 1985 METRIC — newsvendor model (critical-fractile).

    Q: Should I stock parts at each site, or pool them at a regional warehouse?
    Multi-Echelon Inventory Optimisation (MEIO) compares site-level vs regional-pool total stock requirement using Poisson demand aggregation across sites.
    Output: Site-level stock (per site × n sites) vs regional-pool stock, pooling savings (units + $), fleet P(no stockout), recommended echelon structure.
    Use when: designing a hub-and-spoke spares network, evaluating whether to open a regional warehouse, or justifying consolidation of slow-moving critical parts.

    Inputs

    • Site demand rate λ
    • # sites served
    • Vendor → regional LT
    • Regional → site LT
    • Target service level
    • Unit cost + carry rate
    →

    Computation

    • Regional λ = n × λ
    • Poisson inv CDF per echelon
    • Site stock vs pool stock
    • Pooling savings
    →

    Outputs

    • Site vs pool Q
    • Units & $ saved
    • Fleet P(no stockout)
    • Echelon recommendation
    →
    MEIO 2-Echelon Inputs
    MEIO Optimal Allocation
    Regional Stock s₁* ⓘ
    —
    Site Stock s₂* ⓘ
    —
    Site Fill Rate ⓘ
    —
    Annual Holding Cost ⓘ
    —
    Expected Stockout Cost ⓘ
    —
    Total Annual Cost ⓘ
    —
    Total Inventory Value ⓘ
    —
    Effective Site LT (days) ⓘ
    —
    Iterations to Converge ⓘ
    —
    Cost vs Fill-Rate Trade-off Frontier
    ⓘ 2-Echelon METRIC marginal-analysis methodology

    Model: 2-echelon METRIC (Sherbrooke 1968) — Regional Warehouse (echelon 1, replenished from vendor) → Site Stock (echelon 2, replenished from regional). Optimises the split of stock between echelons given a service-level target and optional budget cap.

    VARI-METRIC effective LT: LT_eff = LT_regional + B₁(s₁) / (n × λ) where B₁(s₁) = expected backorders at regional (Little’s Law). Backorder expansion: B(s,λ) = λ(1 − P(X≤s−1)) − s(1 − P(X≤s)) (Poisson closed form; normal approx for λ > 200). Ref: Graves 1985 VARI-METRIC.

    Marginal analysis pick rule: At each iteration, add one unit to the echelon with the higher marginal fill-rate gain per dollar of holding cost. Stop when target fill rate is achieved or budget is exhausted. Ref: Sherbrooke 1968 METRIC — Fox & Landi 1971 marginal analysis.

    Site fill rate: P(Poisson(λ × LT_eff) ≤ s₂) — probability a demand event is satisfied from site stock without waiting for regional replenishment.

    Q: Where should a shared regional hub be located, and how much does it reduce effective lead time?
    Models the hub benefit as OEM lead time vs hub-to-site transit time, and quantifies fleet-wide readiness improvement and inventory cost reduction.
    Output: Hub ROI (%), effective LT reduction, fleet readiness with/without hub, annual inventory savings, breakeven sites.
    Use when: evaluating a new regional DC or logistics hub, presenting a business case for hub investment, or benchmarking hub LT vs direct OEM procurement.

    Inputs

    • # DC sites
    • # critical part types
    • OEM lead time (wks)
    • Hub-to-site LT (wks)
    • Annual demand / site
    • Unit cost + carry rate
    →

    Computation

    • LT reduction = OEM − hub-to-site
    • Safety stock Δ per site
    • Fleet inventory savings
    • Hub ROI = savings ÷ cost
    →

    Outputs

    • Hub ROI %
    • Effective LT reduction
    • Fleet readiness Δ
    • Breakeven sites
    →
    Multi-Site Hub Positioning Inputs
    Hub Positioning Recommendation
    Central Depot ⓘ
    —
    Regional Hub ⓘ
    —
    At Sites ⓘ
    —
    Fleet Readiness ⓘ
    —
    Hub Delta ⓘ
    —
    Hub Extra $ ⓘ
    —
    Hub Recommendation
    ⓘ Simplified 2-echelon MEIO / VARI-METRIC approach

    This is a transparent heuristic approximation (not a full VARI-METRIC solver). Hub units are sized to cover demand during hub-to-site lead time at the target fill rate. Site-level stock covers demand during the OEM lead time minus hub coverage. Remaining budget fills the central depot.

    Fleet readiness is estimated as min(100, totalStock / (demandDuringMaxLT × safetyFactor)). Hub delta = readiness with hub minus readiness without hub.

    Ref: METRIC/VARI-METRIC review (UMD); MEIO framework (Umbrex).

    Q: How exposed is my supply chain to a single-supplier failure or disruption?
    Composite weighted risk score across 8 dimensions: financial health, single-source exposure, geographic concentration, lead time, on-time delivery, quality, capacity, and ESG.
    Output: Composite supplier risk score + RAG band + per-dimension radar + recommended mitigations + annual disruption exposure ($).
    Use when: qualifying a new supplier, reviewing an existing supplier's risk tier, preparing a sourcing strategy brief, or building a business case for dual-sourcing.

    Inputs

    • Financial health (1–10)
    • Single/dual/multi source
    • Geographic conc. (1–10)
    • Lead time variability
    • OTD %, quality score
    • Capacity reserve %
    →

    Computation

    • Weighted composite score
    • Per-dimension scoring
    • Disruption exposure $
    • Radar chart data
    →

    Outputs

    • Composite risk score
    • RAG tier
    • Radar chart
    • Mitigation actions
    →
    Supplier Risk Inputs
    6
    7
    7
    6
    Composite Supplier Risk Score
    —
    — —
    Sourcing Strategy
    ⓘ Composite risk score weights

    Weights: Financial Health 15%, Single-Source 20%, Geographic Concentration 12%, Lead-Time Volatility 15%, OTIF 18%, Capacity Headroom 10%, Geopolitical 10%. Contract status adjusts ±5 pts. Score 0–100. Bands: <30 LOW; 30–59 MEDIUM; 60–79 HIGH; ≥80 CRITICAL.

    Kraljic quadrant: supply-risk dimension = composite score / 10; spend-impact from direct input. Ref: Kraljic, P. (1983) "Purchasing must become supply management", HBR.

    Q: How many units should I buy before EOL / DMSMS notice expires, and is it worth it vs qualifying an alternate?
    NPV-based LTB quantity optimiser with carrying cost model, comparing Last-Time-Buy stock vs alternate qualification investment over the support window.
    Output: LTB recommended quantity + total LTB cost + carry cost + NPV break-even analysis + EOL exposure band.
    Use when: an OEM issues an EOL or NRND notice, deciding whether to commit to a large last-time-buy, or building the business case for an alternate qualification program.

    Inputs

    • EOL notice date
    • Remaining support years
    • Annual demand (units/yr)
    • On-hand + open PO
    • Unit cost + carry rate
    • Alternate options
    →

    Computation

    • LTB_Q = demand × yrs × 1.15
    • Carrying cost (avg × rate)
    • Alt-qual NPV
    • EOL exposure score
    →

    Outputs

    • LTB recommended Q
    • LTB total cost
    • NPV comparison
    • EOL exposure band
    →
    Last-Time-Buy / DMSMS Inputs
    LTB Recommendation
    LTB Qty (units) ⓘ
    —
    LTB Total $ ⓘ
    —
    Cumulative Carry Cost ⓘ
    —
    EOL Exposure Score ⓘ
    —
    — —
    NPV: Option A (LTB Stock) vs Option B (Requalify)
    NPV Option A (LTB) ⓘ
    —
    NPV Option B (Requalify) ⓘ
    —
    ⓘ LTB / DMSMS methodology — formulas & NPV interpretation

    LTB quantity: LTB_Q = max(0, ⌈annualDemand × supportYears × 1.15 − onHand − openPO⌉). Safety factor = 1.15 (15% buffer for demand uncertainty + scrap risk).

    NPV Option A (LTB Stock): t=0: −LTB_Q × unitCost (buy upfront). t=1…n: −carryingCost_t (average remaining inventory × carryRate × unitCost). End of life: ±scrap value (unused units × unitCost × (1 − scrapRisk) − unused × unitCost × scrapRisk).

    NPV Option B (Requalify): t=0: −altQualCost. t=1…n: −demandYr × unitCost × 1.20 (spot premium during qual period) or × 0.90 (qualified alternate at discount) after qualification completes.

    Decision rule: Both NPVs are costs (negative). Higher NPV = less negative = lower total cost = better option. If NPV_B > NPV_A → Requalify is cheaper. Ref: DCF: NPV = Σ CF_t / (1+r)^t.

    EOL Exposure Score: (installedUnits × criticality × supportYrsRemaining) / max(1, qualifiedAlternates). Bands: <50 LOW; 50–149 MEDIUM; 150–299 HIGH; ≥300 CRITICAL.

    Ref: DMSMS — Wikipedia; Lifetime buy estimations (UMD).

    Q: What sourcing strategy should I apply to this commodity — strategic partnership, leverage, or routine management?
    Positions the commodity in the Kraljic 2×2 matrix (supply risk × spend/profit impact) and generates a sourcing strategy brief for the quadrant.
    Output: Kraljic quadrant (Strategic / Leverage / Bottleneck / Non-Critical) + sourcing strategy brief + negotiation posture + relationship model.
    Use when: setting annual category strategy, preparing for supplier negotiations, reviewing commodity portfolio prioritisation, or onboarding a new supplier relationship.

    Inputs

    • Supply risk (1–10)
    • Spend / profit impact
    • Part criticality
    • Contract value ($)
    • Supplier market share
    →

    Computation

    • Quadrant = f(risk, impact)
    • Strategy archetype lookup
    • Negotiation posture
    • Relationship model
    →

    Outputs

    • Kraljic quadrant
    • Sourcing strategy brief
    • Negotiation posture
    • KPIs to track
    →
    Kraljic Matrix Inputs
    Kraljic 2×2 Matrix
    ← Low Spend ImpactHigh Spend Impact →
    Strategic
    High spend · High risk
    Bottleneck
    Low spend · High risk
    Leverage
    High spend · Low risk
    Non-Critical
    Low spend · Low risk
    ← Low Supply Risk / High Supply Risk →
    Strategy Brief
    —
    Q: Given realistic uncertainty in lead time and demand, what is the true probability of a stockout?
    Runs 10,000 stochastic iterations drawing lead time and demand from fitted distributions, outputting a P(stockout) distribution and a tornado chart of the risk drivers.
    Output: P(stockout) at current stock level + P10/P50/P90 readiness range + tornado chart of top risk drivers + recommended stock to hit target service level.
    Use when: presenting risk to leadership, stress-testing a proposed stock level under uncertainty, or identifying the single highest-leverage improvement (LT reduction, demand smoothing, stock increase).

    Inputs

    • Base LT + σ (weeks)
    • Annual demand + σ
    • Current stock on-hand
    • Simulation runs (n)
    • Target service level
    →

    Computation

    • 10,000 LT + demand draws
    • Demand-during-LT per iter
    • Stockout if demand > stock
    • P10 / P50 / P90 readiness
    →

    Outputs

    • P(stockout) %
    • Readiness P10/P50/P90
    • Tornado chart
    • Rec. stock for target SL
    →
    Monte-Carlo Scenario Inputs
    Monte-Carlo Results
    P(Stockout) ⓘ
    —
    P10 Readiness ⓘ
    —
    P50 Readiness ⓘ
    —
    P90 Readiness ⓘ
    —
    Exp. Downtime Cost ⓘ
    —
    Worst-Case Cost ⓘ
    —

    Seeded run: press Run to compute.

    Readiness Distribution
    Tornado Chart — Variance Drivers
    Q: Which input drives the most variation in fill rate?
    2D sensitivity sweep across 2 axes — sweeps any two inputs over a configurable range and renders a viridis heatmap of the chosen metric across the full N×N grid.
    Output: Heatmap (N×N grid, viridis ramp) + most-sensitive axis + metric range across grid + coordinates of the extremum cell.
    Use when: justifying which lever to pull first (reduce lead time vs. increase stock vs. switch supplier), preparing sensitivity slides for leadership, or stress-testing a stocking decision against input uncertainty.

    Inputs

    • X-axis variable
    • Y-axis variable
    • Target metric
    • Resolution (N)
    • X/Y range multipliers
    →

    Sweep

    • N×N grid of (x,y) pairs
    • Each cell: recompute metric using current module values + overridden (x,y)
    • Identify max/min cell
    →

    Heatmap

    • Viridis colour ramp
    • Cell labels (monospace)
    • Axis labels from variable names
    →
    Sensitivity Sweep Inputs
    Sensitivity Results
    Most Sensitive Variable ⓘ
    —
    Range Across Grid ⓘ
    —
    X at Extremum ⓘ
    —
    Y at Extremum ⓘ
    —
    Sensitivity Heatmap

    Viridis colour ramp: dark purple = low metric value, yellow-green = high. Each cell shows the computed metric value.

    Methodology — Sensitivity Sweep Algorithm

    For each of the N×N grid cells the sweep algorithm: (1) reads current values from the corresponding module inputs (Criticality M1, Stock M3), (2) overrides the X-variable with x_base × lerp(x_min_mult, x_max_mult, i/(N-1)) and similarly for Y, (3) recomputes the chosen metric using the same formulas as the live modules, and (4) normalises the result for colour mapping.

    Viridis ramp: perceptually uniform, colour-blind safe. Implemented as a 5-stop linear interpolation through the canonical Viridis control points: #440154 (0%), #31688e (25%), #35b779 (50%), #90d743 (75%), #fde725 (100%).

    Most sensitive axis: computed as the variable whose marginal range (max metric along that axis minus min metric along that axis, averaged across the perpendicular axis) is larger. This is a first-order sensitivity index analogous to a one-at-a-time (OAT) sensitivity analysis.

    Metric formulas: use the same logic as M1 Criticality (RPN), M3 Optimal Stock (fill rate, total cost, optimal qty), and M4 MEIO (expected backorders, P(stockout)). No new math is introduced.

    Q: How much will the fleet spend on critical spares over the next 5 years?
    Cash-flow forecast across 8 commodity classes — projects annual replacement and maintenance spend as installed base grows, failure rates drift, and unit costs inflate.
    Output: Year-by-year stacked area chart (8 commodity classes) + data table (Year | each class | Total | Cumulative) + 4 KPI summary cards.
    Use when: building a multi-year capital budget for spares, presenting a business case for a strategic stockpile, or benchmarking planned spend against industry ratios.

    Inputs

    • Installed base (MW)
    • Fleet growth %/yr
    • Failure rate drift
    • Cost inflation %/yr
    • Maintenance ratio
    • Horizon (3/5/7/10 yr)
    • Commodity mix profile
    →

    Year-by-Year Projection

    • install_base × (1+growth)^Y
    • failure_rate × (1+drift)^Y
    • unit_cost × (1+inflation)^Y
    • 8 commodity classes
    →

    Stacked Area Chart

    • 8 series (Chart.js)
    • Y = $/yr
    • X = year index
    • Data table below
    →
    Projection Inputs
    5-Year Spend Summary
    Total Spend (Horizon) ⓘ
    —
    Year-N Annual Spend ⓘ
    —
    Growth vs Year 0 ⓘ
    —
    Largest Commodity Class ⓘ
    —
    Annual Spend by Commodity Class
    Year-by-Year Spend Table
    Methodology — 5-Year Spend Projection

    For each year Y (0 to horizon): install_base_Y = base × (1+growth/100)^Y; failure_rate_mult_Y = (1+drift/100)^Y; cost_mult_Y = (1+inflation/100)^Y.

    For each commodity class c: replacement_Y_c = failureRate_c × install_base_Y × share_c × unitCost_c × cost_mult_Y × failure_rate_mult_Y.

    maintenance_Y = replacement_Y × maintenance_ratio/100. Total annual spend: total_Y = replacement_Y + maintenance_Y.

    8 commodity classes (failure rates per MW/yr, unit costs at Year 0): Chillers (0.15/MW, $45K), Transformers & Switchgear (0.08/MW, $28K), UPS Systems (0.20/MW, $22K), PDU & Floor Distribution (0.25/MW, $8K), Network (0.40/MW, $4.5K), Mechanical (0.45/MW, $3.5K), Sensors & Controls (0.55/MW, $1.2K), Consumables (2.5/MW, $500).

    Operating Engine — Daily PM Operating System. These templates turn the day-to-day Program Manager workflow (sourcing, supplier reviews, negotiation, contracts, process improvement, meetings) into structured, copy-ready outputs — the qualitative companion to the quantitative models above. Fill in today's situation and click Generate.
    Today's Situation Inputs
    Click "Generate Plan" to build today's situation snapshot, priority stack, critical follow-ups, decision log, and end-of-day update draft based on your inputs.
    ⓘ How priority logic works

    Status: RED if any critical shortage or >3 late POs; YELLOW if 1–3 late POs or unconfirmed suppliers; GREEN otherwise. Priority: critical shortages → P1; late POs >3 or supply severity ≥4 → P2 for supply workstream; finance/exec ask → P3. Each Follow-Up row is generated from your inputs with a recommended message and consequence. The EOD draft is a status email skeleton populated from your inputs.

    Operating Engine — Supplier Scorecard & Review Cadence. Enter a supplier's performance metrics to generate a RAG scorecard, recommended review cadence (Weekly/Monthly/Quarterly), agenda template, and a radar chart of the 8 dimensions.
    Supplier & Metrics Input
    Scorecard
    Recommended Review Cadence
    Agenda Template
    
              
    FIG. 1 · Supplier performance, eight measures scaled 0–100 (higher is better)
    ⓘ RAG logic and cadence derivation

    Each metric is rated GREEN (meets target), YELLOW (within 10% of target), or RED (fails). Overall RAG = worst of the 4 "critical" dimensions (OTIF, Commit Accuracy, Responsiveness, CA Closure). Review cadence: Critical supplier with any RED → Weekly Operational Review; Preferred supplier or any YELLOW → Monthly Business Review; Tactical/Replaceable with all GREEN → Quarterly Executive Business Review.

    Operating Engine — Negotiation & Commercial Strategy. Describe the supplier's ask, your position, and leverage factors. The engine generates a Leverage Assessment, BATNA analysis, Counterproposal, Concession Strategy, and a recommended talk track — all deterministic, no AI calls.
    Negotiation Scenario Inputs
    Click "Generate Strategy" to build a Leverage Assessment, BATNA analysis, Counterproposal, Concession Strategy, and recommended Talk Track for this negotiation.
    ⓘ Leverage & BATNA logic

    Leverage strength is auto-derived: volume commitment is Strong if annual spend >$500K; dual-source threat is Strong if alternates >0, Weak if 0; multi-year is Moderate; forecast visibility Moderate; standardisation Moderate. BATNA: 0 alternates + critical/preferred → "Limited BATNA — pivot to non-price terms"; ≥2 alternates + tactical/replaceable → "Credible BATNA — credibly threaten competitive bid". Counterproposal is templated per scenario type and raw-material justification.

    Operating Engine — Contract / SOW Requirements Checklist. Toggle the contract requirements that matter for this agreement. The engine generates a structured requirements brief with proposed contract language concepts for each of the 14 areas. This is an operational requirements guide — not legal advice.
    Contract Configuration
    Mark requirements you want included:
    Click "Generate Checklist" to build a structured 14-area Contract Requirements Table with proposed language concepts for each selected requirement.
    ⓘ How requirements are built

    All 14 standard MSA/SOW areas (Scope, Pricing, Lead Time, Forecast, Capacity, Delivery/Incoterms, Warranty, Quality, Documentation, EOL Notice, Last-Time-Buy, Change Notice, SLA, Inventory, Termination) are always shown. Rows where you toggled a requirement are highlighted. The "Proposed Contract Language Concept" column shows the plain-English clause intent — a brief to hand to legal, not a legal clause.

    Operating Engine — Process Improvement Builder. Describe a recurring operational problem. The engine generates a structured Process Improvement Proposal: reframed problem statement, root-cause checklist, future-state process, RACI, controls, KPIs, and a 30/60/90-day rollout plan.
    Problem Inputs
    Click "Generate Proposal" to build a reframed Problem Statement, Future-State Process, RACI Table, Controls & KPIs, and 30/60/90-Day Rollout Plan.
    ⓘ How the proposal is built

    The Problem Statement reframes your text with frequency and annualised impact (frequency multiplied per year). Future-State Process is a step-list (intake → triage → assignment → execution → control → review) matched to the ticked root causes. RACI maps the selected stakeholders to each step. Controls & KPIs are generated from ticked root causes — e.g., "no SLA" → SLA control + SLA-adherence KPI. The 30/60/90 plan is generated from a standard PM-ops template with milestones adapted to the problem.

    Operating Engine — Meeting Intelligence. Two modes: Prep generates a structured meeting brief (objective, agenda, data required, risks to surface, recommended position). Notes provides a live editable template for capturing decisions, actions, risks, and open questions.
    Meeting Prep Inputs
    Click "Generate Brief" to build a structured meeting brief with objective, agenda, data required, risks to surface, and recommended position.
    ⓘ How agendas are generated

    The prep brief agenda is auto-generated from the meeting type using the canonical review cadence templates from the master sourcing engine: Supplier Operational Review → PO review, expedite, shortage, commit validation, quality, recovery; Monthly Business Review → KPI trend, cost, lead time, capacity, improvement, contract, upcoming demand; Quarterly Executive Review → strategic alignment, supply roadmap, commercial partnership, long-term capacity, risk & resiliency. The notes template is a live editable structured form — click "Add row" to expand any table.

    Stakeholder & Communication Planner — Select stakeholders involved, describe the topic/situation, set urgency, and build a stakeholder influence strategy: Influence × Impact map, narrative arcs, coalition sequence, and strategic heuristics. All outputs are deterministic templates — edit before using.
    Stakeholder Selection & Context
    Click "Build Strategy" to develop your stakeholder influence approach: Influence × Impact map · Narrative arcs · Coalition sequence · Strategy heuristics.
    ⓘ How the plan is generated

    Stakeholder map attributes (What They Care About, Communication Style) are drawn from the master PM sourcing engine Module 9 stakeholder registry. Channel and cadence are auto-derived from urgency: Critical/Urgent → phone call + written follow-up same day; Elevated → email + meeting within 48h; Routine → email/async. Message drafts are register-adjusted: executive = concise + decision-oriented; supplier = specific ask + written commitment + deadline; finance = numbers + scenario; legal = risk framing + clause intent.

    EOL Response Plan — Enter the EOL notice details for a part or component to generate a complete response plan: options analysis, LTB quantity estimate, replacement qualification roadmap, supplier negotiation points, and stakeholder communication. Complements the Last-Time-Buy (Tab 6) NPV analysis.
    EOL Notice Inputs
    Click "Generate Plan" to build an EOL Options Analysis, LTB quantity estimate, Replacement Qualification Roadmap, Supplier Negotiation Points, and Stakeholder Communication plan.
    ⓘ How EOL quantities are computed

    LTB quantity: LTB_Q = ceil(installedUnits × failureRate × supportYears × 1.20 − onHand − openPO). Safety multiplier 1.20 covers demand uncertainty and scrap risk. Fleet exposure score: EOL_Score = (installedUnits × criticality × supportYears) / max(1, qualAlts).

    Options viability: "Qualify Alternate" shown as viable if alternates > 0 or alt-qual lead time < support years. "LTB Stock" always viable as fallback. "Redesign" viable only if redesign input = Yes. "Refurb / Harvest Pool" viable if criticality ≤ 6 or installed base is large. "Do Nothing" viable only if criticality < 4.

    For full NPV comparison of LTB vs Requalify, open the Last-Time-Buy tab (Tab 6) with the same inputs.

    Ambiguity Solver — Turn an undefined ask into a structured work plan. Enter the vague request, who asked, and the apparent scope. The solver generates candidate interpretations, a sharpened problem statement, a hypothesis tree, clarifying questions, a data request list, a 30/60/90-day plan, and risks/assumptions.
    Ambiguous Ask Inputs
    Click "Solve It" to generate candidate interpretations, a sharpened problem statement, hypothesis tree, clarifying questions, data request list, 30/60/90-day plan, and risks & assumptions.
    ⓘ How interpretations are generated

    The solver scans the ask for supply-chain signal words (readiness, inventory, supplier, cost, lead time, EOL, forecast, risk, process, visibility, alternate, expedite, shortage) and maps each to a candidate interpretation from the master PM sourcing engine Module 14 framework. The sharpened problem statement uses the SMART structure: what to improve, from what baseline, to what target, across what scope, by when. The 30/60/90-day plan follows the Discover → Stabilise → Systematise pattern standard for hyperscale PM roles.

    Interview & Performance Story Builder (STAR) — Build a structured, polished Situation–Task–Action–Result story for hyperscale Program Manager interviews or performance reviews. Enter a competency, brief situation, action, and result — the builder generates a narrative in the right register plus coaching notes and likely interview questions. This is a career-companion tool; use it for interview prep or writing self-assessments.
    STAR Story Inputs
    Click "Build Story" to generate a polished STAR narrative in the right register for a hyperscale PM interview or performance review, plus coaching notes and likely follow-on questions.
    ⓘ How the story is built

    The builder combines your inputs with competency-specific narrative scaffolding for the selected PM dimension (e.g. Supplier Negotiation → frame the constraint, name your leverage, show the process you built). The register targets hyperscale program management interviews: structured → leads with the headline result, names cross-functional stakeholders, shows the system built (not just the firefight), ends with scale/lesson. Coaching notes are generated per competency based on common interviewer scoring rubrics.

    Q: What are the standard DC M&E spare parts for my facility generation and equipment tier?
    Seed catalogue of 360+ data-center M&E spare parts across 6 DC generations (legacy raised-floor through AI-factory liquid-cooled) — with OEM, taxonomy, criticality, lead time, and unit cost data.
    Output: Filtered and sortable parts list; use “Use” button to load any part directly into the analytical modules above for immediate analysis.
    Use when: starting a new facility spares review, benchmarking your current parts list, finding typical lead times and unit costs, or loading a reference part into the criticality or stock modules.
    Parts Catalog — Browse & Search
    Browse the seed catalog of data-center M&E spare parts — legacy raised-floor through AI-factory liquid-cooled. Loading catalog… (Full DB scales to 100k+ rows — see data/spares-parts.sqlite.)
    — parts
    Part ID Description OEM System / Sub DC Gen Crit MTBF (yr) LT typ (wk) Cost (typ $) Lifecycle EOL risk #Alts Use
    Loading catalog data…
    OEM Name HQ Market Position Fin. Health Typ. Lead (wk) Typ. OTIF (%) Single-Source Risk Contract Models
    Loading OEM data…
    Loading facility types…
    Parts in Catalog — OEMs — Blind Risks — EOL/NRND/Obs —
    Catalog Analytics Dashboard — Analyzes the spare-parts database itself using SPARES_CATALOG. All charts are dark-mode aware and mobile-safe. Full SQLite scales to 100k+ rows via tools/query-spares-db.py.
    Scope:
    Parts in catalog
    —
    in scope
    OEMs covered
    —
    suppliers
    Systems / Subsystems
    —
    taxonomy nodes
    % NRND / LTB / Obsolete
    —
    lifecycle risk exposure
    Blind Risks
    —
    crit≥7 + EOL≥6 + 0 alts
    3D-Printable
    —
    collapse LTB risk
    Refurbishable (crit≤6)
    —
    circular economy
    AI-Factory Liquid-Cool
    —
    avg LT: — wk
    OEM Concentration by Subsystem ⓘ
    Lead-Time Distribution by Subsystem ⓘ
    Lifecycle Status by DC Generation ⓘ
    Criticality × Lead-Time Scatter ⓘ
    ⚑ Upper-right zone = high criticality + long lead time → stocking priority
    Blind Risk Parts ⓘ —
    Part IDDescriptionSystemSubsystemDC GenCritEOL RiskLifecycleLT typ (wk)Cost (typ $)
    Loading catalog…
    Opportunity Panels
    3D-Printable Parts
    —
    Loading…
    Refurbishable (crit≤6)
    —
    Loading…
    AI-Factory Liquid-Cool
    —
    Loading…
    ⓘ How this dashboard is computed

    Blind risk proxy: parts where crit ≥ 7 AND eol ≥ 6 AND alts === 0 — high criticality, high EOL risk, no qualified alternate. This is a browser-side approximation of the FMECA definition (high-severity failure mode NOT condition-monitorable).

    OEM concentration: for each subsystem, count parts per OEM. Subsystems where top OEM holds >60% flagged as concentration risk.

    Lead-time distribution: avg and max ltMax per subsystem, sorted descending.

    Lifecycle × DC generation: part counts grouped by lifecycle_status and dc_generation.

    Full database queries: tools/query-spares-db.py on data/spares-parts.sqlite.

    Supply-Chain Exposure ⓘ
    CN Transformer share
    ~60%
    global power-transformer capacity
    CN→NA tariff exposure
    8/10
    Sec 122 + 301 + copper +50%
    Highest-risk lane
    —
    composite risk score
    Lanes with risk >7
    —
    of 13 trade lanes
    ⚠ 2026 Context: US imports >8,000 high-power transformers from China in Jan–Oct 2025 (vs <1,500 in all 2022). Section 122 10% surcharge + Section 301 + copper +50% (Apr-2026). ~30–50% of large US data centers planned for 2026 may be delayed. (webhosting.today, 2026)
    Trade Lanes — Ranked by Composite Risk
    LaneCongestionGeoVolatilityTariffComposite
    Loading…
    ⓘ Lane risk computation

    Composite lane risk = average(congestion, geopolitical, volatility, tariff) — each on a 1–10 scale from SPARES_CATALOG.tradeLanes. Higher = riskier for DC M&E procurement on that route. Sources: Xeneta 2026 · Maersk Winter 2026 · ShipUniverse · SPARES_CATALOG research.

    Fleet Readiness — Parts 0 Critical-at-Risk 0 Total Carrying $ —
    Fleet / Portfolio Dashboard — Build a fleet of spare parts, compute recommended stock levels, carrying costs, stockout-$ risk, and readiness % for each part. Persist in localStorage + scenario snapshot. Load sample presets or add parts from the catalog.
    Shared Fleet Parameters
    Add Part:
    Total Inventory $ at Rec. Stock
    $—
    all parts at recommended SS
    Weighted Fleet Readiness %
    —
    weighted by criticality
    Critical-at-Risk Parts
    0
    crit≥7 AND readiness<90%
    Total Annual Carrying $
    $—
    at recommended stock
    Total Stockout-$ Risk
    $—
    expected annual exposure
    EOL Exposure Score
    —
    Σ units×crit×yrs/max(1,alts)
    Fleet SC Risk KPI
    —
    avg supply-chain risk score (0–100)
    Part / Description Subsystem DC Gen Crit LT (wk) Unit Cost ($) Units On-Hand Rec. SS Annual Carry $ Stockout Risk $ Readiness % Lifecycle SC Risk
    Add parts above or load a sample preset to get started.
    Pareto of Stockout-$ Risk ⓘ
    EOL Exposure Heatmap ⓘ
    ABC-XYZ Demand-Value Scatter ⓘ
    A-X: High value, stable demand
    Tight safety-stock policy, reorder-point driven, VMI candidate
    A-Z: High value, erratic demand
    Safety-stock heavy or VMI; review demand forecasting; dual-source
    C-X: Low value, stable demand
    Automate replenishment; min/max policy; P-card if low cost
    C-Z: Low value, erratic demand
    Don't stock unless crit≥7; review vs on-demand sourcing
    ⓘ Per-part math — safety stock, readiness, carrying $, stockout risk

    Demand rate: λ = units × (1/MTBF_yr). Safety stock: SS = z × σ_LT where σ_LT = √(L/52 × λ) (Poisson approximation: variance = mean for Poisson demand during lead time, σ_LT = √(λ × L/52)).

    Recommended stock: recStock = ⌈SS⌉ + ⌈μ_LT⌉ where μ_LT = λ × L/52.

    Annual carrying $: carryRate × unitCost × recStock.

    Stockout risk: P(stockout) × downtimeCostPerHr × MTTR_hr × units_at_risk. P(stockout) ≈ max(0, (recStock − onHand) / (recStock + 1)) if on-hand < recommended stock, else 0.02 (residual).

    Readiness %: min(100, onHand / max(1, recStock) × 100).

    EOL exposure: Σ (units × crit × 5) / max(1, alts) (5 = nominal support years proxy; alts from catalog).

    Fleet weighted readiness: weighted average of per-part readiness %, weighted by criticality score.

    Methodology
    FrameworkWhat it doesModuleCitation
    FMECA (MIL-STD-1629A)Failure Modes, Effects & Criticality Analysis — computes Criticality Number Cm = β · α · λp · t; assigns Category I/II effect severity → stock decision1 · CriticalityQuality-One FMECA guide
    RCM Criticality RankingReliability-Centered Maintenance — ranks assets by consequence × likelihood × detectability → VITAL / ESSENTIAL / DESIRABLE tiers1 · Criticalityrgbwaves.com
    VED AnalysisVital / Essential / Desirable — rapid 3-bucket criticality sort for early triage before full FMECA data is available1 · CriticalitySupply-chain standard; no single canonical reference
    ABC-XYZ MatrixABC = value/usage Pareto (A=top 70% cost); XYZ = demand variability (X stable, Z erratic) → 9-cell stocking policy matrix3 · Optimal StockStandard inventory management practice
    Newsvendor / Critical-FractileFinds optimal stock Q* where CR = Cu/(Cu+Co) = P(D ≤ Q*). For DC spares Cu ≫ Co → stock generously.3 · Optimal StockSherbrooke 1985 (INFORMS)
    Fill-Rate Safety StockSS = z(FR) × σLT where σLT = √(L·σD² + μD²·σL²) — combines demand and lead-time variability3 · Optimal StockSilver, Pyke & Thomas: Inventory and Production Management
    Poisson / Compound-PoissonDemand model for slow-moving critical spares (λ = installed base × AFR). P(stockout at S) from Poisson CDF — more accurate than Normal for <5 units/yr demand3 · Optimal StockSherbrooke 1985
    METRIC (Sherbrooke 1968)Multi-Echelon Technique for Recoverable Item Control — minimises expected backorders across sites + depot for a given budget4 · Hub PositioningUMD DRUM review
    VARI-METRIC (Slay 1984)Adds variance correction to METRIC → within 1% of optimal vs ~11% for base METRIC; supports multi-echelon repairable item planning at scale4 · Hub PositioningScialert ITJ 2014
    MEIOMulti-Echelon Inventory Optimisation — generalises METRIC/VARI-METRIC to full network: multiple products, echelons, fill-rate and budget constraints simultaneously4 · Hub PositioningUmbrex MEIO
    Supplier Risk IndexComposite 0–100 score: Financial 15%, Single-Source 20%, Geo Concentration 12%, LT Volatility 15%, OTIF 18%, Capacity 10%, Geopolitical 10%. Bands: LOW/MEDIUM/HIGH/CRITICAL5 · Supplier RiskAdapted from procurement risk literature; weights configurable
    Kraljic MatrixSupply risk × profit/spend impact → Strategic / Bottleneck / Leverage / Non-Critical quadrants → per-quadrant sourcing strategy5, 7 · Supplier Risk, KraljicKraljic, P. (1983) "Purchasing must become supply management", HBR
    DMSMSDiminishing Manufacturing Sources & Material Shortages — monitors lifecycle: Active → NRND → Last-Time-Buy → Obsolete; triggers proactive EOL action6 · Last-Time-BuyWikipedia DMSMS
    Last-Time-Buy (LTB)LTB_Q = max(0, ⌈annualDemand × supportYrs × 1.15 − onHand − openPO⌉). NPV comparison: Option A (buy-stock) vs Option B (requalify alternate) via DCF6 · Last-Time-BuyLifetime buy estimations (UMD)
    Monte-Carlo Simulation1,000+ scenarios with variable lead time, demand, supplier reliability → P(stockout), P10/P50/P90 readiness, expected downtime cost, tornado chart of variance drivers8 · Monte-CarloBox-Muller normal variate; standard Monte-Carlo methodology
    Cheapest mode — Fastest mode — Ocean door-to-door — Air door-to-door —
    Lane & Mode Planner — Select origin, destination, part, Incoterm, and urgency to get a mode-comparison table (days · cost · CO₂), chokepoint reroute what-if, and Incoterm cost/risk split. Based on catalog tradeLanes + transportModes reference data.
    Lane & Shipment Inputs
    Chokepoint reroute what-if ⓘ
    Mode Comparison
    ModeDaysEst. Freight $CO₂ Rel.FeasibilityBadge
    Select inputs to compute.
    ⓘ How freight cost is estimated

    Base ocean-FCL rate: $1.20/kg. Other modes scale by catalog costIndex: ocean-LCL ×1.6, air-standard ×12, air-express ×25, road ×3, rail ×2, courier ×18.

    Door-to-door days = mode transit + customsD (scaled by destination country customs-efficiency) + lastMileD. Reroute adds +12 d to ocean options.

    CO₂ relative bar: proportional to co2Index (ocean-FCL = 1.0 baseline; air-express = 22×).

    Estimates are illustrative. Actual rates vary by carrier, season, volume, and congestion. Source: SPARES_CATALOG transport & lane data · Incoterms 2020 (ICC).

    Incoterm Cost & Risk Split — DAP
    Cost/Risk ElementSeller Bears?Buyer Bears?Risk Transfer Point
    SC Risk Score — Band — Top Risk —
    Supply-Chain Risk Map — Composite supply-chain risk score (0–100) from 7 weighted dimensions: single-source exposure, country-of-origin risk, lane congestion/geopolitical/volatility, lead-time pressure, tariff exposure, and hub coverage. Outputs: score + band + radar + ranked mitigations.
    Risk Map Inputs
    Composite SC Risk Score
    SC Risk Score ⓘ
    —
    Band ⓘ
    —
    Top Risks & Mitigations
    • Configure inputs to see mitigations.
    ⓘ Score weighting methodology

    Weights: Single-source 22% · Country geo-risk 15% · Lane congestion 12% · Lane geo/political 12% · LT pressure vs need-window 15% · Tariff exposure 12% · Supplier OTIF 12%. Hub coverage reduces the effective lane congestion + LT-pressure contribution by 60% (partial) or 85% (full hub/VMI).

    Bands: LOW <25 · MEDIUM 25–50 · HIGH 50–75 · CRITICAL >75.

    Sources: SPARES_CATALOG.countryRisk (World Bank LPI) · tradeLanes congestion/geo/volatility/tariff · 2026 tariff research synthesis.

    P10 LT— P50 LT— P90 LT— Exp Expedite $— % On-Time—

    Seeded run: press Run to compute.

    Disruption Scenario / Resilience Sim — Monte-Carlo simulation (≥1,000 iterations) combining lane delay variability, tariff shock, supplier-commit slip, demand spike, and chokepoint reroute. Outputs: % on-time, P10/P50/P90 of lead time and expedite cost, tornado chart, and with/without-hub + dual-source comparison.
    Simulation Inputs
    Base Lane Parameters
    Disruption Probabilities
    Resilience Toggles
    Regional hub available ⓘ
    Dual-source in place ⓘ
    Simulation Results
    Configure inputs and click ▶ Run Simulation.
    ⓘ Simulation methodology

    Monte-Carlo (1,000 iterations): each iteration samples (1) lead-time draw from N(lt_base, lt_sigma) using Box-Muller (same as Module 8); (2) Bernoulli tariff shock; (3) Bernoulli commit slip; (4) Bernoulli reroute (+12 d ocean = +1.7 wk); (5) Bernoulli demand spike (compresses effective need window).

    Recovery logic: if effective LT > need window, compute air-freight expedite cost ($1.20/kg × 12 × weight × tariff_multiplier). If no expedite possible (emergency urgency), count as downtime event (downtime_cost × (LT_overrun weeks × 168 hr/wk)).

    Hub toggle: 70% probability in each iteration that hub stock is available (LT → 1 wk). Dual-source: commit_slip_prob /= 2, slip_mag × 0.6. Safety stock: effective_need_window += safety_stock_wks.

    Tornado chart: each disruption driver is individually held at mean while varying ±1σ; variance contribution measured as range of P50 outcome. Sources: Box-Muller transform · Incoterms 2020 · SPARES_CATALOG lane data.

    Gap (weeks)— Rec. Option— Downtime Risk $—
    ✈️ Logistics Cost & Expedite Calculator — Given a readiness gap (site need-date minus supplier commit), compute and rank all recovery options (air-freight, partial shipment, alternate plant, hub pull, substitute qualification, accept downtime). Recommends the cost-minimising path that closes the gap. Links to Daily PM Ops escalation.
    Gap & Part Inputs
    Regional hub / consignment stock available ⓘ
    Recovery Options
    Configure inputs to see recovery options.
    ⓘ Recovery option cost methodology

    Air-freight (full): weight × $1.20/kg × 12 (air-standard costIndex). Door-to-door = lane airD + customsD + lastMileD days.

    Air-freight (sub-assembly): assumes 30% of weight = critical sub-assembly; air cost × 0.3; ocean for the rest.

    Alternate plant: requires alts > 0. Re-source premium 15% of unit cost + air-freight. Lead time = air days + 2-week qualification check.

    Pull from hub: near-zero lead time (hub→site road ≈ 3 days). Cost = 5% × unit cost × months in hub (proxy for consignment holding fee).

    Qualify substitute: only if alts === 0. Cost $50K (small board/kit) to $150K (major equipment) depending on weight. Lead time 12–24 weeks.

    Baseline (accept downtime): downtime_$ = crit/10 × downtime_cost × gap_hours (gap weeks × 168 hr/wk).

    Sources: Incoterms 2020 · SPARES_CATALOG lane/mode data · 2026 freight rate research.

    02 / Reference

    Method

    • CriticalityCm = (S_eff/10) × (D/10) × λ × N × (oh/8760); VITAL ≥ 0.5, ESSENTIAL 0.1–0.5
    • RPNS_eff × D × (λ × 10), capped at 1,000
    • Readinessmin(100, confirmed supply ÷ required × 100)
    • Lead-time demandμ_LT = μ_annual × L/52; σ_LT = √((L/52)·σ_D² + μ_annual²·(σ_L/52)²)
    • Stock levelQ* = max(0, ⌈μ_LT + Φ⁻¹(CR) × σ_LT⌉), CR = Cu ÷ (Cu + Co)
    • Safety stockSS = max(0, ⌈Φ⁻¹(FR) × σ_LT⌉); ROP = ⌈μ_LT + SS⌉
    • Hub fill1 − Σ_{k=0}^{S−1} e^{−λ_LT} λ_LT^k / k!
    • Last-time buymax(0, ⌈annual demand × support years × 1.15 − on hand − open PO⌉)

    Computed against

    MIL-STD-1629A FMECASherbrooke METRIC / Slay VARI-METRICNewsvendor critical fractileKraljic matrix (HBR 1983)DMSMS lifecycle practice

    Read further

    Engine RZEngine · rz-engine.js · catalog 2026-Q1, 445 parts

    How to use
    1. Pick a commodity. Select it under Analysis setup (Chiller, Switchgear, UPS …): realistic M&E defaults load into every module.
    2. Or load a sample scenario. The scenario list in the bar above (for example "Chiller compressor crisis" or "MV switchgear EOL") sets all modules in one step.
    3. Browse the parts catalog. The Parts Catalog tab holds 445+ DC M&E spare parts; "Use" loads one into Criticality and Optimal Stock. Catalog Analytics charts the whole database.
    4. Export or share. Export PDF writes the analytical modules as one report; Share URL copies a link with your inputs encoded.

    Illustrative models with industry-typical defaults; not a substitute for supply-chain analysis, procurement advice or certified reliability engineering. Check outputs against your site data, supplier agreements and failure history before buying. Methods: FMECA (MIL-STD-1629A), newsvendor / critical fractile, fill-rate safety stock, METRIC / VARI-METRIC (Sherbrooke 1968, Slay 1984), Kraljic matrix (HBR 1983), DMSMS lifecycle management; each module cites its sources. Catalogue data 2026-Q1: parts, 7 transport modes, 13 trade lanes, 16 country-risk profiles. Runs in your browser. Independent research; not affiliated with any current or former employer. Privacy · Terms.