Category Archives: Technology

One Supply Chain Misconception That Should Be Cleared Up Now

This originally posted May 14 (2024).  It’s being reposted because this definitely needs to be cleared up before the new year (due to the constant proliferation of AI, which is, when all is said and done, just another technology).

Not that long ago, Inbound Logistics ran a similarly titled article that quoted a large number of CXOs that made some really good observations on common misconceptions that included, and are not necessarily limited to (and you should check out the article in full as a number of the respondents made some very good points on the observations):

The misconceptions included statements that supply chains should:

  • reduce cost and/or track the most important metric of cost savings
  • accept negotiations as a zero-sum game
  • model supply chains as linear (progression from raw materials to finished goods)
  • … and made up of planning, buying, transportation, and warehousing silos
  • … and each step is independent of the one that proceeds and follows
  • accept they will continue to be male dominated
  • become more resilient by shifting production out of countries to friendly countries
  • expect major delays in transportation
  • … even though traditional networks are the best, even for last-mile delivery
  • accept truck driver shortage as a systemic issue
  • accept the blame when anything in them goes wrong
  • only involve supply chain experts
  • run on complex / resource intensive processes
  • … and only be optimal in big companies
  • … which can be optimized one aspect at a time
  • press pause on innovation or redesign or growth in a down market
  • be unique to a company and pose unique challenges only to that company
  • not be sustainable as that is still cost-prohibitive
  • see disruption as an aberration
  • return to (the new) normal
  • use technology to fix everything
  • digitalize as people will become less important with increasing automation and AI in the supply chain

And these are all very good points, as these are all common misconceptions that the doctor hears too much (and if you go through enough of the Sourcing Innovation archives, it should become clear as to why), but not the biggest, although the last one gets pretty close.

 

THE BIGGEST SUPPLY CHAIN MISCONCEPTION

We Can Use Technology to Do That!

the doctor DOES NOT care what “THAT” is, you cannot use technology to do “THAT” 100% of the time in a completely automated way. Never, ever, ever. This is regardless of what the technology is. No technology is perfect and every technology invented to date is governed by a set of parameters that define a state it can operate effectively in. When that state is invalidated, because one or more assumptions or requirements cannot be met, it fails. And a HUMAN has to take over.

Even though really advanced EDI/XML/e-Doc/PDF invoice processing can automate processing of the more-or-less 85% of invoices that come in complete and error free, and automate the completion and correction of the next 10% to 13%, the last 2% to 5% will have to be human corrected (and sometimes even human negotiated) with the supplier. And this is technology we’ve been working on for over three decades! So you can just imagine the typical automation rates you can expect from newer technology that hasn’t had as much development. Especially when you consider the next biggest misconception.

Enterprises have a Data Problem. And they will until they accept they need to do E-MDM, and it will cost them!

This originally published on April (29) 2024.  It is being reposted because MDM is becoming more essential by the day, especially since AI doesn’t work without good, clean, data.

insideBIGDATA recently published an article on The Impact of Data Analytics Integration Mismatch on Business Technology Advancements which did a rather good job on highlighting all of the problems with bad integrations (which happen every day [and just result in you contributing to the half a TRILLION dollars that will be wasted on SaaS Spend this year and the one TRILLION that will be wasted on IT Services]), and an okay job of advising you how to prevent them. But the problem is much larger than the article lets on, and we need to discuss that.

But first, let’s summarize the major impacts outlined in the article (which you should click to and read before continuing on in this article):

  • Higher Operational Expenses
  • Poor Business Outcomes
  • Delayed Decision Making
  • Competitive Disadvantages
  • Missed Business Opportunities

