Activity-On-Arc(AOA), Activity-On-Node(AON).
Forum Sponsor
Top Posters
Julian Pegg
1 posts
Peter Nagy
2 posts
Raymund de Laza
17 posts
Syed_Asad
0 posts
Tony Greyvenstein
0 posts
Ahmed Al-Jubouri
13 posts
Umar Alvi
3 posts
Sibusiso Mahlalela
0 posts
Michael Samanyayi
3 posts
Simon Gumede
0 posts
Hi Jillian
Welcome to Planning Planet - as you have found this is the forum to learn and share knowledge and experience.
Please remember however that It is not a good idea to liven up a long dead discussion.
BTW whats with the Rabbit Hutch Shop?
Best regards
Mike Testro
Thank you for sharing these helpful information. I learned a lot from it. I really appreciate you guys sharing these information with us.
<SPAM LINK DELETED BY GARY W>
In responce the Brads point about Pertmaster, when I started planning we used Hornet. The Arrow on Arrow drawing was based upon A1 sheets, activity numbers taken from a rows and column numbering. So simple! Especially as my senior planner made me draw every thing out be hand first! And then do a forward / backward pass before putting it into the computer. His idea of making me learn some planning principles and not just software. Stood me in good stead since!
Mal
AOA - Abort Once Around (such a old topic)
Yes, its true that professionals use both the terminology, Arc as well as arrow.
Depends from which school you have passed from?
Cheers,
Rav
AOA can represent both Activity on ARROW &Activity on ARC,
as in scheduling we find authors using both the terminologies interchangably.
As Ron rightly mentioned, AOA should stand for Activity on Arrow, from where the term Arc comes to replacing the Arrow?
IMO, most software supports PDM/AON because the market demand was there. It is easier (more intuitive) for people to work with. Training people to schedule on ADM/AOA systems who dont know anything about it requires a *lot* of patience.
Bernard Ertl
eTaskMaker Project Planning Software
AON (PDM) is developed to fulfill the shortcomings of AOA method in case of complex project. I guess thats why most of the softwares support it.
"But in general activities are not very straight forward with FS relation, I guess that is the reason most of the programme supporting AON(PDM) technique there you can define all other type of dependencies."
Any relationship that can be modelled with complex dependencies and lags can also be modelled using only FS relationships, with greater decomposition and milestones. The FS-only network will have more activities and milestones, but it will be easier to focus on task-completion criteria. And computing critical path DRAG is usually easier in FS-only networks.
AOA - Activity On Arrow
Finish to Start (FS) relationship only; Dummy activities allowed
AON - Activity On Node
Also called Precedence Diagram Method.
Represent improvement to PERT and CPM by adding lag relationships to activities.
All the four types of relationships allowed.
Start to Start (SS), Start to Finish(SF), Finish to Start (FS) and Finish to Finish (FF).
Arrow indicate dependancy, No dummy activities.
Most of the programs inculding Primavera and MS Project use AON. AOA lacks different type of relationships which enable the AON user to model a real life dynamic situation to a considerable extent.
Though one thing I would like to submit that whenever someone is trying to explain a process, he goes by AOA. AON cant beat the simplicity of AOA.
Reagrds
Rashid Iqbal
AOA (ADM) is used when the relationship among the activities are clearly defind as FS. But in general activities are not very straight forward with FS relation, I guess that is the reason most of the programme supporting AON(PDM) technique there you can define all other type of dependencies.
I always though that AOA stood for Activity-on-Arrow, as in arrow diagraming. Did I sleep through another class and miss something?
IMHO, AON (or PDM) is easier for schedulers to conceptualize in the head from a list of predecessors/successors. Ie. there are less numbers/codes/labels representing the logic network.
AOA (or ADM) is more explicit when the logic network is graphed, but is more difficult to conceptualize from a list of I,J nodes.
Bernard Ertl
eTaskMaker Project Planning Software