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

From design to accepted recordAn approved baseline becomes assigned work; field deviations are recorded and reviewed before acceptance, while the baseline and decision history remain available.Approved designKeep the baseline and versionAssigned workDefine scope and evidence requirementsField deviationRecord the change, reason and evidenceQuality reviewReview the change against the baselineAccepted as-builtUpdate inventory; retain the history
From design to accepted recordAn approved baseline becomes assigned work; field deviations are recorded and reviewed before acceptance, while the baseline and decision history remain available.Approved designKeep the baseline andversionAssigned workDefine scope and evidencerequirementsField deviationRecord the change, reasonand evidenceQuality reviewReview the change againstthe baselineAccepted as-builtUpdate inventory; retainthe history
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.

This website remembers your cookie preference in this browser. Google Analytics 4 is optional and loads only after you allow analytics.

With your permission, Google Analytics 4 (Google) measures page visits and usage to help us improve this website. Advertising features are disabled. Analytics cookies (_ga and _ga_*) expire within 90 days. Google may process analytics data outside your country; data retention is controlled by the Analytics property settings. You can withdraw your permission at any time using the controls above.

Save the essential-only preference to turn analytics off, or change your cookie preferences to allow it. Withdrawing consent stops analytics and removes its cookies from this browser.