BICSI OSP common mistakes
BICSI OSP · Understand the traps and how to avoid them.
Treating the minimum cover requirement as a single number memorized for 'buried cable' rather than as a table keyed by cable type, installation method (direct-buried, in conduit, under a road), and surface condition, so answers are chosen from a remembered figure instead of the governing condition stated in the stem.
Candidates study cover depth as a flashcard fact and never build the decision table, so when the item supplies a specific condition (railroad crossing, cultivated field, sidewalk) they default to the most familiar number rather than the one the condition requires.
What to do instead
Build a one-page matrix of cover depths with rows for direct-buried vs. conduit vs. duct and columns for the surface types named in the standards; before answering, underline the condition words in the stem and read across that row. Practice by writing the table from memory weekly until the condition-to-depth mapping is automatic.
Confusing the roles of the route survey and the design package: treating the survey as a design step and producing a design that omits documented field conditions such as existing utilities, water table, rock, easements, or aerial clearance obstructions.
Survey and design are taught as adjacent topics, so candidates collapse them; the exam then tests whether the field data actually drives design decisions, and a design built on assumed conditions fails those items.
What to do instead
For every design scenario, explicitly list the survey inputs first (utility locates, soil/rock notes, water table, easement status, attachment heights, span lengths) and then show how each one changes a design choice. Answer items by asking which field fact the option depends on; options that assume unverified conditions are usually the distractors.
Mixing up cable counts and pair-count conventions when specifying or terminating copper cable, e.g., treating a 25-pair binder group, a 100-pair super-unit, and total pair count as interchangeable, or misstating how pairs are counted in a splice.
Counting conventions are learned on the job in one vendor's color code and never generalized, so under exam pressure candidates apply the convention they saw most recently rather than the one the question's cable construction implies.
What to do instead
Drill the binder-group hierarchy and the standard 25-pair color code in both directions (count to color, color to count) until you can state the group and pair for an arbitrary position. When an item gives a cable size, first convert it to binder groups and super-units in writing before evaluating the answers.
Selecting fire-rated or listed cable and pathway products by general product family rather than by the specific listing, rating, and installation environment the item describes (riser vs. plenum vs. underground vs. aerial, and the corresponding marking on the cable).
Candidates memorize that certain spaces require certain cable types but do not connect the requirement to the printed legend on the cable or to the pathway component's listing, so items that hinge on the marking or the environment are answered from impression rather than rule.
What to do instead
Make a table pairing each environment (plenum, riser, general purpose, underground, aerial) with the required cable marking and the pathway/hardware listing that goes with it. For each practice item, state the environment out loud first, then eliminate every option whose marking or listing does not match that environment.
Applying bonding and grounding rules to the wrong point in the system: bonding at only one end of a metallic shield, grounding a closure to a separate ground rod instead of the required grounding electrode system, or omitting bonding across a splice or transition.
Grounding is studied as a general electrical concept, so candidates import intuition (single-point grounding, independent rods) that conflicts with OSP practice, where shields and metallic members are bonded along the run and tied to the building or system electrode.
What to do instead
Draw the full bond path for a sample route: every splice point, every metallic member, every entrance, and the electrode it terminates at. Learn the reasons behind each bond (fault current, lightning, potential equalization) so that an option proposing an isolated ground or a single-ended bond is recognized as wrong on principle, not memory.
Specifying a pull tension, bend radius, or conduit fill without computing it: quoting a generic maximum pull tension or fill percentage instead of deriving the value from cable diameter, weight, coefficient of friction, and the number of bends in the run.
Field rules of thumb get memorized as absolutes, but exam items supply the inputs and expect the candidate to apply the relationship; candidates who never practiced the calculation cannot tell which given value is the limiting one.
What to do instead
Practice the pull-tension relationship (tension from cable weight, length, and friction, plus the multiplier for each bend) and the fill calculation from conduit and cable cross-sectional areas. In items, identify the limiting factor first (usually bends or fill), compute it, and only then compare with the offered answers.
Ignoring the sequence and hold points of the construction process, answering as if installation, testing, and restoration can be reordered or as if acceptance testing is optional when the specification or contract requires it.
Candidates focus on physical installation technique and treat documentation, inspection hold points, and test-and-accept as administrative afterthoughts, so items about when a step must occur or what must precede backfill are missed.
What to do instead
Write the standard sequence for an underground and an aerial job end to end, marking the points where inspection or testing must occur before work proceeds (before backfill, before restoration, before acceptance). Answer sequencing items by locating the step in that written sequence rather than judging plausibility.
Treating the project management knowledge areas as separate vocabulary instead of applying them to a scenario: choosing a schedule compression action without checking its effect on cost and risk, or responding to a change request by proceeding with work rather than through the change control process.
PM material reads as definitions, so candidates memorize terms and then pick the definitionally correct-sounding option rather than the option that follows the process or the constraint hierarchy in the scenario given.
What to do instead
For each PM topic, practice one scenario and answer by asking 'what does the process require next?' rather than 'which term fits?'. Memorize the change-control sequence and the tradeoff among scope, schedule, cost, and risk, and eliminate any option that performs work before authorization or ignores an impact.
Estimating materials and quantities without accounting for the allowances that the design and contract require (slack, service loops, splice enclosures, waste, and spare capacity), producing quantities that are arithmetically clean but wrong for the installation.
Candidates compute the straight route length and stop, because allowances are learned as field habits rather than as specified quantities, and exam items deliberately supply a route length with the allowances named separately.
What to do instead
Adopt a fixed checklist for every quantity item: measured length, plus vertical and horizontal slack, plus termination and splice allowance, plus waste factor, plus specified spare capacity. Show each addition on scratch paper so an option that equals the bare route length is immediately recognizable as the trap answer.
Reading code and standards citations from memory of the number rather than from the requirement's scope: citing a separation or clearance rule without checking whether it applies to the utility type, voltage class, or crossing geometry in the item.
Candidates memorize distances and section numbers but not the conditions that trigger them, so items that change the utility type or the crossing angle are answered with a distance that belongs to a different situation.
What to do instead
For each clearance or separation rule you study, record the scope alongside the number (what utilities, what voltage, what crossing or parallel condition, what surface). In items, state the scope conditions first and reject any option whose number belongs to a scope the stem does not describe.