1. Technical Field
The present disclosure is directed to systems and method for managing financial risk in information technology (IT) service contracts.
2. Discussion of Related Art
Information technology (IT) services are long-running projects governed by a myriad of factors throughout their lifetime. The goal of service management is to ensure uninterrupted delivery of service from the provider to the customer, while meeting a number of quality and performance goals. The objectives of a service provider are to maintain good service quality, high client satisfaction, and ultimately continuous profitability of its contracts.
Service companies are facing ever-increasing risks in service contracts due to uncertain economic situations. Because service contracts typically span multiple years and could cover various aspects of IT services, numerous derailments can occur during their lifetime. Although some of these derailing risk factors are unpredictable before a contract enters delivery phase, many risk factors do have early signs that can be detected. For example, a provider dealing with a customer who has not been in good financial situations is more likely to have financial troubles for this contract.
From a service provider's perspective, it is important to develop mechanisms to identify these potential risks before the contract is signed. Some of these risk factors can be mitigated through various risk management practices, while the others will remain until the contract enters delivery. The only leverage the provider has at that time is pricing. That is, a provider can negotiate for higher price for high-risk projects, so that the overall profitability of a portfolio of contracts can be maintained.
Analysis has shown that majority of the “troubled” contracts were due to insufficient handling of engagement risks, such as a lack of understanding of client environment, a misunderstanding the service delivery scope or objectives, poor resource planning and management, etc. Engagement risks have direct impact on contract profitability, e.g., the difference between the actual and the planned gross profit.
While preparing for a contract, a question that arises is “what is the fair price for this contract?” The fair price should be determined by the overall profitability target and the risk appetite of the company. The profitability target can be, for example, a certain gross profit margin that needs to be achieved in one or multiple years. The risk appetite is the tolerance of a certain probability of not being able to achieve the target, and the worst-case profit achieved.
According to an aspect of the invention, a method for profiling information technology (IT) service contract risks and generating contract prices includes analyzing historical IT service contract risk data to create a set of IT service contract risk profiles, where the historical IT service contract risk data includes contract risks and percent gross profit associated with a historical set of contracts, where each IT service contract risk profile is a probability distribution function of achieving a percent gross profit associated with a subset of contracts corresponding to particular set of contract risk values, and creating a mapping between a particular IT service contract risk profile and a new IT service contract associated with the set of contract risk values for the IT service contract risk profile to determine an optimum price for the new IT service contract.
According to another aspect of the invention, a method for profiling information technology (IT) service contract risks and generating contract prices includes training a classifier that classifies a set of historical IT service contracts into distinct subsets according to a hierarchy of risk factors, where at each level of the hierarchy of risk factor, an IT service contract is classified into two or more categories based on that contract's risk value or range of values for that risk factor, where each subset of historical contracts is associated with a particular combination of risk factors and risk factor values, and compiling gross profit data of all IT service contracts of each subset of IT service contracts to compute a gross profit probability distribution function for the IT service contracts of each subset of IT service contracts associated with that particular set of contract risk factors and risk factor values.
According to another aspect of the invention, a computer program storage medium readable by a computer, tangibly embodying a program of instructions executed by the computer may perform the method steps for profiling information technology (IT) service contract risks and generating contract prices.
a)-(d) are a series of graphs that illustrate the relationship between risk profile and price contingency, according to an embodiment of the invention.
Exemplary embodiments of the invention as described herein generally include systems and methods for estimating the profit distribution of a contract, given its assessed risks, before contract is signed, and pricing the contract based on the estimated profit distribution. Accordingly, while the invention is susceptible to various modifications and alternative fauns, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that there is no intent to limit the invention to the particular forms disclosed, but on the contrary, the invention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.
The difference between a low risk and a high risk contract is in the probability distribution for achieving a certain profit. For example, a low risk contract has a “tighter” distribution, or less (in particular, down-side) variability in its profitability, while a high risk contract has a “wider” distribution or more variability in its profitability outlook. A base price can be determined by the estimated cost of delivering the contract, plus the target profit. For risky contracts, the variability in its profitability outlook comes from the fact its delivery cost may be underestimated. If the risks cannot be mitigated, then to compensate for such risks, a common approach is to increase the price, or to add “price contingency”. Without changing other aspects of a contract, the effect of adding price contingency is to shift the profitability distribution, so that the probability of achieving or exceeding a certain profit x, P(profit>=x), can be increased. Assuming everything else is the same, a higher risk contract needs more price contingency to achieve the same P(profit>=x), than a lower-risk contract.
Exemplary embodiments of the invention mine historical risk data to identify the key risks that contribute to financial losses in service contracts. Risk factors are identified and quantified through human input, such as questionnaires, in combination with text mining from standard documents, such as contract documents. Iterative and repeatable mining is needed due to the ever-changing environment in the service industry. A list of risk factors associated with service contracts includes service requirements, contract terms and conditions, delivery resources, technical solutions, the client environment, cost and budget, etc. Additional risk factors are listed in the table of
Contract risk profiling uses the identified risk factors to create profiles that can be matched with newly signed contracts. A method for profiling contract risks and generating pricing recommendations according to an embodiment of the invention includes the following steps, illustrated in the flowchart shown in
An example of a regression tree risk profile classifier according to an embodiment of the invention is shown in
Given a matched contract risk profile, the individual impact of each key risk can be predicted, as well as the aggregated impact on overall profitability, in actual dollars of a gross profit percentage. With such prediction, a user can: (1) determine those risks that can be mitigated; (2) project profitability and adjust pricing to compensate for risks; and (3) review risk insights. For those risks that can be mitigated, an expert can assign new risk factor values for the mitigated IT service contract and the classifier can reclassify the IT service contract according to the new risk factor values.
Referring again to
a)-(d) illustrate the relationship between a risk profile and a price contingency.
In the above pricing scenario, all parameters, such as profit target, risk appetite, estimated delivery cost, etc., can be determined, except for the profitability distribution of the new contract to be signed.
A risk profiler according to an embodiment of the invention can use the empirical profitability distribution output from the Risk Analytics Engine classifier based on all historical contracts in the same class or profile as this new contract. With this distribution and the other input parameters, one can compute an optimal price contingency to be added to the price, given a certain target of P(profit>=x). For example, suppose the current portfolio has n contracts belonging to up to k profiles, where k is the maximum number of profiles identified in step 31 of
An example of an optimal price contingency calculation according to an embodiment of the invention is illustrated in
where μ is the mean gross profit margin of the distribution, and σ is the standard deviation of the distribution. Then, the confidence or predicted probability of achieving a gross profit margin x is:
In the present example, for which an 80% confidence level of achieving a gross profit of $x is needed to go forward with the contract, if Φ(x)<80%, a contingency, i.e. the amount of a price adder c, is needed to improve the confidence level to 80%: c=μ′−μ. The price adder c can be determined from the cumulative distribution integral:
This price adder c has the effect of shifting the gross profit margin pdf to the right on the gross profit (GP) axis by the amount c, as shown by graph 61.
Thus, referring again to
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The computer system 71 also includes an operating system and micro instruction code. The various processes and functions described herein can either be part of the micro instruction code or part of the application program (or combination thereof) which is executed via the operating system. In addition, various other peripheral devices can be connected to the computer platform such as an additional data storage device and a printing device.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
While the present invention has been described in detail with reference to exemplary embodiments, those skilled in the art will appreciate that various modifications and substitutions can be made thereto without departing from the spirit and scope of the invention as set forth in the appended claims.