Ford Otosan · CPE Tribe
Every vehicle has something to say. Every engineer has a question waiting. We build the software in between.
01 · Connected Products
Connected Vehicles API
One front door to every connected vehicle.
One official gateway to the vehicles Ford Otosan builds: one login, one format, one way to ask. Live gRPC streams, remote commands and an AI assistant on top. And data only flows once the vehicle owner approves, as the European Data Act asks.
Ask your fleet
Connected vehicle reports, without the SQL.
More than a dozen ready-made reports follow each vehicle from the factory, through transport, onto the road: batteries, fault codes, over-the-air updates. And for the question no report covers, just ask in plain language.
Dealer portal
The customer's trucks, seen by the dealer they trust.
A truck already reports how it is doing, but the dealer who services it usually cannot see that. ConnecTruck Dealer shows each dealer the trucks their customers have authorized: health in three states, fourteen days of history, error codes and driving reports. The vehicle data arrives through CAPI.
Back office
The back office behind every connected truck.
When a fleet manager calls, staff need the whole customer in one look. The Admin Panel finds the customer, the truck and the dealer, starts and stops subscriptions through one central service, handles cancellation requests, and sets what each truck's connectivity unit may do. It can also open a logged view of what the customer sees.
Connectivity cost
The SIM invoice: checked, split, explained.
Every connected vehicle carries a SIM, and every month the operator bills for all of them. VFBill checks that invoice against usage, the contract and the fleet, splits it across the business units that pay, and locks the number once it is approved.
02 · Engineering Services
Digital product development
One dashboard for every open issue.
An engineer's open items used to live in twenty-five different systems. DigitalPD reads them from a single data hub, so every engineer sees what is waiting on them, and every leader sees where the team stands.
Engineering knowledge, in the room
One conversation, signed in as you.
It reads your open issues, searches the fixes the company has already verified, and drafts the closure. Once your manager approves, that solution becomes knowledge for the next engineer.
Engineering tools, one address
Sign in once. Every engineering tool is there.
The app catalog for Product Development, and the home of the tools we build ourselves. Program health as fifteen green-or-red cards. A parts inventory you scan by QR code. A suspension calculator with the formula written once. And usage numbers for every app behind the door.
How we build
Vehicle data flows only after the owner approves a specific request, and stops when they withdraw. Inside the company, an assistant calls each system as you: if you can't see a row on the screen, you won't see it in the answer.
CAPI · EngineeringAI · DigitalPDBefore any language model runs, a small guard model reads the question. In scope? Personal data? An injected instruction? Off-topic questions are refused before they cost anything, and most answers cost less than a cent.
Condash · EngineeringAIEvery Condash query is also a tool, served over the Model Context Protocol. The catalogue behind the CAPI Assistant is open to your own AI agents. Reports and assistants run the same governed queries.
Condash · CAPIClean layers, read-only access, one rule written once in one place. And thousands of automated tests: more than 3,500 behind DigitalPD, more than 1,700 guarding CAPI.
DigitalPD · CAPI · CondashPick a story. Each one runs three to seven minutes, with sound.