Establish the AI infrastructure for analysis of the electricity data (3/7)

From its-wiki.no
Jump to: navigation, search

Establish the AI infrastructure for analysis of the electricity data (thesis #3/7)

by N.n.
Supervisor(s) Josef.Noll, György Kálmán
Due date 2022/05/12
Status Planned
Problem description: Future Homes have the opportunity to be adaptive to the quality of the electricity grid. By monitoring the energy consumption on fuse-level every 10 seconds, one can generate energy profiles of private homes. Current regulations suggest a reading of power values 1/hour, or in maximum every 15 min. Given a high-frequency reading of power consumption (1/10s, 1/min) might give an opportunity to introduce new services.

Given the size of the work, several theses can be performed on the topic:

  1. Establish the low-power monitoring infrastructure in the home (Raspberry Pi/Arduino and ModBus to read from Power Taggs)
  2. Create the public source database for energy consumption, combining high-resolution energy data with 3rd party information such as weather data
  3. Establish the AI infrastructure for analysis of the electricity data
  4. Monitoring the home energy distribution - Feature extraction through AI
  5. Potential of contributions from private homes to energy stability
  6. Wireless control systems for home appliances to support the energy transition
  7. Security and privacy assessment of wireless in-house control systems for energy appliances

The assessment will be based on high-frequency consumption data from actual smart meters and power taggs by fuse level, as well as modelling of services.

Methods and Tools: The tools and methods in this thesis are based on
  • A set of scenario, describing the challenges
  • A list of requirements being extracted from the scenarios
  • A description and evaluation of technologies and tools being candidates for solutions
  • A functional architecture/description of the envisaged system
  • An implementation of the core concepts
  • A demonstration of the solution
  • An evaluation of the solution, including a critical review of the descisions taken earlier
  • Conclusions
  • References
Time schedule The envisaged time schedule (for a long thesis/60 ECTS) is:
T0 0 starting month, T0+m denotes the month where the contribution to a certain chapter shalle be finalized
T0+2 months: create an initial page describing the scenario
T0+3: Provide a list of technologies which you think are necessary for the thesis
T0+4: Establish the table of content (TOC) of the envisaged thesis. Each section shall contain 3-10 keywords describing the content of that section
T0+7: Provide a draft of section 2 (scenario) and 3 (technologies)
T0+10: Establish a draft on what to implement/architecture
T0+11: Set-up an implementation, testing and evaluation plan
T0+15: Evaluate your solution based on a set of parameters, keep in mind there is no such thing as a free lunch
T0+17: Deliver the thesis
Pre-Knowledge This thesis includes a reasonable amount of programming. The envisaged thesis involved security and semantics.
Approved Pending by
Keywords IoTSec, Fog computing, Edge computing, Privacy, Services, Smart Home
Depiction

this page was created by Special:FormEdit/Thesis, and can be edited by Special:FormEdit/Thesis/Establish the AI infrastructure for analysis of the electricity data (3/7)

This page provides hints on what to include in your master thesis.

TOC

Title page, abstract, ...

1. Introduction, containing: short intro into the area, what is happening
1.1 Motivation, containing: what triggered me to write about what I'm writing about
1.2 Methods, containing: which methods are you using, how do you apply them
2. Scenario, optional chapter for explaining some use cases
2.1 user scenario, (bad name, needs something bedre)
2.2 Requirements/Technological challenges
3. State-of-the art/Analysis of technology, structure your content after hardware/SW (or other domains). Describe which technologies might be used to answer the challenges, and how they can answer the challenges
3.1 technology A
3.2 technology B
4. Implementation
4.1 Architecture, functionality
4.2
5. Evaluation
6. Conclusions
References

Comments

Red line

Your thesis should have a "red line", which is visible throughout the whole thesis. This means you should mention in the beginning of each chapter how the chapter contributes to the "goals of the thesis".

Use of scientific methods

A thesis follows a standard method:

  • describe the problem (problemstilling)
  • extract the challenges. These challenges should be measurable, e.g. method is too slow to be useful to voice handover.
  • Analyse technology with respect to challenges. Don't write & repeat "everything" from a certain technology, concentrate on those parts (e.g. protocols) which are of importance for your problem

References

  • Wikipedia is good to use to get an overview on what is happening. But there is not scientific verification of Wikipedia, thus you should use wikipedia only in the introduction of a chapter (if you use text from wikipedia). Use scientific literature for your thesis.
  • Scientific library is "at your hand", you can get there directly from UiO: [[How to get access to IEEE, Springer and other scientific literature -> Unik/UiOLibrary]]
  • I suggest that references to web pages, e.g. OASIS, W3C standards, are given in a footnote. Only if you find white papers or other .pdf documents on a web page then you refer to them in the reference section.

Evaluation of own work

Perform an evaluation of your own work. Revisit the challenges and discuss in how you fulfilled them. Provide alternative solution and discuss what should be done (or what could have been done).