WO2017125777A1

WO2017125777A1 - Enterprise metric visualization platform

Info

Publication number: WO2017125777A1
Application number: PCT/IB2016/000169
Authority: WO
Inventors: Warwick CHAI
Original assignee: Bnw Consulting Pty, Ltd.
Priority date: 2016-01-22
Filing date: 2016-01-22
Publication date: 2017-07-27

Abstract

Embodiments of the present disclosure may provide a visualization tools for enterprise software. Embodiments may be comprised of a plug-in for an enterprise software that collects various data and metrics. Data and metrics to be collected, as well as their sources, may be selected by users. Such collected data may be further processed and presented to the user in a useful display. The useful display may include, for example, charts, graphs, and tables.

Description

TITLE

ENTERPRISE METRIC VISUALIZATION PLATFORM

FIELD OF DISCLOSURE

The present disclosure generally relates to enterprise software metric visualization.

BACKGROUND

Organizations often use enterprise software, such as, for example, SAP, to assist with various functions, such as, for example, inventory maintenance and human resource management. However, enterprise software like SAP provides minimal visibility as to the performance of the software. For example, SAP does not provide users, in a user-friendly form, with information pertaining to the software load, the number of users logged in, and the response time. FIG. PI illustrates some metrics as provided by SAP. FIG. P2 illustrates a screenshot showing a graph presenting the amount of data being collected as provided by SAP. Conventionally, when a user wants to know more about the software performance, often when the software is slow or when the user is encountering glitches, the user hires service providers to assist in traversing the data to visualize metrics and relevant information. This is an expensive and time-consuming process.

Further, SAP, over time, aggregates certain metrics data after a certain amount of time has passed, which reduces data resolution, and eventually deletes such data. FIG. P3 illustrates data collected over the course of 6-hour intervals from the previous day, while P4 illustrates data aggregated over the course of an entire month with lost resolution. The lost resolution prevents users from, for example, searching archives to see if there is a consistent history of upload errors at a given time for previous months, thereby preventing users from diagnosing issues.

BRIEF OVERVIEW

An enterprise software metric visualization platform may be provided. This brief overview is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This brief overview is not intended to identify key features or essential features of the claimed subject matter. Nor is this brief overview intended to be used to limit the claimed subject matter's scope.

Both the foregoing brief overview and the following detailed description provide examples and are explanatory only. Accordingly, the foregoing brief overview and the following detailed description should not be considered to be restrictive. Further, features or variations may be provided in addition to those set forth herein. For example, embodiments may be directed to various feature combinations and sub-combinations described in the detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate various embodiments of the present disclosure. The drawings contain representations of various trademarks and copyrights owned by the Applicants. In addition, the drawings may contain other marks owned by third parties and are being used for illustrative purposes only. All rights to various trademarks and copyrights represented herein, except those belonging to their respective owners, are vested in and the property of the Applicants. The Applicants retain and reserve all rights in their trademarks and copyrights included herein, and grant permission to reproduce the material only in connection with reproduction of the granted patent and for no other purpose.

Furthermore, the drawings may contain text or captions that may explain certain embodiments of the present disclosure. This text is included for illustrative, non-limiting, explanatory purposes of certain embodiments detailed in the present disclosure. In the drawings:

FIG. PI illustrates some metrics as provided by SAP;

FIG. P2 illustrates a screenshot showing a graph presenting the amount of data being collected as provided by SAP;

FIG. P3 illustrates a screenshot consistent with embodiments of the present disclosure for a time profile of recent data collection and processing;

FIG. P4 illustrates a screenshot showing a time profile of long-passed data collection and processing with resolution aggregated out;

FIG. 1 illustrates a platform consistent with embodiments of the present disclosure; FIG. 2 shows some of the code enabling embodiments of the present disclosure; FIG. 3 illustrates a fingerprint mechanism provided by SAP;

FIG. 4 is a flow chart of a method for providing an enterprise software visualization platform;

FIG. 5 illustrates a dashboard for metric and interval selection;

FIG. 6 illustrates a dashboard for selecting more metric parameters;

FIG. 7 illustrates a dashboard for selecting restrictions, including restriction to a specific platform, priority order and other conditions;

FIG. 8 illustrates a dashboard for selecting a location to send collected data;

FIG. 9 illustrates a log of metrics being collected;

