task_description

Information requirement	Business Object(s)
Information that is used to define the message that performs the transmission of the task description information between the source and destination UK_Defence processes.	Message, Record.
The identification, naming, versioning and status of the task.	Task, Status Assignment.
The description of how the task shall be performed, including reference to legal, health and safety advisories.	Task, Document, Document Association.
The representation of the decomposition of the task into sub-tasks.	Task, Task Composition.
The representation of the sequence / precedence constraints between sub-tasks.	Task, Task Dependency.
The justification for the existence of a task, such as to prevent or to rectify a failure, to implement a change, to comply with a requirement or to rectify a health hazard.	Task, Justification, Failure Type, Failure_type_condition,Requirement, Health Hazard (note this maps to Risk, not in PLCS ed1), Change Impact.
The specification of when the task should be executed, such as a planned maintenance interval/usage limit being reached, or a condition or failure being observed.	Task.
Identification of the resources required to execute the task, including material resources (spares, test equipment etc), skills, personnel, facilities, utilities and related information resources such as drawings, documents or procedures.	Task, Resource Requirement, Facility Type, Utility Type, Product Specification, Product Design, Skill, Trade, Document.
Identification of the product to which the task applies.	Task, Maintenance Task, Product Design.
Identification of intended support levels at which the task may be performed, such as on equipment, on bench, at a maintenance depot.	Task, Maintenance Task, Line of Maintenance.
Identification of the depth of maintenance that the task is classified as.	Task, Maintenance Task, Depth of maintenance.
Specification of the required state of the product prior to task execution.	Task, Maintenance Task, Product Design.
Specification of the expected result of performing the task, such as the state of the product.	Task.
Specification of the reporting requirement after the execution of the task, such as reporting on new product configuration, repair time, resources used and consumed.	Task.
Reference to the context (deployment environment and support concept) for which the task specification was developed and to which it applies.	Task, Maintenance Task, Product Design, Deployment Environment, Support Concept.

In terms of business objects, these information requirements are modelled as shown below in Figure 1.

NOTE For clarity, not all of the dependent business objects - those that will make the model referentially complete - have been included on the diagram.

NOTE This business object has been updated (below), but the templates and mapping have yet to be revised (will be a future task).

task_description Business Information Requirements