PAGE

1
Copyright

Copyright Task Force Managed Services EID

Disclaimer

No part of this document may be reproduced in any form without the written permission of
the copyright owner.


Content

1 Abstract ..........................................................................................2
1.1 Task Force Output ...........................................................................3
2 Guideline on Trouble Shooting of MINI-LINK Equipment ..........4
2.1 Prerequisite......................................................................................5
2.2 Preparation ......................................................................................6
2.3 TOC .................................................................................................8

3 Guideline on Trouble Shooting of Power Related Problem....27
3.1 Prerequisite....................................................................................28
3.2 Preparation ....................................................................................29
3.3 TOC ...............................................................................................31

4 Enclosure .....................................................................................58
4.1 Transmission AND RBS Data Report............................................59
4.2 Power Data Report ........................................................................63




PAGE

2





ABSTRACT
After analysis of trouble ticket trend for over 6 months, Managed Services delivery
team notices a pattern of recurring problem related to MINI-LINK and power related
issue.
In an effort to reduce the recurring problem, a task force focusing on the issues
were set up, with a goal to find the root cause of the recurring problem.
The type of MINI-LINK recurring problem that were focused on included:

NPU hanging (stuck in boot process) for AMM 2p B
RSL with measurement of -20dB
Performance degrading on sites with antenna over 1.2m
High temperature leading to MINILINK software hanging in TN R2

Power related problem investigation was focused circuit breaker (MCB) tripping
due to:
Unbalanced power consumption
Insufficient commercial power capacity
Low voltage from commercial power
Phase failure
As an outcome of the investigation, this document is produced as a guideline to
help field maintenance technicians & engineers for troubleshooting similar problem
Ericsson official documentation for MINI-LINK operational and maintenance
guideline should always be the main reference for any operational activities. This
document is to be used specific for the problem described above.









1
PAGE

3
1.1 Task Force Output

DOWNTIME CONTRIBUTOR
8,835 in December (1044 less compared to November)
920 less power related problem; due to battery replacement, faster response on
RST alarm
144 less problem for other issue, mainly transmission, MCB trip cases; due to
task force activity that focused on recurring transmission problem and MCB trip
cases

TT Type: December 2009
Power Outage,
7982, 91%
Access Issue,
34, 0%
RNC, 1, 0%
Lease Line, 22,
0%
Transmission,
157, 2%
BTS, 210, 2%
CME, 308, 4%
Power Outage CME 3rd Party Project
BSC Others Transmission BTS
NODE-B Access Issue RNC Lease Line
0.367%
0.395%
0.440%
0.590%
0.531%
0.704%
0.504%
1.086%
0.228%
0.557%
0.150%
0.791%
0.575%
0.442%
0.290%
0.634%
0.292%
0.654%
0.589%
0.426%
0.372%
0.473%
0.213%
0.572%
0.000%
0.200%
0.400%
0.600%
0.800%
1.000%
1.200%
1.400%
1.600%
Wk
43
Wk
44
Wk
45
Wk
46
Wk
47
Wk
48
Wk
49
Wk
50
Wk
51
Wk
52
Wk
53
Wk 1
Downtime contributor
% - EID % - External
PAGE

4









Guideline on Trouble shooting of MINI-LINK
Equipment











2
PAGE

5

2.1 PREREQUISITES

This chapter describes the hardware tools & software programs that are needed
when trouble shooting shall be done for MINI-LINK equipments. Engineer always
needed to bring the right tools for working with troubleshooting on sites. Please
do not forget to prepare the required sites permit and necessary coordination to
make sure our activities on sites will be done smoothly.
Tools that are needed:
a. Notebook and accessories cables (USB, Ethernet, and RS232).
b. MSS (MINI-LINK Service Software) installed in the notebook.
c. Correct SW version for all equipment if upgrades are necessary (include
the latest software baseline).
d. Basic Tools: digital Volt-meter, LED, screw-driver sets, DDF punch tools,
wrist-stripe, etc
e. HSE Tools
f. If required, always bring BER meter for checking E1 / STM-1 performance.
g. If needed, always bring HW spares (Ex MMU, TRU, NPU, RAU and
dummy) that might need to be replaced.
h. If needed, always bring RAU connectors, electrical insulating tape, butyl
sealing compound for water protect the RAU connector/cable.
Access Permit & Coordination procedures that are needed;
a. Working permit and site key access.
b. Customer approval for equipment down time if needed
c. Always Coordinate with Customer NOC / OMC
d. Approvals from NOC before and after enter the site.






PAGE

6
2.2 PREPARATION
Considering most of trouble-shootings will be done on existing (with live traffic)
sites, we should follow our Network Interruption process.



















Picture 1 Network Interruption process
Prepare
Request Form
to Enter
Customer Site
Information on the request form (Day H)
1.Site name
2.SOW activity on site
3.Person in charge From EID organzation
4.Site access (related with the request for Key
arrangement and Supervisor from Customer)
5. Time frame of the activity
The Form send to
Customer for
approval
1.Customer give approval by signing the
request form (Day H+1)
Engineer Received
Key and information
on PIC from
Customer Spv
All data
approved by
Customer
R
e
v
i
s
e

d
a
t
a

o
n

t
h
e


f
o
r
m

No
Yes
Engineer
arrived on site
Anything
Unusual on
Site
Before enter the site
Call OMC
1.Identify yourself to OMC and Gave information regarding
the task
2. Ask if Site has alarm or not
3.Show / give the letter of assignement ot the spv of the
sites if one exist .Such as IBS (in building solution )site
Call /report to
OMC
1. Check Sorrounding of the site for anything unusual
Such as Grounding missing;Fence broken etc.
2..Check Inside the shelter , Save alarm or status of the
RBS related to Engineers work
3.Take Foto for unusual conditional
Engineer doing
the Activity
Engineer
completing the
activity+ Clean Up
site
Call OMC
before left the
sites
1. Make sure that the site is clean
2. Make sure the RBS status has the sama or less alarm
status compare before engineer enter the shelter
Give notification to OMC that you already completed the
activity on related site
Confirmation on the status site from OMC
Return Sheter Key
to Custome by
filling the report
end
PAGE

7

General key-points before starting our trouble-shooting main activities:
a. Inform Customer NOC team about our activity on site, especially if traffic
interruption will be done, before and after our activity.
b. Check surrounding condition if any Unusual Condition found, such as;
Grounding missing, broken KWH, abnormal indoor temperature, etc.
If needed, take capture / picture as evidences and inform to NOC Team.
c. Check Physical condition of ML equipments especially for LED Status and
Input DC voltage
If we found RED Light or strange Status, check details by LCT for
verification, and take/save Capture & Logs.
For more information, see LED Descriptions MINI-LINK TN
Operating Instructions, Reference [4]
Measure the Input Vdc using a Digital Voltmeter, and compare it with
the specification

Never Turn-Off / Reset the ML equipments before verifying and taking
required information.












PAGE

8
2.3 Table of Content