FIG. 10 illustrates specific details of a metric being logged;

FIG. 11 illustrates an example of a display that may be provided to the user;

FIG. 12 illustrates another example of a display that may be provided to the user; FIG. 13 illustrates yet another example of a display that may be provided to the user; FIG. 14 illustrates a dashboard comprising some charts that may be provided to the user;

FIG. 15 illustrates a dashboard comprising a chart illustrating various processes;

FIG. 16 illustrate a dashboard comprising charts displaying relevant amounts of time per request as well as database size;

FIG. 17 illustrate a dashboard comprising additional charts displaying relevant amounts of time per request as well as database size;

FIG. 18 illustrates a dashboard comprising a chart displaying times for certain actions over certain periods of time. FIG. 19 illustrates a map of geographical region, as it may appear on a dashboard; and

FIG. 20 is a block diagram of a system including a computing device for performing the method of FIG. 4. DETAILED DESCRIPTION

As a preliminary matter, it will readily be understood by one having ordinary skill in the relevant art that the present disclosure has broad utility and application. As should be understood, any embodiment may incorporate only one or a plurality of the above-disclosed aspects of the disclosure and may further incorporate only one or a plurality of the above- disclosed features. Furthermore, any embodiment discussed and identified as being

"preferred" is considered to be part of a best mode contemplated for carrying out the embodiments of the present disclosure. Other embodiments also may be discussed for additional illustrative purposes in providing a full and enabling disclosure. Moreover, many embodiments, such as adaptations, variations, modifications, and equivalent arrangements, will be implicitly disclosed by the embodiments described herein and fall within the scope of the present disclosure.

Accordingly, while embodiments are described herein in detail in relation to one or more embodiments, it is to be understood that this disclosure is illustrative and exemplary of the present disclosure, and are made merely for the purposes of providing a full and enabling disclosure. The detailed disclosure herein of one or more embodiments is not intended, nor is to be construed, to limit the scope of patent protection afforded in any claim of a patent issuing here from, which scope is to be defined by the claims and the equivalents thereof. It is not intended that the scope of patent protection be defined by reading into any claim a limitation found herein that does not explicitly appear in the claim itself.

Thus, for example, any sequence(s) and/or temporal order of steps of various processes or methods that are described herein are illustrative and not restrictive.

Accordingly, it should be understood that, although steps of various processes or methods may be shown and described as being in a sequence or temporal order, the steps of any such processes or methods are not limited to being carried out in any particular sequence or order, absent an indication otherwise. Indeed, the steps in such processes or methods generally may be carried out in various different sequences and orders while still falling within the scope of the present invention. Accordingly, it is intended that the scope of patent protection is to be defined by the issued claim(s) rather than the description set forth herein.

Additionally, it is important to note that each term used herein refers to that which an ordinary artisan would understand such term to mean based on the contextual use of such term herein. To the extent that the meaning of a term used herein— as understood by the ordinary artisan based on the contextual use of such term— differs in any way from any particular dictionary definition of such term, it is intended that the meaning of the term as understood by the ordinary artisan should prevail.

Regarding applicability of 35 U.S.C. §112, Tf6, no claim element is intended to be read in accordance with this statutory provision unless the explicit phrase "means for" or "step for" is actually used in such claim element, whereupon this statutory provision is intended to apply in the interpretation of such claim element. Furthermore, it is important to note that, as used herein, "a" and "an" each generally denotes "at least one," but does not exclude a plurality unless the contextual use dictates otherwise. When used herein to join a list of items, "or" denotes "at least one of the items," but does not exclude a plurality of items of the list. Finally, when used herein to join a list of items, "and" denotes "all of the items of the list."

The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar elements. While many embodiments of the disclosure may be described, modifications, adaptations, and other implementations are possible. For example, substitutions, additions, or modifications may be made to the elements illustrated in the drawings, and the methods described herein may be modified by substituting, reordering, or adding stages to the disclosed methods. Accordingly, the following detailed description does not limit the disclosure. Instead, the proper scope of the disclosure is defined by the appended claims. The present disclosure contains headers. It should be understood that these headers are used as references and are not to be construed as limiting upon the subjected matter disclosed under the header.

The present disclosure includes many aspects and features. Moreover, while many aspects and features relate to, and are described in, the context of enterprise metrics tracking, embodiments of the present disclosure are not limited to use only in this context.

