CN104156795A - Business cockpits based on in-memory database - Google Patents

Abstract

Embodiments of the present disclosure provide systems and methods for lightweight monitoring applications with key performance indicator (KPI) reporting and management. The method can include displaying a page with a plurality of tiles on a user device. The tiles displayed on the page may include a plurality of key performance indicator (KPI) tiles, and at least one of a report tile, a news tile, and a collaboration tile. The method can retrieve metadata from an in-memory database, and the metadata from the in-memory database can correspond to content displayed in at least one KPI tile on the page. In response to input from the user input device selecting one of the tiles displayed on the page, the method may display additional details or controls for the selected tile.

Description

Business cockpit based on memory database

Cross References to Related Applications

This application claims priority from Indian Patent Application No. 1423/DEL/2013, filed May 14, 2013, the contents of which are incorporated herein by reference.

technical field

The present invention relates to a business cockpit based on an in-memory database.

Background technique

In today's competitive marketplace, business managers need to make quick decisions based on changing conditions. Managers need easy and engaging ways to analyze situations, share research findings, and make quick decisions. Existing services are complex and cannot always provide real-time assessment of ever-changing conditions.

Additionally, today, businesses need to make decisions based on many factors, which may include analyzing large amounts of data. Existing methods do not provide a solution to rapidly analyze large amounts of data and provide real-time results of such analysis. As a result, managers are limited in how often they can make decisions and on what data they base them on.

Contents of the invention

An aspect of the present disclosure provides a computer-implemented method comprising: displaying on a user device a page having a plurality of tiles, the tiles including a plurality of key performance indicator (KPI) tiles, and a report tile, an information tile At least one of a sticker and a collaborative tile; retrieve metadata from an in-memory database corresponding to content displayed in at least one of the KPI tiles on the page; receive a user input device indicating that the user is selecting input of one of the tiles displayed on the page; and in response to selecting one of the tiles, displaying additional details or controls for the selected tile.

Another aspect of the present disclosure provides a non-transitory computer-readable medium containing program instructions for providing a user interface on a user device, wherein execution of the program instructions by one or more processors of a computer system causes one or more The plurality of processors performs the steps of displaying on a user device a page having a plurality of tiles including a plurality of key performance indicator (KPI) tiles and at least one of a report tile, a news tile, and a collaboration tile. a; retrieving metadata from an in-memory database, the metadata from the in-memory database corresponding to content displayed in at least one KPI tile on the page; receiving a user input device indicating that the user is selecting one of the tiles displayed on the page one; and in response to selecting one of the tiles, providing additional details or controls for the selected tile.

Another aspect of the present disclosure provides a system comprising: an in-memory database for providing key performance indicator (KPI) details, said in-memory database comprising: a KPI directory for providing KPIs based on KPI-related data stored in memory A list, a virtual data model, providing values for the KPIs based on KPI-related data stored in memory, and a backend service, retrieving the list of KPIs and the values of the KPIs in response to requests; a web application server, coupled to the in-memory database, The web application server includes a page builder for rendering a page including a plurality of tiles, including a plurality of KPI tiles, and a report tile, based on metadata stored in memory of the web application server, At least one of a news tile and a collaboration tile; a unified shell that provides navigation capabilities for the tiles displayed in the page; and a catalog provider that integrates a list of KPIs, values of the KPIs, and tiles on the page; and a browser , used to display the rendered page provided by the page builder.

Another aspect of the present disclosure provides a computer-implemented method comprising: displaying on a user device a page having a plurality of tiles, the tiles including a plurality of key performance indicator (KPI) tiles, a report tile, a news tile tiles and collaboration tiles; retrieve metadata from an in-memory database, where the metadata from the in-memory database corresponds to content displayed in at least one of the KPI tiles on the page, and where the metadata from the in-memory database is not specific to the user device The type of user interface displayed on the page; metadata is retrieved from the web application server, where the metadata from the web application server describes the tile displayed on the page, and the description of the tile is specific to the user displayed on the user device Type of interface; receiving an input at a user input device indicating that the user is selecting one of the tiles displayed on the page; in response to selecting one of the tiles, displaying additional details about the content displayed in the selected tile information; receiving input at the user input device indicating that the user is selecting a settings control for the particular tile; in response to selecting the settings control for the particular tile, displaying a context menu including tile configuration and formatting for the particular tile .

Description of drawings

The drawings illustrate various embodiments and, together with the description, serve to explain the principles of the embodiments and to enable those skilled in the art to make and use the embodiments.

FIG. 1 illustrates an exemplary integration platform including multiple generic pages according to an embodiment of the present disclosure.

