Freight visibility evidence
MacroPoint ELD+ needs a dual-signal conflict record
MacroPoint says ELD+ compares telematics and mobile signals in one tracking session. Buyers need conflict lineage before either signal drives an operating decision.
Coverage desk
Product Intelligence
Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.
Supplier change control
SupplyOn change requests need a first-affected-lot boundary
SupplyOn documents a supplier-initiated PCN and ECN workflow that spans review and implementation follow-through. The operating decision is to identify the first product, lot, site, order, and shipment to which an approved change actually applies.
Carrier and driver governance
MacroPoint tracking needs a driver notice-and-consent record
Descartes' MacroPoint product schedule says tracked freight can reveal a driver's location and assigns customers responsibility for notice and any legally required consent, including for certain text messages. Activation therefore needs a person-level purpose, notice, consent, access, and withdrawal record separate from the shipment record.
Supplier quality evidence
An Elemica eCoA needs batch, specification, issuer, and receipt lineage
Elemica lists electronic certificates of analysis within a network that carries orders, shipments, invoices, and quality documents among trading partners. A received eCoA still has to resolve to the supplied lot, approved specification, authorized laboratory or issuer, exact document version, buyer receipt, exception decision, and material disposition.
Multi-tier dependency evidence
A Prewave sub-tier link needs product and site evidence
Prewave presents multi-tier supply-chain mapping and risk intelligence. A usable dependency record still has to connect the named legal entities, supplying sites, part or material, product or program, relationship basis, observation date, confidence, exception, and accountable validation.
Disruption intelligence
UN OCHA ReliefWeb records disasters—not supplier exposure
ReliefWeb organizes humanitarian reports and disaster context by source, geography, date, format, and related event. Those records can flag where an operating review should begin, but they do not identify a buyer’s supplier, facility, lane, inventory, or service impact.
Product Intelligence
project44's current record shows the boundary between events and decisions
Movement connects transportation events and prediction to operating workflows, but official product language does not establish network completeness or ETA performance.
Product Intelligence
FourKites broadens the control-tower decision beyond transportation tracking
The current platform record spans transportation, orders, inventory, facilities, yards, and workflow, expanding both the opportunity and the integration burden.