Amazon Web Services > Case Studies > Fuelling Conversation: How Springworks got cars talking with SPARK and created an app that’s become a standard on Swedish phones

Fuelling Conversation: How Springworks got cars talking with SPARK and created an app that’s become a standard on Swedish phones

Customer Company Size

SME

Region

Europe

Country

Sweden

Product

SPARK
AWS Lambda
AWS CloudFormation
Amazon Simple Notification Service
Amazon Simple Queue Service

Tech Stack

AWS
Amazon Redshift
Amazon Kinesis

Implementation Scale

Enterprise-wide Deployment

Impact Metrics

Productivity Improvements
Customer Satisfaction

Technology Category

Platform as a Service (PaaS) - Connectivity Platforms
Analytics & Modeling - Real Time Analytics

Applicable Industries

Automotive
Telecommunications

Applicable Functions

Logistics & Transportation
Maintenance

Use Cases

Vehicle Telematics
Fleet Management
Predictive Maintenance

Services

Cloud Planning, Design & Implementation Services
Data Science Services

About The Customer

Springworks is a company with a background in gaming. They launched SPARK, a platform that lets car owners receive key data about their vehicles at the touch of a button, served straight from the cloud, direct to their smartphones. The platform also connects them with service providers that can sort any issues that might come up – from MOTs to tyre changes. Springworks also had an ambition – 20 million talking cars in Europe by 2020. They wanted to create a system that could handle several billion data points in one go and wanted limitless scale. They also wanted to focus on innovation and needed to ensure data security.

The Challenge

Springworks launched SPARK, a platform that lets car owners receive key data about their vehicles at the touch of a button, served straight from the cloud, direct to their smartphones. The platform also connects them with service providers that can sort any issues that might come up – from MOTs to tyre changes. However, each talking car generates about 10,000 data points per day. To handle 20 million cars, Springworks needed a system that could handle several billion data points in one go. They wanted limitless scale. In order to hit the market with a great new product, Springworks needed to be able to focus on innovation. When they started out, the release cycle as about 2 weeks for a new feature – but the team wanted to move faster. Finally, data security was a major concern. For a new market offer that was looking to partner with the big mobile networks, security couldn’t be an afterthought. It had to be built into the SPARK infrastructure from the start.

The Solution

Springworks turned to AWS. They used Elastic Load Balancing and Autoscaling to manage their powerful APIs. This allowed them to scale without limits, regardless of whether they had a hundred or a million cars talking at once. The workload dropped instantly and the entire platform could be operated by a team of 30 instead of 3,000, which eliminated the need for an operations department. They used Lambda and SNS to automate responses to events. This allowed them to focus on innovation and accelerate releases by something like 300%. Instead of one feature every two weeks, they’re now shipping two features weekly. Finally, they used services like CloudTrail and EC2 to build a secure, compliance-friendly infrastructure.

Operational Impact

The entire platform can be operated by a team of 30 instead of 3,000, which eliminates the need for an operations department.
They were able to focus on innovation and accelerate releases by something like 300%. Instead of one feature every two weeks, they’re now shipping two features weekly.
They built a secure, compliance-friendly infrastructure in just a few months.

Quantitative Benefit