FIG. 2 shows possible paths for the first level of navigation of the tiles shown in FIG. 1 .

Figure 3 shows the basic building blocks of a KPI cockpit architecture according to an embodiment of the present disclosure.

FIG. 4 shows a system integrating a web application server and an in-memory database to provide a KPI cockpit according to an embodiment of the present invention.

5 is a block diagram of an exemplary computer system that may be used with embodiments of the present disclosure.

Detailed ways

Embodiments of the present disclosure provide systems and methods for lightweight monitoring applications with key performance indicator (KPI) reporting and management. The method can include displaying a page with a plurality of tiles on a user device. The tiles displayed on the page may include a plurality of key performance indicator (KPI) tiles, and at least one of a report tile, a news tile, and a collaboration tile. The method can retrieve metadata from an in-memory database, and the metadata from the in-memory database can correspond to content displayed in at least one KPI tile on the page. In response to input from the user input device selecting one of the tiles displayed on the page, the method may display additional details or controls for the selected tile.

Embodiments of the present disclosure address the shortcomings discussed above by allowing managers to configure and access strategic and operational KPIs in their personalized cockpit. Including strategic and operational KPIs in a single cockpit allows users to make better and faster business decisions based on both strategic and operational KPIs.

Providing data for KPIs using an in-memory database allows point-to-point KPI calculations, comparisons and simulations with immediate and highly flexible visualization of values. Managers can receive real-time results of enterprise performance even when input parameters change dynamically. As a result, users can execute “what if” scenarios and, based on the results, determine the best course of action for the business.

FIG. 1 illustrates an exemplary integration platform 100 that includes a plurality of general pages 102 according to an embodiment of the present disclosure. The general page 102 can serve as a home screen where users are provided with relevant information for their tasks in one place. The general page 102 can provide users with clearly structured visual information using multiple tiles 110-122. Generic page 102 can be displayed on client device 104, 106 or 108, for example, client device 104, 106 or 108 can comprise mobile device (for example, mobile phone or smartphone), personal computer, tablet computer, terminal device or personal computer. Digital Assistant (PDA). A client device 104, 106 or 108 may include an input device (eg, a touch screen, touch pad, mouse, or keyboard) to receive commands from a user.

The plurality of tiles 110-120 displayed on the general page 102 may include KPIs 110-116, reports 118, news feeds 120, collaboration threads 122, and/or custom tiles for adding additional tiles (e.g., other KPI tiles). Post 124. Each page from the plurality of general pages 102 may include its own set of tiles 110-120 selected and/or arranged based on the tasks associated with the respective page. For example, page 102 may be configured for: Strategic Sourcing; Financial and Commodity Risk; Expedited Financial Closing; Inventory Management; Processing Complex Projects; Each of the tiles 110-120 can be customized by the user.

Tiles 110-120 may provide users of page 102 with real-time information (eg, inventory, purchases in progress, funds received, etc.). Based on the information provided in the tiles 110-120, the user can perform specific transaction processes (eg, material tender planning) or specific in-depth analysis (eg, business process management and job clearance management). Automated tasks (eg, purchases, funds transfers, manufacturing adjustments, etc.) can be set up by the user based on the information provided in the tiles 110-120.

The KPI tiles 110-116 may include KPIs that can be used to assess the performance of the business or specific aspects of the business' activities. KPIs can assess the success of a business based on predefined goals (eg, number of sales or customer satisfaction) or based on the performance of other businesses. KPIs can be used to assess the current state of a business, predict future performance and/or identify areas for improvement. If certain changes are implemented, KPIs can provide information on how the business should perform. The content of the KPI tiles 110-116 can be personalized. For example, users can set thresholds for KPIs, sources of data, methods for displaying what will be displayed and various types of notifications. KPIs may be calculated after each reporting period and interval, or may be calculated when the data used to determine the KPI changes.

Reporting tiles 118 may include charts and/or graphs to visually illustrate the performance of the business. Charts and/or graphs may include projected performance of the business. Reporting tile 118 may display information related to one or more of KPI tiles 110-116.

News feed tile 120 may provide headlines and/or summarized news content related to page 102 or one or more of KPI tiles 110-116. News feed tile 120 may include a feed with information from businesses, customers, and/or partners.

Collaboration tile 122 may include a social network or collaborative environment that brings together people, information, applications, and processes to address key business issues (e.g., blocking collaboration products). Collaboration tiles 122 can connect customers, partners, and employees with key information to collaborate on business tasks. The tiles 110 - 120 displayed on the page 102 or information associated with the tiles 110 - 120 may be provided to collaborators via the collaboration tile 122 .

