FTTH skill

The FTTH (Fiber To The Home) skill turns Nexma into a fiber-network design platform. It was Nexma’s first vertical and is the most mature skill in the catalog.

What it covers

The FTTH skill ships with the entities, relationships, and constraints you’d expect from a production fiber planning tool:

• Entities. OLT, Cabinet, Splitter, Closure, Drop, OpticalNetworkUnit,

Duct, FiberCable, Splice, Strand. Each with typed properties (port count, splitter ratio, fiber count, connector type).

• Relationships. Hierarchical: OLT → Cabinet → Splitter → Drop → ONU. Plus

side-relationships (Cable contains Strands, Splice joins two Strands).

• Constraints. Splitter ratios (1:8, 1:16, 1:32, 1:64), maximum optical loss budget,

minimum bend radius, color-code mappings (TIA-598-D), cascade-depth limits.

• Constants. TIA-598-D fiber color codes (12-fiber and 24-fiber buffer tubes),

standard splitter loss tables, dB budgets for common PON architectures.

• Layer config. Cabinets render as 3D extruded boxes; splitters as colored points

scaled by ratio; cables as thickness-graded lines; drops as fine lines styled per home status.

• Toolbar tools. Generate network, place cabinet, route distribution, validate

budget, export to vendor format.

Typical workflow

1. Scope. Draw a service area on the Globe — usually a neighborhood or a municipal

boundary.

1. Demand. Either bring an addressable-households layer or let Jax derive one from

OSM building footprints.

1. Generate. Ask Jax: “Plan a feeder + distribution network for every household

in this polygon. Use existing pole runs where possible. Splitter ratio 1:32.”

1. Inspect. Click cabinets, inspect splitter chains, hover cables to see fiber

counts.

1. Refine. Move cabinets, adjust ratios, ask Jax to re-optimize.
2. Validate. Run the optical-budget check; surface any over-budget paths.
3. Export. GeoJSON, KML, or vendor formats (e.g. NetAdmin, VETRO, IQGeo) from

Project → Export.

What Jax is good at, in FTTH specifically

• Cabinet placement under a street-network constraint and a maximum-feeder-length

rule.

• Splitter sizing trade-offs (1:32 vs 1:64) for a target take rate.
• Optical-budget validation across a multi-stage cascade.
• Refurbishment moves — “swap this 1:8 for a 1:16 and re-route” — without

breaking downstream constraints.

What it does not do (yet)

• Detailed financial modeling beyond high-level cost estimation.
• As-built reconciliation against legacy GIS (in roadmap).
• Active equipment provisioning workflows (out of scope — handled by NMS systems).

The skill is open: extend it with your own constraints, vendor catalogs, or organization-specific rules. Most production deployments do.