4 Information requirements

This clause specifies the information requirements for the Risk definition application module. The information requirements are specified as the Application Reference Model (ARM) of this application module.

NOTE 1  A graphical representation of the information requirements is given in Annex C.

NOTE 2  The mapping specification is specified in 5.1. It shows how the information requirements are met by using common resources and constructs defined or imported in the MIM schema of this application module.

This clause defines the information requirements to which implementations shall conform using the EXPRESS language as defined in ISO 10303-11. The following begins the Risk_definition_arm schema and identifies the necessary external references.

4.1 Required AM ARMs

The following EXPRESS interface statements specify the elements imported from the ARMs of other application modules.

EXPRESS specification:

*)
USE FROM Activity_method_assignment_arm;    --  ISO/TS 10303-1249



USE FROM Probability_distribution_arm;    --  ISO/TS 10303-1274



USE FROM Process_property_assignment_arm;    --  ISO/TS 10303-1040



USE FROM Product_relationship_arm;    --  ISO/TS 10303-1024



USE FROM Product_view_definition_relationship_arm;    --  ISO/TS 10303-1041



USE FROM Property_assignment_arm;    --  ISO/TS 10303-1030
(*



NOTE 1   The schemas referenced above are specified in the following part of ISO 10303:

Activity_method_assignment_arm	ISO/TS 10303-1249
Probability_distribution_arm	ISO/TS 10303-1274
Process_property_assignment_arm	ISO/TS 10303-1040
Product_relationship_arm	ISO/TS 10303-1024
Product_view_definition_relationship_arm	ISO/TS 10303-1041
Property_assignment_arm	ISO/TS 10303-1030

NOTE 2   See Annex C, Figures C.1, C.2, C.3and C.4 for a graphical representation of this schema.

4.2 ARM type definitions

This subclause specifies the ARM types for this application module. The ARM types and definitions are specified below.

4.2.1 risk_activity_method_item   

The risk_activity_method_item type is an extension of the activity_method_item type. It adds the data type Risk_perception to the list of alternate data types.

NOTE  The list of entity data types may be extended in application modules that use the constructs of this module.

EXPRESS specification:

*)
TYPE risk_activity_method_item = EXTENSIBLE GENERIC_ENTITY SELECT BASED_ON activity_method_item WITH
   (Risk_perception);
END_TYPE;
(*

4.2.2 risk_impact_item   

The risk_impact_item type is an extensible list of alternate data types that allows for the designation of the data types Product and Product_version.

NOTE   The list of entity data types may be extended in application modules that use the constructs of this module.

EXPRESS specification:

*)
TYPE risk_impact_item = EXTENSIBLE GENERIC_ENTITY SELECT
   (Product,
    Product_version);
END_TYPE;
(*

4.2.3 risk_perception_source_item   

The risk_perception_source_item type is an extensible list of alternate data types that allows for the designation of the data type Product.

NOTE   The list of entity data types may be extended in application modules that use the constructs of this module.

EXPRESS specification:

*)
TYPE risk_perception_source_item = EXTENSIBLE GENERIC_ENTITY SELECT
   (Product);
END_TYPE;
(*

4.2.4 risk_property_assignment_select   

The risk_property_assignment_select type is an extension of the property_assignment_select type. It adds the data type Risk_perception to the list of alternate data types.

NOTE  The list of entity data types may be extended in application modules that use the constructs of this module.

EXPRESS specification:

*)
TYPE risk_property_assignment_select = EXTENSIBLE SELECT BASED_ON property_assignment_select WITH
   (Risk_perception);
END_TYPE;
(*

4.3 ARM entity definitions

This subclause specifies the ARM entities for this module. Each ARM application entity is an atomic element that embodies a unique application concept and contains attributes specifying the data elements of the entity. The ARM entities and definitions are specified below.

4.3.1 Causal_consequence   

NOTE    A related_view is considered as an aftereffect of an immediate relating_view.

EXPRESS specification:

*)
ENTITY Causal_consequence
  SUBTYPE OF (View_definition_relationship);
  SELF\View_definition_relationship.relating_view : Risk_consequence;
  SELF\View_definition_relationship.related_view : Risk_consequence;
