Enterprise IoT: Data in Context
Download as PPTX, PDF4 likes1,708 views
The document discusses Internet of Things (IoT) use cases and system architecture patterns for connecting IoT devices to Salesforce. It identifies three common IoT use case patterns: remote monitoring, instrumenting products, and new customer experiences. It then outlines five architecture patterns for connecting devices to Salesforce: anonymous, direct, buffered, gateway, and cloudy. The document promotes connecting IoT data to Salesforce to enable proactive customer engagement and service opportunities.
More Related Content
What's hot (20)
Similar to Enterprise IoT: Data in Context (20)
More from Pat Patterson (20)
Recently uploaded (20)
Enterprise IoT: Data in Context
- 1. Enterprise IoT: Data in Context Pat Patterson Developer Evangelist Architect @metadaddy [email protected]
- 2. 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.
- 4. The Internet of Things is about action.
- 5. 3 Use Case Patterns #1 Remote Monitoring • Replaces human inspection • Drives operational efficiency • Creates proactive service opportunity #2 Instrument Everything • Instrument products like apps • Drives understanding, performance and reliability • Creates proactive service opportunity #3 New Customer UX • Differentiate on deeper understanding • Drives more meaningful engagement • Creates proactive service opportunity
- 6. Create a Proactive Service Opportunity
- 7. Create a Proactive Engagement Opportunity
- 9. Five Enterprise IoT System Architecture Patterns Anonymous, Direct, Buffered, Gateway, Cloudy
- 10. Web2Case Anonymous: Report Problems with Anonymous APIs Possible. Easy to implement. No identity tied to request. One way.
- 11. In: OAuth2, REST Out: Streaming API, Outbound Messaging Direct: Phone Home w/ Standard Salesforce APIs Great for low volume requests dealing with high level objects. Requires Internet and integration user. Data treated as critical biz data.
- 12. Buffered: Phone Home with Custom APIs Great for high volume data. Heroku app figures out what’s important, sends that to Salesforce. Heroku Connect OAuth2, REST Custom API
- 13. Custom API Gateway: Devices to gateways to Salesforce Many lightweight devices talk to a more powerful gateway, gateway does the heavy lifting. Heroku Connect OAuth2, REST
- 14. In: OAuth2, REST Out: Streaming API, Outbound Messaging, REST endpoints Cloudy: Devices with integrated cloud. Devices tightly coupled with cloud services. Simplifies deployment but depends on ability to connect to network.
- 15. Business Process Heroku Connect OAuth2, REST Data Aggregation Abstract Architecture Device Gateway Device Signals & Transport Aggregation & Understanding
- 16. Business Process Heroku Connect OAuth2, REST The Internet of Things is about Action Data Aggregation Device Gateway Device Action!
- 17. Salesforce1 Data Services & Analytics Cloud “BigObject” ● HBase ● read only ● pilot in Summer “Data Pipelines” ● Apache Pig ● access all data ● pilot now “Wave” ● Analytic Cloud ● High performance ● pilot now