Abstract: Systems and methods are provided to produce natural language interpretations of analytic operations in an automated manner, by associating with each analytic procedure a set of parameters that determine the interpretation of the resulting analysis.

Abstract: A method of forecasting workforce demand, includes forecasting an ongoing engagements demand, forecasting an opportunities demand, forecasting a wedge engagements demand, representing a result of the forecasting the ongoing engagements demand as a first workforce demand statement, a result of the forecasting the opportunities demand as a second workforce demand statement, and a result of the forecasting the wedge engagements demand as third workforce demand statement, and integrating the first workforce demand statement, the second workforce demand statement and the third workforce demand statement to generate an overall workforce demand forecast.

Abstract: A system (and method, and method for deploying computing infrastructure) for identifying a customer at risk of revenue change (e.g., revenue loss or revenue gain) including computing a risk score based on a plurality of risk factors associated with the customer.

Abstract: A method and system estimates future software support requirements based on statistical models of previous observations of support requests, either for the same product or for a different product having features previously identified as correlated with features of a new product. The estimates include an estimated volume of support requests and an estimated type of support requests. The estimated types include the activity occurring at the time of the failure, an identifier as to whether a defect in the software was previously known, and the like. The estimates are used to estimate and allocate support resources prior to support requests being received, and prior to a software product being released.

Abstract: A method and system estimates future software support requirements based on statistical models of previous observations of support requests, either for the same product or for a different product having features previously identified as correlated with features of a new product. The estimates include an estimated volume of support requests and an estimated type of support requests. The estimated types include the activity occurring at the time of the failure, an identifier as to whether a defect in the software was previously known, and the like. The estimates are used to estimate and allocate support resources prior to support requests being received, and prior to a software product being released.

Abstract: A method for identifying and using historical work patterns to build high-performance project teams, in one aspect, may comprise identifying historical data associated with one or more past projects, determining from said historical data, one or more patterns in team member attributes that are correlated with at least one of an individual determined to be successful and a project determined to be successful, and generating one or more staffing plans based on said determined patterns. A system and program storage device for performing finctionalities of the method are also provided.

Abstract: A process for determining which of a large number of candidate companies are most likely to outsource some aspect of their business operations, based on a mathematical model capable of analyzing a large number of inputs, including financial metrics, executive changes, and other significant corporate events like mergers and acquisitions.

Abstract: A method and system for predicting resource requirements of a current service engagement by modeling records of past service engagements to create and classify templates of service resource usage. This is done by clustering past engagements into groups having similar time series requirements for service resources. A service resource template for the current service engagement is generated from a classified template by using characteristics of the current service engagement to select a group of which the current service engagement is a likely member. The corresponding template is then customized to fit the characteristics of the current service engagement. The invention may be implemented using Hidden Markov Models. An aspect of the invention is use of dynamic time warping to quantify dissimilarity between engagement sequences prior to fitting Hidden Markov Models. Another aspect of the invention is removal of outliers from the clustered groups.

Abstract: A method and system estimates future software support requirements based on statistical models of previous observations of support requests, either for the same product or for a different product having features previously identified as correlated with features of a new product. The estimates include an estimated volume of support requests and an estimated type of support requests. The estimated types include the activity occurring at the time of the failure, an identifier as to whether a defect in the software was previously known, and the like. The estimates are used to estimate and allocate support resources prior to support requests being received, and prior to a software product being released.

Abstract: A method of forecasting workforce demand, includes forecasting an ongoing engagements demand, forecasting an opportunities demand, forecasting a wedge engagements demand, representing a result of the forecasting the ongoing engagements demand as a first workforce demand statement, a result of the forecasting the opportunities demand as a second workforce demand statement, and a result of the forecasting the wedge engagements demand as third workforce demand statement, and integrating the first workforce demand statement, the second workforce demand statement and the third workforce demand statement to generate an overall workforce demand forecast.

Abstract: A method and system estimates future software support requirements based on statistical models of previous observations of support requests, either for the same product or for a different product having features previously identified as correlated with features of a new product. The estimates include an estimated volume of support requests and an estimated type of support requests. The estimated types include the activity occurring at the time of the failure, an identifier as to whether a defect in the software was previously known, and the like. The estimates are used to estimate and allocate support resources prior to support requests being received, and prior to a software product being released.