1

BRAT – Brandenburg Rapid Analysis Tool

Customer Introduction

Version 2.0

5th April 2013

2

Contents

• BRAT: What? (page 3)

• BRAT: When & Why (page 4)

• KBD: BRAT Outcomes: (page 5)

• Access & Viewing the BRAT detail via KBD: (page 6-8)

• BRAT Outcomes, Explanations and Next Steps: (page 9-10)

• BRAT Graph Parameter Meanings: (page 11)

• BRAT Glossary: (page 12)

• Marker Explanations: (page 13)

3

BRAT: What? What is BRAT?

• Brandenburg BBQ provides algorithms which support BT Wholesale diagnostic accuracy by identifying

specific issues within the customer premises or within the local access network (copper line).

This can help reduce the volumes of SFI visits and of customer domain fault reports into BTW.

• The BRAT tool provides a historic view of up to 14 days DLM type data.

What does it do?

• BRAT uses DLM data in conjunction with new logic and algorithms to provide diagnosis on where a

potential fault is and what the likely cause is. I.e. REIN noise interference, etc..

• BRAT provides a prognosis statement identifying the fault location or ‘Indicative Domain’ and the fault type or ‘Indicative Cause’ over the most recent seven day period.

• BRAT provides a graphical view of the various parameters used in it’s 14 day analysis that can be adjusted to display any timeline within that 14 day period.

KBD Codes (from Release AC 18th June 2012):

CD01 – D/N/R/E/I/B/Q/T/X/H (The last letter indicates the KBD logic flow or fault type).

AN01 - D/N/R/E/I/B/Q/T/X/H (The last letter indicates the KBD logic flow or fault type).

NB: When KBD returns a CD (Customer Domain) or AN (Access Network) outcome this indicates a potential

issue impacting the access network (AN) or the customer domain (CD).

All other KBD tests have passed resulting in a Brandenburg outcome.

4

BRAT: When & Why?

When? • Phase 1 was the standalone version within the SmartBB RRT application on Woosh.

• Phase 2 was deployed in Release AA 13th Feb 2012 and provided enhancements to BRAT including

integration into KBD (Knowledge Based Diagnostics tool).

• Phase 3 was deployed in Release AB 15th Apr 2012 and included additional improvements to the BRAT logic including improved wording on outputs.

• Accuracy enhancements: In Release AB+ 13th May 2012 changes were made to further enhance the accuracy.

• The accuracy was measured at over 90% following analysis post release AC 24th June 2012.

• There are likely to be on going improvements in future releases designed to further enhance the effectiveness and accuracy of the BRAT tool.

Why?

• BRAT benefits BTW customers by providing them with improved diagnostics; thereby increasing overall

accuracy and effectiveness.

• BRAT benefits BTW customers with a reduction in fault handling time for customer domain issues.

• BRAT benefits Openreach by reducing unnecessary and/or repeat engineering visits thereby reducing

costs and enabling more effective use of engineering resource.

5

KBD: BRAT Outcomes.

• D -> The circuit is dropping connection.

• N -> The circuit is not in sync.

• R -> The End User does not have an active PPP session but IP connectivity has been confirmed within the BTW network.

• E -> An LTB issue has been identified/historic LTB issue was identified/ No performance issues have been identified in the BTW network.

• I -> The End User has a working session (letter denotes KBD flow logic path)

• B -> The End User has a working session (letter denotes KBD flow logic path)

• Q -> The End User has reported potential QoS related performance issue.

• T -> This is a TV Connect Premium Service.

• X -> Datastream service

• H -> Issue identified by End User Checks (HETQ)

CD01-D/N/R/E/I/B/Q/T/X/H

Problem Explanation: <The circuit is dropping connection.> BTW Fault Localization Analysis

indicates a potential Customer Domain issue. Please check ‘Local Access Network’ tab for

more information.

Resolution/Recommendation: Please confirm all CP and End User checks have been

