Accepted Workshops

The following workshops have been accepted so far, and the call for workshops has been extended to 22 June, 2017. Check back frequently for information on submission and deadlines for participation in each of the accepted workshops, and contact the workshop committee if needed for any questions.

Further Workshop Proposals

Workshop proposals and any inquiries should be sent by e-mail to the workshops chairs:
  • Josef Spillner josef.spillner(at)
  • Khalid Elgazzar elgazzar(at)
Proposals should be submitted in PDF format.

Topics of interest include but are not limited to:
  • Principles and theoretical foundations of Utility Computing, including pricing and service models
  • Policy languages and programming models, such as cloud-native and cloud-enabled applications
  • Utility-driven models and mechanisms for Cloud federations
  • Autonomic techniques for Cloud applications
  • Utility-/comfort-driven platforms for Clouds
  • Architectural models to achieve Utility in Clouds
  • Designs and deployment models for Clouds: private, public, hybrid, federated, aggregated
  • Cloud Computing middleware, stacks, tools, delivery networks and services at all layers (XaaS)
  • Integration of Cloud systems with edge devices
  • Virtualization technologies and other enablers
  • Economic models and scenarios of use
  • Scalability and resource management: brokering, scheduling, capacity planning, parallelism and elasticity, as well as marketplaces
  • Cloud management: autonomic, adaptive, self-*, SLAs, performance models and monitoring
  • Applications: games, social networks, scientific computing (e-science) and business, as well as large-scale foundations for Big Data and analytics
  • Mobile and energy-efficient use of Clouds
  • Cloud business and legal implications beyond technology, such as government regulation, security, privacy, trust and jurisdiction especially in Utility Computing contexts
  • Hands-on activities, tutorials, and instructional sessions on new technologies and methods

Important Dates

Workshop Proposals Due: 14 May 2017 —> extended to 22 June 2017
Notification of Acceptance: 28 May 2017 —> extended to 30 June 2017
URL of Workshop: 04 June 2017 —> extended to 5 July 2017
Camera-ready & Registration: 30 September 2017
Workshops: 5-8 December 2017

Proposal Requirements

Proposals for workshops should exceed 2 pages in length and must contain the following information.
  1. Title and brief technical description of the workshop, specifying the goals and the technical issues that will be the focus of the workshop.
  2. A brief description of why and to whom the workshop is of interest.
  3. A list of related workshops or similar events held in the last 3 years, or to be held in 2017.
  4. The names and contact information (web page, email address) of the proposed technical program committee. This committee should consist of at least 10 people knowledgeable about the technical issues to be addressed and preferably not more than two members of the same institution. Ideally, there should also be two organizers from distinct institutions.
  5. A description of the qualifications of the organizers (who would be the Workshop Chairs) with respect to organizing this workshop. This can include papers published in the proposed topic area, previous workshop organization, and other relevant information.


Workshop chair(s) will be responsible for the following:
  • Producing a web page and a “Call for Papers/Participation” for their workshop. The URL should be sent to the UCC Workshops chairs. The call must make it clear that the workshop is open to all members of the Cloud, Big Data, Grid and Cluster Computing community. It should mention that at least one author of each accepted submission must attend the workshop and that all workshop participants must pay the UCC 2017 workshop day registration fee or the conference fee. The CfP should make it clear that the registration of at least one author requires the full (non-student, non-workshop) rate.
  • Ensure that all workshop papers are a maximum of 6 pages in length (in IEEE format). It is the responsibility of the workshop organizers to ensure that this page limit has been adhered to. Additional pages may be purchased (in some circumstances) subject to approval by the proceedings chair.
  • Provide a brief description of the workshop for the conference web page and program.
  • Selecting the participants and the format of the workshop. The publication of proceedings will be by the IEEE in the same volume as the main conference.
  • The acceptance notification (by workshop chairs) therefore should be the same as “conference paper acceptance” notification (i.e. the dates should be the same). All other details can be up to workshop organizers to set.
  • Advertising the workshop beyond the conference web page.
  • Assistance in producing a camera-ready version of the workshop proceedings.

The UCC 2017 Conference Organizing Committee will be responsible for the following:
  • Providing a link to a workshop's local page.
  • Providing logistics support and a meeting place for the workshop.
  • In conjunction with the organizers, determining the workshop date and time.
  • Providing copies of the workshop proceedings to attendees.

Details and Important Notes

  1. If the workshop is too small (i.e. does not attract enough submissions) the UCC 2017 Organizing Committee may decide to merge that workshop with another. So we encourage workshop organizers to attract a large community. In extreme situations we may also cancel workshops if there are not enough submissions.
  2. Workshop organizers must ensure that suitable quality measures have been taken to ensure that the accepted papers are of high quality. All papers must be reviewed by an International Technical Program Committee with a minimum of 3 reviews per paper. The workshop organizers should also try to observe an acceptance rate that is no higher than 50%.
  3. Unless indicated on the UCC website, there will be no travel support and no registration discounts for authors and organizers.
  4. Workshops are not automatically endorsed by IEEE or ACM and should not use the names of these organizations in their titles.

Important Dates

* ( Separate calls for submissions will be issued by each workshop or tutorial accepted )


Stacks Image p139_n33
Stacks Image p139_n31
Stacks Image p139_n35
Stacks Image p139_n40
Stacks Image p139_n42

Hosting Organizations

Stacks Image p139_n50
Stacks Image p139_n46