| Client | E-Taşıt |
|---|---|
| Sector | Industry and manufacturing |
| Scope | End-to-end digital ecosystem: mobile app, VT360 smart fault detection, service, supplier and admin panels, integration infrastructure |
| Technologies | OBD vehicle data, integration infrastructure |
About the Project
For E-Taşıt we developed the entire digital ecosystem end to end, from the mobile app to VT360 smart fault detection, and from the service, supplier and admin panels to the integration infrastructure. This project is not a single app but an ecosystem made up of several connected components. Data coming from the vehicle flows within the same structure from the mobile app in the user’s pocket to the service and supplier screens, and from there to the admin panel. In software that talks to hardware, this integrity is the real challenge of the project.
The Need and the Problem Solved
The need was to gather vehicle data on a single platform, from diagnosis to service, and to share it with business partners. Information about vehicle health is generated in the vehicle, but those who act on it are the service centres and suppliers. Without a shared platform between these parties, data stays fragmented and diagnosis and service drift apart. The points to solve were:
- Collecting and interpreting vehicle data without interruption
- Making fault detection understandable for the user and the service centre
- Connecting service and supplier processes to the same data
- Monitoring the whole ecosystem from a single admin panel
Our Solution
The components that make up the ecosystem:
- Mobile app: the mobile interface of the ecosystem.
- VT360 smart fault detection: the fault detection layer that works on OBD vehicle data.
- Service and supplier panels: the screens where business partners run their processes based on vehicle health data.
- Admin panel: the centre from which the ecosystem as a whole is monitored and managed.
- Integration infrastructure: the layer that connects all these components.
In ecosystems of this kind, each component serves a different user group: the service panel is for service centres, the supplier panel for suppliers and the admin panel for the team that manages the ecosystem, while the mobile app forms the ecosystem’s mobile interface. Each group reaching the same vehicle data from a screen suited to its role means all parties talk on the basis of the same information. The integration infrastructure is the backbone of the ecosystem. The mobile app, fault detection and panels could each work on their own, but their value comes from data moving seamlessly between them.
Technologies Used
- OBD vehicle data: diagnostic data taken from the vehicle; the source of VT360 smart fault detection
- Integration infrastructure: the data flow between the mobile app, the panels and fault detection
Process
The steps below describe the general order we follow in multi-component projects that work with hardware data:
- Analysis: in projects of this kind, we identify where data is generated, who needs which data and which parties will connect to the system.
- Architecture design: the components and the data flow between them are planned with the integration layer at the centre.
- Development: the mobile app, fault detection, panels and integration infrastructure are developed to work together.
- Go-live: in systems of this kind, the uninterrupted flow of data from the device to the panel is tested end to end before going into use.
Results and Benefits
In this project we can summarise the result not with measurable figures but with the structure that was built. Vehicle health data was gathered on a single platform and connected to service and supplier processes. An integrated structure was set up that links OBD vehicle data to service and supply chain processes.
The lesson we took from this project: in software that talks to hardware, data must flow without interruption from the device to the panel. However well each component works, if the connections between them are weak, the ecosystem cannot create value as a whole. That is why the integration layer should be treated as the starting point of the design, not as a piece added at the end of the project.
Discuss a Similar Project
If you are developing a product that combines hardware and software, take a look at our custom software development and mobile app development services. Let’s talk about your project: tell us what you need and we will prepare a written proposal covering scope, timeline and cost. Call us on +90 850 335 10 87, message us on WhatsApp, email info@360-soft.com or use our contact page. You can also browse our other case studies.
This case study is a localized version of our reference page in Turkish: Türkçe.
