VeUP
← All case studies
Machine Learning · Connected-vehicle IoT analytics
Sibros wordmark

Sibros: a 75-billion-point/day SageMaker model + Bedrock AgentCore pipeline

Agentic workflowsModel evaluationServerless analytics on S3AI-native deliveryDay-2 runbooks & team enablement
400,000
vehicles forecast across — a line of business that did not exist before
75B
data points a day in production
74%
prediction accuracy against a >70% contractual target
Amazon SageMakerAmazon S3Amazon AthenaAmazon CloudWatch

Sibros’s connected-vehicle platform senses at extraordinary scale: fleets from roughly 20,000 to 400,000 vehicles emitting on the order of 75 billion telemetry points every day, governed by customer-defined logging rules. VeUP built the analyze layer of that IoT loop — a production pipeline that forecasts how much telemetry a given logging configuration will generate — so the platform’s act layer, OTA decisioning and cost planning, runs on predictions instead of surprises.

The challenge

In a connected-vehicle platform, the logging rule is the throttle on everything downstream: each customer-defined rule determines how much telemetry every vehicle emits, and therefore what the platform’s cloud bill — and its customers’ bills — will be. At 75 billion points a day across fleets of hundreds of thousands of vehicles, misjudging a rule’s data volume is an expensive mistake discovered weeks later on an invoice. Sibros needed the IoT loop closed: a way to predict, at configuration time, what a logging rule would cost in data before a single vehicle started emitting under it.

The solution

VeUP built a production predictive-analytics pipeline over the platform’s telemetry lake. The fleet’s emitted telemetry lands in Amazon S3 under the Apache Iceberg table format with Amazon Athena as the query layer; Amazon SageMaker trains telemetry-volume-forecasting models over it — deliberately simple algorithms (XGBoost, Random Forest, regression), honoring the customer’s frugality constraint at this data scale — and serves them through a SageMaker endpoint behind a REST API the platform calls at logging-configuration time. Validation discipline matched the fleet structure: strict GroupKFold cross-validation by logging rule, so the model is scored on rules it has never seen, the way production will actually use it. The pipeline was delivered against a contractual accuracy bar, extended in a second engagement that materially improved generalization, and transferred to Sibros’s engineering team, who operate it independently.

Production outcomes

KPIResult
Forecast accuracy74% prediction accuracy against a >70% contractual bar for telemetry-volume forecasting on the live 75-billion-points/day workload.
Generalizationv2 dataset and strict GroupKFold-by-rule validation lifted R² from 54% to above 80% — accuracy that holds on logging configurations the model has never seen.
IoT loop closedVehicles sense per logging rule; the cloud analyzes and forecasts volume per configuration; the platform acts — OTA decisioning and cost planning informed before data is emitted, with the customer’s team operating the pipeline independently.
Lessons & continuationAt fleet scale, telemetry configuration is a cost-control surface — predict it, don’t discover it; validation structure must mirror deployment structure (score on unseen rules), and simple models over a well-built lake beat complex models over a weak one.
AWS services in production
Amazon SageMaker (training + endpoint)Amazon S3 (Apache Iceberg telemetry lake)Amazon AthenaAWS GlueAWS IAMAmazon CloudWatch