Maintenance Plan

Provides for the capture of all information that defines the maintenance plan.
For technical detail, refer to fp_control_maintenance_plan.
All of the following information can be asserted through the functional part but is identified in sub-groups for convenience.

Task

	Set the globally unique identifier and owner history for the task. These should be handled directly by the software application and should not require action by the user.
	Specify a name for the task that can be used as its representation in a plan or schedule.
	Set the value of the task identifier. This is locally unique (within the maintenance plan), that may be used as a sequence number in a list of tasks 1,2,3,4 etc. or as work breakdown structure identifier.
	Identify if the task is a milestone. Although this value must be asserted, it is not relevant to the maintenance plan. To ensure that it is not taken into consideration, it must be asserted as FALSE for a maintenance plan.
X	The status of a task MUST NOT be used in a maintenance plan.
X	The method of work for a task MUST NOT be used in a maintenance plan.
X	The relative priority of a task MUST NOT be used in a maintenance plan.

Plan Period

	Set the unit time measure to be applied to the period between occurrences of tasks in the workplan e.g. the time measure for lubrication might be 'monthly'.
	Set the number of units of the time measure that specifies the period between recurring occurrences of the task e.g. '2' for 2 months.

Asset-Task Assignment

The asset(s) to which tasks are to be assigned are already identified through the preconditions for this exchange requirement.

	Select the asset(s) to which the task is to be assigned.
	Select the tasks that are to be assigned to the asset.
	Set the globally unique identifier and owner history for the relationship between the asset(s) and the task. These should be handled directly by the software application and should not require action by the user.
	Specify a name that can be used to identify the asset-task relationship. For example 'Change filter in AHU1' gives the task and the name of the asset on which it is carried out.
X	The quantity of the an object specific for the operation by this task MUST NOT be used in a maintenance plan.

WorkPlan

	Set the globally unique identifier and owner history for the work plan. These should be handled directly by the software application and should not require action by the user.
	Specify a name for the work plan that provides a 'human' readable identification.
	Set the value of the work plan identifier. This may be used in for 'human' readable identification in conjunction with the name.
	Set the date on which the work plan was created or modified.
	Set the name of the authors of the work plan.
	Decide if the work control type is baseline, planned or actual (or some other user defined value in which case, the user defined value must also be specified).
X	The total duration of the entire work schedule MUST NOT be used in a maintenance plan.
X	The total time float of the entire work schedule MUST NOT be used in a maintenance plan.
X	The start time of the schedule MUST NOT be used in a maintenance plan.
X	The finish time of the schedule MUST NOT be used in a maintenance plan.

WorkPlan -Task Assignment

	Select the work plan to which the tasks are to be assigned.
	Select the tasks that are to be assigned to the work plan.
	Set the particular type of the work plan/task assignment relationship which must be PROCESS.
	Set the globally unique identifier and owner history for the relationship between the work plan and the tasks. These should be handled directly by the software application and should not require action by the user.
	Specify a name that can be used to identify the work plan-task relationship.
X	The time related information for the task MUST NOT be used in a maintenance plan.