Abstract: A method, system, and computer-readable medium for managing a work packet's life cycle, wherein the work packet is assembled in a software factory that creates custom software in a standardized manner, are presented. In one embodiment, the computer-implemented method comprises: defining a work packet to perform a sub-function of a custom software, wherein the work packet is a pre-stored, reusable, self-contained, discrete unit of software code; assembling the work packet; archiving the work packet in an asset repository; retrieving the work packet from the asset repository; and sending the work packet to an assembly line for consolidation with other work packets to create a custom software.

Abstract: A method, system, and computer-readable medium for managing a work packet's life cycle, wherein the work packet is assembled in a software factory that creates custom software in a standardized manner, are presented. In one embodiment, the computer-implemented method comprises: defining a work packet to perform a sub-function of a custom software, wherein the work packet is a pre-stored, reusable, self-contained, discrete unit of software code; assembling the work packet; archiving the work packet in an asset repository; retrieving the work packet from the asset repository; and sending the work packet to an assembly line for consolidation with other work packets to create a custom software.

Abstract: Methods, systems, and computer program products are provided for workflow decision management. Embodiments include maintaining a device state history; identifying a device usage pattern in dependence upon the device state history; identifying a workflow scenario in dependence upon the device usage pattern; identifying a workflow in dependence upon the workflow scenario; executing the workflow; identifying a user reaction to the execution of the workflow; identifying an unsuccessful device-controlling action in dependence upon the user reaction; and modifying the workflow in dependence upon the identified unsuccessful device-controlling action. Typical embodiment also include recording, as a representation of a negative user reaction, a determined change between the device attribute value set by executing the workflow and the current value of the device attribute in a user reaction log.

Abstract: Methods, systems, and computer program products are provided for workflow decision management. Embodiments include maintaining a device state history; identifying a device usage pattern in dependence upon the device state history; identifying a workflow scenario in dependence upon the device usage pattern; identifying a workflow in dependence upon the workflow scenario; executing the workflow including sending a message to a device to administer at least one value of an attribute of the device; and logging the message. Logging the message may be carried out by recording in a message log message information describing the message sent to the device.

Abstract: Methods, systems, and products are provided for workflow decision management. Embodiments include maintaining a device state history; identifying a plurality of device usage patterns in dependence upon the device state history; identifying a plurality of workflow scenarios in dependence upon the device usage patterns; determining a workflow administration capacity in dependence upon the plurality of workflow scenarios; identifying a plurality of workflows in dependence upon the workflow scenario; executing the plurality of workflows in dependence upon the workflow administration capacity.

Abstract: Methods, systems, and products are provided for intermediate message invalidation that include receiving, to an intermediate message validation service, a message to be forwarded to a device to administer at least one value of an attribute of the device; determining, by the intermediate message validation service, that the message is invalid; and terminating, by the intermediate message validation service, the invalid message. Embodiments may also include notifying a system administrator that the message is invalid.

Abstract: Methods, systems, and computer program products are provided for workflow decision management. Embodiments include maintaining a device state history; identifying a device usage pattern in dependence upon the device state history; identifying a workflow scenario in dependence upon the device usage pattern; identifying a workflow in dependence upon the workflow scenario; executing the workflow including: sending, to an intermediate message validation service, a message to be forwarded to a device to administer at least one value of an attribute of the device; determining, by the intermediate message validation service, that the message is valid; and forwarding, by the intermediate message validation service, the valid message to the device.

Abstract: Methods, systems, and computer program products are provided for deriving a device usage scenario. Embodiments include maintaining a device state history; detecting a device usage pattern in dependence upon the device state history; detecting a device usage scenario in dependence upon the device usage pattern; and assigning a tolerance to the device usage scenario. Typical embodiments also include associating a workflow with the device usage scenario.

Abstract: Methods, systems, and computer program products are provided for workflow decision management. Embodiments typically include maintaining a device state history; identifying a device usage pattern in dependence upon the device state history; identifying a derived scenario in dependence upon the device usage pattern; and selecting a heuristic in dependence upon the derived scenario. In typical embodiments, the heuristic has a tolerance. Embodiments also include identifying a workflow in dependence upon the selected heuristic and executing the workflow in dependence upon the tolerance.

Abstract: Methods, systems, and computer program products are provided for workflow decision management. Embodiments typically include maintaining a device state history; identifying a device usage pattern in dependence upon the device state history; identifying a derived scenario in dependence upon the device usage pattern. In typical embodiments the derived scenario has a tolerance. Embodiments also include identifying a workflow in dependence upon the derived scenario; executing the workflow in dependence upon the tolerance; and identifying a user reaction to the execution of the workflow.

Abstract: Methods, systems, and computer program products are provided for workflow decision management. Embodiments include maintaining a device state history; identifying a device usage pattern in dependence upon the device state history; and identifying a derived scenario in dependence upon the device usage pattern. The derived scenario has a tolerance. Embodiments also include identifying a workflow in dependence upon the derived scenario and executing the workflow in dependence upon the tolerance.