And then add the following critical impacts (which is not a complete list by any stretch of the imagination) when your supplier, product, and supply chain data isn’t up to snuff:

  • Fines for failing to comply with filings and appropriate trade restrictions
  • Product seizures when products violate certain regulations (like ROHS, WEEE, etc.)
  • Lost Funds and Liabilities when incomplete/compromised data results in payments to the wrong/fraudulent entities
  • Massive disruption risks when you don’t get notifications of major supply chain incidents when the right locations and suppliers are not being monitored (multiple tiers down in your supply chain)
  • Massive lawsuits when data isn’t properly encrypted and secured and personal data gets compromised in a cyberattack

You need good data. You need secure data. You need actionable data. And you won’t have any of that without the right integration.

The article says to ensure good integration you should:

  • mitigate low-quality data before integration (since cleansing and enrichment might not even be possible)
  • adopt uniformity and standardized data formats and structures across systems
  • phase out outdated technology

which is all fine and dandy, but misses the core of the problem:

Data is bad (often very, very bad), because the organizations don’t have an enterprise data management strategy. That’s the first step. Furthermore this E-MDM strategy needs to define:

  1. the master schema with all of the core data objects (records) that need to be shared organizational wide
  2. the common data format (for ids, names, keys, etc.) (that every system will need to map to)
  3. the master data encoding standard

With a properly defined schema, there is less of a need to adopt uniformity across data formats and structures across the enterprise systems (which will not always be possible if an organization needs to maintain outdated technology either because a former manager entered into a 10 year agreement just to be rid of the problem or it would be too expensive to migrate to another system at the present time) or to phase out outdated technology (which, if it’s the ERP or AP, will likely not be possible) since the organization just needs to ensure that all data exchanges are in the common data format and use the master data encoding standard.

Moreover, once you have the E-MDM strategy, it’s easy to flush out the HR-MDM, Supplier/SupplyChain-MDM, and Finance-MDM strategies and get them right.

As THE PROPHET has said, data will be your best friend in procurement and supply chain in 2024 if you give it a chance.

Or, you can cover your eyes and ears and sing the same old tune that you’ve been singing since your organization acquired its first computer and built it’s first “database”:

Well …
I have a little data
I store it on my drive
And when it’s old and flawed
The data I’ll archive

Oh, data, data, data
I store it on my drive
And when it’s old and flawed
The data I’ll archive

It has nonstandard fields
The records short and lank
When I try to read it
The blocks all come back blank

I have a little data
I store it on my drive
And when it’s old and flawed
The data I’ll archive

My data is so ancient
Drive sectors start to rot
I try to read my data
The effort comes to naught

Oh, data, data, data
I store it on my drive
And when it’s old and flawed
The data I’ll archive

It’s Not AI (First,Led,Powered,etc.) or Autonomous. It is Solution with Augmented Intelligence!

By now you know our stance on Gen-AI (and how it should be relegated to the rubbish heap from which it came) because it’s not about “AI”, it’s about outcome. And outcome requires a real, predictable, usable solution that helps Human Intelligence (HI!) make the right decision. Such a solution is one that uses tried and true algorithms that support tried and true processes that provide a human with the insight needed to make the right decision at the time, every time a decision needs to be made.

This requires a solution that walks the human user through the process, step by step, and presents them with the information required to make a decision as to whether to progress to another step, what the next step is, and any conditions that need to be put on that next step. This requires a solution that automatically runs all of the typically relevant analysis, on all of the available data, and presents the insight, along with any typical decisions (as [a] default recommendation[s]) made on any similar situations that can be found in the organizational history.

Automation should only occur in situations the organization has defined as acceptable according to well defined, human reviewed, and verified rules. Not default vendor rules or unverified probabilities or unverified random computations from a random algorithm. A good solution is one that walks a user through the process, often allowing each step to be completed with a single choice or click. It’s not one that makes the choice for the user, which may or may not be the right one, but one that helps the user makes the right choice. It might seem like a subtle difference, but it is a very important one.

