Value proposition of salesforce force com at yale university
This presentation is the property of its rightful owner.
Sponsored Links
1 / 11

Value Proposition of Salesforce & Force at Yale University PowerPoint PPT Presentation


  • 210 Views
  • Uploaded on
  • Presentation posted in: General

Value Proposition of Salesforce & Force.com at Yale University. Yale University Office of the CTO. Andrew Newman 11-September-2014. Salesforce – The Dream. Rapidly Developed, Inexpensive Customized Applications Low Cost Product Lifecycle

Download Presentation

Value Proposition of Salesforce & Force at Yale University

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Value proposition of salesforce force com at yale university

Value Proposition of Salesforce & Force.comat Yale University

Yale University Office of the CTO

Andrew Newman

11-September-2014


Salesforce the dream

Salesforce – The Dream

Rapidly Developed, Inexpensive Customized Applications

Low Cost Product Lifecycle

Performance, Reliability, Availability – Someone Else’s Problem

Zero Capital Footprint

Upgrades, New Features, Keeping up with Modern Application Expectations – Someone Else’s Problem


Early explorations

Early Explorations

The Totally Custom Small Footprint Application.

The Tailored Sales/Service (CRM-ish) Business Need.

The Rise of the “Citizen Developer”

Should Optimizing Subscription Costs Unduly Influence Application Design / Architecture?

Are we OK With “Citizen Data Architects?”


Recommendations 1 year ago

Recommendations – 1 Year Ago

  • Recommendations for “Org” Structure

  • Recommendations for Development Platforms

    • Use the technology that the anchor product uses

    • …Or Use the technology that the anchor product vendor recommends… so with Workday that would be???

  • How much of our expertise / standards can we preserve?

    • Version Control?

    • Continuous Integration?

    • Migration / Backout methodologies?


Present day time for analysis

Present Day – Time for Analysis

  • Examining Three Models

    • Pure Configuration of ServiceDesk or CRM Application

    • Greenfield Force.com Application

    • Hybrid Model – Professional Engineer Partners with Citizen Developer

  • Need Case Studies for Hybrid Model

    • What approaches / division of labor works?

    • Who can document the efficiency gains and/or savings?

    • What does a hybrid developer contract look like? SoW items? Warranty?


Present day looking at demand

Present Day – Looking at Demand

Score


Looking at demand the questions

Looking at Demand – The Questions

  • Does the candidate solution “look” like:

    • A service desk?

    • A CRM?

    • A generic intake queue?

  • Does the candidate solution “look” like:

    • A small departmental application with little need for institutional data?

    • A small focused user base?

  • Does the candidate solution “look” like:

    • “Something” that is amenable to a hybrid development approach?


What can central it provide the community

What Can Central IT Provide the Community

  • Few Users in More Than 1 Org

  • Common Implementation of Roles & Entitlements

  • Each Satellite Supports Applications Common to a Constituent Group


Hey what about workday anyway

Hey! What About Workday Anyway?

So… Is Force.comultimately the extension platform for Workday?

How do we capture the benefits of Force.com without obliging the data to be co-located in the Salesforce ecosystem?

What does a Force.com set of Workday extensions look like from a development lifecycle efficiency point of view?


The development model reconsidered

The Development Model Reconsidered

… Let’s not celebrate quite yet!

External App

External App

JDBC / ODBC / SQLnet etc…

WSDL / REST

Web Svcs

UI / UX

UI / UX

Application Business Logic

Application Business Logic

ORM Mappings

Relational Data Store

Relational Data Store


Good better best for integration libraries

“Good / Better / Best” for Integration Libraries

Good– Core Workday objects available via Web Services and “Wrapped”

Better – Salesforce Customizable UI Components Extended to Use Wrapped Workday Object/Services

Best – Core Workday objects Appear (as if by magic) As Though the Data is Local to Workday


  • Login