Canary Orchestrator for Over-The-Air
| Name | GitHub Handle | Role(s) |
|---|---|---|
| João Chagas | joaocalixto | Pitch writer |
| João Barradas | jbarradas | front-end |
| Gustavo Calonico | randomcash | back-end |
| Nuno Valente | nuvan | back-end |
| Luis Varela | man-lvarela | back-end |
Update Possible Challenge: OTA updates for ECUs
To implement an OTA release process with real-time monitoring and automated decision logic. The solution will deploy updates via a canary release (e.g., 0.5% of devices), progressively expanding the rollout if telemetry shows no regression, or trigger an automatic rollback when error budgets are exceeded. This ensures safe, scalable, and adaptive OTA deployments.
flowchart TD
A[Start OTA Release] --> B[Canary Rollout e.g. 0.5% of devices]
B --> C[Real-time Monitoring & Telemetry]
C --> D{Errors within threshold?}
D -- Yes --> E[Progressively Expand Rollout]
E --> C
D -- No --> F[Automatic Rollback]
F --> G[Restore Previous Stable Version]
E --> H[Full Deployment All Devices]
H --> I[Safe, Scalable & Adaptive OTA Deployment]
Development Process - Iterative approach
- Deploy & rollback – The first milestone was making deployment and rollback mechanisms functional.
- Error monitoring – Functional code was connected to C∞TA module to read errors and validate the next course of action.
- Scalable rollout – Once stability was achieved, we focused on enabling deployment at scale.
- Team division – To move faster, we split into three focus areas:
• Pitch & presentation • Back-end • Front-end
We started with a brainstorming session to define the core idea and outline our priorities. From there, progress was tracked through constant update checks and quick syncs, allowing for adaptation to new challenges and keeping everyone aligned.
Given the short timeframe, we focused on starting small and writing clean and iteratively scaling to ensure clarity. We hope that this approach can make collaboration smoother and reduce integration issues.
Communication is happening both in person during the hackathon and through a shared Slack group channel, ensuring quick exchanges and transparency across the team.
All important decisions are being made through unanimous agreement. This ensures that every team member is aligned with the direction and feels a sense of ownership over the solution.