Whether or not you know it, the UAV you are planning to build right now has a specific mission it needs to fulfill. For many beginners, this can be as simple as having the capability to take off, fly for 5 minutes, and then land. Perhaps you want to lift a payload or achieve a certain speed. In any case, it is essential to be able to determine the mission requirements of your specific UAV project before even thinking about design. Doing so properly will serve to drive your project from start to finish.
Before defining what your mission requirements are, you will need to first think about what is you want your UAV to do. This should be very specific. As an example, we’ll say you want to build a UAV that can carry a small package of candy to your friend that lives two blocks away with a limited budget. You might define the following as your mission requirements:
- Payload capacity of 100g
- 10 minute flight time
- Capable of flying without line of sight (LOS)
- Capable of dropping payload remotely and accurately
- Fixed-wing configuration
- Hand launchable
- Costs under $100 to make
These mission requirements would then become your main considerations for most any design decision you make.
Concept of Operations
One way of visualizing your mission is to create a Concept of Operations, or Con Ops. This will lay out the different stages of your mission that need to be fulfilled using a a simple diagram or flow chart (see Figure 1). It can help you to have a better picture of everything that is required. This is turn will minimize the chances of neglecting any important mission requirements.
Once you have an idea of what your mission requirements are, you can start translating them into specific requirements for each of the systems in you UAV. You might categorize your systems as follows:
Each of these systems has a different function within the UAV, and will therefore be tied to different requirements. System requirements are generally much more specific than mission requirements, and typically much more measurable. You might even need to do some basic calculations to find good metrics to compare to. Continuing with our “candy drop” example, we produce the table of requirements below.
More requirements might be added further into the project, but this represents a good starting point for the candy drop. Notice that each system has specific, relevant requirements attached to them.
Key Performance Indicators
Some of these requirements are more qualitative, but many can be directly measured. To do so, you can create key performance indicators (KPI’s) to measure your design against as it is being developed. This has been done for the candy drop in the table below. As you get more detailed in your design, you can add benchmarks (or goals) for each KPI as something to measure against.