Abstract: In an example embodiment, multiple service requests are bundled into a single bundle via the vertical bundling of the service requests. This involves modularizing the services into subcomponents, identifying common processes and identifying the modularized processes that can run in parallel, then ranking the modularized processes to create an execution plan that minimizes downtime and also schedules downtime in a single contiguous block. The execution plan represents an optimized executable sequence that can contain both related and non-related services in a single bundle for fulfillment. It also represents a blueprint of services requested by the user from a service catalog.

Abstract: Status of software product(s) may be monitored through the cloud by Extract, Transform, Load (ETL) of status information, in the form of business process status indicators from customer tenants. Examples of such status indicators can include a backlog of tasks to be fulfilled, or a number of business documents present in specific processing states, which describe aspects of the business application and allow an understanding of the overall status of the monitored application. A data extractor component of a customer tenant may extract and transform the status indicators from a plurality of business documents. A data import framework of a central monitoring system may in turn employ mapping to condense that heterogeneous data into a monitoring-specific simplified status model.

Abstract: Embodiments of the present invention provide a central monitoring system for enterprise resource planning software hosted in a plurality of customer tenants. The central monitoring system may include software instructions that when executed by a computer processor, performs a method include extracting process status data from one or more customer tenants independently, transforming the extracted process status data to generate generalized status codes according to predetermined status codes, transferring the generated generalized status codes to a central monitoring system, loading the generated generalized status codes to the central monitoring system, and transforming the generalized status codes to monitoring-specific simplified status codes.

Abstract: Status of software product(s) may be monitored through the cloud by Extract, Transform, Load (ETL) of status information, in the form of business process status indicators from customer tenants. Examples of such status indicators can include a backlog of tasks to be fulfilled, or a number of business documents present in specific processing states, which describe aspects of the business application and allow an understanding of the overall status of the monitored application. A data extractor component of a customer tenant may extract and transform the status indicators from a plurality of business documents. A data import framework of a central monitoring system may in turn employ mapping to condense that heterogeneous data into a monitoring-specific simplified status model.