1. Beneficios de Cloud Computing Para PYMEs
consultoría . tecnología . outsourcing
2. Agenda
• Quienes Somos
• Introducción al Cloud Computing
• Evolución de los Modelos de Cómputo
• Retos y Beneficios Para los Negocios
• Ejemplos de Plataformas de Cloud Computing
• Caso de Exito
• Resúmen
3. Quienes Somos
Somos una firma de servicios profesionales enfocada en proveer
soluciones de negocio basados en cloud computing y online media.
Nuestra misión: Generar valor en los negocios impulsando la
innovación y crecimiento a través de:
1) Habilitar a los empleados, mejorando la colaboración, la
administración de la información y optimizando los procesos de
negocio.
2) Brindar mayor control mediante acceso y reporteo de
indicadores clave en tiempo real.
3) Conectar con los clientes mejorando las relaciones e
incrementando ventas.
4) Accesar nuevos mercados mediante la innovación y estrategias
de negocios en línea.
9. Definición
El cloud computing son servicios basados en hardware que
ofrecen servicios de cómputo, red, bases de datos y capacidad de
almacenamiento en los cuales:
1- La administración del hardware es altamente abstracta para el
usuario.
2- Los usuarios incurren en costos operativos de manera
variable.
3- La capacidad de la infraestructura es altamente elástica.
SOURCE: Amazon Web Site; McKinsey & Company
10. Modelos de “suscripción” de cloud computin
Los clientes accesan las aplicaciones
desde el proveedor de servicios cloud bajo
un modelo de suscripción
Los clientes accesan las BDs, herramientas
en plataformas cloud bajo un modelo de
suscripción
Los clientes proveen los servidores, equipo
de almacenamiento y bases de datos en
una infraestructura cloud
11. IaaS no elimina la complejidad del sw
Infraestructura Servidor de
de Software
BD Mensajería Herramientas
Aplicaciones
Infrastructure as a Service
Virtualización
Infraestructura Cómputo Almacenamiento Red Centro de Datos
de Hardware
“Actualizar, parchar, dar soporte al software consume más de la
tercera parte de los recursos de TI”
12. SaaS es más rápido.
Elimina la complejidad del hw y sw
Sin software que administrar
Actualizaciones automáticas
Elasticidad automática
Software como Servicio
Platform
BD Serv. Apps Mensajería Herramient
infrastructure as
Hardware Cómputo Almacenamiento Red Centro
Infrastructure Datos
“Desarrollar apps en PaaS es 5x más ágil”
14. Reducción de Costos
• Reducción en costos de TI: Reducción de costos directos e indirectos
relacionados con el sw, hw y mantenimiento. Mediante costos definidos
y flexibles, el cloud computing permiten que la información del negocio
esté segura, respaldada y accesible desde cualquier lugar.
• Costos indirectos: Reducción de gastos laborales permitiendo trabajar
a distancia y mejorar la administración de recursos empresariales.
• Ventas y mercadotecnia: Los CRMs y análisis de KPIs en línea
permiten determinar las campañas que son efectivas e invertir en
aquellas que generen mejores resultados.
• Administración de proyectos: Colabora en línea administrando y
centralizando información de proyectos para tener acceso al instante
de los avances de proyectos en un sólo lugar.
• Gastos de viaje: Ahorra gastos utilizando herramientas de
telepresencia, comparte información mediante videoconferencias para
tener presencia en cualquier lugar.
15. La infraestructura alenta el desarrollo de apps
Hardware Software
Infrastructure Infrastructure
Red Sist. Operativo
New Centro de Datos BD
Projects Multiples Serv. De Aplicaciones
dispositivos Servidor Web
Redundancia Servidor de Seguridad
Infrastructure Almacenamiento Servidor de
Disponibilidad Integración
DRP Servidor Móvil
Escalabilidad IDE
IT Time and Budget
“Los departamentos de TI invierten el 80% de su tiempo y
recursos manteniendo los sistemas en operación”
18. Automatización de flujo de trabajo
• Flujos de trabajo integrados: Navega en una Intranet con la misma
facilidad que un cliente navega en el sitio web público. Accesa
herramientas de Ventas, Mercadotecnia, Atención a Clientes,
Producción, Administración, documentos y calendarios compartidos. La
Intranet permite que cada trabajador vea su rol dentro de la
organización lo cual es invaluable para llevar a los colaboradores a
trabajar bajo los mismos objetivos de negocio.
• Single sign on: Mediante estándares como OpenID, accesa información
y apps de terceros con un sólo ID y contraseña.
• Elimina silos de información: La mayoría de las empresas cuentan con
silos de información clave en laptops, en la mente de los trabajadores
(sin documentar), hard drives, usb, servidores, sitios web y home PCs.
Cada silo es un obstáculo para la eficiencia. Al centralizar la
información, se reduce la redundancia, mejora la búsqueda y se
incremente la productividad.
• Centraliza la information y elimina fallas en tecnología:
Accesa información relevante en cualquier
dispositivo, eliminando fallas de hw o sw
19. Sitios Web Autoadministrables
Creación sitios dinámicos,
administrado por los usuarios
• Sin conocimiento de HTML
• Sin asistencia administrativa
• Autoadministrables
• Incluye documentos, calendarios,
mapas y cientos de apps de terceros
• Acceso controlado, por página, por
documento, por usuario
Múltiples casos de uso
• Múltiples sitios web dentro de un
dominio
• Intranets corporativas
• Sitios web de grupo
• Sitios web para proyectos
• Sitios web departamentales
20. Mejora la productividad y conecta con tus clientes
Crece tu negocio en línea.
Mide lo que realmente
importa. Prospectos, ventas,
oportunidades, utilidades.
Inteligencia de negocios.
Comparte proyecciones entre
equipos de ventas y personal
clave.
Acceso a KPIs.
Crea paneles customizados para
tener acceso a información
relevante de negocio.
21. Automatización del proceso comercial y servicio
• El CRM permite una visibilidad
completa en el proceso comercial:
mercadotecnia, proyección, ventas,
• Integración con redes sociales
servicio post venta
22. Facilidad de acceso a la información
• Acceso en cualquier plataforma.
Accesa información relevante del
negocio de manera segura fuera de
sitio pudiendo accesible desde
cualquier equipo.
• Navega y busca información para
obtener el contexto: Intranets para
navegar y obtener información por
departamento o proceso de negocio.
Para nuevos empleados, socios no
operativos, o inversionistas, provee
introspectiva al instante y confianza
en el negocio.
• Colabora en vez de enviar archivos
adjuntos: Con documentos en línea
colabora en una sóla versión de
documentos, elimina redundancia Busquedas internas en intranet
causada por versiones múltiples,
facilitando la búsqueda y acceso de
información.
23. Documentos en línea
Una sóla versión con acceso controlado
Herramientas para manejo de
documentos
• Procesamiento de texto, hojas de
cálculo, presentaciones y más
• Características únicas como formas para
hojas de cálculo y acceso remoto
Enfocado en la colaboración
• Colaboración múltiple en tiempo real
integrado en las aplicaciones
• Control de accesso a documentos a nivel
usuario, grupo e institución.
24. Redes sociales privadas para negocios
Colaboración en
tiempo real con
clientes y
socios de
negocio:
noticias,
documentos,
oportunidades de
venta o soporte
post venta, etc
Colaboración
móvil
26. Mayor control
Intranets y herramientas en línea para incrementar la transparencia:
• Notificación de cambios: El uso de documentos en línea permite a los
colaboradores ser notificados de cambios realizados por otras
personas.
• Alinea tareas a objetivos: Mediante herramientas funcionales de
negocio como CRM, Proyectos, RH y Reclutamiento, define objetivos y
asigna tareas para alcanzar dichos objetivos.
Los colaboradores pueden
dar seguimiento a los avances
para facilitar la colaboración,
aprobaciones y evaluaciones
de desempeño.
• Personalización para mejorar
la comunicación: Mejora la
eficiencia compartiendo
calendarios de trabajo, agendas
y videoconferencias en línea
o de mensajería interna.
28. Escalabilidad
Apps para extender la funcionalidad
Extiende la Funcionalidad
• Maneja aplicaciones que se integran de
manera fácil
• Fácil navegación, comparte información
en todas las aplicaciones
• Acceso a las apps a cualquier hora y en
cualquier lugar en cualquier dispositivo
El negocio completo en la nube
o Contabilidad / Finanzas
o CRM – Comercial y Ventas
o Reclutamiento
o Administración de Proyectos
o Firma electrónica de documentos
o Mucho más...
30. Manejo de información en tiempo real
100 % en línea, 100 % customizables
• Manejo de cantidades extendidas de datos con páginas Visualforce
• Agrupación jerárquica de datos en formato expandible
• Capacidad de sorteo y filtrado dinámico, agrupación por otros criterios
(usuarios, período)
31. Integración de mapas interactivos Google Maps
Dentro de los detalles de las oportunidades comerciales
• Despliegue de información visual en el CRM y el sitio web
33. Automatización de tareas
Hojas de cálculo, interfases, consolidación y más
- Automatiza aprobaciones de gastos, seguimiento a registro de horas
trabajadas, manejo de órdenes, aprobación en toma de pedidos.
- Hojas de cálculo dinámicas
conectadas con aplicaciones
externas
- Análisis de hojas de cálculo
con formato customizado
- Interfases gráficas de menus e
interfases de usuarios.
- Automatización de procesos de
resurtido.
- Formas de captura dinámica de
datos conectadas con aplicaciones
externas.
- Consolidación de resultados de
manera automática, paneles de
visualización de indicadores clave.
34. Aplicaciones customizadas
Para extender el alcance de sistemas legacy
Extensión de Apps Apps Móviles Apps Sociales
Core Edge
Apps App
Apps Colaboración social para
departamentales Apps móviles empleados y clientes
Apps conectadas con Apps para Información en tiempo
sistemas legacy, navegadores móviles real
ERPs, sitios web
Compatibles con Visualiza conversaciones
Diseñadas por cualquier dispositivo en el contexto de eventos
usuarios finales de negocio
35. Análisis de datos en iPads
A una fracción del costo de otras
plataformas provee una manera segura de
analizar datos y facilita la búsqueda de
información desde cualquier dispositivo.
36. Caso de éxito
> Resúmen
SERH requería una solución para eficientar sus operaciones, infraestructura de mensajería, reporteo a
Dirección, y su proceso de reclutamiento.
> Solución
• Migración a la plataforma de Google Apps para uso de correo corporativo, documentos en línea,
sitio web e intranet para reporteo de indicadores en tiempo real
• Implementación de CRM para consolidar información de clientes y oportunidades
comerciales
• Implementación de Recruit para la automatización del proceso de reclutamiento en línea e
integración con el sitio web
> Beneficios
• Mejor control administrativo, centralización de la información
• Flujo de trabajo integrado
• Automatización del proceso de reclutamiento
37. Resúmen: El panorama actual
• Muchas empresas ya consideran los servicios cloud como
parte de su estrategia y la adopción continua creciendo.
• Cloud computing es un medio para lograr beneficios
para los negocios, no sólamente ahorros através
de eficiencias
• La estrategia de la nube esta cambiando la filosofía
de cómo los servicios de información están siendo
provistos y utilizados
• Los sectores en las industrias varían en la adopción
• Convergencia creciente: móvil + social + cloud
38. Resúmen: Permite trabajar virtualmente en
cualquier lugar a cualquier hora
• Acceso a la información fuera de la oficina
• Habilidad de seleccionar el área de trabajo
• Independencia a restricciones de TI
• Usuarios toman decisiones de TI
• Habilidad de seleccionar los dispositivos
• Horas flexibles y productividad
39. Resúmen: La colaboración y reducción en la
verticalidad de las comunicaciones
• Existencia de silos que dificulta
• Redes sociales privadas
el manejo de información
• Plataformas cloud permiten la
• Sistemas legacy que no
colaboración en tiempo real
promueven la colaboración
• Capacidades móviles nativas
• Bajo nivel de capacidad móvil
40. Resúmen: Promueve la participación de los
usuarios
• Decisiones de TI realizada • Decisiones tomadas por
por un grupo selecto los usuarios de las tecnologías
• Area de TI: soporte y • IT provee los estandares y
mantenimiento direccionamiento
• Períodos extendidos para • Usuarios solicitan e
obtener soluciones o apps implementan soluciones
41. Resúmen: El significado potencial de cloud
computing
Reducción potencial en ..
• Gastos de TI no diferenciados
• Licenciamiento en hw y sw
• Energía, espacio y mtto para centros de datos
• Uso ineficiente de recursos de TI
Incremento potencial en ..
• Enfoque en los procesos core del negocio
• Flexibilidad para atender las necesidades de los negocios
• Escalabilidad para responder a las demandasd e capacidad
• Oportunidades de integración con socios de negocio
• Habilidad de analizar nuevos tipos de información de clientes
e innovar para impulsar el crecimiento
Info World article Synchronization Options Several synchronization options are available: Direction – The default is to synchronize information bi-directionally so updates made to one calendar automatically update the other. In some circumstances you may wish to only have information be updated in one direction (e.g., updates only flow from Google to Salesforce). Frequency – How often a background synchronization is run. More frequent synchronizations will result in more up to date information. Google Calendar – Google allows you to setup multiple calendars (e.g., my work calendar, my class schedule, etc.). You must choose one of these calendars to synchronize information with. Notifications – The Google and Salesforce calendars have a number of incompatibilities (see Known Issues). For example Google support class schedule recurrences (occurs every Tues/Thurs or Mon/Wed/Fri) and Salesforce does not. Calendar events that utilize any of the incompatible features will not be synchronized. Receiving notifications sends you email when events cannot be synchronized. Notifications can be turned on and off at your discretion without interrupting the synchronization process. Conflicts – These settings determine how conflicting event updates are handled. A conflict happens when the same calendar event is changed in both Salesforce and Google within the same synchronization period. If Most recent update is selected, the last change is synchronized, the other change discarded. Selecting Salesforce or Google means that the selected system is always used as the synchronization source in a conflict. Note that if the same event is deleted in one system and updated in another, the event is deleted from both systems. Multiple Synchronizations You can create up to 3 independent synchronizations. This can be used to merge multiple Google calendars into Salesforce, or to publish a Salesforce calendar into multiple Google calendars. The product prevents the creation of synchronization “loops” - defined as a calendar that is used as both a source and target. For example, you cannot create a synchronization from Salesforce to Google Calendar 1, then from Google Calendar 1 to Salesforce again. Instead you would create a single bi-directional synchronization between the two. discussing sf - http://www.infoworld.com/d/cloud-computing/google-salesforcecom-join-forces-business-apps-333
Info World article Synchronization Options Several synchronization options are available: Direction – The default is to synchronize information bi-directionally so updates made to one calendar automatically update the other. In some circumstances you may wish to only have information be updated in one direction (e.g., updates only flow from Google to Salesforce). Frequency – How often a background synchronization is run. More frequent synchronizations will result in more up to date information. Google Calendar – Google allows you to setup multiple calendars (e.g., my work calendar, my class schedule, etc.). You must choose one of these calendars to synchronize information with. Notifications – The Google and Salesforce calendars have a number of incompatibilities (see Known Issues). For example Google support class schedule recurrences (occurs every Tues/Thurs or Mon/Wed/Fri) and Salesforce does not. Calendar events that utilize any of the incompatible features will not be synchronized. Receiving notifications sends you email when events cannot be synchronized. Notifications can be turned on and off at your discretion without interrupting the synchronization process. Conflicts – These settings determine how conflicting event updates are handled. A conflict happens when the same calendar event is changed in both Salesforce and Google within the same synchronization period. If Most recent update is selected, the last change is synchronized, the other change discarded. Selecting Salesforce or Google means that the selected system is always used as the synchronization source in a conflict. Note that if the same event is deleted in one system and updated in another, the event is deleted from both systems. Multiple Synchronizations You can create up to 3 independent synchronizations. This can be used to merge multiple Google calendars into Salesforce, or to publish a Salesforce calendar into multiple Google calendars. The product prevents the creation of synchronization “loops” - defined as a calendar that is used as both a source and target. For example, you cannot create a synchronization from Salesforce to Google Calendar 1, then from Google Calendar 1 to Salesforce again. Instead you would create a single bi-directional synchronization between the two. discussing sf - http://www.infoworld.com/d/cloud-computing/google-salesforcecom-join-forces-business-apps-333
Info World article Synchronization Options Several synchronization options are available: Direction – The default is to synchronize information bi-directionally so updates made to one calendar automatically update the other. In some circumstances you may wish to only have information be updated in one direction (e.g., updates only flow from Google to Salesforce). Frequency – How often a background synchronization is run. More frequent synchronizations will result in more up to date information. Google Calendar – Google allows you to setup multiple calendars (e.g., my work calendar, my class schedule, etc.). You must choose one of these calendars to synchronize information with. Notifications – The Google and Salesforce calendars have a number of incompatibilities (see Known Issues). For example Google support class schedule recurrences (occurs every Tues/Thurs or Mon/Wed/Fri) and Salesforce does not. Calendar events that utilize any of the incompatible features will not be synchronized. Receiving notifications sends you email when events cannot be synchronized. Notifications can be turned on and off at your discretion without interrupting the synchronization process. Conflicts – These settings determine how conflicting event updates are handled. A conflict happens when the same calendar event is changed in both Salesforce and Google within the same synchronization period. If Most recent update is selected, the last change is synchronized, the other change discarded. Selecting Salesforce or Google means that the selected system is always used as the synchronization source in a conflict. Note that if the same event is deleted in one system and updated in another, the event is deleted from both systems. Multiple Synchronizations You can create up to 3 independent synchronizations. This can be used to merge multiple Google calendars into Salesforce, or to publish a Salesforce calendar into multiple Google calendars. The product prevents the creation of synchronization “loops” - defined as a calendar that is used as both a source and target. For example, you cannot create a synchronization from Salesforce to Google Calendar 1, then from Google Calendar 1 to Salesforce again. Instead you would create a single bi-directional synchronization between the two. discussing sf - http://www.infoworld.com/d/cloud-computing/google-salesforcecom-join-forces-business-apps-333
Key Message: Google applications are built on the "cloud computing" paradigm where applications are run in third party data centers (aka "the cloud") and delivered to any device through a Web Browser via HTML5. Talking Points: Applications will be managed by third parties in outside data centers. This model is generally referred to as "cloud computing" or Software-as-a-Service. The general point is that customers are no longer responsible for managing software, hardware, upgrades, etc. That is all managed by the vendor. Applications are delivered over the Internet and accessed in a web browser. This is a critical point. With the proliferation of devices, these standards allow any application to be easily accessible from any device on the network. Cloud computing allows customer to take advantage of the scale and pace of innovation of the provider. Providers like Google have huge economies of scale that increase reliability and reduce cost. Google has a pace of innovation that vastly outstrips the more traditional installed software model. Transition: We created a version of Google Apps specifically intended for business called Google Apps Premier Edition.
Introduction : Google Apps has a track record of fast, continuous improvement In 2008, there were 68 features releases alone. There’s already been 40 in 2009, so the pace is increasing. - None of these improvements added cost, and required no work on the part of our customers to implement. Note that changes are presented and managed so users can adjust and IT organizations are not taken by surprise. For instance, administrators can choose to deploy or not deploy releases such as Google Sites. You keep getting a better product, and retain control. Transition: In addition to providing a platform for Google to provide innovation, Apps also enables your users to be more innovative.
Introduction : Google Apps has a track record of fast, continuous improvement In 2008, there were 68 features releases alone. There’s already been 40 in 2009, so the pace is increasing. - None of these improvements added cost, and required no work on the part of our customers to implement. Note that changes are presented and managed so users can adjust and IT organizations are not taken by surprise. For instance, administrators can choose to deploy or not deploy releases such as Google Sites. You keep getting a better product, and retain control. Transition: In addition to providing a platform for Google to provide innovation, Apps also enables your users to be more innovative.
Key Message: The challenges we face in the workplace are changing. Talking Points: Information is exploding, and dealing with that is very difficult. Many of our technologies are just automated versions of what we used to do. We need technology that re-thinks managing information in this new age. The concept of manually filing emails or documents into folders simply does not scale given the volume of information we deal with today. Collaboration is central to what we do. Most of our technology today was really designed for personal productivity. One person, one task. Google started with the assumption of multi-user collaboration. Today, almost all of our work involves collaborating: across functional organizations, with colleagues around the world, and with external partners. Our tools need to support this. Finally, people have access to the internet everywhere, and they expect to have their data available. From smart phones to hotel kiosks, users are used to having internet almost all the time. And all of their consumer tools are waiting there for them. Why is getting to corporate information harder than getting to Facebook? All of Google's apps are available for mobile devices, and can be accessed from any machine with an internet connection. Taking your data with you no longer requires a thumb-drive or CD accessing it does not requires a VPN. Transition: Let's look at a few examples of how these challenges present themselves to users and businesses today.
Introduction : Google Apps has a track record of fast, continuous improvement In 2008, there were 68 features releases alone. There’s already been 40 in 2009, so the pace is increasing. - None of these improvements added cost, and required no work on the part of our customers to implement. Note that changes are presented and managed so users can adjust and IT organizations are not taken by surprise. For instance, administrators can choose to deploy or not deploy releases such as Google Sites. You keep getting a better product, and retain control. Transition: In addition to providing a platform for Google to provide innovation, Apps also enables your users to be more innovative.
Before Salesforce, our customers all had a common problem. When their customers wanted customer service and an answer to their question, they don ’t want to pick up the phone today. Instead, they jump onto Google and type in their question. Or they go to Twitter to reach out to the community for an answer. They are looking for faster ways than sitting on hold on the phone with someone that may not have the right answer. Unfortunately, yestersday ’s call centers don’t work with Google, Twitter, Facebook or community sites. Companies are struggling with how to bridge the gap between their existing call center technology and The Cloud, where their customers are today.
Introduction : Google Apps has a track record of fast, continuous improvement In 2008, there were 68 features releases alone. There’s already been 40 in 2009, so the pace is increasing. - None of these improvements added cost, and required no work on the part of our customers to implement. Note that changes are presented and managed so users can adjust and IT organizations are not taken by surprise. For instance, administrators can choose to deploy or not deploy releases such as Google Sites. You keep getting a better product, and retain control. Transition: In addition to providing a platform for Google to provide innovation, Apps also enables your users to be more innovative.
Info World article Synchronization Options Several synchronization options are available: Direction – The default is to synchronize information bi-directionally so updates made to one calendar automatically update the other. In some circumstances you may wish to only have information be updated in one direction (e.g., updates only flow from Google to Salesforce). Frequency – How often a background synchronization is run. More frequent synchronizations will result in more up to date information. Google Calendar – Google allows you to setup multiple calendars (e.g., my work calendar, my class schedule, etc.). You must choose one of these calendars to synchronize information with. Notifications – The Google and Salesforce calendars have a number of incompatibilities (see Known Issues). For example Google support class schedule recurrences (occurs every Tues/Thurs or Mon/Wed/Fri) and Salesforce does not. Calendar events that utilize any of the incompatible features will not be synchronized. Receiving notifications sends you email when events cannot be synchronized. Notifications can be turned on and off at your discretion without interrupting the synchronization process. Conflicts – These settings determine how conflicting event updates are handled. A conflict happens when the same calendar event is changed in both Salesforce and Google within the same synchronization period. If Most recent update is selected, the last change is synchronized, the other change discarded. Selecting Salesforce or Google means that the selected system is always used as the synchronization source in a conflict. Note that if the same event is deleted in one system and updated in another, the event is deleted from both systems. Multiple Synchronizations You can create up to 3 independent synchronizations. This can be used to merge multiple Google calendars into Salesforce, or to publish a Salesforce calendar into multiple Google calendars. The product prevents the creation of synchronization “loops” - defined as a calendar that is used as both a source and target. For example, you cannot create a synchronization from Salesforce to Google Calendar 1, then from Google Calendar 1 to Salesforce again. Instead you would create a single bi-directional synchronization between the two. discussing sf - http://www.infoworld.com/d/cloud-computing/google-salesforcecom-join-forces-business-apps-333
Info World article Synchronization Options Several synchronization options are available: Direction – The default is to synchronize information bi-directionally so updates made to one calendar automatically update the other. In some circumstances you may wish to only have information be updated in one direction (e.g., updates only flow from Google to Salesforce). Frequency – How often a background synchronization is run. More frequent synchronizations will result in more up to date information. Google Calendar – Google allows you to setup multiple calendars (e.g., my work calendar, my class schedule, etc.). You must choose one of these calendars to synchronize information with. Notifications – The Google and Salesforce calendars have a number of incompatibilities (see Known Issues). For example Google support class schedule recurrences (occurs every Tues/Thurs or Mon/Wed/Fri) and Salesforce does not. Calendar events that utilize any of the incompatible features will not be synchronized. Receiving notifications sends you email when events cannot be synchronized. Notifications can be turned on and off at your discretion without interrupting the synchronization process. Conflicts – These settings determine how conflicting event updates are handled. A conflict happens when the same calendar event is changed in both Salesforce and Google within the same synchronization period. If Most recent update is selected, the last change is synchronized, the other change discarded. Selecting Salesforce or Google means that the selected system is always used as the synchronization source in a conflict. Note that if the same event is deleted in one system and updated in another, the event is deleted from both systems. Multiple Synchronizations You can create up to 3 independent synchronizations. This can be used to merge multiple Google calendars into Salesforce, or to publish a Salesforce calendar into multiple Google calendars. The product prevents the creation of synchronization “loops” - defined as a calendar that is used as both a source and target. For example, you cannot create a synchronization from Salesforce to Google Calendar 1, then from Google Calendar 1 to Salesforce again. Instead you would create a single bi-directional synchronization between the two. discussing sf - http://www.infoworld.com/d/cloud-computing/google-salesforcecom-join-forces-business-apps-333
Introduction : Google Apps has a track record of fast, continuous improvement In 2008, there were 68 features releases alone. There’s already been 40 in 2009, so the pace is increasing. - None of these improvements added cost, and required no work on the part of our customers to implement. Note that changes are presented and managed so users can adjust and IT organizations are not taken by surprise. For instance, administrators can choose to deploy or not deploy releases such as Google Sites. You keep getting a better product, and retain control. Transition: In addition to providing a platform for Google to provide innovation, Apps also enables your users to be more innovative.
Introduction : Google Apps has a track record of fast, continuous improvement In 2008, there were 68 features releases alone. There’s already been 40 in 2009, so the pace is increasing. - None of these improvements added cost, and required no work on the part of our customers to implement. Note that changes are presented and managed so users can adjust and IT organizations are not taken by surprise. For instance, administrators can choose to deploy or not deploy releases such as Google Sites. You keep getting a better product, and retain control. Transition: In addition to providing a platform for Google to provide innovation, Apps also enables your users to be more innovative.
Info World article Synchronization Options Several synchronization options are available: Direction – The default is to synchronize information bi-directionally so updates made to one calendar automatically update the other. In some circumstances you may wish to only have information be updated in one direction (e.g., updates only flow from Google to Salesforce). Frequency – How often a background synchronization is run. More frequent synchronizations will result in more up to date information. Google Calendar – Google allows you to setup multiple calendars (e.g., my work calendar, my class schedule, etc.). You must choose one of these calendars to synchronize information with. Notifications – The Google and Salesforce calendars have a number of incompatibilities (see Known Issues). For example Google support class schedule recurrences (occurs every Tues/Thurs or Mon/Wed/Fri) and Salesforce does not. Calendar events that utilize any of the incompatible features will not be synchronized. Receiving notifications sends you email when events cannot be synchronized. Notifications can be turned on and off at your discretion without interrupting the synchronization process. Conflicts – These settings determine how conflicting event updates are handled. A conflict happens when the same calendar event is changed in both Salesforce and Google within the same synchronization period. If Most recent update is selected, the last change is synchronized, the other change discarded. Selecting Salesforce or Google means that the selected system is always used as the synchronization source in a conflict. Note that if the same event is deleted in one system and updated in another, the event is deleted from both systems. Multiple Synchronizations You can create up to 3 independent synchronizations. This can be used to merge multiple Google calendars into Salesforce, or to publish a Salesforce calendar into multiple Google calendars. The product prevents the creation of synchronization “loops” - defined as a calendar that is used as both a source and target. For example, you cannot create a synchronization from Salesforce to Google Calendar 1, then from Google Calendar 1 to Salesforce again. Instead you would create a single bi-directional synchronization between the two. discussing sf - http://www.infoworld.com/d/cloud-computing/google-salesforcecom-join-forces-business-apps-333
Info World article Synchronization Options Several synchronization options are available: Direction – The default is to synchronize information bi-directionally so updates made to one calendar automatically update the other. In some circumstances you may wish to only have information be updated in one direction (e.g., updates only flow from Google to Salesforce). Frequency – How often a background synchronization is run. More frequent synchronizations will result in more up to date information. Google Calendar – Google allows you to setup multiple calendars (e.g., my work calendar, my class schedule, etc.). You must choose one of these calendars to synchronize information with. Notifications – The Google and Salesforce calendars have a number of incompatibilities (see Known Issues). For example Google support class schedule recurrences (occurs every Tues/Thurs or Mon/Wed/Fri) and Salesforce does not. Calendar events that utilize any of the incompatible features will not be synchronized. Receiving notifications sends you email when events cannot be synchronized. Notifications can be turned on and off at your discretion without interrupting the synchronization process. Conflicts – These settings determine how conflicting event updates are handled. A conflict happens when the same calendar event is changed in both Salesforce and Google within the same synchronization period. If Most recent update is selected, the last change is synchronized, the other change discarded. Selecting Salesforce or Google means that the selected system is always used as the synchronization source in a conflict. Note that if the same event is deleted in one system and updated in another, the event is deleted from both systems. Multiple Synchronizations You can create up to 3 independent synchronizations. This can be used to merge multiple Google calendars into Salesforce, or to publish a Salesforce calendar into multiple Google calendars. The product prevents the creation of synchronization “loops” - defined as a calendar that is used as both a source and target. For example, you cannot create a synchronization from Salesforce to Google Calendar 1, then from Google Calendar 1 to Salesforce again. Instead you would create a single bi-directional synchronization between the two. discussing sf - http://www.infoworld.com/d/cloud-computing/google-salesforcecom-join-forces-business-apps-333
Info World article Synchronization Options Several synchronization options are available: Direction – The default is to synchronize information bi-directionally so updates made to one calendar automatically update the other. In some circumstances you may wish to only have information be updated in one direction (e.g., updates only flow from Google to Salesforce). Frequency – How often a background synchronization is run. More frequent synchronizations will result in more up to date information. Google Calendar – Google allows you to setup multiple calendars (e.g., my work calendar, my class schedule, etc.). You must choose one of these calendars to synchronize information with. Notifications – The Google and Salesforce calendars have a number of incompatibilities (see Known Issues). For example Google support class schedule recurrences (occurs every Tues/Thurs or Mon/Wed/Fri) and Salesforce does not. Calendar events that utilize any of the incompatible features will not be synchronized. Receiving notifications sends you email when events cannot be synchronized. Notifications can be turned on and off at your discretion without interrupting the synchronization process. Conflicts – These settings determine how conflicting event updates are handled. A conflict happens when the same calendar event is changed in both Salesforce and Google within the same synchronization period. If Most recent update is selected, the last change is synchronized, the other change discarded. Selecting Salesforce or Google means that the selected system is always used as the synchronization source in a conflict. Note that if the same event is deleted in one system and updated in another, the event is deleted from both systems. Multiple Synchronizations You can create up to 3 independent synchronizations. This can be used to merge multiple Google calendars into Salesforce, or to publish a Salesforce calendar into multiple Google calendars. The product prevents the creation of synchronization “loops” - defined as a calendar that is used as both a source and target. For example, you cannot create a synchronization from Salesforce to Google Calendar 1, then from Google Calendar 1 to Salesforce again. Instead you would create a single bi-directional synchronization between the two. discussing sf - http://www.infoworld.com/d/cloud-computing/google-salesforcecom-join-forces-business-apps-333
Info World article Synchronization Options Several synchronization options are available: Direction – The default is to synchronize information bi-directionally so updates made to one calendar automatically update the other. In some circumstances you may wish to only have information be updated in one direction (e.g., updates only flow from Google to Salesforce). Frequency – How often a background synchronization is run. More frequent synchronizations will result in more up to date information. Google Calendar – Google allows you to setup multiple calendars (e.g., my work calendar, my class schedule, etc.). You must choose one of these calendars to synchronize information with. Notifications – The Google and Salesforce calendars have a number of incompatibilities (see Known Issues). For example Google support class schedule recurrences (occurs every Tues/Thurs or Mon/Wed/Fri) and Salesforce does not. Calendar events that utilize any of the incompatible features will not be synchronized. Receiving notifications sends you email when events cannot be synchronized. Notifications can be turned on and off at your discretion without interrupting the synchronization process. Conflicts – These settings determine how conflicting event updates are handled. A conflict happens when the same calendar event is changed in both Salesforce and Google within the same synchronization period. If Most recent update is selected, the last change is synchronized, the other change discarded. Selecting Salesforce or Google means that the selected system is always used as the synchronization source in a conflict. Note that if the same event is deleted in one system and updated in another, the event is deleted from both systems. Multiple Synchronizations You can create up to 3 independent synchronizations. This can be used to merge multiple Google calendars into Salesforce, or to publish a Salesforce calendar into multiple Google calendars. The product prevents the creation of synchronization “loops” - defined as a calendar that is used as both a source and target. For example, you cannot create a synchronization from Salesforce to Google Calendar 1, then from Google Calendar 1 to Salesforce again. Instead you would create a single bi-directional synchronization between the two. discussing sf - http://www.infoworld.com/d/cloud-computing/google-salesforcecom-join-forces-business-apps-333
Introduction : Google Apps has a track record of fast, continuous improvement In 2008, there were 68 features releases alone. There’s already been 40 in 2009, so the pace is increasing. - None of these improvements added cost, and required no work on the part of our customers to implement. Note that changes are presented and managed so users can adjust and IT organizations are not taken by surprise. For instance, administrators can choose to deploy or not deploy releases such as Google Sites. You keep getting a better product, and retain control. Transition: In addition to providing a platform for Google to provide innovation, Apps also enables your users to be more innovative.
CNS Response. Sharing the secrets of the human brain. Mark Desrosiers, SVP, commercial operations: “We’re using Force.com to run our entire production platform. We needed a scalable, reliable, and secure environment. Force.com was the only tool that could actually do it—and at a fraction of the cost of other solutions.” What if mental illness could be diagnosed as easily as a broken arm or leg? CNS Response, a company headquartered in Aliso Viejo, CA, developed an assessment tool, known as Referenced-EEG (rEEG®), that uses objective, physiological data to help physicians better treat psychiatric disorders, much the same way x-rays or blood tests are used in general medicine. To grow its business, CNS Response needed a secure, scalable, and reliable way to integrate and share data between custom data systems and partner physicians, technicians, and neurologists. It also wanted a way to organize workflows, capture and store data, and present results in an easy-to-use format for physicians and patients. An existing Salesforce customer, CNS Response decided to build what it needed on the Force.com cloud platform because it could develop robust, on-demand applications at significantly reduced development costs. The applications could also be tailored to its precise business needs. For example, a custom production application gathers information about patients in one place and workflows ensure the information flows among physicians, technicians, and neurologists. Custom applications are enhanced by built-in functionality of the Force.com platform. For example, CNS Response modified the customer portal to manage patient data, including medications and technician visits. A combination of Force.com's programmable logic and pages, .Net, and HTML lets the CNS Response store information in one centralized location and present it, as needed, to stakeholders. With Force.com's straightforward integration, CNS was able to link a custom technicians’ portal built on .NET to Force.com for secure access to testing schedules and data upload. A SQL database stores proprietary Referenced-EEG (rEEG®) which is accessed via the Force.com API. CNS also integrated the company's outcomes database and proprietary laboratory system, so physicians can securely access patient reports. Force.com delivered results quickly and at significant cost savings. In 4 months, CNS Response built a complete production system and moved its production processes onto the platform. It estimated that developing on Force.com cost only 25 percent of what it would have cost to build the same solution using .Net or Java. The new system provided an end-to-end solution for managing customer data and workflows. Production time decreased significantly, and test processing shrank from 3 days to 24 hours. “ We’re using Force.com to run our entire production platform,” said Mark Desrosiers, svp of commercial operations. “We needed a scalable, reliable, and secure environment. Force.com was the only tool that could actually do it—and at a fraction of the cost of other solutions.” BENEFITS • Developed and deployed complete production system in 4 months Cost only 25 percent of what it would have cost to build using .NET or Java Reduced test processing time from 3 days to 24 hours
Info World article Synchronization Options Several synchronization options are available: Direction – The default is to synchronize information bi-directionally so updates made to one calendar automatically update the other. In some circumstances you may wish to only have information be updated in one direction (e.g., updates only flow from Google to Salesforce). Frequency – How often a background synchronization is run. More frequent synchronizations will result in more up to date information. Google Calendar – Google allows you to setup multiple calendars (e.g., my work calendar, my class schedule, etc.). You must choose one of these calendars to synchronize information with. Notifications – The Google and Salesforce calendars have a number of incompatibilities (see Known Issues). For example Google support class schedule recurrences (occurs every Tues/Thurs or Mon/Wed/Fri) and Salesforce does not. Calendar events that utilize any of the incompatible features will not be synchronized. Receiving notifications sends you email when events cannot be synchronized. Notifications can be turned on and off at your discretion without interrupting the synchronization process. Conflicts – These settings determine how conflicting event updates are handled. A conflict happens when the same calendar event is changed in both Salesforce and Google within the same synchronization period. If Most recent update is selected, the last change is synchronized, the other change discarded. Selecting Salesforce or Google means that the selected system is always used as the synchronization source in a conflict. Note that if the same event is deleted in one system and updated in another, the event is deleted from both systems. Multiple Synchronizations You can create up to 3 independent synchronizations. This can be used to merge multiple Google calendars into Salesforce, or to publish a Salesforce calendar into multiple Google calendars. The product prevents the creation of synchronization “loops” - defined as a calendar that is used as both a source and target. For example, you cannot create a synchronization from Salesforce to Google Calendar 1, then from Google Calendar 1 to Salesforce again. Instead you would create a single bi-directional synchronization between the two. discussing sf - http://www.infoworld.com/d/cloud-computing/google-salesforcecom-join-forces-business-apps-333
Info World article Synchronization Options Several synchronization options are available: Direction – The default is to synchronize information bi-directionally so updates made to one calendar automatically update the other. In some circumstances you may wish to only have information be updated in one direction (e.g., updates only flow from Google to Salesforce). Frequency – How often a background synchronization is run. More frequent synchronizations will result in more up to date information. Google Calendar – Google allows you to setup multiple calendars (e.g., my work calendar, my class schedule, etc.). You must choose one of these calendars to synchronize information with. Notifications – The Google and Salesforce calendars have a number of incompatibilities (see Known Issues). For example Google support class schedule recurrences (occurs every Tues/Thurs or Mon/Wed/Fri) and Salesforce does not. Calendar events that utilize any of the incompatible features will not be synchronized. Receiving notifications sends you email when events cannot be synchronized. Notifications can be turned on and off at your discretion without interrupting the synchronization process. Conflicts – These settings determine how conflicting event updates are handled. A conflict happens when the same calendar event is changed in both Salesforce and Google within the same synchronization period. If Most recent update is selected, the last change is synchronized, the other change discarded. Selecting Salesforce or Google means that the selected system is always used as the synchronization source in a conflict. Note that if the same event is deleted in one system and updated in another, the event is deleted from both systems. Multiple Synchronizations You can create up to 3 independent synchronizations. This can be used to merge multiple Google calendars into Salesforce, or to publish a Salesforce calendar into multiple Google calendars. The product prevents the creation of synchronization “loops” - defined as a calendar that is used as both a source and target. For example, you cannot create a synchronization from Salesforce to Google Calendar 1, then from Google Calendar 1 to Salesforce again. Instead you would create a single bi-directional synchronization between the two. discussing sf - http://www.infoworld.com/d/cloud-computing/google-salesforcecom-join-forces-business-apps-333
Info World article Synchronization Options Several synchronization options are available: Direction – The default is to synchronize information bi-directionally so updates made to one calendar automatically update the other. In some circumstances you may wish to only have information be updated in one direction (e.g., updates only flow from Google to Salesforce). Frequency – How often a background synchronization is run. More frequent synchronizations will result in more up to date information. Google Calendar – Google allows you to setup multiple calendars (e.g., my work calendar, my class schedule, etc.). You must choose one of these calendars to synchronize information with. Notifications – The Google and Salesforce calendars have a number of incompatibilities (see Known Issues). For example Google support class schedule recurrences (occurs every Tues/Thurs or Mon/Wed/Fri) and Salesforce does not. Calendar events that utilize any of the incompatible features will not be synchronized. Receiving notifications sends you email when events cannot be synchronized. Notifications can be turned on and off at your discretion without interrupting the synchronization process. Conflicts – These settings determine how conflicting event updates are handled. A conflict happens when the same calendar event is changed in both Salesforce and Google within the same synchronization period. If Most recent update is selected, the last change is synchronized, the other change discarded. Selecting Salesforce or Google means that the selected system is always used as the synchronization source in a conflict. Note that if the same event is deleted in one system and updated in another, the event is deleted from both systems. Multiple Synchronizations You can create up to 3 independent synchronizations. This can be used to merge multiple Google calendars into Salesforce, or to publish a Salesforce calendar into multiple Google calendars. The product prevents the creation of synchronization “loops” - defined as a calendar that is used as both a source and target. For example, you cannot create a synchronization from Salesforce to Google Calendar 1, then from Google Calendar 1 to Salesforce again. Instead you would create a single bi-directional synchronization between the two. discussing sf - http://www.infoworld.com/d/cloud-computing/google-salesforcecom-join-forces-business-apps-333