http://ofbiz.116.s1.nabble.com/Users-Requirement-WorkEffort-request-for-comment-tp139587p139593.html
>You might want to search back a bit to discussions I've had with David.
>His opinion was that CustRequest should be used to record these things,
>instead of Requirement.
>
>Si
>
>Charles Johnson wrote:
>
>
>>Silverston, on p.186 states:
>>
>>"A WORK REQUIREMENT and a WORK EFFORT are two different but related
>>entities. A work requirement represents the need to perform some type of
>>work. This could be a requirement stemming from a decision to
>>manufacture inventory items, deliver services, conduct a project or
>>repair an asset of the enterprise such as a piece of equipment or a
>>piece of software.
>> A work effort is the fulfillment of the work requirement"
>>
>>
>>As far as i can see, there doesn't so far seem to be much relating of
>>Requirement and WorkEffort two going on, particularly in the context of
>>*internal* requirements. Is this by accident or by design?
>>
>>Consider the matter of sending emails:
>>
>>Each email that's sent from the office is not in itself, i think, a work
>>effort but should be related to some other work effort. This work effort
>>in turn relates to some requirement. In practice, is it not the case
>>that every email should be recorded as a communication event?
>>What facilities are there to ensure that *incoming* mail is so related
>>where appropriate?
>>
>>There must be others who have examined these issues and considered them
>>in light of best commercial practice and i'd be interested in commentary
>>on this.
>>
>>CJ
>>
>>_______________________________________________
>>Users mailing list
>>
[hidden email]
>>
http://lists.ofbiz.org/mailman/listinfo/users>>
>>
>>
>>
>>
>
>
>_______________________________________________
>Users mailing list
>
[hidden email]
>
http://lists.ofbiz.org/mailman/listinfo/users>
>
>
>
Thanks Si. Please see my reply to David on this one