Events use Rules, Actuators, and Consumers to determine actions to be taken when values in Resources exceed or fall below definable threshold values.
Resource Collections are groups of Resources that Rules and Actuators read from and act on. In this context, Resources are always referred to via Resource Collections rather than individually.
Rules trigger on definable conditions based on sensor data reported from Resources. For example, a rule can trigger if the temperature crosses a threshold value. When this happens, an Actuator can be made to act on a Device. Using temperature as an example, DDM could trigger an automated system such as heating or air conditioning.
Actuators are activated by Rules and act on Devices to produce concrete results, allowing for automation of processes such as switch on/off lights, opening/closing doors, and starting heating/cooling systems.
Consumers are calls to systems outside of DDM that can be notified when a Rule has been triggered. Consumers can notify external systems by either defining an HTTP endpoint to be called or working with an Inbox/Outbox that supports occasionally connected consumers, email, SMS and more.