SharePoint as a Business Platform 
Why, What and How ? –No Code 
Jean-François Saint-Pierre –EvolusysSA
Evolusys SA 
DataMining 
Business Workflows & Forms 
Mobility 
SAP / Microsoft Interop 
Social & Geo Intelligence 
Business Intelligence
SharePoint as a Business Platform 
The Rationale –Why ? 
–It’s not your father’s SharePoint 
–Component of a Business Platform 
–SharePoint & Friends 
Application Types –What ? 
–Candidate Apps 
–Traditional vsSharePoint 
–Task Orientation 
Approach –How ? 
–Capabilities then Processes 
–Real SharePoint Consultants 
Demo 
SharePoint 
LiveTiles 
dox42 
Nintex 
Excel REST
THE WHY ? 
SharePoint as a Business Platform
Knowledge Workers 
It is an era of Knowledge and Services 
Ten IT-enabled business trends 
for the decade ahead –McKinsey (May 2013) 
#5 : Automating Knowledge Work 
Physical labor and transactional tasks have been widely automated over the last three decades. Now advances in data analytics, low-cost computer power, machine learning, and interfaces that “understand” humans are moving the automation frontier rapidly toward the world’s more than 200 million knowledge workers. 
Source : http://www.mckinsey.com/
Not your father’s… 
•Ubiquitous 
•Secure 
•Enterprise Level Tools 
•Workflow Engine (x2) 
•Forms (hum… well..) 
•Office Web Apps 
•Search 
•Mobility 
•Business Intelligence 
Source : http://abalon.fr/blog/
Once installed, well… nothing… 
Still needs … 
•Configuration 
•Design / Branding 
•Support 
•Training 
•Monitoring 
… and Governance 
•Change / Evolution 
•Policies 
•Help / Feedback loops 
Or suffer… 
The Glorified File Share (collaboration) 
The Random File Generator (search) 
The Ugly Outdated Intranet (contents) 
The Big Bucks Cafeteria Menu (purpose) 
The Swiss Cheese File Manager (security) 
The Electronic Quasimodo (design)
But more specifically… 
•Send and Receive Mails 
•Mails can trigger transactions 
•Mails should be tagged and shared 
•Information Assets 
•Consumed and created 
•As part of processes 
•And tagged and shared 
•Integrate with other systems 
•No code, read-write 
•Engaging UX 
•Minimiserequired training 
•Max Productivity 
•Least Resistance Principle 
•Perform Calculations 
•Simple / Complex 
•Rules based 
•Provide reports 
•Performance stats 
•Monitoring 
Gartner Survey (2008) -BPM 
‘How often do your process change ?’ 
•67% of processes change every 6 months 
•18% every month
How does SharePoint Rank…
The Case for No Code 
Code 
•Need Developers 
•Tunnel Effect 
•Complex Software Lifecycle 
•Opaque 
•Efforts / Costs 
MAINTENANCE !!! 
No Code 
•Need Analysts 
•Iterative Prototype 
•Simplified Software Lifecycle 
•Declarative 
•Need additional tools (ROI) 
MAINTENANCE !!!
With a little help…
SharePoint (with a little help)… 
Capability 
Comments 
Solution 
ConnectSAP & SharePoint 
4 waysto integrate –no code 
Theobald Software 
Drawyour Processes 
SharePoint Executes 
NintexWorkflow 
BuildIntelligent Forms 
Also targetMobile 
NintexForms 
Integrateyour mails 
From Outlook,Office… 
OnePlaceSolutions 
Create acompelling UX 
And v2 is Responsive 
LiveTiles 
Generate personalized documents 
Using FamiliarOffice Tools 
dox42 
BridgeOn-Prem& SaaSSolutions 
Allmajor SaaSincluding SalesForce 
NintexLive 
Evolusys’ modern App -Ingredients
What is LiveTiles? 
LiveTilesis User Experience 
•Modern user experience demands faster, more intuitive, convenient and personalized interactions. 
•Delivers user-centric information within 1-2 touches or clicks, including tasks and schedules, meetings and popular documents 
LiveTilesis Design 
•Supports modern UI design, mobile site creation and out-of-the-box integration with external platforms. 
•Wizard-based interface is simple for non-technical users to navigate, and tiles, apps or additional functionality can be added or removed at the touch or click of a button 
LiveTilesis Mobile 
•Mobile site views can be quickly created using a simple ‘drag and drop’ method. Tiles and apps can be dragged to an interface and saved as a mobile device channel 
•Phase 2 roll out in 2014 is an in-built Device Bar; build interfaces using device specifications from all the major brands on the market 
- 13 -
What is dox42 ? 
Create 
•Templates in Word, right from SharePoint 
•Dox42 Ribbon 
Merge 
•Automate Document Generation using Nintex 
•Drive Server from any Workflow 
Output 
•Outputs results directly into SharePoint 
•In one or more of many output formats
THE WHAT? 
SharePoint as a Business Platform
Candidate Apps 
Poor Candidate Apps 
•High Volume / Short Time 
•Highly Relational Structures 
•Industrial 
•Mostly outside SP 
•Few Manual Steps 
Good Candidate Apps 
•Human Centric (slow) 
•Unstructured KM Based 
•Admin / Business 
•Various Systems but SP Centric 
•Manual Steps (Copy / Paste)
New Development Paradigm 
From the ‘Window that does it all’ 
To ‘Task Orientation’ and User Profiling
That Leverages SharePoint 
Bring Information Closer To the Owners 
•Capitalizing on familiar tools : Excel, Word 
•Whether as inputs our outputs 
Versioning, Search, Lists, Approvals 
•Change audit trails 
•Search based perspectives 
From the horses mouth… 
•Calculation models born in Excel / Remain in Excel 
•Documents born in Word / Remain in Word
Example –Replacing a .NetApp 
•LiveTiles/ NintexForms 
•Task Oriented 
Complete EOI Form 
•Excel REST 
•Always up to date 
•Excel from doclib 
Obtain Vaccine Cost Calculations 
•dox42 
•Merge with various Sources 
•Word from doclib 
Create Contract Document 
•NintexWorkflow 
•Review and Approval WF 
Route to Country Owners 
Collecting Metrics –throughout the process 
Security & Access
Example –Replacing a .NetApp 
Before 
Calculations 
•Created in Excel 
•But reprogrammed twice 
Outputs (Contracts) 
•Created and maintained in Word 
•But recreated in Reporting Services 
•Huge performance problems 
Business Rules / Workflow 
•All over the place (Interface, App, BD) 
•Hard to maintain / Coded 
•Execution per code 
After 
Calculations 
•Created and maintained in Excel 
•Remain in Excel (Excel REST) 
Outputs (Contracts) 
•Created and maintained in Word 
•Remain in Word (dox42) 
•Incredible performance 
Business Rules / Workflow 
•NintexForms / Workflow 
•Visible, Maintainable / Versioned 
•Execution engine (data points at every step)
THE HOW ? 
SharePoint as a Business Platform
Approach towards a great app 
•Get the Big Picture (Why) 
•Then the What 
•Then the How 
•It willchange, design with evolution in mind 
•Adoption & Least Resistance : UX 
•Respects each other’s backgrounds (Business vsIT)
Approach 
Method 
•Define the solution as a Service 
•Define the Service(s) as a Suite of Capabilities 
•Deliver the Capability through Processes 
•Prototype, prototype, prototype… 
•Iterate, Iterate, Iterate… 
Deliverables 
•Service Definitions 
•Capability Definitions 
•Use Cases 
•Process Definitions 
•Prototype 
•Solution
Anatomy of a ServiceDelivering Value to a Population 
Rationale 
–Strategic, Tactical Motives 
–Service Definition (Vision) 
–Balanced Scorecard (Benefits, Clients, Process, People) 
People 
–Stakeholders (Service Owners / Governance / RASCI) 
–Clients / Target population(s) 
–Supporting population(s) (Business) 
Processes (Service Specific) 
–Automation whenever possible / User Experience / Design 
–Training / Change requirements (path of least resistance) 
–Constraints (Environment, Policies, Legal, Security) 
Tools 
–Implementation 
–Services Levels Objectives / Monitoring / Availability 
–Change Requests / Issues Registers (Parking Lot) 
- 24 - 
Delivering a SharePoint Platform 
Modeling your SharePoint as a services platform 
•Embodying principles (Principles –Self-Service, Great UX, Security, Coherence) 
•Based on a Common Core (Foundation Services) 
•Managed by Business committees (Governance) 
•Bringing the Best Experience to different populations (User Experience) 
•With Adapted automation and Support (Change Management)
Capabilities, then Processes 
1. Business Capabilitiesare stable 
2. WhileProcessesChange 
3. Start with Why and What (Business) and then How (Implementation)
Disaggregation of the value chainCorporate CreditBuildingCreditConsumer CreditPaymentEntry inLandRegisterPaymentCollateralsRegistrationCheckContractGetSignatureFinal Vote& DecisionCollateralsEvaluationProductConfig- urationFirstVoteRatingDataEntryCollateralsAcquisitionProductSelectionCheckContractGetSignatureFinal Vote& DecisionCollateralsEvaluationProductConfig- urationFirstVoteScoringDataEntryCollateralsAcquisitionProductSelectionPaymentCheckContractGetSignatureDecisionVoteScoringProductSelectionDataEntryProductConfigurationProductSelectionCollateralsRegistrationCollateralsEvaluationScoringRatingProductConfigurationProductSelectionEntry inLand RegisterCollateralsEvaluationScoringCollateralsAcquisitionGetSignatureVotePaymentDataEntryCheckContractDecision 
Identifying Capabilities
Anatomy of a Capability 
Start 
People 
Procedures 
Technology
Encapsulating a Capability 
Business owns the WHAT and the WHY 
SharePoint Consultant owns the HOW
SharePoint is a strange Beast 
Just because it’s possible… 
… does not mean it’s a good idea ! 
Advice : 
Know your SharePoint (Analyst)
Your SharePoint Analysts 
Should care about : 
•Why and What we are building 
•User Experience 
•Reuse 
•Maintenance 
•Metrics 
Advice : Simple is Hard
SharePoint Analysts 
Humm… Question… 
Consider SharePoint as a Framework 
•1stoption is to develop 
•Know the API, but not the Configuration 
Do not see the forest for the trees 
•Fail to see the big picture 
•Focus on the How, not the What / Why 
Have a hard time speaking clearly 
•Sounds like Klingon 
•Do not care about UX 
Prefer the following… 
See SharePoint as a Platform 
•Know the Features (all of them) 
•Understand why there are many possibilities for a given goal 
Put themselves in the users shoes 
•Focus on the outcome 
•Will challenge to understand the what 
Should be easy to understand 
•Talk Business 
•Make suggestions for Improvement 
•Understand User Experience
One Last Quote…
DEMO 
SharePoint as a Business Platform
LiveTilesnot only design… but a huge component !
Excel REST Services 
Model 
http://evolab.cloudapp.net/sites/evoludays/sd/_vti_bin/ExcelRest.aspx/xl/SSC2014.xlsx/Model/ 
Graba Cell 
•http://evolab.cloudapp.net/sites/evoludays/sd/_vti_bin/ExcelRest.aspx/xl/SSC2014.xlsx/Model/Ranges('TotalProgramCost')?$format=atom 
Use as calculator 
•http://evolab.cloudapp.net/sites/evoludays/sd/_vti_bin/ExcelRest.aspx/xl/SSC2014.xlsx/Model/Ranges('TotalProgramCost')?$format=image&Ranges('EstimatedProgramCost')=65000&Ranges('CountrySupportPercent')=0.8 
And now… 
•http://evolab.cloudapp.net/sites/evoludays/sd/_vti_bin/ExcelRest.aspx/xl/SSC2014.xlsx/Model/Charts('Program_Performance')?$format=image&Ranges('EstimatedProgramCost')=65000&Ranges('CountrySupportPercent') =0.5
Jean-François Saint-Pierre 
ManagingPartner –Business Development 
jfsp@evolusys.ch

