When designing cloud applications, you should take into account the fact that a failure or malfunction of any component of the system is possible. This template is called Designing for Failure. This design approach helps minimize the negative consequences of failure of any component of the internal or external system. Sometimes, it is not so simple to use the Designing for Failure template, but the Azure platform greatly facilitates this task due to the fact that some of the functions are implemented by cloud services—Azure Web Sites, Traffic Manager, CDN, RA—Geo Redundant Storage. During this session, we shall talk about how to use the functionality provided by Azure to ensure the accessibility of a website, even in the event of failure of one of the regions of the platform.
UCB is a patient-centric biopharma leader, focusing on severe diseases in Immunology and the Central Nervous System. The company employs in the region of 9000 employees and operates in approximately 40 countries. UCB achieved revenues of $3.46 billion in 2012.
The main driver to implement Lync in the early part of 2011 was first started by the need for a video conferencing solution. This was further accelerated by the "Smarter Ways" efficiency program – which included effective collaboration within the scope. The Lync conferencing services alone helped UCB realize savings of $1.2M compared to the legacy conferencing solutions that were previously in place. The choice of Lync has also allowed full integration of the Unified Contact Centre systems at UCB.
During this session, UCB will cover their drivers for unified communication, the Lync journey (strategy with scope expansion and timeline), communication & change management activities and finally some KPI's.