Grouping and display of logically defined reports

Abstract

Report views offer a user the ability to specify ancillary data views and also view that data in a scorecard viewing experience. A report view definition may be implemented as a metadata-based mapping of logical reports to physical reports for scorecards and KPIs. Reports are categorized based on their presentation size and/or type. Categorized report attributes included in the report view metadata are managed by a configuration UI. The report view metadata further includes schema, ordering capabilities, and mapping UI such as re-use of report views in multiple areas.

Description

BACKGROUND

Key Performance Indicators, also known as KPI or Key Success Indicators (KSI), help an organization define and measure progress toward organizational goals. Once an organization has analyzed its mission, identified all its stakeholders, and defined its goals, it needs a way to measure progress toward those goals. Key Performance Indicators are used to provide those measurements.

Scorecards are used to provide detailed and summary analysis of KPIs and aggregated KPIs such as KPI groups, objectives, and the like. Scorecard calculations are typically specific to a defined hierarchy of the above mentioned elements, selected targets, and status indicator schemes. Business logic applications that generate, author, and analyze scorecards are typically enterprise applications with multiple users (subscribers), designers, and administrators. It is not uncommon, for organizations to provide their raw performance data to a third party and receive scorecard representations, analysis results, and similar reports.

Even with the flexibility offered by a business scorecard building application, users may need the ability to view ancillary information to enable more intelligent consumption of the data offered with scorecard views. Without this functionality, users may be left to either speculate as to the importance or relevance of the information displayed or they may have to browse around outside of the scorecard environment for additional information to accurately assess the meaning and significance of the data presented.

It is with respect to these and other considerations that the present invention has been made.

SUMMARY

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended as an aid in determining the scope of the claimed subject matter.

Embodiments are directed to determining suitable visual presentation size for a logically defined report, categorizing a plurality of reports based on the visual presentation sizes, and providing a set of user interface controls to select and set properties of the plurality of reports such that the reports can be consumed based on their category. According to some embodiments, the reports may be associated with one or more elements of a scorecard and consumed by the scorecard application or associated reporting applications.

These and other features and advantages will be apparent from a reading of the following detailed description and a review of the associated drawings. It is to be understood that both the foregoing general description and the following detailed description are explanatory only and are not restrictive of aspects as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example computing operating environment;

FIG. 2 illustrates a system where example embodiments may be implemented;

FIG. 3 illustrates an example scorecard architecture according to embodiments;

FIG. 4 illustrates a screenshot of an example scorecard;

FIG. 5 illustrates a screenshot of a report view User Interface (UI) with a configuration task pane according to embodiments;

FIG. 6 is a diagram illustrating interactions between different components of a scorecard system for grouping reports in a scorecard viewer;

FIG. 7 illustrates a screenshot of an example report view definition UI in a scorecard application;

FIG. 8 illustrates a screenshot of example report view properties editor after the scorecard is published;

FIG. 9 illustrates a screenshot of an example report view configuration task pane in a scorecard application; and

FIG. 10 illustrates a logic flow diagram for a process of grouping and display of report views in a scorecard application.

DETAILED DESCRIPTION

As briefly described above, logically defined reports such as scorecard reports may be categorized based on their visual presentation size, and user controls may be provided for controlling a layout and properties of the reports based on their categorization. In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustrations specific embodiments or examples. These aspects may be combined, other aspects may be utilized, and structural changes may be made without departing from the spirit or scope of the present disclosure. The following detailed description is therefore not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents.

Referring now to the drawings, aspects and an exemplary operating environment will be described. FIG. 1 and the following discussion are intended to provide a brief, general description of a suitable computing environment in which the invention may be implemented. While the embodiments will be described in the general context of program modules that execute in conjunction with an application program that runs on an operating system on a personal computer, those skilled in the art will recognize that aspects may also be implemented in combination with other program modules.

Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that embodiments 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 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.

Embodiments 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.