Each tile 110-122 may include a context menu. The context menu can be activated by selecting a tile (eg, right-click or double-click) or by selecting a context menu icon (not shown in FIG. 1 ) on a tile 110-122. The context menu may include tile configuration and formatting, follow-up actions, additional information, options to delete the tile, and other options to modify or control the tile.

In one embodiment, by selecting (eg, clicking or tapping on a tile) one of the tiles 110-122, the user can navigate to a page showing additional detailed information corresponding to the information of each tile. For example, as shown in FIG. 1 , the first-level tiles of page 102 can navigate to second-level navigation goals 130 by clicking on one of the KPI tiles. Second level navigation objects 130 may include additional details of KPI tiles, for example, while KPI tiles may include a summary of KPI details, second level navigation objects 130 may include graphs, charts, timelines, sources of information, and the filters or selections that can be made on the information displayed.

In one embodiment, clicking on one of the tiles 110-122 may display a specific application 132 (eg, an analytics application). Concrete applications 132 may provide a cockpit to perform tasks associated with KPI tiles 110-116. A specific application 132 may include settings that may be configured to perform analysis of data for one or more of the KPI tiles 110-116.

The tiles 110-122 can be rearranged, resized, added and/or removed by the user to customize the display of the tiles on the display. For example, a user may tap and hold a desired tile, and then drag the tile to move the selected tile to a new location on the displayed page. An option may be provided to the user to define the size of the page 102 (eg, the number of pixels or other units on the horizontal and vertical axes) in which the tiles 110-122 may be provided. The visualization of tiles 110-122 may vary based on corporate design (eg, branding), and may include tiles for company logos.

The types of changes a user is allowed to make to the page 102 may be based on the user's role. Accordingly, personalization of the page 102 and/or one or more tiles 110-122 may be based on the user's role. For example, customers of an enterprise may only be allowed to use the tiles 110-122 of the page 102, and may not be provided the option to change the setting or arrangement of the tiles 110-122. In contrast, an employee of the enterprise (eg, an administrator) may be allowed to make any type of change to the tiles 110 - 122 on the page 102 . The user's role may be used as a basis for determining which tiles 110-122 will be displayed, which tiles 110-122 may be changed, and which tiles 110-122 may be added or deleted.

FIG. 2 illustrates possible paths for a first level of navigation of the tiles 110-122 shown in FIG. 1 . As shown in FIG. 2 , KPI tile 210 can navigate to a navigation target including KPI details 212 , or to a specific application 214 . KPI details 212 may include graphs, diagrams, charts, tables, and/or details on how details of the KPIs were determined. Specific applications may include applications that perform further analysis on associated KPIs 210 (eg, analytics applications). Specific applications 214 may allow users to predict the performance of KPIs 210 by changing various activities of the enterprise.

Reporting KPIs 216 can be mapped to specific applications 214 . Specific applications 214 may allow users to control the performance of reports 216 . Specific application 214 may allow a user to predict the performance of the business provided in reports 216 by changing various activities of the business.

News tiles 218 may map to detailed news objects 220 . The detailed news object 220 may include detailed news content and/or settings for the news tile 218 . Settings may include selecting a news source, the content of the news, and/or which portion of the news to display in the news tile 218 .

Collaboration tiles 222 may map to collaboration activity goals 224 . Collaborative activity goals 224 can provide a social networking or collaborative environment on a single page.

As shown in FIG. 2 , a user may navigate back to an initial page including tiles 210 , 216 , 218 and/or 222 from supported navigation targets 212 , 214 , 220 , and 224 . When a user navigates to supported navigation objects 212, 214, 220, and 224, supported navigation objects 212, 214, 220, and 224 may display themselves on a single page.

Navigation paths can include additional levels. For example, as shown in FIG. 2 , KPI details 212 may include paths to navigate to other KPI details 226 and/or specific applications 228 .

FIG. 3 illustrates the basic building blocks of a KPI cockpit architecture 300 according to an embodiment of the present disclosure. The basic building blocks of the KPI cockpit architecture 300 may include components that function as front-end services and components that function as back-end services that are accessed by front-end components. Front-end services can be associated with KPI cockpit 302 , shell 314 and application 316 . Backend services can be associated with backend services 320 , KPI catalog 322 , tile repository 324 , and personalization services 330 . Backend services may also be associated with tile information provider 332 and KPI provider 334 .

