plan

Information requirement	Business Object(s)
Information that is used to define the message that performs the transmission of the plan information between the source and destination UK_Defence processes.	Message, Record.
The identification, naming, versioning and status of the plan.	Plan, Status Assignment.
The plan type.	Plan.
The dates defining the effectivity of the plan.	Plan.
The justification for the existence of the plan, such as to prevent or to rectify a failure, to implement a change, to comply with a requirement or to rectify a health hazard.	Plan, Justification, Failure Type, Requirement, Health Hazard, Change Impact.
The purpose of the plan.	Plan.
The context for which a plan was developed and to which it applies.	Plan.
The identification, naming, versioning and status of the tasks within the plan.	Plan, Task, Status Assignment.
The description of how each task shall be performed, including reference to legal, health and safety advisories.	Task, Document, Document Association.
The representation of the decomposition of the plan into tasks and the tasks into sub tasks.	Plan, Task, Task Composition.
The representation of the sequence / precedence constraints between tasks and sub tasks.	Task, Task Dependency.
The justification for the existence of each 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, Requirement, Health Hazard, Change Impact.
The specification of when each 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 product to which each task applies.	Task, Maintenance Task, Product Design.
Identification of the 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 each task, such as the state of the product.	Task.
Specification of the reporting requirement after the execution of each 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 each task specification was developed and to which it applies.	Task, Maintenance Task, Product Design, Deployment Environment, Support Concept.
Identification of the resources required to execute the plan, including material resources (spares, test equipment etc), skills, personnel, facilities, utilities and related information resources such as drawings, documents or procedures. Resources may be required to execute the individual tasks or they may be rationalized and applicable to the plan as a whole.	Plan, Task, Resource Requirement, Facility Type, Utility Type, Product Specification, Product Design, Skill, Trade, Document.

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.

plan Business Information Requirements