01
OTIF for key customers
One agreed OTIF definition with order-line detail behind it.
Transportation / Logistics Analytics
Transportation and logistics analytics with one number per KPI
Operations, finance and customer teams each report on-time delivery and cost per shipment, and no two numbers match. Agnotic Technologies builds the data layer under your logistics and supply chain dashboards: each KPI defined once, traced to its source event in the TMS, WMS, ELD or carrier EDI feed, and owned by a named team.
One definition
Per KPI, versioned
X12 214 and 856
Carrier and ship events
Named owner
For every metric
Trusted by global innovators
Industry Overview
What is transportation and logistics analytics?
Transportation and logistics analytics is the data layer that turns shipment, warehouse, carrier and driver events into agreed measures such as on-time in full, dwell time and cost per shipment. Agnotic Technologies builds it so each KPI has one written formula, one source event and one owner, and every dashboard reads the same number.
Industry Challenges
Why do logistics teams disagree on the same KPI?
The data is usually there. The definitions are not.
On-time is measured against the requested date in one report and the promised date in another, and both are called OTIF.
Delivery time comes from the carrier's X12 214 status in one system and from the proof of delivery scan in another, hours apart.
Dwell is calculated from gate check-in in the yard system but from the arrival status in the TMS, so detention claims and reports disagree.
Cost per shipment uses the rate quote, not the paid invoice, until accessorials arrive weeks later.
Fill rate is calculated by order line in the warehouse and by unit in sales.
ELD location points recorded during authorized personal use are mixed into empty mile calculations.
KPI definitions
How should each logistics KPI be defined?
The definition table we agree with your operations, finance and customer teams before building any dashboard. Wording and thresholds are yours; one formula, one source event and one owner per KPI is the rule.
| KPI | Formula in words | Source event | Owner |
|---|---|---|---|
| On-time in full (OTIF) | Orders delivered complete by the agreed date, divided by all orders due in the period | Delivery status from X12 214 or proof of delivery, matched to order lines and the agreed date | Customer operations |
| Carrier on-time pickup | Loads picked up inside the appointment window, divided by all loads tendered to that carrier | Pickup status in X12 214 against the appointment in the X12 204 load tender | Transportation |
| Carrier on-time delivery | Loads delivered inside the appointment window, divided by all loads that carrier delivered | Delivery status in X12 214 against the delivery appointment | Transportation |
| Dwell time | Time from arrival at a facility to departure, per stop | Arrival and departure statuses, or yard gate check-in and check-out | Facility or yard manager |
| Cost per shipment | Total paid freight charges, including accessorials, divided by shipments in the period | Paid carrier invoices (X12 210) joined to shipments | Finance |
| Order fill rate | Units shipped divided by units ordered, for orders shipped in the period | WMS ship confirm and the X12 856 ship notice, against the order | Warehouse operations |
| Empty miles | Miles driven with no load, divided by total miles, per tractor | ELD vehicle miles and duty status, joined to dispatched loads | Fleet operations |
Our Approach
How should you build logistics analytics every team trusts?
Three rules carry most of the weight. The tools matter less than these.
Define the KPI before the chart
Each measure gets a written formula, a source event, a time basis and an owner who approves changes. The definition is stored with the data, not in a slide deck.
Keep event time and received time apart
Carrier status messages arrive late and out of order. We store when an event happened and when it arrived, so a late 214 corrects the record instead of being lost.
Join on shipment identity once
Orders, loads, shipments and invoices carry different references. One shipment key mapping means every KPI joins the same way.
Capabilities
What do we build for transportation and logistics analytics?
How to build transportation and logistics analytics in layers, from raw events to governed measures. Dashboards sit on top and are a separate, smaller piece of work.
Event ingestion
X12 204, 210, 214 and 856 from carriers and partners, TMS and WMS exports, ELD data and EPCIS events where partners publish them.
Shipment identity mapping
Orders, loads, stops, shipments and invoices linked by one key, with unmatched records shown rather than dropped.
KPI definition catalog
Every KPI with its formula, source events, time basis, owner and version history, readable by people and by BI tools.
Late and corrected events
Late statuses and corrected invoices recalculate the KPIs they touch, with the earlier value kept.
Exception views
Shipments missing a delivery status, invoices with no matching shipment and ship notices that disagree with the ship confirm.
Carrier scorecard data
On-time pickup and delivery by carrier and lane, from the same definitions finance and transportation use.
SCM analytics measures
Supplier on-time delivery and inventory measures defined in the same catalog, for teams that need SCM analytics beyond transportation.
Lineage and access
Each number links back to the events behind it, and access follows customer, region and business unit.
Engineering Stack
Which systems and standards feed the KPIs?
The sources we connect most often. Each one is added only when a KPI needs it.
Carrier and partner EDI
X12 204 load tenderX12 210 freight invoiceX12 214 shipment statusX12 856 ship notice
Operations systems
TMSWMS ship confirm and inventoryYard management and gate eventsERP orders and invoices
Fleet
ELD records under 49 CFR Part 395Telematics location and engine dataDispatch and load assignment
Data platform
GS1 EPCIS 2.0 eventsWarehouse or lakehouse on AWS, Microsoft Azure or Google CloudSemantic layer for KPI definitionsBI tools for dashboards
Measured Impact
How do you know the analytics layer is working?
Measures of the data layer itself, reviewed with each KPI owner.
Definition coverage
KPIs with a written definition
Every published KPI has a formula, source and owner.
Event completeness
Shipments with all statuses
Shipments that have every status a KPI needs.
Reconciliation
Agrees with the owner's report
Differences explained before a KPI is published.
Freshness
Event to KPI
How long a new event takes to reach the numbers.
Use Cases
Where do logistics teams start?
First releases built around the KPIs that cause the most argument.
02
Carrier scorecards
On-time pickup and delivery by carrier and lane.
03
Detention and dwell
Dwell by facility from yard and carrier events.
04
Freight cost per shipment
Paid invoices, accessorials included, joined to shipments.
05
Fill rate across warehouses
One unit-based fill rate for every site.
06
Empty miles for a private fleet
ELD miles joined to dispatched loads.
Integrations
Which systems does logistics analytics connect to?
The systems the KPI layer reads from.
Loads and tenders
TMS
Ship confirms and inventory
WMS
Gate events
Yard management
X12 EDI
Carriers and partners
Fleet data
ELD and telematics
Orders and invoices
ERP
Partner events
EPCIS repositories
Dashboards
BI tools
What we check
Is a logistics KPI ready to publish?
The checks we run on each KPI before it appears on any dashboard.
Definition
- Formula written in words and in code
- Time basis stated: event date, ship date or delivery date
- Inclusions and exclusions listed, such as cancelled orders and customer pickups
Source
- Source event named for every input
- Late and corrected events handled
- Shipment identity joins tested on real data
Ownership
- Owner named and change approvals recorded
- Earlier definition versions kept
- Reconciled once against a report the owner already trusts
Compliance-First Development Services Backed by Global Standards
We build secure, scalable products designed for privacy, interoperability, and regulatory readiness from day one across every sector we serve.
General Data Protection Regulation
Implement lawful consent flows, data minimization, and secure processing for global data privacy.
Information Security Management
Adhering to the international gold standard for managing information security risks.
Our Edge
Why Global Leaders Choose Us
We combine deep technical expertise with industry-specific knowledge to deliver solutions that aren't just functional, but transformational.
Enterprise-Grade Security
We implement rigorous security protocols and compliance standards (HIPAA, GDPR, SOC2) across all industrial solutions to protect sensitive data.
High-Performance Scaling
Our architectures are built to handle massive data loads and user bases, keeping performance steady whether you're serving ten or ten million.
Accelerated Time-to-Market
Using our suite of internal tools and proven frameworks, we cut setup work so your first release reaches users sooner.
Embedded AI Integration
Beyond simple wrappers, we build deep-learning integrations and predictive analytics directly into the core of your industry-specific workflows.
Engagement Model
How does a logistics analytics engagement run?
Transportation and logistics analytics services from Agnotic start with definitions. It depends on scope; we agree a fixed first release on the scoping call.
01
Scoping call
We list the KPIs in dispute, the systems behind them and who owns each number.
02
Definition workshop
Operations, finance and customer teams agree each formula, source event and owner in the KPI definition table.
03
Fixed-scope first release
Ingestion and governed definitions for a first set of KPIs, reconciled against a report the owner trusts.
04
Extend
More KPIs, partners and SCM analytics measures on the same layer.
05
Support
New partners, definition changes and data quality monitoring under agreed change control.
Facts and sources
Standards behind logistics events
The event standards and rules our KPI definitions rely on.
The X12 214 Transportation Carrier Shipment Status Message lets a carrier give shippers, consignees and their agents the status of shipments in terms of dates, times, locations, route, identifying numbers and conveyance.
Source: X12, Transaction Sets (214)The X12 856 Ship Notice/Manifest lists the contents of a shipment with order information, product description, packaging, carrier information and the configuration of goods within the transportation equipment.
Source: X12, Transaction Sets (856)An electronic logging device automatically records the date, time, vehicle location, engine hours, vehicle miles and the driver, vehicle and motor carrier identification at each change of duty status.
Source: 49 CFR 395.26(b) and (c) (eCFR)When a driver indicates authorized personal use of a commercial motor vehicle, the ELD logs location with a single decimal point resolution, approximately within a 10-mile radius.
Source: 49 CFR 395.26(i) (eCFR)GS1 EPCIS is a data sharing standard for supply chain visibility that captures the what, when, where, why and how of products and assets, and EPCIS 2.0 adds a REST API for capturing and querying event data.
Source: GS1, EPCIS and CBV
Voice of success
We don't just build products; we forge lasting partnerships. See how we've helped industry leaders transform their vision into technical reality.
“I can clearly see how Agnotic has a unique way of handling end-to-end development. They are always active on quick chat and provide support quickly.”
Aaron Phelan
Founder, Benchmark
“Agnotic combines deep technical expertise with strong domain knowledge. They understand the business context, anticipate challenges, and make collaboration smooth and effective.”
John Pasmore
Founder, Latimer
“Agnotic is the best technical team we evaluated. Their engineering excellence made our work dramatically easier and allowed us to stay focused on what matters most for maternal care outcomes. They took full ownership of the technical execution, and we are always happy to continue working together.”
Kim Smith
Founder, My Lauren
Related pages
Related logistics software
This page covers the KPI and data layer. These pages cover the systems that run operations and the dashboards on top.
Transportation management system
Planning, carrier management, execution and freight audit.
Supply chain visibility software
Real-time shipment, supplier and inventory visibility across the chain.
Freight management software
Freight planning, rates, documentation and billing for shippers.
Fleet management software
Vehicle, driver and maintenance management for owned fleets.
Fleet telematics platform
GPS, vehicle data and ELD support for connected fleets.
Dashboard development
Power BI, Tableau and custom dashboards built on a governed data layer.
More in Transportation
More Transportation Solutions
Explore other production-grade engineering platforms we deliver across transportation.
Frequently Asked Questions
A TMS reports on the freight it plans and executes. Transportation and logistics analytics joins TMS data with warehouse, carrier EDI, ELD and ERP data, applies one definition per KPI and serves every team's dashboard from that single layer.
Most programs start with TMS loads, WMS ship confirms, carrier X12 214 status messages and freight invoices. ELD and telematics data, X12 856 ship notices, yard events and EPCIS events are added when a KPI needs them.
We store the time an event happened and the time it arrived, keep corrections as new versions and recalculate the KPIs they affect. Shipments missing a required status appear in an exception view instead of silently counting as late or on time.
It uses the same data layer. SCM analytics adds supplier on-time delivery, inventory and order measures across the supply chain, defined in the same catalog with the same rule of one formula, one source and one owner.
We can, but dashboards are the smaller part. Once the KPI layer exists, dashboards in Power BI, Tableau or a custom app read from it, and our dashboard development team builds those screens.
The number of source systems and trading partners, EDI volume and quality, the KPIs in scope, how much history must be loaded, and access rules by customer or region. We explain these drivers on the scoping call instead of quoting a fixed price.
It depends on scope; we agree a fixed first release on the scoping call. A common first release covers OTIF and carrier on-time performance for one business unit, reconciled against a report the owner already uses.
Yes. Startups and smaller 3PLs often begin with three or four KPIs from their TMS and carrier feeds, defined properly from the start, which is easier than untangling conflicting reports later.
Industries