PRE2016 4 Groep4: Difference between revisions
(Added reference section) |
No edit summary |
||
Line 15: | Line 15: | ||
* Make to do list - Bern | * Make to do list - Bern | ||
* Get interviews with beekeepers - Allemaal | * Get interviews with beekeepers - Allemaal | ||
What to do for monday: | |||
Problem description | |||
- What are the exact problems we try to tackle (Pick 2 problems that we can tackle like winter, mites (and maybe dissentery) | |||
- Consequences of the problem (economic and environmentally) | |||
Our idea to tackle the problems | |||
- Smart beehive for optimal conditions (temperature, moisture, and more?) | |||
- Possibility to sense mites (in breed chamber) | |||
- Possibility to eleminate mites (put chemical in specific breed chambers) | |||
= Week 1 = | = Week 1 = |
Revision as of 11:08, 4 May 2017
Group Members
- Bern Klein Holkenborg 0892107
- Marrit Jen Hong Li 0963568
- Jorik Mols 0851883
SSA
- Look up why bees are dying exactly - Marrit
- What are the consequences - Bern
- What do bees need to live - Koen
- What is the state-of-the-art - Marrit
- Investigate USE aspects - Jorik
- Make to do list - Bern
- Get interviews with beekeepers - Allemaal
What to do for monday: Problem description
- What are the exact problems we try to tackle (Pick 2 problems that we can tackle like winter, mites (and maybe dissentery) - Consequences of the problem (economic and environmentally)
Our idea to tackle the problems
- Smart beehive for optimal conditions (temperature, moisture, and more?) - Possibility to sense mites (in breed chamber) - Possibility to eleminate mites (put chemical in specific breed chambers)
Week 1
The progress of the first week is shown below. The start of the project is described and explained in categories.
Assignments and results
Subject
Bees are little creatures, yet essential to flora and fauna around the globe. Bees are some of the hardest working creatures on the planet, and because of their laborious work ethic, we owe many thanks to this amazing yet often under appreciated insect.
Our lives – and the world as a whole – would be a much different place if bees didn’t exist. To illustrate this fact, consider these numbers: bees are responsible for pollinating about one-sixth of the flowering plant species worldwide and approximately 400 different agricultural types of plant. Thus bees support a large billion euro economy of farmer industry, but more importantly, bees support a wide variety of food for both animals and humans.
However, in recent years, bee population has dramatically dwindled down, mainly because of freezing to death in harsh winters caused by global warming. To indicate the problem: In the last decade, 30% of the bee population in the United States dissappeared already.
In this project, this problem is analysed and a robotic solution like a smart beehive will be investigated.
Objectives
In order to keep bees alive in winter, a system is needed that monitors and acts on the bee colony and it's environment. The main and obvious objective thus is keeping bee colonies alive. However furter objectives have to be set as to specify our goals for this system.
Bees are fragile creatures, this system has to protect them versus an everchanging harsh environment. Information is essential for any smart system so it can act upon the data. The monotoring of a bee colony should be accurate, have a wide range of parameters such as temperature, humidity, bee activity, bee deaths, bee population and honey storage, and most importantly, the monotoring of the bee colony should not interfere with the colonies well-being. Creating such a monotoring system will prove to be challenging but essential, thus making this our first objective.
Secondly, the smart beehive must be able to act upon the information fed to the system via it's sensors. It not only should inform beekeepers on essential data, but should interact with the system itself as well. It should be able to change temperature and humidity. It should be able to control light level and intensity. It should be able to control it's doors. It should maybe even control where the colonies queen is located, or where/how/when how much honey is stored. These actuators have to be designed as to comfort the colony without any possible chance of inflicting damage to the colony and or beekeeper.
As said above, the system should be interactable by human as well. Information must be fed to the beekeeper for optimal beekeeping. This information stream must be desigend and an user-friendly interaction system should be included in the smart beehive.
Optimally, the smart beehive should be modular, as to easily increase or decrease the capacity of the hive as needed by the beekeeper. A compleet smart beehive is to be designed/prototyped and subjected to a series of test by expert and amateur beekeepers. Usability, effectivity, productivity and overall benefit are to be assesed.
Users
The users of this system consists mostly of beekeepers, who are given the responsibility of caring for the bees in the system. On a larger scale, companies might be interested in having a multitude of these systems, so that their employees (eg their own beekeepers) have to maintain them. These two groups are in direct contact with the system, such that the interface of the system is necessary knowledge for those groups.
Users that do not depend on the actual usage (and interface) of the system are for example gardeners or flowerists who want to have a beehive system nearby to aid the pollinating of their flowers. These stakeholders might hire someone to maintain the system for example, such that the purchasing and selling of these systems becomes a separate product or trade. Again, on a larger scale the ruling parts of provinces or countries might be involved with large-scale deployment of these systems, as to ascertain the survival of bees for our future.
Both these user groups have different needs towards such a beehive system.
Direct users want:
- The interface to the beehives to be easy to use and understand
- The usability of the beehives to be restricted to certain personnel
Owners of a beehive system (owning it for their own purpose but not directly using it) want:
- The system to be affordable
- The system to be easily placeable, and if possible to be compact
Finally, all users have the common need that the system should be reliable, so that the deployment of these systems helps in the survival of bees to some specified extent.
Approach
Our approach is to define the current problems with keeping bees alive, especially in the winter, and then try to incorporate solutions to these problems in our prototype. Our prototype should be able to be tested, probably by means of simulation. This way we can find out what the effectiveness of our system is at every point in its development.
More concrete, the milestones we will have to reach in the development of our system and in our general approach for this project are:
- Creating a way of simulating our design
- This means we have to select some kind of software or maybe even hardware
- Being able to collect test results from this simulation efficiently
- Depending on what platform we run tests, this might again be a software issue or a hardware issue
- Also needed here is some place to store test results and maybe visualize them
- Improving upon our design such that these test results can be optimized
- For this we need to define parameters that we can optimize
As it says above, we still have to find out if we are going to develop our model of a beehive system by using software or hardware. This will be looked into in the second week. Collection of test results entirely depends on this choice, and thus we will have to figure that out after we know how we will develop our model.
Project planning
Week 2:
- Give presentation
- Research into the subject, state-of-the-art and USE aspects
- Define a concrete problem
- Brainstorm on potential prototypes
- Contact users we could interview
- Finalize planning and work division
- Update wiki and evaluate progress made in the previous week
Week 3:
- Finish research
- Start on design prototype
- Interview users
- Update wiki and evaluate progress made in the previous week
Week 4:
- Finish design prototype
- Work on prototype itself
- Interview users
- Update wiki and evaluate progress made in the previous week
- Evaluate planning
Week 5:
- Work on prototype itself
- Interview users
- Update wiki and evaluate progress made in the previous week
Week 6:
- Finish interviews
- Finish prototype
- Testing prototype and discussing improvements
- Update wiki and evaluate progress made in the previous week
Week 7:
- Improving prototype
- Testing prototype
- Finishing the wiki
- Working on final presentation
- Evaluate progress made in the previous week
Week 8:
- Final presentation
- Finalize prototype and wiki