iot, m2m: three events, three takeaways, three to-dos (iot & the connected device present)

25
Enterprise IoT: 3 To-dos 3 Events, 3 Takeaways, 3 To- dos January 30, 2014 Last Update: 3 Feb 2014 Reid Carlberg Director, Evangelism @ReidCarlberg in/ReidCarlberg

Upload: reidcarlberg

Post on 15-Jan-2015

1.794 views

Category:

Technology


0 download

DESCRIPTION

Yes, the IoT is upon us. But what do we need to do to make it come to life? I've attended three big events recently. I share what I learned and I offer three //todos. First presented at M2M Evolution in Miami, January 30, 2014

TRANSCRIPT

Page 1: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

Enterprise IoT: 3 To-dos

3 Events, 3 Takeaways, 3 To-dos January 30, 2014Last Update: 3 Feb 2014

Reid CarlbergDirector, Evangelism

@ReidCarlberg

in/ReidCarlberg

Page 2: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

I travel to events and talk to people about their work.

This is a summary of my recent findings.

Page 3: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

Safe Harbor

Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.

Every Salesforce presentation starts with a Safe Harbor.

Page 4: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

Who is Salesforce.com?

(Just in case.)

Page 5: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

#1 in Cloud Computing and CRM

#1 World’s #1CRM

Cloud Computing

2011

2012

2013

Market LeaderEnterprise,

MidMarket, SMB & Sales Force Automation

Innovation

Page 6: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

We’ve Been Talking About Connected Products For Years

Page 7: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

Connect with your customers in a whole new way

In fact, at Dreamforce 2013, we introduced a key concept:

Page 8: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

• Freezers contain genetic enzymes and are primary touch point with customers.• End-to-end customer service, sales, marketing & inventory app runs on Salesforce.• Mobile freezer app and telematics reporting built on Heroku and stored in Force.com.

Mobile Apps on Salesforce1 Platform Allow NEB to reach Scientists Through Connected Freezers

Watch on YouTube.

And we shared a great new story!

Page 9: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

Core Principal:

Behind Every Device Is a Customer.

Page 10: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

Three Events, Three Takeaways

Page 11: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

Event #1: The Connected Device Lab

Dreamforce 2013 DevZoneLab20k Enterprise Dev Attendees, 15 Partners, 21 Workshops,Arduinos, Raspberry Pis, ARM mbeds, sensors, actuators,

2 Product Launches,1 Open Source Robotics Library Release

Page 12: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

Takeaway #1: The Connected Device Lab

Enterprise devs are not IoT ready.Don’t get devices, sensors or business use cases.

Page 13: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

Event #2: ThingMonk

Produced by RedMonkLondon, ~20 Presentations (all on YouTube),

Maker/Hacker focused: Lots of really creative thinking.Best question: “Does your project deserve to exist?”

Page 14: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

Takeaway #2: ThingMonk

Makers are not enterprise ready.Don’t get scale, monetization, long term.

Page 15: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

Event #3: Executive Lab

Global Organization, C LevelReally intelligent, extremely business savvy.

Focus on highly polished products.

Page 16: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

Takeaway #3: Executive Lab

Executives don’t quite understand possibilities.

Love “IoT”, pretty vague on the details.

Page 17: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

Summary:

Developers aren’t ready. Makers aren’t ready.

Executives aren’t ready.

Page 18: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

Which really means:

It’s a GREAT time

to be in the IoT business!

Page 19: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

Three To-dos

Page 20: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

#1 To-do: Play

Hands on experience with consumer productsdrives alignment. Tie features to business value.

Page 21: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

#2 To-do: Hack

Hacking drives engagement, interest and curiosity. Curious developers make incredible progress.

Page 22: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

#3 To-do: Make

Make habit of turning ideas into prototypes and iterating.Looks for internal interest, hire unusual candidates.

Page 23: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

Get to Know Our Partners

Page 25: IoT, M2M: Three Events, Three Takeaways, Three To-Dos (IoT & The Connected Device Present)

@ReidCarlberg ~ [email protected]