Computerized method, computer program product and computer environment

The following application relates to a computerized method for processing and displaying data, a computer program product and a computer environment.

There exists an increasing demand for providing economic evaluation of business units, such as real estate, vehicle parks, etc. A conventional statistical approach for asset valuation, in particular for evaluating a business unit can be a discounted cash flow (in the following referred to as "DCF") calculation, as described in the following.

Survey of current definitions and methods of a DCF calculation

In the following there is provided an exemplary overview of a common discounted cash flow calculation method, as it is available under www.wikipedia.org.

Common definition of a discounted cash flow calculation:

Definition

In finance, the discounted cash flow (DCF) approach describes a method to value a project or an entire company using the concepts of the time value of money. The DCF methods determine the present value of future cash flows by discounting them using the appropriate cost of capital. This is necessary because cash flows in different time periods cannot be directly compared since most people prefer money sooner rather than later (put simply: a dollar in your hand today is worth more than a dollar you may receive at some point in the future). The same logic applies to the difference between certain cash flows and uncertain ones, or "a bird in the hand is worth two in the bush". This is due to opportunity cost and risk over time. DCF procedure involves three problems: <ul id="ul0001" list-style="dash" compact="compact"><li>the forecast of future cash flows,</li><li>the incorporation of taxes (firm income taxes as well as personal income taxes),</li><li>the determination of the appropriate cost of capital.</li></ul>

Discounted cash flow analysis is widely used in investment finance, real estate development, and corporate financial management. Depending on the financing schedule of the company four different DCF methods are distinguished today. Since the underlying financing assumptions are different they do not need to arrive at the same value of the project or company: <ul id="ul0002" list-style="bullet" compact="compact"><li>Equity-Approach <ul id="ul0003" list-style="none" compact="compact"><li>○ Flows to equity approach (FTE)</li></ul></li><li>Entity-Approach: <ul id="ul0004" list-style="none" compact="compact"><li>○ Adjusted present value approach (APV)</li><li>○ Weighted average cost of capital approach (WACC)</li><li>○ Total cash flow approach (TCF)</li></ul></li></ul>

Mathematics

The discounted cash flow formula is derived from the future value formula for calculating the time value of money and compounding returns. <maths id="math0001" num=""><math display="block"><mi mathvariant="italic">FV</mi><mo mathvariant="italic">=</mo><mi mathvariant="italic">PV</mi><mo>⋅</mo><mrow><mo>(</mo><mn>1</mn><mo>+</mo><mi>i</mi><mo>⁢</mo><msup><mrow><mo>)</mo></mrow><mi>n</mi></msup></mrow></math><img file="EP1988499A1_D0001.tif" /></maths>

The simplified version of the Discounted cash flow equation (for one cash flow in one future period) is expressed as: <maths id="math0002" num=""><math display="block"><mi mathvariant="italic">DPV</mi><mo>=</mo><mfenced><mfrac><mi mathvariant="italic">FV</mi><mrow><mo>(</mo><mn>1</mn><mo>+</mo><mi>d</mi><mo>⁢</mo><msup><mrow><mo>)</mo></mrow><mi>n</mi></msup></mrow></mfrac></mfenced><mo>,</mo></math><img file="EP1988499A1_D0002.tif" /></maths> where <ul id="ul0005" list-style="none" compact="compact"><li>DPV is the discounted present value of the future cash flow (FV), or FV adjusted for the opportunity cost of future receipts and risk of loss;</li><li>FV is the nominal value of a cash flow amount in a future period;</li><li>d is the discount rate, which is the opportunity cost plus risk factor (or the time value of money: "i" in the future-value equation);</li><li>n is the number of discounting periods used (the period in which the future cash flow occurs). I.e. if the receipts occur at the end of year 1, n will be equal to 1; at the end of year 2, 2-likewise, if the cash flow happens instantly, n becomes 0, rendering the expression an identity (DPV=FV).</li></ul>

Where multiple cash flows in multiple time periods are discounted, it is necessary to sum them as follows: <maths id="math0003" num=""><math display="block"><mi>DPV</mi><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>t</mi><mo>=</mo><mn>0</mn></mrow><mi>N</mi></munderover></mstyle><mfrac><msub><mi mathvariant="italic">FV</mi><mi>t</mi></msub><mrow><mo>(</mo><mn>1</mn><mo>+</mo><mi>d</mi><mo>⁢</mo><msup><mrow><mo>)</mo></mrow><mi>t</mi></msup></mrow></mfrac></math><img file="EP1988499A1_D0003.tif" /></maths> for each future cash flow (FV) at any time period (t) for all time periods. The sum can then be used as a net present value figure or used to further calculate the internal rate of return for a cash flow pattern over time.

Enterprise Evaluation:

Theoretically probability distributions have to be predicted for coming outputs. The probabilities can be interpreted only as subjective credibilities or grades of "taking-for-truth" of a result. Probabilities extracted from logical considerations or from interpretation of relative frequencies/occurrences are not to be obtained for purposes of enterprise evaluation. In my opinion practitioners resist appointing explicit properties for future outputs. They are able to refer to difficulties within their inspection justly. [Ballwieser, Springer, München 2004, p. 50f.]

However, the above estimate can be very difficult due to the large number of data, necessary to be handled. Moreover, said statistical evaluation approach is difficult due to the kind of data to be examined. Furthermore, a manual estimate by a human person is very cumbersome or even impossible due to the large data typically available and due to the nature of the data, which cannot be entirely overseen by a human person.

Accordingly, it is an object of the present invention to provide a possibility of evaluating a future evolution of a business unit.

This object is solved by the computerized method according to claim 1, the computer program product according to claim 13, and the computer environment according to claim 14. Preferred embodiments are subject to the dependent sub-claims.

Computerized method

One aspect of the present invention relates to a computerized method for processing and displaying data of a business unit comprising the steps: <ul id="ul0006" list-style="dash"><li>extracting a set of past data of said business unit from a past data base using a closed computer environment and introducing said set of past data into said closed computer environment;</li><li>extracting a set of future plan data of said business unit from a future plan data base using said closed computer environment and introducing said set of future plan data into said closed computer environment, wherein extracting of said set of future plan data comprises: <ul id="ul0007" list-style="none" compact="compact"><li>-- automatic determining and extracting of at least one preconfigured subset of said set of future plan data;</li><li>-- automatic extracting the remaining data of said future plan data from said data base;</li></ul></li><li>determining at least one estimate value from said set of past data and said set of future plan data, using said closed computer environment and</li><li>displaying said at least one determined estimate value.</li></ul>

Following that, in spite of a large set of past data and a large set of future plan data, advantageously, only very few parameters, namely the at least one estimate value is/are provided by the computerized method for evaluating the business unit. As an example, a large set of past data can be used. Said past data can comprise balance-data, including costs and income of the business unit. The business unit can be a real estate unit, comprising one or more real estates, such as apartments, apartment buildings, industrial buildings, supermarkets, warehouses, warehouse complexes etc. Additionally, a large set of future plan data is provided. Said future plan data can comprise e.g. possible future income, such as rent, increase of rent, and/or possible future costs, such as maintenance fees, etc.. Advantageously, from the large number of data, at least one single parameter, namely the at least one estimate value is determined and displayed, which is used for evaluation and comparison of the business unit. Following that, said business unit can be compared and/or evaluated manually, i.e. by a human person in an easy manner using said at least one determined estimate value. Therefore, with this improved way of displaying data, a large number of data can be processed and visualized more efficiently.

Further advantageously, at least one pre-configured subset of the future plan data can be chosen by an operator of the computerized method and/or by the computerized method itself. Said pre-configured subset of said future plan data can be determined and said data and can be extracted automatically. Moreover, the remaining (sets of) future plan data are preferably extracted automatically from the data-base comprising all the future plan data.

Following that, further advantageously, it is possible to assure that a specific subset of the future plan data is extracted. In particular, it is possible to provide specific methods and/or ways of extracting such a pre-configured subset of future plan data. This can be particularly the case, when specific routines and/or methods are necessary for determining and/or extracting said pre-configured subset of said future plan data. As an example, the specific future plan data can be included in one or more floating text-files and/or pdf-files and/or picture-files, etc. Therefore, specific methods can be applied for extracting data from said files. Moreover, further future plan data can be provided as entries in a table. Therefore, said data can be easily extracted by entering said data-base/tables and reading said data in a conventional manner.

Moreover, not necessarily two databases need to be provided. Rather, the past data base and the future data base can be part of a common data base. Moreover, a database can be one or more tables. In other words, the past data and the future plan data can be comprised in one table.

Further advantageously, it is possible not only to obtain at least one value, namely the at least one estimate value, from a large number of given data. Moreover, it is also possible to simulate different values from the large number of data. As an example one or more subsets of the large number of data can be changed and/or taken away from the given data. Following that, the at least one estimate value can be determined again and can be compared e.g. to the at least one estimate value determined with the entire subset. This step can also be carried out iteratively for one or more (different) subsets of data. Thereby, effect of one or more such subsets of data on the at least one business unit can be determined easily. As an example, the at least one estimate value can be the discounted cash flow value of a business unit. The business unit can comprise a number of real estate objects. By changing the elements of the business unit, i.e. by deleting and/or introducing one or more further real estate objects, the effect of said objects on the estimate value can be easily determined.

Moreover, it may also be possible to determine the at least one estimate value depending from the market traded interest and/or from the degree of risk aversion (see below). It may be possible to provide a graphical display of the at least one estimate value as a function of the market traded interest and/or the degree of risk aversion.

In the present application, the term "determine" can be synonymous to the term "calculate".

In particular, the set of past data and the set of future plan data can be subsets of a common set of data. In particular, the past data can be extracted by a subsystem of the closed computer environment. Said subsystem can e.g. be a SAP QS system. Said subsystem can particularly be a source system. The SAP QS system is e.g. a so called Online Transactional Processing system, also referred to as an OnLine Analytical Processing system (OLAP system). An OLAP system conventionally comprises or represents a decision support software that allows the user to quickly analyze information that has been summarized into multidimensional views and hierarchies.

Also the future plan data can be extracted by an SAP QS system. The database comprising the past and the future plan data can be part of the closed computer environment. At least part of the past data and/or the future plan data can be extracted by the SAP QS system into the closed computer environment. As an example, when automatically determining and extracting the subset of the future plan data, one or more statistical calculation(s) can be carried out. As an example, for the subset, a likelihood and/or an estimate can be provided, indicating the uncertainty of a value of one or more members of said subset. For the remaining subset of future plan data, as an example, no likelihood and/or no estimate, indicating the uncertainty of the values the members of said subset is provided. Rather, these future plan data are taken as given in the remaining subset.

Extracting the past data and the future plan data also comprises the step of providing the past data and the future plan data to another subsystem of the closed computer environment which e.g. is an SAP BW system. An SAP BW system is/comprises Data warehouse used as a basis for making strategic and operational decisions in companies. It combines state-of-the-art warehousing technology with preconfigured business content, and gives users a clear overview of company-internal data and any external data that is relevant. SAP Business Information Warehouse (SAP BW) contains a wide selection of predefined reports that have been specially tailored to meet the needs of specific industry sectors and user groups, for example production planners, financial controllers, human resource managers. The SAP BW system is e.g. a so called Online Transactional Processing system, also referred to as OLTP system. The OLTP system can be a conventional SAP ERP system. The SAP BW may be used to determine, in particular calculate the at least one estimate value.

In other words the computerized method allows an efficient way of extracting data, using a subsystem of the closed computer system. Said extracting step can comprise manipulating at least a subset of said data, e.g. the future plan data. Said data is the provided to the another subset of the closed computer environment, which then determines the at least one estimate value.

Further embodiments of the computerized method

The closed computer environment system may, as an example, be or comprise a specific system application that is or can be installed on the computers of a company, such as a real estate management company. The specific system application may be a standard SAP product, e.g., a standard SAP computer program. In particular, the system application may be SAP R/3, and/or SAP, such as SAP ERP, SAP business suite, etc. Particularly, closed computer environment may be based on SAP R/3, and/or SAP, such as SAP ERP, SAP business suite or modifications thereof.

Advantageously, according to an embodiment, it is possible, to provide and/or manipulate and/or evaluate a large number of data, which can relate to real estate, as an example of a business unit, in an SAP environment, as described above. Data can, as an example, be imported and/or visualized using a conventional table calculation program, such as Microsoft Excel. Consequently, it is possible to evaluate a large number of data fast and effectively within one system.

According to a specific embodiment, the step of automatically determining and extracting said at least one pre-configured subset of said future plan data comprises: <ul id="ul0008" list-style="none"><li>-- automatic evaluation of contract data;</li><li>-- automatic determining and extracting of said at least one pre-configured subset of said set of future plan data from contract data.</li></ul>

Following that, it is possible to provide a large number of contract data as part of the data-base, and said contract data can be provided as pdf-files, text-files, picture-files, such as jpeg-files, sql-files, xml files, etc. Using specific methods and/or routines, single or multiple elements of said files can be determined and extracted from said files. As an example, said contract data can comprise a text-file of a rent-contract. Using a specific algorithm and/or method and/or routine said text-file can be examined, and e.g. a value of a rent and/or a contracted time period of said rent and/or a contracted increase of said rent, etc can be extracted automatically.

