Building Business Solutions on Office 365 SharePoint Online

Darrell TrimbleCEO SP Marketplace

Introduction

Collaborative Business Applications Built on SharePoint

• 2011 Architected Business Solutions out of the box for Office 365

• Implemented at over 300 organizations – 70% on Office 365

• Target Market SMBs (50 – 100 employees) cross industry

Agenda

Objective: Educate on how you can build Business Solutions on SharePoint Online

• First: Put SharePoint in the Context of the Organization• SharePoint Solutions vs. SharePoint Apps• Differences between On-Premise vs. Cloud SharePoint• Overcoming the limitations in SharePoint Online• Our 365 Business Solution Model• Business Solution Examples• Questions and Answers

What is SharePoint?

• A Replacement for our Network File Sharing?

• Competition for Outlook tasks and Calendars?

• Document Management

• An Internal Facebook for our Employees?

• Team Site = Intranet Portal

Typical SharePoint Structure We See

Central Portal for Collaboration and Access to Services

Put SharePoint Structure into the Context of the Organization

Intranet Portal

Self - Service

HR

HR. Employee Portal

IT

IT Portal

Marketing

Admin Sales Services Other…

A Little History – Business Applications• Traditional Application Approach - CODING BY DEVELOPERS• Pick the platform – database• Design the application• Code the application• Package and deliver• Customization – coding• Integration – ADK (application developer kit)

ISSUES – time consuming and costly to develop in, not flexible, business users cannot change or manage

• Platform Based Rapid Application Development – BUSINESS ANALYST• Built on a platform that supports data, forms, views, workflow etc.• Design the application• Build the application on platform using components• Package and Install• Customization – platform features• Integration – built into platform

BENEFITS – fast development, common UI, configurable – change by business users

Business Solutions vs. SharePoint Apps

• Business Solutions• SharePoint Solutions – Site for a department or Functional Team• Made up of several business processes and collaboration components• Assembled by Business Analysts who understood the business processes

• SharePoint Apps• SharePoint App Model• Isolated applications for a specific function• Can be used in a site, maybe share data

SharePoint Solutions vs. Apps

Business Solution SharePoint App Model

What is it? Business Application Web part or small app

Who Builds it? Business Analyst or SharePoint Developer (non-coder)

Web Developer or Programmer(coder)

What is it written in? Not a program but a SharePoint Site(s)

HTML, CSS, JS, asp, JQuery

What tools are needed to build

SharePoint (UI) Browser, optionally SharePoint Designer

Visual Studio, Azure, Web development tools

App User Interface SharePoint Native Browser Custom Built

User capabilities All SharePoint Features (Views, notifications, pages etc.

Only what is built

Who can customize? Business Power User Developer, only if code is available

Comparison

SharePoint Solution SharePoint App Model

Who Built it SharePoint App Analyst Web developer

How long to Develop 2-3 Days Weeks

Easy Install and Configuration

Yes Yes

Standard UI (like other apps)

Yes No

X-Ref to Docs, email, other Yes No

Changes to fit my needs Application Admin No

Custom Reporting/Views Yes No

Add Fields, change forms Yes No

Custom Workflows Yes No

Upgrades easily to new SP Yes No

Add web parts Yes No

Best of All Worlds – Component Assembled Solutions

• Business Applications• SharePoint Solutions that covered 1 or more business processes• Assembled by Business Analysts who understood the business processes

• Web parts and applications components• SharePoint App Model• Use in the Business Applications to make them better

SharePoint in the Cloud vs. On-Premise

On-Premise Cloud (multi-tenant)

Notes

Model Server or Farm Multi-tenant

Code Resides In Server Client

Limited Capacity Some Yes – Specific to level Online Limits

SharePoint Install Complex Done

SP Version Support By version Support all versions Architectural issue

Feature Limitations

Feature Availability

Incoming Mail Yes No Cloud2050

Timer Jobs (scheduling)

Yes No Reminder 365

BI Features Yes Limited Google Chart Part

Web Part Availability 100s 10s App Store

SharePoint Online Market Segments

• Traditional SharePoint Enterprise Customers• Using SharePoint for years – perhaps document oriented• Typically a larger organization >1000 employees• Big issues: Governance, Compliance, etc.• Trying to figure out what to do regarding Cloud

• New SMB SharePoint Customers• Small Budgets• Started with Office 365 – a strategic step for the business• Discovered SharePoint• View it as a collaboration platform – Intranet• Probably are using email and office (Excel) for processes• Looking for new ways to leverage the cloud to automate their business• Going full blast into the cloud

SP Marketplace Model - Rules

1. Must be 100% customizable by power business users2. Must use the same structure across modules for familiarity3. Must support all editions of SharePoint4. Must be able to upgrade to new SP versions dynamically5. Must be able to take advantage of 3rd Party web parts, app

parts.6. Continuous improvement using new MS Cloud Features7. KISS – Keep It Simple Stupid

SP Marketplace Model

Application Platform

JQuery ComponentsForm ProcessingRelated lists / librariesSP ServicesMisc Java Script Parts

Web PartsCharts,Tabs,…Cross Site ListsRoll-upsMapping, Weather, Social network links…

Third Party OtherIncoming EmailOutlook mail integrationRemindersData IntegrationYammer

Office App IntegrationExcel ServicesWord MergeLync Skydrive

SharePoint Apps Components

Standard Tasks Directory SyncTime Sheets / Check in –outOthers

Intranet Portal

EmployeeSelf Service

Dept Portal

TemplateHR IT Facili

tiesProjects

Customer

ServiceCRM

Learn More

Thank You

www.spmarketplace.com