Template:— assigning_activity_method (asg_act_meth)
Context:— NDLO
Date: 2007/09/28 12:44:03
Revision: 1.2

Issue raised against: assigning_activity_method

GENERAL issues


Open issue Issue: PBM-1 by Peter Bergström (2007-05-21) major_technical issue
Resolution: Accept. Status: open

This template seems to be a business specific template, that could be instantiated using the following existing templates: assigning_activity, representing_planned_activity, and representing_typical_activity.
When analysing how to work with Activity and Activity_method I have understood that the combination of them is complex, depending on for what purpose they exist. It is a difference between corrective maintenance (both previous identified and unforeseen), preventive maintenance, product usage, and design engineering change. There might be a need for this type of larger templates, where the entity instances are combined in order to achieve a specific result (such as preventive maintenance), but I believe we need more real world examples from projects in order to do that right.
Suggest it be moved to the business DEX area, or removed.