Data Mapping

Alarms
Sample Data TELE2 convention CAN convention
BSCN-NIN496 site Equipment
NN1021 hostname Equipment
2017-02-28 23:00:16 firstoccurrence Creation Date
2017-02-28 23:00:48 enddate Closed Date
Major severity Severity
7624 CS U-PLANE CONNeventid Alarm Cause
PLMN-PLMN/BSC-401487additionalinfo1 Equipment
00 00 00 69 00 00 additionalinfo2 Description

Page 1
 Data Mapping
Tickets
Sample Data TELE2 convention CAN convention
TT4520942 Entry ID TT Reference ID
02/01/17 00:06 Created date Creation Date
01/01/17 23:05 Alarm Up Alarm Up Time
02/01/17 00:43 Closed Time Closed Date
Closed Status TT Status
NOC Assigned group
5 Net Prio Severity
BTS Service Equipment Type
External Alarms Short description
BSC-NIN129 Site Equipment
NN2327 Hostname Equipment
PLMN-PLMN/BSC-396075/BAdditional Info 1 Equipment
Other Fault Cause
7402 RECTIFIER Alarm description Alarm Cause
NOC TT_Group
Other Fault Cause By
0.37 Fault-time per TT
1 on time
null Additional Info 2

Page 2
 Data Clarification
Alarm
Sl. No.
1
2

Ticket
Sl. No.
1
2

Page 3
 Data Clarification
Alarm
Clarification requested from Avanseus
Combination of “site”, “hostname”, “additionalinfo1” is considered as Equipment for prediction
Tcket Refernece ID is missing

Ticket
Clarification requested from Avanseus
For auto generated tickets, combination of “Site”, “Hostname”, “Additional Info 1” is considered as Equipment.
Severity contains values 0,3,4,5. How to categorize them as Low, Medium, High severity tickets?
For manually generated tickets with “Alarm Up” time missing, “Site” and “Additional Info 1“ is missing in many
cases. Hence only “Hostname” will be considered as Equiment. Also “Alarm description“ in these cases looks
to be written maually and are not standard.

Page 4
 Data Clarification

Answer from Tele2 Final decision

Answer from Tele2 Final decision

s Equipment.

Page 5