| Capability (C052):— representing_resource |
Date: 2012/05/23 17:37:04
Revision: 1.39
|
Issue raised against: representing_resource
Issue:
TJT-1 by Tim Turner (2006-4-16) minor_technical issue
Resolution: Accept. Status: open
The capability describes a usage of an applied_activity_method_assignment (AAMA), which seems to reverse current thinking
- I agree with GLY-1.
The use of AAMA is also apparently not in scope for this capability given that this entity is not included in the usage section.
AAMA also does not appear on any of the figures or examples.
Nor is the AAMA listed in any dependant capabilities.
Issue:
TJT-2 by Tim Turner (2006-4-16) minor_technical issue
Resolution: Accept. Status: open
The capability does not describe the usage of a resource_item_assignment (RIA) which is present on Fig 1
The use of AAMA is also apparantly not in scope for this capability given that this entity is not included in the usage section.
AAMA also does not appear on any of the figures or examples.
Issue:
TJT-3 by Tim Turner (2006-4-16) minor_technical issue
Resolution: Accept. Status: open
Some of the figures still refer to Task which is an entity of the DIS model and now no longer used/available in the IS version
of AP239. Same for task_assignment - please remove. The text also needs to be updated to reflect the IS model.
Issue:
TJT-4 by Tim Turner (2006-4-16) minor_technical issue
Resolution: Accept. Status: open
Some references to entities still not using entity-refs e.g. under fig2
Issue:
TJT-5 by Tim Turner (2006-4-16) minor_technical issue
Resolution: Accept. Status: open
I did not think we should list the entities of a select_type list in a capabilility since when the capability is used within
a DEX, some of those items listed may no longer be in scope. Hence they will not be available but the documentation which
includes the capability will still make reference to them which wil be misleading. E.g. Fig1, list under fig 1, under fig2,
and under fig4. Some of these lists are also out of date or incorrect - e.g. 2 items missing from list under fig1 product_as_individual_version
and _view; 3 misisng from under fig2; under fig5 only 5 out of 12 are correct.
Issue:
TJT-5i by Tim Turner (2006-4-16) minor_technical issue
Resolution: Accept. Status: open
Some of the entities of the select_type lists are also out of date or incorrect - e.g. 2 items missing from list under fig1
(product_as_individual_version and _view); 3 missing from under fig2; under fig5 only 5 out of 12 are correct.
Issue:
TJT-6 by Tim Turner (2006-4-16) minor_technical issue
Resolution: Accept. Status: open
A number of items of reference data seem no longer available and get reported as errors in the capability. It is not clear
if these are actually errors in referencing or whether the reference data has been removed for other reasons. When reference
data gets removed, it can look ugly. Clarify usage of ref data apparently missing.
Issue:
TJT-7 by Tim Turner (2006-4-16) minor_technical issue
Resolution: Accept. Status: open
A number of items of reference data seem to read more like step entities than reference data. E.g. Resource_group_association_relationship,
Locating_resource_item_assignment etc.. These may well be there as stubs to be further specialised into more readily understandable
concepts, but then they should state that. E.g. this is a generic class and narrower contexts may be provided through sub-classes.
e.g. Resource_location maybe a sub-class of Locating_resource_item_assignment.
Issue:
TJT-8 by Tim Turner (2006-4-16) minor_technical issue
Resolution: Accept. Status: open
Templates are required for assigning_required_resource_item and assigning_specified_resource_item, others are possible but
probably not necessary (e.g the resource_item_relationship / assignment. Templates should be shown for the different types
of characterizations.
Issue:
TJT-9 by Tim Turner (2006-4-16) minor_technical issue
Resolution: Accept. Status: open
The text mentions the use of .description attribute to record info/details in places. Ensure that all description info is
provided through assigning_descriptor.
Issue:
TJT-10 by Tim Turner (2006-4-16) minor_technical issue
Resolution: Accept. Status: open
The characterizations of resources should include some indication of the different types of reference data needed when using
them in relation to each resource concept applicable.
Issue:
TJT-11 by Tim Turner (2006-4-16) minor_technical issue
Resolution: Accept. Status: open
The statement "An instance diagram showing the assignment of a classification to an Resource_item is given in Figure 5" is
incorrect.
Issue:
TJT-12 by Tim Turner (2006-4-16) minor_technical issue
Resolution: Accept. Status: open
Fig2 - and corresponding text: it is important to state that the quantity refers to the related resource_item and not the
relating.
I don't know if the example provided in the text for Fig2 is appropriate as the capacity of a tank should (ideally?) be reported
using a resource_property(?!) assuming this is meant to be a resource item group (maybe re-word to contains 2000litres). Reference
is made to a resource_event_relationship but this is not in scope or defined or dependant or related. The relationship needs
to be between 2 or more items in the same contextual role. A resource_item_relationship could infer alternative/substitute
resource_items. In my opinion, a group relationship should be classified on the basis of what is being grouped. For instance,
the toolbox and hammer should be classified as (something like) a type of physical_resource_grouping; the facility and compressed
air should be classified as a type of functional_resource_grouping. Other ref data looks good.
Issue:
SB/LG-DEX3-1 by Sean Barker (2005-9-19) minor_technical issue
Resolution: Accept. Status: open
Replace required quantity with property, which may then be classified as (calculation, estimate, management-decision, measured),
and allow for alternate quantities.
Issue:
GYL-1 by Leif Gyllstrom (2005-11-07) minor_technical issue
Resolution: Accept. Status: open
The capability contains the following recommendations.
-
"if, in order to use a resource, it has to be prepared in some way,
then the preparation task is specified by a Required_resource_assignment
in the role of "Resource preparation";
- if a resource is needed in the performance of a task,
then Applied_activity_method_assignment is used in the role of
"Required resource" and points to the appropriate subtype of Required_resource;
Actually, the intentions in writing the module was to use Required_resource_assignment to assign
required resources to a task/activity/... and to use Applied_activity_method_assignment/Task_method_assignment/...
to represent Tasks/Activities that is to executed on the resource.
Issue:
DNV-34 by Sylvia Schwab on behalf of DNV (07-03-07) major_technical issue
Resolution: Accept. Status: open
A template is needed to represent required resource, e.g. for a Task.
Proposal: Add NEW template, representing_required_resource (rep_req_src), containing Required_resource_assignment with classification,
Required_resource_by_resource_item with classification and Value_with_unit with unit, and Resource_item with identifier and
optional classification.
Issue:
DNV-35 by Sylvia Schwab on behalf of DNV (07-03-07) major_technical issue
Resolution: Accept. Status: open
A template is needed to represent resource item groups , e.g. number of resource items in a stock.
Proposal: Add NEW template, representing_resource_item_group (rep_src_it_grp), containing Resource_item_assignment with classification,
Resource_item with classification and reference to a resource_item_select, and Resource_group_relationship with classification
and a Value_with_unit
with classification and unit. When used as part of a business object, the Resource_group_relationship will reference a Resource_item
that is part of the template representing_required_resource (rep_req_src).
Comment:
(Leif Gyllstrom 2007-05-04)
Resources in stock shall be represented as a Managed_resource and not Resource_group. Resource_groups are ment to
be used for representing tool kits etc.
Issue:
RBN-2 by Rob Bodington (07-08-09) minor_technical issue
Resolution: Accept. Status: open
Move template representing_required_resource
representing_resource_item_group to NDLO/templates
Issue:
RBN-3 by Rob Bodington (2008-02-26) minor_technical issue
Resolution: Accept. Status: open
Do we really need two templates:
representing_resource_item_realization
representing_resource_item.
Issue:
RBN-1 by Rob Bodington (05-01-12) minor_technical issue
Resolution: Accept. Status: closed
You should use express_ref to hyper links to the entities.
Comment:
(Mike Ward 2004-03-21)
All express and capability refs changed to hyperlinks.