We continue to develop resources related to the COVID-19 pandemic. See COVID-19 initiatives on Appropedia for more information.

International collaboration protocol QAS

From Appropedia
Jump to navigation Jump to search

QASlogo.png This page was developed by the Queen's University Applied Sustainability Research Group. QASlogo.png

This page discusses how to run an international collaboration on scientific and engineering research in applied sustainability.

It includes links to software and services and provides an example project: Open source solar spectrum project

The desgin of an international collaboration will be divided into categories related to the development of an engineering project

Project Scope and Description Definition

The first and most important step of the project is the clear definition of project scope. This will allow for the proper allotment of resources (both human and physical) to the varying aspects of teh project, and will ensure that project completion is possible. Especially in an international context, it is important to ensure that the scope and description of the project is well understood, and is aceivable with the resources available at each location. In order to ensure full comprehension by all parties, the project scope and descriptoin should be written down and sent to all parties in the project. In the case of a modificaiton of scope or description, these modifications should similarily be written and distributed.

Assignment of Roles and Responsibilities

Definition of project timelines and goals

Progress tracking


Project completion

Useful software packages and best practices for use

Teams are responsible for:

  1. In week 1, students choose a format for communication in both asynchronous and synchronous situations in private. You enable your advisors to see what is going on....(e.g. Emails are cc'd, blogs passwords are provided).
  2. In week 1, create a Gantt chart of tasks and the individuals that will be responsible for them
  3. Use a logged weekly full team meetings(voice)(private).
  4. Use a design journal/idea blog/chat room/wall, which is logged?(private).
  5. Share design iterations shared on Appropedia [project] and Thingiverse [designs] (public) – history file will track contributions.
  6. Building and testing the devices, with publishing full instructions/protocols.
  7. Develop method of sharing data access between universities and the public. See for example Pachube or consider ftp protocol – whatever is going to work.