Even though an AI-powered autonomous solution might seem to make the right decision over 90% (or 95%) of the time, it doesn’t mean it actually is. If it looks right, it might be a good decision, but it doesn’t mean it’s a good decision for the organization at the time, or the best decision that can be made. Only human review, at the time, can make that decision. A good solution runs all the analysis it can, summarizes the results, and lets a human verify the data for any recommendation made by the system.

To better understand the the subtlety, consider a situation where the organization lets the system automatically re-auction all regularly purchased products and commodities for manufacturing or MRO where the price is typically constant over time using a lowest bidder takes all e-Auction that results in the auto-generation and auto e-Signature of a one year contract. Now, most of the time this is probably going to work okay, but imagine you let it run on full auto-pilot and in the e-Auction queue is your regular RAM contract that expired three days after a major RAM plant factory fire (that happens about once every decade if you trace back through the last forty years), and prices have just skyrocketed about 50%. Prices which would drop back down as soon as the plant comes back online in three months. Locking in a full year contract would result in excessive cost overruns on the items for almost nine months longer than necessary, instead of just three months or so. A human would know to buy the bare minimum on the spot market at overly inflated rates and wait until the market stabilized before running an e-Auction to lock in the next contract. But a system told to just re-auction and re-order at every contract expiration would do this that. It wouldn’t know that the current market rates are just temporary, why, and how to change course. This is just one example where over-automation and AI will lead to failure without Human Intervention.

A good system presents the user with the products/commodities that are typically automatically auctioned, the history of costs, the current market costs, the recommendation for auto-sourcing and term, the expected results, and whether the recommendation is for the auction to auto-award and contract or, when the auction is complete, pause and include a human in the loop to make a final decision. A well designed system minimizes the work and input required by a human, eliminating all the tactical data analysis and e-paperwork, making it easy to make the right strategic decision without a lot of effort. Technology isn’t about trying to replace human intelligence (which it can’t), but about eliminating unnecessary drudgery or computation (“thunking”) that humans are not good at (or don’t have the time for), so that humans can focus on strategic decisions and value add.

That’s why the right answer is always a solution with augmented intelligence. Not autonomous AI solutions.

The Complete AI in Procurement, Sourcing, and Supplier Management: No Gen-AI Needed Series Indexed

The Complete AI in X (No Gen-AI) Series, 2018/2019 and 2024!

CLASSIC (SM Content Hub)

AI In Procurement

AI in Procurement Today Part I
AI in Procurement Today Part II

AI in Procurement Tomorrow Part I
AI in Procurement Tomorrow Part II
AI in Procurement Tomorrow Part III

AI in Procurement The Day After Tomorrow

AI in Sourcing

AI in Sourcing Today

AI in Sourcing Tomorrow Part I
AI in Sourcing Tomorrow Part II

AI in Sourcing The Day After Tomorrow

AI in Supplier Discovery

AI in Supplier Discovery Today

AI in Supplier Discovery Tomorrow

AI in Supplier Discovery The Day After Tomorrow

AI in Supplier Management

AI in Supplier Management Today Part I
AI in Supplier Management Today Part II

AI in Supplier Management Tomorrow Part I
AI in Supplier Management Tomorrow Part II

AI in Supplier Management The Day After Tomorrow

AI in Optimization

AI In Sourcing Optimization Today

AI In Sourcing Optimization Tomorrow

AI In Sourcing Optimization The Day After Tomorrow Part I
AI In Sourcing Optimization The Day After Tomorrow Part II

CURRENT (Your SI!)

AI In Procurement

Advanced Procurement Yesterday: No Gen-AI Needed

Advanced Procurement Today: No Gen-AI Needed

Advanced Procurement Tomorrow: No Gen-AI Needed

AI in Sourcing

Advanced Sourcing Yesterday: No Gen-AI Needed

Advanced Sourcing Today: No Gen-AI Needed

Advanced Sourcing Tomorrow: No Gen-AI Needed

AI in Supplier Discovery

Advanced Supplier Discovery Yesterday: No Gen-AI Needed

