Consider a shipment with three arrival dates. The supplier has one, the carrier has another, and the customer is still looking at yesterday’s spreadsheet. Nothing has necessarily gone wrong with the goods. The trouble is that the people responsible for them are working inside different versions of events. One Network Enterprises built its business in that space between organizations. In August 2024, Blue Yonder bought it at an enterprise value of approximately $839 million.
- Shared supply chain data, from suppliers to delivery partners.
- Planning and execution connected on a cloud network.
- Customers include ALDI’s Asian buying hub, HPE, and Dana.
- Acquired by Blue Yonder in 2024; its network continues within that business.
A plan that crosses company lines
Greg Brady founded One Network in 2002 after holding senior roles at i2 Technologies and Oracle. Co-founder Ranjit Notani became its chief technology officer. Their subject was familiar enterprise territory: orders, inventory, transportation, demand. The architectural choice was to organize those activities around a network of trading partners, extending coordination beyond the boundaries of any individual company.
The resulting Real Time Value Network and Digital Supply Chain Network let participants share a common operational picture. The product family combines control towers, planning, logistics execution, and tools for building multi-party applications. A control tower, in this context, means a place to detect trouble and coordinate a response. A late delivery matters because of what depends on it: a production run, a replenishment order, a promise to a customer.
Blue Yonder’s acquisition announcement put the network at more than 150,000 trading partners. That describes participants, rather than a disclosed population of paying customers. Still, the distinction helps explain the purchase. Blue Yonder was buying technology and connections that could extend its planning and execution business into the businesses surrounding each customer.
The ocean freight test
Ocean freight makes the proposition tangible. In January 2024, ALDI International Buying Asia announced it was live on One Network’s Intelligent Control Tower. The Hong Kong operation sources products from Asia and manages ALDI’s global ocean freight logistics. Its stated aims included centralizing shipping volumes, improving cost transparency, and gaining more control over the movement of goods.
The mechanism matters more than the vocabulary. Bringing suppliers and logistics partners around a common data model allows purchasing decisions and shipment decisions to inform one another. ALDI’s announcement described reducing freight, handling, storage, and manual work as objectives. It did not publish an audited savings figure. The useful lesson is the choice of problem: coordinate a defined flow of goods before treating visibility as an end in itself.
Dana offers an older, more operational example. In a 2016 release, the automotive supplier described using One Network for inbound supply and intercontinental freight. It gained access to inventory at third-party warehouses that had previously been unavailable. Dana’s logistics director said adjustments that once took weeks could typically happen within a business day. These were customer statements in a vendor release, rather than an independent benchmark.
When 100 systems meet one patient
Ghana’s health logistics project reveals the same problem with different stakes. In an August 2021 account, the Ministry of Health’s IT head, Samuel Ampomah, described an initial evaluation that uncovered more than 100 systems. Data lacked portability and standardization. The obstacle arrived before any sophisticated prediction: people could not readily combine what their systems knew.
“We realized we had over 100 different systems.”
Samuel Ampomah · Ghana Ministry of Health · 2021
GhiLMIS, built on One Network’s NEO platform and implemented with S4D Consulting, connected more than 1,500 medical facilities, according to that account. The Global Fund financed the project. It supported tracking, planning, and prioritizing COVID-19 supplies. Here the scarce resource was partly a shared view of where supplies were needed. Standardization gave the network something usable to distribute.
Give the assistant something to do
In February 2024, One Network launched the beta of NEO Assistant. Its advertised capabilities included conversational queries, maps and inventory views inside the conversation, and adaptive guidance through decisions. The distinctive claim concerned executable recommendations, called Smart Prescriptions. In a semi-autonomous configuration, a person could review a proposed action before approving it.
That makes the assistant’s usefulness depend on the system underneath it. Knowing that a shipment is late is one task. Understanding affected orders, available inventory, and permitted responses requires connected operational information. One Network described the assistant as inheriting the network’s multi-party permissions. The sensible reading is a product design with human controls, rather than evidence that an entire supply chain can safely run unattended.
Its partnerships show how much specialist work lives behind that proposition. In 2023, Optessa and One Network announced an integration connecting manufacturing schedules with material and logistics plans. A factory sequence has consequences for suppliers; a missing component has consequences for that sequence. The partnership sought to connect those calculations. Bluecrux, meanwhile, brought consulting and digital twin expertise to a separate collaboration. Network software still needs people who understand the processes being represented.
The handoff is the product
One Network sold enterprise cloud software as SaaS and PaaS, supported by integration and implementation work. Its expertise also extended to defense logistics: the NEO Defense Enterprise Solution announced in January 2024 covered military supplies, transportation, and maintenance. Comparable collaboration networks include SAP Business Network and e2open. One Network’s pitch emphasized combining a shared data model with planning and executable workflows.
For a prospective buyer, the practical question is participation. Which suppliers and carriers will connect? Who owns each data field? Who can authorize the response? These are implications of the architecture: stale inputs or missing partners constrain any shared picture. A business with simple internal logistics may have less reason to take on that coordination work.
The idea worth copying is modest. Pick one recurring delay. Follow its information across every handoff. Agree on identifiers, responsibilities, and the decision that follows an alert. Measure whether that decision happens sooner. For example, a useful trial could track how quickly a revised arrival time reaches a production planner and triggers an approved response. Counting alerts alone would miss the point. The work ends when the right people can act on the same update. One Network’s story makes a useful case for examining the distance between knowing something and getting several organizations to do something about it.