While enterprise transportation systems sat blind to what was happening on the road, an SAP engineer at ITC Infotech identified the gap, designed a solution, and brought it to market as a commercial product before the industry had a name for what he was building.
Rajashiva Ramalingam had a recurring frustration across enterprise logistics deployments, and it was not the kind of problem that vendor documentation acknowledged. The SAP Transportation Management and Event Management systems he was implementing were technically capable platforms. Configured correctly, they could plan freight, select carriers, monitor shipments, and settle invoices across complex international supply chains. What they could not do was see past the office door.
The moment a truck left a warehouse, the system’s view of that shipment depended entirely on whether someone at a desk entered an update. Drivers had no connection to the platform. Carrier dispatchers communicated by phone or fax. Proof of delivery was a paper document that could sit in a truck cab for days. The system knew what should be happening. It had no reliable way of knowing what was.
Ramalingam’s response was not to work around the limitation, as most practitioners did. He decided to build what was missing.
The result was MobiSmart, a mobile application developed during his tenure as Senior SAP TM and Event Management consultant at ITC Infotech, connecting shippers and carriers directly to SAP Transportation Management and SAP Event Management in real time, from the field, without requiring access to a corporate network or a full SAP installation. The platform was developed and commercialized by ITC Infotech, a global technology firm and wholly owned subsidiary of ITC Ltd, one of India’s largest conglomerates, and marketed to enterprise clients across the manufacturing, retail, consumer goods, and high-tech sectors.
Seeing the Problem Others Described As Unavoidable
The visibility gap Ramalingam identified was not a secret in the logistics industry. Shippers and carriers had long accepted that real-time freight data was difficult to capture, and that the information inside their transportation management systems would always lag behind what was happening on the road. Most practitioners treated this as a structural constraint of the technology rather than a solvable engineering problem.
Ramalingam did not accept that framing. His background was in system-level design: he had spent years working across SAP Transportation Management, Event Management, and Extended Warehouse Management implementations, developing a technical understanding of how these platforms were architecturally connected and where the gaps between them created operational failures. The visibility problem, in his analysis, was not caused by a limitation in SAP’s core technology. It was caused by the absence of a connected mobile layer that could bring field personnel into the system in real time.
SAP Event Management, the platform designed to monitor freight against expected milestones and trigger alerts when shipments deviated from plan, was built to receive event data from connected sources. Without a mobile field data source, it was monitoring against a plan using information that was often hours or days behind reality. The platform was capable. The connection was missing.
Ramalingam did not accept that the visibility gap was a structural constraint. He identified it as an engineering problem with an engineering solution.
His assessment was that building a mobile front end, one that used SAP’s own documented interface standards rather than proprietary integration points, would close the gap without requiring modifications to the core SAP environment. That architectural judgment shaped every decision that followed.
What Ramalingam Designed and Why It Held Together
The platform Ramalingam led into production was organized around four capabilities, each targeting a specific failure point in the shipper-carrier relationship that existing enterprise tools left unaddressed.
For track and trace, he built a module that gave both shippers and carrier personnel a live view of freight status from a mobile device. Drivers and carrier staff could log loading confirmations, in-transit updates, delay notifications, and arrival records directly from the field. Shipment and truck locations are rendered on a map in real time. The module connected to SAP Event Management to trigger alerts and notifications automatically when exception conditions were detected, and allowed carrier representatives to record proof of delivery and upload supporting documents without returning to an office.
For carrier tendering, Ramalingam brought the subcontracting workflow into the mobile environment. Shippers could issue loads and create requests for quotation through the application. Carriers received instant notifications and responded in real time. The shipper reviewed responses and awarded the quotation through the same interface. A process that had previously involved multiple communication steps, email chains, and manual follow-up was compressed into a single mobile workflow.
For freight invoicing, he designed a module that closed the settlement loop at the point of delivery. Once a carrier recorded proof of delivery, the carrier could initiate an invoice directly from the mobile device, sending it to the shipper for review. Both parties could perform approval, rejection, and dispute management through the platform, compressing a financial cycle that previously took days.
The reporting module surfaced carrier performance data, fleet utilization metrics, and on-time delivery rates for transportation managers, making information that previously required back-office access available in the field.
The Architectural Choices That Defined the Platform
Ramalingam built MobiSmart using SAP UI5, SAP’s own user interface technology framework, connected to SAP Transportation Management and Event Management through standard OData services via SAP NetWeaver Gateway. The architecture was platform-agnostic by design, running across web browsers, Android, and iOS from the same codebase.
The decision to use standard OData services rather than proprietary or semi-documented integration points was deliberate and consequential. Many tools that connect to SAP are built against undocumented internal interfaces that break when SAP releases major updates, creating ongoing maintenance overhead. By anchoring MobiSmart to the same interface layer that SAP uses for its own Fiori applications, Ramalingam ensured that the platform would remain structurally compatible with future SAP releases without requiring custom modifications to the underlying system after each update cycle.
He also required that the application use transportation and logistics industry messaging standards for communication between the mobile layer and the SAP back end. This was not a formality. For event updates posted by drivers in the field to integrate correctly with SAP Event Management’s alert and notification framework, those updates needed to arrive in the precise format the platform expected. A driver recording a delivery confirmation in the field was creating a data object that had to behave identically to an event posted by a back-office system administrator. Ramalingam designed the communication layer to guarantee that consistency.
The driver recording a delivery in the field was creating a data object that had to behave identically to one posted by a system administrator. Ramalingam designed the communication layer to guarantee that consistency.
He also designed MobiSmart to extend beyond the standard shipper-and-third-party-carrier model. Organizations operating their own vehicle fleets could extend the platform to cover their own drivers and assets using the same framework, making MobiSmart applicable across a wider range of logistics operating models than a tool designed for a single scenario. This extensibility reflected Ramalingam’s orientation toward systems that could adapt, an orientation that would later define his approach to larger enterprise transformation programs.
From Consulting Work to Commercial Product
What distinguished Ramalingam’s contribution here from the routine output of enterprise consulting was the trajectory from identified gap to commercial product. Most practitioners who encounter a missing capability in the software they are implementing build a workaround for the client in front of them and move on. Ramalingam identified the gap, designed a solution with genuine architectural coherence, and worked to bring it to market through ITC Infotech as a product available to enterprise clients across industries.
MobiSmart was not a prototype or a client-specific customization. It was a commercial offering, developed within a serious technology firm with an existing enterprise client base in supply chain, manufacturing, and retail, and positioned as a complement to SAP Transportation Management implementations. The business case ITC Infotech made for the product, better data quality, real-time field visibility, improved carrier partnership, measurable reductions in manual intervention, reflected the specific failure modes Ramalingam had documented across his implementation work.
That move from practitioner to product developer is relatively uncommon in the enterprise SAP consulting world, and it reflected a characteristic that would mark Ramalingam’s later career as well: the willingness to treat the systems he worked with as objects worthy of rigorous improvement rather than fixed products to be deployed and maintained.
A Pattern That Continued
Ramalingam has since held senior roles at organizations including Merck, A.P. Moller Maersk, and ACCO Brands, where he currently serves as Manager of SAP Transportation Management and Warehouse Applications. In that role he has led a global migration from SAP TM 9.5 to S/4HANA, integrated SAP TM with real-time freight visibility platform Project 44, and built automated transportation optimization systems for direct-to-customer and LTL shipments.
His published research, a peer-reviewed paper demonstrating that systematic freight consolidation in SAP S/4HANA Transportation Management environments can reduce transportation costs by up to 22.7 percent, applied the same diagnostic approach he brought to MobiSmart: identifying a gap between what enterprise logistics technology is capable of and what it actually delivers in practice, then building a rigorous, documented case for how to close it.
MobiSmart was an early expression of that pattern. The field visibility problem it addressed has since become one of the most heavily invested areas in supply chain technology, as the industry has spent heavily on real-time freight visibility platforms, connected carrier ecosystems, and event-driven logistics infrastructure. Ramalingam identified and addressed that challenge at a time when the enterprise logistics community was still treating it as an unavoidable limitation of the technology.
The gap he built MobiSmart to fill is the same gap the industry is still working to close. He started earlier, and he built something real.