According to a further embodiment, said at least one estimate value is calculated using the equation: <maths id="math0004" num=""><math display="block"><msub><mi mathvariant="italic">DCF</mi><mi>c</mi></msub><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>t</mi><mo>=</mo><mn>1</mn></mrow><mi>∞</mi></munderover></mstyle><mfrac><mrow><msub><mi>f</mi><mi>c</mi></msub><mo>⁢</mo><mfenced separators=""><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mfenced></mrow><msup><mfenced separators=""><mn>1</mn><mo>+</mo><msub><mi>i</mi><mrow><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mrow></msub></mfenced><mi>t</mi></msup></mfrac><mo>;</mo><msub><mi>f</mi><mi>c</mi></msub><mfenced><mi>t</mi></mfenced><mo>:</mo><mo>=</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>0</mn></msub></math><img file="EP1988499A1_D0004.tif" /></maths> wherein <ul id="ul0009" list-style="none"><li><i>i_t</i> represents a market traded interest at time index <i>t</i> and</li><li><i>t</i>₀; 0 ≤ <i>t</i>₀ ≤ <i>n</i> represents the index of a predetermined date.</li><li><i>β̂</i>₀ represents the statistical estimator for parameter <i>β</i>₀</li></ul> and/or wherein said at least one estimate value (80, 108) is calculated using the equation: <maths id="math0005" num=""><math display="block"><msub><mi mathvariant="italic">DCF</mi><mi>l</mi></msub><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>t</mi><mo>=</mo><mn>1</mn></mrow><mi>∞</mi></munderover></mstyle><mfrac><mrow><msub><mi>f</mi><mi>l</mi></msub><mo>⁢</mo><mfenced separators=""><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mfenced></mrow><msup><mfenced separators=""><mn>1</mn><mo>+</mo><msub><mi>i</mi><mrow><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mrow></msub></mfenced><mi>t</mi></msup></mfrac><mo>;</mo><msub><mi>f</mi><mi>l</mi></msub><mfenced><mi>t</mi></mfenced><mo>:</mo><mo>=</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>0</mn></msub><mo>+</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>1</mn></msub><mo>⁢</mo><mi>t</mi><mo>,</mo></math><img file="EP1988499A1_D0005.tif" /></maths> wherein <ul id="ul0010" list-style="none"><li><i>i_t</i> represents a market traded interest at time index <i>t</i> and</li><li><i>t</i>₀; 0≤<i>t</i>₀≤<i>n</i> represents the index of a predetermined date.</li><li><i>β̂</i>₀ represents the statistical estimator for parameter <i>β</i>₀</li><li><i>β̂</i>₁ represents the statistical estimator for parameter <i>β</i>₁</li></ul> and/or wherein said at least one estimate value (82, 110) is calculated using the equation: <maths id="math0006" num=""><math display="block"><msub><mi mathvariant="italic">DCF</mi><mi>n</mi></msub><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>t</mi><mo>=</mo><mn>1</mn></mrow><mi>∞</mi></munderover></mstyle><mfrac><mrow><msub><mi>f</mi><mi>n</mi></msub><mo>⁢</mo><mfenced separators=""><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mfenced></mrow><msup><mfenced separators=""><mn>1</mn><mo>+</mo><msub><mi>i</mi><mrow><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mrow></msub></mfenced><mi>t</mi></msup></mfrac><mo>;</mo><msub><mi>f</mi><mi>n</mi></msub><mfenced><mi>t</mi></mfenced><mo>:</mo><mo>=</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>0</mn></msub><mo>+</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>1</mn></msub><mo>⁢</mo><msup><mi>t</mi><mrow><mover><mi>β</mi><mo>^</mo></mover><mo>⁢</mo><mn>2</mn></mrow></msup><mo>,</mo></math><img file="EP1988499A1_D0006.tif" /></maths> wherein <ul id="ul0011" list-style="none"><li><i>i_t</i> represents a market traded interest at time index <i>t</i> and</li><li><i>t</i>₀; 0 ≤ <i>t</i>₀<i>≤ n</i> represents the index of a predetermined date.</li><li><i>β̂</i>₀ represents the statistical estimator for parameter <i>β</i>₀</li><li><i>β̂</i>₁ represents the statistical estimator for parameter <i>β</i>₁</li><li><i>β̂</i>₂ represents the statistical estimator for parameter <i>β</i>₂.</li></ul>

In the above, DCF_c relates to a constant DCF approach, DCF_l relates to a linear DCF approach and DCF_n relates to a non linear DCF approach.

Following that, as specific examples, one estimate value, two estimate values or three estimate values can be provided by the method. Said estimated values can be calculated, using different equations, as described above. Said equations represent different specific methods of processing said large number of data provided in said data-base(s). Following that, using said large number of data one parameter can be generated, which is the estimate value. Alternatively, two parameters can be generated, which are two estimate values or three parameters can be generated, which are three estimate values. Using said one, two, three estimate values the business unit can be evaluated by a human person using said computerized method in a simple and effective manner. In particular, a very good evaluation is possible by comparing two or three estimate values. Consequently, an efficient way of processing and evaluating a large amount of data is possible. In particular, it is possible to provide an automatic way of processing data, which then can be evaluated manually. Without said computerized method, an automatic evaluation of said large number of data would not be possible. In particular, is possible to provide an automated processing of data of a business unit, which can otherwise not be processed and evaluated. Moreover, said at least one estimate value allows a comparison of different business unit, which could otherwise not be compared. Hence, an automated method is provided for comparing two or more business units. In particular, the comparison of said at least one estimate value per business unit can be carried out automatically, as well. A result of said comparison can be displayed.

The term <i>β</i>₀ can e.g. be a conventional DCF value.

According to a further embodiment for the at least one estimate value, a limit factor <i>I_m</i> is calculated using the equation: <maths id="math0007" num=""><math display="block"><msub><mi>l</mi><mi>m</mi></msub><mo>:</mo><mo>=</mo><mfrac><msubsup><mi mathvariant="italic">DCF</mi><mi>m</mi><mi>r</mi></msubsup><mrow><msub><mi>f</mi><mi>m</mi></msub><mo>⁢</mo><mfenced separators=""><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mn>1</mn></mfenced></mrow></mfrac><mn>.</mn></math><img file="EP1988499A1_D0007.tif" /></maths>

The limit factor <i>l_m</i> can also be referred to as the limit m. In particular, the non-linear approach and the linear approach can be easily compared in an automated manner.

Moreover, the risk-premium can be chosen manually or automatically.

According to another embodiment, a risk-premium is between approx. 80 % and approximately 99 %, in particular approximately 95 %. In particular, the risk premium RP can depend on the level of confidence the human person using the computerized method wants to obtain. In other words, the value of the risk premium RP can be chosen manually.

According to another embodiment, said step of extracting said set of past data and said step of extracting said set of future plan data comprise the step: <ul id="ul0012" list-style="none" compact="compact"><li>displaying an activating device for simultaneously activating said extraction of at least one subset of said set of past data, and at least one subset of said future plan data.</li></ul>

In other words, e.g. on a display of said computer environment, a button can be displayed. When activating said button, e.g. by a pointing device, such as a mouse, a track ball, a touch pad, etc., at least one subset of said past data, and at least one subset of said future plan data are extracted simultaneously. Said at least one subset of said past data, and at least one subset of said future plan data can be referred to as a category of the past data and a category of the future plan data. Moreover, multiple categories of the past data and multiple categories of the future plan data can be extracted simultaneously. As an example, maintenance cost data, as an exemplary category of past data and the future plan data can be extracted simultaneously for the past and the future plan data.

According to another embodiment, said step of extracting said set of past data and said step of extracting said set of future plan data comprises: <ul id="ul0013" list-style="none" compact="compact"><li>displaying an activation device simultaneously activating said extraction of a plurality of subsets of said past data and plurality of subsets of said future plan data.</li></ul>

In other words, when e.g. a button, as a preferred activation device, is activated or selected, maintenance data and/or rent data, etc. can be selected and provided. As a further subset, when activating said button, value adjustment data, etc., as a further subset of past data and future plan data can be provided for the past and future plan data, simultaneously.

According to a further embodiment, after extracting said at least one set of past data and said at least one set of future plan data, said data are displayed to a user for manual inspection.

In other words, all or a fraction of said extracted past data and said extracted future plan data is displayed to the user. Such a display can be carried out in form of a large table or a number of tables. Although, as described above, a manual evaluation of the business unit is hardly or not possible for the user due to the large number of data, the user can verify single entries of said data. In particular, all the extracted past data and all the extracted future plan data can be displayed to the user. The user is able to change, in particular correct one or more of said past data and said future plan data.

According to a further embodiment, a choice of a present date is made manually and, after choice of the present date, the set of past data and the set of future plan data are determined automatically.

In other words, a large number of data is available, wherein not necessarily past data and future plan data are indicated as past or future plan data. Rather some or all of the data can be provided with a date. The user can choose the present date. Consequently, data having a date prior to the present date can be referred to as past data. Data having a date after the present date preferably is referred to as future plan data.

According to a further embodiment, a choice of a present interval is provided manually, wherein said set of past data is provided for a past interval and wherein said set of future plan data is provided for a future interval automatically.

In other words, the user can choose a present date. Further, the user can choose an interval of a past date. Such interval can e.g. be a number of years. As an example, the user can choose the interval for the set of past data of three years. An interval can also be one year. Hence, even though past data for e.g. the past 5, 10, 15, 20, etc. years can be available, the computerized method only uses the past data for the last three years, starting from the present date. Moreover, the user can choose an entire interval for the computerized method; e.g. such interval can be 5, 10, 15, 20, 25, 30, 40, 50, 70, 90, etc. years. When the user e.g. chooses/selects 50 years for the entire interval and selects as the interval for the set past data 3 years, the past data is extracted for the last 3 years. The future plan data is extracted for the next 47 years.

Alternatively, it is also possible, that the user does not set the entire interval, but sets the interval for the past data and also for the future plan data independently. As an example, the past data can be extracted for the last 3, etc. years. The future plan data can be extracted for the next 50, etc. years.

Following that, according to such an embodiment, the set of past data and the set of future plan data is automatically determined using the present date and said interval.

As a further alternative, e.g. every year can be referred to as an interval, and for a number of intervals the past data can be provided. As an example, for 5 years past data can be provided. For the time following said intervals, for which past data is provided, future plan data is provided. In this example, e.g. for the years 6 to 50, future plan data is provided. The user then can choose any interval he likes, e.g. interval number 4. Consequently, past data is provided for the intervals, e.g. the years 1 to 3. Future plan data is provided for the intervals 4 to 50. However, the future plan data for the interval, e.g. the year 6, not necessarily needs to be an estimation but can be data that is already given (strictly speaking as past data).

According to a further embodiment, for the future plan data an individual estimate value can be determined automatically for every time unit of said future interval.

In other words, for e.g. every year one or more estimate values can be determined. The term "determined" in the sense of the present application is referred to as calculated and/or estimated and/or taken from a table, etc. For every time unit, e.g. for every year, an individual estimate value can be determined. In particular, the estimate value can be calculated for a number of subunits of the business unit. The estimate value of the business unit can be calculated from the number of estimate values of the subunits of the business unit.

Computer program product

A further aspect of the present application relates to a computer program product, in particular stored in a computer readable medium or as a signal which, when loaded in the memory of a computer carries out the method according to the invention.

Computer environment

Another aspect of the application relates to a computer environment for processing and displaying data of a business unit comprising: <ul id="ul0014" list-style="none"><li>a past data extractor which is adapted for extracting a set of past data of said business unit from a past data base, wherein the computer environment is a closed computer environment and wherein said extractor is adapted for introducing said set of past data into said closed computer environment</li><li>a future plan data extractor which is adapted for extracting a set of future plan data of said business unit from a future plan data base and wherein said future plan data extractor is adapted for introducing said set of future plan data into said closed computer environment, wherein</li></ul> said future plan data extractor comprises: <ul id="ul0015" list-style="dash" compact="compact"><li>a determinator which is adapted for automatically determining and extracting at least one preconfigured subset of said set of future plan data</li><li>a remaining data extractor which is adapted for automatically extracting the remaining data of said future plan data from said data base</li></ul> an estimate value determinator which is adapted for determining at least one estimate value from said set of past data and said set of future plan data, using said closed computer environment and a display which is adapted for displaying said determined estimate value.

Further embodiments of the computer environment

According to an embodiment, said future plan data extractor, in particular said determinator of said future plan data extractor comprises a reader, which is adapted for automatically reading contract data, wherein said determinator is adapted for automatically determining and extracting said at least one pre-configured subset of said set of future plan data and said contract data.

According to a further embodiment, said displays adapted to display said past data and said future plan data.

According to a further embodiment, said display is adapted to display at least one estimate value.

Moreover, the present application can also relate to a method for determining a value of a business unit, comprising the steps: <ul id="ul0016" list-style="dash"><li>providing past data of the business unit for a given first period of time in the past;</li><li>providing future plan data of said business unit for a given second period of time in the future;</li><li>determining from the past data and the future plan data at least one value of the business unit using one or more business-calculation-models of the set comprising constant business-calculation-model and a linear business-calculation-model and a non-linear business-calculation-model.</li></ul>

As an example, the past data of the business unit and/or the future plan data of said business unit are extracted from an external database. The past data can comprise data of the business unit from the past, up to now. The future plan data can comprise e.g. assumptions of the business unit for the future.

As a further example, the business unit includes one or more rental objects.

According to an embodiment, the determination of said value of said business unit includes at least one of planning positions and profit center groups.

According to another embodiment, said method includes at least one of the following five categories of plan positions: <ul id="ul0017" list-style="dash" compact="compact"><li>revenues;</li><li>operating costs;</li><li>maintenance;</li><li>building operation; and</li><li>building administration,</li></ul> wherein said five categories constitute a cash flow.

In a further embodiment, the future plan data includes individual rental contract data of the business unit.

Exemplary, at least one of the past data of the business unit and the future plan data of said business unit are provided on an annual basis.

Further exemplary, said value of said business unit includes a discounted cash flow.

In another example, for calculating the discounted cash flow, market traded annual interest rates are taken into account for a period of 50 years.

According to an embodiment, using said constant business-calculation-model said discounted cash flow, as a specific value of said business unit is calculated using the equation: <maths id="math0008" num=""><math display="block"><msub><mi mathvariant="italic">DCF</mi><mi>c</mi></msub><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>t</mi><mo>=</mo><mn>1</mn></mrow><mi>∞</mi></munderover></mstyle><mfrac><mrow><msub><mi>f</mi><mi>c</mi></msub><mo>⁢</mo><mfenced separators=""><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mfenced></mrow><msup><mfenced separators=""><mn>1</mn><mo>+</mo><msub><mi>i</mi><mrow><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mrow></msub></mfenced><mi>t</mi></msup></mfrac><mo>;</mo><msub><mi>f</mi><mi>c</mi></msub><mfenced><mi>t</mi></mfenced><mo>:</mo><mo>=</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>0</mn></msub></math><img file="EP1988499A1_D0008.tif" /></maths> wherein <ul id="ul0018" list-style="none"><li><i>i_t</i> represents a market traded interest at time index <i>t</i> and</li><li><i>t</i>₀; 0 ≤ <i>t</i>₀ ≤ <i>n</i> represents the index of a predetermined date.</li><li><i>β̂</i>₀ represents the statistical estimator for parameter <i>β</i>₀.</li></ul>

According to a further embodiment, using said linear business-calculation-model said discounted cash flow, as a specific value of said business unit is calculated using the equation: <maths id="math0009" num=""><math display="block"><msub><mi mathvariant="italic">DCF</mi><mi>l</mi></msub><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>t</mi><mo>=</mo><mn>1</mn></mrow><mi>∞</mi></munderover></mstyle><mfrac><mrow><msub><mi>f</mi><mi>l</mi></msub><mo>⁢</mo><mfenced separators=""><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mfenced></mrow><msup><mfenced separators=""><mn>1</mn><mo>+</mo><msub><mi>i</mi><mrow><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mrow></msub></mfenced><mi>t</mi></msup></mfrac><mo>;</mo><msub><mi>f</mi><mi>l</mi></msub><mfenced><mi>t</mi></mfenced><mo>:</mo><mo>=</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>0</mn></msub><mo>+</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>1</mn></msub><mo>⁢</mo><mi>t</mi><mo>,</mo></math><img file="EP1988499A1_D0009.tif" /></maths> wherein <ul id="ul0019" list-style="none"><li><i>i_t</i> represents a market traded interest at time index <i>t</i> and</li><li><i>t</i>₀; 0 ≤ <i>t</i>₀ ≤ <i>n</i> represents the index of a predetermined date.</li><li><i>β̂</i>₀ represents the statistical estimator for parameter <i>β</i>₀</li><li><i>β̂</i>₁ represents the statistical estimator for parameter <i>β</i>₁.</li></ul>

