The switching system shall be capable of providing traffic measurement reports. These reports shall be automatically printed on a system printer and on a remote teletypewriter or video display unit, at time intervals determined on command given by the operating personnel locally at the exchange or remotely at a remote location.
Statistics and Measurement of Traffic of Digital Telephone Switching Systems
5.29.1 Reports on Command
a) The switching system shall provide the following reports on command:
1. Traffic in erlangs.
2. Number of call attempts.
3. Percentage of successful calls.
4. Average holding time.
5. Number of equipped device (line module, network module, Dual Tone Multi Frequency (DTMF) registers, etc.) and number of blocked devices out of service.
7. Percentage of overflow.
b) The reports shall include the following types of traffic.
2. Local calls, coin box, and PABX.
3. DDD (Direct Distance Dialing (national)) calls.
4. IDDD (International Direct Distance Dialing) calls.
5. Operator-assisted calls.
6. Special services and subscriber’s services.
7. Special services and subscribers, covered in the ISDN.
5.29.2 Scheduled Reports
The digital switching system shall have the capability and flexibility of providing, per request and under software control, various scheduled reports with specified parameters/values.
a) When previously specified values for a given measurement period are met, an automatic printout shall be made at the maintenance center. Saudi Aramco shall be able to modify the following report schedules by command:
1. Percentage of delayed calls per exchange.
2. Percentage of blocked calls per module.
3. Percentage of blocked calls per trunk group.
The printed out reports shall include at least the information described on the following sub-paragraphs (b, c, d & e), plus a system-wide summary:
b) Switching equipment (line module, network module, common control, etc.):
1. Peg count of seizures.
2. Usage in erlangs per line unit.
3. Average holding time.
Each kind of traffic-sensitive equipment shall be reported individually.
c) Subscriber Lines
1. Attempts: Number of originating and terminating calls offered per line unit.
2. Usage in erlangs per line unit.
d) Trunk Group
1. Peg count of seizures per outgoing/incoming group.
2. Peg count of the number of overflows per outgoing trunk group.
3. Usage per trunk group; the erlangs per incoming and outgoing trunk group.
4. Average holding time in seconds per trunk group.
e) Dial Tone Delay
1. Average dial tone delay per line module in increments of 0.3 second.
2. Number of test calls per line module.
3. Number of calls delayed more than specified threshold time per line module.
5.29.3 Monitoring of Trunking Network
The trunking monitoring system shall allow for automatic traffic observations of calls and fault tracing on certain trunks or trunk groups that can be selected for study.
5.29.4 Service Quality
Service observation shall be available to determine the quality of service provided to subscribers in the following traffic cases:
a) All originating connections.
b) All incoming connections.
c) Specific incoming trunk groups.
d) Number of calls.
e) The number of times the calling subscriber dials non-existent subscriber numbers.
f) Percentage of completed calls, answered calls.
g) Percentage of non-completed calls:
1. Number of calls when the called subscriber line is free, but the called subscriber does not answer.
2. Number of calls that are not completed because the called subscriber is busy.
3. Total number of completed calls and non-completed calls.
4. Number of calls that do not mature for other reasons.