EDITOR’S NOTE: Today’s post was orginally going to be a follow-up to yesterday’s post AI Tells Us How Five Solution Providers’ AI Can Help The LCBO During A Rail Strike. However, based on a question I received in the the corresponding LinkedIn discussion stream, we are going to go in a different direction today? You should use the previous link to join what is a very energized and insightful discussion by some of our industry’s top thinkers – in short, come on in, the water’s great!
Supporting the Liquor Control Board of Ontario (LCBO) during a rail strike requires a procuretech provider that offers strong supply chain visibility, risk management, and flexibility in sourcing and logistics. Considering these needs, SAP Ariba stands out as one of the best options to support LCBO during a rail strike. Here’s why:
1. Comprehensive Supplier Network
2. Supply Chain Visibility and Risk Management
3. Flexible Procurement and Logistics Solutions
4. Cost Management and Efficiency Optimization
5. Scenario Planning and Contingency Strategies
6. Seamless Integration with Existing Systems
7. Sustainability and Compliance
Alternative Providers
While SAP Ariba is a strong candidate, other providers like Jaggaer and Coupa could also offer valuable support:
- Jaggaer: Known for its robust supplier management and advanced analytics capabilities, Jaggaer can provide strong visibility and risk management, making it a good alternative for managing the complexities of a rail strike.
- Coupa: Coupa’s spend management and procurement solutions, combined with its focus on supply chain visibility, can help LCBO manage costs and maintain operational efficiency during the disruption.
Conclusion
Given the LCBO’s specific needs during a rail strike—such as the need for robust supplier management, real-time visibility, and flexible sourcing—SAP Ariba emerges as the best procuretech provider to support the organization. Its comprehensive suite of tools and integrations will help LCBO navigate the challenges of the rail strike effectively, ensuring continuity of supply and minimizing disruptions to its operations.
What Do 40-plus Years Think?
After 40-plus years in high tech and almost as long in procurement, it is amazing what a generational understanding of our industry provides. In short, you can break through the silos of the different IT eras while having a front-row seat to procurement’s evolution from a back-office adjunct of finance to becoming a strategic imperative in a volatile global economy.
Through this extended lens, I view what is happening today based on what happened in the past. In the case of SAP’s AI recommendation, here is a paper I wrote in 2008 for the CATA Alliance and the Ontario Knowledge Cluster.
ACCESS PAPER THROUGH SLIDESHARE LINK: https://www.slideshare.net/piblogger/sap-a-propensity-for-failure
While I encourage you to read the white paper in its entirety – it really is an eye-opening read in 2024, here is the paper overview:
This white paper was originally released in early 2008 and examines the myriad of challenges experienced by government organizations in their efforts to successfully implement an SAP-based eProcurement solution.
Citing actual case studies, including the City of Houston and Kings County, it is ironic that, against the backdrop of SAP’s current move towards offering a SaaS-based model, the relevance of these failed projects takes on an even greater significance.
An added benefit is the revelation that colossal failures such as these were not limited to the public sector as demonstrated by misses at companies such as Hewlett-Packard, Fox Meyer Drugs, and Hershey Food Corp. as it demonstrates an inherent flaw in the foundational premise of ERP-based initiatives.
This raises many questions with the ChatGPT search, such as on what it has based its recommendation of SAP Ariba and how far back in history it will go to provide a much-needed collective history of a subjective. In short, is it limited by an unintentional selective bias? This last point should be especially troubling for those using AI to screen suppliers in areas of past performance and compliance.
30
Procurement Insights
Who Did “AI Pick” As The Best Solution Provider For LCBO?
Posted on August 14, 2024
0
EDITOR’S NOTE: Today’s post was orginally going to be a follow-up to yesterday’s post AI Tells Us How Five Solution Providers’ AI Can Help The LCBO During A Rail Strike. However, based on a question I received in the the corresponding LinkedIn discussion stream, we are going to go in a different direction today? You should use the previous link to join what is a very energized and insightful discussion by some of our industry’s top thinkers – in short, come on in, the water’s great!
Supporting the Liquor Control Board of Ontario (LCBO) during a rail strike requires a procuretech provider that offers strong supply chain visibility, risk management, and flexibility in sourcing and logistics. Considering these needs, SAP Ariba stands out as one of the best options to support LCBO during a rail strike. Here’s why:
1. Comprehensive Supplier Network
2. Supply Chain Visibility and Risk Management
3. Flexible Procurement and Logistics Solutions
4. Cost Management and Efficiency Optimization
5. Scenario Planning and Contingency Strategies
6. Seamless Integration with Existing Systems
7. Sustainability and Compliance
Alternative Providers
While SAP Ariba is a strong candidate, other providers like Jaggaer and Coupa could also offer valuable support:
Conclusion
Given the LCBO’s specific needs during a rail strike—such as the need for robust supplier management, real-time visibility, and flexible sourcing—SAP Ariba emerges as the best procuretech provider to support the organization. Its comprehensive suite of tools and integrations will help LCBO navigate the challenges of the rail strike effectively, ensuring continuity of supply and minimizing disruptions to its operations.
What Do 40-plus Years Think?
After 40-plus years in high tech and almost as long in procurement, it is amazing what a generational understanding of our industry provides. In short, you can break through the silos of the different IT eras while having a front-row seat to procurement’s evolution from a back-office adjunct of finance to becoming a strategic imperative in a volatile global economy.
Through this extended lens, I view what is happening today based on what happened in the past. In the case of SAP’s AI recommendation, here is a paper I wrote in 2008 for the CATA Alliance and the Ontario Knowledge Cluster.
ACCESS PAPER THROUGH SLIDESHARE LINK: https://www.slideshare.net/piblogger/sap-a-propensity-for-failure
While I encourage you to read the white paper in its entirety – it really is an eye-opening read in 2024, here is the paper overview:
This white paper was originally released in early 2008 and examines the myriad of challenges experienced by government organizations in their efforts to successfully implement an SAP-based eProcurement solution.
Citing actual case studies, including the City of Houston and Kings County, it is ironic that, against the backdrop of SAP’s current move towards offering a SaaS-based model, the relevance of these failed projects takes on an even greater significance.
An added benefit is the revelation that colossal failures such as these were not limited to the public sector as demonstrated by misses at companies such as Hewlett-Packard, Fox Meyer Drugs, and Hershey Food Corp. as it demonstrates an inherent flaw in the foundational premise of ERP-based initiatives.
This raises many questions with the ChatGPT search, such as on what it has based its recommendation of SAP Ariba and how far back in history it will go to provide a much-needed collective history of a subjective. In short, is it limited by an unintentional selective bias? This last point should be especially troubling for those using AI to screen suppliers in areas of past performance and compliance.
30
Share this:
Related