allocation
An allocation is a description of how your organization is internally approved to use a particular software product, as specified in your software license. Some examples of an allocation are enterprise, single-user, and single-server.
allocation relationship
An allocation relationship is a record that provides the attributes of a software internal allocation. Each allocation relationship provides attributes and relationships that apply to a particular type of allocation.
asset
An asset is an IT product that you own or are about to acquire. Assets represent physical products with unique identifiers such as a serial number, a configuration, or a contact. You define an asset record for each asset that you want to track individually.
asset configuration
An asset configuration is a record that describes the configuration of a hardware asset as it currently exists in your environment. Asset configurations are different from model configurations due to changes made over time.
asset family
An asset family is a way to organize and classify assets to track specialized information about products, services, or equipment used in your organization. The asset family determines the information that you see on the page when you define an asset. Asset family was previously named asset type.
asset group
An asset group is a related set of assets that share information. Information is tracked only for the group and not for individual members of the group.
attachment
An attachment is an electronic file or URL page that contains supporting documentation for an object. For example, you can attach a scanned contract with a legal document to represent the contract.
audit history
An audit history is a chronological list of changes made to an object record over time.
change event
A change event monitors field changes for an object and works with notifications that are created by a workflow provider (for example, CA Process Automation) to notify you that the field value has changed.
class
A class is a broad descriptive category of an asset family that is assigned to a model or asset and facilitates information retrieval.
company
A company is an organization that manufactures, sells, or purchases products tracked in your repository or is a party to legal documents tracked in your repository.
configuration
A configuration has two specific definitions within CA APM. A configuration can be a description of a computer (such as a PC, laptop, server, and so forth) and its individual components (monitor, modem, and so forth). You use configuration records to identify models and assets that represent a computer's components. A configuration is also a method to change the user interface and default behavior of the product so users can more easily enter, manage, and search for information.
configuration relationship
A configuration relationship is the set of attributes that belong to a particular category of hardware configurations. Configuration relationships are provided for assets and models.
contact
A contact is a person or department that is involved with the acquisition, use, or management of an object in your repository.
date event
A date event monitors date field changes for an object and works with notifications that are created by a workflow provider (for example, CA Process Automation) to notify you that an important date is approaching or has passed.
escalation
An escalation is the process of automatically forwarding a notification to another person after the original recipient does not respond within a given time period.
escalation cap
An escalation cap is an upper limit on the amount a recurring cost can increase. Typically, contracts specify the limit.
escalation percentage
An escalation percentage is an amount by which you expect a recurring cost that is associated with an asset or legal document to increase each recurring period. For example, you have a $100 charge that recurs once a year for three years. To account for inflation, you expect a vendor to increase product costs by 5 percent each year. The cost of the product would be $100 for the first year, $105 for the second year ($100 + (.05 x $100) = $105), and $110.25 for the third year ($105 + (.05 x $105) = $110.25).
The escalation percentage is based on the recurring period. If you make monthly payments, but the amount due is likely to increase on a yearly basis, you can enter the cost as a yearly cost with an escalation percentage. A yearly payment is calculated, increased by the escalation percentage every year until the termination date.
Event Server
The Event Server is a product component that processes events. The server periodically scans event tables in the repository and fires the event when the event occurs. After firing the event, the workflow provider sends notifications to users and manages acknowledgements. The server updates the repository with the information so you can determine whether the workflow process is completed, in progress, failed, or aborted.
extended field
An extended field is a field that can be added to any object record. Extended fields can be used to store information that you need to track about an object not provided by a default field.
governing legal document
A governing legal document is the document on which a legal document is based. The governing legal document has the main set of terms and conditions from which the legal document is derived.
item
See model.
legal document
A legal document is a document that describes a legal relationship or agreement between two or more parties. For example, contracts, notification letters, master agreements, leases, volume purchase agreements, letters of intent, and so on are all considered legal documents. Although software licenses are legal documents, they are tracked differently.
legal template
A legal template is the set of attributes that belong to a particular category of legal documents (for example, all leases have start dates, end dates, lessors, and lessees). These attributes include terms and conditions that typically apply to that category and user fields.
location
A location is the physical place where an asset, a company, or a contact is found.
masking
Masking is a way to specify search criteria in which you substitute one character for part of a character string. Masking characters are also known as wildcard characters. Use masking to limit the number of records returned by a search or to substitute for search characters when you do not know the exact spelling.
match values
Match values are key fields that uniquely identify entities within a database. For a hardware asset, the match values would be the combination of Domain ID, Unit ID and Type, which uniquely identify a row in the UNIT table.
model
A model is a record that describes a product that you may have purchased in the past or may possibly purchase in the future. Model was previously named item.
model configuration
A model configuration is a record that describes the standard configuration that you purchase for a particular hardware model.
multi-tenancy
Multi-tenancy is the ability for multiple independent tenants (and their users) to share a single product instance (for example, CA APM). Multi-tenancy lets tenants share hardware and application support resources, reducing costs while gaining most of the benefits of an independent implementation. Tenants can only interact with each other in defined ways; otherwise, each tenant views the application instance as solely for its own use.
normalization
Normalization is part of the reconciliation process where you establish a list of rules to standardize, organize, and consolidate data between CA APM and discovered repositories.
note
A note is text that is added to an object record to add more detailed information.
notification
A notification is created by a workflow provider (for example, CA Process Automation) to communicate information to your team members about important events and activity.
object
An object represents something that you record and track in your repository. The primary objects in CA APM are models, assets, legal documents, contacts, companies, organizations, locations, and sites.
parent company
A parent company is a company that owns or controls another company (its subsidiary company).
parent tenant
To place a tenant into a hierarchy, you assign it a parent tenant. The parent tenant becomes the tenant immediately above that tenant in a hierarchy. To remove a tenant from a hierarchy, you can remove its parent tenant assignment.
payment schedule
A payment schedule is a list of payments to be made for a particular cost record. Information in the payment schedule includes when a payment is due, the amount due, whether a payment was made or approved, and in what amount. The information you provide on the Cost page is used to calculate the payment schedules. If you define the recurring period details, the system auto-creates payment records in the database based on the recurring period details you define.
preferred vendor/preferred seller
A preferred vendor/preferred seller is the seller company that you prefer to use for future acquisitions of a product.
recurring cost
A recurring cost is a cost that repeats for a certain time period. Recurring time periods are based on the terms of your agreement. Do not confuse the length of the recurring period with the frequency of payments. For example, if a cost recurs yearly for three years, specify three years as the recurring cost even if you make payments on a monthly basis. You can change the payment frequency at a later time.
related tenants group
A related tenants group is a tenant group that includes a tenant and all tenants belonging to its subtenant group or its supertenant group.
relationship
A relationship is an association between a managed object and another object. Relationship records provide detailed information about the association.
relationship record
A relationship record is created when a primary object is linked with one or more secondary objects.
relationship template
A relationship template is the set of attributes that belong to a particular category of relationship. These attributes determine what types of objects can be linked to each other and the nature of those links.
reminder
A reminder is a notification triggered by an event that alerts a user about an important event or activity.
role
A role, used in security, is a group of users who perform the same tasks and who require the same levels of access to data or functionality.
service provider
The service provider is the master tenant (owner) of a product instance. A product instance can have only one service provider, which can also participate as a parent in one or more tenant hierarchies.
start request form
A start request form is a CA Process Automation automation object that allows users to request the initiation of a new workflow process. A start request form creates an interface that lets users provide structured input and launch a process.
subclass
A subclass is a descriptive category of a class that is assigned to a model or asset to further refine the description provided by the class.
subsidiary company
A subsidiary company is a company that is owned or controlled by another company (its parent company).
subtenant
A subtenant is a tenant that is lower than another tenant (its relative supertenant) in the same tenant hierarchy. Subtenants can be departments or sites within their supertenants. Subtenants can have their own business rules and data, and they also share some business data with their parent tenant and higher supertenants.
subtenant group
A subtenant group is a tenant group that includes a tenant, its subtenants, their subtenants, and so on, to the bottom of that hierarchy. As long as a tenant resides in a hierarchy, its subtenant group is product-maintained; only its name and description can be modified.
supertenant
A supertenant is a tenant that is higher than another tenant (its relative subtenant) in the same tenant hierarchy.
supertenant group
A supertenant group is a tenant group that includes a tenant, its parent tenant, and so on, to the top of that hierarchy. As long as a tenant resides in a hierarchy, its supertenant group is product-maintained; only its name and description can be modified.
template
A template provides pre-defined groups of fields that are associated with a specific object type. For example, a legal template provides fields that belong to a particular type of legal document.
tenant
A tenant is one instance among multiple instances of a single product installation. Using tenants, CA APM can manage multiple separate enterprises that provide support to customers. Each tenant has unique settings and properties and sees the product as its own application, except when the tenant shares data through service provider authorization or a tenant hierarchy.
tenant hierarchy
A tenant hierarchy is a tenant group that you define and manage when you define subtenants (that is, you assign them parent tenants for organizational or data sharing purposes). CA APM supports tenant hierarchies of unlimited depth. However, the service provider can limit the total number and depth of tenants in a hierarchy. The service provider also can prevent individual tenants from having subtenants.
terms and conditions
Terms and conditions specify the areas of agreement for legal documents. Before you define a legal template, create a single master list of all terms and conditions that can be assigned to a legal template. A term and condition can be assigned to multiple legal templates and legal documents.
trimming
Trimming is a way to specify a fixed number of leading or trailing characters to ignore on an asset when performing hardware reconciliation. For example, discovered computer names at one site have a three-character location code as a prefix. You create a trimming record for the asset matching criterion that trims three characters from the left side of the discovered computer names.
watch event
A watch event monitors field changes for an object and works with notifications that are created by a workflow provider (for example, CA Process Automation) to notify you about a potential obstruction to completing a task.
workflow provider
A workflow provider manages notifications and acknowledgements for events.
|
Copyright © 2013 CA.
All rights reserved.
|
|