The basic idea for this (series of) blogpost(s) is pretty simple: graph problems are often characterised by lots of connections between entities, and by queries that touch many (or an unknown quantity) of these entities. One of the prime examples is pathfinding: trying to understand how different entities are connected to one another, understanding the cost or duration of these connections, etc. So pretty quickly, you understand that logistics and supply chain management are great problems to tackle with graphs, if you think about it. Supply Chains are graphs. So why not story and retrieve these chains with a graph database? Seems obvious.
We've also had lots of examples of people trying to solve supply chain management problems in the past. Take a look at some of these examples:
- https://neo4j.com/graphgist/supply-chain-management
- https://neo4j.com/blog/graph-technology-supply-chain-transparency-corporate-social-responsibility/
- https://neo4j.com/news/graphing-the-supply-chain/ and https://www.enterprisetimes.co.uk/2019/09/10/graphing-the-supply-chain/
- https://neo4j.com/blog/nlp-at-scale-maintenance-supply-chain-management/
- Our friends at Caterpillar used Neo4j for this:
- TransparencyOne actually built a business on it:
So I had long thought that it would be great to have some kind of a demo dataset for this use case. Of course it's not that difficult to create something hypothetical yourself - but it's always more interesting to work with real data - so I started to look around.