The backend operation of KPI cockpit 302 can be in memory database (for example: HANA database). An in-memory database may be a database management system that relies on main memory (eg, storage that acts as a cache) for storing the database's data. Utilizing main memory may allow faster retrieval of data stored in main memory and allow reports to be provided in real time. In-memory databases can take advantage of multi-core processors and solid-state drives. A database can support both relational data (for example, with row-oriented and column-oriented representations) as well as graphics and word processing in the same system.

The in-memory database can provide KPI details in response to requests (eg, via OData). An in-memory database can include a KPI repository, a KPI definition cockpit, and perform KPI runtime and evaluation based on local data. In another embodiment, the backend service may be executed on a web application server (eg, an ABAP application server running an APAP (Advanced Business Application Programming) application) and an in-memory database. The web application server can also provide one or more of the front-end services (eg, user interface with KPI cockpit 302 ). KPI cockpit 302 may be provided to client devices via a browser. In another embodiment, one or more of the backend service, and the frontend service may execute on an in-memory database.

The integration of the in-memory database with the KPI cockpit 302 provides real-time analysis of variance and bias in large volumes of data. The architecture may allow users of an enterprise to select forecasts based on current as well as historical data. The architecture can also provide users with immediate insight into existing deviations and predict potential problems. The KPI cockpit 302 can provide the user with a combined overall view of the status and progress of the enterprise's operations relative to financial and/or logistical data. The data displayed in the KPI cockpit 302 can be driven by alarm and exception coverage values, dates and volumes defined by the enterprise.

The KPI cockpit 302 can include a page 304 for displaying a number of tiles 306 . Page 304 may be provided on a display of a client device via browser 318 . KPI cockpit 302 may be based on a document language (eg, markup language) used to structure and present content to users 312 . The KPI cockpit 302 may be based on a document language for displaying content over the Internet, a local network, or a private network. The document language may include Hypertext Markup Language (HTML) (eg, HTML5), but is not limited thereto.

As discussed above, tiles 306 may include different types of tiles (eg, tiles including KPI, reports, news, and collaboration). The type of tile 306 may be defined by the configuration of the tile. Each tile 306 in the KPI cockpit 302 can be defined by metadata. For each type of tile 306 (eg, point value type, line graph type, column graph type, etc.), specific code can be used to generate a visualization of the content based on the metadata. The specific code for each type of tile 306 may include personalization features applicable to each tile type.

KPI cockpit 302 can provide users with personalization functionality (eg, add or delete tiles). Personalization features may be provided for each tile and may include thresholds for changing the content displayed on the tile. Personalization features can affect which tiles 306 are displayed, how they are displayed on the page 304, and how content is displayed on the tiles. By defining the content of tiles 306 via configuration rather than using code, the distributor and customer of the KPI cockpit (eg, user 312 ) can define multiple KPI cockpits and/or tiles 306 based on the same application code.

KPI cockpit 302 may include user interface 308 and other libraries 310 to render pages 304 and/or tiles 306 . User interface 308 may include UI5 (User Interface for HTML5). The tiles 306 rendered on the page 304 may only be loaded using libraries provided as part of the KPI cockpit 302 . The KPI cockpit 302 that renders the page 304 to display the tiles 306 can operate as a front-end component (eg, an interface between the user and the back-end).

Shell 314 may provide navigation capabilities and/or basic functionality to user 312 . The navigation capabilities provided by the shell 314 can go beyond the KPI cockpit 302 . Shell 314 may provide front-end services that are not tied to a specific application.

Applications 316 may include applications associated with one or more tiles 306 . Applications 316 may include HTML (eg, HTML5 applications). Application 316 may be an application running outside of KPI cockpit 302 . User 312 can navigate to application 316 by making a corresponding selection on tile 306 . Parameters describing the context of navigation from tile 306 within KPI cockpit 302 to application 316 may be passed from tile 306 to invoked application 316 . Navigation by the user from the tile 306 to the detailed view of the KPI can be handled by the KPI cockpit 302 with specific codes for the type of tile or KPI.

As discussed above, KPI cockpit 302 can render pages 304 and/or tiles 306 . Information needed to render the page and/or tile 306 (eg, a description of the tile and the KPI) can be retrieved from a backend service 320 (eg, a KPI cockpit backend service). This information may be received via a data access request using known protocols such as HTTP or the Open Data Protocol (OData). In one embodiment, the request can be made using OData via HTTP. A single HTTP request can be used to provide all required metadata to the KPI cockpit 302 . To achieve this goal, in a single HTTP request, the backend service 320 can call other backend services to get additional information for processing the request. Additional information may include, for example, details about tiles, KPIs, and other applications.

