Tuesday, November 24, 2009

Service Problems: Mitigate the Ingress in Your Plant

Ingress, the troublesome noise within your plant, organically finds its way into your system by way of cracked outside plant cable, loose connectors, bad drops and fitting, etc. Ingress also enters the plant from within the home where RF cabling in uncontrolled.

Ingress travels the reverse path with cable modem data from the home to the headend. As different types of ingress build within the reverse portion of the network, it is sure to start interfering with your cable modem data carriers. This can destroy the integrity of any data being transmitted. This means, disruption of customer services including impaired or completely offline data and voice services.

If ingress is left uncorrected in your plant, not only will you pay more to get it out, but your revenue streams and service quality will suffer.

 So how do you take the ingress out of the plant?

Detect the Sources of the Ingress

To locate where the ingress is infiltrating, each node needs thorough examination. While many systems have a number of large points of ingress, the most common sources are a multitude of small problems that accumulate to typically become a major network impairment.

Repair Problem Areas

Depending on the cause of infiltration and location, hard line cables or drop cables may need to be repaired. If the noise is coming from inside the home, filters could be added to the drop plant to block the noise traveling to the headend.

Determining the location of the ingress and mitigating it is a time-consuming and labor-intensive job that your in-house technicians may be too busy to handle.


Having a continuous eye on your plant will ensure ingress won't get the best of your network. In a previous blog, Take Better Care of Your Plant in 3 Easy Steps, we discussed the three ways you can take better care of your plant. The three steps include:


To receive more ideas on how to get the most out of you network, subscribe to this blog. CCI is also on
Twitter.

No comments:

Post a Comment