STATE OBSERVED Capability

["Barker, Sean (UK)" <sean.barker@baesystems.com>]

Rob,

As I read it, the current state_observed capability is restricted to being a state of something, such as a product. I would like to use it to track the lifecycle of Task. In the case of lifecycle, a Task is in the given state by assertion (usually by approval), rather than observation. Should State_observed be updated to cover this case?

Also, I have the following observations:
1) It is ambiguous from the capability whether every state_observed must be the assertion of some state_definition. Can there be observed states for which there is no defined state?
2) When applying identification to state, what is the reference data that ensures the identifier is interpreted as a state_identifier. What does this state identifier mean?
3) There are currently no part 21 fragments for several of the instance diagrams - is this intended?

Sean Barker
ATC Filton
0117 302 8184

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************