Application Note - TechComplete™ Test Productivity Pack ...

of 12 TechComplete™ Test Productivity Pack (TPP)

Proof of Performance Reporting

Application Note - TechComplete™ Test Productivity Pack


Introduction The term Proof of Performance tests may have different interpretations depending on your geographic locality. In North America, Proof of Performance tests can tie directly to testing mandated by the Federal Communications Commission (FCC); however, in other localities Proof of Performance test may simply refer to having the ability to run test over various times and physical constraints such as weather and/or temperature. The DSAM meter can perform Proof of Performance tests immediately or over any set of time intervals that you desire. This is particularly useful when you are running the 24-Hour test required by the FCC in the US and by other international governing bodies. This Application Note specifically focuses on how to:

• Configure Proof of Performance tests

• Execute Proof of Performance tests and

• Compile Proof of Performance Test Results It is a fact that all cable systems need to be able to consistently check measurements in their network during various times and over a wide temperature range. The DSAM together with the Test Productivity Pack (TPP) provides a seamless way for operators to conduct Proof of Performance. This Application Note will provide key step-by-step instructions on setting up TPP to work in conjunction with the DSAM to deliver the Proof of Performance functionality.

Proof of Performance Test Configuration Proof of Performance testing is configured using TPP. A typical configuration for performing Proof of Performance test is shown below.

1. Select the Location File Icon from the main menu.



2. Create a new Proof Location File by double-clicking on the default “Proof of Performance” file.

3. Customize Proof of Performance initial values and/or Field Names

4. Deploy / Save the location in the same fashion as done for Channel or Limit Plans

5. Synchronize selected meters with the appropriate TPP Server

Executing the Proof of Performance Tests Key steps in running the Proof of Performance test on the DSAM include the following:

1. Press the AutoTest button on the DSAM

2. Scroll down to and select “proof of performance”



3. Configure the Proof of Performance Test

• Channel Plan, Limit Plan, Filename to save to, Ambient Temp, etc.

4. Configure Proof of Performance Test Scheduling via Scheduled Soft Key

• Meter shuts down until time of AutoTest and wakes itself

• Input start time, interval, date, etc..

• 4 sessions over a 24 hour period

5. Input location data (i.e. Location, Location Type, Area, Trunk, AMP ID …)



6. Start Proof of Performance Test

7. Monitor progress and Review Results.

8. Results are saved in an appropriately named folder.

9. Sync the DSAM to the TPP Server to transfer test results to the server

Compiling Proof of Performance Tests Results Proof of Performance test results are easily accessible using the TPP software. TPP was designed specifically to work in conjunction with the JDSU DSAM meters.

Key steps in viewing Proof of Performance Tests results / reports are outlined below.



1. Log into the Test Productivity Pack, which includes the Test Reporting System.

2. Select the TPP test files

3. Under the Queries drop down menu select “All Proof of Performance tests for 24 hrs Proof report”

4. Choose 4 files for your Proof of Performance report and click on “Proof Reports” to generate your report.



5. The Proof Report shows a side by side comparison of 4 tests PASS/FAIL results covering a 24 hour time period and the test reports are very similar to StealthWare Proof Reports

6. You may also Print / Export results. Export options include EXCEL & a FamilyWare Proof of Performance Report batch “zip” file.

Summary Following the step by step procedures of this Application Note will allow a technician to quickly learn how to set up and execute Proof of Performance Test on an automated basis using a DSAM coupled with the Test Productivity Pack Software. Technicians can perform a battery of test for any or all channels in the channel plan. The technician can now easily print and export reports in order to make educated decisions in regard to the maintenance of their particular network.



APPENDIX A. TPP – Test Reporting System Proof Repor t Details

Requirements to Pass the Proof Report

For a given channel tested:

• It was tested on all 4 measurement files.

• It has the same number, frequency and type for all 4 measurement files.

• The difference between the max and min video level is less than or equal to the “24 Hour Video Deviation” limit stored in the measurement files.

• Minimum and Maximum video limits are passed for all analog and digital type channels (e.g. Min/Max Video Level, Min/Max Digital Level).

For each measurement file:

• Limit checking was done on the file.

• The limit values used must match those used by the other measurement files.

