- Florida Crystals is a case study for S/4HANA that has some surprising claims, including that the implementation was performed in an unheard of 4 weeks. In this article, we will cover the likelihood of what Florida Crystals says is true.
Florida Crystals is a sugar refiner based in Florida. Florida Crystals have made some rather extreme claims about its implementation of S/4AHANA. The following quotation is an excellent example of this.
This is a video of the CIO of Florida Crystals at an ASUG event.
4 Week Upgrade of S/4HANA?
“This year at ASUG Annual Conference and Sapphire Now, he announced that Florida Crystals had pulled off an upgrade to S/4HANA and Simple Finance 2.0 in just four weeks.” – ASUG
This is another one of the silly claims. This brings the Florida Crystals under suspicion as a client that received something in return for the claim. Once a company claims to be able to do something that is not possible, it does bring up the question of why they did it. So let us review some of the quotes from Florida Crystals.
Florida Crystals Chose S/4HANA Because it is not a Development Shop?
“We are not a development shop, so we rely on SAP for our IT solutions and innovations in feature and functions,” says Whittington, who was interviewed in the ASUGNews Studio at Annual Conference and Sapphire Now.
This is a peculiar statement as the vast majority of SAP customers are also not “development shops.” Development shops usually are software vendors. But this statement is a reason to use packaged applications in general. It is not a very good reason individually to purchase any one application in particular.
Florida Crystals Must be on the Bleeding Edge?
Of course, that requires Florida Crystals to stay very close to the bleeding edge with SAP’s new releases, but to Whittington, that’s worth the effort.
That is certainly untrue. The vast majority of SAP customers that run ECC are also not development shops, but they have not migrated to S/4HANA, and they don’t stay near the bleeding edge with SAP’s releases. Whittingham’s logic here is simply incorrect.
Not Worrying About Bricks and Mortar is a Good Reason to Purchase S/4HANA?
“Think about IT when you don’t have to worry about bricks and mortar and hardware, and you’ve got SAP as your development [shop],” he says, adding: “I think that’s the future.”
That is not the future, that is, in fact, the past. Companies transitioned from using predominantly internally built applications to packaged applications in the 1980s. Although there was never a complete transition as the packaged applications could never do everything that the custom-built applications could do.
In part of the quote Whittingham is actually describing not hosting an application or set of applications on premises, but instead either having one’s applications hosted or SaaS-based. But this is a different topic from whether a company purchases applications from a packaged software vendor, rather than building the applications internally.
When is it Wrong to do Due Diligence Up Front?
“During an interview in the ASUGNews Studio, Atkinson shares some of her lessons learned on the high-stakes project and how the team dealt with data migration challenges. “You’ve got to do your due diligence up front,” she says.”
This is a strange comment. When would the opposite be the case? Is Atkinson intimating that S/4HANA Finance is a challenging implementation? If so, the supposed 4-week implementation timeline would seem to contradict that.
I could go into more detail in the Florida Crystals S/4HANA implementation, but the case study is simply not credible. Florida Crystals are receiving some type of SAP-related benefit that is not being published. There are probably career reasons for why Florida Crystals attended ASUG and presented fallacious information on its S/4HANA experience. But those details are private.
Financial Bias Disclosure
Neither this article nor any other article on the Brightwork website is paid for by a software vendor, including Oracle, SAP or their competitors. As part of our commitment to publishing independent, unbiased research; no paid media placements, commissions or incentives of any nature are allowed.
S/4HANA Implementation Research
We offer the most accurate and detailed research into S/4HANA and its implementation history. It is information not available anywhere else and is critical correctly interpreting S/4HANA, as well as moderating against massive amounts of inaccurate information pushed by SAP and their financially biased consulting ecosystem.
Select the description that best matches you.
Option #1: Do You Work in Sales for a Vendor?
See this link for an explanation to sales teams.
Option #2: Do You Work for an Investment Entity that Covers SAP?
See this link for an explanation for investment entities.
Option #3: Are You a Buyer Evaluating S/4HANA?
For companies evaluating S/4HANA for purchase. See this link for an explanation to software buyers.
Search Our Other S/4HANA Content
The Risk Estimation Book
Better Managing Software Risk
The software implementation is risky business and success is not a certainty. But you can reduce risk with the strategies in this book. Undertaking software selection and implementation without approximating the project’s risk is a poor way to make decisions about either projects or software. But that’s the way many companies do business, even though 50 percent of IT implementations are deemed failures.
Finding What Works and What Doesn’t
In this book, you will review the strategies commonly used by most companies for mitigating software project risk–and learn why these plans don’t work–and then acquire practical and realistic strategies that will help you to maximize success on your software implementation.
Chapter 1: Introduction
Chapter 2: Enterprise Software Risk Management
Chapter 3: The Basics of Enterprise Software Risk Management
Chapter 4: Understanding the Enterprise Software Market
Chapter 5: Software Sell-ability versus Implementability
Chapter 6: Selecting the Right IT Consultant
Chapter 7: How to Use the Reports of Analysts Like Gartner
Chapter 8: How to Interpret Vendor-Provided Information to Reduce Project Risk
Chapter 9: Evaluating Implementation Preparedness
Chapter 10: Using TCO for Decision Making
Chapter 11: The Software Decisions’ Risk Component Model