Download to read offline
Uploaded byMichael Blumenthal (Microsoft MVP)
PSC Case study: SP2013 Public Facing Internet Site - Roadrunner Transportation Systems
The document presents a case study of Roadrunner Transportation Systems' transition from an aging ASP.NET site to a modern SharePoint 2013 platform to consolidate multiple subsidiary sites and business applications. The project aimed to enhance user experience through modern design and robust technical architecture, resulting in increased web traffic and improved efficiency. Key measures of success included a significant increase in page views and a reduction in exit rates post-implementation.
More Related Content
Similar to PSC Case study: SP2013 Public Facing Internet Site - Roadrunner Transportation Systems
PSC Case study: SP2013 Public Facing Internet Site - Roadrunner Transportation Systems
- 1. 2014 Case Study: SP2013Internet Site ROADRUNNER TRANSPORTATION SYSTEMS
- 2. 2014 Who are theseguys? Michael Blumenthal • Sr. Solution Architect • CSPUG Co-Leader • 19 years in IT Consulting • 11 years of SharePoint • Team member on this project Malcolm Eaton • Microsoft Practice Leader • 14 years of SharePoint • Project Leader on this project
- 3.
- 4. 2014 Agenda The business challenge Thesolution Technical Architecture & key components Team Measures of success
- 5. 2014 Roadrunner Transportation Systems •Truckload, Less-Than-Truckload, Intermodal • 2500+ Employees, 15,000+ Contractors • 30 Different Acquisitions
- 6. 2014 The Challenges Aging ASP.Netsite Consolidate 30+ Subsidiary Sites Consolidate 500+ Line of business apps Small Internal developer staff AS400 integration User Management VB.NET code base
- 7. 2014 What Did WeSee? • 32 Subsidiary Sites • 251 Pages • 49 Forms • 16 Login Methods • 32 Reports • 63 Tools • 57 Forms 5/21/2014 7
- 8. 2014 What Did WeBuild? • 15 Admin Apps • 30 Line of Business Apps • 8 SSRS Reports • 7 Web Services • 8 Service Segments Pages • 16 Company Sites 5/21/2014 8
- 9. 2014 Project Management Strategy •Frequent Status Meetings • PSC Client Portal – SharePoint 2013 • Shared OneNote Notebook • Yammer
- 10. 2014 Design • Axure PrototypingTool • Site Design Strategy • 20/20 Hindsight • Create UX Before any Development 5/21/2014 10
- 11. 2014 UX Goals • Modern • UserFriendly Tools • SharePoint ECM Features • Twitter Bootstrap • Telerik ASP.NET AJAX Controls • SSRS Reports
- 12.
- 13.
- 14.
- 17.
- 18.
- 19.
- 20.
- 21.
- 23.
- 24. 2014 HOW IT WORKS TechnicalArchitecture
- 25. 2014 Technology Overview • SharePoint2013 for Internet • Web Part Development • Solution Packages • Telerik • Twitter Bootstrap • SQL 2012 / Custom Database
- 26. 2014 Development Decisions • TraditionalSharePoint Model vs. App Model? • Authentication? • Where to store Data? 5/21/2014 26
- 27. 2014 “Traditional” SP Dev,Not SP Apps Traditional SP Dev • On Premise • Mature • Resources SP App Model • Cloud Oriented • Immature • Challenging
- 28.
- 30.
- 31. 2014 LOB APPS ANDREPORTS Demo
- 32. 2014 The A-Team • Client:2 .Net developers, 1 Team Lead, 1 manager, 1 CIO , 1 Dir of Marketing Account Exec Practice Lead Project Manager Sr. UX Designer UX Designer SP Arch Data Arch SP Devs Tester
- 33. 2014 Measures of success •700 Bills Of Lading/day • Increased hits, decreased exits Google Analytics 3 mo Before 3 mo After Page Views 3,393,986 5,270,783 Unique Page Views 2,609,161 3,606,197 Average Time on Page 1m:51s 1m:21s % Exit 27.92% 20.79%
- 34. 2014 Summary • Plan UXDesign First • Determine Development Strategy • Incorporate Pre-Built Tools and Frameworks • Store Relational Data in a Database • Test, Test, Test
- 35. 2014 Come to ourboth for a chance to win! • ASUS Transformer Book T100TA-C1-GR Touchscreen 2 in 1 • Sells for $399! • 10.1-inch HD touchscreen • Up to 11 hours battery life
- 36. 2014 Questions • Michael Blumenthal SharePointArchitect PSC Group, LLC • MBlumenthal@psclistens.com • psclistens.com • www.cspug.org • Blog.blumenthalit.com • Twitter: @MichaelBL • SPYam & MWC Yam Thank you for your time today. • Malcolm Eaton Practice Lead PSC Group, LLC • MEaton@psclistens.com • psclistens.com • SPYam & MWC Yam
Editor's Notes
- #4 Devs?Admins?Using sp2013 for internet site?Public Facing Website on SharePoint?
- #7 We wore many hats:Gather RequirementsBusiness Process ConsultingTechnology ConsultingManagement ConsultingWe helped the business understand what they needed to communicate and accomplish.
- #8 Over 504 pieces of content
- #10 PSC Client Portal (our SP2013 extranet) was heavily used.
- #26 No more Internet license costs vs 2010Development of Web Parts in parallel with site structure, branding, navigationPutting each app in its own solution package rather than one giant solution package made maintenance, upgrades easyUse of Telerik controls ASP.NET Ajax Controls(details later in the deck) Integrating OOTB FBA user management model with a rich user model(details later in the deck) Use of a custom SQL database because this is highly relational Line of Business data.SQL DB vs. Lists
- #28 Decided to go with server side development. Made decision in June 2013.Initially wanted to go App ModelTried of couple of process / Took 3-4 time as longApp Model is maturing / But Still Not ready Yet
- #29 External Users – Extended Properties – FBA FrameworkMuch customization required.
- #30 Back-End is SQL instead of using Lists- Integrate with AS/400Pre-existing web services needed to be maintained.Active/Passive SQL Cluster had two SQL Instances, one for SP, one for the Roadrunner LOB data.
- #31 No Fault tolerance / Disaster Recovery in the system that we replaced. New system uses a fault tolerant design.LB3 WFE2 App1 SQL Cluster2 instances: SP, RRC DBStage, dev: reduced farm members
- #33 Possibly play A-Team theme song?
- #37 Add Malcolm info