Product screenshot · A-ND-03 — The Acme — Brooklyn demo design in Williamsburg: underground, in ducts, with a chamber at every closure. Streets and buildings from OpenStreetMap. Demo company.
Architecture
Your architecture. Aerial or underground.
Start from an architecture template, such as a 1:4 split at the cabinet and 1:8 at the closure. The agent designs to its split ratios, drop limits and optical budget, on poles or in ducts, and only for the buildings inside the area you drew. Anything it places, you can move.
Aerial on poles, or underground in ducts and chambers
Only the buildings inside the area you drew
Move a closure, add a cabinet, reroute a cable
Product screenshot · A-ND-01 — The Acme — Queens demo design over Bayside: 912 homes on poles.
Product screenshot · A-ND-06 — The design check on the Acme — Queens demo design.
Checks
Findings named and located.
Before a design goes to review it is checked for closure and cabinet capacity, drop and distribution distances, cables crossing buildings, missing fibre counts, and the optical budget on the worst path from the central office to each closure. A design with a violation is marked invalid, and a failed step stops the run rather than falling back.
Valid, invalid or incomplete
Spans on poles without a licensed application flagged
Every number graded is saved with its source
Bills
Every line priced, or marked unpriced.
The bill of materials, the bill of quantities and the work orders compile from the design. Each line is priced from your rate card. A line with no rate is marked unpriced, with the reason, never a silent zero.
BoM and BoQ as CSV or XLSX
Work orders as CSV, XLSX or a PDF field packet
Cost per home, labour hours by trade, cable metres by tier
Product screenshot · C-DES-04 — The three documents the Acme — Queens demo design compiles to.
Product screenshot · C-DES-06 — Comparing a design version with the live design.
Approval
Nothing goes live until your engineer approves.
Every design run is a version. Compare it with the live design, with what was added, removed or changed on the map, then approve it or ask for changes. Approving merges it into the live design, records who approved it and moves the project to permitting.
Added, removed and changed, counted on the map
The approver recorded on the design
The build plan recompiled on approval
Release
Issued for construction, item by item.
Before construction, a project passes a release checklist: design approved, splice handoff current, build plan compiled after the approval, zero violations, no capacity exhausted, permits in place. A red item refuses the release and names itself. Issuing it files a proposal a person accepts.
Six release checks, each named
A red item blocks the release
A person accepts the release
Product screenshot · C-DES-07 — The issued-for-construction checklist on the Engineering desk.
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.
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.