Microsoft Fabric for Logistics & Transportation · Powered by S.C.A.L.E.™
The logistics data warehouse, built on Microsoft Fabric for every role that moves a load
The driver on the ELD, the dispatcher at the board, the billing analyst matching 210s to 214s, the terminal manager running P&L, the safety officer reviewing CSA scores, the executive on the weekly call - they all need different slices of the same truth. Algoscale stands up a governed, role-aware carrier and 3PL data warehouse on Microsoft Fabric - with TMS, WMS, ELD, and fuel-card feeds unified under one certified model.
Works with
AWS 
Azure 
Power BI 
SAP 
Dynamics 
NetSuite 
ServiceNow 
SQL Server Why now
What breaks on the dispatch floor today
Four problems every carrier and 3PL CIO recognizes. None of them get fixed by another TMS - they get fixed by the warehouse underneath.
TMS, WMS, ELD living separate lives
Loads live in MercuryGate or McLeod. Trailer moves live in Manhattan or Blue Yonder. Hours-of-service and GPS live in Samsara or Motive. Stitching them together for a single operational view is a spreadsheet job that nobody owns.
Billing trails operations by weeks
A load finishes on Friday. The 210 goes out on Tuesday. The short-pay hits Thursday of the following week. Cash conversion, settlement deltas, and margin-per-load lag the reality of the network by a full billing cycle.
Safety data sits in the ELD vendor's portal
CSA BASIC scores, HOS violations, DOT recordable incidents - each in the vendor's dashboard. Rolling them up to corporate safety, linking them to the driver's training record, and forecasting the next audit is a manual exercise.
No single view for executive, terminal, and auditor
The CEO wants a network number. The terminal manager wants lane-level drill. The FMCSA auditor wants lineage on HOS. Today that's three reports, three definitions, and three sources of friction.
KPIs by function
The metrics each role actually asks for
One certified semantic model, six role-specific surfaces. Every metric below is defined once and reused everywhere - so 'on-time' means the same thing to the driver and the CFO.
Dispatch / Operations
OTIF (on-time-in-full) · Dock-to-dock cycle time · Loads dispatched vs. planned · Dwell time at shipper and consignee · Exception-per-load rate.
Safety & Compliance
DOT recordable incidents per million miles · HOS violations (11-hour, 14-hour, 70-hour) · CSA BASIC scores · Preventable vs non-preventable accident rate · Inspection intervention rate.
Finance
Revenue per load · Operating ratio · DSO (days sales outstanding) · Contribution margin per lane · Fuel surcharge realization · Service revenue MoM Δ - multi-leg loads spanning period-end reconciled by completion.
Fleet / Trucking
Fleet utilization · Empty miles % · Fuel cost per mile · Driver turnover (annualized) · Idle time per power unit · Trailer dwell.
Billing
Invoice cycle time (POD to 210) · Settlement delta MoM · Short-pay rate · Freight-audit accuracy · Open AR aging bucket mix · Auto-bill percentage.
Commercial (Sales + Marketing)
Pipeline coverage · Rate attainment vs bid · Customer retention by lane · New-lane win rate · Share of wallet by top-50 accounts.
One warehouse, six lenses
Mock-ups of the role-specific views
Same certified model underneath, six Power BI consumers on top. Rendered here inline as illustrations of the shape - your colors, KPIs, and thresholds on delivery.
Dispatch
- Loads today
- 1,284
- Avg dwell
- 38 min
Safety
- CSA UnsafeDrv
- 38
- Preventable rate
- 41%
Finance
- DSO (days)
- 38
- Svc rev MoM Δ
- +$412K
Fleet
- Fuel CPM
- $0.54
- Driver turnover
- 62%
Billing
- Auto-bill %
- 78%
- Audit accuracy
- 99.1%
Commercial
- Retention (YoY)
- 89%
- New-lane win
- 34%
Every system the carrier runs on
The source inventory we wire up by default
S.C.A.L.E. brings a hardened connector per category - full load on first run, incremental delta after - so the warehouse covers the whole operation, not just the loudest system.
TMS (MercuryGate / McLeod / Oracle OTM / SAP TM)
Orders, loads, stops, tenders, rates, fuel surcharges. Incremental CDC so billing and dispatch work off the same as-of timestamp.
WMS (Manhattan / Blue Yonder / SAP EWM)
Inbound receipts, outbound shipments, inventory moves, dock door assignments. Ties warehouse labor and equipment to the load that caused the move.
ELD / HOS (Samsara / Motive / Omnitracs / Geotab)
Hours-of-service status, speeding events, hard-brake events, engine fault codes, trailer GPS. Feeds both the safety rollups and the ETA prediction model.
Fuel cards (WEX / EFS / Comdata)
Fuel purchases, IFTA-ready miles-by-jurisdiction, surcharge reconciliation. Closes the loop between planned fuel cost and actual.
ERP (SAP / Dynamics / NetSuite)
GL, AR, AP, settlements with carriers and owner-operators. The finance close runs off this plus TMS billing in the same model.
EDI + IoT
Inbound 204 / 990 / 214 / 210 carrier EDI, trailer and reefer telemetry via Azure IoT Hub on OneLake shortcuts. See the Fabric shortcuts vs ADLS mounts decision matrix we use on every migration.
From the dock door to the board pack
Raw operational signals - TMS loads, ELD events, WMS moves, EDI messages - flow in through Automated Acquisition, land in a governed medallion lakehouse (Bronze/Silver/Gold), pass through a certified semantic model, and are served to six role-specific consumers. Built on Fabric's F-SKU capacity model for cost predictability - no per-query surprises on a 10M-event day. See the full capability in the S.C.A.L.E. product page.
Your enterprise source systems
Owned by you · outside SCALE
SAP ECC / S/4HANA NetSuite 
Salesforce Dynamics 365 / BC ServiceNow SQL Server / Azure SQL Structured Setup
SCALE - the prebuilt, production-ready accelerator
Cloud-Ready Core
- secure, compliant, multi-cloud foundation
AWS
Azure
Standalone Automated Acquisition
- pulls raw data from every source system above
Connectors
SuiteQL · RFC/BAPI · Bulk API · OData · pyodbc
Extraction
Chunked reads · full + incremental · watermarks
Reliability
Retries · backoff · failure alerts
State
DynamoDB · Azure Table · SQLite
Lifecycle Layering
- the data lake medallion + governed pipelines
Bronze
Raw, as landed
Silver
Cleaned, conformed
Gold
Consumption-ready
Execution Engine
- Arcastra™-powered orchestration out to every consumer
Downstream consumers
Served by SCALE · deployed where you need them
Arcastra™ AI agents
- Document Intelligence
- AnalystIQ
- Voice & Chatbot
BI & reporting
- Power BI
- Tableau
- Looker
AI / ML models
- Training data
- Fine-tuning
- RAG pipelines
Reverse ETL
- Hightouch · Fivetran
- Back to operational systems
What we deliver, concretely
Five capabilities every logistics warehouse needs
S.C.A.L.E.™ is the delivery vehicle under every engagement - the five capabilities that separate a Fabric warehouse that ships from one that stays in diligence. Each card is a capability we build in by default.
S - Structured Setup
Prebuilt, production-ready lakehouse
C - Cloud-Ready Core
Multi-cloud, secure, compliant
A - Automated Acquisition
Prebuilt connectors, instant ingestion
L - Lifecycle Layering
Medallion pipelines, governed flow
E - Execution Engine
Arcastra™-powered orchestration
Why it matters
RBAC by persona
Access wired to the network, not the IT backlog
Five personas, five access scopes. Implemented via Fabric workspace roles, Power BI RLS, Purview sensitivity labels, and Microsoft Entra groups mapped to the org hierarchy - so a new hire at a new terminal inherits the right view on day one.
Driver
Mobile-first. Own loads, HOS status, next stop ETA, messages from dispatch. No lane margin or other drivers' data. PII-safe.
Dock Supervisor
Today's inbound and outbound at the dock, trailer pool, equipment availability, shift labor. Facility-scoped. No cross-network drill.
Dispatcher
Region-scoped. Active loads, driver assignments, lane-level utilization, customer exceptions. No financial drill beyond revenue-per-load.
Terminal / Regional Manager
Terminal P&L, driver turnover, safety rollups for the region, customer scorecards. Cross-dispatcher comparisons. No cross-region financial drill.
Executive
Network-wide directional dashboards - dollar-denominated, safety and DSO rollups, regulatory posture. No raw signals, no PII.
Findability
Metadata that makes the warehouse discoverable
A data warehouse nobody can find is a data warehouse nobody trusts. Purview and Fabric's catalog do the heavy lifting so dispatchers, analysts, and auditors stop asking the same question twice.
Certified datasets
OTIF, operating ratio, CSA scores, DSO - each metric is defined once in the certified semantic model. Every report, every Copilot prompt, every integration reads from the same definition.
Auto-generated lineage
TMS load field → Bronze → Silver → Gold mart → Power BI visual, rendered as a Purview lineage graph. When an FMCSA auditor asks where a number came from, you show them instead of guess.
Business glossary + Copilot
Fabric Copilot is constrained to certified models only - chat-with-your-data is safe by construction, not by hoping the prompt doesn't pull from a rogue Excel extract.
Compliance, enforced at the infrastructure layer
DOT / FMCSA / CSA audit posture (HOS and recordable-incident lineage), IFTA (fuel tax by jurisdiction), C-TPAT (customs security), ISO 28000 (supply-chain security), PCI-DSS (customer-portal billing), and GDPR (driver and customer PII). Controls are written into the Terraform that stands the Fabric capacity up - encryption, access boundaries, audit logging, and resource tagging are pipeline output, not documentation. Pairs with Algoscale's data governance consulting and data integration consulting practices - the warehouse is the spine they both run on.
Bring your stack
Book a Fabric × logistics walkthrough
45 minutes, your TMS and ELD vendor, your settlement pain. We'll map the warehouse shape and show you what S.C.A.L.E. ships against it.
Keep exploring
More from the data journey
The data journey, from report to agent
A maturity-model view of how enterprises move from scattered reports to AI-native operations — and the specific work required at each stage.
Read moreThe enterprise data warehouse, built by people who ship them
Algoscale builds enterprise data warehouses that ship - on AWS, Azure, or Fabric - with governance, real numbers, and production ownership in weeks.
Read moreAzure + AWS, without the tax
Six real challenges of running Azure and AWS side by side — and a four-step playbook to stop bleeding cost, latency, and engineering time.
Read morePrefer the long form? Reach out directly.
Bring your TMS, your ELD vendor, and your settlement pain. We'll map the warehouse shape and show you what S.C.A.L.E. ships against it on Fabric.