With reference to FIG. 1, one example system for implementing the embodiments includes a computing device, such as computing device 100. In a basic configuration, the computing device 100 typically includes at least one processing unit 102 and system memory 104. Depending on the exact configuration and type of computing device, the system memory 104 may be volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two. System memory 104 typically includes an operating system 105 suitable for controlling the operation of a networked personal computer, such as the WINDOWS® operating systems from MICROSOFT CORPORATION of Redmond, Wash. The system memory 104 may also include one or more software applications such as program modules 106, scorecard application 120, report configuration module 122, and reporting application(s) 124. Scorecard application 120 manages business evaluation methods, computes KPIs, and provides scorecard data to reporting applications. In some embodiments, scorecard application 120 may itself generate reports based on metric data.

Report configuration module 122 manages determination of subordinate report definitions for selected scorecard metrics and categorization of available reports such that they can be consumed by the scorecard application 120 or reporting application(s) 124 based on their categories. Report configuration module 122 may be an integrated part of scorecard application 120 or a separate application. Scorecard application 120, report configuration module 122, and reporting application(s) 124 may communicate between themselves and with other applications running on computing device 100 or on other devices. Furthermore, any one of scorecard application 120, report configuration module 122, and reporting application(s) 124 may be executed in an operating system other than operating system 105. This basic configuration is illustrated in FIG. 1 by those components within dashed line 108.

The computing device 100 may have additional features or functionality. For example, the computing device 100 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. 1 by removable storage 109 and non-removable storage 110. 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 104, removable storage 109 and non-removable storage 110 are all examples of computer storage media. Computer storage media includes, but is not limited to, RAM, ROM, 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 the desired information and which can be accessed by computing device 100. Any such computer storage media may be part of device 100. Computing device 100 may also have input device(s) 112 such as keyboard, mouse, pen, voice input device, touch input device, etc. Output device(s) 114 such as a display, speakers, printer, etc. may also be included. These devices are well known in the art and need not be discussed at length here.

The computing device 100 may also contain communication connections 116 that allow the device to communicate with other computing devices 118, such as over a network in a distributed computing environment, for example, an intranet or the Internet. Communication connection 116 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” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. The term computer readable media as used herein includes both storage media and communication media.

Referring to FIG. 2, a system where example embodiments may be implemented, is illustrated. System 200 may comprise any topology of servers, clients, Internet service providers, and communication media. Also, system 200 may have a static or dynamic topology. The term “client” may refer to a client application or a client device employed by a user to perform business logic operations. Scorecard service 202, database server 204, and report server 206 may also be one or more programs or a server machine executing programs associated with the server tasks. Both clients and application servers may be embodied as single device (or program) or a number of devices (programs). Similarly, data sources may include one or more data stores, input devices, and the like.

A business logic application may be run centrally on scorecard service 202 or in a distributed manner over several servers and/or client devices. Scorecard service 202 may include implementation of a number of information systems such as performance measures, business scorecards, and exception reporting. A number of organization-specific applications including, but not limited to, financial reporting, analysis, marketing analysis, customer service, and manufacturing planning applications may also be configured, deployed, and shared in system 200. In addition, the business logic application may also be run in one or more client devices and information exchanged over network(s) 210.

Data sources 212, 214, and 216 are examples of a number of data sources that may provide input to scorecard service 202 through database server 204. Additional data sources may include SQL servers, databases, non multi-dimensional data sources such as text files or EXCEL® sheets, multi-dimensional data source such as data cubes, and the like. Database server 204 may manage the data sources, optimize queries, and the like.

Users may interact with scorecard service 202 running the business logic application from client devices 222, 224, 226, and 228 over network(s) 210. In one embodiment, additional applications that consume scorecard-based data may reside on scorecard service 202 or client devices 222, 224, 226, and 228. Examples of such applications and their relation to the scorecard application are provided below in conjunction with FIG. 3.

Report server 206 may include reporting applications, such as charting applications, alerting applications, analysis applications, and the like. These applications may receive scorecard data from scorecard service 202 and provide reports directly or through scorecard service 202 to clients.

Network(s) 210 may include a secure network such as an enterprise network, or an unsecure network such as a wireless open network. Network(s) 210 provide communication between the nodes described above. By way of example, and not limitation, network(s) 210 may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

Many other configurations of computing devices, applications, data sources, data distribution and analysis systems may be employed to implement a business logic application automatically generating dashboards with scorecard metrics and subordinate reporting.

