Adjusting the export scheme

The export schema consists of designation and conversion schemes and can be customized by you as the user.

In particular, you have the option of defining the naming of trenches, ducts, cables, layer points and structures, of specifying the type assignments of trenches, connectors and trays, and of defining the rules for splicing in the layer points. 

Adjustment of the naming and conversion schemes

You have the option of adjusting the naming and conversion schemes to your needs.

The adjustments are saved in the target file with NET Engineering structure. In practical work, this means that you can create different naming and conversion schemes and save them in the appropriate NET Engineering templates.

Start the settings dialog for editing the conversion rules by clicking on the “Create detailed planning” button.

mceclip0.png

The source and target documents are displayed.

The appropriate scheme is selected under “Adjustment”. Export schemes customized for the customer are also displayed and can be selected here. 

mceclip19.png

You have the option of saving defined export schemes and loading them in an empty template.

mceclip20.png

By default, a “General naming scheme” and a “General conversion scheme” are available.

General naming scheme > naming of trenches, ducts, cables, structures and layer points, as well as assignment of connector and tray types as well as cluster types.

General conversion scheme > like naming, plus definition of a splicing scheme.

Clicking on the “Settings” button opens the dialog for editing the export scheme.

Settings for the export—basics

The export scheme basically works with placeholders that can be combined with fixed values.

Possible placeholders are offered after entering a curly brace: {. A click on the placeholder opens a tool tip with more information on the placeholder; double-clicking on the corresponding value selects this placeholder and adds a closing bracket: }.

mceclip18.png

The placeholders vary depending the feature class and are explained below.

Settings for the export—layer point

Layer points are to be understood as the FO points of the corresponding network layer.

mceclip17.png

Building drop > Closure in front of building

Other layer point > Junction closure

Building point > FO terminator in the building

Additional device > each additional closure/terminator in a layer point

Placeholders

Explanation

{AGG_ID}

This is the assignment ID of the corresponding point.

{UPSTREAM_ID}

This is a combination of the assignment IDs of all thehigher-layer layer points. The first number is the assignment ID of the root layer point. The last assignment ID is that of the layer point immediately above. The IDs are separated by periods.

{GLOBAL_SEQ}

This is a global counter that is set across all network layers. 

{LAYER_SEQ}

This is a counter that is set for all layer points of the respective network layer.

{STREET}

This placeholder is replaced by the address of the layer point (input).

{HOUSE_NR}

           

This placeholder is replaced by the house number of the layer point (input). 

{CITY}

 

This placeholder is replaced by the city of the layer point (input). 

{POSTCODE}

This placeholder is replaced by the ZIP code of the layer point. 

{UPSTREAM_SEQ}

Sequential number for all layer points of the same parent layer point. 

{ID}

 

This is a combination of the assignment ID of the higher-layer layer point followed by the assignment ID of this layer point.

All IDs are displayed separated by periods.

 

Settings for the export—cable

mceclip16.png

Other cable > for project-specific customer adjustments

Placeholders

Explanation

{AGG_ID}

 

This placeholder is replaced by the assignment ID of the higher-layer network point. 

{UPSTREAM_ID}

 

This placeholder is replaced by the full {UPSTREAM_ID} of the higher-layer layer point of the cable.

{CITY}

 

This placeholder is replaced by the city of the higher-layer layer point (input). 

{POSTCODE}

This placeholder is replaced by the ZIP code of the higher-layer layer point (input). 

{STREET}

This placeholder is replaced by the street of the higher-layer layer point (input).

{HOUSE_NR}

           

This placeholder is replaced by the house number of the higher-layer layer point (input). 

{DUCT_IDX}

 

This placeholder is replaced by the index of the multi-duct bundle in which the cable is located. If the cable is not located in a duct, the index is set to 0. The duct at the higher-layer network point determines the numbering. 

{MICRODUCT_NR}

 