Furthermore, using said non-linear business-calculation-model said discounted cash flow, as a specific value of said business unit can be calculated using the equation: <maths id="math0010" num=""><math display="block"><msub><mi mathvariant="italic">DCF</mi><mi>n</mi></msub><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>t</mi><mo>=</mo><mn>1</mn></mrow><mi>∞</mi></munderover></mstyle><mfrac><mrow><msub><mi>f</mi><mi>n</mi></msub><mo>⁢</mo><mfenced separators=""><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mfenced></mrow><msup><mfenced separators=""><mn>1</mn><mo>+</mo><msub><mi>i</mi><mrow><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mrow></msub></mfenced><mi>t</mi></msup></mfrac><mo>;</mo><msub><mi>f</mi><mi>n</mi></msub><mfenced><mi>t</mi></mfenced><mo>:</mo><mo>=</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>0</mn></msub><mo>+</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>1</mn></msub><mo>⁢</mo><msup><mi>t</mi><mrow><mover><mi>β</mi><mo>^</mo></mover><mo>⁢</mo><mn>2</mn></mrow></msup><mo>,</mo></math><img file="EP1988499A1_D0010.tif" /></maths> wherein <ul id="ul0020" list-style="none"><li><i>i_t</i> represents a market traded interest at time index <i>t</i> and</li><li><i>t</i>₀; 0 ≤ <i>t</i>₀<i>≤ n</i> represents the index of a predetermined date.</li><li><i>β̂</i>₀ represents the statistical estimator for parameter <i>β</i>₀</li><li><i>β̂</i>₁, represents the statistical estimator for parameter <i>β</i>₁</li><li><i>β̂</i>₂ represents the statistical estimator for parameter <i>β</i>₂</li></ul>

Moreover, the future cash flow developments can be compared by calculating the limit factor <i>I_m</i> using the equation: <maths id="math0011" num=""><math display="block"><msub><mi>l</mi><mi>m</mi></msub><mo>:</mo><mo>=</mo><mfrac><msubsup><mi mathvariant="italic">DCF</mi><mi>m</mi><mi>r</mi></msubsup><mrow><msub><mi>f</mi><mi>m</mi></msub><mo>⁢</mo><mfenced separators=""><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mn>1</mn></mfenced></mrow></mfrac><mn>.</mn></math><img file="EP1988499A1_D0011.tif" /></maths>

Description of the figures

One or more embodiments of the present application are described in the following with reference to the Figures, wherein there is shown in <ul id="ul0021" list-style="none" compact="compact"><li><figref idref="f0001">Figure 1</figref>: an exemplary display of data;</li><li><figref idref="f0002">Figure 2</figref>: an exemplary display of data;</li><li><figref idref="f0003">Figure 3</figref>: an exemplary display of data;</li><li><figref idref="f0004">Figure 4</figref>: an exemplary display of data;</li><li><figref idref="f0005">Figure 5</figref>: an exemplary display of data;</li><li><figref idref="f0006">Figure 6</figref>: an exemplary display of data;</li><li><figref idref="f0007">Figure 7</figref>: an exemplary display of data;</li><li><figref idref="f0008">Figure 8</figref>: an exemplary display of data;</li><li><figref idref="f0009">Figure 9</figref>: an exemplary display of data;</li><li><figref idref="f0010">Figure 10</figref>: an exemplary display of data;</li><li><figref idref="f0011">Figure 11</figref>: an exemplary display of data;</li><li><figref idref="f0012">Figure 12</figref>: an exemplary display of data;</li><li><figref idref="f0013">Figure 13</figref>: an exemplary display of data;</li><li><figref idref="f0014">Figure 14</figref>: a schematic overview of components the computerized method;</li><li><figref idref="f0015">Figure 15</figref>: an exemplary display of data,</li><li><figref idref="f0016">Figure 16</figref>: an exemplary display of data;</li><li><figref idref="f0017">Figure 17</figref>: an exemplary display of data;</li><li><figref idref="f0018">Figure 18</figref>: an exemplary display of data;</li><li><figref idref="f0019">Figure 19</figref>: an exemplary display of data;</li><li><figref idref="f0020">Figure 20</figref>: an exemplary display of data;</li><li><figref idref="f0021">Figure 21</figref>: an exemplary display of data,</li><li><figref idref="f0022">Figure 22</figref>: an exemplary display of data;</li><li><figref idref="f0023">Figure 23</figref>: an exemplary display of data;</li><li><figref idref="f0024">Figure 24</figref>: an exemplary display of an evaluation;</li><li><figref idref="f0025">Figure 25</figref>: an exemplary display of an evaluation;</li><li><figref idref="f0026">Figure 26</figref>: an exemplary display of an evaluation;</li><li><figref idref="f0027">Figure 27</figref>: a schematic overview of components the computerized method;</li><li><figref idref="f0028">Figure 28</figref>: a schematic overview of components the computerized method;</li><li><figref idref="f0029">Figure 29</figref>: a schematic overview of components the computerized method;</li><li><figref idref="f0030">Figure 30</figref>: a schematic overview of a computer environment.</li></ul>

<figref idref="f0001"><b>Figure 1</b></figref> shows an exemplary display of data according to an embodiment of the present application. Particularly, <figref idref="f0001">figure 1</figref> can show a representation of a graphical user interface as part of an embodiment of the computerized method. More particularly, <figref idref="f0001">figure 1</figref> shows a variety of activation devices 10 which can be used for extracting past and future plan data. Moreover, <figref idref="f0001">figure 1</figref> shows a number of data 12. The data can comprise past data 14 and future plan data 16 of one or more subunits of a business unit. As an example, the business unit can be referred to as "GEWOFAG". The subunits can be one or more apartment buildings, e.g. referred to as "WE201 - Fürstenried I", "WE202 - Fürstenried I", "WE203 - Fürstenried I", ... "WE222 - Käpfelstr. 14 - 16". Consequently, according to <figref idref="f0001">Figure 1</figref>, data for determining cash flow on annual basis can be provided. In particular, past data for 5 years, namely the years 2002, 2003, 2004, 2005, 2006, is provided. Moreover, future plan data for 6 years, namely "Plan 2007", "Plan 2008", "Plan 2009", Plan 2010", "Plan 2011 ", and "Plan 2012" is provided. Said past data and said future plan data can be extracted from a data base. Particularly, said data can be loaded from said data base. Moreover, all conditions for rent-contracts can be simulated and loaded. Thereby, each document (also referred to as evidence, slip, voucher, record, etc.) in the profit centre calculation can be used as a data basis or as a data in a data basis for planning. The term "profit centre" can be used for the described method and/or the computer program implementation thereof.

Using basis-data (also referred to as "Stammdaten") credit/advance management and investment/capital accounting positions in a balance are planned. Possibly, the data can be manually corrected and/or adapted. Following that, planned data on an annual basis are determined, in particular, defined.

As shown in <figref idref="f0002"><b>figure 2</b></figref>, the future plan data per year, as shown in <figref idref="f0001">figure 1</figref>, can be divided in future plan data on a monthly basis. Moreover, during the course of the current year, the monthly future plan data can be exchanged by current data, i.e. data as actually received per year. As seen in <figref idref="f0002">figure 2</figref>, the current values for the first year are shown in column 18. In column 20 the future plan data for the current year is shown. In the subsequent columns 22 to 30, monthly desired values are shown in specific intervals. As an example, in columns 22 and 30 there are shown the monthly desired values within a 95 % confidence interval. In other words, every line represents a month of the first year. Following that, lines 1 to 5 (see column 32) are already provided with current values. Also for a said numbers, there are provided future plan data (reference is made to column 20). In columns 24 and 28 there is provided the monthly desired value according to the expectation variance. For details see below, in particular see section "Mathematics". In column 26 there is provided a monthly estimate value. Using said monthly values, as shown in columns 28 to 30, estimated values can be calculated on a yearly basis, as shown in table 34. Particularly, in column 36 the years are indicated. In columns 38 and 46 the estimate values per year are shown, comparable to the monthly estimated values according to columns 22 to 30. In other words, in columns 38 and 46 there is shown the yearly desired value. In particular the lower 95 % boundary and the upper 95 % boundary are shown in Tables 38 and 46. In columns 40 and 44 the yearly desired value according to expectation variance are shown and in column 42 the yearly estimated value is shown.

In graph 48 the values of table 34 are plotted. Particularly, graph 48 can provide a very effective warning system for determining and showing, whether the wanted values are reached or not.

<figref idref="f0003"><b>Figure 3</b></figref> shows an exemplary graphical interface for providing the estimate value per year. The estimate value can be referred to as a "discounted cash flow"-value (referred to SDCF-value). In particular, in <figref idref="f0003">figure 3</figref> there are shown past data in column 48 and 50, referred to as "Ist 2005", and "Ist 2006". Further, there are shown future plan data for the subsequent 6 time periods, referred to as "Plan 2007" in column 52, "Plan 2008" in column 54, "Plan 2009" in column 56, "Plan 2010" in column 58, "Plan 2011" in column 60, and "Plan 2012" in column 62. Column 64 refers to a description of the specific value of the respective columns 58 to 62. Particularly, as a part of the future plan data, discounting interest rates can be provided. In other words, the discounting interest rates can form a subset of the future plan data. The discounting interest rates are shown in line 66. Preferably, the discounting interest rates can be provided for the next 50 years. More particularly, the discounting interest rates can be guaranteed for the next 50 years.

Using said data, the cash flow can be calculated on an annual basis. Possible cash flows are shown in lines 68, 70 and 72. In line 68 the cash flow is shown, wherein for a future cash flow discounting interest rates are not taken into account. In line 70 the discounted cash flow is shown, however without any restoration and/or service and/or corrective maintenance of the respective business unit or subunit. In line 72 the discounted cash flow is shown.

In line 74 different values of the discounted cash flow as a specific estimate value, as the discounted cash flow is calculated according to different embodiments of the present application. Moreover, different deviations are shown, such as the deviation according to expectation variance, the deviation according to a 95 % confidence interval, etc.

<figref idref="f0004"><b>Figure 4</b></figref> shows a table 76 comprising values of discounted cash flows, calculated according to different embodiments of the present application. Particularly, in sub table 78, the discounted cash flow is calculated according to a constant model using the equation: <maths id="math0012" num=""><math display="block"><msub><mi mathvariant="italic">DCF</mi><mi>c</mi></msub><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>t</mi><mo>=</mo><mn>1</mn></mrow><mi>∞</mi></munderover></mstyle><mfrac><mrow><msub><mi>f</mi><mi>c</mi></msub><mfenced><mi>t</mi></mfenced></mrow><msup><mfenced separators=""><mn>1</mn><mo>+</mo><msub><mi>i</mi><mi>t</mi></msub></mfenced><mi>t</mi></msup></mfrac><mo>;</mo><msub><mi>f</mi><mi>c</mi></msub><mfenced><mi>t</mi></mfenced><mo>:</mo><mo>=</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>0</mn></msub><mn>.</mn></math><img file="EP1988499A1_D0012.tif" /></maths>

In sub table 80 the discounted cash flow is shown which is calculated according to a linear model using equation: <maths id="math0013" num=""><math display="block"><msub><mi mathvariant="italic">DCF</mi><mi>l</mi></msub><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>t</mi><mo>=</mo><mn>1</mn></mrow><mi>∞</mi></munderover></mstyle><mfrac><mrow><msub><mi>f</mi><mi>l</mi></msub><mfenced><mi>t</mi></mfenced></mrow><msup><mfenced separators=""><mn>1</mn><mo>+</mo><msub><mi>i</mi><mi>t</mi></msub></mfenced><mi>t</mi></msup></mfrac><mo>;</mo><msub><mi>f</mi><mi>l</mi></msub><mfenced><mi>t</mi></mfenced><mo>:</mo><mo>=</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>0</mn></msub><mo>+</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>1</mn></msub><mo>⁢</mo><mi>t</mi><mo>,</mo></math><img file="EP1988499A1_D0013.tif" /></maths>

In sub table 82 the discounted cash flow is shown, calculated according to a non-linear model using the equation: <maths id="math0014" num=""><math display="block"><msub><mi mathvariant="italic">DCF</mi><mi>n</mi></msub><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>t</mi><mo>=</mo><mn>1</mn></mrow><mi>∞</mi></munderover></mstyle><mfrac><mrow><msub><mi>f</mi><mi>n</mi></msub><mfenced><mi>t</mi></mfenced></mrow><msup><mfenced separators=""><mn>1</mn><mo>+</mo><msub><mi>i</mi><mi>t</mi></msub></mfenced><mi>t</mi></msup></mfrac><mo>;</mo><msub><mi>f</mi><mi>n</mi></msub><mfenced><mi>t</mi></mfenced><mo>:</mo><mo>=</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>0</mn></msub><mo>+</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>1</mn></msub><mo>⁢</mo><msup><mi>t</mi><msub><mover><mi>β</mi><mo>^</mo></mover><mn>2</mn></msub></msup><mn>.</mn></math><img file="EP1988499A1_D0014.tif" /></maths>

Moreover, in the columns the discounted cash flow values are shown for different time periods. Particularly, the discounted cash flow is shown for the future plan data of the years 2007, 2008, 2009, 2010, 2011, and 2012. Accordingly, in graphs 84, 86, 88 there are shown the discounted cash flow values and also the respective deviation difference. Graph 84 shows the discounted cash flow value and its evolution for the next 11 time periods, using a constant calculation model (see above). Graph 86 shows a discounted cash flow value and its evolution for the next 11 time periods, using a linear calculation model (see above). Graph 88 shows the discounted cash flow value and its evolution for the next 11 time periods, using a non linear calculation model (see above). Accordingly, in graphs 86, 88 the deviations are shown.

In the following, a detailed description of the calculation of the discounted cash flow values is provided. In particular, <figref idref="f0005"><b>figure 5</b></figref> shows a graphical user interface for providing past data and future plan data. Exemplary, <figref idref="f0005">figure 5</figref> shows a graphical user interface having buttons 90, which can be used for loading specific balance values. Said balance values can comprise past data and future plan data. In the table in <figref idref="f0005">figure 5</figref> there are provided past data for the years 2002 to 2006 and future plan data for the years 2007 to 2012, as mere examples of a method according to the present application. Exemplary, past data and future plan data are extracted simultaneously when activating one or more of buttons 90. Accordingly, using the buttons 90, in particular using buttons 90, referred to as "Lade ABS, BIL" and "Lade FIN, BIL", all the relevant data for real estate objects are provided from the investment accountancy and the credit management. Said data can be loaded from a data base and planning can be made with said data. In particular, said data can comprise bonds, liabilities, amortizations, liquidation, interest rates, acquisition and manufacturing costs, (value) adjustments, (accumulated) depreciation, provision for depreciation, accrual, etc. Moreover, profit and loss values can be provided by extraction from a data base. Particularly, said values can be provided by loading from a data base. The profit and loss values can particularly be provided using buttons 92. Said data are shown in <figref idref="f0006"><b>figure 6</b></figref>, which represents a view of a screen shot/graphical user interface (GUI), as shown in <figref idref="f0005">figure 5</figref>, at a later stage in time. Particularly, the lines comprising data referred to as "IRL_001" to "IRL_013", are subject of the specific planning functions and rules, which are exemplary described in the following (in particular referred to as sections 1.1.1.1. to 1.1.1.6. and sections 1.1.2. to 1.1.7.3.):

1.1.1.1. PF download OPC (operating costs expenditure)

Planning Rules for Portfolio Planning

The planning function 'download OPC (operating costs expenditure)' initiates the function module Z_BPS_002_RFC_CONS in the source system.

