Introduction to WCDMA BTS site commissioning

Generic commissioning tasksCommissioning is a sequence of tasks, such as visual checks and inspections, parameter and SW configurations, tests and reporting, to ensure that the stand-alone equipment in question has been properly installed, has no faulty modules and is ready for integration.The generic commissioning steps can be seen in the following Commissioning overview figure. The details of each step depend on the equipment and version in question and can be found in the relevant documentation.

From WN6.0 onwards the autoconnection procedure starts automatically when the BTS is starting up and initializes transport connections to the upper network elements. During the autoconnection procedure, the transport part for online changes is disabled. Autoconnection procedure is stopped when a full configuration file is sent to the BTS and activatedMore information on the autoconnection and autoconfiguration issues can be found in Monitoring autoconfiguration and autoconnection chapter and in the WCDMA RAN rel. RU20 feature descriptions document. When the RAML2.1 conversion (RAN885: Remote BTS SCF Management for Flexi/Ultra/MetroSite BTS) is carried out by the WN6.0 SW, two WN5.0- and WN6.0- specific commissioning files are stored into the BTS. WN6.0 SCF is converted automatically when WN6.0 SW delivery is done and WN6.0 SW is activated (after BTS reset).Automatic conversion is active until first recommissioning is done with WN6.0.

To get all the BTS capacity and features in use, required licenses need to be downloaded to the BTS from Nokia Siemens Networks NetAct™. For more information on licenses, see the License Management document.

Visual checks and inspection The first part of the visual check is done before powering on the BTS site at the power system. When all is proven to be OK, the 'Power on' check is done and the LED status is verified. The equipment is checked visually to see that there are no fatal installation errors, which might lead to equipment damage during the power on.The following items are checked:

the grounding power cabling and supply voltage other cables and fibres LED status during power up TX/RX/antenna connector torque check

Local SW download

This step contains all the actions required to update and/or download SW to the equipment or to the PC for managing the equipment at the site. The exact order in the step sequence is equipment-specific and thus might take place after some self tests.Parameter setupThis contains all the actions required to set up the parameters for commissioning and for integration. Parameters might include software parameters fed in manually or as a file. The equipment specific product documentation describes the details. Some of the parameters need to be given during the test step.Note that when a parameter is not mentioned in a commissioning instruction, the parameter should be left at its default value even though it might be possible to change it.Commissioning testsThis contains the key tests that need to be carried out to ensure the basic functionality of the equipment in question. Some of the tests are activated automatically, some of them are run as a part of the Commissioning wizard and some might need to be activated separately. Some of the tests are optional and are run for diagnostic purposes if there is a reason to suspect the functionality. Typical tests and measurements:

internal loop tests external alarm and control tests site tests site support system alarms shown at the BTS RF max power measurement (optional test)

Some of the functional tests need more parameters than are available during the commissioning and thus can be run only after the network element has been integrated and it is able to get the rest of the parameters from the RNC.

Troubleshooting The purpose of troubleshooting is to rectify the problems found by analysing the test results and perhaps running some further tests to identify the cause of the problem. Information about troubleshooting hints and optional tests can be found in the equipment specific documentation. To avoid double work, it is essential to be aware of the current known problems. The Technical Notes (TN), List of Generic Faults and Change Deliveries (CD) need to be studied from time to time for latest information about known problems and work-around solutions. Based on the experience and HW repair statistics about the cause of the faults one major group is 'no fault found'. To minimize unnecessary shipping, spare waiting and 'no fault found' reports, it is essential to double-check the suspected module one more time before sending it to repair. Once the module is suspected and the replacement seems to rectify the problem, the original suspected module needs to be tried once more. In many cases the actual reason which rectified the problem is power off/on-reset or plug off/push in reset.When the module is really suspected or proven faulty, the appropriate error report attached with possible log or test report files is filled. The following information needs to be clearly available in the report:

site and equipment identification module identification

based on which test the module was suspected faulty what other modules were suspected what parameters were used what other tests failed what was the error/fault message/alarm number what was the used SW version responsible engineer (report filled by) and contact info

In case of module replacement the site inventory need to be updated.Bar code reading and site inventoryTo be able to trace a given module based on the serial number or the version number, it is important to collect and keep the information about the module version and serial numbers up to date. The most advanced modules and their SW versions support the electronic serial and version number detection and recording. Some less advanced and passive modules do not necessarily have this feature and those modules need to be scanned. Most of the modules installed on the BTS have a set of extra serial and version number labels, which must be attached to the BTS cabinet door or in the inventory form in the site folder during the installation. During the bar code reading also these labels need to be scanned. More information on the bar code reading is available in the Nokia Siemens Networks NetAct™ documentation Using Bar Code Scanner and Using Asset Manager documents.ReportingThe most important part of the commissioning is the reporting. Without relevant reports the equipment can be considered not commissioned. The purpose of reporting is to keep track of the latest status of the equipment and the work done. Some new equipment supports features where the reports are automatically updated to the main database in the NetAct™ system, some need a few manual steps, and some reports need to be saved/printed manually. Typical reports are:

commissioning report produced by the Commissioning wizard of WCDMA BTS Site Manager

snapshot file saved by WCDMA BTS Site Manager site inventory report delivery reclamation for missing items failure report for each faulty module failure report for each new problem site deficiency report for outstanding problems site progress report

Some of the reports might be used as a technical appendix for a site acceptance document.