This placeholder is replaced by the number of the microduct in which the cable was placed. If the cable is in a conventional duct, the index of the conventional duct at the start point is used.  

{TREE_POS}

This placeholder is replaced by the tree-position ID. This is only the case if it is a shared cable that supplies several subordinate layer points. The ID consists of lowercase letters that identify the respective branch.

{ID}

 

This placeholder is replaced by the full ID of the cable. It consists of the upstream ID of the cable followed by the duct index, microduct index and the tree-position ID. 

{TARGET_AGG_ID}

 

This placeholder is replaced by the assignment ID of the subordinate layer point that is connected by the cable. It is the downstream assignment ID.

In the case of a shared cable, TARGET_AGG_ID is the respective end of the shared cable.

{GLOBAL_SEQ}

 

This placeholder is replaced by a global counter that counts across the cables of all network layers.

{LAYER_SEQ}

 

This placeholder is replaced by a counter that applies to all cables of the same network layer.

{LAYER_POINT_SEQ}

 

This placeholder is replaced by a counter for each higher-layer distribution point that is individual for each cable.

{END_SEC}

This is a unique name for each cable that connects a specific device. 

{START-NAME}

This is the device name at the start point of the cable. 

{END-NAME}

This is the device name at the end point of the cable.

{START_AGG_ID}

This is the device assignment ID at the start point of the cable. 

{END_AGG_ID}

This is the device assignment ID at the end point of the cable. In the case of a shared cable, END_AGG_ID is the respective end of the complete cable.

TYPE_NAME

Identifier of the cable 

 

Settings for the export—ducts

Naming of multi-duct bundles or conventional ducts

mceclip14.png

Other duct > for project-specific customer adjustments

Other microduct > for project-specific customer adjustments

Placeholders

Explanation

{AGG_ID}

 

This placeholder is replaced by the assignment ID of the layer point at the start point of the duct.

{UPSTREAM_ID}

 

This placeholder is replaced by the upstream ID of the layer point at the start point of the duct. 

{CITY}

 

This placeholder is replaced by the city of the layer point (input) at the start point of the duct. 

{POSTCODE}

This placeholder is replaced by the ZIP code of the layer point (input) at the start point. 

{STREET}

This placeholder is replaced by the street of the layer point (input) at the start point.

{HOUSE_NR}

           

This placeholder is replaced by the house number of the layer point (input) at the start point. 

{ORIGIN_NAME}

This placeholder is replaced by the name of the structure to which the start layer point of the duct is assigned.

{DUCT_IDX}

 

This indicates the duct index of the duct.

The duct index is a sequential numbering of the ducts at their start points. 

{TARGET_AGG_ID}

 

This placeholder is replaced by the assignment ID of the target layer point.

TREE_POS

This is a value that is incremented when the duct branches.

{GLOBAL_SEQ}

 

This placeholder is replaced by a global counter that counts the ducts of all network layers of the project that use this placeholder. 

{SEGMENT_SEQ}

 

This placeholder is replaced by a counter that counts across all ducts of the corresponding network layer.

{BRANCH_SEGMENT_SEQ}

This placeholder is replaced by a counter that restarts for each branch of a tree.

{ID}

 

This placeholder is a combination of the upstream ID, the assignment ID and the duct index {DUCT_IDX}.

{TYPE_NAME}

This is the identifier of the ducts from the ruleset.

{MICRODUCT_COUNT}

This is the number of microducts of the duct type

[{}]

Placeholders in square brackets [] cause the complete expression to be ignored if the requested value returns an empty string in the curly brackets {}

 

Naming of microducts

mceclip15.png

Other microduct > for project-specific customer adjustments

Placeholders Explanation

{AGG_ID}

 

This placeholder is replaced by the assignment ID of the layer point at the start point of the microduct. 

{UPSTREAM_ID}

 

This placeholder is replaced by the upstream ID of the layer point at the start point of the microduct. 

{DUCT_IDX}

 

