"The numbers are green, Arjun," said Meera, the plant manager, pointing at a dashboard that showed production up 12%. "So why did we just lose the Eastern Rail contract?"
The next morning, Meera called an all-hands. The new alert sat on The Bridge’s main screen—not as a green dashboard, but as a single, blinking orange light. management information system waman s jawadekar pdf
Arjun Seth had been the IT director at Vikram Cement for three years. Every morning, he walked past the old server room—now a dusty graveyard of tape drives and dial-up modems—and into the glass-walled command center they called "The Bridge." "The numbers are green, Arjun," said Meera, the
Arjun pulled up a second screen—a raw data feed from the legacy ERP system. "Because our MIS shows averages . The Eastern Rail order required 10,000 tonnes of Grade-A slag cement. We delivered 9,800 tonnes of Grade-A and 200 tonnes of Grade-B mixed in. The average grade looks fine. The reality? Their inspection team rejected the entire shipment." Arjun Seth had been the IT director at
Meera stared at the glowing graphs. "Then your system is lying."
That night, Arjun didn't go home. He pulled the PDF up on his tablet—the same diagrams of three-level pyramids: operational, tactical, strategic. Vikram Cement had operational data (kiln temps) and strategic reports (annual forecasts), but the tactical layer—the layer that could have flagged the Grade-B mix before it left the plant—was missing.