• Ambient temperature was successfully recorded for each test (only possible in Proof of Performance AutoTests).

• Each test must be 6, 12, and 18 hours from the 1st test (plus or minus 1 hour).

• Each test must have passed based on all current Autotest limit checking, including Min/Max Delta Video/Audio, Max Adjacent Channel Delta, Max Video Delta, Max and Video to Digital Delta.

Configuring the Proof Report

To configure Signal Level Units:

From the TPP Web Application, select “system preferences” from the left panel. Under the “global system preferences” section, select “measurements”.. Select the desired “Signal Level Units” value and press “Save”.

To configure a custom report header:

From the TPP Web Application, select “system preferences” from the left panel. Under the “global system preferences” section, select “report header”. Check the “use custom report header” box. Enter the HTML for the Address and Custom sections. Via the file system, install a new custom icon and press “Save”.

To configure the Proof of Performance export to FamilyWare:

The following properties can be added and modified with in the configuration.properties file located in the cfg folder of your TPP install folder (typically: C:\Program Files\Acterna FDM-250). If the property is not in the file, then it will have the following default values:

• pop.export.location_lookup.location = Location

• pop.export.location_lookup.location_type = Type of Location



• pop.export.location_lookup.v1 = AC Voltage

• pop.export.location_lookup.v2 = DC Voltage (reg)

These properties are used to map the Location data from a measurement file to fields specific to FamilyWare. If you are not using the default “Proof of Performance” Location file with the default field names, then you will have to change these properties.



APPENDIX B. Summary of FCC Proof of Performance Tes t

Overview of FCC Proof of Performance Test Requirements

For details of the Proof of Performance test requirements, refer to the Code of Federal Regulations (CFR) 47, part 76. This book is available from the US Government Printing Office, Mail Stop: SSOP, Washington, DC 20402-9328. Many cities in the US have US Government Printing Office stores that sell Government publications directly to the public.

Who must run the tests?

All systems with 1000 or more subscribers. Smaller systems are required to comply with the Cumulative Leakage Index requirements (including quarterly measurements) but are not normally required to demonstrate proof of performance of the other technical standards. The technical standards are expected to be met by all systems -- but small systems don't need to prove it.

When do the tests need to be run?

Most tests need to be conducted "at least twice each calendar year (at intervals not to exceed seven months)". The "24 hour" tests "shall be measured and recorded, along with the date and time of the measurement, once every six hours (at intervals of not less than five hours nor more than seven hours after the previous measurement), to include the warmest and the coldest times, during a 24 hour period in January or February and in July or August".

The 24 hour test is the only one required during those particular months.

The color tests (Chrominance to Luminance Delay Inequality, Differential Gain, and Differential Phase), need to be conducted at least triennially (once every three years).

How many channels need to be tested?

Many tests are required on all "NTSC or similar video channels" of the system. Other tests are required "a minimum of four (4) channels plus one additional channel for every 100 MHz, or fraction thereof, of cable distribution system upper frequency limit (e.g. 5 channels for cable system upper frequency limit of 101 to 216 MHz; 6 channels for cable television systems with a cable distribution system upper frequency limit of 217-300 MHz; 7 channels for cable television systems with a cable distribution upper frequency to 300 to 400 MHz, etc.)."

All channels are required to meet all of the technical standards. However, for certain of the technical standards, you only need to demonstrate "proof of performance" on a sampling of the channels...

How are the test channels selected?

"The channels selected must be representative of all the channels within the cable television system." Generally, systems select channels from across the system's spectrum.

How many test sites do we need?

For systems from 1000 to 12,500 subscribers, tests "...... shall include measurements taken at six (6) widely separated points. However, within each cable system, one additional test point shall be added for



every additional 12,500 subscribers or fraction thereof (e.g., 7 test points if 12,501 to 25,000 subscribers, etc.). "

Also, there must be at least one test point "for each portion of the cable system served by a technically integrated microwave hub".

Note that this does not mean a test point for each fiber node.

Where, in the system, are the tests conducted?

Test points "shall be balanced to represent all geographic areas served by the cable system. At least one-third of the test points shall be representative of subscriber terminals most distant from the system input and from each microwave receiver (if microwave transmissions are employed), in terms of cable length".

