Service level agreement

Modified on: Mon, 11 Oct, 2021 at 11:59 AM

Service Level Agreements dialog is used to set SLAs for given company that the user works with - i.e. an Airline that has signed an agreement with our customer to handle their flights/activities on given Station (it is mainly important for ground tasks done by the airport)

Name	name of the SLA that helps the user to find the SLA "rule" and name it in a human readable way
Valid	period within the SLA is valid
Frequency	frequency within the SLA is valid
Company	name of the company that the SLA shall be valid for (i.e. if the user of the N-OC (our customer) is Airport Company AC1 and they are making some special activities for Airline A1, Airline A2, Airline A3 then in this field set value Airline A2 if one sets the SLA "rules" for Airline A2)
Station	station for which the SLA is valid (i.e. if the user of N-OC (our customer) is Airport Company AC1 that have more than 1 airport i.e. in Station ABC, Station CDE and Station XYZ then here one shall select the station for which the rule is valid - i.e. if there are different SLAs for different stations then for each station there shall be a separate SLA object created using this dialog)
Active flag	informs whether the SLA is active or not
Default flag	informs whether the SLA is default or not (in general it is not supported by the demands calculation algorithm)

Click Add to add a rule:

Function	name of a function
Value	how many handling units (i.e. people/counters) shall be available
Equipment	In the Equipment Qualifications you specify the diffent "equipments" e.g. Service Counters.
Working area	in which working area "handling unit" is required. From Working Areas
Start	start time of "handling unit" availability
End	end time of "handling unit" availability
Department	Performing department. From Department
Destination	which destination the "handling unit(s)" is going to handle (i.e. there can be different rules for different destinations - FRA vs. POZ vs. EWR)
Filter	legs filter for which the "rule" is valid (i.e. "Domestic flights", "European flights", "US flights")
Dedicated	whether the rule is dedicated for given airline or not (i.e. "only SAS counter", or "any airline counter")
Split	Specifies whether the task can be split into smaller chunks (i.e. so different people can be assigned to parts of it) or not
Time based	Specifies whether the rule is time based or not (whether it is prior to departure/after an arrival or not) - if set to true then Start value can be i.e. -0130 which means 1.5h before (scheduled) departure, End can be i.e. 0000 - which means 0 minutes before (scheduled) departure
Arrival	Specifies whether the rule is for departures (set to false) or arrivals (set to true)
Customer priority	In case of more than 1 rule matching then the priority will be taken into account to explicitly choose one
Active	the rule is active or not
Default	The rule is default or not (in general it is not supported by the demands calculation algorithm)

Related Articles