Page one was normal: "Welcome to ETAP. This tutorial covers Load Flow, Short Circuit, and Arc Flash." But by page three, the examples became... specific.
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.
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. etap software tutorial pdf
Heart thudding, he flipped to Chapter 7: Protective Coordination .
His phone buzzed. A text from his boss: "Did you open the PDF? Stop. Now." Page one was normal: "Welcome to ETAP
"ETAP is not a simulation. It is a mirror. What you see coming is what you already allowed."
"Because if you had run it... you’d realize the tutorial was written by you. Last year. Before the memory wipe." He closed the PDF
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."
Example 3.2: "A 138kV bus at the Lagos Port Substation fails when the harmonic distortion exceeds 12%. Simulate the cascading blackout of April 14th."
"Good. You didn’t run the breaker sequence. Now close the file and forget the password."
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: