FTTH network design by zone: A1 drawings, fibers and materials

Q: Which network standards does it accept?

Any that can be described in a profile: 1:8 x 1:8 cascade, 1:4 x 1:16 or another, FAT sizes, cables and TIA-598 buffer colors, slack, losses, optical budget, maximum span and hardware. A profile can inherit from another and change only what differs.

Q: Who reviews the design?

The design is validated against the standard and was tested against real zones designed by hand, but it is an engineering proposal: the person responsible for the build reviews and signs it, and the drawings carry the note to verify details on site.

Q: Is it included in a plan?

Yes, FiberBuild is included in the Enterprise plan of the ISP CRM, at USD 120 per month.

89poles in an Excel, with their routes and their trunk

36.9 sto design the zone and produce the A1 drawings, on a laptop

320customer ports in 40 eight-port FATs, with 0 validation errors

$127,967of materials at reference prices, including fiber, closures, FATs, splitters and hardware

Demo zone: "Colonia Demo", a fictional neighborhood over real streets of Celaya, Guanajuato. Every figure comes from a file the factory generated.

In under a minute

This is how a complete zone comes out

The Excel with the coordinates and the profile with your conventions go in; everything the crew and the build manager need comes out. The video walks through a real demo zone from start to finish, with subtitles and no sound.

What goes in

Pole coordinates and your conventions

No reworking your data for the system: it accepts inputs as you already have them, and whatever changes from one company to another lives in a profile you edit, not in the code.

Inputs

The coordinates, as you have them

Poles: KMZ or KML, DWG or DXF (it detects the block and the pole-number attribute by itself), Excel or CSV with latitude and longitude in decimal or in degrees, minutes and seconds, or UTM coordinates.
Route: KMZ lines, DWG layers or a table with the sequence of poles of each cable (route, order, pole, type). The trunk is detected by name, by color or by being the only line that differs.
Optional base drawing (utility company): if it is not georeferenced, the factory calculates the scale, rotation and offset by comparing pole numbers. It works on a copy and never modifies the original.
Boxes only: with the boxes marked in Google Earth it traces the path along OpenStreetMap streets and estimates the poles. They must be verified with the utility company or in the field.
Homes per pole (optional): sizes each FAT by demand instead of by coverage.

Colonia_Demo_coordenadas_postes.xlsx

The input. One row per pole and route; the demo zone has 89 poles and 9 routes, one of them the trunk.

Profiles

Your standard in a profile, not in the code

Standard: architecture (1:8 × 1:8, 1:4 × 1:16 or yours), FAT sizes, cables and TIA-598 buffer colors, slack formulas, losses, optical budget, maximum span, hardware rules, and material names and costs.
Naming: templates with fields for hub, route, closure, cable, splitter, box and pole: H1R1T1, H1R1-1D1, CTO-001…
Drawing template: the blocks and layers of your company's DXF; if a block is missing, it draws a generic symbol.
Per zone: change a value only in that project, fix closures or FATs by hand or forbid poles for FATs. A profile inherits from another and changes only what differs.
In the ERP profiles are edited on screen and validated before queuing. An optional regulation AI, off by default, proposes adjustments from a text; a person reviews them before the job runs.

estandar: fisher_networks
arquitectura:
    spl1: 8 # cierre T
    spl2: 8 # FAT
    fat_puertos: [8]
    costos: {cierre: 2500, m_distribucion: 14, m_troncal: 19}
cables:
    troncal: {nombre: "ADSS 96H", hilos: 96}
    distribucion: {nombre: "Fig-8 24H", hilos: 24}
    colores_buffer: [AZUL, NARANJA, VERDE, CAFE, GRIS, ...]
reservas:
    caja_paso: "2*H+2+1.5"
optica:
    atenuacion_db_km: {1310: 0.35, 1490: 0.25}
    presupuesto_db: 28.0
reglas:
    vano_max_m: 80
nomenclatura: fisher_hr
    cierre: "H{hub}R{ruta}T{t}"
    fat: "H{hub}R{ruta}-{t}D{dc}"

A fragment of the profile used to design the demo zone. Costs are reference values: replace them with yours.

How it designs

The engineering that used to be done by hand, with rules you can audit

It is not a black box: each step applies a rule of your standard and leaves its result in the report, with the alternatives it discarded.

1 · The route over the poles

It snaps each route vertex to the nearest pole (within 10 m), inserts the poles the line crosses without a vertex and builds the span network. A span longer than 80 m calls for an intermediate pole. Then it builds the shortest-path tree from the entry point, preferring the trunk.

2 · FATs by coverage or by demand

By coverage, every pole is within one span of a FAT. With homes per pole, ports equal homes times take rate and the smallest FAT that covers the demand is chosen; boxes are only placed where there are homes.

3 · Splitters and closures by real cost

It splits the tree into first-level splitters and tries several groupings of T closures; the one with the lowest real cost wins: closures plus fiber to buy. If several splitters go down together along a long branch, it places a closure off the trunk with a single cable.

4 · Cables, buffers and fibers

Splitters of the same closure going down the same street share a cable, one per buffer. Fibers are numbered in route order and every buffer and fiber carries its TIA-598 color. Each splice ends up on its own row.

5 · Losses, slack and hardware

Optical loss at each FAT against the budget, slack loops and storage with your formulas (2*H+2+1.5), tension and suspension hardware pole by pole, materials, and validation against the standard.

6 · Feeder from the NOC

With the NOC coordinates it traces the shortest path along OpenStreetMap streets to the entry of the zone. Its length goes into the dB and into the cable to buy, and it is drawn on the plan and in the KMZ.

Change the standard, the design changes

The same Excel of 89 poles, with two profiles

To show that conventions rule, the demo zone was designed again with a 1:4 × 1:16 standard, a 48-fiber feeder and CE-01 and CTO-001 naming. Same poles, a different network, and neither with validation errors.

	Fisher profile	1:4 × 1:16 profile
Splitters (1st × 2nd level)	1:8 × 1:8	1:4 × 1:16
FATs	40 of 8 ports	31 of 16 and 1 of 32 ports
Customer ports	320	528
PON ports	5	9
T closures	3	3
Distribution cables	4 · 2,187 m	9 · 2,695 m
Trunk fiber to buy	1,505 m of ADSS 96H	1,529 m of ADSS 48H
Distribution fiber to buy	2,848 m of Fig-8 24H	3,237 m of Fig-8 12H
Maximum loss at 1310 nm	23.67 dB	23.67 dB
Closures plus fiber	$75,967	$81,869
Names	H1R1-1D1	CTO-001

Fiber diagram · 1:4 × 1:16 profile

The same diagram with another standard and another naming: closures CE-01 to CE-03 and boxes CTO-001 to CTO-032.

What comes out

Six deliverables, one source

They all come from the same design, so they do not contradict each other: the splice you see in the diagram is the same one in the Excel sheet and the same one the bill of materials counts. The images are real outputs of the demo zone.

A1 drawings in PDF

Sheets ready to print

ROUTE and DIAGRAM on A1 sheets with title block, legend, notes and a standard scale.
Street sketch with curb lines and names, taken from OpenStreetMap (it does not repeat a name the utility-company drawing already labels).
If the network cannot be read on a single sheet at 1:2000, it adds "ROUTE i of n" sheets and an overview sheet with numbered frames.
It is generated without AutoCAD, on the server too.

Colonia Demo · Planos.pdf · sheet 1 of 2

Route sheet. A complete A1 page of the demo zone PDF.

DWG and DXF

The same drawing, to edit

Route, closures, FATs and slack in layers and blocks, mounted on a copy of the utility-company drawing, with the fiber diagram and the notes.
DXF for those without AutoCAD: BricsCAD, QGIS or LibreCAD.
DWG with ODA File Converter (free) or with AutoCAD. In the zones with DWG output, the AutoCAD AUDIT closed with 0 errors introduced by the design.
Every label carries its FAT, cable and loss: 1-2D18, FAT 8P NAR H14, 574m 23.3dB@1310.

Colonia Demo · plano.dxf · detail

Drawing detail. Closure H1R1T2 and its FATs, with fiber, meters and loss.

KMZ

The network, on the map

Trunk, distribution cables, closures, FATs with their fibers and loss, slack and poles, for Google Earth or any KMZ viewer.
Useful for the field visit and for showing the zone to whoever decides, without opening a drawing.
In the ERP the same design is drawn on a map of its own, with each FAT's loss in color.

Colonia Demo · Diseno.kmz over OpenStreetMap

The KMZ drawn over the street map, with its three closures and its 40 FATs.

Fiber diagram

Which fiber goes into each splitter and where it is cut

Fiber by fiber: the buffer and TIA-598 color of each fiber, which fiber feeds each first-level splitter and which ones pass through uncut.
Each FAT with its cable, its buffer, its fiber and the point where it is spliced; branches to another street keep the same fiber number.
Splitter outputs without a customer are marked as spare, and closures off the trunk show the cut and the splice to the branch.
What a person had to work out (the fiber number, the distances and the total number of splices) is written out.

Colonia Demo · Planos.pdf · sheet 2 of 2

Fiber and splice diagram of the whole zone: ODF, three closures and 40 FATs.

Colonia Demo · detail of closure H1R1T2

Detail. Closure T2: three splitters, outputs F2 and F3 and one branch.

Excel

Boxes, fibers and splices, one row for each

