Basic Info (SLA) |
The Basic Info tab for primary service level agreement (SLA) information enables you to display and define the SLA agreement ID and description; equipment category; department ID; station location; and start and end dates.
The Primary Information screen supports department-level access control, so you must belong to a user group with the applicable authorizations to make changes or updates.
The field in the top section of this tab defines the data that displays.
Service level agreement ID
Identifier of the SLA currently selected in the grid or that you are defining. This field has a list box. If the ID already exists, its description displays to the right of the ID.
The data in the fields at the bottom section of this tab define basic information about the service level agreement. Unless otherwise indicated, these fields are required.
Description
Description of the service level agreement. Free-format area.
Availability location ID
Identifier of the availability location. If SLAs are defined by location, this ID is used to identify which equipment units belong to that SLA.
The default availability location ID is specified on the Basic Info tab of the Data -> Setup -> Organization Structure -> Locations -> Primary Information screen.
SLA equipment category
Equipment category this service level agreement covers. An equipment category may be part of more than one SLA at a time.
Department ID
Identifier of the department for this service level agreement. You must specify either a department or a location ID.
Station location ID
Identifier of the station location to which the agreement applies. This field has a list box. The location name displays to the right of the ID. This field is optional.
Locations are designated as station locations in the Station field on the Functions tab of the Data -> Setup -> Organization Structure -> Locations -> Primary Information screen.
Note: The dates in the following date fields determine the length of the requirements period. Consider the following in regard to these dates:
The dates must not allow the service level agreement date range to fall within the date range of an existing agreement for this department and this equipment category.
A lengthy agreement period may adversely affect performance, especially if the number of minutes in a requirements period is small.
The "same" SLA (e.g., department and category combination or location and category combination or department, location, and category combination) cannot be active for overlapping dates.
Begin date
Date the service level agreement takes effect. Once saved with the agreement it may not be changed. Only requirement periods beginning in the future will be created and have status calculated.
End date
Date this service level agreement expires. An agreement may be of any length as long as it does not violate the overlap restrictions. The date must not be earlier than the system date.
You may change this date to an earlier one but not a later one.