IoTDI 2017 Call for Posters/Demos (CFP in PDF)

 
ACM/IEEE IoTDI is a premier conference on IoT and a new member of CPS Week! Topics span the entire ecosystem revolving around IoT, such as cloud and edge computing, data analytics, sensor networks, mobile devices, Internet architecture, middleware and numerous IoT applications. IoTDI organizers invite you to submit posters and demos.

Important Dates:


  • Submission deadline: Wednesday, Feb 15th
  • Acceptance notification: Monday, Feb 20th
  • Final manuscript deadline: Wednesday, March 1st

Poster/Demo Submission Link


Submit your posters and demos through EasyChair.

Poster Submissions


Posters will provide an opportunity for conference attendees to learn about innovative work in progress and to preview late-breaking research results. Poster sessions will provide an informal setting for presenters to communicate ideas or results and obtain feedback from attendees. If you have any questions, please contact the poster chair: Octav Chipara (University of Iowa) at octav-chipara@uiowa.edu.

Submissions describing posters should be at most 2 pages PDF using the ACM proceedings format . The submission should include:

  • Title of the poster (beginning with “Poster Abstract:”)
  • Authors, affiliations, and contact information
  • A description of the problems addressed
  • Research and technical approach
  • Preliminary results
  • Related work with bibliography


Demo Submissions


Demo submissions will give the audience an up-close peek into the latest technologies, systems, devices, and other (Internet-) “Things,” offering an interactive experience with the demonstrated entities. Demo abstracts should describe both the technology being showcased as well as the user experience of the demo. If you have any questions, please contact the demo chair: Mi Zhang (Michigan State University) at mizhang@egr.msu.edu.

Submissions describing live demos should be at most 2 pages PDF using the ACM proceedings format . The submission should include the following:

  • Title of the demo (beginning with “Demo Abstract:”)
  • Authors, affiliation, and contact information
  • A description of the problems addressed
  • Research and technical approach
  • A description of user experience/interaction with the demo
  • Related work with bibliography