Everything you described was realised in Spider Project too. In Spider Project we create references like what resources are necessary for the work volume unit on certain activity types. This references can be applied to any project and activity volume will define what materials and in what quantities are necessary to perform project activities. Changes in references can be transfered to projects.
But you are wrong about algorithms. Resource levelling algorithms are different. We are proud that our algorithms produce best schedules. And this is one of the reasons why Spider Project is most popular in Russia.
What I saw nice in Artemis is the opportunity to assemble resoruce.
For example i can say the 1 cm of concrete is a level 1 resoruce, link to level 2 resoruces like cement, sand, batch plat, etc ... every one with its quantities, costs.
And any change in the elementary quantity or cost in level 2 is reflected in the upper level.
Is P3 this is possible but You have to develop your little application outside.
After all the software are good and all are bad, in function of the information I put "inside".
All are based on the same algorithms, the difference is in the interface, the ready report system they offer.
Well, I used Artemis quite a lot. I can say that it is the most perfect PM software that I ever used. Though it was said that it is not user-friendly, in reality most of my Artemis "coding" (an instruction to tell what to do)were easily managed or modified by even a technician level within a period of 1 to 2 weeks. I agree that to be able to design a customised system to cater for a certain project requirements need a least a programming skill. However, for experienced user it is always easy to simply use the existing coding with minor modification for other projects.
Ive developed quite a number of systems using Artemis, e,g, timesheet, deliverables register for drawings & document, procurement tracking system, etc. All this can be linked to a schedule with a press of a button.
Member for
22 years 8 months
Member for22 years8 months
Submitted by Gilbert Rayco on Sun, 2003-12-14 08:54
Member for
24 years 9 monthsRE: Artemis: implementation issues
Everything you described was realised in Spider Project too. In Spider Project we create references like what resources are necessary for the work volume unit on certain activity types. This references can be applied to any project and activity volume will define what materials and in what quantities are necessary to perform project activities. Changes in references can be transfered to projects.
But you are wrong about algorithms. Resource levelling algorithms are different. We are proud that our algorithms produce best schedules. And this is one of the reasons why Spider Project is most popular in Russia.
Member for
22 years 3 monthsRE: Artemis: implementation issues
The same can be done with P3 using Ra engine.
What I saw nice in Artemis is the opportunity to assemble resoruce.
For example i can say the 1 cm of concrete is a level 1 resoruce, link to level 2 resoruces like cement, sand, batch plat, etc ... every one with its quantities, costs.
And any change in the elementary quantity or cost in level 2 is reflected in the upper level.
Is P3 this is possible but You have to develop your little application outside.
After all the software are good and all are bad, in function of the information I put "inside".
All are based on the same algorithms, the difference is in the interface, the ready report system they offer.
Member for
16 years 9 monthsRE: Artemis: implementation issues
Well, I used Artemis quite a lot. I can say that it is the most perfect PM software that I ever used. Though it was said that it is not user-friendly, in reality most of my Artemis "coding" (an instruction to tell what to do)were easily managed or modified by even a technician level within a period of 1 to 2 weeks. I agree that to be able to design a customised system to cater for a certain project requirements need a least a programming skill. However, for experienced user it is always easy to simply use the existing coding with minor modification for other projects.
Ive developed quite a number of systems using Artemis, e,g, timesheet, deliverables register for drawings & document, procurement tracking system, etc. All this can be linked to a schedule with a press of a button.
Member for
22 years 8 monthsRE: Artemis: implementation issues
Artemis is a very flexible tool, all format works best.
I may be of help if u can specify format,are u referring to method (PDM or ADM) or reporting format, i.e gattchart, logic,tabular.
I used artemis for years & for me its perfect tool but not user friendly.
G. Rayco