Colocation Post-Installation Information Submission SOP
1. Table of Contents
- Purpose & Scope
- Required Information
- Standard Submission Format
- Operational Notes (Internal)
- FAQ
- Summary
- Use Case
Purpose & Scope
This SOP outlines the required post-installation information that must be submitted by clients or iCoreHosting engineers after any server or equipment is installed in the colocation rack.
The objective is to ensure accurate asset tracking, network mapping, PDU allocation, and compliance with iCoreHosting's internal audit and datacenter operations standards.
Required Information
After installation, the following information must be recorded and submitted:
- IP Address Assigned: Example: 103.6.xxx.xxx
- Datacenter / Rack / RU: Example: CJ1 / 1F-D03 / RU12
- Network Port Mapping: Example: RU13 port 3 / RU12 port 2
- PDU Port Mapping: Example: PDUA-B8 / PDUB-A8
- Installation Date & Time: Example: 21 November 2025, 14:30
- Installed By (Internal): Engineer Name / Team
- Client Representative (If Applicable): Name / Contact
These details are compulsory for:
- Internal colocation audit
- Support traceability
- Power usage monitoring
- Network troubleshooting
- Rack space documentation
Standard Submission Format
All submissions must follow this exact format for standardization:
IP Address: Datacenter / Rack / RU: Network Port: PDU Port: Installed Date: Installed By (Internal): Client Representative:
Submission channels:
- iCoreHosting Support Ticket (Preferred)
- Internal Engineering Log System
- Email to [email protected]
- WhatsApp Support (Only when ticket access is unavailable)
Operational Notes (Internal)
1. Engineering Verification
Internal engineers must verify the following before closing installation tasks:
- Correct rack and RU placement
- Network port link status tested
- PDU port allocated and labelled
- Photo taken for audit (front and back)
2. Audit Record Storage
All installation info must be stored in the internal audit folder for the corresponding client.
3. Change Management
Any later changes (port swap, PDU change, RU movement) must be resubmitted using the same format.
FAQ
Q1: Why is this information mandatory?
For accurate network, power, and rack documentation needed during audits, troubleshooting, and resource planning.
Q2: Who is responsible for submitting the information?
Clients installing their own equipment must submit it.
If installation is done by iCoreHosting engineers, internal staff will submit on behalf of the client.
Q3: What happens if information is incomplete?
Support response time may be delayed, and certain technical actions may be paused pending verification.
Q4: Can I update the information later?
Yes. Any movement or port changes must be updated immediately for audit consistency.
Summary
This SOP ensures all colocation installations are properly documented with accurate and consistent information. This process supports internal audits, improves troubleshooting speed, and maintains accurate rack, network, and power allocations.
Use Case
Example: During a PDU overload alert, engineers can immediately identify which server is connected to which PDU port, verify the actual load, and take action without needing physical tracing. This prevents downtime and speeds up incident resolution.