In order to transfer to BPS (which is an abbreviation of business planning and simulation) from the profit centre calculation, the function module selects the actual values of the past window, i.e. of the past five years including the planning year, limited to all of the OPC accounts. We identify as an OPC account all types of cost which are allocated to those plan items (TA ZBPS005) which are allocated to plan item type 'OPC' (TA ZBPS004). The allocation of the OPC items to the cost types is not arbitrary, but the extractor attributes different levels of significance to the individual plan items. He also requires a fixed scheme for allocating plan items to cost types (TA ZBPS005), without however checking its correctness. The user is responsible for this. The allocation logic is as follows: <ul id="ul0022" list-style="none" compact="compact"><li>The item <ul id="ul0023" list-style="bullet"><li>OPC_001 (EU rates) combines the three accounts which are allocated in the source system in the account locator of the incidental cost account (Table TIV80) to the rates account (OPC_009) in the 'Accounts for the distribution of net incidental costs' block, to the item 'Offset account RA' for the apportionable part, to the item 'Offset account RA' without further settlement' for the non-apportionable part, and to the item 'Offset account RU' for vacancy.</li><li>OPC_002 (EU operating costs) similarly to OPC_001 combines the three accounts which are allocated in the source system in the account locator of the incidental cost account to the operating costs account (OPC_010) in the 'Accounts for the distribution of net incidental costs' block.</li><li>OPC_003 (EU heating costs) similarly to OPC_001 combines the three accounts which are allocated in the source system in the account locator of the incidental cost account to the heating costs account (OPC_011) in the 'Accounts for the distribution of net incidental costs' block.</li><li>OPC_004 (non-deductible input tax) combines all of the accounts which are allocated in the source system in the account allocator of the incidental cost account to the three accounts for rates, operating costs and heating costs in the 'input tax' block in the 'Offset account - non-deductible input tax' field.</li><li>OPC_005 (credit - rates) refers to the account which is allocated in the source system in the account locator of the incidental cost account to the rates account in the 'Credit - accounting units' block in the 'Credit account AU' field.</li><li>OPC_006 (credit - operating costs) refers to the account which is allocated in the source system in the account allocator of the incidental cost account to the operating costs account in the 'Credit - accounting units' block in the 'Credit account AU' field.</li><li>OPC_007 (credit - heating costs) refers to the account which is allocated in the source system in the account locator of the incidental cost account to the heating costs account in the 'Credit - accounting units' block in the 'Credit account AU' field.</li><li>OPC_008 (credit - non-deductible input tax) combines all of the accounts which are allocated in the source system in the account locator of the incidental cost account to the three accounts for the rates, operating costs and heating costs in the 'input tax' block in the 'Credit - non-deductible input tax' field.</li><li>OPC_009 (AU rates) refers in the source system in the account locator of the incidental costs account (Table TIV80) to the rates account.</li><li>OPC_010 (AU operating costs) relates in the source system in the account locator of the incidental costs account (Table TIV80) to the operating costs account.</li><li>OPC_011 (AU heating costs) relates in the source system in the account allocator of the incidental costs account (Table TIV80) to the heating costs account.</li><li>OPC_012 (miscellaneous) includes all of the operating costing accounts which are not involved in the allocation to economic units, but are entered under companies.</li></ul></li></ul> The scheme divides the plan items into three groups: <ul id="ul0024" list-style="bullet" compact="compact"><li>debiting of the accounting units (OPC_009 - OPC_012),</li><li>crediting of the accounting units (OPC_005 - OPC_008),</li><li>debiting of the economic units (OPC_001 - OPC_004).</li></ul>

Background: The operating costs are recorded in accounting units (AU) and from here passed on to rental units (RU) and rental agreements (RA). The accounting to the rental units and rental agreements is partially implemented according to a complicated attribution scheme. Only for some accounting units is there a 1:1 relationship to economic units, whereas the rental units and rental agreements are directly allocated to the economic units. We require the plan values, but on the level of the economic units because the operating costs are introduced into the DCF calculation on this level. Therefore, for the planning we consider the actual values after (and not before) accounting to the rental units and rental agreements. The advantage of this approach is the logically tidy allocation of the operating costs, even if there is a year's time offset: Relevant to the invoice date (year of entering the debit in RU and RA) is the cost collector as an account assignment object. When entering a debit in the AU, the reference date is also given. By means of the reference date the correct cost collector is drawn in. Each year there is a new cost collector for each AU. The incidental costs settlement takes place once a year and always relates to exactly one year (reference year). However, the date of entering the debit in the AU can, but does not have to fall in the year following the settlement. Therefore, one can expect stronger fluctuations in the debit accounts of the AU. A disadvantage with this approach is that the offset accounts of the rental units and rental agreements (plan items OPC_001 - OPC_004) and the credit accounts of the AU (plan items OPC_005 - OPC_008) are not only allocated to the three AU accounts for rates, operating costs and heating costs (plan items OPC_009 - OPC_012), but to further secondary cost types (such as lift attendant activities, heating maintenance). In this way a non-differentiated picture is formed for the economic units.

In the first step the extractor considers the plan items of the debit of the economic units (OPC_001 - OPC_004), and does not do so aggregated on the overall level, but in detail on the EU level, and executes the following calculations: <ul id="ul0025" list-style="bullet"><li>debit EU, displayed directly on EU and the rest on top level Gewofag (0002) in ACTUAL and PLAN (OPC_001 - OPC_004)</li><li>credit AU, displayed directly on EU, in the PLAN (OPC_005 - OPC_008)</li></ul>

For this, for the plan items OPC_001 - OPC_004 he takes the actual values from the profit centre calculation and consolidates <ul id="ul0026" list-style="bullet" compact="compact"><li>the values of the 16 periods to the annual level,</li><li>the accounts to the allocated plan items and</li><li>each profit centre to the allocated profit centre group. If for one profit centre there does not exist a profit centre group of an economic unit, the function module consolidates to the top profit centre group 'Gewofag' (0002).</li></ul>

The actual values form the data base for estimating the plan values. We revise this data base: We only incorporate feature combinations - plan item, profit centre group, accounting area and currency key into the data base if they have actual values over the whole, maximum span for each plan item of the past window. For each of these combinations of features we calculate the inaccuracy as a maximum percentage deviation of the estimated values from the actual values. We now re-sort the data base according to these inaccuracies and calculate for the more accurate half the average trend and the maximum for the maximal deviations for each plan item. We then calculate for each plan item with a separate linear ansatz, but all (profit centre groups of the) economic units with the same trend. We understand trend here as being the percentage increase of the estimated value of the last actual year to the estimated value of the first plan year. According to the information given by the specialist field (Mr. Götz, Gewofag) it is senseless to apply a separate trend for each economic unit. For the estimate we apply the following rules:

• OUTGOING RULE:

If in the last actual year of the extracted time series no actual value has accrued for an economic unit for a plan item, we update the plan values 0 in the planning horizon.

• INCOMING RULE:

If an actual value accrues for an economic unit in the final actual year of the extracted time series, in the estimate we take into account the date of use for the first time (TA FOE3) of the allocated rental units (Tab VIMI01). With newly added EUs, in the following year one should count on operating costs at the level of the reciprocal value (13 - incoming period) / 12. If, for example, all of the rental units of an EU were newly added on 1.10., in the following year one should count on operating costs of four times the level.

• TREND DEVIATION RULE:

In order to keep structural interruptions, i.e. exceptional influences in the past, out of the estimate, we apply the trend deviation rule: Each set of data includes a plan item into which we calculated the average trend t and the maximum inaccuracy i covering the above accounting area and profit centre groups. For one set of data we calculate the plan values according to the method of the smallest squares on the additional condition that trend = t. If the maximum deviation exceeds i we recursively remove the oldest actual value from the data base until both conditions are met. This is the case at the latest if just one actual value is still present in the data base. In the plan we then also update for each profit centre group of the economic unit, but not for the top level Gewofag (0002), the plan items of the credit of the accounting units (OPC_005 - OPC_008), and with prefixes which are reversed in relation to the corresponding item of the debits EU (OPC_001 - OPC_004). On the top level Gewofag (0002) we implement a delta calculation (see below) for the plan values of items OPC_005 - OPC_008. We only display a summary of the actual values for plan items OPC_005 - OPC_012 on the top level Gewofag (0002): <ul id="ul0027" list-style="none" compact="compact"><li>In the second step the extractor considers the debiting and crediting of the accounting units (OPC_005 - OPC_012), and does not do so in detail on the EU level, but aggregated on the company level, and executes the following calculations: <ul id="ul0028" list-style="bullet"><li>credit AU in total shown over all profit centre groups on top level Gewofag (0002) in ACTUAL (OPC_005 - OPC_008)</li><li>debit AU in total shown over all profit centre groups on top level Gewofag (0002) in ACTUAL (OPC_009 - OPC_012)</li><li>credit AU directly on top level Gewofag (0002) PLAN (OPC_005 - OPC_008)</li><li>debit AU in total shown over all profit centre groups on top level on top level Gewofag (0002) PLAN (OPC_009 - OPC_012)</li></ul></li></ul>

For this, for item positions OPC_005 - OPC_012 he takes the actual values from the profit centre calculation and consolidates <ul id="ul0029" list-style="bullet" compact="compact"><li>the values of the 16 periods to the annual level,</li><li>the accounts to the allocated plan items and</li><li>each profit centre to the top profit centre group 'Gewofag' (0002).</li></ul>

On this data base we estimate for each plan item, covering the whole accounting area, the linear trend over all selected actual values (OPC_001 - OPC_012), and in so doing apply the following rules:

• COMPLETENESS RULE:

Incomplete annual values falsify the estimate. With items OPC_009 - OPC_012 the values for the current year may not be present in their entirety. We therefore blank out the current year for the estimate. Values for the remaining (accounting) items OPC_001 - OPC_008 are either complete or not available at all. The problem does not arise here.

• TREND-CAPPING RULE:

If the trend exceeds the constant c_maxtrend or falls short of the constant c_mintrend, we assume that at least the last (linearly estimated) plan value is set too high (c_maxtrend) or too low (c_mintrend). We therefore limit the trend. With the estimate on the EU level (OPC_001 - OPC_004) the problem does not arise due to the broader data base. Therefore, we do not apply the rule here.

• AVERAGE VALUE RULE:

We basically estimate the 'miscellaneous' item (OPC_012) with the average value, i.e. with trend specification 0 due to strong fluctuations. With the subsequent estimate on the company level with the trend specification and dependent upon the accounting area and the plan item we then apply the following rules:

• TREND-ADAPTATION RULE:

With the items <ul id="ul0030" list-style="dash" compact="compact"><li>'rates' (OPC_001, OPC_005, OPC_009)</li><li>'operating costs' (OPC_002, OPC_006, OPC_010)</li><li>'heating costs' (OPC_003, OPC_007, OPC_011)</li><li>'non-deductible input tax' (OPC_004, OPC_008)</li></ul> for each group respectively we use the most accurate trend. Within these four groups, on the advice from the specialist field we can apply respectively identical trends.

• TREND DEVIATION RULE (see above)

We estimated plan items OPC_005 - OPC_012 in total on the company level. It must now be taken into account that we have already updated plan items OPC_005 - OPC_012 on the EU level. Therefore, on the company level we apply the difference between the company total - EU total if the company total exceeds the EU total. Otherwise we update value 0 here.

1.1.1.2. PF download INC (income)

The planning function 'download INC (income)' initiates the function module Z_BPS_003_RFC_CONS in the source system. In order to transfer to BPS from the profit centre calculation, the function module selects the actual values of the past window, i.e. of the past five years including the planning year, limited to all of the INC accounts. We identify as an INC account all types of cost which are allocated to those plan items (TA ZBPS005) which are allocated to plan item type 'INC' (TA ZBPS004). The function module consolidates <ul id="ul0031" list-style="bullet" compact="compact"><li>the values of the 16 periods to the annual level,</li><li>the accounts to the allocated plan items and</li><li>each profit centre to the allocated profit centre group. If for one profit centre there does not exist a profit centre group of an economic unit, the function module consolidates to the top profit centre group 'Gewofag' (0002).</li></ul> By means of the actual values we calculate the vacancy quota as the quotient INC_004 (calc. income vacancy) / (INC_001 (desired rents) + INC_004). over all economic units and actual years of the past period. We apply this quota when calculating the plan values for the individual economic units. It is senseless to establish the vacancy quote for each economic unit due to irregular modernisation costs and missing operators. Therefore, we also dispense with a trend calculation. In order to calculate the plan values we differentiate according to the plan item. We calculate plan items <ul id="ul0032" list-style="bullet" compact="compact"><li>INC_001 (desired rents)</li><li>INC_003 (own use)</li></ul> for each rental unit and from this deduce the values for the following plan items: <ul id="ul0033" list-style="bullet" compact="compact"><li>INC_004 (calc. income vacancy) proportional to the vacancy quota</li><li>INC_006 (calc. expenditure vacancy) with reversed prefix in relation to INC_004</li><li>INC_007 (occupancy costs rent own use) with reversed prefix in relation to INC-_003.</li></ul> In order to distinguish between INC_001 (desired rents) and INC_003 (own use) we differentiate for each rental unit according to the occupancy type. If occupancy type I0129 (corporate use with RA) or I0130 (own use) is allocated to the rental unit, we add its plan income to plan item INC_003 (own use) or else to plan item INC_001 (desired rents). We calculate the plan income dependently upon the type of use which is clearly allocated to the rental unit. An increase, a capping and an exceedance rule is respectively precisely allocated to each type of use (TA ZBPS030). With these rules we calculate the plan income for the planning horizon and aggregate the rental units to their economic units. The calculated plan values are still unrealistic because they are based upon full rental. Therefore, we apply the above vacancy quota calculated from the actual to each economic unit to plan item INC_001 (desired rents) in order to calculate plan item INC_004 (calc. income vacancy) and deduct this value from INC_001 (desired rents) again. We finally update INC_006 (calc. expenditure vacancy) and INC_007 (occupancy costs rent own use) with a reversed prefix in relation to INC_004 (calc. income vacancy) and INC_006 (calc. expenditure vacancy). Whereas we only calculate the plan values for plan items <ul id="ul0034" list-style="bullet" compact="compact"><li>INC_008 (rates):</li><li>INC_009 (operating costs)</li><li>INC_010 (heating costs)</li><li>INC_011 (non-deductible input tax.) in the BPS (from plan items OPC_001 to OPC_004), the extractor establishes the remaining plan items</li><li>INC_002 (turnover rent/other income)</li><li>INC_005 (balance figure/income curtailment)</li><li>INC_012 (allocation deficit risk)</li><li>INC_013 (rent/expenditure allowance) according to the outgoing rule and the trend capping rule in the source system. Outgoing rule:</li></ul>

If in the last actual year no actual value has accrued for an economic unit for a plan item, we update the plan value 0 for this item for each plan year. Due to entries which are still expected in the current year, we consider the minimum as the last actual year {current year-1; last selected actual year}.

Trend capping rule:

At all times an economic unit is precisely allocated to an accounting area, but can however also change this during the year. Therefore, we calculate the regression parameters linearly to cover the accounting area for each economic unit and plan item. In so doing we specify that the trend must not exceed the percentage c_maxpercent or fall short of the percentage c_minpercent.

The extractor calculates items INC_002 (turnover rent/other inc), INC_005 (balance figure/inc curtailment) and INC_012 (allocation deficit risk) with the capping constants c_maxtrend = 5%, c_mintrend = -2%.

The extractor calculates item INC_013 (rent/expenditure allowance) with the capping constants c_maxtrend_inc13 = -0.5%, c_mintrend_inc13 = -3%.