1 Troubleshooting Procedure ...................................................... 9
1.1 Received Alarm / Fault Description.............................................. 9
1.2 Troubleshooting MLTN............................................................... 10
1.2.1 SW troubleshooting MLTN......................................................... 10
1.2.2 Data Collection MLTN................................................................ 11
1.3 Troubleshooting MLHC .............................................................. 11
1.3.1 SW troubleshooting MLHC on site ............................................. 11
1.3.2 Data Collection MLHC................................................................ 12
1.4 Hardware Installation Check ...................................................... 12
2 Example problem found in Transmission.............................. 13
2.1 Hardware Faulty......................................................................... 13
2.1.1 RAU with RSL 20 dBm............................................................ 13
2.1.2 AMM 2p B faulty......................................................................... 14
2.2 Low RSL..................................................................................... 15
2.3 Switching 1+1 HS failed (MMU2 D)............................................ 18
2.4 HCC/RCC Alarm........................................................................ 20
3 Problem analysis & Escalation Process ................................ 23
4 Replacement Faulty Module.................................................... 24
5 Closing Preparation ................................................................. 25
6 Reporting .................................................................................. 25
7 Reference.................................................................................. 26
PAGE

9
1. TROUBLESHOOTING PROCEDURE
Please follow our general Technical Trouble-shooting
process:

Picture 2 General trouble-shooting process

1.1 Received Alarm / Fault Description
The receiver alarm / fault description should include details about the following:
a. Exact date and time of the problem.
The time shall be given in relation with the time setting in the affected
NEs.
b. Effect of the problem.
Explain the fault events as they occurred, step by step. Specify slot
positions when applicable.
c. Events that might have lead to the fault.
d. Frequency of the fault.
e. Software Baseline (SBL) running on the NE when the fault occurred.

PAGE

10
1.2 Troubleshooting of MLTN
1.2.1 SW Troubleshooting MLTN on site
Please follow below procedure of trouble-shooting MLTN:
a. Connect to the MLTN (using Ethernet or USB cable)
b. Check the event / alarms / fault to evaluate what the problem is
See more details information in documents of:
Fault Management Operations MINI-LINK TN ETSI, Reference [6]
Alarm Descriptions MINI-LINK TN ETSI Description, Reference [7]
Event Descriptions MINI-LINK TN ETSI Description, Reference [8]
c. Verifying Radio Link Configuration Parameters
Verify that all hop setup parameters are set and correspond to the value in
SID / PQR, such as: RSL (Received Signal Level), Tx power, Switching
mode, Frequency setting, etc.
d. Checking for RF Interference
If the Radio Link reports unexpectedly bad BER performance but RF input
level is normal, the receiver might be interfered by external RF sources.
Check RF interference using Far-end Tx-off procedure.
e. Use a loop on the unit that having problem to trace the fault (i.e.: RF Loop,
IF Loop, etc).
f. Use built-in BERT (Bit Error Ratio Tester) or external BER meter to verify
or trace the fault.
g. Restarting the NE (Network Element)
In some cases, if required, we can do a Warm or Cold Restart of the NE.



A cold restart will disturb the traffic.
Always collect Logs before restarting the NE since the alarm and
event logs, as well as power cycling information, are deleted at
both cold and warm restarts and potentially valuable information is
lost.
h. Take capture of specific problems.
i. Check and (if required) perform SW upgrade if its an older SW-baseline
version.


PAGE

11
The SW version should be checked with O&M to synchronize that the
MINI-LINK has the same SW baseline in all MLTN.
Please perform a software upgrade to the new software baseline according
to the MINI-LINK TN ETSI Operating Instruction, Reference [2] or MINI-
LINK Craft User Interface Descriptions, Reference [3], chapter Software
Upgrade.
For details about recommended upgrade paths of MLTN, please also see
the Compatibility Information and Release Note documents.

1.2.2 Data Collection MLTN
Take following data from MLTN terminals for any further technical analysis or
escalation:
a. Error log file and Event log / history
Always collect alarm logs and event log before any warm/cold restart or
power cycling.
b. Alarm list (needs to be done before power reset)
c. Get the configuration file and saved report if you dont have the latest file
d. Collect PM (Performance Management) data if PDH/SDH MMUs is used
(Near & Far end)

1.3 Troubleshooting of MLHC
1.3.1 SW Troubleshooting MLHC on site
Please follow below procedure of trouble-shooting MLHC:
a. Connect to the MLHC (using Ethernet or Serial OM cable)
b. Take Capture of existing parameters needed and Save Configuration for
backup purposes
c. Check the alarms to evaluate what the problem is.
d. Always upload the Alarm logs of MLHC
e. Verifying Radio Link Configuration Parameters refer to SID / PQR
f. Checking for RF Interference
g. Use loops to trace were the problem is (example : RF Loop, IF Loop, SPI
Loop)
h. If necessary, use external BER meter to verify or trace the fault.
i. Always take capture of specific problems.
PAGE

12
j. Make a save before any power cycling.

Note: If you have not save before power cycle and you have made
any changes the
TRU will go back to the latest saved configuration.
k. Perform SW upgrade if its an older SW version. This should be checked
from the O&M what version that shall be used.

1.3.2 Data Collection MLHC
Take following data from MLHC terminals for any further technical analysis and
escalation:
a. Alarm logs from (Near-end and Far-end). Needs to be collected before
power reset.
b. Performance log (monitoring data) from Near-end and Far-end.
If performance data is not available, follow the performance setup in
as document of Settings for performance measurements in Mini-Link
High Capacity, Reference [13]
c. Inventory data (Near-end and Far-end)
d. Configuration file

