homeapartmentpencilmagic-wanddroplighterpoopsunmooncloudcloud-uploadcloud-downloadcloud-synccloud-checkdatabaselockcogtrashdiceheartstarstar-halfstar-emptyflagenvelopepaperclipinboxeyeprinterfile-emptyfile-addenterexitgraduation-hatlicensemusic-notefilm-playcamera-videocamerapicturebookbookmarkuserusersshirtstorecarttagphone-handsetphonepushpinmap-markermaplocationcalendar-fullkeyboardspell-checkscreensmartphonetabletlaptoplaptop-phonepower-switchbubbleheart-pulseconstructionpie-chartchart-barsgiftdiamondlineariconsdinnercoffee-cupleafpawrocketbriefcasebuscartrainbicyclewheelchairselectearthsmilesadneutralmustachealarmbullhornvolume-highvolume-mediumvolume-lowvolumemichourglassundoredosynchistoryclockdownloaduploadenter-downexit-upbugcodelinkunlinkthumbs-upthumbs-downmagnifiercrossmenulistchevron-upchevron-downchevron-leftchevron-rightarrow-uparrow-downarrow-leftarrow-rightmovewarningquestion-circlemenu-circlecheckmark-circlecross-circleplus-circlecircle-minusarrow-up-circlearrow-down-circlearrow-left-circlearrow-right-circlechevron-up-circlechevron-down-circlechevron-left-circlechevron-right-circlecropframe-expandframe-contractlayersfunneltext-formattext-format-removetext-sizebolditalicunderlinestrikethroughhighlighttext-align-lefttext-align-centertext-align-righttext-align-justifyline-spacingindent-increaseindent-decreasepilcrowdirection-ltrdirection-rtlpage-breaksort-alpha-ascsort-amount-aschandpointer-uppointer-rightpointer-downpointer-left

Additonal details in a test report

30.06.2023 In a test report there have to be the test results and the values specified by the standards. That’s a no-brainer. However, in a test report there has to be a lot of additional information. Read on to learn the details.

 

According to EN 50174-1:2018 and EN 50346:2010, there have to be much more details in a test report than just the test results and the correspondig values specified in the cabling standards. These are:

 

  • Validation of the test results
    (Pass, Fail, *Pass, *Fail)
  • Teste (local and remote unit)
    • Manufacturer
    • Type
    • Serial number
    • Calibration
    • Software release
    • Testing accuracy
  • Test adapter/test cords
  • Manufacturer
  • Type
  • Serial number or user-defined number (e.g. for patch cords
  • Category (test cords)
  • Link type: Permanent link, channel, ...
  • Standard/test procedure (e.g. ISO/IEC 11801 permanent link class EA 2 connector/configuration B)
  • Date of test (It is also a good idea to add the time in case a link is tested several times)
  • Ambient details (temperature, etc.)
  • Name of the person who did the test
  • Name/number of the tested link
  • Details of the tested link (manufacturer, type and part number of the installed components, special features of the link, etc.)

It is wise to include these points in the test report if possible, then one has everything together. Many testers allow to enter most of the points listed above upfront testing. The tester then automatically adds them to the test reports.

 

EN 50174-1 demands a certificate or a similar document of the tester’s calibration and that the documentation of the testing has to be kept.

 

The next episode will focus on test results with a star: *Pass and *Fail.

 

Author:

Dirk Traeger

Technical Solutions Manager DataVoice