I. PLATFORM OVERVIEW

Consistent with embodiments of the present disclosure, an enterprise software visualization platform may be provided. This overview is provided to introduce a selection of concepts in a simplified form that are further described below. This overview is not intended to identify key features or essential features of the claimed subject matter. Nor is this overview intended to be used to limit the claimed subject matter's scope. The enterprise software metric visualization platform may be used by individuals or companies to visualize business enterprise software metrics.

Embodiments of the present disclosure may comprise a software plug-in that interfaces with enterprise software. The plug-in may be configured by the user to provide the desired metrics for visualization.

First, the platform may enable users to pick specific metrics to be collected. For example, embodiments of the present disclosure may be configured to collect software load, number of users logged in, and response time metrics. The platform may further receive user specifications such as, for example, intervals between data collection, platform restrictions, and data archiving preferences. Next, the platform may collect metrics based on user specifications. The platform may then display the collected metrics to the user. For example, the platform may display charts, graphs and tables. The displayed information may be presented on a user dashboard. The dashboard as well as displayed charts, graphs and tables may be built into the platform or customized by the user. The tables may be configured to be searched, sorted and manipulated by the user.

Both the foregoing overview and the following detailed description provide examples and are explanatory only. Accordingly, the foregoing overview and the following detailed description should not be considered to be restrictive. Further, features or variations may be provided in addition to those set forth herein. For example, embodiments may be directed to various feature combinations and sub-combinations described in the detailed description.

II. PLATFORM CONFIGURATION

FIG. 1 illustrates one possible operating environment through which a platform consistent with embodiments of the present disclosure may be provided. By way of non- limiting example, an enterprise software metric visualization platform 100 may be hosted on a centralized server 110, such as, for example, a cloud computing service. A user 105 may access platform 100 through a software application. The software application may be embodied as, for example, but not be limited to, a website, a web application, a desktop application, and a mobile application compatible with a computing device 2100. One possible embodiment of the software application may be provided by a suite of products and services provided by BNW Consulting Ltd. FIG. 2 shows some of the code enabling embodiments of the present disclosure. Software may be fingerprinted such that the business enterprise software may recognize when the software is being used. FIG. 3 illustrates a fingerprint mechanism 305 provided by SAP.

As will be detailed with reference to FIG. 21 below, the computing device through which the platform may be accessed may comprise, but not be limited to, for example, a desktop computer, laptop, a tablet, or mobile telecommunications device. As will be detailed with reference to FIG. 21 below, the computing device through which the platform may be accessed may comprise, but not be limited to, for example, a desktop computer, laptop, a tablet, or mobile telecommunications device.

III. PLATFORM OPERATION FIG. 4 is a flow chart setting forth the general stages involved in a method 400 consistent with an embodiment of the disclosure for providing an enterprise software metric visualization platform 100. Method 400 may be implemented using a computing device 2100 as described in more detail below with respect to FIG. 21.

Although method 400 has been described to be performed by platform 100, it should be understood that computing device 2100 may be used to perform the various stages of method 400. Furthermore, in some embodiments, different operations may be performed by different networked elements in operative communication with computing device 2100. For example, server 110 may be employed in the performance of some or all of the stages in method 400. Moreover, server 110 may be configured much like computing device 2100.

Although the stages illustrated by the flow charts are disclosed in a particular order, it should be understood that the order is disclosed for illustrative purposes only. Stages may be combined, separated, reordered, and various intermediary stages may exist.

Accordingly, it should be understood that the various stages illustrated within the flow chart may be, in various embodiments, performed in arrangements that differ from the ones illustrated. Moreover, various stages may be added or removed from the flow charts without altering or deterring from the fundamental scope of the depicted methods and systems disclosed herein. Ways to implement the stages of method 400 will be described in greater detail below.

Method 400 may begin at starting block 405 and proceed to stage 410 where platform 100 may receive user selections for metrics to be collected. For example, platform 100 may provide the user with a dashboard that enables the user to select which metrics to collect 505 and intervals between data collection 510, as illustrated in FIG. 5. FIG. 5 illustrates such dashboard for such metric and interval selection. Platform 100 may provide the user with a dashboard that enables the user to select other metric collection parameters such as, for example, archive parameters (e.g., archive duration). FIG. 6 illustrates a dashboard for selecting such other parameters. Platform 100 may provide the user with a dashboard that enables the user to select further restrictions, including restriction to a specific platform 710, priority order 705 and other conditions. FIG. 7 illustrates such a dashboard. Once all restrictions are met, the platform may execute a function, (e.g., collect data, and archive data).