Now referring to FIG. 3, example scorecard architecture 300 is illustrated. Scorecard architecture 300 may comprise any topology of processing systems, storage systems, source systems, and configuration systems. Scorecard architecture 300 may also have a static or dynamic topology.

Scorecards are a simple method of evaluating organizational performance. The performance measures may vary from financial data such as sales growth to service information such as customer complaints. In a non-business environment, student performances and teacher assessments may be another example of performance measures that can employ scorecards for evaluating organizational performance. In the exemplary scorecard architecture 300, a core of the system is scorecard engine 308. Scorecard engine 308 may be an application that is arranged to evaluate performance metrics. Scorecard engine 308 may be loaded into a server, executed over a distributed network, executed in a client device, and the like.

In addition to performing scorecard calculation, scorecard engine may also provide report parameters associated with a scorecard to other applications 318. The report parameters may be determined based on a subscriber request or a user interface configuration. The user interface configuration may include a subscriber credential or a subscriber permission attribute. The report parameter may include a scorecard identifier, a scorecard view identifier, a row identifier, a column identifier, a page filter, a performance measure group identifier, or a performance measure identifier. The performance measure may be a KPI, a KPI group, or an objective. The page filter determines a period and an organizational unit for application of the scorecard calculations.

Data for evaluating various measures may be provided by a data source. The data source may include source systems 312, which provide data to a scorecard cube 314. Source systems 312 may include multi-dimensional databases such as an Online Analytical Processing (OLAP) database, other databases, individual files, and the like, that provide raw data for generation of scorecards. Scorecard cube 314 is a multi-dimensional database for storing data to be used in determining Key Performance Indicators (KPIs) as well as generated scorecards themselves. As discussed above, the multi-dimensional nature of scorecard cube 314 enables storage, use, and presentation of data over multiple dimensions such as compound performance indicators for different geographic areas, organizational groups, or even for different time intervals. Scorecard cube 314 has a bi-directional interaction with scorecard engine 308 providing and receiving raw data as well as generated scorecards.

Scorecard database 316 is arranged to operate in a similar manner to scorecard cube 314. In one embodiment, scorecard database 316 may be an external database providing redundant back-up database service.

Scorecard builder 302 may be a separate application, a part of the performance evaluation application, and the like. Scorecard builder 302 is employed to configure various parameters of scorecard engine 308 such as scorecard elements, default values for actuals, targets, and the like. Scorecard builder 302 may include a user interface such as a web service, a Graphical User Interface (GUI), and the like.

Strategy map builder 304 is employed for a later stage in scorecard generation process. As explained below, scores for KPIs and parent nodes such as Objective and Perspective may be presented to a user in form of a strategy map. Strategy map builder 304 may include a user interface for selecting graphical formats, indicator elements, and other graphical parameters of the presentation.

Data Sources 306 may be another source for providing raw data to scorecard engine 308. Data sources may be comprised of a mix of several multi-dimensional and relational databases or other Open Database Connectivity (ODBC)-accessible data source systems (e.g. Excel, text files, etc.). Data sources 306 may also define KPI mappings and other associated data.

Scorecard architecture 300 may include scorecard presentation 310. This may be an application to deploy scorecards, customize views, coordinate distribution of scorecard data, and process web-specific applications associated with the performance evaluation process. For example, scorecard presentation 310 may include a web-based printing system, an email distribution system, and the like. A user interface for scorecard presentation 310 may also include an overview of available scorecards for a subscriber to select from. Scorecard presentation 310 may further include a matrix or a list presentation of the scorecard data. The scorecard presentation and one or more zones for other applications may be displayed in an integrated manner.

Report configuration module 320 is configured to interact with scorecard engine 308, scorecard presentation 310, other applications 318, and manage grouping and display of available reports associated with one or more scorecard elements. Report views offer the user the ability to specify ancillary data views and also view that data in the scorecard viewing experience. The report view definition may be implemented as a metadata-based mapping of logical reports to physical reports for scorecards and KPIs. The report view metadata may include schema, ordering capabilities, and mapping UI (re-use of report views in multiple areas). The report view definition may be rendered to multiple physical display formats and briefing books based on logical definition. If a shared portal web service is the output method, users may customize ancillary views available in the scorecard view using a report view configuration UI as shown in FIG. 5.

