Mölnlycke / Alejandra Ellerås | Jesper Olsson - Nordic Intranet Summit 2015-05-25
•Transferir como PPTX, PDF•
1 gostou•846 visualizações
Nordic Intranet Summit 25-26 maj 2015 Mölnlycke / Alejandra Ellerås | Jesper Olsson - Episerver and Sharepoint integration when developing an intranet Episerver 7 and Sharepoint 2013 are the main platforms used in Mölnlycke Health Care’s intranet. Find out the main benefits and setbacks when using these two systems together.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais de Summit & Friends
Mais de Summit & Friends (20)
Último
Último (20)
Mölnlycke / Alejandra Ellerås | Jesper Olsson - Nordic Intranet Summit 2015-05-25
- 2. Episerver and Sharepoint integration when developing and intranet Alejandra Ellerås Internal Digital Communications Specialist Corporate Communications Alejandra.elleras@molnlycke.com Jesper Olsson Business Application Specialist, Web IT Jesper.olsson@molnlycke.com
- 3. Agenda • Company information • Project milestones • Episerver 7 and Sharepoint • Lessons learned
- 4. The Mölnlycke Health Care story
- 5. Mölnlycke Health Care is a world-leading provider of single-use surgical and wound care products for customers, healthcare professionals and patients. What we do
- 6. 32 countries where we are present Gothenburg, Sweden Head Office Quick facts 99 1,213 7,423 % owned by Investor AB remainder by management annual global sales in MEUR (2014) employees worldwide
- 7. Manufacturing sites Sales office coverage Global HQ and R&D hub Our global footprint
- 8. Our products and innovations
- 9. Optimising wound treatment along the continuum of care Our strategic objectives Taking a leading role in preventing hospital- and community-acquired conditions Creating value with cost-effective and safe surgical solutions We strive to make a difference to customers and patients by:
- 10. Leading the way in: Managing all exuding wound healing stages Dealing with complex wounds Simplifies management of highly exuding wounds
- 11. Leading the way in: Pressure ulcer prevention Preventing radiotherapy- induced skin reactions Reducing the risk of infection
- 12. Leading the way in: Preferred fit, feel and comfort Increasing Operating Room (O.R.) efficiency No compromise in infection control
- 13. Intranet project
- 14. Jan 2014 Intranet launch Gothenburg, Sweden Head OfficeJan 2015 Episerver 7 and Sharepoint 2013 Mobile devices Integration Intranet project milestones Feb 2013 Project started
- 15. Episerver 7 and Sharepoint 2013 • Episerver CMS 7 – All information pages • Sharepoint 2013 – Document management, out of the box social features (collaboration), profile information, teamsites, search
- 17. Forum
- 18. Status updates
- 19. Hashtags
- 20. Newsfeed block • Shows a specific hashtag. • *Only certain usernames are shown. • Used mostly for management updates.
- 21. The technical stuff • EPiServer Connect for SharePoint
- 22. The technical stuff • User and editor access via groups in our Active Directory.
- 23. The technical stuff • Search
- 24. The technical stuff • Lync integration.
- 25. Pros/Cons & Lessons Learned
- 28. Lessons learned Involve field experts On-site developer Performance testing Education/training
Notas do Editor
- Responsible: Jesper We are truly a global company with presence in 32 countries around the world. This global presence was the biggest technical challenge in the project. Ower owners Investor creates the possibilities for us to plan long term which is really nice. We had a global sales above 1200 million Euros during 2014. We are more than 7000 eomplyees in total. Appriximately 50% of those work in our factories. We have more than 3400 computer accounts globally. Factory personnel can access the Intranet via workstations but they don’t have their own account.
- Responsible: Jesper Here is a map of our global presence. We have sales offices in over 30 countries and factories in nine. You don’t have to be a network geek in order to realize that this setup creates performance challanges.
- Optimise wound treatment along the continuum of care Establish a complete wound care portfolio around the patient journey – from prevention and diagnostics through to pharmacy Strengthen presence in both acute and post-acute setting Win NPWT through a disruptive business model Take a leading role in preventing hospital- and community-acquired conditions Consider broader solutions preventing key conditions (e.g. Surgical Site Infection and Pressure Ulcer Pevention) Broaden antiseptics portfolio Create value with cost-effective and safe surgical solutions Re-focus procedure packs on depth and procedure complexity to capture higher value products through Original Equipment Manufacturing (OEM) Continue conversions from reusables to single-use drapes as an entry point to other solutions Maintain our premium gloves position Consider tiered portfolio to serve different market segments
- Our range of products includes both wound care and surgical. We handle exuding wounds in all their stages, complex wounds
- Ulcer prevention, radiotherapy skin reactions and infection reduction.
- surgical.- procedure pak- OR efficiency, gloves and surgical gowns, scrubs, headgear, masks,
- Responsible: Jesper The project started in February 2013 and we launched almost a year later. The launch went very well with no major problems. This was the first time we had an intranet that was an integration between EPiServer and SharePoint. The reason why we did this integration was that many of the social features that we needed existed ”out of the box” in SharePoint 2013. So we didn’t have to develop them in EPiServer CMS. We made it possible for mobile devices to access the Intranet in January 2015. It was developed with responsive design from the start but we didn’t have a management system good enough for our mobile devices until January 2015. You don’t need to enter any user credentials on your device in order to go to the Intranet. All that you need to do is to enter a four digit code in the tool we use for mobile access (Mobile Iron).
- Responsible: Jesper You can say that the ”information pages”, i.e. News items, standard pages and such are created in EpiServer. All editorial work for the Intranet pages are being done in Epi. The only thing the editors have to use SharePoint for is document management. SharePoint is used for document storage, forums, profile information, team and project sites, search and tags (taxonomies).
- Responsible: Alejandra This is what the start page looks like The functionalities on the Start page which are connected to both Episerver and Sharepoint are: Profile information and status update Hashtag newsfeed block My project sites Management update block (which is similar to the newsfeed block) Forums Search
- Responsible: Alejandra Inside forums: we have On the episerver forum page we made a filter for the forums, the create a forum form (with links to more information on forums), you have the list of all the forums, and we have highlighted forums on the right hand side. Here it is also visible which forums are open or closed (only a few members have access to them, but they can request access) When the user clicks on the forum they are taken to the sharepoint page. This view is out of the box sharepoint 2013 for a forum. Users are able to create categories for their forums, add discussions, like and reply on others discussions. Thinking that this year one improvement will be to change the look&Feel of sharepoint to look more like the Episerver.
- Responsible: Alejandra For profile information and status updates we added a block on the start page where we included both on the start page on episerver. When you navigate to sharepoint, if you want to see yoru profile, you have to go to one screen and if yu want to do a status update, to need to navigate to another screen to add a status update.
- Responsible: Alejandra Some other social feature that we customized on episerver are status updates with the use of hashtags. We use specific hashtags on specific sections of the intranet. This example shows a block that we are now using on the start page to show product launches with the #LaunchExcellence. Limit them to latest 3 at a time. As for the sharepoint view, shows all the updates with that hashtag, number of likes,
- Responsible: Jesper I would like to give you a little deeper insight in our newsfeed block that Alejandra showed you just now. We have the possibility to make it possible to only show newsfeeds for a selected group of users if they use a specifiic hashtag. In this example you see our management newsfeed block on the start page. If one our executive team members use the hashtag #Execmanagement their post will be shown in this block. However if I use it will only be visible in my newsfeed since my user name isn’t written in the list of approved members. This functionality is very good for management updates both from a global standpoint but also for local offices. We also use it in the IT department for the hashtag #ITNews so that every IT person can share their latest information in an easy way.
- Responsible: Jesper Here you see how it looks for an editor when they want to upload documents via EPiServer’s Connect for SharePoint. You wiull see it as a ”Starting point” in Episerver. As you can see here we have created a folder structure for the editors so it will become easier for them to store their information. Note that the connection is quite basic, you can’t make it mandatory to add metadata to a document for instance. If you want that you have to upload the documents directly into SHarePoint or develop a new connection.
- Responsible: Jesper We wanted to make it as easy as possible for our local IT personnel to manage access rights for the Intranet. Here you can see two examples of how they can grant access for both editors and visitors for the site. In the background the access rights is done by groups in the AD but this is an easier and safer way to edit them.
- Responsible: Jesper As I said earlier we use SharePoint as our search engine. But our search result page is created in EPiServer. Since it is that time of the year I have searched for “salary” and you can see the results in the right hand part of the window. To the left you see some of the filters that we have so that the users can drill down further into the results. We are currently working on the search functionality in order to further improve it.
- Responsible: Jesper The Lync integration allows us to see if the page author or owner is online and get in touch with them directly and ask questions or comment. As you can see in the screen dump the image Alejandra have on the Intranet (and on SharePoint) isn’t synced to our AD is it is now. However that is something that we will implement shortly.
- Responsible: Alejandra Epi Editor friendly, easier to create static pages Reusable blocks For us- same took for both internal and external web Sharepoint 2013 Powerful document handling Out of box social functionalities More social than Epi CMS Better IT infrastructure More powerful search- compared to the episearch search
- Responsible: Alejandra Harder setup: connection and integration is harder. We had a hard job in the beginning and we had to call in a sharepoint expert to make the connection Supporting the two systems Harder setup Not making tags mandatory on pages made it hard for metadata Metadata for documents is not automatic No author as metadata Performance issues because of the systems integration Information from AD
- Responsible: Alejandra and Jespercito On site developer(s)- if you have one depeloper for both system, good to have inhouse. Feel more responsible, if you have two, have them onsite, working together as a team. Involving field experts from the beginning of the project can help avoid problems. Sharepoint expert for the integration, which assured the connection was made correctly. We learned that integration of sharepoint and epi, in regards to search, has caused some problems with metadata of docuemnts. For example. Jesper: We did quite extensive performance tests before, during and after the project and this was very useful for us. It made it possible for us to keep the pressuer on the supplier since we had hard facts regarding the performance and not only a vague feeling. Some of the problems we stumbled upon was performance problems due to the fact that we have two systems that have to talk to each other. That is one thing to think about if you want to use both Epi and SharePoint. Two systems also adds to the complexitivity when it comes to user adoption. We found it very useful to have manuals, trainings and a plan for user adoption both for editors and visitors.