From stage 410, where platform 100 receives user selections for metrics to be collected, method 400 may advance to stage 420 where platform 100 may collect, store and transmit data. For example, platform 100 may collect data as prescribed by the user selections and transmit data to a specified URL 805, as shown in FIG. 8. Metrics being logged may be provided to the user. FIG. 9 illustrates a log of metrics being collected. Collected metrics may further be embedded with metadata such as, for example, but not limited to, date and time of collection and metric source. Details, such as collection source 905 and collection parameters 910 may further be provided to the user. Further, details of each metric may be provided to the user. FIG. 10 illustrates specific details of a metric being logged. FIG. 11 illustrates an ability to define a group of metrics being logged.

A user may be provided with the ability to start, stop, and pause archiving. Further, the user may be provided with the ability to archive data to keep records as well as view the data log. Once platform 100 collects, stores and transmits data in stage 420, method 400 may continue to stage 430 where platform 100 may process and display data in a useable format. For example, platform 100 may provide a display of charts, graphs, tables, and relevant data points for the user to interpret. The displays may comprise a dashboard. Such dashboard may enable a plurality of functionalities for the user, including, for example, sharing, printing, and manipulation of data displays. FIGs. 12-21 illustrate examples of displays that may be provided to the user. The displays may be pre-set or customizable.

The FIGURES are meant to be illustrative of potential embodiments only, and not limit embodiments. FIG. 12 illustrates a dashboard 1100 comprising a chart displaying a number of users versus time, chart displaying a number of users for each of a number of users cancelled, a number of expired users, and a number of locked users, versus time, a chart displaying a number of lock entries versus time, and chart displaying a number of RFC in error versus time. FIG. 13 illustrates the dashboard 1100 in FIG. 12 as well as tables including the number of update task entries, the number of files in each directory, and the channels with associated information. FIG. 14 illustrates a dashboard 1300 comprising a chart displaying CPU utilization versus time, a chart displaying a number of unique users versus time, a chart showing a hit rate percent of nametab buffers, a hit rate percent of programs, CUA, etc., a chart showing a number of dialog steps versus time, and a chart illustrating a relative breakdown of dialog steps by type. FIG. 15 illustrates a dashboard 1400 comprising some charts from FIG. 14 as well as a chart displaying memory usage versus time, a chart displaying memory pressure versus time, a chart showing relative memory usage versus time, a chart showing network transfer rates versus time, and a chart showing relative disc response time. FIG. 16 illustrates a dashboard 1500, comprising a chart illustrating process utilization percent by type versus time and a chart illustrating dialog database time, response time, and network time versus time. FIGs. 17-18 illustrate a dashboard 1600, comprising charts displaying relevant amounts of time per request as well as database size. FIG. 19 illustrates a dashboard comprising a chart displaying times for certain actions over certain periods of time. FIG. 20 illustrates a map of Australia, as it may appear on a dashboard.

Once platform 100 provides a display of data in a useable format in stage 430, method 400 may then end at stage 440.

IV. PLATFORM ARCHITECTURE

The enterprise software metric visualization platform 100 may be embodied as, for example, but not be limited to, a website, a web application, a desktop application, and a mobile application compatible with a computing device. The computing device may comprise, but not be limited to, a desktop computer, laptop, a tablet, or mobile

telecommunications device. Moreover, platform 100 may be hosted on a centralized server, such as, for example, a cloud computing service. Although method 400 has been described to be performed by a computing device 2100, it should be understood that, in some embodiments, different operations may be performed by different networked elements in operative communication with computing device 2100.

