Cable connections

Cable work is recorded as a connection from one port to another, with cable type, cable identity and installation date. The connection belongs to an incident record. That link lets an Incident Coordinator see which patch work was associated with an operational event and lets the Service Technician return to the same cable identity during follow-up.

Port text should use the names staff see on equipment. If one end is recorded as a panel position and the other as a device port, write both in a convention the next technician can recognize. The cable identity must identify the installed cable rather than an informal description. Record the date of actual installation so that an earlier patch is not mistaken for the response under review.

The Service Technician enters the patch observation; the Incident Coordinator keeps the operational record coherent.

• Two endpoints. The from and to ports describe the connection being checked.
• Cable identity. A required cable identifier carries the physical label into the record.
• Incident context. The patch record points to the incident that prompted it.

Agree on port naming, cable labeling and when to create a new connection record. Decide who verifies work at the panel and who may correct an entry made during a busy response. Give technicians a sample incident and labeled cable to rehearse the whole entry. If another cabling inventory is authoritative, agree how its identifiers will be reconciled with the records here.

An incident linked to a service and asset requires a patch. The technician reads the physical labels, records both ports, cable identity, type and installation date, then links the patch to that incident. The Incident Coordinator can read the update alongside the incident’s assigned person and current state. A later investigator can see the cable record without treating it as a free-standing diagram of the whole facility.

Submit the same example with a blank port or cable identity, then with an incident link that cannot be resolved. The entry should be rejected with a useful reason. Correct it and check that the saved connection is attached to the intended operational record.

• Cable connections — Patch identity, endpoints, installation date and the linked incident.
• Open incidents — The operational work to which a patch can be attached.

Trace physical work and follow an incident.