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
Planning evidence
Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.
Planning decision controls
GAINS automation thresholds need decision-class approval
GAINS says heuristics can identify higher-risk supply-chain decisions for human intervention and set thresholds for lower-risk automation. Buyers should approve those thresholds by decision class, object, horizon, and exception consequence before an automated recommendation becomes an operating action.
Process-manufacturing planning
Arkieva batch plans need yield-and-sequence acceptance
Arkieva positions its planning software for process manufacturers facing batch operations, limited capacity, yield variability, and sequencing constraints. A plant should test whether a proposed batch plan still meets material, capacity, quality, and sequence conditions before a named operator accepts it for execution.
Connected Planning
Anaplan connected plans need a measure-and-calendar contract
Anaplan's current supply-chain page connects demand, supply, production, sourcing, long-range, sales-and-operations, and financial planning. Connection does not make similarly named measures equivalent. Each promoted plan needs shared definitions for grain, unit, calendar, scenario, version, ownership, and reconciliation before teams act across functions.
Planning Data Governance
Oracle planning data alerts need resolution evidence
Oracle says its Supply Chain Planning AI Advisor summarizes important data-quality issues so planners can resolve problems with less effort. The summary is triage, not repair. Each issue needs source-field lineage, affected plan and decision scope, severity, owner, correction authority, replay, reconciliation, and proof that downstream recommendations were refreshed.
Logistics cost evidence
A Decklar detention prediction is not an approved carrier charge
Roambee's registered address now presents Decklar and positions detention-and-demurrage reduction around real-time prediction. A predicted cost remains separate from the contract, free-time calculation, carrier invoice, dispute, approval, and settlement records.
Planning evidence
Separate NOAA observations, forecasts, and scenarios by horizon
NOAA's Climate page connects readers to distinct data, reporting, drought, heat, research, and preparedness resources. Supply teams need to label the evidence class, issue time, valid period, update cadence, uncertainty, and decision horizon before any signal enters an operating, tactical, or strategic plan.
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.
Delivery evidence
A FarEye delivery milestone does not prove consignee receipt
FarEye documents multimode shipment tracking, estimated delivery dates, alerts, and control-tower visibility. A displayed delivery milestone is still an observation that must be reconciled to the order, carrier event, location, consignee, proof record, exception, and inventory or customer outcome.
Demand planning
An Atlas ensemble forecast needs model-selection and version evidence
John Galt Solutions says Atlas can explain why patterns, trends, and models were selected for an ensemble forecast. That explanation can help planners review an output, but a governed forecast still needs the exact data cutoff, candidate models, selection logic, version, horizon, hierarchy, overrides, and later error record.
Supplier risk
An Interos iScore needs its factor, entity, and observation date
Interos says iScore evaluates extended supply chains across multiple risk factors. A composite score still needs a reconstructable entity, factor, source, model, time, and decision record.
Cargo risk
An Overhaul route alert does not establish cargo tampering
Overhaul documents shipment visibility, route-deviation alerts, cargo-risk intelligence, and response. An alert still needs telemetry, custody, investigation, and product-disposition evidence.
Demand planning
A ToolsGroup forecast override needs its own demand record
ToolsGroup documents probabilistic forecasting and demand sensing. A planner override still needs its baseline, event, horizon, owner, expiry, approval, and downstream plan impact.
Ocean visibility
A Vizion container event does not establish cargo availability
Vizion documents an API for normalized ocean-container tracking events and trade data. Those events can improve shipment observation, but a carrier milestone alone does not establish that cargo is released, accessible, cleared, paid, and ready for pickup at a named terminal.
Integrated planning
An o9 scenario comparison is not an approved operating plan
o9 documents an integrated business-planning platform that lets teams compare alternative futures and evaluate demand, sourcing, capacity, cost, and margin before committing. The comparison informs a decision; it does not identify which scenario leaders approved, when it became effective, or which execution systems received it.
Supplier disruption
A Resilinc event alert does not establish supplier impact
Resilinc documents supplier mapping, event monitoring, impact assessment, response, and continuity workflows. An alert becomes decision-grade only after the business resolves the affected facility, product, dependency, time horizon, operating exposure, and accountable response owner.
Order promising
A Blue Yonder order promise needs an inventory-and-capacity evidence snapshot
Blue Yonder presents order promising within a broader supply-chain planning portfolio. A promise becomes reviewable only when the organization can reconstruct the inventory, capacity, allocation, lead-time, policy, and exception evidence used at the moment it was made.
Cargo condition
A Tive condition alert is not a cargo-disposition decision
Tive documents shipment location and condition monitoring with alerts for events such as temperature, light, shock, delay, and route exceptions. An alert can accelerate attention, but it does not decide whether goods remain usable, should be quarantined, must be rejected, can be released, or require a claim.
Planning systems
An SAP IBP supply plan is not a supplier commitment
SAP presents IBP as a connected planning environment for demand, response and supply, inventory, replenishment, and S&OP. A feasible plan remains an internal decision model until source data, capacity, commercial terms, supplier acknowledgement, execution systems, and exception ownership support the quantity and date.
Traceability
Altana's network map does not establish product origin
Altana presents Atlas as an AI-supported map of global supply networks built from public and licensed trade and entity data. That network view can direct due diligence, but origin still requires product-level evidence, applicable rules, and an accountable conclusion.
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.
Network strategy
UNCTAD’s maritime review is a planning baseline—not a shipment forecast
UNCTAD’s annual Review of Maritime Transport documents structural and cyclical conditions across seaborne trade, fleets, freight markets, ports, and regulation. It is a dated research baseline for network decisions, not a live prediction of a shipment’s arrival, rate, capacity, or disruption exposure.
Supply-chain risk
CISA ICT supply-chain guidance needs acquisition evidence—not a supplier score
CISA’s small-business fact sheet frames ICT supply-chain risk as work across products, services, suppliers, and acquisition. A questionnaire score cannot establish the risk, integrity, availability, or suitability of a particular technology supply chain.
Planning
Planning suites converge on scenarios—but not on one decision model
Kinaxis, Blue Yonder, o9, SAP, and Oracle all document scenario and planning capabilities, while horizons, data models, constraints, and decision rights remain buyer-specific.