Embodiments of the present disclosure may comprise a system having a memory storage and a processing unit. The processing unit coupled to the memory storage, wherein the processing unit is configured to perform the stages of method 400. FIG. 21 is a block diagram of a system including computing device 2100. Consistent with an embodiment of the disclosure, the aforementioned memory storage and processing unit may be implemented in a computing device, such as computing device 2100 of FIG. 21. Any suitable combination of hardware, software, or firmware may be used to implement the memory storage and processing unit. For example, the memory storage and processing unit may be implemented with computing device 2100 or any of other computing devices 2118, in combination with computing device 2100. The aforementioned system, device, and processors are examples and other systems, devices, and processors may comprise the aforementioned memory storage and processing unit, consistent with embodiments of the disclosure.

With reference to FIG. 21, a system consistent with an embodiment of the disclosure may include a computing device, such as computing device 2100. In a basic configuration, computing device 2100 may include at least one processing unit 2102 and a system memory 2104. Depending on the configuration and type of computing device, system memory 2104 may comprise, but is not limited to, volatile (e.g. random access memory (RAM)), non-volatile (e.g. read-only memory (ROM)), flash memory, or any combination. System memory 2104 may include operating system 2105, one or more programming modules 2106, and may include a program data 2107. Operating system 2105, for example, may be suitable for controlling computing device 2100's operation. In one embodiment, programming modules 2106 may include a selective data collection application 2120. Furthermore, embodiments of the disclosure may be practiced in conjunction with a graphics library, other operating systems, or any other application program and is not limited to any particular application or system. This basic configuration is illustrated in FIG. 21 by those components within a dashed line 2108.

Computing device 2100 may have additional features or functionality. For example, computing device 2100 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in FIG. 21 by a removable storage 2109 and a nonremovable storage 2110. Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. System memory 2104, removable storage 2109, and nonremovable storage 2110 are all computer storage media examples (i.e., memory storage.) Computer storage media may include, but is not limited to, RAM, ROM, electrically erasable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store information and which can be accessed by computing device 2100. Any such computer storage media may be part of device 2100. Computing device 2100 may also have input device(s) 2112 such as a keyboard, a mouse, a pen, a sound input device, a touch input device, etc. Output device(s) 2114 such as a display, speakers, a printer, etc. may also be included. The aforementioned devices are examples and others may be used.

Computing device 2100 may also contain a communication connection 2116 that may allow device 2100 to communicate with other computing devices 2118, such as over a network in a distributed computing environment, for example, an intranet or the Internet. Communication connection 2116 is one example of communication media. Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The term "modulated data signal" may describe a signal that has one or more characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared, and other wireless media. The term computer readable media as used herein may include both storage media and communication media.

As stated above, a number of program modules and data files may be stored in system memory 2104, including operating system 2105. While executing on processing unit 2102, programming modules 2106 (e.g., selective data collection application 2120) may perform processes including, for example, one or more of method 400's stages as described above. The aforementioned process is an example, and processing unit 2102 may perform other processes. Other programming modules that may be used in

accordance with embodiments of the present disclosure may include electronic mail and contacts applications, word processing applications, spreadsheet applications, database applications, slide presentation applications, drawing or computer-aided application programs, etc.

Generally, consistent with embodiments of the disclosure, program modules may include routines, programs, components, data structures, and other types of structures that may perform particular tasks or that may implement particular abstract data types. Moreover, embodiments of the disclosure may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor- based or programmable consumer electronics, minicomputers, mainframe computers, and the like. Embodiments of the disclosure may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

Furthermore, embodiments of the disclosure may be practiced in an electrical circuit comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors. Embodiments of the disclosure may also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to mechanical, optical, fluidic, and quantum technologies. In addition, embodiments of the disclosure may be practiced within a general purpose computer or in any other circuits or systems.

Embodiments of the disclosure, for example, may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process. The computer program product may also be a propagated signal on a carrier readable by a computing system and encoding a computer program of instructions for executing a computer process. Accordingly, the present disclosure may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.). In other words, embodiments of the present disclosure may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system. A computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific computer-readable medium examples (a non-exhaustive list), the computer-readable medium may include the following: an electrical connection having one or more wires, a portable computer diskette, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, and a portable compact disc read-only memory (CD-ROM). Note that the computer-usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.

Embodiments of the present disclosure, for example, are described above with reference to block diagrams and/or operational illustrations of methods, systems, and computer program products according to embodiments of the disclosure. The

functions/acts noted in the blocks may occur out of the order as shown in any flowchart. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.

While certain embodiments of the disclosure have been described, other

