Air cargo market enjoys some calm before an expected Q4 storm
It has been a quiet couple of weeks in airfreight, owing to China’s Golden Week. Overall ...
XOM: INCOME PLAYSTLA: BOUNCING FROM LOWSCHRW: A SLEW OF UPGRADES MAERSK: MOMENTUMAAPL: BOOOOMMMAMZN: CONF CALL TRANSCRIPT SCREENING ZIM: MAERSK BOOST DHL: SHRUGGING OFF CYBER TROUBLE SO FARGXO: WINCANTON RISK HEIGHTENSGXO: REMARKS THAT WERE NOT LIKEDMAERSK: SURGINGMAERSK: CLIENTS NOT EXPECTED TO PAY MORE FOR GEMINIMAERSK: NO GXO APPETITEMAERSK: 'NOT FULLY SATISFIED YET' MAERSK: 'GEMINI DESIGN' MAERSK: GEMINI NETWORK MOVING PARTSMAERSK: CAPITAL RETURNSMAERSK: CONSOLIDATION ON THE RADARMAERSK: CONF CALL
XOM: INCOME PLAYSTLA: BOUNCING FROM LOWSCHRW: A SLEW OF UPGRADES MAERSK: MOMENTUMAAPL: BOOOOMMMAMZN: CONF CALL TRANSCRIPT SCREENING ZIM: MAERSK BOOST DHL: SHRUGGING OFF CYBER TROUBLE SO FARGXO: WINCANTON RISK HEIGHTENSGXO: REMARKS THAT WERE NOT LIKEDMAERSK: SURGINGMAERSK: CLIENTS NOT EXPECTED TO PAY MORE FOR GEMINIMAERSK: NO GXO APPETITEMAERSK: 'NOT FULLY SATISFIED YET' MAERSK: 'GEMINI DESIGN' MAERSK: GEMINI NETWORK MOVING PARTSMAERSK: CAPITAL RETURNSMAERSK: CONSOLIDATION ON THE RADARMAERSK: CONF CALL
German software giant SAP has defended itself against claims that it was at fault for the €345m write-off by Deutsche Post-DHL due to its abandoned New Forwarding Environment (NFE) IT renewal programme.
The company said: “Recent media reports suggest there is a connection between SAP and problems with the implementation of a new logistics system at DHL. These statements regarding SAP are incorrect.
“SAP was not commissioned by DHL as general contractor and SAP software was not the root cause of the problems. Since 2011 DHL has revised its global logistics system to be rolled out in more than 120 countries. SAP was at no time responsible for the project management and software installation.
“In fact, SAP has offered early support beyond the actual contractual status as a software supplier,” it added.
Part of the confusion may arise from DP-DHL chief executive Frank Apple’s frequent references to SAP systems during DP-DHL’s recent third-quarter results presentation. He announced the company’s new IT strategy, following the well-publicised demise of NFE under previous DHL Global Forwarding chief Roger Crook.
He said: “We want to standardise and harmonise our processes in order to avoid double work and have better data management which will lead to further efficiencies. The first steps will be next year with shipment visibility and documentation management.
“We don’t need an SAP system to do this – we are going to use existing systems which we are going to roll out worldwide, and we believe that this strategy will lead to more incremental change,” Mr Appel said, describing a “middleware architecture” which was part of NFE.
“The middleware is working quite well and allows us to roll out our own products or to acquire products on the market – whether these are going to be SAP or not is still to be decided, but we can use a modular approach.
“It is easier for the organisation to digest this because we don’t have to renew everything at the same time, we can go in step-by-step process and do what is required by the forwarding industry,” he said.
And smaller forwarders that have adopted a more digital-first approach to forwarding systems and the way they are used by both employees and customers.
Flexport chief executive and founder Ryan Petersen told The Loadstar: “My personal view is that this has not been so much an IT problem as a change-management issue – what a lot of the big freight forwarders do is try to change everything at once and it is almost impossible to pull off.
“Whereas we have had the luxury of starting small and manually upgrading different parts of the system,” he said.
However, the high priority that DHL has placed on renewing its IT architecture and increasing customer and employee visibility will be a key forwarders strength, Mr Petersen said.
Flexport, which is based in San Francisco and describes itself as “a freight forwarder built for the modern era”, recently raised $22m from Silicon Valley investors, which will mainly be spent on software engineers’ wages, said Mr Petersen.
And the first development the company set out to do after its inception was to create an app for shippers which gave greater visibility across supply chains.
“We built a dashboard which structures all the data that’s coming out of their supply chains and makes it visible. There is a large amount of information but it is all in different documents issued in different formats such as PDFs, excel or as j-peg images. Our app collects all that information and structures it so that shippers have total visibility of their supply chains down to the SKU level,” he said.
Comment on this article
Peter Mancuso
December 02, 2015 at 7:15 pmWonder when Panalpina will finally wake up from the ‘perfect dream’ of SAP TM solving all their internal issues, now that DGF abandoned ship…
Teaba
May 30, 2020 at 8:17 pmI didn’t know Panalpina went the same root. I hope they have wake up earlier than DHL, unless SAP learnt from DHL disaster.
Ross
December 02, 2015 at 10:24 pmStructured architecture can be a significant party in an enterprise system development failure if it inhibits developers. This sits outside the realm of a developmental roles and contracts.
If the architecture was part of the problem SAP would be judged here to have come up with a strawman in response. Any whiff of a case being merely being plausibly deniable no longer cuts the mustard in commercial terms. German companies should have learned well enough by now to be cautious and ‘fess up if they are party to significant commercial issues. They should also never see themselves as being so far down the track in the engineering sense that they can’t take severe corrective measures if required.
At Gilead we have addressed the process cadre cult of recent decades and defined a specific role for transportation enterprise middleware in the E-commerce age.
R E Krem
December 14, 2015 at 11:02 pmDHL is and always be a 1 eyed cyclops, no vision, no leadership, no execution: despicable organization,, 1st hand knowledge after 4 yrs executive Management …disgraceful
Taeba
May 30, 2020 at 8:15 pmThe main problem with NFE implementation was not the “change management” as guessed by Ryan Petersen. The original DHL management was good, unfortunately the Chroatian (if I remember correctly) advisor was not. I believe she was responsible for employing an external company to write down the requirements, it was a disaster because they did not align with the requirements collected by DHL staff. But this was only a tip of an iceberg. The main problem was that it was not possible to adopt SAP to forwarding needs especially when, to most of the requirements, the SAP specialists were always saying “this is the system standard” or something like that. It’s difficult to remember after so many years.
DHL GF would do a much better job if they developed an in-house system which would suit all their needs instead of trying to adopt a system which was never built for forwarders.
Ryan Petersen was right in a way about management, there were problems. There were many good people who lost their jobs, people who were brave enough to say that this system will never work, some of them worked for DHL for 10-20 years. A few people even lost their lives during implementation, some suspected that they had a heart attack because they were under too much stress.