Figure [ReD-01] Resource ABEs Level 1

MODA / Information Framework / Business Entity / Resource Domain / Figure [ReD-01] Resource ABEs Level 1

Project:

Figure [ReD-01] Resource ABEs Level 1 : Class diagram

Created:	3/28/2022 3:51:09 PM
Modified:	11/14/2024 5:59:31 PM
Project:
Author:	Giu Platania
Version:	1.0.0
Advanced:
ID:	{AD2E247A-883B-421e-A0EB-2CA0A2481FBD}

The Resource Domain consists of a structured set of ABEs that are used to manage the definition, development, and operational aspects of the information computing and processing infrastructure of a system. It supports the eTOM processes that deal with the definition, development and management of the infrastructure of an enterprise. This includes the components of the infrastructure as well as Products and Services that use this infrastructure. The Resource Domain has three important objectives. • To associate Resources to Products and Services and provide a detailed enough set of Resource entities (organized as ABEs) to facilitate this association. • To ensure that Resources can support and deliver Services offered by the enterprise. Management of resources involves planning, configuration, and monitoring to capture performance, usage, and security information. This also includes the ability to reconfigure Resources in order to fine tune performance, respond to faults, and correct operational deficiencies in the infrastructure. Resources also provide usage information which is subsequently aggregated to the customer level for billing purposes. • To enable strategy and planning processes to be defined. Entities in the Resource domain may be associated with processes that involve planning new and/or enhanced Services, or even the retirement of Services, offered by the Enterprise. The following are brief descriptions of each of these ABEs. Resource Party Roles ABE • Resource Party Roles ABE contains all PartyRoles related to the Resource Domain such as Technician, ResourceManager. Resource Specification ABE • The Resource Specification ABE contains entities that define the shared characteristics and behavior of each type of Resource entities. This enables multiple instances to be derived from a single specification entity. In this derivation, each instance will use the shared characteristics and behavior defined in its associated template Resource Strategy & Plan. Resource ABE • A Resource represents an instance of ResourceSpecification. The Resource ABE contains entities that are used to represent the three types of Resources: Logical, Physical and Compound Resources. • The Resource carries the place where the Resource is installed, as well as configuration characteristics, such as assigned telephone numbers and internet addresses. The Resource also tracks the links to Product and/or Service realized. Resource Order ABE • The Resource Order ABE contains entities related to a request to provide / update / remove Resources. Resource Configuration ABE • The Resource Configuration ABE represents the specification of the different possible Resource configurations as well as the Resource Configurations instantiated for a Resource. Resource Usage ABE • The Resource Usage ABE represents the specification of Resource Usage types and collects Resource Usage records with their characteristics (a.k.a. consumption data). The entities in this ABE provide physical, logical, and network usage information. Resource Performance ABE • The Resource Performance ABE collects information used to correlate, consolidate, and validate various performance statistics and other operational characteristics of Resources. Each of these entities also enables network performance assessment against planned goals, performs various aspects of trend analysis, including error rate and cause analysis and Resource degradation. Entities in this ABE also includes statistics defining Resource loading, and traffic trend analysis. Resource Test ABE • The Resource Test ABE contains entities that are used to test PhysicalResources, LogicalResources and CompoundResources. These entities are usually invoked during installation, as a part of trouble diagnosis or after trouble repair has been completed. Resource Capacity ABE • The Resource Capacity ABE specifies the ability of Resource to provide capability measured in quantity and units of quantity over an extended period. It also manages the Resource Capacity Demands. Stock Item ABE • The Stock Item ABE covers all information needed by the supply chain. It includes: The Stock Item catalogue, The Stock Items stored in a warehouse and The Stock Item Shipments specifying Stock Items movements (receiving or shipping). Resource Trouble ABE (not fully developed) • The Resource Trouble ABE collects information about problems found in allocated resource instances, regardless of whether the problem is physical or logical. Entities in this ABE capture detection, root cause, and resoluiton of these problems and maintain a history of the activities involved in diagnosing and solving the problem. This history includes tracking, reporting, assigning people to fix the problem, testing and verification, and overall administration of repair activities. Resource Strategy and Plan ABE (not fully developed) • The Resource Strategy and Plan ABE is used to plan networks and resource elements both initially and for growth. It will coordinate both logical and physical resource growth. Inputs are budgets from business sources, service forecasts, current and projected network utilization, new technologies, and retiring technologies. It handles the lifecycle (installation, modification, removal, and retirement) for both logical and physical resources. Resource Topology ABE (not fully developed) • The Resource Trouble ABE collects information about problems found in allocated resource instances, regardless of whether the problem is physical or logical. Entities in this ABE capture detection, root cause, and resoluiton of these problems and maintain a history of the activities involved in diagnosing and solving the problem. This history includes tracking, reporting, assigning people to fix the problem, testing and verification, and overall administration of repair activities.