Event_Consequence


[Columns] [Composed Of] [Referenced By] [Refers To]

General Information

[Next]
Name Event_Consequence
Entity Type Table
Description The consequences of an event or the potential consequences of a risk
Submodel Event
Entity Scope Project
Primary Key Id
Natural Key
Generalizations IT_Object , Tracked_Object
Specializations


Columns

[Previous] [Next] [Top]
NameValue DomainProperty /
Storage Unit
DescriptionRequired /
Default
Type
Cost double Dimensionless
Estimated cost if the risk is not managed properly or cost saving in case it has been managed properly or the actual cost if the event took place. No
NUMBER
Cost_Currency R_Currency
Code or mnemonic that identifies the currency for the cost. No
VARCHAR2(64)
Description STRING2000 NA
Textual description of the consequence associated with the risk/event. No
VARCHAR2(2000)
Event_Id Event
Reference to the event/risk for which the consequences are defined. Yes
NUMBER(38)
Existence_Kind REF_EXISTENCE_KIND NA
A reference value that describes the state of existence in the lifecycle of the entity, for example, Planned, Predicted, Required, Simulated, and Actual. Yes
Actual
VARCHAR2(64)
GUID STRING128 NA
Globally Unique IDentifier for an instance of a class. USAGE NOTES: There are two cases: 1) GUID is not populated or used; and 2) it is populated with a value that is globally unique. If the GUID is populated there are two means of doing so for a given project: 2a) Seabed automatically generates and populates the GUID when an instance is created (valid only on Oracle based systems); and 2b) the GUID is generated and populated by an application (other than Seabed) on instance creation. Whether Seabed automatically generates GUIDs for a project is determined by the Auto_GUID flag in SDS_Account. Note that techniques 2a and 2b can coexist in the same project. When GUIDs are automatically generated an application can override the automatically generated GUID with its own GUID by simply supplying the GUID value. Applications that generate their own GUIDs and populate the GUID column will function correctly on projects which have automatic GUID generation turned on. No
VARCHAR2(128)
Id ID No_Unit
Unique identifier for this entity. Yes
NUMBER(38)
Insert_Date DATE NA
Date the entity was created in the repository No
DATE
Insert_User STRING64 NA
The name of the user responsible for the creation of this entity in the repository. No
VARCHAR2(64)
Lost_Time double Time
s
Lost time if the risk is not managed properly or time saving in case it has been managed properly. No
NUMBER
Produced_By STRING64 NA
The name of application role that created the entity, for data created programmatically. No
VARCHAR2(64)
SDAT_Label int No_Unit
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. No
NUMBER(10)
Summary STRING2000 NA
Textual summary of consequence associated with the risk/event. No
VARCHAR2(2000)
Update_Date DATE NA
Date of the most-recent modification to the entity. No
DATE
Update_User STRING64 NA
The name of the user responsible for the last modification to this entity. No
VARCHAR2(64)
Version STRING255 NA
The form or variant of the entity. Yes
1
VARCHAR2(255)


Refers To

[Previous] [Next] [Top]
LinkTo EntityDescriptionImplementation TechniqueRequired
Cost_Currency R_Currency Code or mnemonic that identifies the currency for the cost. Restrict No
Event Event Reference to the event/risk for which the consequences are defined. Cascade Yes


[Seabed Objects] [Entities in Schema Seabed] [Index]

Copyright © 2018 Schlumberger. All rights reserved.