Uptime Engineering Institute Mission‑Critical Training • Data Centers
Mission‑Critical Electrical Training • Data Centers

We train electricians who keep billion‑dollar server farms online.

Learn redundancy, concurrent maintainability, failure prevention, and real-world uptime practices— built for modern data centers, not residential wiring.

N, N+1, 2N, 2N+1 Architectures explained
SPOF Hunting Interactive failure drills
Uptime Mindset Principles you apply daily

Quick Start

  1. Read the Critical Question (below).
  2. Run the “What breaks if this fails?” scenario.
  3. Review the mindset principle cards.
  4. Enroll to unlock quizzes + modules.

Demo: SPOF Hunt (placeholder)

Embed your H5P activity here (H5P plugin) or replace with your LMS quiz block.

Tip: In H5P, use “Image Hotspots” or “Question Set” for “What breaks if this fails?” drills.

Critical Question

If this component fails right now… what breaks, how fast, and what’s your first move?

Uptime Engineering Institute — field-proven thinking

This single question turns “maintenance” into uptime engineering. It forces you to identify single points of failure (SPOFs), understand redundancy level (N, N+1, 2N, 2N+1), and choose actions that protect SLA and safety.

SPOF HUNT Trace power path; mark any single component that can drop the critical load. Utility Normal source ATS / Switchgear If single, it's a SPOF UPS Condition power IT Load Critical racks N+1 example: duplicate ATS/UPS module so one can fail and the load stays up (concurrent maintainability).

Interactive Scenario

Use LMS quiz blocks or H5P hotspots. The goal: click the weak link and explain the blast radius.

Interactive: What breaks if this fails?

Embed your H5P activity here (H5P plugin) or replace with your LMS quiz block.

Tip: In H5P, use “Image Hotspots” or “Question Set” for “What breaks if this fails?” drills.

Scenario prompt (copy into Tutor LMS quiz)

A UPS module alarms and drops offline during peak load. The generator is available but not running. Identify the SPOF(s). What happens under N vs N+1 vs 2N? What is your safest first move?

Mindset

Assume Failure

Design and operate as if a component will fail at the worst time.

Eliminate SPOFs

Anything that can take you down becomes a design/ops priority.

Concurrent Maintainability

Maintenance should not equal downtime when architecture is right.

Procedures Beat Heroics

Runbooks, MOPs, and verification steps prevent “good intentions” outages.

Measure What Matters

Track availability, MTTR, change success rate, and near-misses.

Protect the Load

Your job is to keep critical load stable—even while you fix the problem.

Final image (mindset → action)

A simple “decision loop” diagram you can place under the principle cards.

Detect Alarm / anomaly Assess Blast radius Act Safest first move Verify Stability restored