completed. KBD tests indicate no BTW network fault. This is a CCSFI enabled outcome.

AN01-D/N/R/E/I/B/Q/T/X/H

Problem Explanation: <The circuit is dropping connection.> BTW Fault Localization Analysis

indicates a potential Local Access Network issue. Please check ‘Local Access Network’ tab for

more information.

Resolution/Recommendation: Please confirm all CP and End User checks have been

completed. As Copper Line Test is OK this is a CCSFI enabled outcome.

6

Access & Viewing the BRAT detail via KBD

The BRAT detail can be located within the ‘Local Access

Network’ result field on the completed KBD test result.

The ‘Indicative Domain’ and ‘Indicative Cause’ message

provide a fault location and fault type when a potential issue is

seen. In this instance the ‘Indicative Domain’ or location is

‘DSL OK’ (no issues identified) and the ‘Indicative Cause’ is

‘No fault found with DSL’.

Brandenburg logic is designed to support a more accurate

identification and speedier resolution of DSL issues.

To view the BRAT graph click on the ‘View BRAT Graph (it

may take 120 seconds to load the graph)’ link.

ACCESS:

Users need to have applied for RRT access on BTW.com to

view the RRT and BRAT graphs and must have run a full

KBD test to completion before the RRT or BRAT graphs are

available in KBD.

Refer to KBD Handbook for more detail on applying for access.

7

Viewing the BRAT detail via KBD

The BRAT graph will be displayed within 120 seconds and

will detail the circuit identifier(s), the overall prognosis

statement, the most recent seven days prognosis displayed

in a daily format and the BRAT graph (see next slide).

To maximise the screen click the ‘maximise’ rectangle in the

top right hand of the BRAT screen.

8

Viewing the BRAT detail via KBD

Scrolling down the BRAT screen we can see the ‘from’ and ‘to’ date

fields (set to the 14 day default).

To change the timeline within the 14 day period use the drop down

button to set the date on each field and click the ‘Update’ button.

Within the graph field there is a RAG (Red/Amber/Green) display.

NB: the BRAT logic looks at various parameters including upstream

and downstream line rate, noise margins, attenuation , errored

seconds etc.

The timeline displayed is also visible at the bottom of the graph.

This graph will also indicate profile changes and fault closure dates as:

* indicates a profile change

^ indicates a fault cleared date.

9

BRAT Outcomes, Explanations and Next Steps.

FAULT DOMAIN

INDICATIVE

CAUSE

EXPLANATION RECOMMENDED ACTION

PREMISES

WIRING

SUSCEPTIBLE TO

INTERFERENCE.

PREMISES

WIRING VERY

SUSCEPTIBLE

TO

INTERFERENCE.

STRONG/

SEVERE

REIN

STRONG/

SEVERE

SHINE SLOW

CUSTOMERS

PREMISES YES NO NO NO NO

Line is susceptible to radio interference

potentially impacted by the quality of premises

wiring (including bell-wire if no faceplate fitted).

Check premises wiring quality. Check microfilters and

consider fitting iPlate/NTE-2000.

CUSTOMERS

PREMISES NO YES NO NO NO

Line is very susceptible to radio interference

potentially impacted by the quality of premises

wiring (including bell-wire if no faceplate fitted).

Check premises wiring quality. Check microfilters and

consider fitting iPlate/NTE-2000.

CUSTOMERS

PREMISES NO NO YES NO NO

Radio interference is observed. Where line is

not showing susceptibility to interference

through premises wiring quality a strong

interference source is the likely cause.

Check premises wiring quality. Check microfilters and

consider fitting iPlate/NTE-2000. Check potential sources

of REIN interference such as equipment that affects

broadband when it is switched on. REIN investigation may

be required.

CUSTOMERS

PREMISES NO NO NO YES NO

Line shows evidence of short bursts of radio

interference with no clear pattern of occurrence.