The Trend is defined as the percentage increase from the estimated value of the last actual year to the estimated value of the first subsequent year.

As the first actual year of the data base we choose Max {2001; start of the past period} due to completing entries in 2000. Due to entries still expected in the current year we consider as the last actual year Min {current year-1; last selected actual year}.

With the regression parameters calculated for each economic unit and plan item we establish the plan value for each year of the planning horizon and update this value on the accounting area currently allocated to the EU.

1.1.1.3. PF download PRM (property management)

The planning function 'download PRM (property management)' initiates the function module Z_BPS_013_RFC_CONS in the source system. In order to transfer to BPS from the profit centre calculation, the function module selects the actual values of the past window, i.e. of the past five years including the planning year, limited to all of the PRM accounts. We identify as a PRM account all types of cost which are allocated to those plan items (TA ZBPS005) which are allocated to plan item type 'PRM' (TA ZBPS004). The function module consolidates <ul id="ul0035" list-style="bullet" compact="compact"><li>the values of the 16 periods to the annual level,</li><li>the accounts to the allocated plan items and</li><li>each profit centre to the allocated EU profit centre group. If for one profit centre there does not exist a profit centre group of an economic unit, the function module consolidates to the top profit centre group 'Gewofag' (0002).</li></ul> The FM calculates the plan values according to the trend capping specification rule. Trend capping specification rule: <ul id="ul0036" list-style="none" compact="compact"><li>We calculate the trend linearly for each plan item to cover the accounting area and totalling over all profit centre groups. In so doing we specify that the trend must not exceed the percentage c_maxpercent and must not fall short of the percentage c_minpercent with</li><li>c_maxtrend = 3% and c_mintrend = -3%.</li><li>The Trend is defined as the percentage increase from the estimated value for the last actual year to the estimated value of the first subsequent year.</li><li>As the first actual year of the data base we choose Max {2000; 1^st plan year - 5} due to blurs in 1999. Due to entries which are still expected in the current year we consider as the last actual year Min {current year-1; last selected actual year = 1^st plan year - 1}.</li></ul>

With the trend calculated for each plan item we establish the regression parameters for each economic unit such that they correspond to this trend, and from these parameters the plan value for each year of the planning horizon in order to update it on the accounting area currently allocated to the EU.

1.1.1.4. PF download MAI (maintenance, modernisation, renovation)

The planning function 'download MAI (maintenance/mod/ren)' initiates the function module Z_BPS_006_RFC_CONS in the source system. For the transfer to BPS from the profit centre calculation, the function module selects the actual values of the past window, i.e. of the past five years including the planning year, limited to all of the MAI accounts. We identify as a MAI account all types of cost which are allocated to those plan items (TA ZBPS005) which are allocated to plan item type 'MAI' (maintenance/renovation/modernisation expenditure) (TA ZBPS004). The function module consolidates <ul id="ul0037" list-style="bullet" compact="compact"><li>the values of the 16 periods to the annual level,</li><li>the accounts to the allocated plan items and</li><li>each profit centre to the allocated EU profit centre group. If for one profit centre there does not exist a profit centre group of an economic unit, the function module consolidates to the top profit centre group 'Gewofag' (0002).</li></ul> The FM calculates the Plan values for item MAI_001 (maintenance) according to the average value rule. We only update the average value for each economic unit on the active accounting area of the economic unit. On the remaining accounting areas we update the planning value 0. On the company level we update the plan values in the accounting area 0010. There is no active accounting area for this. Average value rule: <ul id="ul0038" list-style="none" compact="compact"><li>We calculate the average value of the actual values in the period h_begyear; h_endyear] := [Max{2000, i_pyear-5}; Min{current.previous year, i_pyear-1}] for each plan item ('MAI_001') and economic unit, covering the accounting area. We do not use the current year because the actual values may not yet be complete. The average value would then be calculated too low.</li></ul>

The FM takes the plan values for item MAI_002 (renovation/modernisation) from the annual budget values of the project system. Costs for modernisation and renovation under cost type '805042' statistically arise in projects, namely <ul id="ul0039" list-style="bullet" compact="compact"><li>costs for modernisation in projects which begin with the code MO,</li><li>costs for renovation with projects which begin with the code RE.</li></ul>

The four figures following the two-figure prefix generally define the economic unit to which the actual and plan values should additionally be added in the SEM-BPS (which is an abbreviation of strategic enterprise management-business planning and simulation): <ul id="ul0040" list-style="none" compact="compact"><li>E.g.: MO02040001 defines EU 204.</li></ul>

As an exception to this rule, a project can also relate to several economic units: <ul id="ul0041" list-style="none" compact="compact"><li>E.g.: MOAOT40002.</li></ul>

In this case the accounting rule for the true accounting object would have to be considered for the correct allocation to the economic units in question. Instead of this, we assign the values in SEM-BPS to the profit centre group '0002'. We take the annual budget values as the approved plan values in SEM-BPS. (According to Mr. Kaiser, the total values of the budget are fully distributed over the year slices.) In contrast, a prognosis calculation does not take place for maintenance because the actual values are only produced at irregular intervals. Instead, the plan values are to be entered manually in SEM-BPS.

Remarks: <ol id="ol0001" compact="compact" ol-style=""><li>1. The accruals for building maintenance were inadvertently entered in the years 2000 - 2002 in account 805040 in periods 13-16. In 1999 they were inadvertently entered in account 805040 in period 12. One can no longer not divide these up here. For the years 2000 - 2002 however, we direct the values for the four particular periods 13 - 16 to plan item MAI_009 (ref: particular period maintenance 805040).</li><li>2. The two features relevant for the consolidation - partner's company ID and movement type are initially updated in the plan.</li></ol>

1.1.1.5. PF download ADC (administration costs for EU)

The planning function 'download ADC (administration costs for EU)' initiates the function module Z_BPS_009_RFC_CONS in the source system. In order to transfer to BPS from the profit centre calculation, the function module selects the actual values of the past window, i.e. of the past five years including the planning year, limited to all of the MAI accounts. We identify as a MAI account all types of cost which are allocated to those plan items (TA ZBPS005) which are allocated to the 'ADC' (administration) plan item type (TA ZBPS004). The function module consolidates <ul id="ul0042" list-style="bullet" compact="compact"><li>the values of the 16 periods to the annual level,</li><li>the accounts to the allocated plan items, and</li><li>each profit centre to the allocated EU profit centre group. If for one profit centre there does not exist a profit centre group of an economic unit, the function module consolidates to the top profit centre group 'Gewofag' (0002).</li></ul>

The FM calculates the plan values according to the trend capping rule. We only update the trend value for each economic unit on the active accounting area for the economic unit. On the company level we update the plan values in accounting area 0010.

Trend capping rule: <ul id="ul0043" list-style="none" compact="compact"><li>We calculate the trend in total over all of the economic units for each plan item and in the next step break it down into the individual economic unit. We do not include any values before the year 200 in the trend calculation, and no values for the current year. We limit the trend to the interval [c_mintrend; c_maxtrend].</li></ul>

1.1.1.6. PF OPC->INC (operating costs -> income)

The planning function 'OPC -&gt; INC (operating costs -&gt; income)' initiates the transfer of plan values of the operating costs into the income calculation in the BPS. <ul id="ul0044" list-style="bullet" compact="compact"><li>rates/operating costs <maths id="math0015" num=""><math display="block"><mi>INC_</mi><mn mathvariant="normal">008</mn><mfenced><mi>operating costs</mi></mfenced><mo mathvariant="normal">=</mo><mo mathvariant="normal">-</mo><mfenced separators=""><mi>OPC_</mi><mn mathvariant="normal">001</mn><mfenced><mi>EU rates</mi></mfenced><mo mathvariant="normal">+</mo><mi>OOC_</mi><mn mathvariant="normal">002</mn><mfenced><mi>EU operating cost</mi></mfenced></mfenced><mn mathvariant="normal">.</mn></math><img file="EP1988499A1_D0015.tif" /></maths></li><li>heating costs <maths id="math0016" num=""><math display="block"><mi>INC_</mi><mn>010</mn><mfenced><mi>heating costs</mi></mfenced><mo>=</mo><mo>-</mo><mfenced separators=""><mi>OPC_</mi><mn>003</mn><mfenced><mi>EU heating costs</mi></mfenced></mfenced><mn>.</mn></math><img file="EP1988499A1_D0016.tif" /></maths></li><li>non-deductible input tax <maths id="math0017" num=""><math display="block"><mi>INC_</mi><mn>011</mn><mo>⁢</mo><mfenced separators=""><mi>non</mi><mo>-</mo><mi>deductible input tax</mi><mn>.</mn></mfenced><mo>=</mo><mi>OPC_</mi><mn>008</mn><mo>⁢</mo><mfenced separators=""><mi>credit</mi><mo>-</mo><mi>non</mi><mo>-</mo><mi>deduct</mi><mn>.</mn><mspace width="1em" /><mi>input tax</mi><mn>.</mn></mfenced></math><img file="EP1988499A1_D0017.tif" /></maths></li></ul>

1.1.2. TA capping rules (ZBPS010)

Transaction ZBPS010 makes it possible to define capping rules (TAB ZBPS024). Function module Z_BPS_003_RFC uses the capping rules for capping increases in the basic rent when calculating the plan income. Function module Z_BPS_003_RFC is initiated with the planning function download INC (income) in the source system. In order to change the capping rules, see. TA ZBPS030, where TA stands for transaction. field index descriptive notes: <tables id="tabl0001" num="0001"><table frame="none"><tgroup cols="2"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="89mm" /><tbody><row><entry colsep="0" rowsep="0">1</entry><entry colsep="0" rowsep="0">Table ZBPS010: capping with EUR/m² to m²</entry></row><row><entry colsep="0" rowsep="0">2</entry><entry colsep="0" rowsep="0">Table ZBPS027: capping with EUR/m² set for each type of use</entry></row></tbody></tgroup></table></tables>

1.1.3. TA capping with EUR/m

2

to m

2

(ZBPS011)

Transaction ZBPS011 makes it possible to parametrise the capping rule 'capping with EUR/m² to m²' specified in TA ZBPS010 with Index 1 (TAB ZBPS010). For each rental unit, generally just one area type is dealt with - the living area or the useful area. Function module Z_BPS_003_RFC multiplies the living area, and if it is initial, the useful area with the allocated condition value to the maximum basic rent. The area field has the unit m² and describes the top limit up to which the allocated condition value should apply.

The condition value field describes the maximum for the monthly basic rent (condition type 10) per m². <tables id="tabl0002" num="0002"><table frame="none"><tgroup cols="2" colsep="0" rowsep="0"><colspec colnum="1" colname="col1" colwidth="26mm" /><colspec colnum="2" colname="col2" colwidth="27mm" /><thead><row><entry valign="top">area</entry><entry valign="top">condition value</entry></row></thead><tbody><row><entry>50,0000</entry><entry>6.75</entry></row><row><entry>100,0000</entry><entry>6.25</entry></row><row><entry>9,999,999,999</entry><entry>6.00</entry></row></tbody></tgroup></table></tables>

1.1.4. TA capping with EUR/m

2

for each type of use (ZBPS012)

Transaction ZBPS012 makes it possible to parametrise the capping rule 'capping with EUR/m² set for each type of use' specified in TA ZBPS010 with Index 2 (TAB ZBPS027).

For each rental unit generally only one area type is dealt with - the living area or the useful area. Moreover, one type of use is allocated to each rental unit. Function module Z_BPS_003_RFC multiplies the living area, and if it is initial, the useful area with the allocated condition value for the maximum basic rent. The condition value field describes the maximum for the monthly basic rent (condition type 10) per m². <tables id="tabl0003" num="0003"><table frame="none"><tgroup cols="2" colsep="0" rowsep="0"><colspec colnum="1" colname="col1" colwidth="20mm" /><colspec colnum="2" colname="col2" colwidth="27mm" /><thead><row><entry valign="top">type of use</entry><entry valign="top">condition value</entry></row></thead><tbody><row><entry>5</entry><entry>9.50</entry></row><row><entry>6</entry><entry>9.50</entry></row><row><entry>7</entry><entry>9.50</entry></row><row><entry>8</entry><entry>9.50</entry></row><row><entry>9</entry><entry>9.50</entry></row><row><entry>10</entry><entry>9.50</entry></row><row><entry>11</entry><entry>9.50</entry></row><row><entry>12</entry><entry>9.50</entry></row></tbody></tgroup></table></tables>

1.1.5. TA rent increase rules (ZBPS020)

Transaction ZBPS020 makes it possible to define rent increase rules (TAB ZBPS024). Function module Z_BPS_003_RFC uses the rules to calculate the increases in the basic rent in the plan. Function module Z_BPS_003_RFC is initiated with the planning function download INC (income) in the source system. With regard to the significance of the three rent increase rules defined here, see TA ZBPS030. field index descriptive notes: <tables id="tabl0004" num="0004"><table frame="none"><tgroup cols="2"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="117mm" /><tbody><row><entry colsep="0" rowsep="0">1</entry><entry colsep="0" rowsep="0">increase every 18 months following the last rent change by 7.5% to the basic value.</entry></row><row><entry colsep="0" rowsep="0">2</entry><entry colsep="0" rowsep="0">Table ZBPS011: rent increase in month x by y percent.</entry></row><row><entry colsep="0" rowsep="0">3</entry><entry colsep="0" rowsep="0">constant updating of the total of the condition items</entry></row></tbody></tgroup></table></tables>

1.1.6. TA rent increase in month x by y percent (ZBPS021)

Transaction ZBPS021 makes it possible to parametrise the rent increase rule 'rent increase in month x by y percent' specified in TA ZBPS020 with Index 2 (TAB ZBPS011). <tables id="tabl0005" num="0005"><table frame="none"><tgroup cols="4" colsep="0" rowsep="0"><colspec colnum="1" colname="col1" colwidth="24mm" /><colspec colnum="2" colname="col2" colwidth="12mm" /><colspec colnum="3" colname="col3" colwidth="14mm" /><colspec colnum="4" colname="col4" colwidth="16mm" /><thead><row><entry valign="top">economic unit</entry><entry valign="top">fin. yr</entry><entry valign="top">period</entry><entry valign="top">percent</entry></row></thead><tbody><row>&lt;entry /&gt;<entry>2004</entry><entry>3</entry><entry>5</entry></row><row>&lt;entry /&gt;<entry>2004</entry><entry>11</entry><entry>8</entry></row></tbody></tgroup></table></tables>

1.1.7. TA rent increase and capping rules/NA (ZBPS030)

Transaction ZBPS030 makes it possible to allocate a rent increase, a capping rule and the exceedance criterion to the type of use of a rental unit (TAB ZBPS026). Function module Z_BPS_003_RFC is initiated with the planning function download INC (income) in the source system. It establishes for each rental unit its annual plan income by applying the rent increase and capping and exceedance rules defined in Table ZBPS026 dependently upon its type of use.

1.1.7.1. Rule for increasing rent every 18 months

For certain rental objects, the basic rent should be increased every 18 months by a maximum of 7.5%. In the plan the extractor calculates from the month of the last actual increase an increase of the last applicable basic rent in the past period (condition type 10) every 18 months, and with immediate effect if the last actual increase was a longer period of time ago.

