Retrouvez ici tous les Posts (+ de 700) des consultants et experts du groupe Infeeny (Plus de 330 collaborateurs, pure player Microsoft).
Vous voulez en savoir plus sur Infeeny ou vous souhaitez nous rejoindre ?
Consultez notre site infeeny.com.
Vous pouvez aussi nous suivre sur :
– Twitter : @Infeeny_fr – https://twitter.com/Infeeny_fr
– LinkedIn : https://www.linkedin.com/company/infeeny
– et vous abonner à notre chaîne YouTube Infeeny !
I must admit that I was quite skeptical when I heard about this new feature earlier this year. One of the main reasons of my skepticism was that I could not find the right use case from an end-user perspective. During the Microsoft Ignite, 3 booths were available to get our hands on this new solution, so why not testing this and trying to change my mind ?
SharePoint Spaces tested by Mozzaik Team
It started with a quick introduction from Vidya who’s part of the Microsoft SharePoint Space product team. I discovered that there are already 7 webparts developed, and more to come. Microsoft teams already using this feature internally, yet I couldn’t find if it would be easy to programmatically convert or extend a webpart so they support the 3D glasses, but I guess it’ll be possible with PnP in due time.
Creating a new space is really easy, you just need to select the « New » menu in the ribbon as you would do for a new page or a list. Select from the spaces available, and you’ll have the page loading instantly. I’ve seen the organization chart demo, then the data visualization (mind blowing!!)
SharePoint Spaces Data Vizualisation
So what about the rendering ? Though it’s still at the early stage for this technology, I can really see the potential in an industrial environment, especially for the FLW (First Line Workers) when browsing the details of a piece and following a specific process which could be a « Process viewer WebPart ». And folks, that’s the key take away here : the WebParts.
SharePoint Spaces Tent with the WebPart panel opened
My skepticism relied on the absence of solid user scenarios that could justify the investment on this technology, but knowing that it relies on webPart, I can easily imagine specific webparts for supply chain processes, where you trigger the right process with the controller, and it points out the manufactured pieces and the associated steps to build the piece. Also, knowing that FLW and Product teams could share and use the same Site and interface could really benefits for the communication for the whole building process.
From a technology standpoint, it relies on BabylonJS , GLTF format for 3D scenes and models, and the HP Windows Mixed Reality for the headset and the controller.
If you want to know more about SharePoint Spaces and the mixed reality, check the Microsoft article : https://www.microsoft.com/en-us/microsoft-365/blog/2018/05/21/sharepoint-innovations-transform-content-collaboration-with-mixed-reality-and-ai/
Best intranet is about getting the work done. Users come back to intranet because it’s usefull, not because it’s beautifull
Fair point, you’d rather spend time interviewing users to get their need than producing a beautiful but very complexed intranet.
Search is one of the biggest pain points.
Definitly one of the paint points out there, and so far Modern SharePoint need an additional effort to customize it.
We should not talk about workloads or services, but more about building scenarios. Many organizations want to lock this down, and guess what ? People will find a way.
It’s all about Governance.
The flat world is crowded with SIte Collections, and THAT’S OK ! Hub Sites is now allowing the creation of Family of sites. #hubsbeforesubs
« Empower and connect every person accros organization to maximize their impact ».
Participation aux live events, Pin posts, People Cards, Geo Storage.
Un point d’attention sur le stockage des données pour l’Europe.
En avril 2015, Microsoft rachetait la société Revolution Analytics pour intégrer sa solution RRE au serveur de bases de données SQL Server. En plus des trois services historiques (Integration Services, Analysis Services, Reporting Services), est donc apparu R Services dans la version 2016 de SQL Server. Un an plus tard, pour la sortie de SQL Server 2017, le service est rebaptisé Machine Learning Services et intègre maintenant le langage Python.
Les deux langages phares de l’Open Source pour la Data Science partagent la notion de packages, c’est-à-dire de libraires apportant des fonctionnalités complémentaires et souvent indispensables.
Ainsi les packages R s’installent avec la ligne de commande :
install.packages("nomPackage")
Il est maintenant possible de jouer le code R au plus près des données (« in Database Analytics ») en l’encapsulant dans un script T-SQL.
Mais l’appel aux librairies spécifiques est conditionné… par leur présence sur le serveur !
Voici un script qui permet d’obtenir la liste des packages présents sur le serveur hébergeant ML Services :
EXEC sp_execute_external_script @language = N'R' , @script = N' pkg_list = data.frame(installed.packages()[,c(1,3,5,16,2)]) ' , @output_data_1_name = N'pkg_list' WITH RESULT SETS (( Package nvarchar(200) ,Version nvarchar(200) ,Depends nvarchar(200) ,Built nvarchar(200) ,LibPath nvarchar(200) ));
Et ci-dessous, un exemple de résultat :
Paul PETON, Microsoft MVP Artificial Intelligence
Jusqu’à maintenant la version 1806 de ConfigMgr était disponible que via un canal lent, il fallait pour cela exécuter un script PowerShell pour faire apparaître la mise à jour dans la console.