Ten sheets: Summary, Closures, FAT, Cables, Splices, Fibers, Materials, Slack, Validation and Coordinates.
Splices: one row per splice (184 in the demo zone), with the location, the pole, the cable, the fiber, the buffer and the color.
Fibers: every fiber of every span, with its use, its destination and the pole where it is cut.
FAT: pole, closure, splitter, cable, buffer, fiber, distance from the ODF and loss at 1310 and 1490 nm.

Cajas_Hilos_Materiales.xlsx · Fusiones sheet

Splices sheet. From the ODF to the closures and from the closures to each FAT.

Cajas_Hilos_Materiales.xlsx · FAT sheet

FAT sheet. Each box with its fiber and its distance.

Bill of materials with costs

What to buy, with its amount

Fiber by type with slack and 3 % waste, closures, FATs, splitters, hardware, strap, splices, ODF and labels.
Editable: change quantities and prices and the total is recalculated; export to CSV. With the expected take rate and the average drop it also adds the customer part.
Hardware pole by pole: 150 tension and 47 suspension pieces in the demo zone.
Profile prices are reference values. In the ERP they come from your warehouse or your purchases.

Colonia Demo · Materiales.html

Materials. Fiber, boxes, splitters and hardware at reference prices: $127,967 MXN, about $400 per customer port.

Accuracy test

It does not grade itself: it is compared with engineers

Each zone was designed using only its KMZ and compared against the design that outside-plant engineers had made by hand, in real zones. More than 50 automated tests run every time a version is packaged.

Test	What it checks	Result
Regression	Reproduce box by box the design of a real zone, made with its own scripts	62 FATs, fibers, cables, slack and hardware identical
Calibration	Real zone, using only its KMZ, against the DWG made by hand	38 FATs by hand; 100 % have a factory FAT within one span or less
Validation (not used for calibration)	Another real zone, with the same profile and no readjustment	41 FATs against 45 (91 %; uncalibrated it was 32, 71 %); 97 % of the hand-placed FATs covered within one span; 18 on the exact same pole
Closures by cost	Automatic closures against the ones placed by hand	3 closures for $206,317 against 4 for $209,355, with the same maximum loss
Different inputs	Excel in degrees, minutes and seconds against KMZ	Identical design
Other standards	1:4 × 1:16, 48 fibers, other naming schemes and templates	0 validation errors
Fiber diagram	Fiber-by-fiber continuity	Every FAT is reached from its PON through a continuous chain of fibers and splices; no fiber repeats in a cable; every splitter output goes to a FAT or stays as spare; the splices in the materials, the model and the drawing match
Traced feeder	NOC to the first closure, along OpenStreetMap streets and by another algorithm	4,953 m against 4,946 m: 0.1 % difference
AutoCAD AUDIT	The generated DWG, opened and audited	0 errors introduced by the design

The comparison zones are real and their names are not published. In one of them the person placed all three closures off the trunk and the factory does not reproduce that layout: there it proposes a different scheme, not the same one with other numbers.

From the drawing to the live network

It does not stay in a PDF: it becomes your ISP's network

A design that is delivered and forgotten stops being true the day the crew moves a box. Inside Fisher Platform the design stays alive until what is built and what is drawn match.

Worker queue

The ERP keeps the queue and the workers ask it for jobs: an always-on Linux server and, if you want, a laptop with AutoCAD. No ports are opened and each worker has its own token.

Revisions and comparison

Every change is a revision. Compare them on FATs, PON, ports, closures, fiber, loss, cost and cost per port, and pick the good one for each project.

Materials with real prices

Each material is matched to an item in your warehouse and takes its purchase price, its average cost or its price. With no price it says "no price", never zero. With one click, a purchase request or a draft warehouse issue.

Poles and utility company

Pole inventory with owner and status (proposed, requested, authorized, installed, withdrawn), an exportable list with hardware, rent per pole or per contract with reminders, and a linked case file.

Business case

Investment in materials and labor, rent and maintenance costs, homes passed, revenue per customer, scenarios, present value and payback month, every figure with its formula and its source.

ISP plant

Closures, splitters, FATs, cables and splices move to the FTTX plant map as planned, without re-entering data. It can be repeated without duplicating and undone while nothing is built.

Field capture

From the phone, with GPS, the crew sees poles, FATs and closures by proximity and marks what is built, moved or nonexistent, with a photo and a note.

As-built

What is marked in the field becomes an "as-built" revision and is reconciled with the plant, with a preview, blocks if customers are connected, and undo.

Connected

It is not an island: it talks to the rest of your CRM

CRM for ISPs

The FTTX plant, the NOC, the ONTs and the outages live in the same system. What you build with FiberBuild is what you later see on the plant map and what a cut affects.

Purchasing and Warehouse

