Structured Cabling Repair Expectations and Process

Network Team Structured Cabling Repair Expectations

All structured cabling repair requests should be sent to Network Team. Network Team will determine the correct course of action for repairs.

Contacting Network Team for Repairs:

  • Non-Urgent Repair Requests
  • Urgent Repair Requests:
    • Contact Network Team in Teams via the OIT-Network Channel.
      • Contact Mike Rusca, Chris Riddlemoser Directly via teams or phone
        • Contact Brian Jemes directly via Teams or phone
    • Contact Network Team via emergency messaging service (208) 885-2002
      • The emergency message service will
        • Forward the voice message to the mobile phone of everyone in Netteam immediately, and will call out until a team member confirms they are working on the issue.

Structured Cabling Repair Process

Once Network Team has been made aware of a need for a cabling repair, netteam will determine the next steps, warranty repair, or out of warranty repair.

Warranty Repair:

When Network Team determines cabling under manufacturer warranty, we will contact our contracted cabling partner for the region in which the repair is to occur. The contracted cabling provider will repair and re-certify the cable at no cost.

Moscow:
If response time is critical for Moscow campus, NetTeam may contact Facilities Electric Shop to repair and re-certify the cable.  There will be a cost associated.

Non-Warranty Repair: Moscow

When Network Team determines cabling is not under manufacturer warranty, we will contact the Facilities Electric Shop to complete this work. If the Electric Shop declines this work, we will contact our stuctured cabling partner for North Idaho to complete this work. There may be a cost associated.

Non-Warranty Repair: Rest of the State

When Network Team determines cabling is not under manufacturer warranty,  we will contact our stuctured cabling partner for the region in which the repair is to occur to complete this work. There may be a cost associated.

Print Article

Details

Article ID: 3122
Created
Fri 8/9/24 10:32 AM
Modified
Mon 8/19/24 2:03 PM