User needs

From Control Systems Technology Group
Revision as of 18:19, 24 February 2018 by S160587 (talk | contribs)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
  • For window washing companies, speed in terms of surface area cleaned per unit of time is of major importance. The higher the speed with which the windows can be cleaned, the more profit that can be made. The goal is to reach a speed of 71 m2 / hr, which is the mean of the three considered window cleaning robots as can be seen in the table below. This seems an acceptable requirement for the model.
  • Water consumption should be as low as possible, since this has an impact on the speed of the cleaning process (provided that the robot has an on-board water tank that needs to be refilled) and also has a minor impact on the total cost of the cleaning job. All current window cleaning robots of the here considered size do not have a water supply or tank, but use detergent instead. The innovate part of the model is therefore that a water supply is included. This is an improvement since this is better for the environment. The requirement for the water consumption is based on a bigger window cleaning robot (GEKKO Facade Robot [7]) which has a water consumption of approximately 1 L/min. Because this bigger robot has a size of around 4 times the size of the considered cleaning robots, a requirement of 0.25 L/min seems suitable.
  • Energy consumption should be as low as possible, since this has an impact on the total cost of the cleaning job. The requirement for the energy consumption is also determined by averaging over the different window cleaning robots in the table above: 73.5 W.
Week What? Who?
1
  • Finish work plan
  • Finish literature study and SotA (Everybody searches 5 articles, reads them and summarizes them)
  • Everybody together
  • Everybody
2
  • Finish analysis of the user and user needs
  • Start solution map
  • Jorick, Kylian
  • Ezra, Ibrahim, Lars
3
  • Finish solution map and pick final solution
  • Everybody
4
  • Start detailing and optimization of final solution, reflect on user needs
  • Start with model
  • Lars, Ibrahim
  • Ezra, Kylian, Jorick
5
  • Finish detailing and optimization of final solution
  • Improve and finish model
  • Start with report
  • Lars, Ibrahim
  • Ezra, Kylian
  • Jorick
6
  • Finish report
  • Everybody
7 ... ...