| Name | Facility_Status |
|---|---|
| Entity Type | Table |
| Description | An association that denotes the historical associations between facilities and their statuses. At a given point in time, a facility can have multiple statuses, but only one status from a given status category (for example, one regulatory status and one operational status). A facility can have many statuses over time. A change of status can be triggered by the start or completion of an activity or an event taking place. |
| Submodel | Facility |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | |
| Generalizations | Transient_Association , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| End_Date | DATE | NA |
End time of the association | 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) |
| Fac_Status_Category_Code | R_Facility_Status | NA |
The facility status category that classifies the facility status for the facility. For example, regulatory, operational, etc. | Yes |
VARCHAR2(64) |
| Facility_Id | Facility |
|
The facility to which the status applies. | Yes |
NUMBER(38) |
| Facility_Status_Code | R_Facility_Status | NA |
A standard abbreviation, mnemonic, or short code that represents the reference value for the facility. | Yes |
VARCHAR2(64) |
| Facility_Tbl | Meta_Entity |
|
Facility type | Yes |
VARCHAR2(30) |
| 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) |
| 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) |
| Start_Date | DATE | NA |
Start time of the association. | No |
DATE |
| Triggering_Activity_Id | Activity |
|
The activity that triggered the status of the facility. | No |
NUMBER(38) |
| Triggering_Activity_Tbl | Meta_Entity |
|
Activity type | No |
VARCHAR2(30) |
| Triggering_Event_Id | Event |
|
The event that triggered the change in status for the facility | 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 |
|---|---|---|---|---|
| Triggering_Event | Event | The event that triggered the change in status for the facility | Nullify | No |
| Triggering_Activity | Activity | The activity that triggered the status of the facility. | Cascade | No |
| Facility | Facility | The facility to which the status applies. | Cascade | Yes |
| Facility_Status_Code | R_Facility_Status | The facility status and status category pairing that is valid for the facility. | Restrict | Yes |