The document discusses RIO, a logistics platform that digitizes the logistics supply chain. Key points:
- RIO's vision is to make the transport and logistics ecosystem more transparent across manufacturers.
- The RIO platform connects over 4,500 vehicles and 80,000 participants across 27 countries.
- The architecture utilizes AWS services like Kafka, MQTT brokers, and microservices across multiple accounts to integrate vehicle data and provide features like fleet monitoring and performance analysis.
4. RIO'S VISION
RIO's vision is to make the
complete transport and
logistics ecosystem more
transparent – across all
manufacturers, and open to
all. The centralizing platform
creates the foundations for a
wide range of new business
and service models.
5. Digitization
of trucks with
the RIO Box
RIO DIGITIZES THE
LOGISTICS SUPPLY CHAIN.
Integration
of producer
platforms
System connection of
the receivers
TMS connection
of logistics service
providers
6. Fleet customers
registered at
RIO Platform
MORE THAN
4,500Vehicles
equipped with
RIO Box
MORE THAN
80,00027Participating
countries
OUR CUSTOMERS
ON THE RIO PLATFORM.
With RIO since end of 2017
Formerly known as Volkswagen Truck & Bus
Line-fitment in MAN trucks started August 2017
Platform launched December 2017
Third connectivity for device signing is not shown.
It is the only part that is actually on premise, using a hardware HSM.
Embedded SIM
Cloud only connectivity without intermediates
Microservices architecture with local persistence requires a different approach for cross service data use cases, then with a shared database.
Data Hub uses optimized format for querying:
Zipped, flattened, partitioned by time and stored in Parquet format
Massage and filter data for specific use cases
Microservices size and boundaries discussion lead to thinking model bounded context, which comes from domain-driven design. The technical implementation and size is not the focus anymore. Especially when heading towards serverless. So what is a bounded context...
Context accounts
Not everything within a bounded context is an AWS service.
Account provisioning is almost completely self-service.
Bitbucket
Account bootstrapping.
Convention based pipeline definition in repo.
Infrastructure as code used to create supporting resources in the account
Showing a Fargate based deployable unit,
Serverless blueprints are also available.
Autonomy is one of the ingredients in microservices architecture
Map based information hub for the dispatcher at a transport service provider
Configuration: Adjust sample rate 1 minute with 3 data points vs. 15 minutes.
Analyses and rates the performance on an asset and driver level.
Like foresighted driving, coasting, harsh breaking, speed, fuel consumption
Configurable data displays
Fleet performance data from the last three months
Simplified: Left out Fleetadmin and driver info service.
Configuration changes include how signals are aggregated on the box: Thresholds, sampling rate and median
RIO Compliant is a service for fleet managers who needs to download and oversee data from digital tachographs and driver cards.
AWS improved tooling support to simplify managing multiple accounts. Most prominently with Organizations, Landing Zone, Control Tower
Started with a single, shared production account and move to multiple context accounts.
Separation
Easy and transparent cost allocation
Organize and categorize accounts by security, function and structure
Ownership, Autonomy
Aligned with bounded context
Enforcing the architecture with explicit boundary
Freedom and responsibility within an account
Clearly defined public interfaces, APIs, Events (incl. Kafka)
Faster development cycles due to fewer dependencies
Allows organizational scaling due to less centralization
https://unsplash.com/photos/rk_Zz3b7G2Y
Photo by Samuel Zeller on Unsplash