These are normally seen as irregular retrain

events and short irregular bursts of errors.

Source of random interference may be difficult

to identify.

Check premises wiring quality. Check microfilters and

consider fitting iPlate/NTE-2000. Potential sources of

SHINE interference may be difficult to identify due to their

erratic pattern of occurrence.

CUSTOMERS

PREMISES NO NO NO NO YES

Line has a lower than expected line rate. High

applied margin, Capped or Banded Profile may

be suppressing evidence of cause.

Check premises wiring quality. Check microfilters and

consider fitting iPlate/NTE-2000. If issue has been

identified and resolved consider reprofiling line and/or

remove Capped/Banded Profile. N.B Reprofiling may be

required to confirm underlying nature of fault has been

resolved. This may cause line instability during reprofiling.

Retest circuit later to confirm resolution.

DSL OK OK

The DSL line appears to be working correctly. No DSL problem detected. If the service is still affected by

an issue this may lie elsewhere I.e in the IP layer or

customer's setup and configuration.

10

BRAT Outcomes, Explanations and Next Steps.

FAULT DOMAIN

IINDICATIVE

CAUSE INDICATIVE

CAUSE INDICATIVE

CAUSE INDICATIVE

CAUSE

INDICATIVE

CAUSE INDICATIVE

CAUSE EXPLANATION RECOMMENDED ACTION

Line attn

unstable

Line fault

possible

joint

Line fault

probable

joint

Line fault

highly

likely joint

Line fault

suspect

HR

Wet joint

strip

termination

ACCESS

NETWORK YES NO NO NO NO NO

Changing line attenuation

indicates a line fault. No other

symptoms detected for better

localisation.

Investigate access line condition and terminations.

Check that there hasn't been a network uplift e.g.

pair swap within the analysis period as this can

cause a change in line attenuation.

ACCESS

NETWORK NO YES NO NO NO NO

Instability in line characteristics

indicate a possible faulty line

connection.

Investigate access line condition and terminations

to identify and resolve possible faulty connection.

ACCESS

NETWORK NO NO YES NO NO NO

Instability in line characteristics

indicate a probable faulty line

connection.

Investigate access line condition and terminations

to identify and resolve probable faulty connection.

ACCESS

NETWORK NO NO NO YES NO NO

Instability in line characteristics

indicate a high probability of a

faulty line connection.

Investigate access line condition and terminations

to identify and resolve likely faulty connection.

ACCESS

NETWORK NO NO NO NO YES NO

Line characteristics indicate a

high-resistance connection. Investigate access line condition and terminations

for corrosion or damage in-span e.g. Abrasion of

cable run through trees.

ACCESS

NETWORK NO NO NO NO NO YES

Characteristics indicate water

ingress into cable terminations.

This is likely to be underground or

exposed block termination.

Investigate access line condition and terminations

for water ingress.

11

BRAT Graph: Parameter Meanings. Parameter Title Full Title Explanation

ILQ Indicative Line Quality ILQ is taken from the RRT detail and displayed in the BRAT graph to support diagnostic comparison

Rate D/S Downstream sync rate

Downstream line sync rate reported for each 15-minute period.

Max Rate D/S Maximum achievable

downstream rate

Daily aggregated maximum achievable downstream rate (minimum value of maximum achievable

downstream rate per day from 15-minute samples)

Rate U/S Upstream sync rate Upstream line sync rate reported for each 15-minute period.

Max Rate U/S Maximum achievable upstream

rate

Daily aggregated maximum achievable upstream rate (minimum value of maximum achievable upstream rate

per day from 15-minute samples)

Attn Ds Downstream Line Attenuation Daily aggregated Downstream line attenuation in dB (max value seen during day)

Attn Us Upstream Line Attenuation Daily aggregated Upstream line attenuation in dB (max value seen during day)

Attn Ratio Attenuation Ratio Ratio of Upstream to Downstream attenuation