The extractor constantly updates the other rental portions (condition type &lt;&gt; 10). For the case where a capping rule is active, he calculates from this the maximum basic rent and caps the increases in the basic rent upon reaching the maximum basic rent, unless the exceedance criterion is set. In this case he constantly incorporates the actual for the monthly basic rent for the whole planning horizon into the plan in so far as the actual value already exceeds the maximum basic rent.

1.1.7.2. Rule of percentage increase

The extractor calculates an increase in the basic rent (condition type 10) as from a specific month and by a specific percentage. The month and percentage can, but do not have to be, specified for each economic unit. The function module first of all searches in the customising table (TA ZBPS021) for an entry for the economic unit of the current rental unit, and then for an entry with the initial economic unit. The further calculation is implemented as described under '18 months rental increase rule' in the second paragraph.

1.1.7.3. Rule of constant updating

The extractor constantly updates the rent in all condition types. The allocation of a capping rule and the setting of the exceedance criterion do not have any effect. In order to define the rental increase rules, see TA ZBPS010. In order to define the capping rules, see TA ZBPS020. <tables id="tabl0006" num="0006"><table frame="none"><tgroup cols="4" colsep="0" rowsep="0"><colspec colnum="1" colname="col1" colwidth="20mm" /><colspec colnum="2" colname="col2" colwidth="17mm" /><colspec colnum="3" colname="col3" colwidth="17mm" /><colspec colnum="4" colname="col4" colwidth="23mm" /><thead><row><entry valign="top">type of use</entry><entry valign="top">increase</entry><entry valign="top">capping</entry><entry valign="top">exceedance</entry></row></thead><tbody><row><entry>1</entry><entry>1</entry><entry>1</entry><entry>X</entry></row><row><entry>2</entry><entry>2</entry>&lt;entry /&gt;<entry>X</entry></row><row><entry>3</entry><entry>2</entry>&lt;entry /&gt;<entry>X</entry></row><row><entry>4</entry><entry>1</entry><entry>1</entry><entry>X</entry></row><row><entry>5</entry><entry>1</entry><entry>2</entry><entry>X</entry></row><row><entry>6</entry><entry>1</entry><entry>2</entry><entry>X</entry></row><row><entry>7</entry><entry>1</entry><entry>2</entry><entry>X</entry></row><row><entry>8</entry><entry>1</entry><entry>2</entry><entry>X</entry></row><row><entry>9</entry><entry>1</entry><entry>2</entry><entry>X</entry></row><row><entry>10</entry><entry>1</entry><entry>2</entry><entry>X</entry></row><row><entry>11</entry><entry>1</entry><entry>2</entry><entry>X</entry></row><row><entry>12</entry><entry>1</entry><entry>2</entry><entry>X</entry></row></tbody></tgroup></table></tables>

Moreover, the current portfolio can be provided using area in m² and number of units or subunits.

Some or all the data extracted can be subject of a quality inspection. As an example, the quality inspection can be a manual inspection by a user, verifying the data in the GUI. In particular, said quality inspection can be a plausibility inspection. In specific, particularly exceptional cases, manual adaptation of the data can be carried out. Particularly, manual adaptation and/or correction of the data is possible for such data, which cannot be recognized using automated statistical approaches. Such data can be changed in strategic direction of the assessment/evaluation of planned change(s) in basic data which was not yet introduced into the data and/or the automatic method. Examples of the before mentioned can comprise planned activities, such as constructional activities for the business unit and for subunits of the business unit, which have not yet been introduced or which cannot be introduced in the basic data.

Using the planned position, i.e. the future plan data, a second quality inspection can be provided. Therefore, living/housing-economic numbers are calculated. Said quality inspection provides a fast overview of a starting point for the DCF-calculation (i.e. discounted cash flow-calculation) of every individual real estate object as specific embodiments of business units or business subunits. However, extreme outliners cannot be changed at that stage. Using said calculated data, as living-economic key-data, real estate objects can be compared with each other. An example hereof is shown in <figref idref="f0007"><b>figure 7</b></figref>.

Referring to <figref idref="f0002">Figure 2</figref>, all planned data, which can include one or more of the future plan data, the past data and the estimated values, calculated from future plan data and the past data, are taken from an annual level of the real estate object planning into the monthly statistic cube. This can be obtained by buttons 94 as shown in <figref idref="f0008"><b>figure 8</b>. Figure 8</figref> is identical to <figref idref="f0002">Figure 2</figref>, wherein buttons 94 are shown in a magnified view. Hereby, a cube may be a data container, containing e.g. monthly statistic data.

The planned data on a monthly level are, according to a specific distribution, distributed on monthly basis (referred to as "reference distribution/equal distribution"). When using the reference distribution, a reference business year can be chosen. The real values of said reference business year can be used as basis for the distribution. The real values can be referred to as "current values". Particularly, real values can be the past data for the last year. Possible manual changes and/or corrections in the monthly planning can be made for the individual real estate objects. The button-up approach is applied. In other words, the data can be very granular and be further processed from said very granular form to finally provide the at least one estimate value. Particularly, in the SAP BW system, no extraction is carried out. Rather, only in the QS system, extraction is carried out. On the other hand, in the BW system, determination of the at least one estimate value is carried out and in the QS system no determination may be carried out.

<figref idref="f0009"><b>Figure 9</b></figref> shows a schematic overview of the reference distribution. Following that, monthly statistics can be calculated. Particularly, older risk values can be calculated per planned position, real estate object, property management units, and the business. The calculation can be made on a daily basis using updated current values.

Subsequently, the current values of the first planning year are updated. Hereby, older current values per month are taken from planning cube.

A planning version can be copied in a new version, which can be used for simulation periodical reports, etc. For further details on the simulation, reference is made to the above description.

<figref idref="f0010"><b>Figure 10</b></figref> is similar to <figref idref="f0002">figure 2</figref>. In particular, <figref idref="f0010">figure 10</figref> comprises two magnified sections of <figref idref="f0002">figure 2</figref>. In <figref idref="f0010">figure 10</figref>, the planning year (referred to as reference numeral 96) is the year 2006. Consequently, the business year is 2007. Moreover, the current interval is chosen as 1 (referred to as reference numeral 98). The current interval 98 defines the time period for the past data and time period for the future plan data. Said values, i.e., the past data and the future plan data, represent the respective applicable annual values for a current/present period/year of business. As another example, the current interval could be chosen to 4. Therefore, the past data would be provided for 3 intervals in the past, namely, interval 1, interval 2, and interval 3. In other words, the past interval comprises intervals 1 to 3. The future plan data, according to said example, then correspond to intervals 4 to 12. In other words, the future interval comprises time intervals 5 to 12 with the time interval number 4 being the present interval. However, for the present interval (also referred to as "current interval") future plan data is extracted as well as for the future interval. Only for the past interval, past data is extracted.

Moreover, a discount rate can be chosen at reference numeral 100. As an example, said due date is used to determine the respective discount rates.

Another magnified view of a section of the display according to <figref idref="f0002">figure 2</figref> is shown in <figref idref="f0010">figure 10</figref>. The following steps can be carried out: <ol id="ol0002" ol-style=""><li>1. After determining selection criteria (as exemplary described with reference to <figref idref="f0010">figure 10</figref>) for a novel calculation the method according to the application is applied for all real estate objects (also referred to as "profit centre groups").</li><li>2. Thereby, for the planning positions (referred to as "Revenues-Administration"; German language: "Erlöse-Verwaltung") a cash flow in view of risk points are determined and discounted with the chosen discount rates.</li><li>3. The discounted cash flow was calculated/determined for all real estate objects. Hence, the discounted cash flow can be evaluated for all real estate objects as well.</li></ol>

Steps 1 to 3 can be carried out by selecting and/or activating one or more buttons as shown in a magnified section of the GUI (referred to as reference "A").

Moreover, for a manual interference, the cash flow for an individual real estate object can be changed/corrected in field 104, which is referred to as the field "correction" (German language: "Korrektur"). The cash flow can be corrected for every planned year. For an individual calculation/determination of the discounted cash flow (as the preferred estimate value) in the selection image according to <figref idref="f0010">Figure 10</figref>, it is possible to navigate over the last row/line. The above described method steps are related to "B" in <figref idref="f0010">Figure 10</figref>.

<figref idref="f0011"><b>Figure 11</b></figref> shows a screen shot of an analysis of limit factors/limit factors.

<figref idref="f0012"><b>Figure 12</b></figref> shows a ranking list according to the discounted cash flow values of business units, wherein individual business units are shown in lines 16 to 22 (line-numbers are indicated in the left column of the screen shit according to <figref idref="f0010">figure 10</figref>). Moreover, subunits of the business units, which can be real estate objects, are shown in lines 23 to 39. Further subunits can follow, but are not shown in the screen shot. Moreover, for each business unit and/or subunit discounted cash flow-values are shown according to the constant approach (column 106), the linear approach (column 108), and the non-linear approach (column 110). Following that, an easy overview can be obtained, which business unit and/or subunit has a specific discounted cash flow value according to the different approaches. Moreover, a very easy variation and/or comparison between the different business units and/or subunits is possible.

<figref idref="f0013"><b>Figure 13</b></figref> shows two screen shots of graphical user interfaces, wherein a possible variation is shown in screen shot 112. In particular, booking periods 1 to 12 shown in column 114 of screen shot 112. These booking periods can correspond to years particularly in the future of the present year. There are shown the discounted cash flow values in column 116 (as preferred estimate values). In column 118 and 120 estimate values are shown. In columns 122, 124 values representing the 95 % confidence interval are shown. In column 126 the gained values are shown, and in column 128 the current real values are shown. In other words, the present period is period 5, and the values of 128 referring to periods 1 to 4 are past data.

Reference numeral 130 represents a graphical user interface similar to that of <figref idref="f0004">figure 4</figref>.

Summarizing, as can be seen e.g. from <figref idref="f0005">Figure 5</figref> and <figref idref="f0006">6</figref>, which show that large number of data is provided for a business unit, said large number of data can be used and an estimate value can be determined, as shown in <figref idref="f0012">figure 12</figref>. The estimate values (constant discounted cash flow-value, linear discounted cash flow-value, and non-linear discounted cash flow-value) can be easily compared with a number of business units, such as real estate objects and sub-objects, etc. Such an easy comparison is not possible from the data, e.g. shown in <figref idref="f0005">figure 5</figref> and <figref idref="f0006">figure 6</figref>. Moreover, as shown in screenshot/GUI 130 of <figref idref="f0013">figure 13</figref>, estimate values can be easily visualized as graphs. Reference is also made to <figref idref="f0004">figure 4</figref>. In graphs 84, 86, and 88, there are shown discounted cash flow values according to the constant approach, the linear approach, and the non-linear approach.

Moreover, the above description is a mere example only. A combination of one or more individual features and/or method steps of the individual embodiments and/or variants is possible. Therefore, it is possible to provide further embodiments and/or variance of computer systems and/or methods, which are not described above.

<figref idref="f0014"><b>Figure 14</b></figref> comprises a schematic overview of components of and/or data used by one or more embodiments of the computerized method.

<figref idref="f0015 f0016 f0017 f0018 f0019 f0020 f0021 f0022 f0023"><b>Figures 15 to 23</b></figref> comprise an exemplary display of data used for and/or by and/or created by one or more embodiments of the computerized method.

<figref idref="f0024 f0025 f0026"><b>Figures 24 to 26</b></figref> comprise an exemplary display of an evaluation carried out and/or displayed and/or possible by one or more embodiments of the computerized method.

<figref idref="f0027 f0028 f0029"><b>Figures 27 to 29</b></figref> each comprises a schematic overview of components of and/or data used by one or more embodiments of the computerized method.

Exemplary, an embodiment of the method can be summarized as follows: <ul id="ul0045" list-style="none" compact="compact"><li>A statistical DCF approach for asset valuation can be realized within SAP Business Information Warehouse (SAP BW). 'Relevant business information from productive SAP applications and all external data sources can be integrated, transformed, and consolidated in SAP BW with the toolset provided.' Within SAP BW system the BW-BPS (business planning and simulation) application provides a framework to develop customer specific planning application like our DCF application.</li></ul>

Calculation

The calculation of the DCF is done in two steps. First data are extracted from the source system. Then statistics are performed on the extracted data.

Database

From the profit and loss account (P&amp;L) of the SAP enterprise resource planning system (source system) actual values for 5 years in the past and plan values for 6 years in the future are extracted on an annual basis into the SAP BW system. Planning is mainly performed on two characteristics, on planning positions and on profit center groups: <ul id="ul0046" list-style="bullet"><li>A plan position describes a set of accounts, which for planning purposes can be logically grouped together. For example several accounts of ordinary depreciation form one plan position, while accounts of rental revenues form another one.</li><li>A profit center group forms a set of profit centers. In profit center accounting a profit center 'reflects a management-oriented structure of the organization for the purpose of internal control'. In our application profit center groups represent a business entity. A business entity groups coherent real estate objects.</li></ul>

Within the DCF application five categories of plan positions define which values add up to the cash flow. Category 'Revenues' identifies the incoming payments. The categories 'Operating costs', 'Maintenance', 'Building operation' and 'Building administration' terms the payouts. The sum of incoming payments and payouts constitute the cash flow.

Mathematics

The mathematics of regression analysis on which we base our DCF approach can be found in <ul id="ul0047" list-style="bullet" compact="compact"><li><nplcit id="ncit0001" npl-type="b"><text>Sen and M. Srivastava, Regression analysis: Theory, methods and applications. Springer, New York, 1990</text></nplcit>)</li><li><nplcit id="ncit0002" npl-type="b"><text> G.A.F. Seber, C.J. Wild, Nonlinear Regression. Wiley, New York, 1989</text></nplcit>, which disclosure is explicitly incorporated by reference. In particular, the specific following mathematical terms can have a meaning, as conventionally assumed and applied in the field of statistics, statistical methods, statistical mathematics, etc.</li></ul>

To discount the cash flows, market traded annual interest rates <i>i_t</i> are taken into account for all available periods, i.e. typically for a range of fifty years. The years beyond are calculated with the last available interest rate.

