| Name | WCS_Inspection |
|---|---|
| Entity Type | Table |
| Description | Safety Inspection of well control system (WCS) including BOPs. |
| Submodel | WS_Activity |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | |
| Generalizations | Wellsite_Activity , Activity , Entity , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Activity_Program_Id | Activity_Program |
|
Reference to the program during which the activity was performed. | No |
NUMBER(38) |
| Activity_State | STRING64 | NA |
The current state, or status, of the activity. Activity state is a refinement of the lifecycle indicator Existence_Kind. For example, a drilling job whose Existence_Kind is "Actual" could have an activity state of "turning to the right", "suspended due to weather", or "tool makeup or breakdown". An activity whose Existence_Kind is "Required" could have State values like "under investigation", "proposed" and "AFE approved". Note: The valid list of activity states will vary from one kind of activity to another, so the values entered into this column are not validated via a lookup table. | No |
VARCHAR2(64) |
| Activity_Template_Id | Activity_Template |
|
The identifier of the activity template which activates or characterizes the Activity. | No |
NUMBER(38) |
| BOP_Annular_Pressure | double | Pressure kPa |
Pressure to which Annular BOP was successfully tested | No |
NUMBER |
| BOP_Connector_Test_Flag | boolean | NA |
A flag to indicate whether or not BOP Connector Function Tested | No |
NUMBER(1) |
| BOP_Function_Test_Date | DATE | NA |
Date and Time when BOP was last Function Tested | No |
DATE |
| BOP_Next_Test_Date | DATE | NA |
Date of the next scheduled BOP test | No |
DATE |
| BOP_Pods_Test_Flag | boolean | NA |
A flag to indicate whether or not BOP Pods Function Tested | No |
NUMBER(1) |
| BOP_Pressure_Test_Date | DATE | NA |
Date of last BOP test | No |
DATE |
| BOP_Ram_Test_Pressure | double | Pressure kPa |
Pressure to which the BOP Rams were successfully tested | No |
NUMBER |
| Choke_Line_Test_Press | double | Pressure kPa |
Pressure to which Choke Line was successfully tested | No |
NUMBER |
| Choke_Manifold_Test_Press | double | Pressure kPa |
Pressure to which Choke Manifold was successfully tested | No |
NUMBER |
| Diverter_Test_Pressure | double | Pressure kPa |
Pressure to which Diverter was successfully tested | No |
NUMBER |
| Duration | double | Time s |
The duration of the activity. For planned activities, this would be expected duration. | No |
NUMBER |
| End_Date | DATE | NA |
The date and time at which the activity will end or did end. For planned activities, this would be expected end date. | No |
DATE |
| 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) |
| External_Reference | STRING64 | NA |
A value that is used by an external organization to reference this activity. For example, if an external organization is hired to perform this activity, this column could be used to store the work order or purchase order number that organization uses to reference this activity. | No |
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) |
| Internal_Reference | STRING64 | NA |
A value that is used internally within the organization to reference this activity. | No |
VARCHAR2(64) |
| Kelly_Hose_Test_Pressure | double | Pressure kPa |
Pressure to which Kelly Hose was successfully tested | No |
NUMBER |
| Name | ENTITY_NAME | NA |
The name given to any object or data item, e.g. name of Well, name of Field, etc. | No |
VARCHAR2(255) |
| Original_Source | STRING64 | NA |
The name of the person, Organization or project source that originally provided this entity, e.g. "IHS-EnergyData" or "FinderUpper Stratton Deeper Pool 15" | No |
VARCHAR2(64) |
| Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
| Purpose | STRING255 | NA |
A description of purpose of the activity or its stage | No |
VARCHAR2(255) |
| Remarks | STRING2000 | NA |
Any type of remarks added to an entity instance. | No |
VARCHAR2(2000) |
| SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
| Source | STRING64 | NA |
Name of the person or organization responsible for this entitys E and P content and quality. Not the data technologist or IT expert creating the entity, for which see IT_Object.Insert_User and Update_User. | No |
VARCHAR2(64) |
| Stand_Pipe_Test_Pressure | double | Pressure kPa |
Pressure to which Stand Pipe was successfully tested | No |
NUMBER |
| Start_Date | DATE | NA |
The date and time at which the activity will start or did start. For planned activities, this would be expected start date. | No |
DATE |
| Time_Offset | double | Time s |
The time offset from the start of the program that this activity is scheduled to start at. This is normally used while planning a job. | No |
NUMBER |
| Total_Cost | double | No_Unit |
The total cost of the activity expressed in the local currency. | No |
NUMBER |
| Transient_Period | R_Transient_Period |
|
A code or name that indicates whether the activity is executed daily, monthly, on demand, etc. | No |
VARCHAR2(64) |
| Triggering_Event_Id | Event |
|
The identifier of the event that triggered the start of this activity. Events can trigger activities. For example, an explosion event could trigger a firefighting activity. Note that this value should not conflict with, or be confused with, the value in Activity_Status.Triggering_Event. | No |
NUMBER(38) |
| 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) |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Activity_Template | Activity_Template | _ | Restrict | No |
| Fulfilled_Activity | Activity | _ | Assoc to Many | No |
| Activity_Program | Activity_Program | _ | Restrict | No |
| Transient_Period | R_Transient_Period | _ | Restrict | No |
| Super_Activity | Activity | _ | Assoc to One | No |
| Triggering_Event | Event | _ | Nullify | No |