Project Planning and Design Specification

Why Planning Comes First

In a professional data center build, no cable is run and no server is racked until a complete project plan exists and has been reviewed. This is not bureaucracy — it is how technicians avoid overloaded circuits, hot-aisle bypass, unsafe wiring, and rework that costs far more than the planning time saved. Your capstone project mirrors real industry practice: you will produce five planning documents before you touch any physical equipment, and your instructor must approve all five before lab access is granted.

Reading the Client Scenario

Every data center build starts with a client brief. Your two-page scenario describes the server count, the available power budget (expressed as a circuit amperage or total kilowatt allowance), the cooling requirement, and the security tier. Read it carefully and build a structured requirements list before drawing anything. A requirements list answers four questions for every major item: What is needed? How many? What are the power and thermal specs? What are the constraints (rack units available, cable path length, clearance rules)?

BICSI's Telecommunications Distribution Methods Manual (TDMM) is the standard reference for structured cabling design in data centers. Your excerpts cover minimum bend-radius rules, horizontal and vertical pathway sizing, and documentation requirements — all of which feed directly into your cable schedule.

Rack-Elevation Diagram

A rack-elevation diagram is a scaled front-view drawing of a rack cabinet showing every device assigned to every rack unit (U) position. Standard racks are 42U tall. Each device occupies 1U, 2U, or more. The diagram must:

• Show the rack to scale (each U equal in height).
• Label every device by name and U position (for example, "Server A — U14–U15").
• Show the patch panel port assignments and PDU (power distribution unit) receptacle numbers for each device.
• Leave planned blank-panel positions visible so airflow gaps are intentional, not accidental.

Use Visio or draw.io (free tier) for your drawing. Handwritten diagrams are not accepted because scale and legibility cannot be verified reliably. Your instructor will check that the diagram is internally consistent — every device listed in the requirements appears in the rack, and no U position is double-booked.

Cable Schedule

A cable schedule is a table that lists every cable in the build: an ID number, origin port, destination port, cable type and category, length (measured or estimated from the pathway), and color. A complete cable schedule allows any technician — not just you — to verify, replace, or trace a connection without guessing. Missing entries or unlabeled ports are revision-required errors on your approval checklist.

Power-Load Worksheet

Data centers run on branch circuits that have a defined amperage rating. The National Electrical Code (NEC) limits continuous loads to no more than 80 percent of a circuit's rated capacity to prevent nuisance tripping and overheating. Your worksheet requires you to:

1. List every device's nameplate wattage (use the label on the equipment or the manufacturer datasheet).

2. Sum all nameplate wattages to get total load in watts.

3. Convert watts to amps using the formula: Amps = Watts ÷ Volts (use 120 V for standard US branch circuits or 208 V for high-density circuits as specified in the scenario).

4. Divide your calculated amps by the circuit's rated amperage and multiply by 100 to get load percentage.

5. Flag any result above 80 percent as an overload risk requiring redesign.

Nameplate wattage is a worst-case figure. Actual draw is typically lower, but you always plan for worst-case to stay safe.

Airflow: Hot-Aisle/Cold-Aisle Strategy

Servers draw cool air from the front (cold aisle) and exhaust hot air from the rear (hot aisle). Racks must be oriented so all fronts face a cold aisle and all rears face a hot aisle. Never mix orientations in a row. Your airflow plan is a top-down diagram showing:

• Aisle labels (cold/hot alternating).
• Direction of server airflow (arrows).
• Location of computer room air conditioning (CRAC) or computer room air handler (CRAH) units.
• Any containment panels or blanking panels used to prevent hot and cold air from mixing.

Missing blanking panels in unused U positions allow hot exhaust to recirculate into cold-aisle intakes, raising inlet temperatures and causing thermal throttling or shutdowns.

Pre-Work Safety Checklist

Before any physical work begins, you must complete a safety checklist that identifies:

• Required PPE: At minimum, safety glasses and ESD wrist strap for electronic work; steel-toed shoes if heavy equipment (servers, UPS units) will be lifted.
• LOTO points: Lockout/tagout (LOTO) is required by OSHA standard 29 CFR 1910.147 whenever servicing equipment where unexpected energization could cause injury. Your checklist must identify every energy source (electrical circuits, UPS bypass) that must be locked out before work inside an energized rack or PDU. Never assume a circuit is de-energized — verify with a calibrated meter before touching.
• Lifting plan: Servers can weigh 30–60 pounds or more. Note whether a mechanical lift or two-person lift is required.
• Emergency contacts and exit routes: Required on every site safety document.

OSHA 10 training covers hazard identification, fall protection, electrical safety, and LOTO at a foundational level — all directly applicable here.

Approval Gate

All five documents — rack-elevation diagram, cable schedule, power-load worksheet, airflow plan, and safety checklist — must be submitted together. Your instructor will not approve partial packages. Missing power calculations, missing LOTO points, or diagrams that are not to scale are automatic revisions. Only after written approval may you proceed to the lab build phase.