|
Fixed |
Class |
Description |
|
10 |
Enh |
Lease Analysis has been modified to accept
analysis based on negative revenues as well as positive. This facilitates analysis
of leases on an after tax basis, to compare with other alternatives such as purchase
and/or build to suit. See our Cost Comparison sample for an example of
this capability. |
|
10 |
Enh |
Utilities/Cash Flow Analysis has
been enhanced to allow you to combine
cash flows from multiple investments/analyses in one cash flow analysis. Access
this new capability by choosing File/Import Cash Flows, and then choosing
the new Combine Cash Flows ... button in the Import Cash Flows Dialog.
You may specify any number of Assumption Sets as you want, and then save the specification
for later use when you change one of more of the Assumption Sets, so that you may
re-do the combined analysis with no additional effort. The combined cash flows are
sorted by date for your easy comprehension and presentation of the combined results. |
|
10 |
Bug |
In Lease Analysis, requesting Print/Print
in the Lease View and then choosing to print All Leases with
page numbering turned on, the page number would repeat rather than increasing properly.
Thanks to John Ennis, CCIM for the report. |
|
10 |
Enh |
We have added a new capability to input development
projects at Edit/Development Spending. In addition to providing an incredibly
easy data input process, this Development Spending Dialog provides the ability to
specify the parameters for a Construction Draw loan and the Permanent Loan to take
the Draws out at the end of the development project. Both loans are linked
to the development spending items, so when you change the amount of a spending item,
the loans are automatically adjusted. This capability is compatible with all elements
of planEASe, including Basic, Sensitivity, Detail and Risk analysis, as well as
the Partnership Models and the Monthly Extension. This capability
eliminates the previous need to set Substitute Basis and structure separate Draw
Loans for development projects, as well as adding new and realistic capabilities
for Sensitivity and Risk Analysis of such projects. |
|
10 |
Enh |
We have added an entirely new analysis capability
- Unit Sales - for our users who have the optional Monthly Extension.
Unit Sales developments include
land development, subdivisions, and condo conversion, for instance. Use this capability
any time you are dividing a property, developing it, selling the pieces, and, therefore,
are taxed as a dealer (yes, the analysis is valid after tax). Pop
up the Unit Sales dialog box (at Edit/Unit Sales...) to enter the costs
for the development, schedule the sales of the units, and specify the draw loan
parameters (the draw loan is structured as a revolving line of credit,
so you can include multiple construction phases in your development).
Entering the specifications on a single screen makes the assumption entry process
a breeze. Press OK and the analysis is ready to go. The loan is linked
to both the costs (for draws), and unit sales (for repayments), so if you vary any
of these items the loan automatically adjusts, and the tax ramifications are changed
as well. Global assumptions like Price Multiplier and Cost Multiplier
make it easy to perform powerful what-if analysis with the planEASe Sensitivity
and/or Risk analysis capabilities. |
|
10.01 |
Bug |
Depreciation pages using the default value
of zero for the Depreciation Start Date (at acquisition) did not produce the normally
expected depreciation. The work-around is to explicitly declare the Start Date to
be the Acquisition Date, but we consider this problem to be so central that we provided
everyone shipped version 10 with a replacement CD containing version 10.01, fixing
this problem. Introduced in version 10 and fixed in 10.01 |
|
10.01 |
Bug |
Using the new Edit/Development Spending...
capability, in some situations, if you used a Permanent Loan Amount Method different from % of total Draw Loan Balance and then saved the Assumption Set, the
next time you loaded that Assumption Set, the method was reset to % of total Draw
Loan Balance from your previous choice, and the method would have to be
reset. Additionally, if you chose not to use a draw loan, but did specify a Permanent
Loan, the amount of the loan was generally in error. Thanks to Dean Cotlow, CCIM
SIOR for the very fast and complete report. Introduced in version 10 and fixed in
10.01 |
|
10.01 |
Bug |
If you were in a Partnership Model, in either
the Unit Sales Dialog or the Development Spending Dialog, and accessed File/Open
Unit Sales ... or File/Open Development ... you would see RP Assumption
Sets rather than the new Development Spending or Unit Sales files. Introduced in
version 10 and fixed in 10.01 |
|
10.01 |
Bug |
The new Accrue by Period growth
methods introduced in Version 9 mis-computed if used for Continuation Pages in Monthly
Mode. Thanks to Beau Stoneman CCIM for his well documented report. Introduced in
version 9 and fixed in 10.01. |
|
10.02 |
Bug |
The Prepayment Penalty, Payment Override
and Balloon Payment Due fields in the new Permanent Loan Page of the new Development
Spending capability did not function properly. Thanks to Dane Hillyard for the report.
Introduced in version 10 and fixed in 10.02. |
|
10.02 |
Bug |
In both Unit Sales and Development Spending,
the Mos (Expenditure Months) Column entry was designed for amounts of 1
month or more, but entries of 0 were accepted. Likewise, the various date fields
in the new dialogs accepted 0 entries. Furthermore, entry of dates before and at
Acquisition as well as after the end of the Holding Period were accepted. This caused
a trapped computations error, so all analysis functions and audits would not work.
A similar problem for Unit Sales Std Cost (Standard Cost) Column entries
existed. Eliminating the 0 entries in the Dialog solves the problem. Zero entries
are no longer permitted. Introduced in version 10 and fixed in 10.02. |
|
10.02 |
Bug |
In Unit Sales, if the combination of the
Start Date and the Expenditure Months for a Unit Sales Item extended beyond the
end of the Holding Period, and a Draw Loan was requested, a trapped computation
error occurred. Thanks to Brad McGill for the report. Introduced in version 10 and
fixed in 10.02. |
|
10.02 |
Enh |
Many users of the new Unit Sales Capability
have asked for better visibility of the Unit Sales Draw Loan. We have added a Unit
Sales Draw Loan report to the Report Menu in the Unit Sales Dialog, displaying
the Loan Balance for the draw loan during the project. |
|
10.02 |
Enh |
Several home builders have suggested that
the Unit Sales Draw Loan be discharged by payments consisting of a percentage (exceeding
100%) of the Standard Cost for the Units sold. Effective with version 10.02, if
you enter a percentage exceeding 100% in the Draw Discharge Rate, the loan payments
will be computed as that percentage of the Standard Cost. |
|
10.02 |
Enh |
Now, with Assumption Sets containing either
a Development Spending Draw Loan, or a Unit Sales Draw Loan, if you conduct Sensitivity
or Risk Analysis using the Loan Amount as the Measure, the amount reported will
be the maximum loan balance for the draw
loan. |
|
10.02 |
Enh |
The Audit Window for both the Unit Sales
Draw Loan and the Development Spending Draw Loan has been changed to show the Draw
Loan Balance at the end of the period (either Month (in Monthly Mode) or Year (in
Annual Mode)) |
|
10.02 |
Bug |
In Edit/Development Spending, if
you entered an Item Amount (Price/Item times Quantity) of $100 or less, the Development
Spending Dialog handled it properly, but when the Dialog was posted to planEASe
pages, the amount was interpreted as a percentage of the Price of Property, resulting
in either 0 or an outlandish amount for the Item. Thanks to Joe Turner CCIM for
the report, and his patience. Introduced in version 10 and fixed in 10.02. |
|
10.02 |
Bug |
In Edit/Development Spending, if
you increase a Spend Date so as to cause spending beyond the until date of the Draw
Loan, the until date (which is the Origination Date of the Permanent loan, if a
permanent loan is specified) is automatically increased to occur after
the end of the last spending. Unfortunately, if you decreased the time of the last
scheduled spending, the system would not let you decrease the until date correspondingly.
Introduced in version 10 and fixed in 10.02. |
|
10.02 |
Bug |
In Utilities/Cash Flow Analysis,
if you chose Import/Combine Cash Flows, and included the Current Assumption
Set rather than choosing a saved Combination, the Investment Name did not post to
the automatic comment. Introduced in version 10 and fixed in 10.02. |
|
10.02 |
Enh |
When recovering existing specifications into
the Development Spending Dialog or the Unit Sales Dialog, the default filename was
Untitled. This has been changed so the default filename is the name of
the Assumption
Set. |
|
10.02 |
Enh |
In Edit/Unit Sales, we have added
a Unit Sales Profit report showing in summary, the sales, cost, and, if
a draw loan is specified, the interest costs, leading to the
currently planned profit. |
|
10.02
|
Bug |
If you used one (or more) of the new
Exp -%ei pages, and chose a Sale Price Method of Cap Current NOI, the NOI on
which the Sale Price was based would typically be slightly understated. Thanks to
David Sindusuprono for the report. Introduced in version 9 and fixed in 10.02. |
|
10.02 |
Bug |
Development Spending and Unit Sales Titles
(such as "Hard Costs", etc.) were inadvertently shown in Detail Analysis grids and
graphs. Introduced in version 10 and fixed in 10.02. |
|
10.02 |
Enh |
The format of the Project Cost Schedule Reports
in both Development Spending and Unit Sales has been improved to better show the
cost items which are spread over multiple months. Our thanks to Virgil Kemp for
suggesting the improvements during a planEASe Class. |
|
10.02 |
Bug |
In Income Statements for projects using Construction
Draw loans, the Net Sale Proceeds for the year(s) that the Construction Draw was
outstanding were misstated due to a sign reversal on the loan repayment. Thanks
to Marc Weinberg for the report. Introduced in version 10 and fixed in 10.02. |
|
10.02 |
Enh |
The Economic Stimulus Bill signed into law
in March 2002 allows certain (significantly restricted) Tenant Improvements to qualify
for an immediate 30% depreciation deduction, with the remaining 70% to be depreciated
over the normal 39 year life as under previous law. This treatment is sunsetted
at the end of 2004 in the Bill. To implement this treatment in version 10.02 and
beyond for a $10,000 TI incurred February 2003, add a Depreciation Page, Page Title
as you prefer, Depreciable Amount $3,000, Depreciable Life 1 year, Depreciation
Start Date 2.03. Then use Edit/Add Sub Page Depreciable Amount $7,000,
Depreciable Life 39 years, Depreciation Start Date 2.03. |
|
10.03 |
Bug |
The new Unit Sales Draw Report mis-computed
if you entered a number of loan points without specifying a draw loan maximum amount. The loan itself computed properly -- only the Report was wrong. Thanks to Steve
Altman for the detailed report. Introduced in version 10.02 and fixed in 10.03. |
|
10.03 |
Bug |
If you specified a Development Spending Draw
loan, the total amount of the loan was erroneously shown as interest expense in
Basic Analysis and Income Statements, thereby mis-stating after tax results. Thanks
to Gene Trowbridge, CCIM for the detailed report. Introduced in version 10.02 and
fixed in 10.03. |
|
10.03 |
Bug |
The revised Development Spending Project
Cost Schedule Report misstated items spread over 2 or more months. Thanks to Jim
Langdoc for the detailed report. Introduced in version 10.02 and fixed in 10.03. |
|
10.03 |
Enh |
In both the Unit Sales and Development Spending
Cost Grids, the Measure column allows you to add as many measures as needed by typing
over the default Each measure. Now you can also rename any measure (other
than Each) by typing over it in any item where it has been chosen, and
any other usages will be updated to the new name automatically. Now you may also
delete any measure (other than Each and SqFt) by highlighting
the measure name and pressing the delete key. All items using that measure will
be changed to use Each. |
|
10.04 |
Bug |
In the Partnership Models, if the Holding
Period was greater than 33 years and you specified a Partnership fee Type 2 (%of
Effective Income) there was an Error 9 causing the software to halt. Thanks to Dan
Blackford for the detailed report. |
|
10.04 |
Bug |
In Unit Sales, if you entered one or more
cost items without any Unit Names in the Unit Grid, you would receive an error 9
causing the software to halt when re-entering the Unit Sales Dialog. Introduced
in Version 10.03 and fixed in 10.04. |
|
10.04 |
Bug |
In Unit Sales and Development Spending, using
the " character in Item Name caused a corrupted Assumption Set file when saved.
Introduced in Version 10 and fixed in 10.04. |
|
10.04 |
Bug |
In Unit Sales Partnership / LLC computations,
the Investment Return to Limiteds / Members Assumption was not effective, due to
lack of a sale at the conclusion of operations. Now, for (Unit Sales Partnerships
only) this assumption applies to all Partnership / LLC income. Introduced in Version
10 and fixed in 10.04. |
|
10.04 |
Bug |
If you specified interest to be Paid
rather than Accrued for the Unit Sales Draw Loan, the interest did not
post properly to Debt Service. Thanks to Joe Turner for the report. Introduced in
Version 10.02 and fixed in 10.04. |
|
10.04 |
Bug |
The Unit Sales Cost Schedule Report and the
Development Spending Project Cost Schedule Report mis-computed when handling items
of quantity greater than 1 spread over more than 1 month. Introduced in Version
10.03 and fixed in 10.04. |
|
10.04 |
Bug |
In Development Spending, you could not spread
an item over more than 2 years in Annual mode. Thanks to Steve Altman for the report.
Introduced in Version 10 and fixed in 10.04. |
|
10.05 |
Bug |
In the Partnership Models, the After Tax
Cash Flow for the Limited Partners / Members was misstated. Introduced in version
10.04 and fixed in 10.05. Thanks to Robert Sheppard for his detailed report. |
|
10.05 |
Bug |
In both Development Spending and Unit Sales,
entry of more than about 950 cost items caused the cost reports to miscompute. While
not reported, the Unit Sales Summary and Schedule Reports contained the same error.
Introduced in version 10 and fixed in 10.05. Thanks to Michael Williams for his
detailed report. |