Design Basics
Design Basics
Design Basics is the vocabulary and logic layer of the RCDD exam: the concepts you use to justify every later decision. A candidate must be fluent in the hierarchy of standards and codes (codes are legally enforceable; standards are consensus best practice; guidelines are advisory), the meaning of shall versus should versus may, and the difference between a requirement and a recommendation. Know the service-life and capacity-planning mindset: design for the owner's growth horizon, not just today's device count, and document assumptions.
Core concepts include: the usable vs. total area distinction, the role of a technology/ICT designer as an advocate for the owner, life-cycle cost versus first cost, scalability, redundancy and diversity (separate paths, not just duplicate equipment), and pathways and spaces as the backbone that is hardest to change later. Understand design phases (programming, schematic/concept, design development, construction documents) and what deliverable belongs to each.
Traps to watch: confusing redundancy with diversity; treating a guideline as a code; assuming more outlets always means better design without considering density and cost; and forgetting that future capacity (conduit fill, spare counts, rack space) is a design requirement, not an afterthought. Questions often ask which decision is most appropriate when budget conflicts with growth - the answer usually favors documented, scalable infrastructure.
Rule of thumb: design spare capacity so that a single failed component or a near-term growth step does not force a redesign - e.g., keep spare conduit capacity and rack units, and size pathways for the projected device count plus a healthy margin. When in doubt, choose the option that preserves future flexibility and is documented.