Uptime Uptime Count of seconds of line uptime (a.k.a showtime) in each 15-minute period (max is 900 seconds)

Inits Initialisation count Count of successful initialisations in each 15-minute period

Failed Inits Failed Initialisation Count Count of unsuccessful initialisations in each 15-minute period

Loss of Link Loss of Link Count of loss of link events (line drops) in each15-minute period

FEC Sec D/S Forward Error Corrector

Seconds Downstream

Count of seconds in which the forward error corrector corrects errors in the downstream path in each 15-

minute period (max is 900 seconds)

FEC Sec U/S Forward Error Corrector

Seconds Upstream

Count of seconds in which the forward error corrector corrects errors in the upstream path in each 15-minute

period (max is 900 seconds)

Err Sec D/S Errorred Seconds Downstream Count of seconds in which uncorrectable errors occur in the downstream path in each 15-minute period (max

is 900 seconds)

Err Sec U/S Errorred Seconds Upstream Count of seconds in which uncorrectable errors occur in the upstream path in each 15-minute period (max is

900 seconds)

Mgm Ds Downstream Noise Margin Downstream noise margin recorded for each 15-minute period (measured in dB)

Mgm Us Upstream Noise Margin Upstream noise margin recorded for each 15-minute period (measured in dB)

12

BRAT – Glossary

REIN (Repetitive Electrical Impulse Noise):

This is radio interference arising from an electrical source. There are a large number of possible

sources, including switch-mode power supplies, motors (e.g. vacuum cleaner) and industrial machinery.

Some REIN sources have distinct signatures, such as a switch-mode power supply, whilst others are

broad-spectrum. REIN may be continuously present at some (usually varying) level, or may occur at

intervals and for periods that correlate with human activity or scheduled programming. Some sources

have a seasonal pattern, such as interference caused by (usually cheaply manufactured) Christmas

tree lights. In extreme cases, REIN can prevent a line from synching up and can cause extended

periods of dropped connection, but normally will be observed as patterns of errors and possible dropped

connections in the DLM data.

SHINE (Single Hit Impulse Noise Event):

This is radio interference that is emitted in short bursts, often at seemingly random intervals. In some

cases SHINE is sometimes visible as periods of bursts of errors in the DLM data. In severe cases the

interference is sufficiently powerful to cause an immediate drop in connection and can prevent the line

synching up until the interference has ceased. In these cases we do not see evidence in error data but

we do see periods of dropped connection. The cause of SHINE is the most difficult type of noise to

locate because of its spurious nature. It might be expected that when SHINE is preventing reconnection

for a period that there would be a record of failed retrains but we have not observed this in

investigations to date.

13

Marker Explanations.

There are a variety of additional markers against each outcome but where an ACCESS NETWORK

(LINE) issue is seen this will take priority over HOME (CUSTOMER PREMISES).

NB: BRAT uses the most recent seven days of data in it’s prognosis logic.

NB: This logic is configurable and can be altered in future releases.

OCCASIONAL

This indicates that an ACCESS NETWORK (LINE) issue was seen on 1 day out of the recent 7 days

used for the prognosis analysis. For HOME (CUSTOMER PREMISES) this is set to 1-2 days within the

seven day prognosis period.

INTERMITTENT

This indicates that an ACCESS NETWORK (LINE) issue was seen on 2-3 days out of the recent 7 days

used for the prognosis analysis. For HOME (CUSTOMER PREMISES) this is set to 3 days within the

seven day prognosis period.

FREQUENT

This indicates that an ACCESS NETWORK (LINE) issue was seen on 4 or more days out of the recent

7 days used for the prognosis analysis. For HOME (CUSTOMER PREMISES) this is also 4 days within

the seven day prognosis period.

RECENT

This is a little more complex but essentially ‘RECENT’ requires a 75% (3/4 ) count of either ACCESS

NETWORK or HOME in the most recent part of the seven day prognosis period.