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
Quantitative Benefit
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
Related Case Studies.
Case Study
Integral Plant Maintenance
Mercedes-Benz and his partner GAZ chose Siemens to be its maintenance partner at a new engine plant in Yaroslavl, Russia. The new plant offers a capacity to manufacture diesel engines for the Russian market, for locally produced Sprinter Classic. In addition to engines for the local market, the Yaroslavl plant will also produce spare parts. Mercedes-Benz Russia and his partner needed a service partner in order to ensure the operation of these lines in a maintenance partnership arrangement. The challenges included coordinating the entire maintenance management operation, in particular inspections, corrective and predictive maintenance activities, and the optimizing spare parts management. Siemens developed a customized maintenance solution that includes all electronic and mechanical maintenance activities (Integral Plant Maintenance).
Case Study
Monitoring of Pressure Pumps in Automotive Industry
A large German/American producer of auto parts uses high-pressure pumps to deburr machined parts as a part of its production and quality check process. They decided to monitor these pumps to make sure they work properly and that they can see any indications leading to a potential failure before it affects their process.