To approximate the discounted cash flow <i>DCF</i> of a a business unit, we perform regression analysis on its past and/or future time indexed periodical cash flows <maths id="math0018" num=""><math display="block"><msub><mi>y</mi><mi>t</mi></msub><mo>;</mo><mi>t</mi><mo>=</mo><mn>1</mn><mo>,</mo><mn>..</mn><mi>n</mi></math><img file="EP1988499A1_D0018.tif" /></maths> using three different models: <maths id="math0019" num=""><math display="block"><msub><mi mathvariant="italic">DCF</mi><mi>c</mi></msub><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>t</mi><mo>=</mo><mn>1</mn></mrow><mi>∞</mi></munderover></mstyle><mfrac><mrow><msub><mi>f</mi><mi>c</mi></msub><mo>⁢</mo><mfenced separators=""><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mfenced></mrow><msup><mfenced separators=""><mn>1</mn><mo>+</mo><msub><mi>i</mi><mrow><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mrow></msub></mfenced><mi>t</mi></msup></mfrac><mo>;</mo><msub><mi>f</mi><mi>c</mi></msub><mfenced><mi>t</mi></mfenced><mo>:</mo><mo>=</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>0</mn></msub><mspace width="1em" /><mfenced><mi>constant model</mi></mfenced></math><img file="EP1988499A1_D0019.tif" /></maths><maths id="math0020" num=""><math display="block"><msub><mi mathvariant="italic">DCF</mi><mi>l</mi></msub><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>t</mi><mo>=</mo><mn>1</mn></mrow><mi>∞</mi></munderover></mstyle><mfrac><mrow><msub><mi>f</mi><mi>l</mi></msub><mo>⁢</mo><mfenced separators=""><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mfenced></mrow><msup><mfenced separators=""><mn>1</mn><mo>+</mo><msub><mi>i</mi><mrow><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mrow></msub></mfenced><mi>t</mi></msup></mfrac><mo>;</mo><msub><mi>f</mi><mi>l</mi></msub><mfenced><mi>t</mi></mfenced><mo>:</mo><mo>=</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>0</mn></msub><mo>+</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>1</mn></msub><mo>⁢</mo><mi>t</mi><mspace width="1em" /><mfenced><mi>linear model</mi></mfenced></math><img file="EP1988499A1_D0020.tif" /></maths><maths id="math0021" num=""><math display="block"><msub><mi mathvariant="italic">DCF</mi><mi>n</mi></msub><mo>=</mo><mstyle displaystyle="true"><munderover><mo>∑</mo><mrow><mi>t</mi><mo>=</mo><mn>1</mn></mrow><mi>∞</mi></munderover></mstyle><mfrac><mrow><msub><mi>f</mi><mi>n</mi></msub><mo>⁢</mo><mfenced separators=""><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mfenced></mrow><msup><mfenced separators=""><mn>1</mn><mo>+</mo><msub><mi>i</mi><mrow><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mi>t</mi></mrow></msub></mfenced><mi>t</mi></msup></mfrac><mo>;</mo><msub><mi>f</mi><mi>n</mi></msub><mfenced><mi>t</mi></mfenced><mo>:</mo><mo>=</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>0</mn></msub><mo>+</mo><msub><mover><mi>β</mi><mo>^</mo></mover><mn>1</mn></msub><mo>⁢</mo><msup><mi>t</mi><mrow><mover><mi>β</mi><mo>^</mo></mover><mo>⁢</mo><mn>2</mn></mrow></msup><mspace width="1em" /><mfenced><mi>nonlinear model</mi></mfenced><mn>.</mn></math><img file="EP1988499A1_D0021.tif" /></maths>

Therein <ul id="ul0048" list-style="none" compact="compact"><li><i>i_t</i> represents a market traded interest at time index <i>t</i> and</li><li><i>t</i>₀; 0 ≤ <i>t</i>₀ ≤ <i>n</i> represents the index of the last actual data; i.e. <i>t</i>₀ + 1 represents the index of the first plan data. Typically, one would prefer to restrict the estimation of the parameters <i>β̂</i>₀, <i>β̂</i>₁, and <i>β̂</i>₂ to a sample of past or actual data, i.e. choose <i>t</i>₀ :=<i>n</i>. To stabilize the estimation, if only small samples of actual data are available, however future or plan data can be incorporated into the data base. We allow this in our application, since all important future values are planned on the most granular level of the objects of the source system application. For example rental revenues are planned on the basis of the individual conditions of each rental contract.</li></ul>

To calculate the parameters <i>β̂</i>₀, <i>β̂</i>₁ and <i>β̂</i>₂ we assume, as within the classical regression approach, a normal distribution with expectation 0 and variance <i>σ</i>² for all random error variables <i>ε_t; t=</i>1,..<i>n</i>, i.e. <i>ε_t ~</i>N(0<i>;</i> σ²); <i>t</i> = 1<i>,..n.</i>

Now in <ul id="ul0049" list-style="bullet"><li>the constant model <i>β̂</i>₀ is calculated as the statistical estimator for parameter <i>β</i>₀ in the constant, time independent model <i>y_t = β₀</i> + <i>ε_t</i> ; <i>t</i> = 1,..<i>.n.</i></li><li>the linear model <i>β̂</i>₀ and <i>β̂</i>₁ are calculated as the statistical estimators for parameters <i>β</i>₀ and <i>β</i>₁, respectively, in the linear, time dependent model <i>y_t = β</i>₀<i>+ β</i>₁<i>t + ε_t ; t</i>=1,...<i>n.</i></li><li>the nonlinear model <i>β̂</i>₀, <i>β̂</i>₁ and <i>β̂</i>₂ are calculated as the statistical estimators for parameters <i>β</i>₀, <i>β</i>₁ and <i>β</i>₂, respectively, in the nonlinear time dependent model <i>y_t = β</i>₀ + <i>β</i>₁<i>t</i>^{<i>β</i><sub2>2</sub2>} + <i>ε_t ; t</i> = 1,...<i>n</i>.</li></ul>

<i>f_c</i>(<i>t</i>), <i>f_l(t)</i> and <i>f_n(t)</i> are special occurences of function class <i>f</i>(B,t), where B constitutes the parameter vector to be estimated. Other special occurences of function class <i>f</i> (B, <i>t</i>) can be added to approximate the DCF value, if appropriate.

<i>f_c(t)</i> was chosen, because it reflects the conventional approach, where over a fixed period a variable cash flow is estimated and over the rest of time a cash flow, typically the last one, is assumed to be constant.

<i>f_l</i>(<i>t</i>) was chosen, because it additionally allows to model constant growth, incorporates the classical linear regression model and allows - using only two parameters <i>β</i>₀ and <i>β</i>₁ - fairly stable estimations.

<i>f_n(t)</i> was chosen, because it incorporates functions with monotone curvature and thus allows to model dynamic growth. On the other hand, incorporating one more parameter than <i>f_l</i>(<i>t</i>), this class is more susceptible to outliers in the database.

In other words, e.g. the estimators can be calculated using standard methods, such as minimizing least square values, etc.

The calculation is performed for several models in parallel, because the choice of the model results not always straightforward from the database. This problem can be tackled by taking more years of historical data, i.e. past data, into account. In practice however, databases are usally fairly small.

The advantages of the statistical approach over the classical approach (as for example described in<nplcit id="ncit0003" npl-type="s"><text> Ballwieser, 'Unternehmensbewertung, Prozeß, Methoden und Probleme', Schäffer/Poeschel, 2004</text></nplcit>) are that within the standard assumptions of the specific regression model <i>m</i> an unbiased estimator not only for <i>DCF_m</i>, but also for the variance of the random error variables and thus for the variance of <i>DCF_m</i> , <i>σ</i>²(<i>DCF_m</i>), can be calculated. This allows to approximate the distribution of <i>DCF_m</i> and thus to evaluate the precision of its estimation and to model risk premiums objectively, whereas in the field of estimating economic values (subjective) expert knowledge is susceptible to biases, see e.g. the above reference(s).

The need, but not the possibility of this aspect is seen in the classical DCF approach. Ballwieser, for example, states: <i>"Theoretically for future earnings probability distributions have to be forecasted. The probabilities can only be interpreted</i> as <i>subjective plausibilities or degrees of accepting an outcome as true. Probabilities derived from logical considerations or from the analysis of relative frequencies are not to be attained for the purposes of the valuation</i> of a <i>company.",</i> see<nplcit id="ncit0004" npl-type="s"><text> Ballwieser, Unternehmensbewertung, Prozeß, Methoden und Probleme', Schäffer/Poeschel, 2004, page 49f</text></nplcit>.

To model a risk adjusted DCF <maths id="math0022" num=""><math display="inline"><msubsup><mi mathvariant="italic">DCF</mi><mi>m</mi><mi>r</mi></msubsup><mo>,</mo></math><img file="EP1988499A1_D0022.tif" /></maths> we calculate a risk premium <i>RP_m</i> for <i>DCF_m</i> and set <maths id="math0023" num=""><math display="block"><msubsup><mi mathvariant="italic">DCF</mi><mi>m</mi><mi>r</mi></msubsup><mo>:</mo><mo>=</mo><msub><mi mathvariant="italic">DCF</mi><mi>m</mi></msub><mo>-</mo><msub><mi mathvariant="italic">RP</mi><mi>m</mi></msub><mo>,</mo></math><img file="EP1988499A1_D0023.tif" /></maths> because a risk premium defines "the difference between the expected value of an uncertain bet that a person is willing to take and the certain value that he is indifferent to" (reference is made to www.wikipedia.org). Since the distribution class is given within regression model m , the uncertainty of the 'bet' <i>DCF_m</i> only depends on its standard deviation <i>σ_m</i> := <i>σ(DCF_m</i>).

If, sufficient for practical reasons, we assume the risk premium to be independent from the expectation of <i>DCF_m ,</i> the risk premium <i>RP_m</i> can be modeled using the unbiased estimator σ<i>_m</i> of <i>σ_m,</i> i.e. <maths id="math0024" num=""><math display="block"><msub><mi mathvariant="italic">RP</mi><mi>m</mi></msub><mo>:</mo><mo>=</mo><msub><mover><mi>σ</mi><mo>^</mo></mover><mi>m</mi></msub><mo>⁢</mo><mi>c</mi><mo>,</mo></math><img file="EP1988499A1_D0024.tif" /></maths> wherein constant c expresses the degree of risk aversion.

To simplify the approach for the user, he is offered to set the risk premium (i.e. to express <i>c</i>) by naming a confidence level, i.e. a probability for the risk of the deviation from the expectation of <i>DCF_m</i>, or by choosing the expectation of the deviation from the expectation of <i>DCF_m</i> , i.e. by choosing <i>E</i>(|<i>DCF_m-E</i>(<i>DCF_m</i>)|)<i>.</i>

Advantageously <i>c</i> can be given in advance of the calculation of <i>DCF_m,</i> so that the user can easily simulate the outcome <maths id="math0025" num=""><math display="inline"><msubsup><mi mathvariant="italic">DCF</mi><mi>m</mi><mi>r</mi></msubsup></math><img file="EP1988499A1_D0025.tif" /></maths> for different degrees of risk aversion.

In advantage over the classical DCF approach, risk premiums are modeled by using only one parameter, not by using utility functions, which are hard to judge and to express.

For the purpose of comparing the performance of different business units, we scale <maths id="math0026" num=""><math display="inline"><msubsup><mi mathvariant="italic">DCF</mi><mi>m</mi><mi>r</mi></msubsup></math><img file="EP1988499A1_D0026.tif" /></maths> by the first estimated plan value <i>f_m</i>(<i>t</i>₀+1) and define the model dependent <i>limit factor</i><maths id="math0027" num=""><math display="block"><msub><mi>l</mi><mi>m</mi></msub><mo>:</mo><mo>=</mo><mfrac><msubsup><mi mathvariant="italic">DCF</mi><mi>m</mi><mi>r</mi></msubsup><mrow><msub><mi>f</mi><mi>m</mi></msub><mo>⁢</mo><mfenced separators=""><msub><mi>t</mi><mn>0</mn></msub><mo>+</mo><mn>1</mn></mfenced></mrow></mfrac><mn>.</mn></math><img file="EP1988499A1_D0027.tif" /></maths>

This key figure allows to compare the future cash flow developments of the different business entities on a relative basis. By sorting the limit factors of a big number of business entities, f.i. in a periodical report, the controlling department of a real estate company can easily identify good and undesirable developments. Making comparable different business units, the limit factor concept promotes competition within a company and thus supports the beyond budgeting approach.

Features and benefits

Polyvalence principle

Polyvalence principle with the components principle of reference to the future and principle of risk and chance. "A company evaluator, who, instead of exploring the diversity of future possible operating revenues, confines himself to a single value forecast, takes his task too easy. He immunizes his result; only a fortuneteller can contradict a fortuneteller." [Moxter, cited in Ballwieser, S.56]

Reactivity to changing environmental conditions

All changes reflected in the underlying ERP system are automatically propagated into the results.

The following advantages and features can be provided by the above described method and/or the following features can be incorporated in the above described method. <ul id="ul0050" list-style="none"><li>Extraction of the actual and planned data on annual level for a horizon of 5 years in the past and a planning (future) horizon of 6 years per planning position and profit-center-group (economic entity)</li><li>· Individual planning maps for the partial planning of the cost centers, economic entities, profit-centers and investments</li><li>Bottom-up-Planning: up-roll of the partial plannings onto the group/concern to a total planning</li><li>· Period distribution of the planning values of the profit and loss account</li><li>· Period related Value-at-Risk-Calculations (VaR calculations) inclusive expectation deviations and 95%-confidence-interval (so-called monthly statistic) with novel characteristic value as a component of a risk early-warning system</li><li>· Novel DCF-calculation for enterprise controlling for the purposes of a Beyond-Budgeting-Approach and for enterprise evaluation</li><li>· Interface for the transfer of the values into the consolidation</li><li>· Web and GUI based BI-Reporting for all above-mentioned areas (SAP Business Intelligence)</li><li>· Calculation of economic characteristic values and value-driver for enterprise controlling</li><li>· Risk management: Calculation and Monte-Carlo-Simulation of economic characteristic values</li><li>· Portfolio-Management-Approach</li><li>· Reporting in Balanced Scorecard</li><li>· BI-Reporting according to IAS 40 (opening balance sheet, appendix values, DCF-first-evaluation), IAS 11 (POC for building contractor business) and IAS 12</li></ul>

In the following a further detailed description: <ul id="ul0051" list-style="none" compact="compact"><li>The positions of the balance and of the profit and loss account from the source system into the BPS (Business Planning System) are selected. The positions should be displayed hierarchically as in the source system in the BPS, too. The hierarchy and the positions on their own depend on the submission of accounts. Different approaches of the submission of accounts mean for example different evaluation areas, accounts and depreciations in the placement accounting. The submission of accounts according to Commercial Code (HGB) and International Accounting Standards IAS (now: International Accounting Reporting Standards IFRS) is relevant to the Gewofag. For these two submissions of accounts these two versions of the balance- and profit and loss account hierarchies GEW3 (German language: "Bilanzstruktur_GEWOFAG(neu)") respectively GIAS (German language: "Bilanzstruktur_GEWOFAG IAS") exist in the FI (i.e. the Financial Accounted Module in SAP). Reference thereto is also in the BPS.</li></ul>

In analogy to the grouping of accounts into positions in the balance and profit and loss accounts hierarchies of the FI, planning positions for the selection into the BPS are also built which (planning positions) group logical continuous accounts. For example accounts of the balance position 3.1.2 (incomes from the selling of properties) are grouped to the planning position ERA_001 (income from the selling). Planning positions are grouped to planning position types for being able to load them selectively in the BPS by pushing a button. For example the positions ABS_001 (standard depreciation), ABS_002 (special depreciation) and ABS_003 are grouped to the planning position type ABS (depreciations). The summary from accounts to planning positions and from planning positions to planning position types is orientated just loosely on the balance and profit and loss accounts hierarchy. More decisive are the characterization according to the class of the allocation to account objects, according to the algorithm for the selection of the actual values and for calculating of the planned values and the as possible uncomplicated possibility to plan in the BPS. In this way there is differentiated the positions of the hierarchy GEW3 1.1.21 (properties with residential buildings) - 1.1.24 (buildings on strange properties) only between BIL_112A (properties) and BIL_112B (buildings) in the BPS for simplifying the investment planning.

