Re: ... more on Asset Manager

When someone hires an asset they do not own it.

Asset 1----* Ownship *----1 Owner

Every time you transfer ownership you add a new Ownership.  This would track 
multiple transfers, however, I presume that you only really need to know

A: Date acquired + from whom.
B: Date relinquished + how.

For this I would have something like the following.

Asset 1-----1 AssetAcquisition (contains the date, former owner details, 
etc).
Asset 1-----1 AssetRelease (abstract class)

AssetRelease <|------ AssetSale (holds information about the new owner)
AssetRelease <|------ AssetScrapped (whatever info you feel is relevant)



As for hire you simply need an asset movement history


Asset 1------* AssetMovement *-----1 Location




Pete 

I need to model ownership of any asset. Ownership can be borrowed, leased, 
bought(cash), rented etc. Each of these types have different properties. My 
thoughts so far:-

                        Leases
        Financier    ------->   Asset
                       1..*     1..*

                        Rents
        Rentor    --------->   Asset
                        1..*    1..*

etc...

Now the class structure is a wee bit of a problem for me:-

Do we have the same situation as my previous asset manager post; ie, that a 
'legal' system should be asked for the ownership details, as I also believe 
that an asset should not know who owns it, it just needs to do 
certain(asset) things. So,

                    TAsset 
TContracts
                    -----------                                              
       ------------
                    ownership: TOwnerType  ?????   or 
GetOwnerType(Asset): TOwnerType;


I am open to all suggestions, including name changes.

Thanks.
Dion. 

>> When someone hires an asset they do not own it.
I struggled for a generic word, maybe 'Possess'? as oppossed to 'Own'.

>> A: Date acquired + from whom.
     B: Date relinquished + how.

This will do for now.

So if I have an instance of an asset class, and want to establish how I have 
acquired it(the asset) and from whom, which class will handle this?

GetPossessionType(Asset): TPossessionType?

dion. 

I am interested in the assets from the company who posesses(not necessarily 
owns) the assets point of view. So, if I am a vending company who places 
machines(assets) at clients sites(for profit), I want to know which machines 
I have financed, rented or have rebuilt from scrap, or have inherited etc.


"Dion" <dion@mighty.co.za> wrote in message 
news:47b953fd@newsgroups.borland.com...
>>> When someone hires an asset they do not own it.
> I struggled for a generic word, maybe 'Possess'? as oppossed to 'Own'.
>
>>> A: Date acquired + from whom.
>     B: Date relinquished + how.
>
> This will do for now.
>
> So if I have an instance of an asset class, and want to establish how I 
> have acquired it(the asset) and from whom, which class will handle this?
>
> GetPossessionType(Asset): TPossessionType?
>
> dion.
> 

That's an asset location.  I would model it like so.....


Asset *------1 AssetLocation


Customer 1---* CustomerAssetLocation
AssetLocation <|------ CustomerAssetLocation


This way you can have any number of things (Customer, Garage) owning a 
location with a reciprocal link.  You could have a PermanentLocation (where 
it is most of the time), BaseLocation (where it is hired out from), 
LastKnownLocation (for temporary relocation for repairs etc).

Having a CustomerAssetLocation has the additional benefit that you can have 
additional logic for receiving assets.  You may need to record the number of 
assets / reject additional assets if it would violate the operating license 
of the location for example.


>I am interested in the assets from the company who posesses(not necessarily

>owns) the assets point of view. So, if I am a vending company who places 
>machines(assets) at clients sites(for profit), I want to know which 
>machines I have financed, rented or have rebuilt from scrap, or have 
>inherited etc.

SomeCustomer.Locations.Assets would give you the list of assets currently 
held by a specific customer.


Pete