This post has already been read 12125 times!
Why your “network” is not delivering the results you expect.
The confusion in the market about the difference between multi-enterprise or multi-party networks and other options, such as Planning and B2B Networks, is rampant. Yet the differences in performance, maintenance and implementation are huge. I looked at some of these differences in my post Multi-Enterprise Networks versus Pseudo Networks. Now I want to give some telltale signs that indicate a so-called network is not what it seems.
1. Proliferation of IT Connections
Beware of old school point to point B2B vendors claiming they have a Multi-Enterprise Network but really require new IT connections between each enterprise pair; and worse, new IT connections between functions across enterprise pairs (demand, inventory, transportation, etc.). Ask them if they can bring more than two parties onto the same workflow or make instant connections to another company that joined the network previously.
Single enterprise applications connected to a legacy B2B cloud platform still function as silo applications and suffer from a host of problems... - Geoff Annesley @onenetwork Click To Tweet2. Conglomeration of Enterprise Applications
Beware of vendors that have purchased “Single Enterprise Focused” applications designed for use by one company but claim they are now magically “Multi-Enterprise Apps” because the acquiring company has a B2B platform. These single enterprise applications connected to a legacy B2B cloud platform still function as silo applications with complex (hidden) behind the scenes app-to-app integrations, messy error-prone and often slow data translations between applications, master data management (MDM) cross-referencing, even separate databases. It doesn’t matter if they use the same RDBMS the application data models are rarely ported to a common data model because it requires expensive rewriting of algorithms and database access code. These applications connected to legacy cloud platforms also replicate important objects such as orders and planned events. All this causes synchronization, trust and timing issues.
3. Siloed Master Data Models
Beware of B2B vendors who have purchased or have legacy point solutions that run on siloed master data models that they claim work “seamlessly together” but in reality require on project master data mapping and duplicate transactions across their own application persistent stores (no true single version of truth across all parties and business functions on the network). This creates elongated and overly complicated deployment projects which drives up technical debt and costly maintenance which inhibits future business agility and automation.
Related: Ten Pillars of an Effective Network Platform
4. Separate Planning and Execution Systems
Beware of the high labor costs associated with operating and maintaining supply chain solutions designed around planning that rely on “other systems” for execution and one-off data aggregation projects for visibility. In order to really automate your end to end network planning must be designed to understand, modify and create real time transactions (orders, events, instructions) as well as workflows and processes that traverse multiple companies in your network.
Trying to bridge your planning system to your internal execution systems (often ERPs), is expensive and results in clunky and costly integrations, but more importantly the planning and execution with your partners is left to pin hole B2B data transfers that undermine your ability to optimize and automated the entire end-to-end network.
If you find that your data planning data models and policies diverge from reality, or you have to spin up special projects to feed your planning data models with accurate data such as real time asset locations, inventory status, real transportation lead times, capacities, etc., you are suffering the symptoms of the divide between planning and execution which will inhibit your ability to automate and optimize your network.
5. Automation Without Multi-Enterprise Coordination
Beware of solutions that claim they provide end-to-end visibility and automation when they are lacking multi-party workflows with shared applications on a shared real-time single version of the truth (SVOT). Many companies have invested heavily in B2B platforms and best of breed planning systems so why can’t they realize end-to-end automation and optimize their networks? To automate your end-to-end network you must have a platform and applications that is designed from the ground up for multi enterprise shared processes and algorithms: sense, learn, predict, plan, execute, measure). This requires multi-party permissions infused in all dimensions of the platform not just user roles and screen views.
One clear red flag that you don’t have a multi-enterprise platform is characterized by processes you have to spend manual time and effort on trying to model the external world in your internal application models such as external sites, lanes, lead times, capacities, inventory locations, etc. for entities that you don’t own. A multi-enterprise platform will have a multi-enterprise MDM system that allows each party to maintain the part of the network they own which keeps the network model in synch with reality which in turn enables feasible automated decisions to be made and drives the accuracy and trust required to transition to an end-to-end automated state.
6. Scalable without Self-Tuning and Learning
Beware of solutions that claim scalability and massive parallel planning capabilities but are not self-tuning, lack focused learning and require “planners” to continually update policies, data models and rely on static data model parameters. Ask your planners why they are still using Excel, email and phone calls to partners to “fill in the gaps” in their planning and execution processes.
Often, we find that “one company at a time” planning applications (with point to point B2B connections) and different planning and execution cadences between companies results in mismatches between plans, data models, time delays, visibility latency, gaming between parties which inhibits automation and results in extra manual effort and an inability to respond intelligently to fast changing supply and demand scenarios.
7. Deep Neural Networks are only part of the Solution
Beware of AI solution vendors that claim one massive Deep Neural Network (DNN) will solve all their supply chain problems. In reality many types of algorithms working together provide a much more effective and pragmatic approach to solving the vast array of network problems companies and networks encounter. When you can get the right answer with a heuristic or other type of manually crafted algorithm there is no need to waste time and increase complexity by training a DNN for that task.
Using DNNs in the right area with the ability for DNN digital agents to work with other types of digital agent algorithms enables a pragmatic, controllable and superior approach to optimizing the entire end-to-end network.
Related: 8 Keys to Success with Artificial Intelligence in Supply Chains
8. Lack of Digital Agents and a Digital Agent Fabric
Recognizing patterns with DNNs and Analytics is only part of the equation to enabling end-to-end network automation and optimization. Decisions need to be executed automatically to take advantage of fast moving and short time frame issues. Without digital agents that can predict issues, issue impact and act on mitigation options to solve the problems automatically much of the value of DNNs and Analytics is lost.
Also, networks can be enormous which requires a scalable design. Our approach to scalability revolves around dynamically breaking networks up into subnets and attaching an array of digital agents to each subnet to realize near real time decision making and automation across global networks. When a problem cannot be solved on a local subnet the system enables cross subnet decision making enabling a horizontally scalable platform that adjusts to both small and massive business networks.
This design allows the system to adapt polices (forecasting, inventory, transportation, procurement, replenishment, etc.) and decisions for each subnet to accommodate local behaviors of your network actors: customers, suppliers, carriers, channels, factories, etc.
The Right Questions Can Save You from a Costly Mistake
There are few things more important than choosing a network platform that forms the foundation for integrating your systems and connecting with your trading partners. The cloud is a useful part of that, but it’s not sufficient. If you are looking for end-to-end and automation solutions for optimizing your enterprise and your business network, consideration of these key factors will be critical for success. Betting on a cobbled together best of breed “one enterprise design applications” application strategy (combined with a hub and spoke B2B platform) is a high risk and high cost strategy that is sure to disappoint.
Related: The Control Tower Tech Brief
- Gartner Supply Chain Conference: Trends 2019 - October 8, 2019
- 8 Signs Your Cloud B2B Network is Broken - April 5, 2019
- Multi-Enterprise Network Platforms vs Pseudo Networks - March 28, 2019