END_ENTITY;
(*

Attribute definitions:

relating_view: represents the more immediate consequence of the risk occuring

related_view: represents the aftereffect of the more immediate risk consequence.

4.3.2 Probability_representation   

EXPRESS specification:

*)
ENTITY Probability_representation
  SUBTYPE OF (Activity_property_representation);
  SELF\Activity_property_representation.property : Risk_event_probability;
  SELF\Activity_property_representation.rep : Probability;
END_ENTITY;
(*

Attribute definitions:

property: the attribute hold the probable event that can occur.

rep: the attribute hold the representation of the probability of the event to occur.

4.3.3 Related_consequence   

EXPRESS specification:

*)
ENTITY Related_consequence
  SUBTYPE OF (View_definition_relationship);
  SELF\View_definition_relationship.relating_view : Risk_perception;
  SELF\View_definition_relationship.related_view : Risk_consequence;
END_ENTITY;
(*

Attribute definitions:

relating_view: represents the expected consequences if the risk occurs

related_view: represents the perception of the risk that can lead to the specified consequences.

4.3.4 Risk   

NOTE 1   ISO GUIDE 73 defines "risk" as the combination of the probability of an event and its consequence. In some situations, risk is a deviation from the expected.

NOTE 2   A risk can also have a possible positive outcome. In such cases it is often referred to as an opportunity or reward.

NOTE 3   ISO/IEC Guide 51:1999 defines risk as the combination of the probability of occurance of harm and the severity of that harm.

NOTE 4   In the safety field, risk management is focused on prevention and mitigation of harm. ISO/IEC Guide 51:1999 should be used for safety aspects.

EXAMPLE 1   'Line shutdown' is an example of Risk in the context of a manufacturing system's reliability.

EXAMPLE 2   'Transportation jam-up', 'customer anger', 'collateral damage', and 'greater susceptibility to interruption of supply during crises' are all examples of Risk.

EXAMPLE 3   'Privacy' and 'security' are examples of Risk for the telecommunications industry.

EXAMPLE 4   'Fly-by-wire', the form-fit-function replacement of mechanical devices with a combination of electrical, hydraulic, and pneumatic units.

EXAMPLE 5   Timing such as 'premature rejection' and 'premature commitment' are other examples of Risk.

EXPRESS specification:

*)
ENTITY Risk
  SUBTYPE OF (Product);
END_ENTITY;
(*

4.3.5 Risk_attitude   

NOTE    A negative number for the criticality factor means risk attractive and gives a concave function if increasing, a convex if decreasing. For a risk averse utility function the criticality factor should be positive if the function is increasing, negative if decreasing utility. The converse applies for risk attractive utility functions.

EXPRESS specification:

*)
ENTITY Risk_attitude
  SUBTYPE OF (Property_representation);
  SELF\Property_definition_representation.rep RENAMED criticality_factor : Property_value_representation;
  SELF\Property_representation.property : Risk_level;
END_ENTITY;
(*

Attribute definitions:

criticality_factor: the factor that indicates whether the attitude towards a risk is risk averse or risk attractive.

property: a description of the level the risk

4.3.6 Risk_consequence   

NOTE 1   There may be one or more consequences of an event.

NOTE 2   Consequences can range from positive to negative. However, consequences are always negative for safety aspects.

NOTE 3   Consequences can be expressed qualitatively or quantitatively.

EXPRESS specification:

*)
ENTITY Risk_consequence
  SUBTYPE OF (Product_view_definition);
  SELF\Product_view_definition.defined_version : Risk_version;
END_ENTITY;
(*

Attribute definitions:

defined_version: the version of the risk this is a consequence of.

4.3.7 Risk_event   

EXPRESS specification:

*)
ENTITY Risk_event
  SUBTYPE OF (Applied_activity_method_assignment);
  SELF\Applied_activity_method_assignment.items RENAMED associated_risk : SET[1:1] OF Risk_perception;
DERIVE
  SELF\Applied_activity_method_assignment.role : STRING := 'causal event';
