<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Call for Workshops: UCC 2014<br><br>7th IEEE/ACM International Conference on Utility and Cloud Computing<br><br>8-11 December 2014 Hilton London Paddington<br><br>General Information<br><br>Cloud Computing promises to deliver computational resources on demand as services that are commoditised and delivered as in traditional utilities such as electricity, gas, water and telephony. Utility with Cloud services can already be achieved for compute, storage and communication resources but also for hosted software and data. UCC is the premier IEEE/ACM conference covering all areas related to Cloud Computing as a Utility. There is also increasing interest from commercial providers to offer business and revenue models around the services they offer. Understanding how these models could be used to provide utility for both users, intermediary brokers (aggregators) and providers will also be of interest for this conference.<br><br>This will be the 7th UCC in a successful conference series. Previous events were held in Shanghai, China (Cloud 2009), Melbourne, Australia (Cloud 2010 & UCC 2011), Chennai, India (UCC 2010), Chicago, USA (UCC 2012), and Dresden, Germany (UCC2013). UCC 2014 happens while cloud providers worldwide add new services and increase utility at an accelerated pace and is therefore of high relevance for both academic and industrial research.<br><br>Important Dates<br><br>Workshop proposals and any enquiries should be sent by e-mail to the workshops chair<br><br>Josef Spillner <<a href="mailto:josef.spillner@tu-dresden.de">josef.spillner@tu-dresden.de</a>><br><br>Proposals should be submitted in PDF format.<br><br><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Workshop Proposals Due: 12 May 2014<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Notification of Acceptance: 26 May 2014<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• URL of Workshop: 9 June 2014<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Workshops: 8-11 December 2014<br></div>Proposal Requirements<br><br>Proposals for workshops should be no more than 2 pages in length. This should contain the following information.<br><br><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Title and brief technical description of the workshop, specifying the goals and the technical issues that will be the focus of the workshop.<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• A brief description of why and to whom the workshop is of interest.<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• A list of related workshops or similar events held in the last 3 years, or to be held in 2014.<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• 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.<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• 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.<br></div>Responsibilities<br><br>Workshop chair(s) will be responsible for the following:<br><br><div><span class="Apple-tab-span" style="white-space:pre"> </span>• 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 2014 conference registration fee. Finally, it should also clearly describe the process by which the Organizing Committee will select the participants.<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• 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.<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Provide a brief description of the workshop for the conference web page and program.<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• 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.<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Assistance in producing a camera-ready version of the workshop proceedings.<br></div><div><br></div>Important Note<br><br><br><div><span class="Apple-tab-span" style="white-space:pre"> </span>• If the workshop is too small (i.e. does not attract enough submissions) the UCC 2014 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.<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• 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%.<br></div><div><br></div>The UCC 2014 Conference Organizing Committee will be responsible for the following:<br><br><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Providing a link to a workshop’s local page.<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Providing logistics support and a meeting place for the workshop.<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• In conjunction with the organizers, determining the workshop date and time.<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Providing copies of the workshop proceedings to attendees.<br></div><div><br></div>Topics of interest to the conference include (but are not restricted to):<br><br><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Big Data and Analytics<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Principles and theoretical foundations of Utility Computing, including pricing and service models<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Policy languages and Programming models<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Architectural models to achieve Utility in Clouds<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Designs and deployment models for Clouds: private, public, hybrid, federated, aggregated<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Cloud Computing middleware, stacks, tools, delivery networks and services at all layers (XaaS)<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Virtualisation technologies and other enablers<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Economic models and scenarios of use<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Scalability and resource management: brokering, scheduling, capacity planning, parallelism and elasticity, as well as marketplaces<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Cloud management: autonomic, adaptive, self-*, SLAs, performance models and monitoring<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Applications: games, social networks, scientific computing (e-science) and business<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Mobile and energy-efficient use of Clouds<br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>• Beyond technology: Cloud business and legal implications, such as security, privacy, trust and jurisdiction especially in Utility contexts</div><div><br></div><div><br></div><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">=============================================================<br>Ivan Rodero, Ph.D.<br>Rutgers Discovery Informatics Institute (RDI2) <br>NSF Center for Cloud and Autonomic Computing (CAC)<br>Department of Electrical and Computer Engineering <br>Rutgers, The State University of New Jersey <br>Office: CoRE Bldg, Rm 624 <br>94 Brett Road, Piscataway, NJ 08854-8058<br>Phone: (732) 993-8837<br>Fax: (732) 445-0593<br>Email: irodero at rutgers dot edu<br>WWW: <a href="http://nsfcac.rutgers.edu/people/irodero">http://nsfcac.rutgers.edu/people/irodero</a><br>=============================================================<br><br></div>
</div>
<br></body></html>