SharePoint has matured since its inception in the early 2000’s from a product that provides a lot of important features to a full blown platform that small and large business are building critical solutions on. The average $1 billion company maintains, on average, 48 disparate financial systems and uses 2.7 ERP systems. SharePoint enables incredible interoperability to these various systems in a way that’s consistent across various groups within the enterprise. In this session we will talk about how SharePoint can be used to create convergence across the various line of business systems in a way that not only saves time and money but also breaks down silos that impeded productivity and innovation.
CNIC Information System with Pakdata Cf In Pakistan
The Rise of SharePoint as a Business Critical Hub
1. 1
SharePoint History
Business Critical SP
ROI through Adoption
Integration
Dan Barker, Global Product Manager
Dell Software
The rise of SharePoint as a business critical
hub for LOB solution delivery
2. 2
• Global PM and evangelist for Quick Apps for SharePoint
• Worked with SharePoint since the “Tahoe” days
• Stints as a software engineer, systems architect financial &
data analyst, and general manager
• Prior work at Progressive Insurance, Crowe
Horwath, Rubbermaid, Pharmacia
• Executive MBA from the Nance School of Business at
Cleveland State University
• Live in the greater Seattle, Washington area
Who on earth is Dan Barker?
3. 3
Agenda
• SharePoint Over the Years
• The Rise of Business Critical SharePoint
• The Business & IT Relationship
• A Real Life Example
• Business Critical SharePoint Data Points
• Tools
• Q&A
4. 4
SharePoint Over Time
2001
SharePoint Team
Services (STS)
2003
Windows
SharePoint
Services 2.0
(WSS 2.0)
2001
SharePoint Portal
Server (SPS)
2003
SharePoint Portal
Server (SPS)
2007
Windows
SharePoint
Services 3.0
(WSS 3.0).
2007
Windows Office
SharePoint Server
(MOSS)
2010
Microsoft
SharePoint
Foundation 2010
2010
Microsoft
SharePoint Server
2013
Microsoft
SharePoint
Foundation
2013
Microsoft
SharePoint Server
5. 5
The Early Years: 1998 - 2001
• 1996 Site Server – Dot com hype, getting websites up quickly
• 1998 Site Server 3.0 – Commerce edition, content
management, search, personalization, order processing
• 2001 SharePoint Portal Server (SPS) – Tahoe / SharePoint Team Services S(TS)
– Portal product that helped businesses aggregate corporate information
through nav & search
– Enter SQL as the data store & ASP.Net as the dev platform
– Web parts (server controls) – digital dashboard design
• 2001/2002 – Content Management Server (CMS)
– ASP.Net functionality
– Very popular/public web site use
• Good for targeted scenarios but had little integration between them (portal
and collaboration). Further integration was needed.
6. 6
2001
• No YouTube
• No FaceBook
• No iTunes
• No Twitter
BUT…
• Matchbox Twenty – If You’re Gone
• Wikipedia is started
• The first iPod is launched
• Toyota Prius is launched
• The Segway
7. 7
The Early Years: 2003
• 2003 SharePoint Portal Server 2.0 (SPS) / Windows SharePoint
Services 2.0 (WSS) were born
– Built on a common base platform
– SPS – Deep portal and search functionality
– WSS – Core collaboration capabilities –Lead to viral adoption
because of the ease of deployment
– Adopted as an intranet solution
– Ease of deployment led to mass adoption
– Customers were excited about the ability to create team sites
and departmental solutions (Collaboration and portal) on the
same platform
• Further integration was needed – Customers wanted one
integrated platform for WSM, portal and collaboration
8. 8
The Early Years: 2007
• Microsoft Office SharePoint Server (MOSS) / Windows
SharePoint Services (WSS) 3.0
– Personalized Portals (MySites, Aggregation Web Parts)
– Content Types, Workflow, Records Management, InfoPath
Form Services, Enterprise Search (Fast)
– Integrated collaboration, portal, search, content
– Changed the way customers and partners thought about
business collaboration
– Consistent experience for both IT and end users
– BDC – Business Data Connector - limited to only reading
data from the external data sources
– Connectors to SAP, Siebel, Dynamics
17,000 customers, 100m licensees, 4,000 Si’s, 1.3 billion in revenue.
9. 9
Maturing as a Platform: 2010
• SharePoint Server 2010 / SharePoint Foundation 2010
– Business Connectivity Services (BCS)
– supported updating, deletion and insertion of data into external data
sources.
– Excel, Access, User Profile Services, Query Throttling, Batch Query
Support, Remote Blob Storage
– External Lists (providing supporting large lists without burdening the
SharePoint 2010 content database)
– SandBox Solutions
• Further integration was needed – Customers wanted more social
features and integration, improved mobile/tablet experience
10. 10
Maturing as a Platform: 2013
• SharePoint Server 2013 / SharePoint Foundation 2013
– Cloud ready (Azure/AWS or pure cloud play)
– Office 365
– SharePoint/Office App Store
– Search Engine Optimization & Analytics is in Search (FAST)
– SEO
– Cross-Site publishing
– Yammer acquisition and integration
– SP Social
– Follow sites & people
– Tags
– Activity Streams
– My Sites improvements
– Cross-browser functionality (no active X!)
– Device specific master pages – What Whaaaat?
– Workflow Integration with Workflow Manager
– oData in BCS
– Branding Flexibility
11. 11
SharePoint Over Time
2001
SharePoint Team
Services (STS)
2003
Windows
SharePoint
Services 2.0
(WSS 2.0)
2001
SharePoint Portal
Server (SPS)
2003
SharePoint Portal
Server (SPS)
2007
Windows
SharePoint
Services 3.0
(WSS 3.0).
2007
Windows Office
SharePoint Server
(MOSS)
2010
Microsoft
SharePoint
Foundation 2010
2010
Microsoft
SharePoint Server
2013
Microsoft
SharePoint
Foundation
2013
Microsoft
SharePoint Server
13. 13
A Picture in Phases -Phase 1
SharePoint
External SpaceInternal Space The Great Divide
Customer / Partner / Market
Legal IT Sales Marketing Finance
Content mgt. Doc mgt. Intranet
HR Admin Customer Service
14. 14
A Picture in Phases -Phase 2
SharePoint
External SpaceInternal Space The Great Divide
Customer / Partner / Market
Legal IT Sales Marketing Finance
Content mgt. Doc mgt. Intranet
Forms Reporting/BI Search
HR Admin Customer Service
Workflow Workflow Navigation
15. 15
A Picture in Phases -Phase 3
External SpaceInternal Space The Great Divide
Customer / Partner / Market
Legal
IT
Sales
Marketing
Finance
HR
Admin
Customer
Service
SharePoint
16. 16
SharePoint
A Picture in Phases -Phase 4
The Extended Network
Customer / Partner / Market
IT
Sales
Marketing
Finance
Legal
HR
Customer
Service
int
18. 18
BCSP Enhances the IT and business relationship
Improves Organizational agility
• improves organizational agility
19. 19
A Real Life Example
Top insurance company in the US
• Contract group
• Managed all IT contracts for Hardware, Software, Consulting & Services
• Kept paper contracts in special file cabinets, peoples desks, and in some cases nowhere
• Both business and IT project managers depended on the IT Control group to:
– Procure necessary assets for their projects
– Provide a single point of engagement
– Understanding the timing of the process (SLA’s)
– Provide transparency while in flight
– Understand the overall IT budget and “control” costs
– Cut a PO
– Help IT and business sponsors/owners manage “Run the business” IT spend
- 0 to operational in 6 months -
20. 20
A Real Life Example
Procurement group
The Problem:
• No centrally managed process
• No centrally utilized system
• No SLA
• No transparency
• Silos
The Result:
• Customers had to “call” to see where things stood
• Lack of documented priority (Squeaky wheel syndrome)
• “Hair on fire” procurement staff = snowball effect
• 4-6 month completion estimate
• Slower speed to market
• Different answers from different people
21. 21
A Real Life Example
Procurement group – The black box
22. 22
A Real Life Example
The actual process
Procurement Legal Exec Team BuyersCustomer Tax
Silo Silo Silo Silo Silo SiloSharePoint
23. 23
A Real Life Example
Architecture
IT Control SharePoint
Sites
IT Control
Transaction Library
InfoPath
Form
SQL Server Integration
Services (SSIS)
Transaction Warehouse
MSRS
Report
MSRS
Report
MSRS
Report
Microsoft Reporting Services
(MSRS)
Report Users
Operational Users
Batch Process
24. 24
A Real Life Example
Disparate systems
IT Planning
(SQL)
Oracle DW
(Oracle)
Project Management
DW
(SQL)
ITC SQL Server
SAM
(SQL)
IT Planning DB
(Notes)
Oracle Financials
(Oracle)
Oracle Primavera
(Oracle)
PSC
(Notes)
RTB Budget
(Excel)
Markview – 170
Systems
(Web)
ITC SharePoint
(SharePoint)
9 11
2 3 4 5 76
8
12
10
Service Management
(SharePoint)
13Color Key
PC Purchase
(Notes)
14
1
Not Currently Integrated (Future state)
Current System
Current System (Used in
Automated Data Feed)
25. 25
A Real Life Example
Top 3 insurance companies in the US
The End Result
• Single source of the truth
• A unified “operational” process
• A unified system - SharePoint
• SLA’s & Shorter Cycle Times
• Internal & external transparency
• Process improvement mechanism
• Silo elimination
• Faster speed to market
• Happier customers & stakeholders
• Operationally dependent on SharePoint = business critical = ROI
26. 26
LOB systems
Device
Proliferation
Mobile
Workers
Less funding
to modernize
Mobility
Expecting
interactive
collaboration
Expecting
immediate
access
Need to
maximize
existing
systems
Data to grow
44x over the
next decade 1
BI is No. 1
technology
priority for
CIOs 2
Challenges
with inter-
operability
1 IDC Digital Universe Study, sponsored by EMC, May 2010; 2 www.computerworld.com/s/article/9223502/The_top_10_tech_priorities_of_CIOs; 3 Business Intelligence Purchase Drivers and Adoption Rates, Gartner
Only 28% of
potential BI
users have
meaningful
access 3
Market drivers
27. 27
The problem—multiple, disparate applications
The average $1 billion company maintains, on
average, 48 disparate financial systems and uses 2.7 ERP
systems Source: The Hackett Group
29. 29
Become a connected organization
From systems of record to systems of engagement
SalesEngineering Human Resources Procurement
Administration Operations Customer Service Finance
Business Process/Workflow
33. 34
Tools are Critical
• Use SharePoint as the unified UI across teams and groups
• BCSP - Integrate and elevate
• Need a way to integrate…..EASILY
• Cross Skillset enablement (tech/non-tech)
• Use SharePoint as a “platform” and engagement mechanism
• There are a lot of scenarios
(forms, charts, calendaring, navigation, workflow, BI, reporting, KPI’s, security)
35. 36
Enhance
Navigation
With Panel
Menus Quickly Create
better Forms
Including Tabs
Lists/views
Charting
Forms
Data filtering
Data integration
And more!
Display Data in a
Drop Down Control
From Any List
Easily Combine Data
From Multiple Lists
Easily Create Vibrant
3D Charts
Quick Apps for SharePoint
Elevate the visualization of critical information to your end users
Workflow
compatible
36. 37
Summary
• SharePoint is a Platform not a Product
• As a platform it can act as a common language
– Between IT and the Business
• Everyone usually has access
• Most scenarios are not incredibly complex
• Destroy silos and connect people
• SharePoint is the conveyer belt of the business
• Doing the everyday better than your competition
• Operational = business critical = adoption = ROI
37. 38
Contact Information
• Dan’s Contact information
– Email: d_barker@dell.com
– Twitter: @BarkingD
– LinkedIn: http://www.linkedin.com/in/danielbarker
– Blog: http://danbarker.typepad.com/changeplane/
– Pager Number: Just Kidding
Worked with SharePoint before it was called SharePoint (12+ years)When the content management piece was a separate tool altogether. All the good old days…..not really….it sucked!!Progressive Insurance (the third-largest auto insurer in the US) and as a senior consultant for Crowe Horwath (one of the largest public accounting and consulting firms in the US)Founded a consulting practice that ran for 5 years.
We haven’t even touched the LOB integration scenarios much yet.These are SharePoint Specific requirements and integration needs (within SharePoint itself)The scope was broader but it had to start at the SharePoint level first, then extend to external platforms.A unified solution is what customers want and needThis is why SI partners were so important and critical to extending SharePoint beyond native capabilities.
Expanding native SharePoint It always starts small, then grows.Users started to learn the importance of aligning SharePoint initiatives to key business objectives.Personal and business spaceThis is when it changes from being a product to being a platform (in my opinion
I say social integration because social was defined outside the enterprise firstThe enterprise (Microsoft) needed to catch up with what has been happening on the consumer side for years
I say social integration because social was defined outside the enterprise firstThe enterprise (Microsoft) needed to catch up with what has been happening on the consumer side for years
No external integration with customers vendors or partnersConnection mechanism is a typical PC and BrowserNot everyone is using SharePointThose who are, only use it for documents or simple web site informationIT is the primary driver of the technology and platform in the beginning
More groups within the enterprise start using SharePoint for various purposesSome groups gain deep knowledge of specific functions such as: Need for getting data in and out
More groups within the enterprise start using SharePoint for various purposesSome groups gain deep knowledge of specific functions such as: Need for getting data in and outDependancy becomes operationalThis is where silos are brokenSilos here are both physical and virtual (process, disparate teams, geography)There is process and connection points everywhere in an organizationSome are obvious, some are not.
More groups within the enterprise start using SharePoint for various purposesSome groups gain deep knowledge of specific functions such as: Need for getting data in and outDependancy becomes operationalThis is where silos are brokenSilos here are both physical and virtual (process, disparate teams, geography)There is process and connection points everywhere in an organizationSome are obvious, some are not.
I call SharePoint the conveyer beltCan makes the process better, more efficient.Both sides can provide input to improving and managing the process.
Operational UsersStakeholders/customers (internal and external, executives)Basic reporting and BI in SharePoint, forms, team engagement, workflowAdvanced reporting and BI in SSRSAll in SharePoint
SOME of the systems that were integrated to make this workMore on this “on average in a later slide”
Consumerization of IT: Consumer technology becoming part of our business lives. employees don’t have patience to wait for static reports. Business professionals are demanding real-time, dynamic data delivered in an interactive and visually immersive experience
Oracle users face these problems because they can't build the solution into their apps and they have to build it separately. These tools are expensive, it's time consuming and they don't have the resource power to do that. That’s where SharePoint comes into play.Collapse disparate systems into a common platform and toolsetEXAMPLE: SalesForce integration with Quick Apps
The overall environment is bigger than Oracle and that the solutions are up to you. You have a choice. You can choose flexible solutions at a more affordable price. SharePoint enables incredible interoperabilityIt provides a rapid time to value because of its simplicity.
Connect business and industry apps through an organization-wide collaboration platformShare relevant data across different functions and respond to market changes on-demandImprove your LOB ROI while reducing business risk without “rip and replace”You cannot have ROI without adoption. You can’t have adoption without a strong value prop!!
But don’t just take my word for it…Over the past year, BCSP partners and customers have come together to lock on some of the main drivers of ROI for BCSP solutions Through 3rd party research, it was discovered that there is a particular “flow” to the value experienced by BCSPThese are some of the common benefits from a business, process, and IT perspectiveIT-related benefits are realized in “getting to the solution” which then drives process impacts around time and productivityBoth of these then lead to the business impact, which is often what can be measured in value (dollars and cents) {Summarize the benefits listed for each section}These benefits are what customers are seeing within their organization when they take the Business-Critical SharePoint approach, and these are all benefits that you want to bring to your organization to help deliver the best possible experience for your customers
- More than 50% of SP case studies- Customers are excited about these because they reflect business effectiveness
Customer applications without custom codeEnable the lions share of users to create the solutions they needSupported and upgradeableCustomization without the riskThe 80/20 rule applies here
Quite frankly most of this stuff isn’t rocket scienceDoing the everyday better than your competitorsThis is one of the reasons why I love the app store opportunityReusability, enablement, easy access, less risk, solution delivery, GETTING THINGS DONW