Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

IoT/M2MIWG/M2M Scenarios

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. It is expected that specific 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.

M2M Scenario Description Template

The following is the template for an M2M Scenario Description.

  1. M2M Scenario Number - Incremental id number from Scenario list page for easy reference in other pages/docs.
  2. M2M Scenario Name - Descriptive name of the scenario
  3. M2M Scenario Description - Description of the scenario.
  4. Related M2M Scenario Numbers - Numbers of other scenarios that are closely related to this one.
  5. 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.

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



Back to the top