Backend service 320 may present a list of tiles 306 to be displayed on page 304 , as well as metadata describing tiles 306 . Metadata may correspond to a personalized list of tiles 306 . Metadata for KPI tiles may be stored in KPI directory 322 . Metadata for tile 306 may be stored in repository 324 . Metadata for personalization of tile 306 may be stored in personalization service 330 .

KPI catalog 322 may include all metadata used to describe KPIs. A KPI can be defined by a given set of attributes (eg, numerical value, multilingual text, technical key, Uniform Resource Identifier, etc.). The same metadata used to describe KPIs can be used in different user interfaces. Therefore, metadata may not be specific to the user interface. The KPI directory 322 can centrally maintain all KPIs in one place. The KPI catalog 322 allows all KPIs to be defined in the same way and in one location. That is, the KPI catalog 322 can maintain standard KPIs provided by the enterprise, but also maintain custom or customer-developed KPIs. Values for KPIs can be retrieved from a virtual data model (VDM), from a third-party system, or from a business information warehouse.

Tile repository 324 may include a complete list of tiles available for display in page 304 . Tile descriptions in tile repository 324 may be specific to a user interface. For example, tile descriptions may include tile descriptions for HTML applications and for native mobile applications. Tile descriptions may include indirect descriptions (eg, referencing abstract identifiers for specific implementations of different user interface technologies).

The KPI cockpit 302 can receive tile information from a tile information provider 332 and receive KPI information from a KPI provider 334 . This information may be provided in addition to information provided from KPI catalog 322 , tile repository 324 , and/or personalization service 330 via backend service 320 . Additional tiles and/or KPI information may be received from third party systems or from a business information warehouse. Tile information provider 332 and/or KPI provider 334 may provide customer-specific information to define tiles and/or KPIs. Customer-specific data may be stored in backend service components (eg, KPI catalog 322, tile repository 324, and/or personalization service 330).

Data used for KPIs can be associated with specific customers and/or businesses. The business and/or customers can define and maintain KPIs. In one embodiment, default or sample definitions of KPIs may be provided by the enterprise, the distributor of the service, or the maintainer of the system. The system shown in Figure 3 allows KPI and tile information to be centrally maintained in one place and using the same system. The system allows users to utilize the same definitions (eg, descriptive data) of KPIs that can be stored in the same place (eg, KPI catalog 322 ).

FIG. 4 shows a system 400 integrating a web application server 410 and an in-memory database 420 to provide a KPI cockpit according to an embodiment of the present invention. Web application server 410 may be an advanced business application programming server, and in-memory database 420 is HANA database, but not limited to it. FIG. 4 shows how the components shown in FIG. 3 may be distributed between a web application server 410 and an in-memory database 420 . System 400 may operate such that front-end components and back-end components are not limited by the type of front-end components and/or back-end components used in system 400 . Thus, the same front-end components (e.g. communication library, navigation shell) can reuse the specific type of back-end stack used in the system (e.g. ABAP server and/or HANA). OData (Open Data Protocol) can be used by system 400 to communicate between front-end and back-end components.

Web application server 410 and in-memory database 420 may perform backend operations. Web application server 410 may perform one or more of the front-end operations. The web application server 410 can provide a user interface with a KPI cockpit to the browser 440 . The KPI cockpit can be provided to the browser 440 via the web distributor 430 . A web distributor 430 may be provided to process HTML and OData protocol content from the web application server 410 and the in-memory database 420, respectively.

User interface artifacts corresponding to KPI tiles to be displayed in the KPI cockpit may be stored in a stack of the web application server 410 . Reporting of information for KPI tiles can be performed via PCFG (role maintenance) and reporting quick launch. PFCG can perform role maintenance management to manage roles and authorizations for data on the ABAP stack including user interface artifacts corresponding to KPI tiles.

Drill down applications and second-level applications for further analysis of KPIs can be provided on the in-memory database 420 stack. The in-memory database 420 stack may also include KPI framework definitions, runtime conditions (eg, no visualization), and all drill-down applications.

The integration of KPIs into the unified shell's tile catalog can be performed via a catalog provider in the web application server 410 . The catalog provider can access the KPI catalog of the in-memory database 430 and provide the list of KPIs to end users. The directory provider may need to verify the current user's credentials against the in-memory database 430 in order to use the concept of authorization in the in-memory database 420 . Therefore, an enterprise can limit the list of KPIs for each user and/or user's role in the enterprise.

When a user selects a KPI, the catalog provider in the web application server 410 can create a configuration for the KPI tile template containing a resource locator (eg, URL) to a corresponding in-memory database 420 service (eg, query, note, etc.). The KPI tile template and configuration can be passed to a page builder in the web application server 410 . The page builder can render the KPIs for display in the KPI cockpit.

