5 Comment choisir sa solution de Workflows
•Transferir como PPTX, PDF•
1 gostou•192 visualizações
Lors de L'ESPC (European SharePoint Conference) 2014, seules 2 ou 3 solutions s'affichaient pour proposer de réaliser du Workflow sur Sharepoint. Lors de l'ESPC 2016, nous pouvons en compter une bonne dizaine ! Architecture, complexité de Workflow, Formulaire, Mobilité, Cloud, connecteurs... Tant de service qui diffèrent au cœur de ces solutions, nous tenterons d'en faire le tour pour que vous puissiez y voir plus clair dans cette jungle!
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (14)
Semelhante a 5 Comment choisir sa solution de Workflows
Semelhante a 5 Comment choisir sa solution de Workflows (20)
Mais de aOS Community
Mais de aOS Community (20)
5 Comment choisir sa solution de Workflows
- 1. aOS Toulouse 20 juin 2017 Choisir sa solution de workflow AlexSharepoint
- 2. aOS Toulouse 20 juin 2017 Présentation du conférencier • Alexandre Joly • CEO HubCollab • 3 ans Technical Evangelist @Nintex • 3 ans Responsable Centre d’expertise MS/Sharepoint Sogeti • 15 ans sur Sharepoint • Codeur (il fut un temps…) • Adepte des solutions NoCode/LowCode • Local de l’étape AOS AlexSharepoint
- 3. aOS Grenoble 22 mai 2017 Quel type de workflow pour votre entreprise?
- 5. Les types de processus métier
- 6. Les types de processus métier
- 7. ERP BPM WCA (workflow and Content Automation) Solution de productivité personnelle Les types de processus métier
- 8. ERP BPM WCA (workflow and Content Automation) Solution de productivité personnelle Les types de processus métier
- 9. ERP BPM WCA (workflow and Content Automation) Solution de productivité personnelle Les types de processus métier
- 10. aOS Grenoble 22 mai 2017 Quel type de plate-forme? AlexSharepoint
- 11. aOS Toulouse 20 juin 2017
- 12. aOS Toulouse 20 juin 2017 La puissance du moteur? • Processus complexes • A la miliseconde • Large masse de données => Solutions BPM • Process opérationnels … • Process personnels …
- 13. ERP BPM WCA (workflow and Content Automation) Solution de productivité personnelle Les types de processus métier
- 14. aOS Toulouse 20 juin 2017 Qui a la compétence des workflows? • Qui est le plus capable de concevoir un workflow? • Vos utilisateurs doivent-ils travailler sur les workflows? • Qui va maintenir les workflows? A quelle fréquence? • Connaissent-ils les normes? Complexité de prise en main de la solution Niveau d’expertise nécessaire Coût de développement Réactivité / Agilité
- 15. aOS Toulouse 20 juin 2017 Qui pilote? •Les métiers • Solution rapide • ROI Rapide (Retour sur investissement) • Ne pas être limité par l’IT • Coût maitrisé. •L’IT • Maitrise des coûts • Compliance • Répondre rapidement aux besoins des métiers • Sécuriser sa plate-forme • Augmenter son catalogue de services • Ne plus être goulot d’étranglement
- 16. aOS Toulouse 20 juin 2017 Quel est la source de données ? • SQL • Sharepoint • O365 • Azure • CRM / ERP • Autres.. Est-ce que Sharepoint/O365 est bien votre cible?
- 17. aOS Toulouse 20 juin 2017 A quels services doivent se connecter les workflows ? • Service tiers (WebService) • SAP • O365 • SalesForce / Dynamics CRM • Facebook / Twitter / Linkedin • Box / OneDrive / DropBox Evolutivité des interfaces
- 18. aOS Toulouse 20 juin 2017 Quel modèle de prix? • Prédictif / Non-prédictif • CAPEX : • A la plate-forme • Aux serveur • OPEX : A la souscription • A l’itération • Au workflow • Que payerez vous? La production? La preproduction? l’intégration?
- 19. aOS Toulouse 20 juin 2017 Cloud / On-Premise / Hybride? • Solutions On-Premise sur Infrastructure dédiée • Solutions On-Premise hébergée sur Sharepoint • Solutions On-Premise As-A-service • Solutions Cloud sur Infrastructure dédiée • Solutions Office365 As-A-service • Solutions Cloud As-A-service • Solutions avec offres conjointes • Solutions Full cloud
- 20. aOS Toulouse 20 juin 2017 Et la mobilité? • Solutions mobiles natives • Solutions déconnectées • Solutions personnalisables • Solutions mobiles évolutives (générateurs d’apps)
- 21. aOS Toulouse 20 juin 2017 Combien ? $€£
- 22. aOS Toulouse 20 juin 2017 • Complexité de prise en main • Rapidité de développement • Mobilité • Services tiers • Ouverture aux services tiers • CAPEX / OPEX • Modèle de prix • Coût • On-Premise / Cloud • Stockages des données • Moteur de workflows Infra Prix Utilisateurs / développeursIntégration
- 23. aOS Toulouse 20 juin 2017 Merci à nos sponsors !
- 24. aOS Toulouse 20 juin 2017 Conclusion
Notas do Editor
- For years, BPM and ERP vendors have been trying to sell into the mid-market, trying to increase the agility, but downsize the TCO of their products. It hasn’t worked. Customers don’t want to wait for 6 month change cycles anymore. And think about the money they have been justifying on applications like SAP, Oracle, Lotus Notes. Hundreds of thousands of dollars per year.
- For years, BPM and ERP vendors have been trying to sell into the mid-market, trying to increase the agility, but downsize the TCO of their products. It hasn’t worked. Customers don’t want to wait for 6 month change cycles anymore. And think about the money they have been justifying on applications like SAP, Oracle, Lotus Notes. Hundreds of thousands of dollars per year.
- For years, BPM and ERP vendors have been trying to sell into the mid-market, trying to increase the agility, but downsize the TCO of their products. It hasn’t worked. Customers don’t want to wait for 6 month change cycles anymore. And think about the money they have been justifying on applications like SAP, Oracle, Lotus Notes. Hundreds of thousands of dollars per year.
- For years, BPM and ERP vendors have been trying to sell into the mid-market, trying to increase the agility, but downsize the TCO of their products. It hasn’t worked. Customers don’t want to wait for 6 month change cycles anymore. And think about the money they have been justifying on applications like SAP, Oracle, Lotus Notes. Hundreds of thousands of dollars per year.
- For years, BPM and ERP vendors have been trying to sell into the mid-market, trying to increase the agility, but downsize the TCO of their products. It hasn’t worked. Customers don’t want to wait for 6 month change cycles anymore. And think about the money they have been justifying on applications like SAP, Oracle, Lotus Notes. Hundreds of thousands of dollars per year.
- For years, BPM and ERP vendors have been trying to sell into the mid-market, trying to increase the agility, but downsize the TCO of their products. It hasn’t worked. Customers don’t want to wait for 6 month change cycles anymore. And think about the money they have been justifying on applications like SAP, Oracle, Lotus Notes. Hundreds of thousands of dollars per year.
- For years, BPM and ERP vendors have been trying to sell into the mid-market, trying to increase the agility, but downsize the TCO of their products. It hasn’t worked. Customers don’t want to wait for 6 month change cycles anymore. And think about the money they have been justifying on applications like SAP, Oracle, Lotus Notes. Hundreds of thousands of dollars per year.