The bill of materials becomes a purchase request or a warehouse issue, with your items and your prices, using Purchasing numbering.

Case files

The pole access request opens as the project's case file with the template you choose, and the pole list comes out already with the real poles.

Filings

Alerts when the design is ready, when it fails, when jobs are waiting and no worker is online, and when a pole rental contract is about to expire.

Bastino

The copilot queries projects, revisions, poles and the business case, and proposes with a confirmation card: queue a design, move it to the plant, mark what is built or request the purchase.

Events and extensions

Every finished revision, every handover to the plant and every pole status change publishes its event. Profiles, field marks and pole owners are open catalogs.

Stated plainly

What it does and does not do yet

Better to know before you sign up than to find out on the build.

Designed with control in mind

A design you can review and a build you can audit

Engineering proposal: the standard validates it and the person responsible for the build reviews and signs it; the drawings ask for details to be verified on site.
Workers with their own token, stored only as a hash, with a per-minute quota and a list of allowed addresses. Files are validated by content and kept outside the public folder.
Separate permissions to view and create designs, for the workers and for field capture.
Nothing is overwritten silently: what is built asks for double confirmation and, if customers are connected, reconciliation is blocked. Bastino never decides alone.

What you need to know

What it does not include yet

DWG needs an engine: ODA File Converter or AutoCAD on the machine that does the job. The PDF, DXF, KMZ, Excel and materials do not.
FATs are sized by pole coverage. The by-homes calculation exists in the factory, but the ERP form does not send the homes yet. In the business case, homes per pole are entered.
With boxes only, the poles are estimated: OpenStreetMap does not have the utility company's poles and they must be verified with the utility company or in the field.
It does not invent utility-company rates or formats: pole rent starts empty and the exportable list uses its own columns, because each division asks for its own format.
As-built: splitters, which FAT hangs from which, fibers and splices are always recalculated; what changes in what is already built is shown with double confirmation. Field capture needs a signal.
Prices are reference values until you load yours, and the real cost is not taken from the warehouse on its own.

Frequently asked questions

What we are usually asked

Do I need AutoCAD to use it?

No. The A1 PDF drawings, the DXF, the KMZ, the Excel and the bill of materials are generated without AutoCAD. DWG output needs ODA File Converter (free) or AutoCAD on the machine that does the job.

Which network standards does it accept?

Any that can be described in a profile: 1:8 × 1:8 cascade, 1:4 × 1:16 or another, FAT sizes, cables and TIA-598 buffer colors, slack, losses and optical budget, maximum span and hardware rules. A profile inherits from another and changes only what differs.

Does it work without the utility company's drawing?

Yes. It starts from an Excel, a CSV, a KMZ or a DWG of poles. The utility-company drawing is optional: if you have it, the design is mounted on a copy of it, and if it is not georeferenced, the factory aligns it by comparing pole numbers.

How long does it take to design a zone?

The demo zone, with 89 poles, was designed in 5.5 seconds without drawings and in 36.9 seconds with the A1 PDF drawings, on a laptop. DWG output adds the time of the engine that converts it.

Who reviews the design?

The design is validated against your standard and was tested against real zones made by hand, but it is still an engineering proposal: the person responsible for the build reviews and signs it. Every drawing carries the note to verify details on site.

Are the bill of materials prices mine?

The profile comes with reference prices (for example, a $2,500 closure, an $850 8-port box and fiber at $19 and $14 per meter) that you can edit. In the ERP each material is matched to an item in your warehouse and takes your purchase price, your average cost or your price.

What if the build differs in the field?

The crew marks it from the phone. The marks become an "as-built" revision, are compared against the plant and are reconciled with a preview, blocks and undo, so the drawing and the ISP plant say the same thing as what is built.

Is it included in a plan?

Yes. FiberBuild is included in the Enterprise plan of the ISP CRM, at USD 120 per month, along with TR-069, inventories, WhatsApp, Telegram and AI.

Let the next zone come out in minutes, not weeks

FiberBuild comes included in the Enterprise plan of the ISP CRM. Send us the Excel or KMZ of one of your zones and we will return it designed, with your conventions.

Fisher Networks ventas@fishernetworks.net 442 138 8102

See the Enterprise plan Request a demo on WhatsApp

About the images and the data

All images and figures come from a fictional demo zone, "Colonia Demo", laid out over real streets of Celaya, Guanajuato, with 89 estimated poles that do not correspond to real poles. The drawings, the KMZ, the Excel and the bill of materials are real outputs of the design factory; the map is the KMZ drawn over OpenStreetMap. Prices are the profile's reference prices. No data belongs to a customer.

Costs and times depend on your standard, your prices and the machine doing the job; the 36.9-second measurement is for the demo zone on a laptop, with PDF drawings and without DWG.

From an Excel of poles to the construction package, in under a minute.