Spotlight Platform
With the Seek-See-Solve approach, Spotlight is designed to allow you to follow your own investigations throughout the various analysis pages and reports. Starting from the Summary Dashboard, examine the summary map and then the appropriate report for the loaded data, which might indicate the presence of one or more problems. Cell coverage, interference problems and other visualization can be investigated from the Radio Network Explorer analyses. These might then point you to specific problem events which you can examine and diagnose using the Event Explorer.
Spotlight Platform
Radio Network Analyses
Non event based analysis (i.e. Coverage analysis) of data with high user interaction. These pages are not configurable, and require customization.
Event-based troubleshooting
Event based analysis with automated root cause diagnostics for the most common subscriber problems.
Reporting
Integrated, professional-quality reports including embedded maps.
The configuration process involves creating and editing XML configuration files and using advanced Analyzer features (such as writing queries and expressions) but does not require scripting or programming knowledge. The KPI configuration mechanism is similar to troubleshooter's but is more complex and consequently more powerful. However, if you have used the troubleshooter configuration mechanism, you will find you have a head start when learning to use the Spotlight configuration mechanism.
Note: You then need to restart Analyzer in order for the change to take affect. The following diagram provides a graphical representation of the relationship of the elements in the XML schema.
TopPanel
Field
Height Unit
Type
Optional Optional
Description
An integer value that specifies the height of the top panel in the specified units. The unit in which the height is specified. Valid options are: Pixels Percent
SidePanel
Field
Width Unit
Type
Optional Optional
Description
An integer value that specifies the width of the side panel in the specified units. The unit in which the width is specified. Valid options are: Pixels Percent
Spotlight Reports
Although creating the Excel workbook and app pack XML for a Spotlight report is essentially the same as for a standard app pack, there are some special considerations that apply to app packs for use in Spotlight: The definitions of all of the queries that are used in tables and charts in the workbook must be added to the app pack XML using AttachedQuery elements. The queries must be a crosstab format (i.e Crosstab or Event queries only).
You must create the Excel report using repository data and not data that has been loaded into Analyzer in full load mode. This is because the query definitions that are embedded in the workbook are subtly different depending on whether the data is in a repository or fully loaded and they are not interchangeable. (New tool help development in classic analyzer the
convert to Spotlight)
Spotlight reports can contain maps. For this to work, you must define the maps using the Maps node in the app pack XML, then run the app pack to generate the initial image files and finally insert these into the workbook manually.
Spotlight Reports
Generates the following files: An Excel workbook that defines the actual report. App pack XML that specifies the name and location of the Excel workbook and includes definitions of all of the queries that are used in the tables and charts in the workbook. Reports XML that specifies the name of the report and the location of the app pack XML.
Spotlight Reports
Report XML
Specifies the name of our report and the location of the app pack XML to Spotlight
Spotlight Reports
APP Pack XML
Specifies the Location/Name of the EXCEL report and the queries to be used be Spotlight
Spotlight Reports
Changes in the XML schema:A ShowAllTabs field (which is set to True) to the Report element. This indicates that when users run the report we want them to see a tab for all of the worksheets in the workbook that are not hidden. A Maps element with its ImageDirectory field set to Analyzer://Reports/images. The maps are inserted into the report as bitmaps and this is where they will be stored. A single Map element, which has two child Layer elements. Each of these specifies a single attribute to be displayed on the map and for the ServRxQualSub attribute we have set the ZoomTo field to True, indicating that we want the map to zoom to this layer. This effectively results in a "best fit" operation on the drive test route within the map window.
Spotlight Reports
From the Insert menu, choose Object to open the Object dialog box
Select or deselect the Relative to original picture size option according to your requirements. Select the option if you want the map to be stretched and shrunk to fit the size of the current image. You should normally do this if you are placing several maps on the same worksheet. Deselect the option if you want the size of the map to vary according to the size of the image that is generated each time the report is run. This means that the map will vary in size. This option will generally provide a better quality and is useful when you have a single map on a page.
It is generally advisable to select the Lock aspect ratio option, because this reduces the amount of distortion when the image is resized.
If the map appears as an icon with the name and path of the linked file underneath, see Changing the Microsoft Office Picture Manager Settings.
Note: There are similarity to configuring spotlight event KPIs and Radio Network KPIs. However the Radio Network KPIs normal drilldown to a Radio network page this requires customisation and real understand of the analyser platform and scripting.
KPI Node
Field Priority Type Required, Integer Description This is a numeric value that is used to group KPIs by priority and control the order in which the KPIs appear in lists and tables. Lower values are processed before higher values. KPIs that have the same priority value are processed in the sequence in which they appear in the file, if they are defined in the same file. However, when KPIs with the same priority value are defined in separate files, there is no way of controlling the order in they are processed. Typically, the most important KPIs would have a priority of 1, the next most important ones have a priority of 2, etc. Controls whether the KPI is visible to the user in the main dashboard (provided the display condition has been passed) and the Event Explorer or Radio Network Explorer. Note that with one exception all KPIs appear in the list of KPIs on the New Project Template Step, regardless of this setting. This is in order to make it possible to deselect KPIs that are not required. The exception is the internal KPIs that are used simply to define the initial drive route and the name of the KPI to be used to color the cell sector wedges on the Summary Dashboard. This is because provided these KPIs do not add any queries to the template, provided they do not include any other elements (such as a Summary element) that specify a query. The name of the KPI. This is used to identify the KPI internally and is how the KPI appears in the list of KPIs when you create a new template. The name can be any combination of alphanumeric characters (including spaces) but it must be unique within Spotlight. Used to group KPIs in the Summary Dashboard side panel, the type can be one of the following: Critical Important Information The top-level category or group to which the KPI belongs. Generally (but not necessarily) this is the technology name. For Example: GSM HSDPA UMTS Controls whether the KPI is selected by default in the list of KPIs on the New Project Template page when you create a new template based on the default Spotlight template. As a consequence of this, the Enabled flag also controls whether the KPI is included in a project that is based on the default Spotlight template. If your KPI is designed for use in special circumstances only, it is recommended that you set this flag to False and then set up a custom project template to accompany the KPI in which it is selected. This means that the custom KPI will not be present to slow users down when they are working on projects in which it is not relevant. This applies to event KPIs only and is a text that is used in the label for the data layer in the Map legend when the KPI is used to color the cell sector wedges. The label is formed from the network element type (for example, WCDMA_Cell), the device name (for example, All) and the text specified here. This text must not contain any spaces, because they are not allowed in Map legend labels. This applies to event KPIs only and is the name of the KPI as it is shown to the user. For example, this text is used as the column heading for the KPI in the table in the Event Explorer's top panel. A second-level category for the KPI. For radio network KPIs, this should be "Radio Network". For event KPIs, this might be, for example, "Circuit Switched", "Packet Switched", or "Handover Issues". These are used as subheadings in the main dashboard side panel. In the Event Explorer, the top panel displays the events for the selected Category - SubCategory combination.
Visible
Required, Boolean
Name Type
Category Enabled
LegendName
Optional, String
DisplayName SubCategory
DriveRoute Node
Field Query Type Required, String Description The binned data query that includes the attribute or binned query that is to be displayed on the map in the Summary Dashboard. You should specify this as the name of a binned data query that already exists within the default Spotlight template. To find the names of the binned data queries in the default template and what attributes they contain, create a new project template based on default Spotlight template and select all of the default KPIs in Step 3. Step 4 will then list all of the default binned data queries and when you select one, the names of the attributes it contains are displayed in the central pane. The name of the attribute or repository binned query that is to be displayed on the map in the Summary Dashboard. Typically this would be an attribute that represents a measurement of the signal level.
Attribute
Required, String
CellsWithData Node
Field
EventMapKpi
Type
Required, String
Description
The internal name of the KPI that is to be used to color the cell sector wedges on the map in the main dashboard. This KPI must have an EventMapExplorer node. Typically, this KPI would be created specifically for this purpose and would make the cell sectors opaque if there is no data for them. This would enable users to spot immediately any cell sectors for which there is no data when it would normally be expected (for example, in the center of an area that has been heavily drive tested. To make the cell sectors that have no data associated with them opaque, set the FormatGroup field on the EventMapExplorer node to the name of a format group in the XML definition for which the Range element for the "no data" value is set to 305419896. This acts a "magic number" that makes the wedges completely transparent.
IssueText
Required, String
DisplayCondition
Optional, String
Query dimension by Cell. In EventMapExplorer Node Drilldown feature as controlled by the Investigation node Node
Event on the Map & Side panel, as defined by the EventResolution Node
CellNumber
Required, String
Query
Required, String
AttributeSourceQuery
Required, String
Expression FormatGroup
Type
Required, String
Description
The name of the expression. This must be unique within the Diagnosis node and must not contain brackets ( [ ] ), but can contain any alphanumeric characters or underscores, but not spaces. This is an optional field that can be used to specify the name of a format group that is to be used to format the evaluated results of the expression. Typically you should specify a format group if the expression is used to supply a value that is simply to be rendered. However, if the expression is to be used as a formula or condition within the diagnosis, you should normally leave this field blank: otherwise the formatted results will be used instead of the raw value. You can specify the name of any format group. The following are useful for rounding numeric values to a specified number of decimal places:
FormatGroup
Optional, String
Group
Field
Name Condition
Type
Required, String Optional
Description
The text for the subheading. The name of an Expression element within this Diagnosis node that controls whether the contents of this element are to be returned. If the expression evaluates to False, zero, an empty string, or Null, this node and all of its contents are ignored. If the expression evaluates to any other value, Spotlight processes the contents of this node.
SubGroup
Field
Condition
Type
Optional
Description
The name of an Expression element within this Diagnosis node that controls whether the contents of this element are to be processed. If the expression evaluates to False, zero, an empty string, or Null, this node and all of its contents are ignored. If the expression evaluates to any other value, Spotlight processes the contents of this
Item
Field
Name
Type
Required, String
Description
An internal name for the item. This is used by the logger to identify the item.
THE END
Spotlight Reports
Changing the Microsoft Office Picture Manager Settings
There is a known problem that can result in maps that have been embedded in an application pack or Spotlight report not appearing correctly. When this happens, the maps may simply not appear in the report viewer and appear in the Excel workbook as icons with the name and path of the linked file underneath. This is a result of an interaction with a setting in Microsoft Office Picture Manager. This topic provides instructions for changing this setting so that the maps appear correctly. You can ignore this topic if you do not have the Microsoft Office Picture Manager or have never used it and have no problems with viewing the maps. To change the setting: Open the Microsoft Office Picture Manager from the main Windows Programs menu. (Generally this is Start | Programs | Microsoft Office | Microsoft Office Tools | Microsoft Office Picture Manager, but this might vary depending on your setup).
Sometimes the File Types dialog opens automatically. If not, open it by choosing File Types from the Tools menu
Deselect the BMP Windows Bitmap (*.bmp; *.dib) option. Click OK. Close the Microsoft Office Picture Manager. If necessary, close the report viewer and Excel.
The maps should appear correctly the next time your run your reports.
Variance = ( Sum ( ServRxLev * ServRxLev ) ( (Sum ( ServRxLev ))^2 / Count ( ServRxLev) ) ) / Count ( ServRxLev) Standard Deviation = SQRT ( Variance )