Categorization of suitable reports for selected metrics, may include determining presentation size(s) and type(s) for the reports, grouping of the reports based on the presentation size(s) and/or type(s), and assigning designators to each group such that reports can be identified as a member of their corresponding group and consumed based on their group by the scorecard application or a reporting application. Homogeneous and heterogeneous reports may be more easily manageable by grouping them based on their presentation size and/or type.

Other applications 318 may include any application that receives data associated with a report parameter and consumes the data to provide a report, perform analysis, provide alerts, perform further calculations, and the like. The data associated with the report parameter includes content data and metadata. Other applications may be selected based on the report parameter, a subscriber request, or a user interface configuration. The user interface configuration may include a subscriber credential or a subscriber permission attribute. Other applications 318 may include a graphical representation application, a database application, a data analysis application, a communications application, an alerting application, or a word processing application.

FIG. 4 illustrates a screenshot of an example scorecard. As explained before, Key Performance Indicators (KPIs) are specific indicators of organizational performance that measure a current state in relation to meeting the targeted objectives. Decision makers may utilize these indicators to manage the organization more effectively.

When creating a KPI, the KPI definition may be used across several scorecards. This is useful when different scorecard managers might have a shared KPI in common. The shared use of KPI definition may ensure a standard definition is used for that KPI. Despite the shared definition, each individual scorecard may utilize a different data source and data mappings for the actual KPI.

Each KPI may include a number of attributes. Some of these attributes include frequency of data, unit of measure, trend type, weight, and other attributes. The frequency of data identifies how often the data is updated in the source database (cube). The frequency of data may include: Daily, Weekly, Monthly, Quarterly, and Annually.

The unit of measure provides an interpretation for the KPI. Some of the units of measure are: Integer, Decimal, Percent, Days, and Currency. These examples are not exhaustive, and other elements may be added without departing from the scope of the invention.

A trend type may be set according to whether an increasing trend is desirable or not. For example, increasing profit is a desirable trend, while increasing defect rates is not. The trend type may be used in determining the KPI status to display and in setting and interpreting the KPI banding boundary values. The trend arrows displayed in scorecard 400 indicate how the numbers are moving this period compared to last. If in this period the number is greater than last period, the trend is up regardless of the trend type. Possible trend types may include: Increasing Is Better, Decreasing Is Better, and On-Target Is Better.

Weight is a positive integer used to qualify the relative value of a KPI in relation to other KPIs. It is used to calculate the aggregated scorecard value. For example, if an Objective in a scorecard has two KPIs, the first KPI has a weight of 1, and the second has a weight of 3 the second KPI is essentially three times more important than the first, and this weighted relationship is part of the calculation when the KPIs' values are rolled up to derive the values of their parent Objective.

Other attributes may contain pointers to custom attributes that may be created for documentation purposes or used for various other aspects of the scorecard system such as creating different views in different graphical representations of the finished scorecard. Custom attributes may be created for any scorecard element and may be extended or customized by application developers or users for use in their own applications. They may be any of a number of types including text, numbers, percentages, dates, and hyperlinks.

One of the benefits of defining a scorecard is the ability to easily quantify and visualize performance in meeting organizational strategy. By providing a status at an overall scorecard level, and for each perspective, each objective or each KPI rollup, one may quickly identify where one might be off target. By utilizing the hierarchical scorecard definition along with KPI weightings, a status value is calculated at each level of the scorecard.

First column of scorecard 400 shows example elements perspective 420 “Manufacturing” with objectives 422 and 424 “Inventory” and “Assembly” (respectively) reporting to it along with objective details 426. Second column 402 in scorecard 400 shows results for each measure from a previous measurement period. Third column 404 shows results for the same measures for the current measurement period. In one embodiment, the measurement period may include a month, a quarter, a tax year, a calendar year, and the like.

Fourth column 406 includes target values for specified KPIs on scorecard 400. Target values may be retrieved from a database, entered by a user, and the like. Column 408 of scorecard 400 shows status indicators.

