BICSI RCDD common mistakes
BICSI RCDD · Understand the traps and how to avoid them.
Treating the horizontal cabling maximum distance as 90 m of cable plus 10 m of patch cords/equipment cords as a single combined 100 m limit, and applying that 100 m to the permanent link.
Candidates blend the permanent link and channel limits, forgetting that the 90 m horizontal cable limit excludes the cords and that the 100 m channel total includes them.
What to do instead
Memorize the two-link model explicitly: permanent link = 90 m horizontal cable (plus up to 5 m of work-area/telecom-room consolidation allowance depending on the standard's model), channel = 100 m total including cords. Practice labeling a diagram of each as a separate budget before answering.
Selecting cable category or media based on the current device speed rather than on the required supported frequency, distance, and the standard's channel performance class.
Candidates anchor on familiar device speeds (e.g., '1 Gb needs Cat 5e') instead of mapping the application to the standard's class/frequency requirements and distance constraints.
What to do instead
Build a small table mapping common applications to minimum media class and maximum supported distance, and answer from the table rather than from device-speed intuition.
Sizing telecommunications spaces (TR/ER) by room aesthetics or by the number of racks rather than by the standards' area, clearance, door, and environmental criteria.
Candidates recall that a TR must be 'adequate' but not the specific minimum dimensions, clear working space, dedicated power, or environmental limits, so they guess.
What to do instead
Memorize the TR/ER sizing rules as a checklist (minimum floor area, ceiling height, door size/swing, dedicated HVAC and power, lighting, no water/sewer piping overhead) and rehearse applying it to a floor plan.
Routing pathways through spaces that are prohibited for telecommunications (e.g., through elevator shafts, hazardous areas, or sharing a pathway with high-voltage power without the required separation) to shorten the run.
Candidates optimize for distance and cost and overlook the separation and prohibited-location rules that constrain pathway design.
What to do instead
Study pathway separation and prohibited-location rules as hard constraints, and for every routing question first ask 'is this location/separation permitted?' before evaluating length.
Confusing the roles and separations of entrance facility, equipment room, and telecommunications room, and placing equipment in the wrong space.
The functional boundaries between EF, ER, and TR overlap in real projects, so candidates merge them and misplace demarcation or active equipment.
What to do instead
Draw the hierarchy (EF -> ER -> TR -> work area) with what belongs at each level, and classify each piece of equipment by function and location before answering.
Applying a bonding/grounding or firestopping requirement as an afterthought or omitting it because the question focuses on cabling counts.
These are 'invisible' infrastructure items that candidates under-weight when the question's surface topic is cabling or pathways.
What to do instead
Treat telecom bonding/grounding and firestopping as mandatory scope items: when reviewing any design or installation scenario, explicitly check both before finalizing the answer.
Answering project-management questions by choosing the most technically thorough option rather than the option that matches the project's defined scope, budget, schedule, or change-control process.
Technically minded candidates equate 'more/better' with 'correct' and ignore that scope changes require formal change control and that gold-plating violates the baseline.
What to do instead
For PM questions, identify the constraint being tested (scope, time, cost, quality, risk) and pick the option that follows the documented process, not the most elaborate technical solution.
Skipping the administration/documentation deliverable (as-builts, labeling, test records, cable schedules) because the question emphasizes installation.
Candidates view documentation as clerical and focus on the physical work, missing that handover records are required deliverables.
What to do instead
Memorize the standard closeout/administration package (as-built drawings, test results, labeling scheme, cable records, warranties) and treat it as part of every installation answer.
Misreading the question stem for qualifiers like 'EXCEPT', 'BEST', 'minimum', or 'not required', and answering the inverse of what is asked.
Under time pressure, candidates pattern-match to a familiar concept and miss the negation or superlative that changes the correct answer.
What to do instead
Adopt a habit: before selecting, underline the operative qualifier and restate the question in your own words; for 'EXCEPT' questions, eliminate the three true statements first.
Using memorized numeric values (distances, counts, separations) without checking which standard or edition the question references, and applying a value from the wrong context.
Many numbers differ by media type, application, or standard edition, so a memorized figure is often right in one context and wrong in another.
What to do instead
Store each number with its context tag (media, application, standard) rather than as a bare value, and when a question gives a context, retrieve the matching tagged value instead of the most familiar one.