87 lines
2.7 KiB
Markdown
87 lines
2.7 KiB
Markdown
---
|
||
title: 17.06.2025 - Pilot Kickoff Planning
|
||
created_date: 2025-06-12
|
||
updated_date: 2025-06-12
|
||
meeting_date:
|
||
aliases:
|
||
tags:
|
||
type: habit
|
||
status: not_started
|
||
---
|
||
# 17.06.2025 - Pilot Kickoff Planning
|
||
- **🏷️Tags** : #06-2025 #habit
|
||
---
|
||
## Meeting Summary
|
||
### Participants
|
||
-
|
||
### Summary
|
||
> [!important] 17.06.2025 - Pilot Kickoff Planning
|
||
> Please summarize the meeting here
|
||
|
||
## Preparation
|
||
### Points to Discuss
|
||
- last week showed many problems
|
||
#### Problems
|
||
- we have so many pcbs that are not well tested --> we don't even know what is happening. Every P we make should be onboarded --> user manual, way of logging its sensors continuously (ideally fully integrated, less ideal with a teensy, instructions and a serial port)
|
||
- we build everything from scratch --> takes a lot of time, a lot of tooling is missing. visualization tools, etc.
|
||
-
|
||
|
||
### Timeline
|
||
|
||
|
||
December:
|
||
Pilot Project Start
|
||
-
|
||
|
||
### Agenda
|
||
1. Quick Overview of Scope, Timeline and goals
|
||
2. Detailed definition of scope
|
||
3. Detailed requirements definition based on scope
|
||
4. Review rough planning and then go into detailed planning based on requirements
|
||
1. Areas: drone development (hardware, software), ground station development, business software development, regulatory, testing and QA
|
||
2. For each area: final requirements, intermediary milestones,
|
||
## Meeting Minutes
|
||
|
||
Vertrag abgeschlossen
|
||
|
||
Ziel: Launch im Dezember.
|
||
|
||
|
||
Hasan: waypoint mission and hooklanding.
|
||
Valentin: focus on reliability and VTOL full flight envelope.
|
||
|
||
### Definition of Pilot Project
|
||
- 3-4 active drones
|
||
|
||
#### Mobile Parts
|
||
- second story with windows that can be opened and contain a second smaller glass (1), which acts as a fall guard for people.
|
||
- if crash, drone falls onto cars / people. (2)
|
||
|
||
![[Pasted image 20250623154221.png]]
|
||
|
||
#### Stallikon as Homebase
|
||
- Avoid busstop
|
||
- avoid sunflower drones
|
||
- what is the garage of drones?
|
||
- automatische sonnenstoren
|
||
- kleiner Regenschirm.
|
||
#### JTL Extension
|
||
- Both customers (mobile parts and tobacco shop in schwyz) use [JTL](https://www.jtl-software.de/) as their e-commerce platform.
|
||
- We can build a JTL extension (OneSec Drone Delivery) which integrates with their website.
|
||
- We get information of new orders.
|
||
- we know where the drone needs to fly.
|
||
- Involve Hasan in JTL extension dev: interfaces need to work together with the autopilot.
|
||
- Fleet management (can be primitive) or off the shelf (OTS).
|
||
|
||
#### Example Delivery to Wohlen Downtown
|
||
- ~11km, roughly 500m over populated area.
|
||
- Transition always over forest / fields
|
||
|
||
#### VTOL
|
||
- Enough testing in all different conditions.
|
||
- we need to be confident that it works.
|
||
|
||
|
||
#### Alternatives if Problems
|
||
- if no VTOL: charging infrastructure needed at customers
|
||
- custom GCS? [Anra](https://www.anratechnologies.com/home/)? |