IBM Tivoli Netcool Performance Manager for Wireless 9.1.2
IBM Tivoli Netcool Performance Manager for Wireless 9.1.2 Terminology
IBM Tivoli Netcool® Performance Manager for Wireless 9.1.2 - Terminology
Assumptions
Assumptions You have some knowledge of the wireless telecommunications industry
The assumption is that you have some knowledge of the wireless telecommunications industry.
Objectives
Objectives Attributes Fields Peg Counter Primitive Calculations (PCalc) User Defined Calculation (UDC) Stored Summary Stored Busy Hour Network Configuration Data Technology Pack Global Object Model Perspectives Upon completion of this module, you should be able to define the following terms:
Objectives. Upon completion of this module, you should be able to define the following terms: Attributes, Fields, Peg Counter, Primitive Calculations (PCalc), User Defined Calculation (UDC), Stored Summary, Stored Busy Hour, Network Configuration Data, Technology Pack, Global Object Model, Perspectives.
Module outline
Module outline Overview Define terms
Module outline: Overview; Define terms.
Attributes
Attributes Attributes are key characteristics of a network entity Examples are: Primary ID Location Name Label Technology Parentage ID
Attributes Attributes are key characteristics of a network entity. Examples of attributes are primary ID, location, name, label, technology, and parentage ID.
Fields
Fields For the IBM Tivoli Netcool Performance Manager for Wireless (TNPMW) system, a field represents any of the following terms: Peg count Primitive Calculation (PCalc) User Defined Calculation (UDC) External Field
Fields For the IBM Tivoli Netcool Performance Manager for Wireless (TNPMW) system, a field represents any of the following terms: Peg count; Primitive Calculation, called (PCalc); User Defined Calculation, called (UDC); and External Field.
Fields: alternative names
Fields: alternative names Fields might be called other words on other systems, such as metrics, counters, measurements, and network performance metrics.
Fields might be called other words on other systems, such as metrics, counters, measurements, network performance metrics, and so on.
Peg counter
Peg counter A peg counter is the most basic type of a field in the TNPMW software. Peg is a shortened version of peg counter. They might also be called fields, metrics, or key performance indicators (KPI). Peg counters can be combined into a PCalc or a UDC, which are defined in this module.
Peg Counter. Peg is a shortened version of peg counter. They might also be called fields, metrics, or key performance indicators (KPI). A peg is the most basic type of a field in the Performance Manager for Wireless software. Pegs can be combined into a PCalc or a UDC, which are defined later in this module.
Primitive calculation (PCalc)
Primitive calculation (PCalc) Primitive calculations are one or more peg counters that have been manipulated mathematically.
Primitive Calculations are one or more peg counters that have been manipulated mathematically. They are delivered with the software. PCalc is the abbreviation for primitive calculation. You can not edit a PCalc. If none of the PCalc meet your requirements, you can create a user-defined calculation and customize it to meet your requirements. You can view the contents of a PCalc in the report definition’s Field Selection. Select a field’s row and scroll to the right until you find the PCalc Source column heading. When you point at the field’s PCalc cell, its contents are displayed.
User defined calculation (UDC)
User defined calculation (UDC) A user defined calculation is a user-created field made from any or all of the following items: Peg counter PCalc Other UDC Algebraic functions
User Defined Calculation also called (UDC). A User Defined Calculation is a user-created field made from any or all of the following items: Peg counter, PCalc, Other UDC, Algebraic functions.
Stored summary
Stored summary A stored summary is traffic data aggregated for a day, week, or month and stored in the database as a traffic field.
Stored Summary. A Stored Summary is traffic data aggregated for a day, week, or month and stored in the database as a traffic field.
Stored busy hour (SBH)
Stored busy hour (SBH) TNPMW can compute and store data for the busiest hour of the day, week, and month based on the designated determiner. The stored busy hour (SBH) data is stored as traffic data fields in the data base.
Stored busy hour, also called (SBH) . TNPMW can compute and store data for the busiest hour of the day, week, and month based on the designated determiner. The stored busy hour (SBH) data is stored as traffic data fields in the data base.
Network configuration data
Network configuration data Network configuration data (NC data) is data provided by the network that represents one of the network elements in the PMW data base. Performance Manager for Wireless refers to NC data as attributes in the user interface. NC data is stored in the database in NC tables.
Network Configuration Data (NC data) is data provided by the network that represents one of the network elements in the PMW data base. PMW refers to NC data as attributes in the user interface. NC data is stored in the database in NC tables.
Technology pack
Technology pack A technology pack is an application package designed for use with Tivoli Netcool Performance Manager for Wireless. A Technology Pack always delivers technology-related performance management functions Example: Global System for Mobile Communications (GSM)
A technology pack is an application package designed for use with Tivoli Netcool Performance Manager for Wireless. A technology pack always delivers technology-related performance management functions. An example is Global System for Mobile Communications (GSM).
Technology pack
Technology pack A technology pack might also deliver vendor-specific performance management functions, for example, Ericsson GSM. A technology pack is deployed on the core TNPMW application platform. A technology pack can be configured to use essential core functions to collect and present wireless data information specific to vendors and technology.
A Technology Pack might also deliver vendor-specific performance management functions, for example, Ericsson GSM. A Technology Pack is deployed on the core TNPMW application platform. A Technology Pack can be configured to use essential core functions to collect and present wireless data information specific to vendors and technology.
Global object model
Global object model The Global Object Model (GOM) is designed to define a base set of vendor-neutral objects that can be reused across technologies and vendors. When you create and use a GOM Technology Pack, the vendor-neutral objects are excluded from the vendor-specific objects.
The Global Object Model (GOM) is designed to define a base set of vendor-neutral objects that can be reused across technologies and vendors. When you create and use a GOM Technology Pack, the vendor-neutral objects are excluded from the vendor-specific objects.
Gateway
Gateway The gateway picks up raw performance data collected from the network, parses it, and produces Loader Input Files (LIFs).
The Gateway picks up raw performance data collected from the network, parses it, and produces Loader Input Files (LIFs). LIFs are defined next.
Loader input files (LIFs)
Loader input files (LIFs) LIFs are produced by a gateway; they contain raw performance data and hierarchy information in a standard text format The file extension is .lif
Loader Input Files also called (LIFs) are produced by a gateway; they contain raw performance data and hierarchy information in a standard text format. The file extension is .lif.
Loader
Loader The loader parses a LIF and inserts the data into performance tables within the TNPMW database.
The loader parses a LIF and inserts the data into performance tables within the TNPMW database.
Perspectives
Perspectives Perspectives are used to organize hierarchically a subset of entity types based on several attributes: Technology Vendor Subsystem Qualifier
Perspectives are used to organize hierarchically a subset of entity types based on a number of attributes such as technology, vendor, subsystem, and qualifier.
Perspectives
Perspectives The vendors, technologies, subsystems, and qualifiers that are available depend on the network configurations used in your system. Qualifiers are attributes that are not necessarily linked to technologies, subsystems or vendors. They are used to represent other aspects of a network such as geographical organization.
The vendors, technologies, subsystems, and qualifiers that are available depend on the network configurations used in your system. Qualifiers are attributes that are not necessarily linked to technologies, subsystems, or vendors. They are used to represent other aspects of a network such as geographical organization.
Summary
Summary Attributes Fields Peg Counter Primitive Calculations (PCalc) User Defined Calculation (UDC) Stored Summary Stored Busy Hour Network Configuration Data Technology Pack Global Object Model Perspectives You should be able to define the following terms:
Summary. You should be able to define the following terms: Attributes, Fields, Peg Counter, Primitive Calculations (PCalc), User Defined Calculation (UDC), Stored Summary, Stored Busy Hour, Network Configuration Data, Technology Pack, Global Object Model, Perspectives.
Training roadmap for IBM Tivoli Netcool Performance Manager for Wireless
Training roadmap for IBM Tivoli Netcool Performance Manager for Wireless Click this link to the training page: http://www.ibm.com/software/tivoli/education/edu_prd.html Click this link for the section on IBM Tivoli Netcool Performance Manager for Wireless: http://www.ibm.com/software/tivoli/education/edu_prd.html#X916845N81075L22
Training roadmap for IBM Tivoli Netcool Performance Manager for Wireless. Click this link to the training page. Click this link for the section on IBM Tivoli Netcool Performance Manager for Wireless.
Trademarks