| Business DEX (UK_Defence039):— platform_system_equipment_behaviour | Date: 2010/03/12 11:54:12 Revision: 1.15 |
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. A diagramtic representation of
the AP239 templates used is shown below in Figure 2.
Please note that to improve understanding of the diagram, not all of the templates referenced in the table are shown.
|
Business Object |
Business Object Definition |
Business Templates |
|---|---|---|
| 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 |
| Failure Type | This information object represents information about the predicted failures that may occur to a type of item.
Failure is defined to be a state or condition of an item that renders it incapable of performing a required function. |
UK_Defence.failure_type and UK_Defence.failure_type_condition |
| Failure Type Consequence | This information object represents the consequence of a failure type, including the probability that the consequence will result. | UK_Defence.failure_type_consequence |
| Failure Type Consequence Criticality | This information object represents the criticality of the related failure type consequence. | UK_Defence.failure_type_consequence_criticality |
| Failure Type During Usage | This information object represents the probability of a specific failure type occurring during an associated failure context. | UK_Defence.failure_type_during_usage |
| Failure Type Relationship | This information object represents the relationship between two failure types, one of which is the causal failure type, the other being the consequential failure type. | UK_Defence.failure_type_relationship |
| FMECA | This information object represents a support analysis that is a Failure Mode, Effects and Criticality Analysis (FMECA) of the related PSE constituent. | UK_Defence.fmeca |
| Function | This information object represent a function of a product. | UK_Defence.function |
| Functional Breakdown | This information object represents the hierarchical structure of functions of the product. | UK_Defence.functional_breakdown |
| 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 |
| Mission Type | This information object represents an operational task that needs to be performed. | UK_Defence.mission_type |
| Physical Breakdown | This information object represents the hierarchical structure of physical components of a product. | UK_Defence.physical_breakdown |
| Physical Breakdown Item | This information object represents the identification of, and the reference to, a physical components in a breakdown. | UK_Defence.physical_breakdown_item |
| Platform System Equipment | This information object describes how to represent the UK_Defence concept of a platform, system and its equipment in terms of PLCS model elements. | UK_Defence.platform_system_equipment |
| Platform System Equipment Behaviour | This information object represents the collection of information that defines the predicted behaviour of the platform, system
and equipment constituents that are referenced by the related FMECA object, which in turn are defined in terms of:
- The anticipated failures, failure modes, their expected probabilities, frequencies of occurrence and effects. - The consequences of expected failures and failure modes. |
UK_Defence.platform_system_equipment_behaviour |
| Platform System Equipment Constituent | This information object describes how to represent the UK_Defence concept of the constituents of a platform, system and its equipment in terms of PLCS model elements. | UK_Defence.platform_system_equipment_constituent |
| Product | This information object represents the information about a physical instance of a Product Design, with individual products are typically identified by a serial number. | UK_Defence.product |
| Product Design | This information object represents the information about a Product Design. | UK_Defence.product_design |
| Product Specification | This information object represents the information about a Product Specification. | UK_Defence.product_specification |
| Record | This information object represents a permanent statement for preserving the memory or knowledge of facts, activities or events. | UK_Defence.record |
| Required PSE Constituent Usage Phase | This information object represents the relationship between an identified platform system equipment, and an item that forms a part of it. | UK_Defence.required_pse_constituent_usage_phase |
| Required PSE Constituent Usage Role | This information object represents the relationship between an identified platform system equipment, and an item that forms a part of it. | UK_Defence.required_pse_constituent_usage_role and UK_Defence.conditional_availability |
| Status Assignment | This information object represents the record of the assignment of a status to a subject. | UK_Defence.status_assignment |
| Support Analysis | This information object represents the record of an analysis process having been conducted.
Subtypes of this object type record specific types of analyses. The results of each support analysis are recorded by means of relationships from the information objects that are generated by the analysis and the support analysis object itself |
UK_Defence.fmeca |
| 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 |
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