END_ENTITY;
(*

Attribute definitions:

associated_risk: the risk the event is assigned to

role: a constant value to specify the role of this assignment

4.3.8 Risk_event_probability   

EXPRESS specification:

*)
ENTITY Risk_event_probability
  SUBTYPE OF (Activity_property);
  SELF\Activity_property.described_element : Activity_method;
END_ENTITY;
(*

Attribute definitions:

described_element: the activity method that the probability is assigned to.

4.3.9 Risk_impact_assignment   

EXPRESS specification:

*)
ENTITY Risk_impact_assignment;
  assigned_risk_consequence : Risk_consequence;
  items : SET[1:?] OF risk_impact_item;
END_ENTITY;
(*

Attribute definitions:

assigned_risk_consequence: assignement to the consequence

items: the items impacted by this consequence

4.3.10 Risk_level   

NOTE    A Risk_level includes a Risk_attitude that helps weigh the criticality or objective of the Risk_perception

EXPRESS specification:

*)
ENTITY Risk_level
  SUBTYPE OF (Assigned_property);
  SELF\Assigned_property.described_element : Risk_perception;
END_ENTITY;
(*

Attribute definitions:

described_element: the actual Risk_perception

4.3.11 Risk_perception   

NOTE 1   There is only one probability for each perceived risk. The probability for something to happen does not vary depending on the consequences.

NOTE 2   Risk_perception depends on the stakeholder's expressed needs, issues, and knowledge.

NOTE 3   Risk_perception can differ from objective data.

NOTE 4   Risk_perception may be used qualitatively or quantitatively to form a risk matrix.

NOTE 5   Risk will be perceived differently in different contexts, such as in the context of human safety, mission success, project time schedule, performance or economy.

EXPRESS specification:

*)
ENTITY Risk_perception
  SUBTYPE OF (Product_view_definition);
  SELF\Product_view_definition.defined_version : Risk_version;
  SELF\Product_view_definition.initial_context RENAMED risk_perception_context : Risk_perception_context;
END_ENTITY;
(*

Attribute definitions:

defined_version: the version of the risk this is a perception of.

risk_perception_context: the text that provides further information about the Risk_perception. the context that forms the basis for this perception.

4.3.12 Risk_perception_context   

EXPRESS specification:

*)
ENTITY Risk_perception_context
  SUBTYPE OF (View_definition_context);
END_ENTITY;
(*

4.3.13 Risk_perception_relationship   

EXPRESS specification:

*)
ENTITY Risk_perception_relationship
  SUBTYPE OF (View_definition_relationship);
  SELF\View_definition_relationship.relating_view : Risk_perception;
  SELF\View_definition_relationship.related_view : Risk_perception;
END_ENTITY;
(*

Attribute definitions:

relating_view: the first of the instances of Risk_perception that is a part of the relationship.

related_view: the second of the instances of Risk_perception that forms the relationship.

4.3.14 Risk_perception_source_assignment   

EXPRESS specification:

*)
ENTITY Risk_perception_source_assignment;
  assigned_risk : Risk_perception;
  items : SET[1:?] OF risk_perception_source_item;
END_ENTITY;
(*

Attribute definitions:

assigned_risk: the source to be assigned to

items: the items assigned to the risk perception.

4.3.15 Risk_relationship   

EXPRESS specification:

*)
ENTITY Risk_relationship
  SUBTYPE OF (Product_relationship);
  SELF\Product_relationship.relating_product RENAMED relating_risk : Risk;
  SELF\Product_relationship.related_product RENAMED related_risk : Risk;
END_ENTITY;
(*

Attribute definitions:

relating_risk: the first of the instances of Risk that is a part of the relationship.

related_risk: the second of the instances of Risk that forms the relationship.

4.3.16 Risk_version   

NOTE 1   Use of Risk_version allows several Risk_perception to be defined to a specific Risk

EXPRESS specification:

*)
ENTITY Risk_version
  SUBTYPE OF (Product_version);
  SELF\Product_version.of_product RENAMED of_risk : Risk;
END_ENTITY;
(*

Attribute definitions:

of_risk: the version of the Risk to which this is a specified version of.

© ISO 2011 — All rights reserved