Measurements may be made at convenient monitoring points in the system so long as the data reflects system performance for nearby subscribers.

Some measurements (visual signal level and 24 hour tests) are required to be measured "at the end of a 30 meter (100 foot) cable drop that is connected to the subscriber tap, ..." Usually, all tests in the field are conducted at the end of a 100 foot drop cable. The 100 foot drop cable simulates typical drops provide to homes. For tests at the output of a set-top converter, connect the converter to the end of the drop cable.

Are there specified procedures for each test?

In general, no. However, good engineering practices are to be used for all tests. For some measurements, the rules refer to documents such as the "NCTA Recommended Practices for Measurements on Cable Television Systems, 2nd edition, November 1989". A review of that document is an excellent starting point.

Of course, measurement equipment and techniques are continually evolving. There is a lot of test equipment available today that make the tests much easier than some of the procedures described in the NCTA documents. Before you decide to use any procedure, you should of course, have a thorough understanding of the test requirements and the algorithms used by your test gear. Do not blindly trust automated test gear simply because it provides "numbers"!

Where do we send the test results?

Unless told otherwise by the FCC or your franchise authorities, you simply keep the data on file for at least five years. The test data is required to be made available to the FCC or local franchise authorities upon request.

What happens if we don't pass?

Tests have been run on over 50 systems, many of them multiple times. So far, one system has "passed" all the requirements (it passed one of the two times in which tests were run on it).

Given the complexity of today's cable systems, the thousands of mechanical connections involved, the number of back hoes and other rodents in our society; something, somewhere, is likely to be broken at any given point in time.



The most important thing is to run the tests, find the problems, fix them, and keep a log of the whole process.

Of course, carrier leakage problems should be addressed as soon as they are discovered. Authorities tend to frown when aircraft start honing in on bad splices.

Where do I go for more information on Proof Testing?

http://www.fcc.gov/omd/pra/3060-0289.html



APPENDIX C. Acronyms DSAM – JDSU’s Digital Service Activation Meter

QAM - Quadrature amplitude modulation (QAM) is a modulation scheme which conveys data by changing (modulating) the amplitude of two carrier waves. QPSK - Phase-shift keying (PSK) is a digital modulation scheme that conveys data by changing, or modulating, the phase of a reference signal (the carrier wave).

Voice over IP - Voice over Internet Protocol, also called VoIP, IP Telephony, Internet telephony, Broadband telephony, Broadband Phone and Voice over Broadband is the routing of voice conversations over the Internet or through any other IP-based network.

CMTS - A cable modem termination system or CMTS is equipment typically found in a cable company's headend, or at cable company hubsite [[1]] and is used to provide high speed data services, such as cable internet or Voice over IP, to cable subscribers

FCC – Federal Communications Commission www.fcc.gov

Symbol Rate – rate at which symbols are transmitted

DOCSIS - Data over Cable Service Interface Specification (DOCSIS) is an international standard developed by CableLabs and contributing companies. DOCSIS defines the communications and operation support interface requirements for a data over cable system.

Proof of Performance Test - Applies to the FCC Proof of Performance test requirements as specified in CFR 47 part 76.

BER - an error ratio is the ratio of the number of bits, elements, characters, or blocks incorrectly received to the total number of bits, elements, characters, or blocks sent during a specified time interval. The error ratio is usually expressed in scientific notation; for example, 2.5 erroneous bits out of 100,000 bits transmitted would be 2.5 out of 105 or 2.5 × 10-5.

Subscriber Terminal – The cable television system terminal to which a subscriber's equipment is connected. It is basically where your subscriber's equipment (TV, VCR, etc.) connects to your equipment (at the output of the set-top box you provide, at the end of the drop cable, etc.).

System Noise - That combination of undesired and fluctuating disturbances within a cable television channel that degrades the transmission of the desired signal and that is due to modulation processes or thermal or other noise-producing effects, but does not include hum and other undesired signals of discrete frequency. System noise is specified in terms of its rms voltage or its mean power level as measured in the 4 MHz bandwidth between 1.25 and 5.25 MHz above the lower channel boundary of a cable television channel.

Application Note - TechComplete™ Test Productivity Pack ...

Documents

Transcript of Application Note - TechComplete™ Test Productivity Pack ...