KPIs can be defined through metadata. Each KPI may be defined by a specific set of attributes, which may include numeric values, multilingual text, technical keys, and/or URIs (Uniform Resource Identifiers). Specific attributes of KPIs can be defined by users, enterprises, providers of the system, or administrators. Components of the system can search for KPIs based on attribute values. As discussed above, KPIs can be defined independently of the user interface technology used to display the KPIs. Providing KPIs that are independent of user interface technology can allow re-use of user-defined metadata.

Values for KPIs may be retrieved through the KPI catalog from a virtual data model (VDM) in the in-memory database 420, from a third-party system, or from a business information warehouse.

Although some concepts of the system are described above with reference to ABAP Server and HANA, these concepts can be applied to other infrastructures.

Some embodiments may include the methods described above written as one or more software components. These components, and the functionality associated with each component, can be used by client, server, distributed or peer-to-peer computer systems. These components may be written in a computer language corresponding to one or more programming languages, such as functional languages, declarative languages, procedural languages, object-oriented languages, low-level languages, and the like. They can be linked to other components via various application programming interfaces, and then compiled into a complete application for server or client. Alternatively, components can be implemented in server and client applications. Furthermore, these components can be linked together via various distributed programming protocols. Some example embodiments may include remote procedure calls for implementing one or more of these components across a distributed programming environment. For example, the logic layer may reside on a first computer system that is remote from a second computer system that contains the interface layer (eg, a graphical user interface). These first and second computer systems may be configured in a server-client, peer-to-peer, or some other configuration. Client complexity can range from mobile and handheld devices, to thin clients, to thick clients and even other servers.

The software components illustrated above are tangibly stored as instructions on a computer-readable storage medium

superior. The term "computer-readable storage medium" should be understood to include a single medium or multiple media that store one or more sets of instructions. The term "computer-readable storage medium" shall be understood to include any physical article capable of undergoing a set of physical changes to physically store, encode, or otherwise carry a set of instructions for a computer system to execute, causes a computer system to perform any of the method or process steps described, represented or illustrated herein. Examples of computer-readable storage media include, but are not limited to: magnetic media, such as hard disks, floppy disks, and magnetic tape; optical media, such as CD-ROMs, DVDs, and holographic devices; magneto-optical media; and Hardware devices such as Application Specific Integrated Circuits (“ASICs”), Programmable Logic Devices (“PLDs”) and ROM and RAM devices. Examples of computer readable instructions include machine code, such as produced by a compiler, and files containing high-level code run by a computer using an interpreter. For example, embodiments of the present disclosure may be implemented using Java, C++, or other object-oriented programming languages and a development cockpit. Another embodiment of the present disclosure may replace machine-readable software instructions with hard-wired circuits,

Alternatively, it may be implemented as hardwired circuitry combined with machine-readable software instructions.

FIG. 5 is a block diagram of an exemplary computer system 500 . The computer system 500 includes a processor 505 that executes software instructions or code stored on a computer-readable storage medium 555 to perform the above-described embodiments of the present disclosure. Computer system 500 includes a media reader 540 to read instructions from a computer-readable storage medium 555 and store the instructions in memory 510 or random access memory (RAM) 515 . The memory 510 provides a larger space for storing static data, and at least some instructions can be stored in the memory 510 for later execution. Stored instructions may also be compiled to generate other representations of instructions and may be dynamically stored in RAM 515 . Processor 505 reads instructions from RAM 515 and executes actions in accordance with the instructions. According to one embodiment of the present disclosure, the computer system 500 also includes an output device 525 (for example, a display) to provide the user with at least some operating results as output, the results including but not limited to visual information, and the computer system 500 also includes an input Device 530 to provide a user or another device with means for entering data and/or interacting with computer system 500 . Each of these output devices 525 and input devices 530 may be combined with one or more additional peripheral devices to further expand the capabilities of computer system 500 . A network communicator 535 may be provided to connect the computer system 500 to a network 550 and, in turn, for example, to a network 550 including other clients, servers, data stores and interfaces. The modules of the computer system 500 are interconnected via a bus 545 . Computer system 500 includes data source interface 520 for accessing data source 560 . Data sources 1160 may be accessed via one or more abstraction layers implemented in hardware or software. For example, data source 560 may be accessed via network 550 . In some embodiments, data sources 560 may be accessed via an abstraction layer, such as a semantic layer.

Data sources are information resources. Data sources include sources of data that enable data storage and retrieval.

