After opening the planning settings, you will find the “File” and “Edit” menu entries in the form header.
File
This is where you can import and export planning settings, restore the default settings with certain options or delete all settings.
Edit
Under "Edit", existing path types in the project are loaded.
- Load trench types from data > all trench types will be reloaded, existing entries will be overwritten.
- Load missing trench types from data > only new entries in the trench types will be loaded to the existing entries.
Note
Trench types can also be added manually in the Components tab.
The planning settings for the atesio optimizer are grouped thematically in 3 tabs.
General/Global tab
| Subject | Description |
| Optimization mode | Selection of planning depth: FTTH or FTTB |
|
Trench intersection mode
|
Splits paths at intersections or point of contact in the preprocessing step.
Recommended settings: Split trenches |
|
Connection trench distance |
Specifies the maximum distance (length) in meters for drop trenches in the preprocessing step. |
|
Split trenches |
Splits trenches to segments before transfer to the optimizer. The shorter the subsections, the more possible distribution locations are available to the optimizer. A fixed length of the subsections can be entered or a halving, quartering or octupling of the respective segments can be required. Trenches are only split if the resulting segments are at least 1 m long. House entries, crossings and transitions are generally not split. |
|
Duct transitions spacing |
Distance between the individual transition trenches between trench and duct. 0 = No transition |
|
Transition length |
Maximum length of the transition trenches between trench and duct |
|
Optimize geometry |
Optimizes the geometry of the ducts during preprocessing. The geometry of the base points is adapted to the spatial tolerance set for the project; base points located too close to one another are deleted. |
|
Import unused infrastructure (affects ducts and cables) |
False: Infrastructure not used by the optimization is excluded in the result True: Infrastructure not used by the optimization is included in the result and given the status “Spare” |
General/Trench network generation tab
| Subject | Description |
|
Trail network type
|
Sidewalks: Depending on the individual street configuration (under Components), a possible trench is created on one or both sidewalks for each street center line. Center: the possible trenches are created on the street center line |
| Drop Costs per meter | Costs per meter of drop trench |
| Railway crossing cost | One time cost at railroad crossings |
| Adjust trench distance | True: Activates the mode for different trench widths |
General/Optimization tab
| Subject | Description |
| Demand point blow in distance | Length between demand point and layer point at distribution layer |
| Distribution point blow in distance | Maximum length between layer point at distribution layer and layer point at feeder layer |
| Distribution point setup cost | Costs for layer point at the distribution layer |
| Splicing cost | Costs per splice |
| Distribution topology (distribution layer) | Options are: Direct or Shared Cable |
| Feeder topology (feeder layer) | Options are: Direct or Shared Cable |