1.4 Hardware Installation Check
Aside checking the software status, in some conditions we need to check physical
installation also:
a. FAN unit correctly installed on MLTN / MLHC.
b. Dummy fronts installed (MLTN).
c. Grounding completely & properly installed according to the installation
manuals
d. Traffic and DC Cabling/Connectors properly installed.
See more details in document of Installing Indoor Equipment MINI-LINK TN
ETSI Installation Instructions, Reference [1].
e. Radio cable and the connectors properly installed.
(See more details in document of Radio Cable Check [13].
f. All connectors tightened (DC/traffic/radio)
g. Check power distribution (battery, DC power level and MCB Ampere).
PAGE

13
h. Modem units correctly inserted and tightened
i. If the problem is still intermittent, check interfaces on front and the
backplanes for broken or damage pins

2. Example Problem found in Transmission
2.1 Hardware Faulty
2.2 Low RSL
2.3 Switching 1+1 HS failed (MMU2 D)
2.4 HCC/RCC Alarm

2.1 Hardware Faulty
2.1.1 RAU with RSL -20 dBm
In the Radio Link Alarm, we found the RSL of the RAU is 20 dBm. In 1+1 HS
configuration, sometimes the switch can not work caused by this problem. There is
a known problem with a component handling the attenuation on the RAU.
The following steps must follow to solve the problem;
1. Prepare RAU with same product code.
2. Unplug jumper cable on MMU.
3. Replacement RAU with the new one.
4. Plug jumper Cable onto MMU.
5. Reset Performance in Near End and Far End
6. Send the RAU to Ware House with BLUE TAG FORM.
Note: Write in Remark Column; RAU faulty with RSL 20 dBm.



PAGE

14
2.1.2 AMM 2p B Faulty
AMM 2p B faulty with problem NPU stuck in Boot Process. There is a known
problem with a bad soldering of the component in the backplane. The Fault LED in
NPU was ON.
The following steps must follow to solve this problem;
1. Prepare new AMM 2p B
2. Turn off DC Source. Unplug DC cable from AMM 2p B (faulty).
3. Unplug some modules from AMM 2p B: NPU3, MMU and FAU4.
4. Uninstall AMM 2p B (faulty).
5. Install new AMM 2p B.
6. Plug in some modules into new AMM 2p B: NPU3, MMU and FAU4.
7. Plug in DC Cable to AMM 2p B.
8. Turn ON DC Source then pressing the BR button of NPU (2-3 seconds
after Turn ON DC source).
9. The LED BR in the NPU will flash. It means, the NPU in Installation mode
status.
10. Log in to ML TN with your laptop.
11. Activate the configuration from RMM card.
12. If AMM 2p B does not have RMM, You have to activate configuration with
LOAD CONFIGURATION FILE from your laptop.
13. Otherwise, you should create configuration by manually.
14. Call NOC to check the status of our equipment (RBS and Transmission).
15. Send AMM 2p B to ware house with BLUE TAG FORM.
Note: Write in remark column; AMM faulty with problem NPU stuck in Boot
Process.


PAGE

15
2.2 Low RSL
Low RSL can cause performance degradation in our link. The RSL of the Link
have to follow the value from the PQR. The tolerance value is +- 4 dB from
PQR. Otherwise we have to realignment the antenna to get expected RSL or
reroute the link if the link get obstacle path.
Sometime, Low RSL can happened cause by shifted antenna especially for
antenna over than 1.2 m which do not have properly for side strut installation of
antenna. Please see picture below;




Picture 3 Improperly side strut installation on Tower



PAGE

16









Picture 4 Improperly side strut installation on Pole

The following steps must follow to solve this problem (Low RSL caused by
Shifted antenna);
1. We have to make sure position of antenna in NE and FE site can
allow installation side strut with the right way. Please see picture
below ;








Picture 5 Proper angle for attaching the side strut
PAGE

17
2. If needed we have to reinstall antenna on NE and FE;
a. Change leg of tower for attaching antenna
b. Change handle of antenna from right to left side or vice
versa.
3. If antenna attaching in pole we need install additional mounting for
attaching side strut.
4. Then realignment antenna to get expected RSL (PQR).
5. Install side strut refer from standard installation document.
6. Coordination to NOC to check our equipment status.

Note: For above activity, it shall cause traffic disturbance for 4
5 hours. So, please make coordination with the
customer for permit activity.
Please see the picture below for properly side strut installation;











Picture 6 Properly side strut installation on tower

PAGE

18












Picture 7 Properly side strut installation on pole


2.3 Switching 1+1 HS failed (MMU2 D)
When the RAU N has used for MMU2 D, The switching protection in 1+1
HS does not work. It is caused by software compatibility in the RAU N.
Note: If using RAU N with MMU2 D, software of RAU have to over than
R2X.
The following steps must follow to solve this problem;
1. Log in to ML TN
2. Go to the inventory Tab then Check software of the RAU N in NE
and FE.


PAGE

19














Picture 8 RAU Software in inventory list

Note: RAU in Slot 4 is OK, over than R2X
RAU in Slot 5 is not OK, below than R2X

3. Upgrade software for RAU N with Software RAU over than R2X,
example R3C.
4. Testing switch protection to verify the switch is working.
5. Coordination with NOC to check our equipment status.





PAGE

20
2.4 HCC/RCC Alarm

HCC Alarm means communication is lost on Hop Communication Channel,
between MMU and far-end MMU.

RCC Alarm means Communication is lost on the Radio Communication
Channel (RCC), between MMU and RAU.

Those problems were caused by bad connection between MMU and RAU or the
modules are fault.

Picture 9 Radio Link Alarm


PAGE

21



Picture 10 Alarm List

The following steps must follow to solve this problem;
1. Log In to ML TN.
2. Go to Radio Link Alarm Tab then found which slot have problem RCC.
3. Check installation of connector coaxial at near end and far end.
4. If needed, reinstall connector coaxial with the right way.
5. Coordination with NOC to check our equipment status.





PAGE

22
Please see the picture below for bad installation;


















Picture 11 Coaxial connector without fold grounding cable and
2.5mm of the dielectric





















Picture 12 Coaxial connector without 2.5mm jacket isolation of dielectric




PAGE

23

Please see the picture below for good installation;


Picture 13 GOOD installation

3. PROBLEM ANALYSIS & ESCALATION PROCESS
After getting enough information from sites, we need to analyze it to get the
correct solution.
Please always refer to:
a. Ericsson Mini-Link technical documentations.
Some of those as listed in the Reference chapter at page 11, or more
complete documents in Alex / Ericsson CPI documents.
b. Check to the previous applicable technical report.
The purpose is to minimize our trouble-shooting duration. Search any
similar and applicable report that can be reused in our problem. We can
PAGE

24
get those from previous Trouble-shooting Report, CSR report, Service
Advice document, as well as some sharing experiences in Ericsson
Knowledge Based.
In case of internal team can not solve the problem, especially which related with
competence and product issue, we can escalate it to higher level support.
Any escalation to 1
st
or 2
nd
line support will need a CSR (Customer Support
Request). A CSR is primarily used in situations of a non-emergency nature,
indicating a software or hardware design-related problem. It is also used to ask
general questions of a technical nature. An emergency request is normally
taken care of in another routine, but it is always registered as a CSR afterwards
for follow-up reasons. Usually, only one issue can be addressed per CSR.
We shall enclose relevant and complete troubleshooting data shall in the CSR
as the required procedure. See Data Collection Guidelines MLTN Operating
Directions, Reference [5].

4. REPLACEMENT FAULTY MODULE
In case there is/are faulty module/s found based on the fault tracing phase, we
can replace that plug-in unit/s accordingly. Please take below precaution and
procedure carefully:
a. Identifying Current Hardware and Software
b. Checking the Compatibility
c. Uploading Configuration File when Replacing a NPU or RMM
d. Required Tools and Equipment
e. Prepare for Software Upgrade: FTP server and SBL firmware
f. Procedure to replace the Hardware module
g. Concluding Routines of checking any active alarms, handling faulty unit,
etc
PAGE

25
See details in Replacing a Radio or Plug-In Unit MLTN Operating Instruction,
Reference [11]

5. CLOSING PREPARATION
After activities had been done, ensure that the following actions have been
performed:
a. Reset Performance Log (if needed to monitor performance link for few
days)
b. Reset alarm list and Event history (if needed to monitor performance
link for a few days)
c. Inform customer NOC team that our activity had been done.
d. Get confirmation from NOC that all equipments are back to normal
operation and there are no active alarms caused by our activity.
e. Clean up the site for any trashes from our activity.
f. Lock all doors and leave the site.

6. REPORTING
After activities had been done, spare your time to make report to your
supervisor such as;
a. Create a Troubleshooting Report.
b. Complete raw data (alarm list, even log, error log, save report and any
capture) as evidence.
c. Collect Photo as evidence (if required).
d. Fill BLUE TAG Form for any HW Faulty and send to the ware house.
e. Please fill-in completely as described in HWS RDN (Repair delivery
Note), Reference [12]











PAGE

26


7. REFERENCE
[1] Indoor Installation Instruction Mini-link TN ETSI, 1531-CSH 109 32/1-S1 Uen
[2] Operating Instruction Mini-link TN R3, 1543-CSH 109 32/1-V1 Uen
[3] MINI-LINK Craft User Interface Descriptions, ML Craft 2.2, 7/1551-CSH 109 32/1-V1
Uen
[4] LED Description MINI-LINK TN ETSI, 24/1543-CSH 109 32/1-V1 Uen
[5] Data Collection Guidelines MLTN Operating Directions, 34/1543-CSH 109 32/1-V1
Uen
[6] Fault Management Operations MINI-LINK TN ETSI, 4/1543-CSH 109 32/1-V1 Uen
[7] Alarm Descriptions MINI-LINK TN ETSI Description, 5/1543-CSH 109 32/1-V1 Uen
[8] Event Descriptions MINI-LINK TN ETSI Description, 9/1551-CSH 109 32/1-V1 Uen
[9] Troubleshooting MINI-LINK TN ETSI Operating Guideline, 5/154 43-CSH 109 32/1-V1
Uen
[10] Troubleshooting Guideline by EID/OP/MR Ronny Stralhed
[11] Replacing a Radio or Plug-In Unit MLTN Operating Instruction, 11/1543-CSH 109
32/1-V1 Uen
[12] HWS RDN (Repair delivery Note), 2/1546-FAP 130 495 Uen
[13] Settings for performance measurements in Mini-Link HC, EAB/FBM/LG-07:001 Uen
[14] Radio Cable Check by MO/EAB/JT/GG EMWCRM





PAGE

27










Guideline on Trouble Shooting of Power Related
Problem











3
PAGE

28
3.1 PREREQUISITES

This chapter describes the hardware tools & software programs that are needed
when trouble shooting shall be done for MINI-LINK equipments. Engineer always
needed to bring the right tools for working with troubleshooting on sites. Please do
not forget to prepare the required sites permit and necessary coordination to make
sure our activities on sites will be done smoothly.
Tools that are needed:
a. Notebook and accessories cables (USB, Ethernet, and RS232).
b. Correct SW version for all equipment if upgrades are necessary (include
the latest software baseline).
c. Basic Tools: digital Volt-meter, LED, screw-driver sets, DDF punch tools, ,
etc
d. HSE Tools
e. If needed, always bring HW spares (power & grounding cable, MCB etc a)
that might need to be replaced.
Access Permit & Coordination procedures that are needed;
a. Working permit and site key access.
b. Customer approval for equipment down time if needed
c. Always Coordinate with Customer NOC / OMC
d. Approval from NOC before & after enter site









PAGE

29
3.2 PREPARATION
Considering most of trouble-shootings will be done on existing (with live traffic)
sites, we should follow our Network Interruption process.



















Picture 1 Network Interruption process
Prepare
Request Form
to Enter
Customer Site
Information on the request form (Day H)
1.Site name
2.SOW activity on site
3.Person in charge From EID organzation
4.Site access (related with the request for Key
arrangement and Supervisor from Customer)
5. Time frame of the activity
The Form send to
Customer for
approval
1.Customer give approval by signing the
request form (Day H+1)
Engineer Received
Key and information
on PIC from
Customer Spv
All data
approved by
Customer
R
e
v
i
s
e

d
a
t
a

o
n

t
h
e


f
o
r
m

No
Yes
Engineer
arrived on site
Anything
Unusual on
Site
Before enter the site
Call OMC
1.Identify yourself to OMC and Gave information regarding
the task
2. Ask if Site has alarm or not
3.Show / give the letter of assignement ot the spv of the
sites if one exist .Such as IBS (in building solution )site
Call /report to
OMC
1. Check Sorrounding of the site for anything unusual
Such as Grounding missing;Fence broken etc.
2..Check Inside the shelter , Save alarm or status of the
RBS related to Engineers work
3.Take Foto for unusual conditional
Engineer doing
the Activity
Engineer
completing the
activity+ Clean Up
site
Call OMC
before left the
sites
1. Make sure that the site is clean
2. Make sure the RBS status has the sama or less alarm
status compare before engineer enter the shelter
Give notification to OMC that you already completed the
activity on related site
Confirmation on the status site from OMC
Return Sheter Key
to Custome by
filling the report
end
PAGE

30

General key-points before starting our trouble-shooting main activities:
a. Inform Customer NOC team about our activity on site, especially if traffic
interruption will be done, before and after our activity.
b. Check surrounding condition if any Unusual Condition found, such as;
Grounding missing, broken KWH, abnormal indoor temperature, etc.
If needed, take capture / picture as evidences and inform to NOC Team.
c. Check Physical condition of ML equipments especially for LED Status and
Input DC voltage
If we found RED Light or strange Status, check details by LCT for
verification, and take/save Capture & Logs.
For more information, see LED Descriptions MINI-LINK TN
Operating Instructions, Reference [4]
Measure the Input Vdc using a Digital Voltmeter, and compare it with
the specification

Never Turn-Off / Reset the ML equipments before verifying and taking
required information.












PAGE

31
3.3 Table of Content

1 Mini Circuit Breaker (MCB).................................................................32
1.1 Definition MCB.......................................................................................32
1.1.1 PLN MCB...............................................................................................32
1.1.2 ACPDB MCB.........................................................................................33
1.1.2.1 Main MCB ACPDB ................................................................................33
1.1.2.2 Utility MCB ACPDB ...............................................................................33
1.1.3 DCPDB MCB.........................................................................................34
1.1.3.1 Main MCB Rectifier................................................................................34
1.1.3.2 Utility MCB Rectifier / PBC 6500...........................................................34
1.1.3.3 Battery MCB Rectifier ............................................................................35
1.1.3.4 19 Rack MCB / DCPDU.......................................................................35
2 Power Root Cause Analysis...............................................................36
2.1 MCB Trip Problem Identification............................................................36
2.2 Cause of MCB Trip................................................................................36
2.2.1 Trip of MCB PLN ...................................................................................36
2.2.2 MCB PLN & Main ACPDB.....................................................................36
2.2.3 Trip of MCB Utility ACPDB....................................................................37
2.2.4 MCB DCPDB.........................................................................................37
2.3 Analysis .................................................................................................37
2.3.1 Short Circuit...........................................................................................37
2.3.2 Unbalance Power Consumption............................................................37
2.3.3 Air Conditioning Problem.......................................................................38
2.3.4 Insufficiency PLN Capacity....................................................................38
2.3.5 PLN Problem; Phase Failure, Low Voltage...........................................42
2.3.6 Short Circuit at Air Conditioning Controller ...........................................43
2.3.7 Short Circuit at Air Conditioning ............................................................44
2.3.8 MCB Trip at DOU for MCB DCPDU (19 rack)......................................44
3 Action Taken Recommendation.........................................................46
3.1 Check Installation ..................................................................................46
3.2 Balancing Power Consumption .............................................................46
3.2.1 Indoor ....................................................................................................46
3.2.2 Outdoor..................................................................................................47
3.3 PLN Capacity.........................................................................................49
3.3.1 PLN Capacity Indoor Sites ....................................................................49
3.3.2 PLN Capacity Outdoor Sites .................................................................50
3.4 Air Conditioning Maintenance ...............................................................53
3.4.1 Measurement AC Current for Air Conditioning......................................53
3.4.2 Air Conditioning Phase Controller .........................................................53
3.5 Power Source for DCPDB at 19 Rack..................................................54
3.6 Exhaust Fan Status ...............................................................................56
4 Reference .............................................................................................57
PAGE

32

1 Mini Circuit Breaker (MCB)
1.1 Definition MCB
1.1.1 PLN MCB
Location : KWH panel
Type : Blue toggle; CL curve
Band : Merlin Gerin, ABB, Vyckler, J&P, Okachi

















MCB 1 phase 1 pole
MCB 3 phase 1 pole
PAGE

33
1.1.2 ACPDB MCB
1.1.2.1 Main MCB ACPDB
Location : ACPDB panel
Type : Black toggle; C curve; MCB 3 phase-1 pole
Band : Merlin Gerin, ABB






1.1.2.2 Utility MCB ACPDB
Location : ACPDB panel
Type : Black toggle; C curve; MCB 1 phase-1 pole
Band : Merlin Gerin, ABB










Outdoor ACPDB
Indoor ACPDB
PAGE

34
1.1.3 DCPDB MCB
1.1.3.1 Main MCB Rectifier
Location : Rectifier
Type : Black toggle; C curve; MCB 1 phase-1 pole
Band : Merlin Gerin, ABB, Nader









1.1.3.2 Utility MCB Rectifier/PBC 6500
Location : Rectifier or PBC 6500
Type : Black toggle; C curve; MCB 1 pole
Band : Merlin Gerin, ABB, Nader






Main MCB Rectifier
Utility MCB Rectifier Utility MCB PBC6500
PAGE

35
1.1.3.3 Battery MCB Rectifier
Location : Rectifier or PBC 6500
Type : Black toggle; C curve; MCB -1 pole
Band : Merlin Gerin, ABB, Nader








1.1.3.4 19 Rack MCB / DCPDU
Location : 19 Rack
Type : Black toggle; C curve; MCB -1 pole
Band : Merlin Gerin, ABB, Nader
DCPDU : for Transmission equipment
DCPDB RBS : for RBS







DCPDB RBS for RBS
DCPDU - Transmission
MCB Battery Rectifier MCB Battery PBC 6500
PAGE

36
2 Power Root Cause Analysis
2.1 MCB Trip Problem Identification
Base on data trouble ticket week 39-40, percentage of MCB trip:
a. MCB PLN : 60% (14 times)
b. MCB PLN & Main ACPDB : 26% (6 times)
c. MCB Utility ACPDB : 9% (2 times)
d. MCB DCPDB : 5% (1 times)
2.2 Cause of MCB Trip
2.2.1 Trip of MCB PLN

A. Cause MCB trip Indoor Sites
a. Short Circuit
b. Unbalance power consumption
c. Air Conditioning problem; high AC current (out off manufacture standard)
d. Insufficient PLN capacity
e. PLN Problem :Low Voltage PLN, Phase failure

B. Cause MCB Outdoor Sites
a. Unbalance power consumption
b. Insufficient PLN capacity
c. PLN Problem :Low Voltage PLN, Phase failure
2.2.2 MCB PLN & Main ACPDB

A. Cause MCB trip Indoor Sites
a. Short Circuit
b. Unbalance power consumption
c. Air Conditioning problem; high AC current (out off manufacture standard)
d. Insufficient PLN capacity
e. PLN Problem :Low Voltage PLN, Phase failure

B. Cause MCB Outdoor Sites
a. Unbalance power consumption
b. Insufficient PLN capacity
c. PLN Problem :Low Voltage PLN, Phase failure

Location : ACPDB Indoor sites
Cause MCB Trip :
a. Short circuit at MCB use for Air Conditioning controller.
b. Short circuit at MCB use for Air Conditioning
PAGE

37
2.2.3 Trip of MCB Utility ACPDB
Location : ACPDB Indoor sites
Cause MCB Trip :
a. Short circuit at MCB use for Air Conditioning controller.
b. Short circuit at MCB use for Air Conditioning
2.2.4 MCB DCPDB
Location : Rectifier/PBC 6500 Indoor sites
Cause MCB Trip : Insufficiency rate of MCB DCPDU (19 rack) .
2.3 Analysis
2.3.1 Short Circuit
A short circuit between phase - neutral due to the destruction of AC Contactor,
outdoor unit, lamp, dc fan, rectifier or all equipment that connected to power.
This results in an excessive electric current (over current), and potentially causes
circuit damage, overheating, fire or explosion
In mains circuits, short circuits are most likely to occur between two phases,
between a phase and neutral or between a phase and earth (ground). Such short
circuits are likely to result in a very high current and therefore quickly trigger an
over current protection device.
2.3.2 Unbalance Power Consumption

Indoor:
Configuration of connecting power Air Conditioning, Rectifier/PBC module
unbalance to all phase, It is making power for each phases are not same or
higher than MCB PLN

Unbalancing Configuration of power - Indoor
Phase
R S T Remark
Air conditioning
Rectifier / PBC 2 unit 1 unit 1 unit
Lamp, others
Note: = power connection

PAGE

38

Outdoor:
Configuration of connecting power PSU module unbalance to all phase, It is
making power for each phases are not same or higher than MCB PLN

Unbalancing Configuration of power - Outdoor
Phase
R S T Remark
PSU RBS 2G 2 unit 1 unit 1 unit
PSU RBS 3G 1 unit 1 unit 1 unit
Lamp, others
Note: = power connection

2.3.3 Air Conditioning Problem
Some problems with the Air Conditioning are:

The high AC current Air Conditioning cause by problem at Air Conditioning
outdoor unit.
Short circuit Air Conditioning outdoor unit
The high AC current Air Conditioning has make insufficiency PLN MCBm and
short circuit make PLN MCB and Air Conditioning MCB trip

2.3.4 Insufficiency PLN Capacity
Indoor

Location : sites with PBC 6500
Cause : Insufficiency PLN capacity
Description :
Indoor site use PBC 6500
o PSU : 4x1400 watt
o Battery : 3x100Ah
o PLN : 10.6 kVA (MCB 3x16A)
o Air Conditioning : non Inverter







PAGE

39


Configuration of power Indoor
Phase
R S T Remark
Air conditioning
PBC 6500 1 unit 1 unit 2 unit
Lamp, others

Current Analysis Full load
Phase
R S T Unit
Air Conditioning 1892 1892 VA
RBS 2116 1879 1879 3757 VA
Lamp 125 VA

Voltage 210 210 210 Volt
Total
18 18 18 Amp
PLN MCB 16 16 16 Amp

Note: Will be trip at full consumption

Outdoor

Location : sites with 2G RBS 2116
Cause : Insufficiency PLN capacity due 4 installed PSU
Description :
Outdoor site RBS 2G 2116
o PSU : 4x1520 watt
o Battery : 4x100Ah
o PLN capacity : 10.6 kVA (MCB PLN 3x16A)









PAGE

40


Configuration of power - Outdoor
Phase
R S T Remark
PSU RBS 2G 2 unit 1 unit 1 unit
Lamp, others


Current Analysis Full load
Phase
R S T Unit
RBS 2116 3757 1879 1879 VA
Lamp 125 VA

Voltage
210
210 210 Volt
Total 18 9 10 Amp
PLN MCB 16 16 16 Amp

Note: Will be trip at full consumption

2.
Location : sites with 2G 3G (RBS 2116 + RBS 3116/3107)
Cause : 4 installed PSU
Description :
Outdoor site RBS 2G 3G (RBS 2116 + RBS 3116)
o PSU RBS 2G : 4x1520 watt
o Battery RBS 2G : 4x100Ah
o PSU RBS 3G : 3x1400 watt
o Battery RBS 3G : 2x100Ah
o PLN capacity : 13.2 kVA (MCB PLN 3x20A)












PAGE

41


Configuration of power - Outdoor
Phase
R S T Remark
PSU RBS 2G 2 unit 1 unit 1 unit
PSU RBS 3G 1 unit 1 unit 1 unit
Lamp, others

Current Analysis Full load
Phase
R S T Unit
RBS 2116 3757 1879 1879 VA
RBS 3116 1730 1730 1730 VA
Lamp 125 VA

Voltage
210 210 210 Volt
Total 26 17 18 Amp
PLN MCB 20 20 20 Amp

Note: Will be trip at full consumption

3
Location : sites with 2G RBS 2116
Cause : Insufficiency PLN capacity due 4 installed PSU 2G
Description:
Outdoor site (RBS 2116 + RBS 3116+ Nobi TRM)
o PSU RBS 2G : 3x1520 watt
o Battery RBS 2G : 4x100Ah
o PSU RBS 3G : 3x1400 watt
o Battery RBS 3G : 2x100Ah
o Nobi TRM : 2x2000 watt
o Battery Nobi TRM : 2x100Ah
o PLN capacity : 13.2 kVA (MCB PLN 3x20A)








PAGE

42


Configuration of power Outdoor
Phase
R S T Remark
PSU RBS 2G 1 unit 1 unit 1 unit
PSU RBS 3G 1 unit 1 unit 1 unit
Rectifier Nobi TRM 1 unit 1 unit
Lamp, others


Current Analysis Full load
Phase
R S T Unit
RBS 2116 1879 1879 1879 VA
RBS 3107 1730 1730 1730 VA
Nobi TRM 1167 1167 0 VA
Lamp 125 VA

Voltage 210 210 210 Volt
Total
23 23 17 Amp

PLN MCB 20 20 20 Amp

Note: Will be trip at full consumption
2.3.5 PLN Problem; Phase Failure, Low Voltage
Cause : PLN voltage drop bellow 190V AC
Description :
PLN Voltage drop (Below 190V AC) led to increase AC current and
PLN capacity is not sufficient to make power requirement.



PAGE

43

Current Analysis Full load
(Nominal Voltage)
Current Analysis Full load
(Under Voltage)
Phase
Phase

R S T Unit

R S T Unit
RBS 2116 1879 1879 1879 VA

RBS 2116 1879 1879 1879 VA
RBS 3116 1730 1730 1730 VA

RBS 3116 1730 1730 1730 VA
Lamp 125 VA

Lamp 125 VA



Voltage 210 210 210 Volt

Voltage 180 180 180 Volt
Total 17 17 18 Amp

Total 20 20 21 Amp



PLN MCB 20 20 20 Amp

PLN MCB 20 20 20 Amp



- High AC Current at under voltage, makes PLN MCB not sufficient.
- PLN MCB will be trip

2.3.6 Short Circuit at Air Conditioning Controller
Short circuit location : Air Conditioning controller using relay Omron MY 2
Cause : the connection R phase and S phase as controller to
close
Description:
There are Air Conditioning controller designs:

a. Air Conditioning controller relay 1-phase
b. Air Conditioning controller relay 2-phase using relay Omron MY 2
c. Air Conditioning controller relay 2-phase using CAD 32 M7








PAGE

44





















Air Conditioning controller using relay Omron willing to use 2-phase for the work
of Air Conditioning. The advantage using 2-phase controller is if one phase is off
the other phase will be backup. Since use 2-phase to controller Air Conditioning
than there will be 2 voltages into relay.
The relay Omron found connection 2-phase is to narrow, and if the 2-phase are
start at the same time it cause short circuit than MCB Air Conditioning will trip

2.3.7 Short Circuit at Air Conditioning
Short circuit location : Air Conditioning outdoor unit
Cause : Short of body Air Conditioning
Description :
Short circuit because Air Conditioning often switch off

2.3.8 MCB Trip at DOU for MCB DCPDU (19 rack)
Location MCB Trip : DOU 2x10A
Cause : Insufficient of MCB rate as power source DCPDU (19 rack)
Description :
Power Line Connection:
Relay Omron MY 2 CAD 32 M7
PAGE

45
DOU 1x125A connected to DCPDB RBS-----Connected to RBS 2G
DOU 2x10A connected to TRM 19 rack (via DCPDU)
o Connected AMM20p
o Connected exhaust fan
Power Analysis:
Total Power consumption = 500 watt ( -48V; 11 Amp)
TRM Amm20p (5 radio) = 300 watt
DC fan = 200 watt




















Picture: Power cable connection
PAGE

46
3 Action Taken Recommendation
3.1 Check Installation
Check tightened of power cable connection
Check for short circuit:
Use buzzer (AVO meter) to no short circuit at the system KWH, ACPDB
Measure at MCB Air Conditioning, MCB Lamp, etc
Connection one probes to neutral bar and other toon top MCB connection
biiiiiiiiip sound mean there are short circuit

3.2 Balancing Power Consumption
3.2.1 Indoor
Connected Air Conditioning power cable to R phase and S phase
Maximum 4 unit PSU/Rectifier module and connected with configuration; 1
unit at R phase, 1 unit at S phase, 2 unit at T phase

Configuration of power Indoor
Phase
R S T Remark
Air conditioning
PBC 6500 / Rectifier 1 unit 1 unit 2 unit
Lamp, others
Procedure to balancing power consumption:
Turn on both Air Conditioning, wait until outdoor unit are working
Measure current and voltage for R phase, S phase and T phase
Check power connection of Air Conditioning:
o 1 unit at R phase, 1 unit at S phase, 1 unit at T phase (if available)
Check power connection of rectifier module or PBC 6500 PSU :
o Maximum 4 unit PSU/Rectifier
o Configuration; 1 unit at R phase, 1 unit at S phase, 2 unit at T phase
o If available 5 PSU/module removed or unplug, make sure no alarm appear

PAGE

47
3.2.2 Outdoor
Maximum number PSU at RBS 2G and 3G are = 3 unit
Incase there Nobi rectifier enclosure the maximum rectifier module = 3 unit
Table configuration PSU connection
Configuration of power Outdoor
Phase
R S T Remark
PSU RBS 2G 1 unit 1 unit 1 unit
PSU RBS 3G 1 unit 1 unit 1 unit
Rectifier Nobi TRM 1 unit 1 unit
Lamp, others
Procedure balancing power
Using Clamp- Ampere Meter to measure AC current for R phase, S
phase and T phase
Check PLN MCB ratting (PLN Capacity)
Check power connection of rectifier module or RBS PSU:
o PLN 6,6 kVA (MCB 3x10A),
RBS 2G (3 PSU) or
Nobi TRM (2-3 mdl)
o PLN 10.6 kVA (MCB 3x16A),
RBS 2G (3 PSU) + Nobi TRM (2 mdl)
o PLN 13.2 kVA (MCB 3x20A),
RBS 2G (4 PSU),
RBS 2G (3 PSU) + RBS 3G (3 PSU)
o PLN 16.5 kVA (MCB 3x25A),
RBS 2G (3 PSU) + RBS 3G (3 PSU) +Nobi Rectifier (3 PSU)
Check MCB ratting at ACPDB
o MCB for RBS 2G, RBS 3G and Nobi Rectifier
o MCB 3x16A (minimum)
o MCB 3x20A (recommendation)
PAGE

48
Site 2G 3G with PLN capacity 13.2 kVA, RBS 2G have 4 PSU, as
temporary solution do unplug 1PSU (PSU number 4), with no alarm
appear
Site 2G 3G Nobi Rectifier and Nobi TRM with PLN capacity 13.2 kVA, as
temporary solution do unplug 1PSU RBS 2G (PSU number 1) and
Unplug 1 PSU RBS 3G (PSU number 2), with no alarm appear

Configuration of power Outdoor
Phase
R S T Remark
PSU RBS 2G 0 unit 1 unit 1 unit
PSU RBS 3G 1 unit 0 unit 1 unit
Rectifier Nobi TRM 1 unit 1 unit 1 unit
Lamp, others


Current Analysis Full load
Phase
R S T Unit
RBS 2G 1879 1879 0 VA
RBS 3G 1730 0 1730 VA
Nobi TRM 0 1167 1167 VA
Lamp 0 VA

Voltage 208 200 198 Volt
Total 17 15 15 Amp

PLN MCB 20 20 20 Amp







PAGE

49
3.3 PLN Capacity
3.3.1 PLN Capacity Indoor Sites
1. PLN 10.6 kVA (MCB PLN 3x16A)
a. Air Conditioning : 2 PK inverter (AC current 7.4A ; 220V AC)
b. Rectifier : 2x200 watt or 3x2000 watt









Current Analysis Full load
Phase
R S T Unit
Air Conditioning 1628 1628 VA
Rectifier 1069 1069 1069 VA
Lamp 125 VA

Voltage 210 210 210 Volt
Total 13 13 6 Amp

PLN MCB 16 16 16 Amp






PAGE

50

2. PLN 13.2 kVA (MCB PLN 3x20A)
a. Air Conditioning : 2 PK non inverter (AC current 10.6A ; 220V AC)
b. Rectifier or PBC 6500 : maximum 4 unit








Current Analysis Full load
Phase
R S T Unit
Air Conditioning 2438 2438 VA
Rectifier 1069 1069 2138 VA
Lamp 125 VA

Voltage 210 210 210 Volt
Total 17 17 11 Amp

PLN MCB 20 20 20 Amp

3.3.2 PLN Capacity Outdoor Sites
1. PLN 6.6 kVA (MCB 3x10A),
RBS 2G (3 PSU) or
Nobi TRM (2-3 mdl)



PAGE

51

Configuration of power Outdoor Current Analysis Full load
Phase Phase
R S T

R S T Unit
PSU RBS 2G 1 unit 1 unit 1 unit

RBS 2116 1879 1879 1879 VA
Lamp, others

Lamp 125 VA


Voltage 210 210 210 Volt


Total 9 9 9 Amp


PLN MCB 10 10 10 Amp

2. PLN 10.6 kVA (MCB 3x16A),
RBS 2G (3 PSU) + Nobi TRM (2 mdl)

Configuration of power Outdoor Current Analysis Full load
Phase Phase
R S T

R S T Unit
PSU RBS 2G 1 unit 1 unit 1 unit

RBS 2116 1879 1879 1879 VA
Nobi TRM 1 unit 1 unit

Nobi TRM 1297 1297 VA
Lamp, others

Lamp 125 VA


Voltage 210 210 210 Volt


Total 15 15 10 Amp


PLN MCB 16 16 16 Amp










PAGE

52
3. PLN 13.2 kVA (MCB 3x20A),
RBS 2G (4 PSU),
RBS 2G (3 PSU) + RBS 3G (3 PSU)

Configuration of power Outdoor Current Analysis Full load
Phase Phase
R S T R S T Unit
PSU RBS 2G 1 unit 1 unit 1 unit RBS 2116 1879 1879 1879 VA
PSU RBS 3G 1 unit 1 unit 1 unit RBS 3116 1370 1370 1370 VA
Lamp, others Lamp 125 VA
Voltage 210 210 210 Volt
Total 18 18 18 Amp
PLN MCB 20 20 20 Amp


4. PLN 16.5 kVA (MCB 3x25A),
RBS 2G (3 PSU) + RBS 3G (3 PSU) + Nobi Rectifier (3 PSU)
Configuration of power Outdoor Current Analysis Full load
Phase Phase
R S T R S T Unit
PSU RBS 2G 1 unit 1 unit 1 unit RBS 2116 1879 1879 1879 VA
PSU RBS 3G 1 unit 1 unit 1 unit RBS 3116 1370 1370 1370 VA
Nobi TRM 1 unit 1 unit Nobi TRM 1297 1297 125 VA
Lamp, others Voltage 210 210 210 Volt
Total 24 24 18 Amp
PLN MCB 25 25 25 Amp






PAGE

53
3.4 Air Conditioning Maintenance
3.4.1 Measurement AC current for Air Conditioning
Procedure:
Turn on Air Conditioning, wait until the outdoor unit is working
Take Clamp-Ampere Meter to measure AC current at line for Air Conditioning
only
AC Current allowed <=13 Amp
If more than 13 amp indication Air Conditioning failure , please call FM MS
3.4.2 Air Conditioning Phase Controller
Air Conditioning controller 2-phase using relay Omron MY 2, where MCB 1x4A at
R-phase and MCB 1x4A S phase
Temporary solution :
Switch off one of MCB connected to relay
For standard switch off MCB 1x4A at S phase
Recommendation Solution
Additional timer delay equipment to delay Phase S connected to Relay
Band/Type : Omron / H3CR













PAGE

54
Wiring diagram














3.5 Power Source for DCPDU at 19 Rack
Power capacity for DCPDU at 19 rack:
MCB ratting at Rectifier / PBC 6500:
MCB 2x25A (minimum)
MCB 2x32A (recommendation)
Recommendation for Indoor site configuration:
DC Power source : PBC 6500
PSU : 4x1400 watt
Battery : 3x100Ah
DOU : DOU 1x125A + DOU 2x10A
Load :
o RBS 2G RBS 2216/2206
o TRM Amm20p
o Exhaust fan

PAGE

55
Procedure:
o Change power source for TRM 19 rack to DOU 1x125A
DOU 1x125A connected to DCPDB RBS
Connected to RBS 2G
Connected to DCPDU TRM
Connected AMM20p
Connected Exhaust fan
o Exhaust fan and EAS connected power to DOU 2x10A
DOU 2x10A connected to:
Exhaust fan
o Wiring Power connection





























Recommendation Power Connection
PAGE

56
3.6 Exhaust Fan Status
Problem : High Temperature
Cause : Exhaust fan not working properly due external alarm panel is
broken
Description :
Exhaust fan is the emergency fan to circulate the hot air out of shelter when the
Air Conditioning is not working properly.
The exhaust fan is trigger by temperature sensor at external alarm system (EAS),
if the sensor detection high temperatures (set 30oC) in the shelter than the fan
will working and send alarm to NOC (Alarm high temperature)

Temporary Recommendation:
If in the site found EAS is broken
1. Use phase failure as trigger working of the exhaust fan
Procedure:
o Removed power connection for exhaust fan from relay EAS to relay
phase failure
o Use relay R phase failure and connection DC power of exhaust fan










R-phase
PAGE

57
Recommendation Solution:
Additional thermostat for triggering exhaust fan start relay
The thermostat will bet at 30C for trigger the relay and send alarm high
temperature














4 Reference

2008-09-16 - 198/1551-LZA 701 0001 Uen A Technical Description RBS 2111
EID-08:013998 Uen Rev. A Petunjuk Instalasi RBS 2000 Ericsson Indonesia
EID-08:017130 Uen Rev. A Petunjuk Instalasi RBS 3000 Ericsson Indonesia
EID-09:010738 Uen Rev. A Configuration of Sites Using The Outdoor Enclosure
(NOBI)







PAGE

58











Enclosure












4
PAGE

59


4.1 TRANSMISSION AND RBS DATA REPORT

SITE BUKIT PAMULANG MEGAH

NTS Project


Contents
1 Abstract ................................................................................................60
2 Problem.................................................................................................60
3 Alarm & Data Capture ...........................................................................60
3.1 Alarm & Data Capture Transmission.....................................................60
3.2 Alarm & Data Capture RBS...................................................................61
4 Actual Configuration..............................................................................61
4.1 Actual Configuration Transmission........................................................61
4.2 Actual Configuration RBS......................................................................61
5 Analyze..................................................................................................62
6 Solution Recommendation ....................................................................62
7 Supporting Document............................................................................62






PAGE

60
1. Abstract
This document describes reporting site BTTG005 Bukit Pamulang Megah.
2. Problem

BFU Problem: (from TT-20090923-00068).
Action Taken by MS: FM replaced BFU module.


3. Alarm and Data Capture
3.1 Alarm and Data Capture Transmission

Alarm List Capture;



Picture 1 RSL Capture







PAGE

61
3.2 Alarm and Data Capture RBS

Alarm List Capture;



















Picture 2 Alarm List
4. Actual Configuration
4.1 Actual Configuration Transmission
AMM Type : AMM 2p
Configuration network : 1+0 ML TN 18 GHz
Hop Name : BTTG005 B Pamulang Megah to JBKD052
Wr Poncol.
Software Baseline : R7M06 (Release 2.4.10)

4.2 Actual Configuration RBS
RBS Type : 2116
Configuration network : 2/2/2
Site Name : BTTG005 Bukit Pamulang Megah.
PAGE

62

5. Analyze
Transmission: No Transmission problem found.
RBS: When BFU Module was fault, The RBS do not have Battery backup system.
And DC source to transmission equipment was disconnected. It is hardware faulty.



6. Solution Recommendation

FM already changed the BFU with the new one. Now, The RBS have been in
service and have stable condition.


7. Supporting Document

BTTG005 B Pamulang Megah (TRM).rar


BTTG005 B Pamulang Megah (RBS).rar




















PAGE

63


4.3 POWER DATA REPORT

SITE BUKIT PAMULANG MEGAH


NTS Project
Contents
1 Introduction....................................................................................................64
1.1 Purpose.........................................................................................................64
1.2 Reference......................................................................................................64
1.3 Site Location .................................................................................................64
2 Power Data....................................................................................................65
2.1 kWh Panel .....................................................................................................65
2.2 ACPDB..........................................................................................................65
2.3 Power Supply ................................................................................................66
3 Problem Identification....................................................................................66
4 Analysis.........................................................................................................67
4.1 Check Balancing Power ................................................................................67
5 Recommendation Solution............................................................................68
6 Supporting Document ...................................................................................68





PAGE

64

1 Introduction
1.1 Purpose
This document explains about root cause analysis of site problem
1.2 Reference

EID-08:013998 Uen Rev. A Petunjuk Instalasi RBS 2000 Ericsson Indonesia
EID-08:017130 Uen Rev. A Petunjuk Instalasi RBS 3000 Ericsson Indonesia
1.3 Site Location

Site Name : BTTG 005, Bukit Pamulang Megah






























PAGE

65

2 Power Data
2.1 KWh Panel

Description Value
MCBInputBrandandCapacity MG;3xCL20A
SurgeProtection
OBOtypeB/3+1
( 3X255VAC50kA&
1XC255VAC125kA)
SinglePhaseMainsInputVoltage(RN/SN/TN) 209.4/217.3/210.2
ThreePhaseMainsInputVoltage(RS/ST/RT) 361.8/382.6/3721.9
NGVoltage 0.4V
CurrentforPhaseR 2.1A
CurrentforPhaseS 2.5A
CurrentforPhaseT 2.0A

2.2 ACPDB
Description Value
ACPDBPANEL
CheckMCBInputBrandandCapacity MG;3x63A
CheckSurgeProtection
OBOtypeC/3+1
( 3XV20C&1XC25B+C)
CheckMCBInputCapacityforRBSOutdoorRphase 32A
CheckMCBInputCapacityforRBSOutdoorSphase 32A
CheckMCBInputCapacityforRBSOutdoorTphase 32A








PAGE

66

2.3 Power Supply

Description Value
RectifierType(brand,typeofPowerSystem) 2G:PSURBS2116
RectifierCapacity(qtymodulexcapacitypermodule) 2G:3xPSU1520watt
MCBInput(QtyxRattingMCB,Brand/TypeinACPDB) 3X32AMERLINGERIN
MCBInput(QtyxRattingMCB,Brand/TypeinRectifier) NA
SurgeProtectionTypeandCondition(arresterbrand/type) NA
InputCurrentPhaseR(ACPDBtoRectifier) 2.1A
InputCurrentPhaseS(ACPDBtoRectifier) 2.5A
InputCurrentPhaseT(ACPDBtoRectifier) 2.0A
LoadConfiguration(RBS/TRM/DXX) RBS2GAMM2P
LoadCurrentTotal 6.7A

BatteryBrandandType FiammFIT100
BatteryCapacity(qtybankxcapacityAh) 4X100Ah
MCBbattery1(Brand,ratting) BFU+24/250A
MCBbattery2(Brand,ratting) NA
MCBbattery3(Brand,ratting) NA
MCBbattery4(Brand,ratting) NA

3 Problem Identification

No power issue







PAGE

67
4 Analysis
4.1 Check Balancing Power

Configuration Load

Rebalancing Configuration of power
Phase
R S T Remark
PSU RBS 2116 1 psu 1 psu 1 psu
Lamp


Power balancing analysis average load:

Current Analysis average load
Phase
R S T Unit
PSU RBS 2116 2.1 2.5 2.0 Amp
Lamp Amp

Total 2.1 2.5 2.0 Amp

PLN MCB 20 20 20 Amp


Power balancing analysis full load:

Current Analysis Full load
Phase
R S T Unit
RBS 2116 1879 1879 1879 VA
Lamp 125 VA

Voltage 210 217 210 Volt
Total 9 9 9 Amp

PLN MCB 20 20 20 Amp
PAGE

68

5 Recommendation Solution


Keep balancing phase R, phase S, phase T with changing connection phase
power PSU module
Connected PSUs RBS 2116 with configuration; 1 module at R phase, 1
module at S phase, 1 module at T phase

Rebalancing Configuration of power
Phase
R S T Remark
PSU RBS 2116 1 mdl 1 mdl 1 mdl
PSU RBS 3116 1 mdl 1 mdl 1 mdl
Lamp

6 Supporting Document

BTTG 005 Bukit Pamulang Megah (Power).rar