Network Design
Agents draft. Engineers decide.
Choose an area on the map. The Design agent places the cabinets and closures, routes cable to every home and counts every quantity. Then it checks its own work, ready for an engineer to review.
Product capture
A-ND-01
The Lux design engine’s output for Bayside, Queens, in the Acme demo company. Streets and buildings are OpenStreetMap; the pole line and the customers are generated for the demo.
Design
Select an area. Get a buildable design.
Draw a boundary, drop a circle or name a neighbourhood, and confirm the area. The agent picks one of your architecture templates, places closures and cabinets, and routes drops, distribution and feeder along the real street graph. It counts homes, not just buildings.
Real streets and buildings, not a template
Centralised, distributed, home-run, tap and indexing architectures
Your ducts and pole spans used before any new trench
Aerial on the pole line, or underground in ducts and chambers
Product capture
02-tasks
What the agent does, in order: read the streets, place the closures, route the cables, check every optical path.
Product capture
A-ND-04
Cost
Every quantity counted before you dig.
The bill of materials, the bill of quantities and the work orders compile from the design itself. Move a closure and they recompile. Prices come from your rate card, and every number traces back to where it came from.
BoM and BoQ with materials, labour and civil split out
Priced from your project or company rate card
Work orders for the crews as CSV, Excel or a PDF field packet
Validation
Checked before it reaches you.
Before a design reaches an engineer, Lux checks it against the physical rules of the plant and the optical budget of every subscriber path. Every cable must sit in its duct, path or span. Split ratios and distances stay under their ceilings. Anything that fails is named and located.
Every cable checked against its duct, path or span
Worst-case loss computed for every subscriber path
Warnings shown alongside the result, never hidden
Product capture
A-ND-06
Product capture
C-DES-03
Control
Your engineers stay in control.
The agent drafts; an engineer approves. Draft the design on a version and it sits beside the live network until someone approves it. Approving merges it and moves the project on to permitting, and approval is always a recorded click, never read from chat. You also choose how often the agent stops to ask: before every write, or only at the end.
Draft on a version, merge on an engineer’s approval
Ask before every write, or review the draft at the end
A full history of who changed what, agent or person
Deliverables
One design. Every document.
The project’s deliverables sit in one place: the design, splice and riser diagrams, the bills, the work orders and the permit packages. Each is built from the same record, so when the design changes, the documents follow.
DXF for CAD, with proposed and existing layers
GeoJSON, Shapefile, KML, GPX or CSV for GIS
BoM and BoQ as CSV or Excel
Product capture
C-DES-04
Scope
Everything a build needs, from one design.
Routes and equipment on the real street graph
Closures, splitters and cabinets sized to your split ratios
Existing ducts and pole spans reused first
Pole loading verdicts and make-ready fixes on aerial routes
Physical and optical checks on every design
BoM and BoQ priced from your rate card
Work orders ready for the crews
Versions you can compare and keep
DXF, GeoJSON, Shapefile and KML exports
The agent draws the network. Your engineers decide what gets built.
Bring a service area.
In a demo we run the Design agent on an area you choose, then walk your engineers through the checks, the bill and the approval.