The old system would have discovered the welder shortage three weeks later, when the missing girders stopped the entire bridge deck pour. Three months later, Elena presented to the board. But this time, she didn’t bring paper.
Her project coordinator, Mark, pointed at the paper. “The issue is data. Procurement uses Excel. Construction uses a whiteboard. Finance uses a legacy system that talks to no one. We have three versions of reality.”
Elena slammed a report on the table. “The Ministry of Transport just fined us $200k for missing a safety compliance milestone. A milestone I didn’t even know existed until the fine arrived.”
“One down,” she said. “One to go.”
“They’re throwing a party for us tonight,” Elena said. “But I want to show you something.”
Key SAP Project System Concepts Embedded in the Story: | Concept | Story Element | | :--- | :--- | | Work Breakdown Structure (WBS) | Breaking the bridge into survey, piling, girders, certification. | | Networks & Activities | Linking “pour deck” to “girder certification” with predecessors. | | Milestones with Tollgates | Safety certification milestone that blocked contractor payment. | | Integration with MM/FICO/HR | Bolts auto-ordered; costs live-updated; welder availability checked. | | Project Status Board / Early Warning | Red light for Supplier B delay; diesel price simulation. | | Change Request & What-If Analysis | Cross-supplier welder loan; fuel surcharge cap. | | Project Builder (PSP) | Central dashboard with schedule, cost, and variance. | | Project Closure & Settlement | Final milestone locking WBS and archiving to controlling area. |
On the left: the WBS hierarchy, clean as a skeleton. In the center: a with actual dates, forecast dates, and variance analysis. On the right: a Cost Dashboard showing committed costs, actual costs, and remaining budget—all in real time.
