SC-Wiki24

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
**''see last modified date at base of all pages''**

{{:opencart_-_logo-268x50.png?nolink&200|}}
===== Naming convention used by SupportCALL =====
----

Here we will explain a simple and good naming convention to use.
This is also the naming convention that we use.
This can be applied to anything.

**Note:** Simple & Logical.

''Think Big to small''

eg. **World, Continent, Country, State/Province, City, Suburb, Street, House** 

eg. **Human, South Africans, Capetonians**

So let's say you need to reference a port on a patch panel is a data centre.

**''SC-DC02-RK4-PP3-P14''**
  * **SC** = Location Name (town, building, country)
  * **DC02** = Data Centre #02
  * **RK4** = Rack #4
  * **PP3** = Patch Panel #3
  * **P14** = Port #14

A wallbox could be...

**''RK1-PP2-DP17''**
  * **RK1** = Rack #1
  * **PP2** = Patch Panel #2
  * **DP17** = Data Point #17

Use common names and the actual name of something...
eg. **Data Centre, RacK, Data Point, Wash Room**


-----


===== Professional Guide to ICT Labelling in Office Environments =====

Proper labelling in office environments is essential for maintaining organization, ensuring efficient workflow, and reducing the risk of errors. This guide covers detailed labelling practices for data cabinets, patch panels, switches, equipment, and wall data and communication points.

===== 1. Office Environment Labelling =====

=== 1.1 Data Cabinets ===

  - **Cabinet Identification**: Label each data cabinet with a unique identifier.
  - **Front and Back**: Labels should be placed on both the front and back of the cabinet.
  - **Label Content**: Include cabinet number, location, and contents overview.
  - **Example**: 

   Cabinet A1 - Floor 2 - Network Equipment

=== 1.2 Patch Panels ===

  - **Port Numbering**: Number each port sequentially.
  - **Label Both Ends**: Ensure that each patch cable is labelled at both ends with the corresponding port number.
  - **Consistent Format**: Use a consistent format for labels to avoid confusion.
  - **Example**: 

    PP1-01, PP1-02, ...

=== 1.3 Switches ===

  - **Switch Identification**: Label each switch with a unique identifier.
  - **Port Labelling**: Number each port and ensure they are labelled on both the switch and the connected device.
  - **Label Content**: Include switch ID, port number, and connected device information.
  - **Example**: 

     SW1 - Port 01 - Device A

=== 1.4 Equipment ===

  - **Device Labelling**: Label all equipment with a unique identifier.
  - **Cable Management**: Ensure all cables are labelled with the source and destination information.
  - **Label Content**: Include device name, function, and IP address if applicable.
  - **Example**: 

      Server 01 - File Server - 192.168.1.10

=== 1.5 Wall Data and Communication Points ===

  - **Port Numbering**: Number each wall port sequentially and consistently.
  - **Label Content**: Include port number and destination (e.g., Patch Panel Port).
  - **Example**: 

  WP-01 - PP1-01

==== 2. Data Centre Labelling ====

Labelling in a data centre requires a higher level of detail and consistency due to the complexity and scale of the environment.

=== 2.1 Data Cabinets ===

  - **Cabinet Identification**: Label each cabinet with a unique identifier and location code.
  - **Front, Back, and Side**: Place labels on the front, back, and sides of the cabinet for visibility.
  - **Label Content**: Include cabinet number, row number, and data centre zone.
  - **Example**: 

  Cabinet R1-C2 - Row 1 - Zone A

=== 2.2 Patch Panels ===

  - **Port Numbering**: Sequentially number each port and use a standard format across all patch panels.
  - **Label Both Ends**: Each patch cable should be labelled at both ends with the corresponding port number and rack location.
  - **Example**: 

  PP1-R1-01, PP1-R1-02, ...

=== 2.3 Switches ===

  - **Switch Identification**: Label each switch with a unique identifier and location code.
  - **Port Labelling**: Number each port sequentially and ensure they are labelled on both the switch and the connected device.
  - **Label Content**: Include switch ID, port number, and connected device information.
  - **Example**: 

  SW1-R1 - Port 01 - Device A

=== 2.4 Equipment ===

  - **Device Labelling**: Label all equipment with a unique identifier, rack location, and device function.
  - **Cable Management**: Ensure all cables are labelled with the source and destination information, and use colour-coded labels for different types of connections.
  - **Label Content**: Include device name, function, rack location, and IP address if applicable.
  - **Example**: 

  Server R1-C2-01 - File Server - 192.168.1.10

=== 2.5 Wall Data and Communication Points ===

  - **Port Numbering**: Number each wall port sequentially and consistently within each zone.
  - **Label Content**: Include port number, zone, and destination (e.g., Patch Panel Port).
  - **Example**: 

  WP-ZA-01 - PP1-R1-01

===== Best Practices for Labelling =====

  - **Consistency**: Maintain consistent labelling formats across all environments.
  - **Durable Labels**: Use high-quality, durable labels that can withstand environmental conditions.
  - **Clear and Readable**: Ensure all labels are clear and readable, using large fonts and contrasting colours.
  - **Documentation**: Keep detailed documentation of all labelling schemes and update it regularly.

By following these guidelines, you can ensure a well-organized and efficient office or data centre environment, reducing downtime and improving workflow management.