SAP insider Magazine
A Single Pane of Glass That search led Lightner to SAP Cloud ALM, specifically its system monitoring capabilities. One of Lightner’s primary goals in rolling out SAP Cloud ALM was to create a central dashboard for under- standing what was happening across the SAP landscape — a place where the team could see the same facts at the same time after go-live. Rather than chasing issues across tools, tickets, and anecdotes, he wanted a way to quickly understand system health, performance, and user- impacting issues in one place. “Our key goal was to get a tool that had this single pane of glass view of our sys- tem landscape,” he recalls. Within a month, the team deployed SAP Cloud ALM to support IT opera- tions, with proactive monitoring estab-
mediate aftermath of go-live exposed deeper issues with how work was co- ordinated, tracked, and governed. Pro- ject artifacts lived across disconnected SharePoint sites, email threads, and spreadsheets. Action items from SAP readiness checks and service engage- ments were documented but not always followed through. Visibility across workstreams was lim- ited, and responsibility for outcomes was often unclear. “Some of those ac- tion items were just lost,” Lightner says. “There were too many things going on, too many separate documents.”
operations. Lightner oversees the tech- nical operations of Woodstream’s SAP landscape, spanning system stability, security, and integrations. One recur- ring issue was the expiration of secu- rity certificates used to connect SAP S/4HANA with external partners such as freight carriers. “FedEx or UPS, one of our carriers for example — whenever those certificates expire, that integration breaks and we can no longer communicate with UPS or FedEx,” Lightner explains illustrating the issue with data not being available in real time. “If that happens, we can’t ship prod- uct. We’re essentially dead in the water.” Each lapse triggered P1 or high-pri- ority incidents that quickly escalated to executive attention. Leadership wanted a long-term fix, not more firefighting.
Catching Issues Before They Caused Outages
The true inflection point came after implementation, during steady-state
31
let’s connect sapinsider.org
Made with FlippingBook - Share PDF online