DEX (D003):— task_set Date: 2008/03/11 17:07:00
Revision: 1.67
CoverContentsAbstractIntro.TermsScope239 AAMBusiness overviewBus. info. overviewBus. info. reqs.239 rep.TemplatesSchemasRef. dataConformanceBiblio.Issues

Issue raised against: task_set

OTHER issues

Closed issue Issue: RBN-1 by Rob Bodington (05-11-30) minor_technical issue
Resolution: Accept. Status: closed

Following the recent TOG meeting where we reviewed the capabilities required by the DEXs, - I have added the following capabilities to the Fault state DEX: assigning_approvals assigning_codes assigning_date_time assigning_descriptor assigning_effectivity assigning_identifiers assigning_organization assigning_process_properties assigning_product_properties assigning_reference_data assigning_resource_properties messaging referencing_contract referencing_documents referencing_part_or_slot referencing_person_organization referencing_person_organization_typical referencing_product_breakdown_element referencing_product_configuration referencing_project referencing_resource referencing_task representing_condition representing_environment_typical representing_information_controls representing_justification representing_life_cycle_opportunity representing_location representing_periodicity representing_person_organization_typical representing_probability representing_properties_numerically representing_properties_textually representing_property_value_ranges representing_resource representing_state_type representing_task representing_task_and_state

Closed issue Issue: RBN-2 by Rob Bodington (07-04-10) minor_technical issue
Resolution: Accept. Status: closed

Figure 3 in the section "Task identification and versioning" shows the Task_method_version being identified by the template "assigning_identification_with_no_organization" - I would have expected the template "assigning_identification" to be used. We have previously agreed that ALL identification should be in the context of an organization - apart from an organization.
Comment: (Leif Gyllstrom 2008-03-05)
Corrected.

Closed issue Issue: RBN-3 by Rob Bodington (07-04-10) minor_technical issue
Resolution: Accept. Status: closed

It is not clear what the section "Effectivity domain representation" is representing. The introductory text needs more examples and explanation.
Comment: (Leif Gyllstrom 2008-03-05)
Entire DEX structure has been revised.

Closed issue Issue: RBN-4 by Rob Bodington (07-04-10) minor_technical issue
Resolution: Accept. Status: closed

Figure 35 "How to represent a scheduled periodicity" in the Task trigger section shows one have of the trigger. I would have expected to see the property on the Part that is being compared to the independent property in order to trigger the task. E.g. if I want the task to be done on a part after 10 flying hours, I can represent 10 flying hours as the independent property. I would expect the trigger to be "if independent property flying hours = part property flying hours" then do the task.
Comment: (Leif Gyllstrom 2008-03-05)
Current representation is agreed within the PLCS Core Team, and is harmonized between the Task Set DEX and the Aviation Maintenance DEX.