Skip to content
Weezie

Planning and design

From FTTH design to as-built

Connect baseline, field change, and accepted record.

Version 1.0

Baseline and deviation state diagram

State diagram from approved design through work package, recorded field deviation, quality review, and accepted as-built network
The route object keeps one identity while its approved design, field observations, review decision, and accepted operational state remain distinguishable and traceable.

Worked example: duct obstruction

Deviation record

A crew encounters a blocked duct and proposes a route around the obstruction. The deviation record identifies the approved baseline, changed geometry, reason, affected quantities, photographs, responsible technician, and any connectivity or capacity consequence before the alternative is treated as as-built truth.

Design reviews the proposed route while construction continues only within the agreed boundary. QA then validates the evidence and approval, and the accepted geometry updates inventory without deleting the original design or the decision history.

Handover checklist

  • Identify the approved design version and the assumptions used to create the work package.
  • Give the crew explicit scope, network context, materials, instructions, and evidence requirements.
  • Record each field change as a deviation with reason, owner, impact, and supporting evidence.
  • Validate geometry, asset attributes, splice records, measurements, photographs, and approvals.
  • Promote only accepted changes into the operational model while retaining the baseline and review history.