| Business DEX (UK_Defence051):— fleet_management | Date: 2010/03/11 10:41:38 Revision: 1.10 |
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 Templates |
|---|---|---|
| Message | This information object represents a communicated statement of events, activities, or outcomes that have happened. 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 |
| Assumption | This information object represents an assumption that has been made by a person. An assumption may be referenced from other information objects that have been developed, based on it. | UK_Defence.assumption |
| Document | This information object represents reference material that follows a formal change approval mechanism. | UK_Defence.document |
| 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. | UK_Defence.document_association |
| Fleet | This information object represents a named collection of products that are managed as a whole to meet an operational requirement. | UK_Defence.fleet |
| Fleet Capability | This information object represents the ability of a fleet component to peform a function or meet a required aim. | UK_Defence.fleet_capability |
| Fleet Component | This information object represents the relationship between a product (or group of products of the same type) and the fleet to which it is assigned, between specific dates. | UK_Defence.fleet_component |
| Organization | This information object represents an organized body, project, programme or society, which may or may not be a legal entity. | UK_Defence.organization |
| Person | This information object represents the information describing a human being. | UK_Defence.person |
| Product | This information object represents the information about physical instances of a Product Design. Individual products are typically identified by a serial number, and batches are typically identified by a batch number. Both of these would be captured by the referenced Identifier information object. | UK_Defence.product |
| Product Composition | This information object represents the composition of a Product in terms of the parent and child relationships that exist between the constituent Products. | UK_Defence.product_composition |
| Product Design | This information object represents the identification of the aggregated set of information that constitutes the detailed 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 have associated 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.
NOTE This information object is not meant to contain the detailed design information objects themselves (the goemetry, topology, dimensions, tolerances, material specification, surface finishes etc). It is meant to act as the single reference point to which all that other information relates. |
UK_Defence.product_design |
| Product Location | This information object represents a record of the geographical location of a product between specific dates. | UK_Defence.product_location |
| Product Role | This information object represents a role that a product can perform. | UK_Defence.product_role |
| Product Role Fit |
This information object represents the relationship between a named product role and the actual assemblies that constitute it. It is assumed that the relationships instantiated are in addition to the "base configuration" that is established by product composition relationships under each product. That is, if a relationship of this type is created (for example connecting a "bombing role" with a product composition relationship between a "bomb bay" and a "bomb"), the meaning is that the "bomb" is the additional item that is fitted to the "bomb bay" to change the product from the "base configuration" to the "bombing role". The "base configuration" itself could be explicitly defined using this realationship by connecting the "base configuration" to every product composition that constitutes it, but it is not anticipated that that would add significant value. |
UK_Defence.product_role_fit |
| Product Operational State | This information object represents the operational state of a product between specific dates. | UK_Defence.product_operational_state |
| Product Usage Parameter | This information object represents the record of a usage parameter that is measured during the related product usage. | UK_Defence.product_usage_parameter |
| Property | This information object represents a property that defines a functional, physical or financial aspect of the information object that it is a property of. | UK_Defence.property |
| Requirement | This information object represents a statement of need by a person or organization. | UK_Defence.requirement |
Table 2 — Business Objects to Template Mapping table
The key templates that this DEX comprises and the interrelations between those templates are illustrated below:
© UK MOD 2010 — All rights reserved