Data sources may include databases such as relational databases, transactional databases, hierarchical databases, multidimensional (eg, OLAP) databases, object-oriented databases, and the like. Additionally, data sources include tabular data (e.g., spreadsheets, delimited text files), data marked up in markup languages (e.g., XML data), transactional data, unstructured data (e.g., text files, screen scrapes) , hierarchical data (e.g., data in a file system, XML data), files, multiple reports, and any other data source accessible through established protocols such as Open Database Connectivity (ODBC), protocols generated by underlying software systems (eg, ERP systems), etc. Data sources may also include data sources where the data is not tangibly stored, or is ephemeral, such as data streams, broadcast data, and the like. These data sources can include linked data foundations, semantic layers, management systems, security systems, and more.

A semantic layer is an abstraction over one or more data sources. It no longer requires users to master the nuances of existing query languages when writing queries. The abstractions provided include metadata descriptions of data sources. Metadata may include terms that are meaningful to the user in place of the logical or physical description used by the data source. For example, common business items instead of table and column names. These items can be localized and/or domain specific. A layer can include logic associated with the underlying data, allowing it to automatically formulate queries for running against the underlying data source. Logic includes connections to data sources, the structure of data sources, and aspects of data sources. Some semantic layers can be published so that it can be shared by multiple clients and users. Some semantic layers implement security at a granularity corresponding to the structure of the underlying data source or at the semantic layer. The specific form of the semantic layer includes data model objects that describe the underlying data sources and define dimensions, attributes, and measures using the underlying data. These objects can represent relationships between dimension members, providing calculations associated with the underlying data.

In the above description, numerous details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It will be apparent, however, to one skilled in the relevant art that the various embodiments may be practiced without one or more of the details, or with other methods, components, materials, and the like. In other instances, well-known operations or structures have not been shown or described in detail to avoid obscuring aspects of the present disclosure.

Although the processes shown or described herein include a series of steps, it will be understood that various embodiments of the present disclosure are not limited to the order of the steps shown, as some steps may be performed in an order other than that shown and described. They occur in different orders, and some may occur in parallel with other steps. Moreover, not all illustrated steps are required to implement a methodology in accordance with the present disclosure. Furthermore, it will be understood that the processes may be implemented in conjunction with the devices and systems shown and described herein, as well as with other systems not shown.

The above description and illustrations of embodiments of the disclosure, including what is described in the Abstract, are not intended to be exhaustive or to limit the embodiments to the precise forms disclosed. Although specific embodiments, and examples, of the embodiments are described herein for illustrative purposes, those skilled in the art will recognize that,

Various equivalent modifications are possible within the scope of this disclosure. These modifications can be made to the embodiments in light of the foregoing detailed description.

Claims (20)

1. a computer-implemented method, comprising:

On subscriber equipment, demonstration has the page of multiple magnetic subsides, and magnetic pastes and comprises the subsides of multiple KPI Key Performance Indicators (KPI) magnetic, and reports at least one in magnetic subsides, the subsides of news magnetic and the subsides of cooperation magnetic;

From internal storage data library searching metadata, the content showing in pasting corresponding at least one the KPI magnetic on the page from the metadata of memory database;

Receive user input apparatus place, indicating user is being chosen in the input that the magnetic that shows on the page one of pastes; And

In response to selecting magnetic one of to paste, show additional detail or the control of pasting for selected magnetic.

2. computer-implemented method as claimed in claim 1, also comprises that wherein, the magnetic showing on the page from the metadata description of network application server pastes from network application server retrieval metadata.

3. computer-implemented method as claimed in claim 2, wherein, the description that described magnetic pastes is specific to the type of the user interface showing on subscriber equipment.

4. computer-implemented method as claimed in claim 2, wherein, the described metadata from network application server comprises the description of pasting for all magnetic that show on the page.

5. computer-implemented method as claimed in claim 1, wherein, the described metadata from memory database is not specific to the type of the user interface showing on subscriber equipment.

6. computer-implemented method as claimed in claim 1, wherein, if one of KPI magnetic subsides are selected, shows the additional detail of pasting the described one or more KPI that are associated with selected KPI magnetic.

7. computer-implemented method as claimed in claim 1, wherein, if one of KPI magnetic subsides are selected, show and pastes with selected KPI magnetic the analytical applications being associated.

8. computer-implemented method as claimed in claim 1, wherein, comprise that for the control of selected KPI magnetic pastes configuration, formatting, subsequent action setting, deletes the option that the selected magnetic of option, reorientation that selected magnetic pastes pastes and changes at least one of option of the threshold value that selected magnetic pastes.