By means of FI- and CO-relevant SAP-Transactions which register the change of stock/stand respectively inputs and outputs said values come to a large extent into the profit-center-calculation, too. Different profit-centers were allocated to the cost centers, as also to the allocation to an account objects of the RE (Real Estate), for example the economic entities, so that it is possible to differentiate stronger than in the Fl the balance and the profit and loss accounts in important partial areas, for example in the fixed assets, in the profit-center-calculation. Therefore where possible, the values of the profit-center-calculation are accessed. Allocation are grouped to one or more account objects of the profit-center-calculation to different classes for planning separately. For example there is planned <ul id="ul0052" list-style="none" compact="compact"><li>· Investments and maintenance efforts only referring to economic entities,</li><li>· Calculating depreciations only referring to cost-centers,</li><li>· Outputs from participations only referring to business division-profit-centers.</li></ul>

Accordingly there is differentiated the three partial plannings: cost-centers-, business unit- and (business-) profit-center-planning. Therefore three classes are formed from the said amount of the allocation to an account object of the profit-center-calculation: profit-center representing <ul id="ul0053" list-style="none" compact="compact"><li>Economic entities,</li><li>· A cost-center or</li><li>· A business division-profit-center.</li></ul>

Different profit-centers can be allocated to one and the same economic entity. Therefore profit-centers are grouped for planning in BPS to profit-center-groups, so that every economic entity exactly matches to a profit-center-group. For keeping the planning unitary only on profit-center-groups in the BPS is planed, not on profit-centers. So, there is also built for profit-centers which represent cost-centers and for business-profit-centers profit-center-groups, although the allocation of profit-centers to profit-center-groups is one-to-one/unambiguous for them. Profit-centers which can be allocated to any of the three classes are allocated to the profit-center-group 0002 (Gewofag).

The planning maps are the base for the planning in the BPS. Planning maps group the planning layouts and the planning functions. The actual and the planned values are loaded which calculate our extractors in the source system by the planning functions into the planning layouts of the planning map. A planning layout represents the hierarchy of the profit-center-groups of a partial planning for selected planning positions of said partial planning. Additionally, there can be provided in a dumped/tilted presentation the hierarchy of the planning position types and planning positions of a partial planning for a selected profit-center-group. After the performance of the partial plannings, the actual and the planned values are aggregated upwards into the aggregate planning. Technically in this way it is summed up to the profit-center-group 001 Gewofag (aggregate/entire). The hierarchy of the planning positions of the aggregate/entire planning represents/maps the balance- and profit and loss account-hierarchy GEW3 respectively GIAS of the Fl. The planning maps of the aggregate planning and the partial plannings refer to exactly one submission of accounts.

In the following, there are provided components of the above described method: <ol id="ol0003" compact="compact" ol-style=""><li>1. Modules of operative business management <ul id="ul0054" list-style="none" compact="compact"><li>1.1. Automated earning planning and balance sheet planning <ul id="ul0055" list-style="dash" compact="compact"><li>Planning characteristics: <ul id="ul0056" list-style="none" compact="compact"><li>-- Time frame: five years</li><li>-- Plain: Planpositions analog balance sheet and earning sheet</li><li>-- Objects: Cost Center, real estate object, Profit-Center</li></ul></li><li>Cost Center planning: <ul id="ul0057" list-style="none" compact="compact"><li>-- Overhead costs and depreciation expenses</li></ul></li><li>Real estate object planning: <ul id="ul0058" list-style="none" compact="compact"><li>-- Revenues</li><li>-- Operating costs</li><li>-- Rental management costs</li><li>-- Plant maintenance costs, modernization costs and site cleanup costs</li><li>-- Overhead costs</li><li>-- Revenue operating costs</li><li>-- Asset balance and receipt</li></ul></li><li>Profit-Center: <ul id="ul0059" list-style="none" compact="compact"><li>-- other internal activity</li><li>-- Costs for sales lands</li><li>-- balance sheet change</li><li>-- Revenue</li><li>-- Money management</li></ul></li></ul></li><li>1.2. Riskquantify per planposition <ul id="ul0060" list-style="dash" compact="compact"><li>Determination: <ul id="ul0061" list-style="none" compact="compact"><li>-- confidence interval as the expected value for the actual in the days to come</li><li>-- forecast as the expected value for the actual in the days to come</li></ul></li></ul></li><li>1.3. Operative real estate reporting <ul id="ul0062" list-style="dash" compact="compact"><li>Reports: <ul id="ul0063" list-style="none" compact="compact"><li>-- Cash Flow</li><li>-- Real estate information's</li><li>-- Residential rental key figure</li><li>-- Real estate value ranking</li></ul></li></ul></li></ul></li><li>2. Modules of strategic enterprise management <ul id="ul0064" list-style="none"><li>1.1. Hierarchically enterprise earning planning and balance sheet planning <ul id="ul0065" list-style="dash" compact="compact"><li>Planning characteristics: <ul id="ul0066" list-style="none" compact="compact"><li>-- Time frame: five years:</li><li>-- Plain: plan positions analog balance sheet and earning sheet</li><li>-- Objects: profit center; company</li></ul></li><li>Summarization the operative profit center plan values to enterprise plan values</li><li>Summarization the operative plan values to value driver: <ul id="ul0067" list-style="none" compact="compact"><li>-- Revenues</li><li>-- Operating costs</li><li>-- maintenance costs, modernization costs and site cleanup costs</li><li>-- Rental management costs</li><li>-- Overhead costs</li><li>-- Revenue operating costs</li><li>-- Asset balance and receipt</li></ul></li></ul></li><li>2.1. Riskquantify per plan position <ul id="ul0068" list-style="dash" compact="compact"><li>Annual determination: <ul id="ul0069" list-style="none" compact="compact"><li>-- confidence interval as the expected value for the actual in the days to come</li><li>-- forecast as the expected value for the actual in the days to come</li></ul></li></ul></li><li>2.2. Riskquantify per Key Performance Indicator <ul id="ul0070" list-style="dash" compact="compact"><li>Image the real estate risk catalog</li><li>Mapping risks to Key Performance Indicators</li><li>Monthly riskquantify: <ul id="ul0071" list-style="none" compact="compact"><li>-- Forecast as the expected value</li><li>-- Value at Risk</li></ul></li></ul></li><li>2.3. Calculation value based enterprise and real estate key figure</li><li>2.4. Calculation the Net Present Value including risk for real estate objects</li><li>2.5. Calculation the Total Net Present Value for real estate portfolios and calculation the risk <ul id="ul0072" list-style="dash" compact="compact"><li>Calculation the Value at Risk for a real estate portfolio with the Variance Covariance method: <ul id="ul0073" list-style="none" compact="compact"><li>-- Product approach: Riskfactors are the Net Present Values of the real estate objects</li><li>-- Model parameters are the relative change Net Present Value of the real estate objects</li><li>-- Hypothesis of the allocation: The Vektor Net Present Value is standard distributed</li><li>-- Transformation the standard distribution of Net Present Values to the distribution value change</li></ul></li></ul></li><li>2.6. Strategic reporting real estate Key Performance Indicators</li></ul></li></ol>

Accordingly, the terms plan data, plan value, expected value etc. can be used as synonyms.

With reference to <figref idref="f0030">Figure 30</figref>, an exemplary system for implementing the invention includes a general purpose computing device in the form of a conventional computing environment 220 (e.g. personal computer), including a processing unit 222, a system memory 224, and a system bus 226, that couples various system components including the system memory 224 to the processing unit 222. The processing unit 222 may perform arithmetic, logic and/or control operations by accessing system memory 224. The system memory 224 may store information and/or instructions for use in combination with processing unit 222. The system memory 224 may include volatile and non-volatile memory, such as random access memory (RAM) 228 and read only memory (ROM) 230. A basic input/output system (BIOS) containing the basic routines that helps to transfer information between elements within the personal computer 220, such as during start-up, may be stored in ROM 230. The system bus 226 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.

The personal computer 220 may further include a hard disk drive 232 for reading from and writing to a hard disk (not shown), and an external disk drive 234 for reading from or writing to a removable disk 236. The removable disk may be a magnetic disk for a magnetic disk driver or an optical disk such as a CD ROM for an optical disk drive. The hard disk drive 234 and external disk drive 234 are connected to the system bus 226 by a hard disk drive interface 238 and an external disk drive interface 240, respectively. The drives and their associated computer-readable media provide nonvolatile storage of computer readable instructions, data structures, program modules and other data for the personal computer 220. The data structures may include relevant data of the implementation of the computerized method as described in more details above. The relevant data may be organized in a database, for example a relational or object database.

Although the exemplary environment described herein employs a hard disk (not shown) and an external disk 242, it should be appreciated by those skilled in the art that other types of computer readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, random access memories, read only memories, and the like, may also be used in the exemplary operating environment.

A number of program modules may be stored on the hard disk, external disk 242, ROM 230 or RAM 228, including an operating system (not shown), one or more application programs 244, other program modules (not shown), and program data 246. The application programs may include at least a part of the functionality as detailed in <figref idref="f0001 f0002 f0003 f0004 f0005 f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013 f0014 f0015 f0016 f0017 f0018 f0019 f0020 f0021 f0022 f0023 f0024 f0025 f0026 f0027 f0028 f0029">figures 1 to 29</figref>.

A user may enter commands and information, as discussed below, into the personal computer 220 through input devices such as keyboard 248 and mouse 250. Other input devices (not shown) may include a microphone (or other sensors), joystick, game pad, scanner, or the like. These and other input devices may be connected to the processing unit 222 through a serial port interface 252 that is coupled to the system bus 226, or may be collected by other interfaces, such as a parallel port interface 254, game port or a universal serial bus (USB). Further, information may be printed using printer 256. The printer 256, and other parallel input/output devices may be connected to the processing unit 222 through parallel port interface 254. A monitor 258 or other type of display device is also connected to the system bus 226 via an interface, such as a video input/output 260. In addition to the monitor, computing environment 220 may include other peripheral output devices (not shown), such as speakers or other audible output.

The computing environment 220 may communicate with other electronic devices such as a computer, telephone (wired or wireless), personal digital assistant, television, or the like. To communicate, the computer environment 220 may operate in a networked environment using connections to one or more electronic devices. <figref idref="f0030">Figure 30</figref> depicts the computer environment networked with remote computer 262. The remote computer 262 may be another computing environment such as a server, a router, a network PC, a peer device or other common network node, and may include many or all of the elements described above relative to the computing environment 220. The logical connections depicted in <figref idref="f0030">figure 30</figref> include a local area network (LAN) 264 and a wide area network (WAN) 266. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.

When used in a LAN networking environment, the computing environment 220 may be connected to the LAN 264 through a network I/O 268. When used in a WAN networking environment, the computing environment 220 may include a modem 270 or other means for establishing communications over the WAN 266. The modem 270, which may be internal or external to computing environment 220, is connected to the system bus 226 via the serial port interface 252. In a networked environment, program modules depicted relative to the computing environment 220, or portions thereof, may be stored in a remote memory storage device resident on or accessible to remote computer 262. Furthermore other data relevant to the application of the insurance claim management evaluation method (described in more detail further below) may be resident on or accessible via the remote computer 262. The data may be stored for example in an object or a relation database. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the electronic devices may be used.

The above-described computing environment is only one example of the type of computing environment that may be used to implement the computerized method.

List of Reference Numerals

<dl id="dl0001" compact="compact"><dt>10</dt><dd>activation device</dd><dt>12</dt><dd>data</dd><dt>14</dt><dd>past data</dd><dt>16</dt><dd>future plan data</dd><dt>18</dt><dd>current data</dd><dt>20</dt><dd>future plan data</dd><dt>22</dt><dd>monthly desired value; lower 95% boundary</dd><dt>24</dt><dd>monthly desired value; expectation variance</dd><dt>26</dt><dd>monthly estimated value</dd><dt>28</dt><dd>monthly desired value; expectation variance</dd><dt>30</dt><dd>monthly desired value; upper 95% boundary</dd><dt>32</dt><dd>period (months)</dd><dt>34</dt><dd>table</dd><dt>36</dt><dd>period (years)</dd><dt>38</dt><dd>yearly desired value; lower 95% boundary</dd><dt>40</dt><dd>yearly desired value; expectation variance</dd><dt>42</dt><dd>yearly estimated value</dd><dt>44</dt><dd>yearly desired value; expectation variance</dd><dt>46</dt><dd>yearly desired value; upper 95% boundary</dd><dt>48</dt><dd>past data</dd><dt>50</dt><dd>past data</dd><dt>52</dt><dd>future plan data</dd><dt>54</dt><dd>future plan data</dd><dt>56</dt><dd>future plan data</dd><dt>58</dt><dd>future plan data</dd><dt>60</dt><dd>future plan data</dd><dt>62</dt><dd>future plan data</dd><dt>64</dt><dd>description</dd><dt>66</dt><dd>discounting interest rates</dd><dt>68</dt><dd>cash flow</dd><dt>70</dt><dd>discounted cash flow without maintenance</dd><dt>72</dt><dd>discounted cash flow</dd><dt>74</dt><dd>discounted cash flow</dd><dt>76</dt><dd>table</dd><dt>78</dt><dd>subtable</dd><dt>80</dt><dd>subtable</dd><dt>82</dt><dd>subtable</dd><dt>84</dt><dd>graph</dd><dt>86</dt><dd>graph</dd><dt>88</dt><dd>graph</dd><dt>90</dt><dd>button</dd><dt>92</dt><dd>button</dd><dt>94</dt><dd>button</dd><dt>96</dt><dd>planning year</dd><dt>98</dt><dd>current interval</dd><dt>100</dt><dd>selection criteria</dd><dt>102</dt><dd>button</dd><dt>104</dt><dd>field</dd><dt>106</dt><dd>DCF value - constant approach</dd><dt>108</dt><dd>DCF value - linear approach</dd><dt>110</dt><dd>DCF value - non-linear approach</dd><dt>112</dt><dd>screenshot</dd><dt>114</dt><dd>booking periods</dd><dt>116</dt><dd>estimate values</dd><dt>118</dt><dd>estimate variance</dd><dt>120</dt><dd>estimate variance</dd><dt>122</dt><dd>95% confidence interval</dd><dt>124</dt><dd>95% confidence interval</dd><dt>126</dt><dd>gain values</dd><dt>128</dt><dd>current values</dd><dt>130</dt><dd>GUI</dd><dt>220</dt><dd>conventional computing environment</dd><dt>222</dt><dd>processing unit</dd><dt>224</dt><dd>system memory</dd><dt>226</dt><dd>system bus</dd><dt>228</dt><dd>random access memory (RAM)</dd><dt>230</dt><dd>read only memory (ROM)</dd><dt>232</dt><dd>hard disk drive</dd><dt>234</dt><dd>external disk drive</dd><dt>236</dt><dd>removable disk</dd><dt>238</dt><dd>hard disk drive interface</dd><dt>240</dt><dd>external disk drive interface</dd><dt>242</dt><dd>external disk</dd><dt>244</dt><dd>one or more application programs</dd><dt>246</dt><dd>program data</dd><dt>248</dt><dd>keyboard</dd><dt>250</dt><dd>mouse</dd><dt>252</dt><dd>serial port interface</dd><dt>254</dt><dd>parallel port interface</dd><dt>256</dt><dd>printer</dd><dt>258</dt><dd>monitor</dd><dt>260</dt><dd>video input/output</dd><dt>262</dt><dd>remote computer</dd><dt>264</dt><dd>local area network (LAN)</dd><dt>266</dt><dd>wide area network (WAN)</dd><dt>268</dt><dd>network I/O</dd><dt>270</dt><dd>a modem</dd></dl>