This placeholder is replaced by the duct index of the higher-layer duct. 

{MICRODUCT_NR}

 

This placeholder is replaced by the position number of the microduct.

{CABLE_NAME}

 

This placeholder is replaced by the name of the cable in the duct. If there is no cable in the duct or there are several cables with different names, the value will be empty. 

DUCT_NAME

This is the name of the higher-layer duct.  

[{}]

Placeholders in square brackets [] cause the complete expression to be ignored if the requested value returns an empty string in the curly brackets {}

 

Note

When “Shared cable” is set in the optimization rules, using the {DUCT_IDX} or placeholders that use this attribute produce results that do not meet expectations. Due to the “shared cable” rule, the name cannot be mapped generally.

Please contact our support team if you require assistance with this point.

Export details regarding the duct infrastructure

Duct points are automatically created and numbered. 

Duct fittings are created automatically. Duct fittings are named if it is a 1-to-1 connection and the connected ducts have the same name. The name of the duct fitting corresponds to the name of the connected ducts.

The duct-fitting type is formed from the duct types of the connected ducts, separated by a comma. 

Ducts or microducts are interconnected when a cable is in them.

  • Example: A 24-fold composite branches off to a 24-fold composite and a 12-fold composite.

If ducts of the same type run further, an attempt is made to interconnect same-numbered microducts. Furthermore, the microducts of the 24-fold composite that are not needed for the 12-fold composite are also interconnected.

  • Example: A 12-fold composite is divided into two 12-fold composites.

In this case, the longer multi-duct bundle is extended and the other required microducts are connected with fittings.

The export to the detailed planning does not change any network structures and is not able to summarize layer points. It is likewise not possible to assign fiber connections to defined trays.

If you have specific conversion requests, we will create a conversion scheme that is tailored to your requirements.

Settings for the export—clusters

mceclip12.png

Other cluster > for project-specific customer adjustments

Other cluster type > for project-specific customer adjustments

Placeholders Explanation

{AGG_ID}

This is the assignment ID of the cluster.

{UPSTREAM_ID}

 

This is a combination of the assignment IDs of the higher-layer clusters.

The IDs are separated by periods. The last ID is that of the cluster immediately above. 

{CITY}

 

This placeholder is replaced by the city of the associated layer point (input). 

{POSTCODE}

This placeholder is replaced by the ZIP code of the associated layer point (input). 

{STREET}

This placeholder is replaced by the street of the associated layer point (input).

{HOUSE_NR}

           

This placeholder is replaced by the house number of the associated layer point (input). 

{GLOBAL_SEQ}

 

This is a global counter that is set across all network layers. 

{LAYER_SEQ}

This is a counter that is set per network layer. 

{ID}

 

This corresponds to the assignment ID of the higher-layer cluster followed by the assignment ID of this cluster.

All IDs are separated by periods. 

{BB_DEVICE_NAME}

This placeholder is replaced by the name of the linked device at the backbone layer.

{BB_DEVICE}

This placeholder is replaced by the name of the linked device at the same network layer.

Cluster type

This is where you can enter free text. Each cluster on the corresponding network layer is assigned to a cluster type with the name defined in this way. If such a cluster type already exists in the NET Engineering template or the NET Engineering project, it will be used, otherwise it will be newly created.

 

Settings for the export—cabinet, manhole and pole

mceclip11.png

Cabinet and building cabinet > for project-specific customer adjustments

Placeholders Explanation

{AGG_ID}

Assignment ID of the layer point 

{DEVICE_NAME}

Name of the layer point

{UPSTREAM_DEVICE_NAME}

Name of the layer point that is the start point for all ducts connected to the structure. If the ducts do not contain cables, or if the cables start at different layer points, this placeholder will be left empty.

 

Settings for the export—trenches

mceclip10.png

 

Placeholders Explanation
{TYPE_NAME}

The trench type from the trench type from the optimization project is used.

 

Settings for the export—other

