Abstract: A method includes receiving input identifying a dimensional framework and forecasting time period. The method also includes generating a workforce plan based on the dimensional framework and the forecasting time period. The method further includes receiving first data defining a first scenario of the workforce plan, where the first scenario is associated with at least a first turnover assumption, and determining a first set of forecasted headcount values corresponding to the first scenario. The method includes receiving second data defining a second scenario of the workforce plan, where the second scenario is associated with at least a second turnover assumption that differs from the first turnover assumption, and determining a second set of forecasted headcount values corresponding to the second scenario. The method includes generating graphical user interface (GUI) data that includes a comparison of the first set of forecasted headcount values and the second set of forecasted headcount values.

Abstract: Systems and methods of dynamically identifying supported items in an application are described. In one example, an analytics engine receives an indication of available client data, a user's enterprise role, and/or a user's security level. The analytics engine identifies a first subset of supported semantic items (e.g., business topics, business topics, measures, etc.) and a second subset of unsupported semantic items. For example, a semantic item may be supported if corresponding client data is available for analysis and the user's role/security level enable access to the client data. The analytics engine may send data including the supported semantic items and excluding the unsupported semantic items to an application.

Abstract: A method includes receiving input identifying a dimensional framework and forecasting time period. The method also includes generating a workforce plan based on the dimensional framework and the forecasting time period. The method further includes receiving first data defining a first scenario of the workforce plan, where the first scenario is associated with at least a first turnover assumption, and determining a first set of forecasted headcount values corresponding to the first scenario. The method includes receiving second data defining a second scenario of the workforce plan, where the second scenario is associated with at least a second turnover assumption that differs from the first turnover assumption, and determining a second set of forecasted headcount values corresponding to the second scenario. The method includes generating graphical user interface (GUI) data that includes a comparison of the first set of forecasted headcount values and the second set of forecasted headcount values.

Abstract: Systems and methods of dynamically identifying supported items in an application are described. In one example, an analytics engine receives an indication of available client data, a user's enterprise role, and/or a user's security level. The analytics engine identifies a first subset of supported semantic items (e.g., business topics, business topics, measures, etc.) and a second subset of unsupported semantic items. For example, a semantic item may be supported if corresponding client data is available for analysis and the user's role/security level enable access to the client data. The analytics engine may send data including the supported semantic items and excluding the unsupported semantic items to an application.

Abstract: In an example embodiment, a method is provided for linking an annotation to a document object of a document. Here, a structured document format associated with the document is accessed and this structured document format defines document objects and object identifiers identifying the document objects. The annotation assigned to the document object is received and an object identifier that identifies the document object is identified. This object identifier comprises at least one other document object that is related to the document object. The object identifier is then associated with the annotation and this association links the annotation to the document object.