The Machine to Machine (M2M) space combines systems from the embedded space and the enterprise/cloud space.&nbsp;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. It is expected that sepcific [http://wiki.eclipse.org/Machine-to-Machine/M2MIWG/M2M-Problems M2M Problem Descriptions] will reference these scenarios. This catalog is meant to serve as an educational tool for developers and architects who are new to M2M and as a reference during development of M2M technologies at Eclipse.

+

The Machine to Machine (M2M) space combines systems from the embedded space and the enterprise/cloud space.&nbsp;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.

−

== M2M Scenario Description Template ==

+

Scenarios are intended to be high level descriptions which are characteristic of M2M business needs. The goals of this scenario work are to:

−

The following is the template for an M2M Scenario Description.

+

1) Document key needs obstacles, and inhibitors, both technical and market based, that the Eclipse M2M community can address with architecture and projects.

−

#M2M Scenario Number - Incremental id number from Scenario list page for easy reference in other pages/docs.

+

2) Document requirements to be addressed by follow-on architecture and open source project deliverables

−

#M2M Scenario Name - Descriptive name of the scenario

+

−

#M2M Scenario Description - Description of the scenario.

+

−

#Related M2M Scenario Numbers - Numbers of other scenarios that are closely related to this one.

+

−

#Referenced By M2M Problems - Numbers of M2M Problems that are specifically demonstrated by this scenario.

+

−

When creating a new M2M scenario description, please add it to the list of links below, claiming the next number in the sequence. Then add your scenario description to the descriptions section below.

+

It is expected that specific [http://wiki.eclipse.org/Machine-to-Machine/M2MIWG/M2M-Problems M2M Problem Descriptions] will reference these scenarios, identifying technical issues and requirements.

−

== M2M Scenario List ==

+

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.

Please refer to this [[Template:M2M_Scenario|template documentation]].

== M2M Scenario Descriptions ==

== M2M Scenario Descriptions ==

−

=== '''M2M-Scenario-001&nbsp;: Food Refrigeration Unit Failure''' ===

+

{{M2M_Scenario

+

+

| identifier = 0001

+

+

| name = Food Refrigeration Unit Failure

+

+

| description = 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.

+

+

| rel_problem1 = 0001

+

}}

+

{{M2M_Scenario

+

+

| identifier = 0002

+

+

| name = Food Refrigeration Unit Zone Control

+

+

| description = 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.

| description = 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.

−

A regional office for a food store chain wants to detect increasing temperatures in their store's meat freezers. 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 tech dispatch, notification to store manager, etc.

M2M Scenarios

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

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.

Related scenarios

None.

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.

Related scenarios

None.

Referenced by problems

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.