| Name | Rate_Schedule |
|---|---|
| Entity Type | Table |
| Description | A schedule for payments as set up by a business associate, such as a service provider, jurisdiction, or regulatory agency. Rate schedules are often used to administer the rates for rentals or for services provided. (PPDM3.7) |
| Submodel | Obligation |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | |
| Generalizations | Entity , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Basis_Category_Code | R_Rate_Basis_Category |
|
The category of basis on which the rate amounts outlined in a rate schedule are selected. For example, acreage, water depth, etc. The value in this column, combined with the values in Basis_High_Value and Basis_Low_Value tell you the basis of the rate amounts in this rate schedule. For example, if the Basis_Category_Code is water depth and Basis_High_Value is 199 and the Basis_Low_Value is 100, it tells you that the rates in this particular rate schedule are applicable to entities at a water depth between 100 and 199. | No |
VARCHAR2(64) |
| Basis_High_Value | double | No_Unit |
The value in this column, combined with the values in Basis_Category_Code and Basis_Low_Value tell you the basis of the rate amounts in this obligation. For example, if the Basis_Category_Code is water depth and Basis_High_Value is 199 and the Basis_Low_Value is 100, it tells you that the rates in this particular obligation are applicable to entities at a water depth between 100 and 199. If the basis is not a numeric range, the basis will be stored in Basis_Text. | No |
NUMBER |
| Basis_Low_Value | double | No_Unit |
The value in this column, combined with the values in Basis_Category_Code and Basis_Low_Value tell you the basis of the rate amounts in this obligation. For example, if the Basis_Category_Code is water depth and Basis_High_Value is 199 and the Basis_Low_Value is 100, it tells you that the rates in this particular obligation are applicable to entities at a water depth between 100 and 199. | No |
NUMBER |
| Basis_Text | STRING128 | NA |
The value in this column, combined with the values in Basis_Category_Code tell you the basis of the rate amounts in this obligation. For example, if the Basis_Category_Code is Economic Zone and Basis_Text is Zone A, it tells you that the rates in this particular obligation are applicable to entities in Economic Zone A. If the basis is numeric in nature, the basis can be stored in Basis_High_Value and Basis_Low_Value. | No |
VARCHAR2(128) |
| Basis_UOM | R_Unit |
|
The unit in which the values in Basis_High_Value and Basis_Low_Value are expressed. | No |
VARCHAR2(64) |
| End_Date | DATE | NA |
Date on which the rate schedule expired. | 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) |
| 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) |
| Jurisdiction_BA_Id | Business_Associate |
|
The business associate who owns this rate schedule. | No |
NUMBER(38) |
| 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) |
| Rate_Schedule_Number | STRING64 | NA |
A value, either textual or numeric, that uniquely identifies a rate schedule. | No |
VARCHAR2(64) |
| Rate_Schedule_Type | R_Rate_Schedule |
|
The type of rate schedule. Examples are royalty, rental, royalty suspension, etc. | Yes |
VARCHAR2(64) |
| 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) |
| Start_Date | DATE | NA |
Date on which the rate schedule became effective. | No |
DATE |
| 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) |
| From Entity | Link | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Land_Desc_Component | Rate_Schedule | If the land description component is a rate schedule, this is the identifier of that rate schedule. | Cascade | No |
| Rate_Schedule_Component | Rate_Schedule | The rate schedule that defines the rates for this rate schedule component. | Cascade | Yes |
| Rate_Schedule_Detail | Rate_Schedule | The rate schedule under which this rate is paid. | Cascade | Yes |
| Rate_Schedule_Remark | Rate_Schedule | The rate schedule to which this remark applies. | Cascade | Yes |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Basis_Category_Code | R_Rate_Basis_Category | The category of basis on which the rate amounts outlined in a rate schedule are selected. For example, acreage, water depth, etc. The value in this column, combined with the values in Basis_High_Value and Basis_Low_Value tell you the basis of the rate amounts in this rate schedule. For example, if the Basis_Category_Code is water depth and Basis_High_Value is 199 and the Basis_Low_Value is 100, it tells you that the rates in this particular rate schedule are applicable to entities at a water depth between 100 and 199. | Restrict | No |
| Rate_Schedule_Type | R_Rate_Schedule | The type of rate schedule. Examples are royalty, rental, royalty suspension, etc. | Restrict | Yes |
| Jurisdiction_BA | Business_Associate | The business associate who owns this rate schedule. | Restrict | No |
| Basis_UOM | R_Unit | The unit in which the values in Basis_High_Value and Basis_Low_Value are expressed. | Restrict | No |