Curriculum · Level 4 of 5

Systems Engineer Curriculum

~16 hours study + 45-minute exam 5 modules L3 Specialist + 12 months multi-platform field experience

L4 Systems Engineer moves from field diagnosis to fleet architecture. You design the service program, schedule maintenance predictively, optimize the spare-parts supply chain, and lead teams of L1 and L2 technicians. This is where engineering replaces reaction.

Modules

1
Weibull Failure Analysis
3 hours
2
EOQ & Spare Parts Optimization
3 hours
3
Predictive Maintenance Scheduling
3 hours
4
Team Leadership & Escalation
2 hours
5
Enterprise SLA & Architecture
3 hours

Module 1 · 3 hours

Weibull Failure Analysis

The Weibull distribution is the standard statistical model for mechanical failures. This module teaches the math, how to fit a curve to field data, and how to read the shape parameter to diagnose a fleet's life stage.

Learning Objectives

Write the Weibull CDF and PDF and explain each parameter
Fit a Weibull distribution to censored field data
Interpret β: infant mortality (β<1), random (β=1), wear-out (β>1)
Project end-of-life timing for a fleet population

The Weibull equation

F(t) = 1 − exp(−(t/η)^β), where η = scale parameter (characteristic life) and β = shape parameter.

The characteristic life η is the time at which 63.2% of the population has failed — a robust way to describe the life of a mechanical component.

β tells you what kind of failure regime you are in: quality defects, random events, or true wear-out.

Reading β in the field

β < 1: early-life failures dominate. Usually quality escapes or infant mortality. Fix: tighten acceptance testing at receiving.

β ≈ 1: constant hazard rate. Failures are essentially random. Fix: redundancy or faster replacement.

β > 1: wear-out. Probability of failure rises with age. Fix: scheduled replacement before the knee of the curve.

Module 2 · 3 hours

EOQ & Spare Parts Optimization

Too much inventory ties up cash; too little creates downtime. EOQ is the classic optimization. This module teaches the formula, the assumptions, and the modifications you need for robot-fleet reality.

Learning Objectives

Derive the EOQ formula from demand, order cost, and holding cost
Apply safety stock calculations for lead-time variability
Distinguish consumables (filters, lubricants) from critical spares (actuators)
Build a parts plan that balances cash and uptime

The EOQ formula

EOQ = √(2DS / H), where D = annual demand, S = order cost, H = annual holding cost per unit.

This gives the order quantity that minimizes total inventory cost in the steady-state.

Assumes demand is known and constant — a bad assumption for robot fleets. Use safety stock to cover the variance.

Safety stock

Safety stock = Z × σ_LTD, where Z is the service-level multiplier and σ_LTD is the standard deviation of demand during lead time.

For critical spares (anything that takes the robot out of service), target a 99% service level (Z ≈ 2.33). For consumables, 90% (Z ≈ 1.28) is usually fine.

Module 3 · 3 hours

Predictive Maintenance Scheduling

Predictive maintenance combines real-time sensor thresholds with statistical survival curves to schedule work just before failure. This module teaches the scheduling logic and how to avoid the two common failure modes.

Learning Objectives

Combine sensor thresholds with Weibull projections to pick a replacement window
Balance cost of early replacement vs. cost of in-service failure
Avoid the two failure modes: premature replacement and reactive repair
Schedule work in customer-acceptable windows

Two signals, one decision

Sensor thresholds answer 'is this unit showing symptoms right now?'

Weibull projections answer 'is this population statistically nearing its characteristic life?'

Schedule work when either signal crosses its action threshold, not just both.

Module 4 · 2 hours

Team Leadership & Escalation

L4 engineers sign off on work performed by L1 and L2 technicians. This module covers the review protocols, escalation criteria, and training structure that keep a service team safe and effective.

Learning Objectives

Review and approve completed service jobs against the validation envelope
Define escalation criteria that trigger L4 involvement automatically
Run training and certification prep for L1/L2 team members
Write incident post-mortems that lead to platform-level improvements

Automatic escalation criteria

Any critical alert not resolved within 2 hours.

Any repeat failure on the same unit within 30 days.

Any failure that matches a known open platform-level defect.

Any safety event regardless of outcome.

Module 5 · 3 hours

Enterprise SLA & Architecture

Enterprise customers measure the service in uptime and cost per hour. This module covers the architecture patterns that deliver 99.5%+ uptime and the integration points with ERP and WMS systems.

Learning Objectives

Design a service architecture for a 99.5% uptime SLA
Choose between cold, warm, and hot standby strategies
Integrate with ERP for billing and WMS for job scheduling
Write an SLA that is measurable, auditable, and achievable

Uptime math

99% uptime = 3.65 days of downtime per year. 99.5% = 1.83 days. 99.9% = 8.77 hours. 99.99% = 52 minutes.

Each extra nine costs roughly 10× the previous, because the remaining downtime gets harder and harder to eliminate.

Most robot fleets target 99.5% — achievable with warm-standby units and 4-hour response times.

References

Weibull Analysis Handbook, Dr. Robert Abernethy
The standard reference on Weibull fitting and interpretation.
SAE J1739 — FMEA
Industry-standard FMEA procedure, extended here to fleet-level analysis.
BCR Enterprise SLA Template
Starting point for customer agreements, with measurable targets.

Ready to test?

Take the L4 Exam

5 questions · Passing score varies by level · Results emailed instantly

Back to L4 Start Exam