[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [plcs-dex] RE:
Hi Les Have you looked at the “representing_activity” capability? It should explain this – if not could you raise some review comments.
Regards ------------------------------------------- -----Original Message-----
1) Most of the examples seem to be properties: a) Name the property ("measured pressure") b) represent the property - have fun with representation, representation item, representation context, value with global units. There is a capability for representing properties. As an example of how to make things up at the representation level, you could do better than look at probability and probability distribution, but I couldn't say where.
NB: I'm not sure how PLCS should go about defining properties, since agreeing the representation of a properties goes beyond simply recording the property name as reference data, but requires the representation model to be defined.
2) Work out what it is being assigned to, and use the appropriate assignment (things, processes and resources have different assignment models, for various reasons).
3) Each measurement must be the result of an activity_actual (see activity_as_realized module) related to the defining activity by an activity_happening. Complex activities structures can be constructed through the activity_relationship.
4) An activity can use a task to describe activity_method - note task is always a definition - the assertion that a task was done is made by using the task as the method of an activity_actual. A product_as_individual may be assigned to the task through a task_assignment, however, since a task is a definition, it would be a moot point whether this holds the semantics that the task was done on this item. Better to use an activity_method_assignment with an appropriately named role.
5) The measured item, if it is indeed an item, can be asserted also by an activity_method_assignment with appropriately named role (don't forget to add the role into reference data). If no such item exists - that is, it is not predefined in the standard product structure, then you will need to define it through one of the breakdowns.
Therefore I guess that you don't need any extra entities. I hope this helps.
Sean Barker
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]