In the flickering glow of a midnight monitor, Alex, a junior project manager, slumped over a keyboard. A $2.3 million overrun had just landed on his desk. The culprit? A broken "what-if" scenario in the company’s cost-control model. His boss’s final text read: "Fix it. Or else. Look up the ETAP tutorial."
His laptop’s fans roared. COM port 3 was already active—the plant’s real-time control system, the same one that ran the conveyor line outside his window. The PDF began to flicker. Diagrams turned into live feeds. A button appeared: "Execute Scenario 7c – Houston." etap software tutorial pdf
He closed the PDF. The file deleted itself. And somewhere in a control room not yet built, a breaker waited for a command that would never come—because the only person who knew the sequence had just decided to stay ignorant. In the flickering glow of a midnight monitor,
Alex didn’t click it. Instead, he scrolled to the very last page, past the licensing terms and the "About the Authors" blank space. There, in 6-point font, was a single line: A broken "what-if" scenario in the company’s cost-control
Alex froze. April 14th was three months ago. The Lagos blackout had been blamed on a gas pipeline explosion. He ran the simulation anyway. The model collapsed not from harmonics, but from a single mislabeled relay—exactly as the tutorial predicted.
Heart thudding, he flipped to Chapter 7: Protective Coordination .
Alex’s reflection in the dark screen smiled. He didn’t remember smiling.