9. computer-implemented method as claimed in claim 1, wherein, show that having the page that described multiple magnetic pastes comprises that the magnetic showing with using user's the role of described subscriber equipment to be associated pastes, and hide or forbid the magnetic subsides unconnected with user's the role who uses described subscriber equipment.

10. comprise a non-temporary computer readable medium for the programmed instruction for user interface is provided on subscriber equipment, wherein, make one or more processors carry out following steps by one or more processor runs program instructions of computer system:

On subscriber equipment, demonstration has the page of multiple magnetic subsides, and magnetic pastes and comprises the subsides of multiple KPI Key Performance Indicators (KPI) magnetic, and reports at least one in magnetic subsides, the subsides of news magnetic and the subsides of cooperation magnetic;

From internal storage data library searching metadata, the content showing in pasting corresponding at least one the KPI magnetic on the page from the metadata of memory database;

Receive user input apparatus place, indicating user is being chosen in the input that the magnetic that shows on the page one of pastes; And

In response to selecting magnetic one of to paste, be provided for additional detail or control that selected magnetic pastes.

11. non-temporary computer readable mediums as claimed in claim 10, also comprise that, from the step of network application server retrieval metadata, wherein, the magnetic showing on the page from the metadata description of network application server pastes.

12. non-temporary computer readable mediums as claimed in claim 11, wherein, the description that described magnetic pastes is specific to the type of the user interface showing on subscriber equipment.

13. non-temporary computer readable mediums as claimed in claim 10, wherein, the described metadata from memory database is not specific to the type of the user interface showing on subscriber equipment.

14. non-temporary computer readable mediums as claimed in claim 10, wherein, if one of KPI magnetic subsides are selected, show and paste with selected KPI magnetic the analytical applications being associated.

15. non-temporary computer readable mediums as claimed in claim 10, wherein, comprise that for the control of selected KPI magnetic pastes configuration, formatting, subsequent action setting, deletes the option that the selected magnetic of option, reorientation that selected magnetic pastes pastes and changes at least one of option of the threshold value that selected magnetic pastes.

16. 1 kinds of systems, comprising:

Memory database, for KPI Key Performance Indicator (KPI) details are provided, described memory database comprises:

KPI catalogue, based on being stored in relevant data of KPI in storer and providing the list of KPI,

Virtual data model, based on being stored in relevant data of KPI in storer and providing the value of KPI, and

Back-end services, in response to the request retrieval list of KPI and the value of KPI;

Network application server, is coupled to memory database, and described network application server comprises:

Page builder, the metadata based on being stored in the storer of network application server is played up the page that comprises that multiple magnetic pastes, and described multiple magnetic pastes and comprises that multiple KPI magnetic pastes, and report magnetic pastes, news magnetic pastes and at least one in pasting of cooperation magnetic,

Unified shell, the homing capability that provides the magnetic showing in the page to paste, and

Catalogue provides device, and the magnetic on the list of integrated KPI, the value of KPI and the page pastes; And browser, for the page of playing up being provided by page builder is provided.

17. systems as claimed in claim 16, wherein, described in the page played up offer browser via the network distributor that is coupled to network application server and memory database.

18. systems as claimed in claim 16, wherein, described memory database is HANA database, and described network application server is higher level service application programming server.

19. systems as claimed in claim 16, wherein, be stored in the relevant data of KPI in the storer of memory database not specific to the type of the user interface showing in browser, and the magnetic being stored in the storer of network application server posts the data of pass specific to the type of the user interface showing in browser.

20. 1 kinds of computer-implemented methods, comprising:

On subscriber equipment, show and have the page that multiple magnetic pastes, magnetic pastes and comprises that multiple KPI Key Performance Indicators (KPI) magnetic pastes, report magnetic pastes, news magnetic pastes and cooperation magnetic pastes;

From internal storage data library searching metadata, wherein, the content showing in pasting corresponding at least one the KPI magnetic on the page from the metadata of memory database, and from the metadata of memory database not specific to the type of the user interface showing on subscriber equipment;

From network application server retrieval metadata, wherein, the magnetic showing on the page from the metadata description of network application server pastes, and the description of described magnetic subsides is specific to the type of the user interface showing on subscriber equipment;

Receive user input apparatus place, indicating user is being chosen in the input that the magnetic that shows on the page one of pastes;

In response to selecting magnetic one of to paste, show the additional detail about the content showing in selected magnetic pastes;

Receive user input apparatus place, indicating user selecting for specific magnetic paste the input that control is set;

In response to the control that arranges of selecting to paste for specific magnetic, show and comprise that the magnetic pasting for specific magnetic pastes the context menu of configuration and formatting.