Under “Other”, you name the supplied building/address.

mceclip9.png

 

Placeholders Explanation

{CITY}

 

This placeholder is replaced by the city of the building. 

{POSTCODE}

This placeholder is replaced by the ZIP code of the building. 

{STREET}

This placeholder is replaced by the street of the building.

{HOUSE_NR}

           

This placeholder is replaced by the house number of the building. 

 

Settings—splices

This is where you define how and where the fibers in the closures are automatically spliced together when exported to NET.

mceclip8.png

 

Subject Contents

Layer-related sorting

This specifies how the fibers are arranged in the trays of a device.
Setting options Example

From top to bottom

From bottom to top

Not specified

From top to bottom

Feeder-cable splices for shared cables are stored in trays 1 to x. The splices for the drops come into the trays x+1.

Subject Contents

Starting point of the cable

This determines which fiber will be spliced first in the cable.
Setting options Example

Start

End

Start

Fiber 1 is the first to be spliced.

Subject Contents

Use bundles in cables.

This controls the correct use of the fibers for the splices in case of optimization setting “Multi-used cable” and “Assign fiber bundle completely to one subordinate point”.
Setting options Example

None

Feeder layer; primary distribution layer, etc.

For shared cable in the feeder cable, the distribution layer must be set there (even if it concerns the feeder-cable layer, it is not yet logical and will still be changed). The cable type of the shared cable must be defined in the NET template, because the sizes of the bundles are required.

Subject Contents

Spare at the start of the tray

Spare at the end of the tray

Defines the number of splice locations not to be occupied at the start or end of the tray.
Setting options  

The number of spare (and thus not to be used) splice locations is entered as a numerical value.

 
Subject Contents

Start position in tray

Defines the first splicing location to be used in the tray
Setting options  

Start

End

 
Subject Contents

Tray creation

(the outgoing cable is taken into account)

Determines the rule according to which new trays will be created.

Setting options Example

Possible options are “None”, “Network layer”, “Cable” or “Bundle”.

When “Cable” is set, a new tray is created in the distribution cabinet for each drop cable. 
Subject Contents

Cut fibers in the cable trace

(for shared-cable strategy)

Controls how the fibers are handled in a shared-cable strategy.  

The default value is NO.

Setting options Example

YES/NO

NO: only the required fibers/bundles are cut in the distribution point.

YES: All fibers are cut.

Subject Contents

Creating connectors

Rules for creating connectors 

Setting options Example

“None”/“Used fibers”/“All fibers”

Used fibers are active and spare fibers.

Subject Contents

Fiber splices

Splitter splices

Spare-fiber ends

Unused fibers

This is where you define when new trays should be created for the individual connection and storage options.

Tray-filling sequence:

Fiber splices, splitter splices, spare fibers and unused fibers

Setting options  

Do not splice

Place in a separate tray

Share with fiber splices, etc. 

 

 

Subject Contents

Ignore fiber path from the calculation

Selection of whether the fiber path from the comsof fiber-designer calculation should be ignored

Setting options Note

YES/NO 

Should be set to YES

 

Settings—Type assignment for splices

In this tab, the tray and connector types are assigned to the network layers. The tray and connector types defined in the NET Engineering template or in the NET Engineering project are available for selection.

mceclip2.png

Settings for the export—phases

When exporting to NET Engineering, the corresponding status in NET Engineering can be assigned to the elements to be exported depending on the phases (planning depth) and the type of fibers (active and spare).

A prerequisite for this is that the status be defined in the NET Engineering template file.

mceclip0.png

Settings for the export—duct coloring

A duct-sleeve color can be assigned to the multi-duct bundles for export to NET Engineering. To do this, a corresponding color scheme must be defined in the NET Engineering template file and assigned to the corresponding layer in the Duct coloring tab.

mceclip1.png

Settings for the export—user-defined attributes

User-defined attributes are displayed as placeholders in the dialog and can be used as the default placeholders for the name.