Status indicators 430 convey the state of the KPI. An indicator may have a predetermined number of levels. A traffic light is one of the most commonly used indicators. It represents a KPI with three-levels of results—Good, Neutral, and Bad. Traffic light indicators may be colored red, yellow, or green. In addition, each colored indicator may have its own unique shape. A KPI may have one stoplight indicator visible at any given time. Indicators with more than three levels may appear as a bar divided into sections, or bands. Column 416 includes trend type arrows as explained above under KPI attributes. Column 418 shows another KPI attribute, frequency.

FIG. 5 illustrates screenshot 500 of a report view User Interface (UI) with a configuration task pane according to embodiments. Screenshot 500 includes scorecard view 504, selection view 506, report 510, and report view configuration task pane 508.

Scorecard view 504 presents a typical scorecard with hierarchically ordered elements (KPI's) and selected columns (e.g. different quarters of actuals and targets). Selection view 506 presents selected KPI's for which reports are available. A dropdown menu may provide filtering options for the reports such as combinations of rows and columns (e.g. sales by time, sales by store, etc.). Once a filter is set, available reports are listed for further selection. Report 510 is an example report based on the selected scorecard element(s). In FIG. 5, the example report is a bar chart comparing actuals vs. targets for selected stores. Report view configuration task pane 508 provides a UI for selecting report view groups based on available KPI and scorecard report views.

Screenshot 500 is an example presentation of a scorecard application with report grouping capability. Embodiments are not limited to the example scorecard layouts, report types, views, and user interface controls for managing those described above. Definition and instantiation of report grouping may be provided in many other ways using the principles described herein.

FIG. 6 illustrates diagram 600 of interactions between different components of a scorecard system for grouping reports in a scorecard viewer. A report configuration module according to embodiments enables a user to logically categorize report view definitions into groups based on their presentation size(s) and/or types during a scorecard definition (604) or KPI definition (606) processes in a scorecard builder (602). A suitable size for each report may be determined based on a computing device capability, a reporting application capability, a report content, or a user preference. The report types may include a map, a chart, one or more comments, an image, a video stream, an audio stream, a transaction list, a table, and the like. The groups (608, 610, etc.) may be named using system defined or user defined numeric or alphanumeric designators (e.g. “1”, “5”, “tables”, “charts”, “diagrams”, etc.).

The building environment may be configured to display a user-friendly tabular view of all report views for a given KPI or scorecard including the group name (unique ID) as a table column in an associated data grid UI. Furthermore, a report view editing form in the building environment may enable the user to explicitly assign that report view definition to a group.

A resulting scorecard view in scorecard viewer 612 may enable the user to select a KPI and view the related report views (614 and 616) as specified in the scorecard definition 604. Each of the resulting report views may provide an inline dropdown menu control allowing the user to change which report view data to show in a region based on the scorecard report view definition. This control may list the names of the report views as defined in the scorecard report views definition. Both scorecard and KPI report views may be listed as options in the dropdown menu control. A user may be provided options in a dropdown menu to see available scorecard report views and KPI report views. Moreover, the UI may be configured to enable a subscriber to define a report type and a presentation size in addition to a predefined selection of report types and presentation sizes. In another embodiment, report view configuration UI 612 may provide the controls.

Report view configuration UI 612 may include attribute displays, list reports, and the like. Each report view includes information associated with its components in its definition. By grouping the report views based on their presentation sizes and/or types and assigning them to a selected core component, heterogeneous metrics can be handled by the scorecard system in a seamless fashion.

FIG. 7 illustrates screenshot 700 of an example report view definition UI in a scorecard application. Workspace browser portion 702 of the UI includes a listing of KPIs and scorecards available to a subscriber in the scorecard application. The KPIs and scorecards (as well as other elements such as Objectives) may be presented in a listing tree format, a simple listing format, and any other format known in the art. Workspace browser portion 702 may also include a listing of associated data sources and indicators used in the scorecard views.

Upon selection of one of the items (e.g. Budget) in the workspace browser portion 702, information associated with the selected item is presented in the adjacent portion of the UI. The editor UI may provide information such as details of the selected item, actuals and targets included in the selected KPI or scorecard, configured views of the KPI or scorecard, and report views associated with the selected KPI or scorecard. Listing of report views 704 is an example showing available reports associated with the selected item. As shown in the example screenshot, four reports are available for the selected KPI. Listed attributes of each report view include report type 706, group identification 708, and description. In other embodiments, additional attributes such as appearance, name, owner, last modification date, and the like, may also be listed.

The selected KPI may be assigned the listed report views and their attributes. Furthermore, group properties may also be changed in this editor enabling user-specified assignment of report views to groups other than the predefined ones.

FIG. 8 illustrates screenshot of example report view properties editor 800 after the scorecard is published. Portion 802 of report view properties editor 800 includes a listing of editable items such as general properties, comments, or configuration(s). Portion 804 includes report view properties that may be modified by the user once the scorecard is published. Examples of such properties include height and width assigned to the report presentation (in this case a chart), group assignment, rendering type, and the like. The report itself is rendered in portion 806 as a chart of actuals vs. budget over time. As mentioned previously, default selections assigned by the scorecard application may be modified by the user employing this UI. Rendered report views may be dynamically updated to present user modifications. According to one embodiment, the report view attributes may be modified depending on a permission level of the subscriber.

FIG. 9 illustrates a screenshot of example report view configuration task pane 900 in a scorecard application. According to some embodiments, the user may be enabled to open report view configuration task pane 900 and view how many scorecard and KPI report views are available for that scorecard. Each report view groups may be associated with either a KPI 902 and/or a Scorecard 904 via a checkbox in each of the respective columns 906. The UI may be configured to present visually if and how many report views are present for each group. The user may then select groups by clicking the appropriate check box for each desired group. The selected report data may then be consumed by the scorecard application or another application by generating a report, storing a report, performing a query involving the report, and the like.

While the configuration UI is shown as a task pane, embodiments are not so limited. Other forms of the UI such as a pop-up display, a hover-over display, and a dropdown menu may be implemented using the principles described herein. According to some embodiments, the UI may be configured to provide the listing of available reports and manage the attribute of each report based on a subscriber credential or permission.

Furthermore, the example implementations of report views, scorecards, and UIs in FIGS. 5 through 9 are intended for illustration purposes only and should not be construed as a limitation on embodiments. Other embodiments may be implemented without departing from a scope and spirit of the invention.

FIG. 10 illustrates a logic flow diagram for a process of grouping and display of logical reports. Process 1000 may be implemented in a business logic application such as a scorecard application as described in FIGS. 1 and 2.

Process 1000 begins with operation 1002, where available reports are determined. Available reports are determined based on an evaluation of suitable reports for selected scorecard elements such as KPIs, Objectives, and the like. Processing advances from operation 1002 to operation 1004.

At operation 1004, a presentation size for each report is determined. The presentation size for each report may be determined based on a computing device capability, a reporting application capability, a report content, a user preference, and the like. Processing moves from operation 1004 to optional operation 1006.

At optional operation 1006, a report type is determined. The report type for the data included in the element, features of a report presentation layout associated with the report, and the like, may also be taken into consideration when determining the available reports and categorizing. Processing proceeds from optional operation 1006 to operation 1008.

At operation 1008, the reports are categorized based on their presentation size and/or type. Categorized reports may be assigned group names (e.g. numeric or alphanumeric designators) and consumed based on their categorization. Predefined group assignments may be modified based on user selection(s). Processing moves from operation 1008 to operation 1010.

At operation 1010, parameterized data associated with the categorized report views is provided to the scorecard application or other reporting applications for consumption. The report data may be consumed in form of generating a report, storing a report, performing a query, updating an existing report, and the like. After operation 1010, processing moves to a calling process for further actions.

The operations included in process 1000 are for illustration purposes. Grouping and displaying logical reports in a scorecard application may be implemented by similar processes with fewer or additional steps, as well as in different order of operations using the principles described herein.

The above specification, examples and data provide a complete description of the manufacture and use of the composition of the embodiments. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims and embodiments.

Claims

1. A method to be executed at least in part in a computing device for grouping logically defined reports, the method comprising: determining a plurality of logically defined reports;determining a suitable presentation size for each of the plurality of logically defined reports, wherein determining the suitable presentation size for each of the plurality of logically defined reports comprises determining the suitable presentation size based at least in part on a reporting application capability;categorizing, by the computing device, each of the plurality of logically defined reports based on the presentation size for each report, wherein categorizing each of the plurality of logically defined reports allows for consuming each report based on its category;receiving a modification to at least one of the plurality of logically defined reports, the modification corresponding to a change in a grouping property of the at least one logically defined report, the grouping property comprising a group name property, a presentation size property, and a report type property; anddynamically updating the categorization of the at least one logically defined report based on the received modification.

2. The method of claim 1, further comprising: assigning one of a numeric attribute and alphanumeric attribute to each report based on its category.

3. The method of claim 1, further comprising: determining a type of each of the plurality of logically defined reports; andcategorizing each of the plurality of logically defined reports based on their type.

4. The method of claim 3, wherein determining the type of each of the plurality of defined reports includes determining the type of each report including one of: a map, a chart, one or more comments, an image, a video stream, an audio stream, and a transaction list.

5. The method of claim 1, wherein consuming each report includes at least one from a set of: generating each report, storing each report, and performing a query using each report.

6. The method of claim 1, further comprising: providing a User Interface (UI) for managing an attribute associated with each report from a set of: a property, a layout, an order, and a mapping of each report in a report view screen.

7. The method of claim 6, wherein providing the UI comprises providing the UI configured to provide a listing of available reports grouped by their corresponding categories.

8. The method of claim 7, wherein providing the UI comprises presenting the UI as one of a task pane, a pop-up display, a hover-over display, and a dropdown menu.

9. The method of claim 7, wherein providing the UI comprises providing the UI configured to provide the listing of available reports and manage the attribute of each report based on a subscriber credential.

10. The method of claim 7, wherein providing the UI for managing the attribute associated with each report comprises including the attribute of each report in report view metadata in a parameterized form.

11. The method of claim 6, further comprising: providing the report view screen based on selections made through the UI.

12. The method of claim 1, wherein determining the suitable presentation size for each report is further based on at least one from a set of: a computing device capability, a report content, and a user preference.

13. The method of claim 1, wherein determining the plurality of logically defined reports comprises determining the plurality of logically defined reports associated with at least one element of a scorecard.

14. A computer-readable storage medium having computer executable instructions which when executed performs a method for managing parameterized subordinate reports in a scorecard system, the method executed by the computer executable instructions comprising: determining a plurality of reports associated with an element of a scorecard;determining a suitable presentation size for each of the plurality of reports, wherein determining the suitable presentation size for each of the plurality of reports is based at least in part on at least one of the following: a reporting application capability and a content of each report;determining a type for each of the plurality of reports;categorizing each of the plurality of reports based on the type of each report and the presentation size for each report, wherein categorizing each of the plurality of logically defined reports allows for consuming each report based on its category; andproviding a User Interface (UI) for managing at least one attribute associated with each report; andreceiving a modification to a grouping attribute of at least one of the plurality of logically defined reports, the grouping attribute comprising a group identifier; anddynamically updating the categorization of the at least one logically defined report based on the received modification to the grouping attribute.

15. The computer-readable storage medium of claim 14, wherein providing the UI comprises providing the UI configured to enable a subscriber to define the report type and the presentation size in addition to a predefined selection of report types and presentation sizes.

16. The computer-readable storage medium of claim 14, wherein the instructions further comprise creating groups of subordinate reports based on report categories.

17. A system for managing logically defined reports in a scorecard system, the system comprising: a computing device comprising a memory storage and a processing unit;a scorecard application configured to compute scorecard metrics and provide a scorecard presentation based on the computed scorecard metrics; anda report configuration module configured to: determine a number of available report definitions for a scorecard element based on a type of data associated with the scorecard element;determine a presentation size associated with each available report by determining a reporting capability of the scorecard application;categorize the available report definitions based on their presentation sizes; andprovide a set of user interface controls for visualizing and managing contents and layout of the available reports, wherein the set of user interface controls for visualizing and managing the contents and the layout of the available reports are operative to:allow a subscriber to change which report view data to show in a region based on an associated report definition, andupdate the categorization of the report view data based on a change to the associated report definition.

18. The system of claim 17, wherein the report configuration module is further configured to provide a physical instantiation of each category of the available reports for generating a report view screen.

19. The system of claim 17, wherein the report configuration module is further configured to parameterized attributes of each available report to a reporting application.

20. The system of claim 17, wherein the report configuration module is integrated with the scorecard application.