| Business DEX (UK_Defence054):— risk_management | Date: 2010/03/14 11:21:11 Revision: 1.11 |
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 |
| Activity | This information object represents an actual activity that is performed on specific dates. The method for carrying out an activity may be defined by a related task definition. | UK_Defence.activity |
| 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 |
| Event | This information object represents an unexpected event, or happening, at a point in time. | UK_Defence.event |
| Event Type | This information object represents a type of event that may occur. | UK_Defence.event_type |
| Plan | This information object represents a scheme or method of acting, doing, proceeding or making, developed in advance. It may include the logic through which tasks are combined or otherwise related, their sequence and their resource requirements. | UK_Defence.plan |
| Platform System Equipment | This information object represents the identification of a set of one or more items that will be the subject of support concept and support solution development activities. Each item is identified by a related platform system equipment constituent object. Items may be identified by part number, NSN or serial number. Items may include whole platforms, test systems, training equipments, or cross-platform equipment such as communications systems, pumps, engines and so on. | UK_Defence.platform_system_equipment |
| Platform System Equipment Constituent | This information object represents the relationship between an identified platform system equipment, and an item that forms a part of it. | UK_Defence.platform_system_equipment_constituent |
| 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 Event | This information object represents and event that happens to a product. | UK_Defence.product_event |
| Product Event Type | This information object represents a type of event that may happen to a PSE constituent. | UK_Defence.product_event_type |
| 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 Event Type | This information object represents a type of event that may happen to a PSE constituent. | UK_Defence.product_event_type |
| Required PSE Constituent Usage Phase | This information object represents the definition of a usage phase of a PSE constituent. | UK_Defence.required_pse_constituent_usage_phase |
| Risk | This information object represents the definition of a chance or possibility of danger, injury to personnel, or loss of capability that has serious operational and/or financial consequences. | UK_Defence.risk |
| Risk Composition | This information object represent the relationship between parent and child risks in a risk decomposition hierarchy. | UK_Defence.risk_composition |
| Risk Management Feedback | This information object represents feedback that originates from risk management activities. | UK_Defence.risk_management_feedback |
| Risk Mitigation | This information object represents feedback that originates from risk management activities. | UK_Defence.risk_mitigation |
| Risk Realization | This information object represent the record of the realization of an anticipated risk through the occurrence of an event. | UK_Defence.risk_register |
| Risk Register | This information object represents the register of risks that has been created for a specified platform, system and equipment. | UK_Defence.risk_register |
| Schedule | This information object represents the scheduling of activities on specific dates. The referenced activities may be decomposed or sequenced using activity_composition and activity_dependency objects. A schedule may be derived from a Task, Task List or Plan. | UK_Defence.schedule |
| Security Classification Assignment | This information object represents the assignment of a security classification to a subject. | UK_Defence.security_classification_assignment |
| 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 |
| Support Concept | This information object represents a support concept which is defined to be the combination of:
|
UK_Defence.support_concept |
| Support Solution Definition | This information object represents the results of analysing the support need for the related platform, system and equipment, in terms of the planned tasks that are required to support it through life. | UK_Defence.support_solution_definition |
| 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
NOTE This DEX is dependent on entities in the ISO10303-239 Edition 2 schema.
The key templates that this DEX comprises and the interrelations between those templates are illustrated below:
© UK MOD 2010 — All rights reserved