[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [plcs-dex] Assignment of Time properties - to task or person?
|
Thanks Leif,
I found several different approaches in Dex3 & task
related capabilities, but my example seems not to fit squarely into these. We
are not dealing with the actual time (as recorded) here either (yet), though I
see your point regarding the realized/actuals.
It is not possible to create a
required_resource_by_resource_item for time, as this is not defined as a
resource_item. That is, time itself, cannot be modelled as a resource on it's
own. The only mechanism appears to be through another resource_item, like
you mention, which was my clumsy way of explaining option 1. Having defined
a type_of_person representation already, I can also use the
(mandatory) type_of_person_definition to point at using the
assigned_property.described_element. As you also hinted, person &
organization etc., are also in the property assignment select type
list.
I attach 2 slides to illustrate, but I think your third way
- is my option 1.
But of course I could be missing your entire
point...
regards,
Tim
NB -
On an entirely separate note (to ALL), is there general consensus that where
quantity information is not provided for an item (e.g. resource), that by
default only a single item is inferred?
From: Gyllström Leif [mailto:leif.gyllstrom@aerotechtelub.se] Sent: 30 January 2006 03:43 To: Tim Turner; plcs-dex@lists.oasis-open.org Subject: RE: [plcs-dex] Assignment of Time properties - to task or person? Tim I'd say that you shall
use a third alternative : -
Required_resource, and
assign a property to Required resource representing planned required
time -
Resource_as_realized
and assign a property to Resource_as_realized representing actual
time Then you can use a
consistent approach regardless of whether you use a Person, Type_of_person,
Oragnization or Organization_type as
the Resource Regards Leif From: Tim Turner [mailto:tjt@lsc.co.uk]
The
time required to perform a task, by 1 (mechanic) person is 4
hours. Looking at the model, I see that it
is possible for me to represent this in one of two ways;
1.
By modelling the duration as an assigned_property of the (resource)
type_of_person_definition - i.e. 1 mechanic required for 4 hours
or, 2.
By again modelling the duration as an assigned_property, but this time
associated with the task_method_version_assignment
instance. The
fundamental question is whether the time required (duration) should be a
function of the task, or as a function of the
person. Note: this task may be assigned to
more than one item through the task_method_version_assignment. However, the time
required is for each task, thus option 2 forces each item to have it's own
task_method_version_assignment and a repetition of the duration property for
each. The alternative, option 1, assigning the duration to the resource_property
would appear to make more sense, since the duration may change if the skill
level of the person assigned changed. Is
this in agreement with other modeller views? Kind regards,
NB.
Option 2 might be used where the effort is defined in terms of each item that
the task is defined/used with. E.g. if for item a) the task takes 4 hours, but
for item b) the time is 5 hours. Option 1 appears best used if the
time is the same for all items that the task is applicable to.
************************************************************************* DISCLAIMER:
***SECURITY LABEL: NOT PROTECTIVELY MARKED*** The information in
this message is confidential and may be legally privileged. It is intended
solely for the addressee. Access to this message by anyone else is
unauthorised. If you are not the intended recipient, any disclosure,
copying, or distribution of the message, or any action or omission taken by you
in reliance on it, is prohibited and may be unlawful. Please immediately
contact the sender if you have received this message in error. This e-mail
originates from LSC Group. Registered in England & Wales No 2275471
Registered Office: Devonport Royal Dockyard, Devonport, Plymouth, PL1 4SG
DISCLAIMER: ***SECURITY LABEL: NOT PROTECTIVELY MARKED*** The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. This e-mail originates from LSC Group. Registered in England & Wales No 2275471 Registered Office: Devonport Royal Dockyard, Devonport, Plymouth, PL1 4SG
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]