Difference between revisions of "IoT/M2MIWG/M2M Scenarios"
m (minor wording and capitalizaiton changes)
m (Webmaster.eclipse.org moved page Machine-to-Machine/M2MIWG/M2M Scenarios to Iot/M2MIWG/M2M Scenarios)
Revision as of 10:04, 4 February 2014
- 1 M2M Scenarios
- 2 M2M Scenario Description Template
- 3 M2M Scenario Descriptions
- 3.1 M2M-Scenario-0001 - Food Refrigeration Unit Failure
- 3.2 M2M-Scenario-0002 - Food Refrigeration Unit Zone Control
- 3.3 M2M-Scenario-0003 - Fitting Refrigeration Unit Information Into a Multiple Producer/Consumer Model
The Machine to Machine (M2M) space combines systems from the embedded space and the enterprise/cloud space. This page catalogs example scenarios from the M2M space that capture combined overall M2M system requirments that may not traditionally exist in either the embedded space or the enterprise/cloud space.
Scenarios are intended to be high level descriptions which are characteristic of M2M business needs. The goals of this scenario work are to:
1) Document key needs obstacles, and inhibitors, both technical and market based, that the Eclipse M2M community can address with architecture and projects.
2) Document requirements to be addressed by follow-on architecture and open source project deliverables
It is expected that specific M2M Problem Descriptions will reference these scenarios, identifying technical issues and requirements.
Together, the problems and scenarios are also meant to serve as an educational tool for designers, developers and architects who are new to M2M and as a reference during development of M2M technologies at Eclipse.
M2M Scenario Description Template
Please refer to this template documentation.
M2M Scenario Descriptions
M2M-Scenario-0001 - Food Refrigeration Unit Failure
A regional office for a food store chain wants to detect increasing temperatures in their store's meat freezers and delivery vehicles. Upon detecting that the temperature has increased above a specified threshold, a group of analytic processes will access the system for additional data such as the customer activity level (indicator of the doors opening and closing a lot), on/off cycle frequency of the refrigeration compressor, and the recent history of refrigerant temperature values. Based on the outcomes of the analytic processes, a root cause will be determined and appropriate actions to remedy the situation will be started: maintenance technician dispatch, notification to store manager, re-supply, etc.
Referenced by problems
M2M-Scenario-0002 - Food Refrigeration Unit Zone Control
A regional office for a food store chain wants to control and monitor temperatures in each freezer unit within a store. There are many freezer units within each store and many stores within the region. The freezer units are controlled using a legacy point-to-point, request-response, serial protocol from an embedded computer. The embedded computer can simultaneously communicate with many freezer units, up to the maximum number of onboard serial ports. The embedded computers are connected to the in-store network and accessible from the regional office.
Referenced by problems
M2M-Scenario-0003 - Fitting Refrigeration Unit Information Into a Multiple Producer/Consumer Model
Solutions to scenarios 001 and 002 soon result in the business discovering that although the company is monitoring and managing increasing temperatures, the data could also provide valuable information and insight to other business units. It might also be discovered that other business units may have been able to provide input into the “application” that could help in the overall solution. For example, an upcoming sale will increase the level of activity so proactively decrease the temperature in anticipation of the event.
Because the original regional office application which was polling the freezer units did not anticipate having to share the data with multiple data consumers, the application developers and IT architects will have address sharing and access of the data by unanticipated new consumers and providers. They soon realize that writing additional application code for the regional office will unexpectedly require additional firmware having to be developed for the freezer control units. They now need to recommend that the cost effective to replace both the application and the freezer unit code to meet new and future business requirements.
Referenced by problems