: Public abstract <<TMF_BusinessEntity>> Business Entity
| Created: |
1/10/2022 12:00:56 PM |
| Modified: |
4/15/2022 10:27:06 AM |
|
 Project: |
|
| Author: |
Giu Platania |
| Version: |
22.0 |
| Phase: |
prop |
| Status: |
Implemented |
| Complexity: |
Easy |
| Difficulty: |
|
| Priority: |
|
| Multiplicity: |
|
| Advanced: |
|
| UUID: |
{A97B73D0-D46A-4db9-AE53-2E5C44984C96} |
| Appears In: |
Figure SO.06 - Basic Service Model – A Starting Point, Figure SO.07 - Representing BGP as a LogicalResource, Figure RO.06a - Resource Number Portability Relationships (OLD RO.04), Figure Res.03 - Resources and ResourceSpecifications (OLD RS.01), Figure Res.09 - Resource Number - Number Specification (OLD RN.01), Figure PR.03 - Relating the Physical and Logical Aspects of a Device to Each Other, Figure PR.11 - The Relationship Between PhysicalResource and PhysicalResourceSpecification, Figure LR.04 - Resource specialization and inheritance, Figure LR.05 - Relationship between Resource and Product, Figure LR.07 - Relationship between Product, Service and Resource, Figure LR.08 - Principal Subclasses of LogicalResource, Figure LR.17 - Managing ResourceRoles Using PartyRoles, Figure LR.30 - Protocol Interactions, Figure LR.31 - CompoundResource, ResourceCollection, and ResourceElement, Figure LR.32 - Example Instance Implementation of a CompoundResource, Figure LR.16a - Different Types of ResourceRoles (OLD LR50), Figure RF.02 - ResourceFunction inheritance, Figure ResCS.10 - Model Enhancements - Virtual Memory, ResourceSpec-Resource-ResourceRole, Resource-Service-PartyRole, Resource and Role Summary, NOT USEFUL Figure CS.09 - Model Association Enhancements - 2, NOT USEFUL = LR.07 Figure PR.34 - Relationship Between Product, Service and Resource, UNUSED Figure PR.36 - PhysicalResourceSpecification Business Entity Model, UNUSED Figure PR.35 - PhysicalResource Business Entity Model, Router, Simplified Policy Application Model - TMW |
This is an abstract base class for describing different logical aspects of devices (e.g., DeviceInterfaces) that constitute a Product. It has two main purposes: (1) to collect common attributes and relationships for all logical entities, and (2) to provide a convenient, single point where relationships with other managed objects can be defined.<br/>
- Attributes
- Associations To
- Associations From
- Tagged Values
- Advanced
- Other Links
| Attribute |
Public Boolean
isOperational
|
Details:
| Alias: |
|
| Initial: |
|
| Stereotype: |
<<required>> |
| Ordered: |
|
| Range: |
|
| Transient: |
False |
| Derived: |
False |
| IsID: |
False |
|
Notes:
|
This attribute is used to define the operational status of the object, and is implemented as a Boolean: TRUE means that the object is currently operational, and FALSE means that the object is not currently operational.<br/>
|
|
Public Integer
lrStatus
|
Details:
| Alias: |
|
| Initial: |
|
| Stereotype: |
|
| Ordered: |
|
| Range: |
|
| Transient: |
False |
| Derived: |
False |
| IsID: |
False |
|
Notes:
|
This is an enumerated integer whose value indicates the current status of the object. The following values are defined:<br/><br/> 0: Unknown<br/> 1: OK<br/> 2: Initializing<br/> 3: Starting<br/> 4: Paused<br/> 5: Stopping<br/> 6: Stopped<br/> 7: Degraded<br/> 8: Stressed <br/> 9: Predicted Failure<br/> 10: Error - General<br/> 11: Error - Non Recoverable<br/> 12: Not Installed or Not Present<br/> 13: In Maintenance<br/> 14: Unable To Contact<br/> 15: Lost Communications<br/><br/>Stopped indicates that the LogicalResource is known to still exist, but it is no longer operational. However, it has not failed.<br/> <br/>Stressed indicates that the LogicalResource is functioning, but needs attention (e.g., it may be overheating, or overloaded in some way). This is similar to Predicted Failure, which indicates that this LogicalResource is functioning properly, but is predicting a failure in the near future.<br/><br/>In Maintenance indicates that this LogicalResource is being configured, maintained, or otherwise administered and is NOT available for service.<br/><br/>Unable To Contact indicates that the monitoring system has knowledge of this LogicalResource but has never been able to establish communications with it. In contrast, Lost Commmunications indicates that the LogicalResource has been contacted successfully in the past and is known to still exist; however, it is currently unreachable.<br/><br/>This is an optional attribute.<br/>
|
|
Public Integer
serviceState
|
Details:
| Alias: |
|
| Initial: |
|
| Stereotype: |
|
| Ordered: |
|
| Range: |
|
| Transient: |
False |
| Derived: |
False |
| IsID: |
False |
|
Notes:
|
This is an enumerated integer that defines the availability and usage (i.e., the service state) of this LogicalResource. Its values are:<br/><br/> 0: Unknown<br/> 1: In Service<br/> 2: Out of Service<br/> 3: Testing<br/> 4: In Maintenance<br/> 5: Not Available<br/> 6: Not Applicable<br/><br/>This is an optional attribute.<br/>
|
|
| Tag |
Value |
| IsCoreEntity |
False |
 Details:
Values: true,false
Default: False
|
| rsa_guid |
_3E3F0EC000E93CDAA51A00F6 |
Details:
|
| Property |
Value |
| isActive: |
0 |
| isFinalSpecialization: |
0 |