The georeferenced addresses and building points that are to be planned are entered in the “Demand Point” feature class. You can find the demand point form under Data model > Planning > Demand Point.
Opening the form
The following options are available for opening the form:
- In the Industry Model Explorer by right-clicking on Feature class > Show form
additionally, for feature classes with geometry,
- by double-clicking on the geometry in the graphic window
- by single-clicking on the geometry in the graphic window and displaying the form by pressing the
button in the Industry Model Explorer
The demand point form consists of a main demand point form and the detailed forms for the Resident Amount and Planning Attribute Value.
Form details
Demand points are given the following attributes by default:
Main form |
|
Attribute / Form entry / Button |
Meaning |
Postcode |
ZIP code |
City |
City |
Street |
Street |
Abbreviation |
Street abbreviation |
House Number |
House number |
Is Included |
Determines whether the demand point will be included in the planning. “No” selected: During the preprocessing, the drop trenches are created, but the point is not included in the planning. |
Floor Count |
Number of floors |
Defines the depth at which the demand point is planned. |
|
Buildings |
Jump button to the building if the demand point was created via the corresponding preprocessing step. |
This is an additional attribute that can be addressed in the planning rules when defining the fiber requirement. |
|
Resulting Demand Point | Jump button to the result: Demand point |
Home point | Jump button to the home points when the demand point was generated via the corresponding preprocessing step. |
Forced Cable Type (Comsof optimizer only) |
A cable type can be set at the connection point, which the Comsof optimizer must use, regardless of the calculated fiber requirement. The cable-type must be created in the Cable Type object class and in the rule set. |
Detailed form for the Resident Amount |
|
Attribute / Form entry / Button |
Meaning |
Amount |
This is where you can find the number of living and business units, schools, hospitals and public institutions. |
Adoption Rate |
The demand quota can be defined here. |
Expected Revenue |
This is where the expected revenues are entered. |
Building |
Display of the FID of the building to which the detailed record belongs |
Demand Point |
Display of the FID of the demand point to which the detailed record belongs |
Home Point |
Display of the FID of the home point to which the detailed record belongs |
Resident Type |
Specification of terminators by Living unit, Business unit, Hospital, School or Public institution |
Detailed form for the Planning Attribute Value If user-defined attributes were imported during the import, these can be found in the planning attribute values. |
|
Attribute / Form entry / Button |
Meaning |
Value |
User-defined attribute value |
Attribute |
User-defined attribute name |
Feature |
FID of the record to which the planning attribute value belongs |
Connection type – Drop variants
- “Homes passed plus (HP+)”: the connection is planned up to the property boundary including the distribution cable (atesio optimizer only)
- “Homes passed plus (HP+) No distribution cable”: the connection is planned up to the property boundary at the microduct layer (atesio optimizer only)
- “Full”: The building is completely connected
- “No Activation”: The costs for the equipment in the building are not counted. Thus, the activation costs do not apply.
- “No Drop”: No drop duct, drop cable or structure is planned at the drop point. (Has no effect if distribution cables go into the building from the network distribution cabinet.) Only counts when the drop area is considered separately (additional network element in the drop point).
- “No Drop Cable”: Only the drop cable is left out. (Has no effect if distribution cables go as far as the house.) Only counts when the drop area is considered separately (additional network element in the drop point).
- “No Distribution”: There is no planning for the trench, ducts or cables of the distribution layer. If the distribution duct is provided in a trench that will nevertheless be excavated for other cables, the duct will be included in these trenches so that the civil-engineering work does not have to be repeated at this point. At higher network layers, the capacity for connecting these points is also provided.
- “No Distribution Cable”: Only the distribution duct is planned. Distribution cables and the elements at the connection layer are not planned.
- “No Primary Distribution”: The entire infrastructure for the distribution and drop layer is filtered out. If all demand points within this feeder cluster (POP/CO cluster) have this value, then the ducts and cables to the distribution point and the distribution point itself are not placed.
- “No Primary Distribution Cable”: The entire infrastructure for the distribution and drop layer is filtered out. If all demand points within this primary distribution cluster have this value, then the cables to the distribution point and the distribution point itself are not placed.
- “No Feeder”: The entire infrastructure for the distribution and drop layer is filtered out. If all demand points within this feeder cluster (POP/CO cluster) have this value, then the ducts and cables to the distribution point and the distribution point itself are not placed.
- “No Feeder Cable”: The entire infrastructure for the distribution and drop layer is filtered out. If all demand points within this feeder cluster (POP/CO cluster) have this value, then the cables to the distribution point and the distribution point itself will not be placed.
- “No Backbone”: The complete infrastructure for the feeder cable, distribution cable and drop layer is filtered out. If all demand points in the backbone cluster have this value, then the cables and ducts to the POP/CO and the POP/CO itself are not placed.
- “No Backbone Cable”: The complete infrastructure for the feeder cable, distribution cable and drop layer is filtered out. If all the demand points for the backbone cluster have this value, then the cables to the POP/CO and the POP/CO itself are not placed.