embodiments may exist. Furthermore, although embodiments of the present disclosure have been described as being associated with data stored in memory and other storage mediums, data can also be stored on or read from other types of computer-readable media, such as secondary storage devices, like hard disks, solid state storage (e.g., USB drive), or a CD-ROM, a carrier wave from the Internet, or other forms of RAM or ROM. Further, the disclosed methods' stages may be modified in any manner, including by reordering stages and/or inserting or deleting stages, without departing from the disclosure.

All rights including copyrights in the code included herein are vested in and the property of the Applicant. The Applicant retains and reserves all rights in the code included herein, and grants permission to reproduce the material only in connection with reproduction of the granted patent and for no other purpose.

V. CLAIMS

While the specification includes examples, the disclosure's scope is indicated by the following claims. Furthermore, while the specification has been described in language specific to structural features and/or methodological acts, the claims are not limited to the features or acts described above. Rather, the specific features and acts described above are disclosed as example for embodiments of the disclosure.

Insofar as the description above and the accompanying drawing disclose any additional subject matter that is not within the scope of the claims below, the disclosures are not dedicated to the public and the right to file one or more applications to claims such additional disclosures is reserved.

Although very narrow claims are presented herein, it should be recognized the scope of this disclosure is much broader than presented by the claims. It is intended that broader claims will be submitted in an application that claims the benefit of priority from this application.

Claims

I CLAIM THE FOLLOWING:

1. A method comprising:

receiving a selection of metrics to be collected from an enterprise software application;

collecting the selected metrics;

processing the collected metrics to ascertain data; and

displaying the data based on the collected metrics to a user, wherein displaying the data comprises displaying the data in a customizable user interface displaying various widgets for different data sets.

2. The method of Claim 1, wherein receiving a selection of metrics to be collected from an enterprise software application comprises receiving a selection of metrics to be collected from SAP.

3. The method of Claim 1, further comprising receiving a selection of parameters for refining metric collection.

4. The method of Claim 1, wherein receiving a selection of parameters for refining metric collection comprises receiving a selection of at least one of the following: a platform restriction, and an interval between data collection.

5. The method of Claim 1, further comprising archiving the collected metrics.

6. The method of Claim 5, further comprising receiving at least one of the following from the user: an archive duration, and an interval between data archiving.

7. The method of Claim 5 further comprising receiving at least one of the following commands from the user:

Start archiving the collected metrics,

Pause archiving the collected metrics, and

Stop archiving the collected metrics.

8. The method of Claim 1, wherein displaying metrics to the user comprises displaying at least one of the following: a chart, a graph, and a table.

9. The method of Claim 8, wherein the table is configured to be at least one of the following: filtered, searched and sorted.

10. The method of Claim 1, further comprising embedding the collected metrics with metadata.

11. The method of Claim 10, wherein embedding the collected metrics with the

metadata comprises embedding at least one of the following: a date collected, a time collected, and a collection source.

12. The method of Claim 1, further comprising transmitting the collected data.

13. The method of Claim 12, wherein transmitting the collected data comprises

transmitting the collected data to a prescribed URL.

14. The method of Claim 1, further comprising providing a software fingerprint for tracking a software license associated with the collection and display of metrics and data.

15. A computer readable medium comprising a set of instructions which when executed performs a method comprising:

collecting the selected metrics;

processing the collected metrics to ascertain data; and

displaying the data to a user as grouped graphical representations, the grouped graphical representations comprising datasets in a user interface custom selected by a user.

16. The computer readable medium of Claim 15, which when executed performs a

method further comprising at least one of the following:

receiving a selection of parameters for refining metric collection; embedding the collected metrics with metadata;

archiving the collected metrics; and

transmitting the collected metrics.

17. The computer readable medium of Claim 15, which when executed performs a

method further comprising receiving a software fingerprint for tracking a software license.

18. A system comprising:

A memory storage; and

A processing unit coupled with the memory storage, wherein the processing unit is operative to:

receiving a selection of metrics to be collected from an enterprise software application,

collecting the selected metrics,

processing the collected metrics; and

displaying a graphical representation of the collected metrics to a user.

19. The system of Claim 16, wherein the processing unit is further operative to:

archiving the collected metrics; and

transmitting the collected metrics.

20. The system of Claim 16, wherein the processing unit is further operative to

receiving a software fingerprint for tracking a software license.