Advanced Supplier Discovery Today: No Gen-AI Needed

Advanced Supplier Discovery Tomorrow: No Gen-AI Needed

AI in Supplier Management

Advanced Supplier Management Yesterday: No Gen-AI Needed

Advanced Supplier Management Today: No Gen-AI Needed

Advanced Supplier Management Tomorrow: No Gen-AI Needed

You Should Never Build Your Own ProcureTech Solution! Ever!

Integrate your own custom suite to suit your processes, maybe, but never build from scratch. (And we should not have to be talking about this again after just publishing on the subject two weeks ago, but too many conversations are indicating that we still need to shout this loud and clear!)

For some reason, this comes up every decade, usually after a hype cycle has peaked, marketers have switched from focussing on solutions to sound bites from a suite of providers who have released products that don’t meet customer needs, the implementation failure rate has edged back up to the 80%+ range, and customers have gotten absolutely positively fed up with the whole situation.

Customers, fed up with the valueless hype, marketing sound bites, high failure rate, and utter lack of solutions from the vendors targeting them on a daily basis, start to think that the right solution is to build their own.

Sourcing Innovation tackled this subject in depth back in 2015 when it wrote a 4-part series on why you should NOT build your own e-Sourcing solution, followed by an explanation of why you should not build your own Contract Management and e-Procurement platform. (links here)

That’s why we are both repeating and elaborating on last Friday’s Rant on why A Company Should Never Build It’s Own Enterprise Software Systems.

Not only do we have the situation where:

  • the company is not an expert in building software products
  • the company is not an expert in best practices across all of its processes
  • by the time a custom solution is developed, it’s out of date
  • it’s not about the product, it’s about the process you should be working toward and, most importantly,
  • it’s about the data that drives the process!

But we have the situation where, as highlighted in THE REVELATOR‘s article:

1. Developing your own is NOT being an early adopter! (Which is what many companies considering build-your-own think they are.)

Early adopter means someone who adopts leading edge technology from a third party, not someone trying to fast track their digitization effort with custom built tech. This is just high risk with little chance of reward for all the reasons mentioned in all of our prior articles.

2. They think Gen-AI will fix their data problem and allow them to develop their own!

If you’re read anything on Gen-AI on this blog you know that’s the last thing it will do. For Gen-AI to have any chance of working at all, it needs a huge amount of good, clean, data. Otherwise, it’s garbage in, hazardous waste out. No technology has ever needed such large amounts of near-perfect data to have even an abysmal chance of working, and the fact that the marketing madness has convince many CPOs that Gen-AI can fix a data problem is downright terrifying!

3. They obviously think that the initial quote will be close to the final cost.

No where are cost overruns more extreme than in custom development by a non-software organization that contracts a Big X with poor specifications that look easy, and that, due to lack of manpower, sends The C-Team (if you are lucky) because it’s just another instance of system X (when it’s not).

To be honest, in this situation, if the costs ends up being only 3X to get something usable (but still not what you wanted), given the high technology failure rates, that would be amazing.

We know it’s hard to find appropriate solutions given all the noise out there, and the overabundance of vendors that all look, sound, and go all in on useless Gen-AI the same, as it just takes one glance at the Mega Map to figure that out, but that doesn’t mean there aren’t vendors out there appropriate for you. Vendors that put solutions, not tech first, that built affordable tech that works (and didn’t take too much money from investors who then insisted on quadrupling the price), and that will work in an ecosystem with out vendors to solve your problems.

You just have to look hard. Real hard. Probably harder than you’ve ever had to look before. (Expect to eliminate 6 out of every vendors you look at for short list consideration and probably go through 20 to find 3.) But trust us, when you find the right vendor, it will be worth it. The solution will work, will configure to your liking, will be extremely usable for the problems your team faces every day, and will be one where the provider will grow with you for the decade to come.

Good things come to those who wait to find the right vendor. (Even if they have to crawl through multiple pig sties to do so.)