FOA CFOS/L study materials
FOA CFOS/L study resources

FOA CFOS/L: Network Design, Project Management and Documentation

FOA CFOS/L · Work through your exam, one topic at a time.

All guide sections

Network Design, Project Management and Documentation

What the exam tests

This domain tests link design, project planning, and as-built documentation: choosing fiber and optics from distance and bandwidth, planning pathways and schedules, and handing over records that let the plant be maintained.

Core rules

  • Design from requirements: bandwidth, distance, environment, redundancy, and growth. Select multimode OM3/OM4/OM5 for short premises links and OS2 single-mode for long or future-proof backbone runs.
  • Check the standard reach: 10GBASE-SR is 300 m on OM3 and 400 m on OM4; 10GBASE-LR is 10 km on OS2. If the distance exceeds the reach, change fiber or optics, not the test limit.
  • Plan pathways and spaces early: conduit fill, bend radius, telecom room size, power and cooling, and separation from EMI.
  • Project management: scope, bill of materials, schedule, permits, safety plan, inspection hold points, and commissioning. Track changes; do not substitute cable ratings without approval.
  • Documentation: as-built drawings, rack elevations, cable schedules, TIA-606 labels, test reports, OTDR traces, loss budgets, and warranty records. Deliver digital and physical copies.

Worked example

A campus link is 1.5 km between buildings and must support 10 Gb/s now with 40 Gb/s growth. 10GBASE-SR on OM4 reaches only 400 m, so multimode fails the distance requirement. Choose OS2 single-mode with 10GBASE-LR, which reaches 10 km; verify the loss budget at 1310 nm, including connectors, splices, and margin. Document the fiber assignments, patch-panel ports, and OTDR traces. Reasoning: distance eliminates short-reach multimode first; the loss budget and documentation prove the design will work and can be maintained.

Traps

  • Designing to a typical reach rather than the standard reach.
  • Using OM3 for a 500 m 10G link because a datasheet lists a longer reach for a different Ethernet rate.
  • Skipping as-builts, then being unable to trace a fault.
  • Labeling with room names that change instead of a stable TIA-606 scheme.
  • Forgetting growth and repair margin in the loss budget.