SharePoint as a Business Platform Why, What and How? – No Code

  • 1.
    SharePoint as aBusiness Platform Why, What and How ? –No Code Jean-François Saint-Pierre –EvolusysSA
  • 2.
    Evolusys SA DataMining Business Workflows & Forms Mobility SAP / Microsoft Interop Social & Geo Intelligence Business Intelligence
  • 3.
    SharePoint as aBusiness Platform The Rationale –Why ? –It’s not your father’s SharePoint –Component of a Business Platform –SharePoint & Friends Application Types –What ? –Candidate Apps –Traditional vsSharePoint –Task Orientation Approach –How ? –Capabilities then Processes –Real SharePoint Consultants Demo SharePoint LiveTiles dox42 Nintex Excel REST
  • 4.
    THE WHY ? SharePoint as a Business Platform
  • 5.
    Knowledge Workers Itis an era of Knowledge and Services Ten IT-enabled business trends for the decade ahead –McKinsey (May 2013) #5 : Automating Knowledge Work Physical labor and transactional tasks have been widely automated over the last three decades. Now advances in data analytics, low-cost computer power, machine learning, and interfaces that “understand” humans are moving the automation frontier rapidly toward the world’s more than 200 million knowledge workers. Source : http://www.mckinsey.com/
  • 6.
    Not your father’s… •Ubiquitous •Secure •Enterprise Level Tools •Workflow Engine (x2) •Forms (hum… well..) •Office Web Apps •Search •Mobility •Business Intelligence Source : http://abalon.fr/blog/
  • 7.
    Once installed, well…nothing… Still needs … •Configuration •Design / Branding •Support •Training •Monitoring … and Governance •Change / Evolution •Policies •Help / Feedback loops Or suffer… The Glorified File Share (collaboration) The Random File Generator (search) The Ugly Outdated Intranet (contents) The Big Bucks Cafeteria Menu (purpose) The Swiss Cheese File Manager (security) The Electronic Quasimodo (design)
  • 8.
    But more specifically… •Send and Receive Mails •Mails can trigger transactions •Mails should be tagged and shared •Information Assets •Consumed and created •As part of processes •And tagged and shared •Integrate with other systems •No code, read-write •Engaging UX •Minimiserequired training •Max Productivity •Least Resistance Principle •Perform Calculations •Simple / Complex •Rules based •Provide reports •Performance stats •Monitoring Gartner Survey (2008) -BPM ‘How often do your process change ?’ •67% of processes change every 6 months •18% every month
  • 9.
  • 10.
    The Case forNo Code Code •Need Developers •Tunnel Effect •Complex Software Lifecycle •Opaque •Efforts / Costs MAINTENANCE !!! No Code •Need Analysts •Iterative Prototype •Simplified Software Lifecycle •Declarative •Need additional tools (ROI) MAINTENANCE !!!
  • 11.
  • 12.
    SharePoint (with alittle help)… Capability Comments Solution ConnectSAP & SharePoint 4 waysto integrate –no code Theobald Software Drawyour Processes SharePoint Executes NintexWorkflow BuildIntelligent Forms Also targetMobile NintexForms Integrateyour mails From Outlook,Office… OnePlaceSolutions Create acompelling UX And v2 is Responsive LiveTiles Generate personalized documents Using FamiliarOffice Tools dox42 BridgeOn-Prem& SaaSSolutions Allmajor SaaSincluding SalesForce NintexLive Evolusys’ modern App -Ingredients
  • 13.
    What is LiveTiles? LiveTilesis User Experience •Modern user experience demands faster, more intuitive, convenient and personalized interactions. •Delivers user-centric information within 1-2 touches or clicks, including tasks and schedules, meetings and popular documents LiveTilesis Design •Supports modern UI design, mobile site creation and out-of-the-box integration with external platforms. •Wizard-based interface is simple for non-technical users to navigate, and tiles, apps or additional functionality can be added or removed at the touch or click of a button LiveTilesis Mobile •Mobile site views can be quickly created using a simple ‘drag and drop’ method. Tiles and apps can be dragged to an interface and saved as a mobile device channel •Phase 2 roll out in 2014 is an in-built Device Bar; build interfaces using device specifications from all the major brands on the market - 13 -
  • 14.
    What is dox42? Create •Templates in Word, right from SharePoint •Dox42 Ribbon Merge •Automate Document Generation using Nintex •Drive Server from any Workflow Output •Outputs results directly into SharePoint •In one or more of many output formats
  • 15.
    THE WHAT? SharePointas a Business Platform
  • 16.
    Candidate Apps PoorCandidate Apps •High Volume / Short Time •Highly Relational Structures •Industrial •Mostly outside SP •Few Manual Steps Good Candidate Apps •Human Centric (slow) •Unstructured KM Based •Admin / Business •Various Systems but SP Centric •Manual Steps (Copy / Paste)
  • 17.
    New Development Paradigm From the ‘Window that does it all’ To ‘Task Orientation’ and User Profiling
  • 18.
    That Leverages SharePoint Bring Information Closer To the Owners •Capitalizing on familiar tools : Excel, Word •Whether as inputs our outputs Versioning, Search, Lists, Approvals •Change audit trails •Search based perspectives From the horses mouth… •Calculation models born in Excel / Remain in Excel •Documents born in Word / Remain in Word
  • 19.
    Example –Replacing a.NetApp •LiveTiles/ NintexForms •Task Oriented Complete EOI Form •Excel REST •Always up to date •Excel from doclib Obtain Vaccine Cost Calculations •dox42 •Merge with various Sources •Word from doclib Create Contract Document •NintexWorkflow •Review and Approval WF Route to Country Owners Collecting Metrics –throughout the process Security & Access
  • 20.
    Example –Replacing a.NetApp Before Calculations •Created in Excel •But reprogrammed twice Outputs (Contracts) •Created and maintained in Word •But recreated in Reporting Services •Huge performance problems Business Rules / Workflow •All over the place (Interface, App, BD) •Hard to maintain / Coded •Execution per code After Calculations •Created and maintained in Excel •Remain in Excel (Excel REST) Outputs (Contracts) •Created and maintained in Word •Remain in Word (dox42) •Incredible performance Business Rules / Workflow •NintexForms / Workflow •Visible, Maintainable / Versioned •Execution engine (data points at every step)
  • 21.
    THE HOW ? SharePoint as a Business Platform
  • 22.
    Approach towards agreat app •Get the Big Picture (Why) •Then the What •Then the How •It willchange, design with evolution in mind •Adoption & Least Resistance : UX •Respects each other’s backgrounds (Business vsIT)
  • 23.
    Approach Method •Definethe solution as a Service •Define the Service(s) as a Suite of Capabilities •Deliver the Capability through Processes •Prototype, prototype, prototype… •Iterate, Iterate, Iterate… Deliverables •Service Definitions •Capability Definitions •Use Cases •Process Definitions •Prototype •Solution
  • 24.
    Anatomy of aServiceDelivering Value to a Population Rationale –Strategic, Tactical Motives –Service Definition (Vision) –Balanced Scorecard (Benefits, Clients, Process, People) People –Stakeholders (Service Owners / Governance / RASCI) –Clients / Target population(s) –Supporting population(s) (Business) Processes (Service Specific) –Automation whenever possible / User Experience / Design –Training / Change requirements (path of least resistance) –Constraints (Environment, Policies, Legal, Security) Tools –Implementation –Services Levels Objectives / Monitoring / Availability –Change Requests / Issues Registers (Parking Lot) - 24 - Delivering a SharePoint Platform Modeling your SharePoint as a services platform •Embodying principles (Principles –Self-Service, Great UX, Security, Coherence) •Based on a Common Core (Foundation Services) •Managed by Business committees (Governance) •Bringing the Best Experience to different populations (User Experience) •With Adapted automation and Support (Change Management)
  • 25.
    Capabilities, then Processes 1. Business Capabilitiesare stable 2. WhileProcessesChange 3. Start with Why and What (Business) and then How (Implementation)
  • 26.
    Disaggregation of thevalue chainCorporate CreditBuildingCreditConsumer CreditPaymentEntry inLandRegisterPaymentCollateralsRegistrationCheckContractGetSignatureFinal Vote& DecisionCollateralsEvaluationProductConfig- urationFirstVoteRatingDataEntryCollateralsAcquisitionProductSelectionCheckContractGetSignatureFinal Vote& DecisionCollateralsEvaluationProductConfig- urationFirstVoteScoringDataEntryCollateralsAcquisitionProductSelectionPaymentCheckContractGetSignatureDecisionVoteScoringProductSelectionDataEntryProductConfigurationProductSelectionCollateralsRegistrationCollateralsEvaluationScoringRatingProductConfigurationProductSelectionEntry inLand RegisterCollateralsEvaluationScoringCollateralsAcquisitionGetSignatureVotePaymentDataEntryCheckContractDecision Identifying Capabilities
  • 27.
    Anatomy of aCapability Start People Procedures Technology
  • 28.
    Encapsulating a Capability Business owns the WHAT and the WHY SharePoint Consultant owns the HOW
  • 29.
    SharePoint is astrange Beast Just because it’s possible… … does not mean it’s a good idea ! Advice : Know your SharePoint (Analyst)
  • 30.
    Your SharePoint Analysts Should care about : •Why and What we are building •User Experience •Reuse •Maintenance •Metrics Advice : Simple is Hard
  • 31.
    SharePoint Analysts Humm…Question… Consider SharePoint as a Framework •1stoption is to develop •Know the API, but not the Configuration Do not see the forest for the trees •Fail to see the big picture •Focus on the How, not the What / Why Have a hard time speaking clearly •Sounds like Klingon •Do not care about UX Prefer the following… See SharePoint as a Platform •Know the Features (all of them) •Understand why there are many possibilities for a given goal Put themselves in the users shoes •Focus on the outcome •Will challenge to understand the what Should be easy to understand •Talk Business •Make suggestions for Improvement •Understand User Experience
  • 32.
  • 33.
    DEMO SharePoint asa Business Platform
  • 34.
    LiveTilesnot only design…but a huge component !
  • 35.
    Excel REST Services Model http://evolab.cloudapp.net/sites/evoludays/sd/_vti_bin/ExcelRest.aspx/xl/SSC2014.xlsx/Model/ Graba Cell •http://evolab.cloudapp.net/sites/evoludays/sd/_vti_bin/ExcelRest.aspx/xl/SSC2014.xlsx/Model/Ranges('TotalProgramCost')?$format=atom Use as calculator •http://evolab.cloudapp.net/sites/evoludays/sd/_vti_bin/ExcelRest.aspx/xl/SSC2014.xlsx/Model/Ranges('TotalProgramCost')?$format=image&Ranges('EstimatedProgramCost')=65000&Ranges('CountrySupportPercent')=0.8 And now… •http://evolab.cloudapp.net/sites/evoludays/sd/_vti_bin/ExcelRest.aspx/xl/SSC2014.xlsx/Model/Charts('Program_Performance')?$format=image&Ranges('EstimatedProgramCost')=65000&Ranges('CountrySupportPercent') =0.5
  • 36.
    Jean-François Saint-Pierre ManagingPartner–Business Development jfsp@evolusys.ch