Re: new product type: item rental

[Jacques Le Roux]

I agree with both Adrian (a bicycle is a fixed asset of a rental company) and BJ (you provide a service on this fixed asset when you
clean the bicycle, it's an asset maintenance)
And also with Scott: we should really continue to discuss details on dev ML..

Jacques

From: "Adrian Crum" <[hidden email]>

> The items for rent are fixed assets of the rental company, not products.
>
> -Adrian
>
> On 8/30/2011 3:58 AM, Hans Bakker wrote:
>> We have a requirement to rent items like tools, video's cars motocycles
>> or other assets for a certain period of time.
>>
>> The items will be handed out and returned at which point a service or
>> extra charge could be possible for damage.
>>
>> I was thinking about a product which is delivered and where an automated
>> return authorization is assigned so the warehouse knows what is coming
>> back.
>>
>> let me know any other ideas?
>>

[hans_bakker]

Ok I will see if we can use the fixed assets, and will come back if i
see problems......

Regards,
Hans


On Tue, 2011-08-30 at 09:19 +0200, Jacques Le Roux wrote:

> I agree with both Adrian (a bicycle is a fixed asset of a rental company) and BJ (you provide a service on this fixed asset when you
> clean the bicycle, it's an asset maintenance)
> And also with Scott: we should really continue to discuss details on dev ML..
>
> Jacques
>
> From: "Adrian Crum" <[hidden email]>
> > The items for rent are fixed assets of the rental company, not products.
> >
> > -Adrian
> >
> > On 8/30/2011 3:58 AM, Hans Bakker wrote:
> >> We have a requirement to rent items like tools, video's cars motocycles
> >> or other assets for a certain period of time.
> >>
> >> The items will be handed out and returned at which point a service or
> >> extra charge could be possible for damage.
> >>
> >> I was thinking about a product which is delivered and where an automated
> >> return authorization is assigned so the warehouse knows what is coming
> >> back.
> >>
> >> let me know any other ideas?
> >>
>
>

--
Ofbiz on twitter: http://twitter.com/apache_ofbiz
Alternative ofbiz website: http://ofbiz.info
http://www.antwebsystems.com : Quality services for competitive rates.

[BJ Freeman]

I responded to the Product that is a service.
so the difference is this ia no longer an asset of the company but
belongs now to the customer and the service is provided by the company,
to the customer.
like selling a car with a service contract. The contract (agreement)
then determine when and what services will be provided.

To stop duplication, the assetmaint entities and code should be made
generic then association to support the assetmain be done. What I am
addressing is the scheduling of the service to the product sold. Though
in an agreement, the actual maintenance process is run by the generic
service code with supporting types.


Jacques Le Roux sent the following on 8/30/2011 12:19 AM:

> I agree with both Adrian (a bicycle is a fixed asset of a rental
> company) and BJ (you provide a service on this fixed asset when you
> clean the bicycle, it's an asset maintenance)
> And also with Scott: we should really continue to discuss details on dev
> ML..
>
> Jacques
>
> From: "Adrian Crum" <[hidden email]>
>> The items for rent are fixed assets of the rental company, not products.
>>
>> -Adrian
>>
>> On 8/30/2011 3:58 AM, Hans Bakker wrote:
>>> We have a requirement to rent items like tools, video's cars motocycles
>>> or other assets for a certain period of time.
>>>
>>> The items will be handed out and returned at which point a service or
>>> extra charge could be possible for damage.
>>>
>>> I was thinking about a product which is delivered and where an automated
>>> return authorization is assigned so the warehouse knows what is coming
>>> back.
>>>
>>> let me know any other ideas?
>>>
>
>
>

[Adrian Crum-3]

I'm not sure what you mean by "the assetmaint entities and code should
be made generic" - the asset maintenance code is fairly generic.

Asset maintenance is intended to be used to track required/scheduled
maintenance on fixed assets. The most common use is to maintain an
organization's own fixed assets, but there is no reason it can't be used
to track someone else's fixed assets.

One of the features of Asset Maint is the ability to have multiple fixed
assets based on a single product and product maintenance regime. So, a
service depot that is authorized to work on Acme Model B Widget would
have an Acme Model B Widget product (but no inventory of course), and a
maintenance regime set up for the Acme Model B Widget. When a customer
brings in an Acme Model B Widget, a fixed asset is created based on the
Acme Model B Widget product and the customer is made the owner of that
fixed asset. The Acme Model B Widget fixed asset automatically inherits
the Acme Model B Widget product's maintenance regime. The service depot
can even set things up to automatically email the customer when service
is due on their Acme Model B Widget.

The party performing the service can be a depot employee or an outside
service. If the party or outside service is assigned to the product
maintenance in one of the maintenance roles, then they will be
automatically assigned to any maintenance work efforts for fixed assets
based on that product. So, let's say depot employee Trevor Smith is the
only employee certified to repair the Acme Model B Widget. Just assign
Trevor Smith to the Acme Model B Widget product maintenance in one of
the maintenance roles, and any time a customer brings in an Acme Model B
Widget for repair, Trevor will be assigned to that repair automatically.

-Adrian


On 8/30/2011 12:30 PM, BJ Freeman wrote:

> I responded to the Product that is a service.
> so the difference is this ia no longer an asset of the company but
> belongs now to the customer and the service is provided by the company,
> to the customer.
> like selling a car with a service contract. The contract (agreement)
> then determine when and what services will be provided.
>
> To stop duplication, the assetmaint entities and code should be made
> generic then association to support the assetmain be done. What I am
> addressing is the scheduling of the service to the product sold. Though
> in an agreement, the actual maintenance process is run by the generic
> service code with supporting types.
>
>
> Jacques Le Roux sent the following on 8/30/2011 12:19 AM:
>> I agree with both Adrian (a bicycle is a fixed asset of a rental
>> company) and BJ (you provide a service on this fixed asset when you
>> clean the bicycle, it's an asset maintenance)
>> And also with Scott: we should really continue to discuss details on dev
>> ML..
>>
>> Jacques
>>
>> From: "Adrian Crum"<[hidden email]>
>>> The items for rent are fixed assets of the rental company, not products.
>>>
>>> -Adrian
>>>
>>> On 8/30/2011 3:58 AM, Hans Bakker wrote:
>>>> We have a requirement to rent items like tools, video's cars motocycles
>>>> or other assets for a certain period of time.
>>>>
>>>> The items will be handed out and returned at which point a service or
>>>> extra charge could be possible for damage.
>>>>
>>>> I was thinking about a product which is delivered and where an automated
>>>> return authorization is assigned so the warehouse knows what is coming
>>>> back.
>>>>
>>>> let me know any other ideas?
>>>>
>>
>>

[Jacques Le Roux]

Thanks for the detailled explanation Adrian,

Is that already all implemented (like automatically sending an email to user from service depot)?

Jacques

From: "Adrian Crum" <[hidden email]>

> I'm not sure what you mean by "the assetmaint entities and code should
> be made generic" - the asset maintenance code is fairly generic.
>
> Asset maintenance is intended to be used to track required/scheduled
> maintenance on fixed assets. The most common use is to maintain an
> organization's own fixed assets, but there is no reason it can't be used
> to track someone else's fixed assets.
>
> One of the features of Asset Maint is the ability to have multiple fixed
> assets based on a single product and product maintenance regime. So, a
> service depot that is authorized to work on Acme Model B Widget would
> have an Acme Model B Widget product (but no inventory of course), and a
> maintenance regime set up for the Acme Model B Widget. When a customer
> brings in an Acme Model B Widget, a fixed asset is created based on the
> Acme Model B Widget product and the customer is made the owner of that
> fixed asset. The Acme Model B Widget fixed asset automatically inherits
> the Acme Model B Widget product's maintenance regime. The service depot
> can even set things up to automatically email the customer when service
> is due on their Acme Model B Widget.
>
> The party performing the service can be a depot employee or an outside
> service. If the party or outside service is assigned to the product
> maintenance in one of the maintenance roles, then they will be
> automatically assigned to any maintenance work efforts for fixed assets
> based on that product. So, let's say depot employee Trevor Smith is the
> only employee certified to repair the Acme Model B Widget. Just assign
> Trevor Smith to the Acme Model B Widget product maintenance in one of
> the maintenance roles, and any time a customer brings in an Acme Model B
> Widget for repair, Trevor will be assigned to that repair automatically.
>
> -Adrian
>
>
> On 8/30/2011 12:30 PM, BJ Freeman wrote:
>> I responded to the Product that is a service.
>> so the difference is this ia no longer an asset of the company but
>> belongs now to the customer and the service is provided by the company,
>> to the customer.
>> like selling a car with a service contract. The contract (agreement)
>> then determine when and what services will be provided.
>>
>> To stop duplication, the assetmaint entities and code should be made
>> generic then association to support the assetmain be done. What I am
>> addressing is the scheduling of the service to the product sold. Though
>> in an agreement, the actual maintenance process is run by the generic
>> service code with supporting types.
>>
>>
>> Jacques Le Roux sent the following on 8/30/2011 12:19 AM:
>>> I agree with both Adrian (a bicycle is a fixed asset of a rental
>>> company) and BJ (you provide a service on this fixed asset when you
>>> clean the bicycle, it's an asset maintenance)
>>> And also with Scott: we should really continue to discuss details on dev
>>> ML..
>>>
>>> Jacques
>>>
>>> From: "Adrian Crum"<[hidden email]>
>>>> The items for rent are fixed assets of the rental company, not products.
>>>>
>>>> -Adrian
>>>>
>>>> On 8/30/2011 3:58 AM, Hans Bakker wrote:
>>>>> We have a requirement to rent items like tools, video's cars motocycles
>>>>> or other assets for a certain period of time.
>>>>>
>>>>> The items will be handed out and returned at which point a service or
>>>>> extra charge could be possible for damage.
>>>>>
>>>>> I was thinking about a product which is delivered and where an automated
>>>>> return authorization is assigned so the warehouse knows what is coming
>>>>> back.
>>>>>
>>>>> let me know any other ideas?
>>>>>
>>>
>>>

[BJ Freeman]

the top level for  product type service would have an agreement that
sets up the all you mention, and wold also create the project and tasks
for purpose of managing resources.

Adrian Crum sent the following on 8/30/2011 5:00 AM:

> I'm not sure what you mean by "the assetmaint entities and code should
> be made generic" - the asset maintenance code is fairly generic.
>
> Asset maintenance is intended to be used to track required/scheduled
> maintenance on fixed assets. The most common use is to maintain an
> organization's own fixed assets, but there is no reason it can't be used
> to track someone else's fixed assets.
>
> One of the features of Asset Maint is the ability to have multiple fixed
> assets based on a single product and product maintenance regime. So, a
> service depot that is authorized to work on Acme Model B Widget would
> have an Acme Model B Widget product (but no inventory of course), and a
> maintenance regime set up for the Acme Model B Widget. When a customer
> brings in an Acme Model B Widget, a fixed asset is created based on the
> Acme Model B Widget product and the customer is made the owner of that
> fixed asset. The Acme Model B Widget fixed asset automatically inherits
> the Acme Model B Widget product's maintenance regime. The service depot
> can even set things up to automatically email the customer when service
> is due on their Acme Model B Widget.
>
> The party performing the service can be a depot employee or an outside
> service. If the party or outside service is assigned to the product
> maintenance in one of the maintenance roles, then they will be
> automatically assigned to any maintenance work efforts for fixed assets
> based on that product. So, let's say depot employee Trevor Smith is the
> only employee certified to repair the Acme Model B Widget. Just assign
> Trevor Smith to the Acme Model B Widget product maintenance in one of
> the maintenance roles, and any time a customer brings in an Acme Model B
> Widget for repair, Trevor will be assigned to that repair automatically.
>
> -Adrian
>
>
> On 8/30/2011 12:30 PM, BJ Freeman wrote:
>> I responded to the Product that is a service.
>> so the difference is this ia no longer an asset of the company but
>> belongs now to the customer and the service is provided by the company,
>> to the customer.
>> like selling a car with a service contract. The contract (agreement)
>> then determine when and what services will be provided.
>>
>> To stop duplication, the assetmaint entities and code should be made
>> generic then association to support the assetmain be done. What I am
>> addressing is the scheduling of the service to the product sold. Though
>> in an agreement, the actual maintenance process is run by the generic
>> service code with supporting types.
>>
>>
>> Jacques Le Roux sent the following on 8/30/2011 12:19 AM:
>>> I agree with both Adrian (a bicycle is a fixed asset of a rental
>>> company) and BJ (you provide a service on this fixed asset when you
>>> clean the bicycle, it's an asset maintenance)
>>> And also with Scott: we should really continue to discuss details on dev
>>> ML..
>>>
>>> Jacques
>>>
>>> From: "Adrian Crum"<[hidden email]>
>>>> The items for rent are fixed assets of the rental company, not
>>>> products.
>>>>
>>>> -Adrian
>>>>
>>>> On 8/30/2011 3:58 AM, Hans Bakker wrote:
>>>>> We have a requirement to rent items like tools, video's cars
>>>>> motocycles
>>>>> or other assets for a certain period of time.
>>>>>
>>>>> The items will be handed out and returned at which point a service or
>>>>> extra charge could be possible for damage.
>>>>>
>>>>> I was thinking about a product which is delivered and where an
>>>>> automated
>>>>> return authorization is assigned so the warehouse knows what is coming
>>>>> back.
>>>>>
>>>>> let me know any other ideas?
>>>>>
>>>
>>>
>

[Adrian Crum-3]

Yes, all of that works OOTB.

https://cwiki.apache.org/OFBIZ/asset-maintenance-setup.html

-Adrian

On 8/30/2011 1:32 PM, Jacques Le Roux wrote:

> Thanks for the detailled explanation Adrian,
>
> Is that already all implemented (like automatically sending an email
> to user from service depot)?
>
> Jacques
>
> From: "Adrian Crum" <[hidden email]>
>> I'm not sure what you mean by "the assetmaint entities and code
>> should be made generic" - the asset maintenance code is fairly generic.
>>
>> Asset maintenance is intended to be used to track required/scheduled
>> maintenance on fixed assets. The most common use is to maintain an
>> organization's own fixed assets, but there is no reason it can't be
>> used to track someone else's fixed assets.
>>
>> One of the features of Asset Maint is the ability to have multiple
>> fixed assets based on a single product and product maintenance
>> regime. So, a service depot that is authorized to work on Acme Model
>> B Widget would have an Acme Model B Widget product (but no inventory
>> of course), and a maintenance regime set up for the Acme Model B
>> Widget. When a customer brings in an Acme Model B Widget, a fixed
>> asset is created based on the Acme Model B Widget product and the
>> customer is made the owner of that fixed asset. The Acme Model B
>> Widget fixed asset automatically inherits the Acme Model B Widget
>> product's maintenance regime. The service depot can even set things
>> up to automatically email the customer when service is due on their
>> Acme Model B Widget.
>>
>> The party performing the service can be a depot employee or an
>> outside service. If the party or outside service is assigned to the
>> product maintenance in one of the maintenance roles, then they will
>> be automatically assigned to any maintenance work efforts for fixed
>> assets based on that product. So, let's say depot employee Trevor
>> Smith is the only employee certified to repair the Acme Model B
>> Widget. Just assign Trevor Smith to the Acme Model B Widget product
>> maintenance in one of the maintenance roles, and any time a customer
>> brings in an Acme Model B Widget for repair, Trevor will be assigned
>> to that repair automatically.
>>
>> -Adrian
>>
>>
>> On 8/30/2011 12:30 PM, BJ Freeman wrote:
>>> I responded to the Product that is a service.
>>> so the difference is this ia no longer an asset of the company but
>>> belongs now to the customer and the service is provided by the company,
>>> to the customer.
>>> like selling a car with a service contract. The contract (agreement)
>>> then determine when and what services will be provided.
>>>
>>> To stop duplication, the assetmaint entities and code should be made
>>> generic then association to support the assetmain be done. What I am
>>> addressing is the scheduling of the service to the product sold. Though
>>> in an agreement, the actual maintenance process is run by the generic
>>> service code with supporting types.
>>>
>>>
>>> Jacques Le Roux sent the following on 8/30/2011 12:19 AM:
>>>> I agree with both Adrian (a bicycle is a fixed asset of a rental
>>>> company) and BJ (you provide a service on this fixed asset when you
>>>> clean the bicycle, it's an asset maintenance)
>>>> And also with Scott: we should really continue to discuss details
>>>> on dev
>>>> ML..
>>>>
>>>> Jacques
>>>>
>>>> From: "Adrian Crum"<[hidden email]>
>>>>> The items for rent are fixed assets of the rental company, not
>>>>> products.
>>>>>
>>>>> -Adrian
>>>>>
>>>>> On 8/30/2011 3:58 AM, Hans Bakker wrote:
>>>>>> We have a requirement to rent items like tools, video's cars
>>>>>> motocycles
>>>>>> or other assets for a certain period of time.
>>>>>>
>>>>>> The items will be handed out and returned at which point a
>>>>>> service or
>>>>>> extra charge could be possible for damage.
>>>>>>
>>>>>> I was thinking about a product which is delivered and where an
>>>>>> automated
>>>>>> return authorization is assigned so the warehouse knows what is
>>>>>> coming
>>>>>> back.
>>>>>>
>>>>>> let me know any other ideas?
>>>>>>
>>>>
>>>>

[BJ Freeman]

I read you link and have gone over the code.
I don't see where the emails notices are in the data or are sent as
Jacques queried.

My view is that any tasks would be best tied to the ProjectMgr as a
global way to evaluate and manage resources Company wide.

I understand what Asset Maint does now. I was saying since there is a
new requirment for Product.productTypeId ->
ProductType.productTypeId=Service
So this would be a good time To expand to a Service commponet core code
extracted from Asset Maint, then have Asset maint use that code since it
is already doing so.

The reason is that Service as defined in Finacial and Professional
service may not have assets. Like a subscriptions that are services.
DataBk vol II page 362,320.



Adrian Crum sent the following on 8/30/2011 6:51 AM:

> Yes, all of that works OOTB.
>
> https://cwiki.apache.org/OFBIZ/asset-maintenance-setup.html
>
> -Adrian
>
> On 8/30/2011 1:32 PM, Jacques Le Roux wrote:
>> Thanks for the detailled explanation Adrian,
>>
>> Is that already all implemented (like automatically sending an email
>> to user from service depot)?
>>
>> Jacques
>>
>> From: "Adrian Crum" <[hidden email]>
>>> I'm not sure what you mean by "the assetmaint entities and code
>>> should be made generic" - the asset maintenance code is fairly generic.
>>>
>>> Asset maintenance is intended to be used to track required/scheduled
>>> maintenance on fixed assets. The most common use is to maintain an
>>> organization's own fixed assets, but there is no reason it can't be
>>> used to track someone else's fixed assets.
>>>
>>> One of the features of Asset Maint is the ability to have multiple
>>> fixed assets based on a single product and product maintenance
>>> regime. So, a service depot that is authorized to work on Acme Model
>>> B Widget would have an Acme Model B Widget product (but no inventory
>>> of course), and a maintenance regime set up for the Acme Model B
>>> Widget. When a customer brings in an Acme Model B Widget, a fixed
>>> asset is created based on the Acme Model B Widget product and the
>>> customer is made the owner of that fixed asset. The Acme Model B
>>> Widget fixed asset automatically inherits the Acme Model B Widget
>>> product's maintenance regime. The service depot can even set things
>>> up to automatically email the customer when service is due on their
>>> Acme Model B Widget.
>>>
>>> The party performing the service can be a depot employee or an
>>> outside service. If the party or outside service is assigned to the
>>> product maintenance in one of the maintenance roles, then they will
>>> be automatically assigned to any maintenance work efforts for fixed
>>> assets based on that product. So, let's say depot employee Trevor
>>> Smith is the only employee certified to repair the Acme Model B
>>> Widget. Just assign Trevor Smith to the Acme Model B Widget product
>>> maintenance in one of the maintenance roles, and any time a customer
>>> brings in an Acme Model B Widget for repair, Trevor will be assigned
>>> to that repair automatically.
>>>
>>> -Adrian
>>>
>>>
>>> On 8/30/2011 12:30 PM, BJ Freeman wrote:
>>>> I responded to the Product that is a service.
>>>> so the difference is this ia no longer an asset of the company but
>>>> belongs now to the customer and the service is provided by the company,
>>>> to the customer.
>>>> like selling a car with a service contract. The contract (agreement)
>>>> then determine when and what services will be provided.
>>>>
>>>> To stop duplication, the assetmaint entities and code should be made
>>>> generic then association to support the assetmain be done. What I am
>>>> addressing is the scheduling of the service to the product sold. Though
>>>> in an agreement, the actual maintenance process is run by the generic
>>>> service code with supporting types.
>>>>
>>>>
>>>> Jacques Le Roux sent the following on 8/30/2011 12:19 AM:
>>>>> I agree with both Adrian (a bicycle is a fixed asset of a rental
>>>>> company) and BJ (you provide a service on this fixed asset when you
>>>>> clean the bicycle, it's an asset maintenance)
>>>>> And also with Scott: we should really continue to discuss details
>>>>> on dev
>>>>> ML..
>>>>>
>>>>> Jacques
>>>>>
>>>>> From: "Adrian Crum"<[hidden email]>
>>>>>> The items for rent are fixed assets of the rental company, not
>>>>>> products.
>>>>>>
>>>>>> -Adrian
>>>>>>
>>>>>> On 8/30/2011 3:58 AM, Hans Bakker wrote:
>>>>>>> We have a requirement to rent items like tools, video's cars
>>>>>>> motocycles
>>>>>>> or other assets for a certain period of time.
>>>>>>>
>>>>>>> The items will be handed out and returned at which point a
>>>>>>> service or
>>>>>>> extra charge could be possible for damage.
>>>>>>>
>>>>>>> I was thinking about a product which is delivered and where an
>>>>>>> automated
>>>>>>> return authorization is assigned so the warehouse knows what is
>>>>>>> coming
>>>>>>> back.
>>>>>>>
>>>>>>> let me know any other ideas?
>>>>>>>
>>>>>
>>>>>
>