Business DEX (UK_Defence021):— task_description | Date: 2009/04/16 21:06:37 Revision: 1.5 |
The business objects introduced in the Business Information Overview section are modelled in PLCS through a set of business templates. Most business templates are based upon one or more generic PLCS templates. They may be specializations of a PLCS template using one or more classifications or characterizations to capture the required information, whilst some rename and use restricted parameters.
This section summarizes the mappings of the business objects to the corresponding templates.
Business Object |
Business Object Definition |
Business Template(s) |
---|---|---|
Message | This information object represents a communication of the Configuration Management Breakdown. The method by which the message is communicated is various. | UK_Defence.message |
Record | This information object represents a permanent statement for preserving the memory or knowledge of facts, activities or events. | UK_Defence.record |
Task | This information object represents a type of task that requires to be done. A task may actually be executed one or more times and recorded as an activity. | UK_Defence.task |
Task Dependency | This information object represents the relationship between a task and a predecessor task that must be completed, before the task can be started. | UK_Defence.task_dependency |
Task Composition | This information object represent the relationship between parent and child tasks in a task decomposition hierarchy. | UK_Defence.task_composition |
Maintenance Task | This information object represents a task that is required to be performed on a type of product. | UK_Defence.maintenance_task |
Product Design | This information object represents the aggregated set of information that constitutes the design of a product. Product designs can be of any "level" of product, from individual nuts and bolts, up to complete equipments, systems and platforms. Product designs are typically identified by a design authority part number, and when fully specified, will have a detailed drawing/product model associated with them that contain the level of detail that enables instances of the physical elements of the design to be manufactured and/or assembled. Those physical elements will be fully specified by their own Product Design. Product designs will typically also contain performance specifications, physical characteristcs (such as dimensions, weight and material specifications), and other charateristics such as cost. Prior to this level of detail being defined, the product design process may involve specification of functions, conceptual physical design/general layout design and identification of spatial zones within the design. | UK_Defence.product_design |
Deployment Environment | This information object represents the usage profile of a Product (Platforms, Systems and Equipment) by a specific operating organization. A separate Support Context exists for each combination of Product, usage profile, and operating organization. The relevant characteristics of a Support Context (pka Deployment Environment) might include: - temperature ranges, - altitude, - humidity, - wind conditions, - dust, - ice, - snow etc. | UK_Defence.support_context |
Support Concept |
A support concept is the combination of: i. Identification of the contracting strategies to be applied or explored for any aspect of support (e.g. SOM options). ii. Guidance on the lines and levels of maintenance that should be explored or applied to any specific elements of the Platform, System or Equipment (PSE) requiring support . iii. The initial specification of the supportability, cost and readiness metrics that will be used to assess the design of the support solution and the performance of the support system when it becomes operational. |
UK_Defence.support_concept |
Line of Maintenance | This information object represents a defined maintenance line for the related item. | UK_Defence.line_of_maintenance |
Depth of Maintenance | This information object represents the defined level of complexity for the maintenance and repair of unserviceable or damaged product. | UK_Defence.depth_of_maintenance |
Document | This information object represents reference material that follows a formal change approval mechanism. |
UK_Defence.document
and UK_Defence.related_documents |
Document Association | This information object represents the association of a Document with another information object. Example uses of this may be to associate policy or standards documents with Task objects or to associate drawings with Product Design objects. | |
Status Assignment | This information object represents the record of the assignment of a status to a subject. This can be used for example to assign approvals to documents, status to deliveries, or dispositions to design changes (requested, proposed, authorized etc). | UK_Defence.status_assignment |
Justification | This information object represents a justification for a decision or for something having been done. | UK_Defence.justification |
Resource Requirement | This information object represents the identification and quantification of a resource that is needed to perform an individual task or list of tasks. | UK_Defence.resource_requirement |
© UK MOD 2010 — All rights reserved