We've been using Axium's Ajera for about 4 years now. It attracted me because it puts the tools right into our project manager's hands. It also is customizable. I believe that if some basic fundamental design issues could be fixed, Ajera is the ticket. Ajera is aware of the following comments, and I offer them here, in part because I hope Ajera or some other accounting software package picks up on them and incorporates the improvements.
By the way, Ajera has some of the greatest tech support people around. They truly are a joy to work with. I think the issues we experience have to do with how the software has been written. It stems back to IT.
It appears to me that all accounting packages are developed in consultation with accountants, bookkeepers and of course program writers, but not architects. As a result, some items that could really make matters easy to manage and understand just do not exist. For example:
a. The word, "budget" really means, "contract". Thus when a PM enters their budget, Ajera takes that to mean the contract has been signed and fixed at this amount. PMs want to be able to budget one thing, many times well before a contract is in place. However, Ajera is already figuring time entered as "Work In Progress" that is fully billable and expected to be collected. And if a banker or accounting type person looks at our numbers, they also believe it is billable and collectable. In the real world, we know this isn't always true.
b. It is very difficult to determine if a project and/or PM is over budget on any given phase of work or on any given project. I have been suggesting that any work on a "budgeted" but not "contracted" prospect/project be indicated with red negative numerals. As it is right now, it looks like WIP. And all over budget figures should be in red.
c. If a project manager "writes off" some of their work (they were doing this when they knew their time spent was over budget and not billable) on a project, the project then appears to be back on budget. We recently learned to not write off hours, but to "zero invoice" them. However, a saavy PM could still write off hours and make their reports look favorable, thus skewing the reports pertaining to PM performances.
d. We've always had a difficult time using the invoice formats. Although Ajera says they are customizable, our small firm does not have programmers and Ajera's charges for creating these custom formats is beyond our reach.
e. Flow through costs (especially consultants) cause our PMs all kinds of grief. I personally would love to see a system that removes flow through costs. For instance, if our consultant costs us $10,000 and we charge the client $10,000 then it is a revenue neutral item for our PMs. But what happens is they see the $10,000 as time that can be spent on their projects (and they do spend it). And all the charts indicate that they are doing great! Then the invoice from the consultant arrives and our PMs are somehow "shocked" that this put them over budget. We've developed a work around, but it would be great to delete "flow through" costs. Of course, there's always "mark ups" to deal with, but our managers would love to manage those items.
-------------------------------------------
Robin Miller AIA
MSH Architects
Sioux Falls SD
-------------------------------------------