This requires the asset factories to be ordered.
Reading the data used to build agents and relationships (if the model is data-driven); a. Several asset factories create assets and the relationships between them; b.
Behaviour factories are called after all the asset factories, in any order, since behaviour creations are independent of each other - they communicate only via the assets.
For our electricity network, our asset factories constructed assets based on a data file extracted directly from the Ergon Energy database, so had access to the real attributes of each asset, and their connection to one another.
Only then will the battery asset factories be called to create B and attach them to the right nodes N. To satisfy this requirement of reference over the assets, precedence of the creation of some assets over others was determined.
In order to solve this problem, partial ordering of asset factories is used where an attribute (Predecessors) allows defining which other factories need to be called before this one.
A plugin can contain one or more asset factories that can control which assets need to be created; many factories can be defined for a given type of asset creation for example, with slight variations depending on the aim of the factory.
Company B plows back every penny into operating assets – factories, equipment and inventory.
An example of this, previously mentioned in this paper, is the asset network factory, which creates many different types of assets (lines, buses, switches, transformers, and premises) and puts them in relation to one another.
(No other asset from factories and shares to patents enjoyed this capital gains free ride).
