International Business Machines Corporation

Todd D Robinson

Stephen Michael Leonard

Rebecca E Lutz

Clinton Douglas

Srinivas Cheemalapati

Kevin W Hall

Jose Ramon Chavez, Jr

James D McKalko

Christopher Frank Codella

Hamza Yaswi

John R Rexroth

John A Rexroth

Manage a request for a computing service through a hub solution available on a network. The underlying network fabric is the communication bus between individual processes that make up a service request. A process orchestrator may publish an Internet Protocol (IP) address for service requests such as printing services, email services, Active Directory (AD) services and similar service requests. The process orchestrator may determine which processes are to be executed to complete the service request and offload the processes to an available computing resources on the network. Examples of computing resources for each process include a virtual machine and a hardware based process engine. The process orchestrator may manage the processes and act as the primary point of interface for an endpoint host requesting the service.

Process as a network service hub

A computer-implemented method includes: receiving, by a computing device, sensor data relating to the attributes of garment worn by a user; determining, by the computing device, the attributes of the garment based on receiving the sensor data; determining, by the computing device, the user's shopping interest based on determining the attributes of the garment; generating, by the computing device, a targeted advertisement based on the user's shopping interest; and outputting, by the computing device, the targeted advertisement for display at a merchant facility.

Determining a user's shopping interests based on sensor data identifying attributes of the user's garment

A computer-implemented method comprises: generating, by a computing device, a computer-accessible corpus including evidence passage generation information; storing, by the computing device, the corpus; automatically generating, by the computing device, evidence passages that support a proposer's response to a customer's proposal request, wherein the evidence passages include a narrative identifying the proposer's capabilities to satisfy evaluation criteria in the proposal request, and wherein the narrative is based on customer-specific information, wherein the generating includes accessing and searching the corpus via an application programming interface (API); and outputting, by the computing device, the evidence passages as an electronic document that is editable via software running on a user device via a user interface.

Method and computer program product for automated generation and assembly of proposal elements

Alert management may include receiving, by a monitoring module from one or more disparate monitored sources, an alert, where the alert is a data structure that includes a plurality of fields; storing, by the monitoring module, the alert in a database; processing, by the monitoring module periodically at predefined intervals, the database, including identifying, in dependence upon a predefined ruleset, one or more alerts; storing, by the monitoring module, the identified alerts in a staging table, including creating, for each of the identified alerts, a primary key in dependence upon the fields of the identified alert; populating, by the monitoring module for each of the alerts stored in the staging table, one or more attribute fields of the alert in dependence upon the created primary key of the alert; and storing, by the monitoring module, the populated alerts in the database.

Alert management

A method, hardware device, and/or computer program product manages network resources. A cloud service provider hypervisor server that supports a cloud service provider hypervisor receives a cloud consumer's management information base (MIB) via an application program interface. The cloud consumer's MIB is a portable MIB that is capable of being loaded into multiple cloud service provider hypervisors. A trap receiver in the cloud service provider hypervisor server receives a Simple Network Management Protocol (SNMP) trap from a resource described by the cloud consumer's MIB. The SNMP trap is an SNMP message that describes an event in the resource. The cloud service provider hypervisor server transfers the SNMP trap to a cloud consumer without any interpretation of the SNMP trap by the cloud service provider hypervisor.

Network resources management by a cloud consumer

A distributed maintenance mode system and method includes receiving an indicator that a monitored system has entered maintenance mode. Trap data is received for the monitored system. It is determined whether the monitored system is in maintenance mode based on the indicator. The trap data is stored and a billable incident ticket is generated for the monitored system if it is determined that the monitored system is not in maintenance mode. The trap data is stored and no billable incident ticket is generated for the monitored system if it is determined that the monitored system is in maintenance mode.

Distributed maintenance mode control

A cloud service provider hypervisor server, which supports a cloud service provider hypervisor, receives a cloud consumer's management information base (MIB) from a cloud consumer. The cloud consumer's MIB is a portable MIB that is capable of being loaded into multiple cloud service provider hypervisors. A trap receiver in the cloud service provider hypervisor server receives a Simple Network Management Protocol (SNMP) trap from a resource described by the cloud consumer's MIB. The SNMP trap is an SNMP message, from the resource, that describes an event in the resource. The SNMP trap bypasses the cloud service provider hypervisor, such that the cloud service provider hypervisor server transfers the SNMP trap to the cloud consumer without any interpretation of the SNMP trap by the cloud service provider hypervisor.

A computer system and program product for managing events. Program instructions, respond to notification of an event, by determining if a problem ticket can be automatically generated for the event. If so, the program instructions make a request to generate the problem ticket. The program instructions determine if the problem ticket can be automatically generated based in whole or in part on (a) a type of the event and a customer who owns or uses a computer system in which the event occurred, (b) a type of the event, a customer who owns or uses a computer system in which the event occurred, and a severity of the event, (c) a type of the event, a customer who owns or uses a computer system in which the event occurred, and a magnitude of the event, or (d) a type of the event and whether other events of a same type occur at approximately a same time. If a determination is made that a problem ticket cannot be automatically generated, other program instructions notify or initiate notification of an operator and supply event information for the operator so that the operator can determine whether to generate a problem ticket.

Growing community of inventors

Frederick, CO, United States of America

Todd D Robinson