dpCom > Menu reference > Reports

The trace report can be compared to tools such as the connection report, layout reports, duct carving plan and show customer trace data, all of which visualize the results of fiber/wire-level or pipe-level tracing in different ways.

The trace report is a compilation of information that forms the basis of the connection report, but shows the extent horizontally and includes all fibers/wires or pipes that are in the starting object depending on which of the trace reports you select.

The trace may show different columns depending on the object you start from. For example, if you start from a switch, the trace can only go in one direction. The same applies to an ODF without patches or if you have set the trace to stop at the ODF. If instead you were to start from, for example, a cable, the tracing goes in two directions. Since the object you start from becomes a center point, the paths will spread out to both the right and left. A column can also represent different object types for the different rows, and in that case the current object type is entered in a separate adjacent field.

Trace report - submenus

For the submenus in the table below you can follow the steps in section Create a trace report.

Submenu
Trace report for fiber
Trace report for thread/carrier
Trace report for ODF
Trace report for active equipment (fiber side)
Trace report for active equipment (copper side)
Trace report for active equipment (radio side)
Trace report for passive equipment
Trace report for switch
Trace report for fiber splitter
Trace report for copper splitter
Trace report for distribution socket
Trace report for coax connector
Trace report for fiber joint
Trace report for copper joint
Trace report for duct
Trace report for patch fiber cable
Trace report for copper patch wire

For the submenus in the table below, see the Extra info column for additional information.

Submenu

Extra info

Trace report for services

This report assumes that the service has one or more linked connections. If there are more than one connection the report will try to present it as if the connections are parallel, for example as a fibre pair. If the connections are not parallel, the report Trace report for connections below may be a better choice.

The service object for the report can be found in several ways, this is one example:

1.Right-click on a Distribution node in the map an select Show > Show customer trace data. The Show customer trace data dialog opens.

2.Right-click on a column for service ID for a service with services below, and select Create report > Trace report for services. The Create trace report dialog opens.

You can also:

1.Right-click on a column for service ID for a service with services below, and select Object > Place component for object.

2.Place the component in the map.

3.Continue with the steps in section Create a trace report.

Trace report for services below

This report assumes that there are one or more services linked as services below to the selected service. If the selected service has a connection, that service will also be presented in the trace, otherwise only the underlying children are shown. The typical use case for this report is a capacity service that stretch from one node to another via several nodes with active equipment. The report will present this as one stretch. Another use case is a FTTH oriented design where the start service represents the uplink of an access switch that has underlying services connecting the customer nodes. In that case the underlying services are presented more as parallel tracks.

The service object for the report can be found in several ways, this is one example:

1.Right-click on a Distribution node in the map an select Show > Show customer trace data. The Show customer trace data dialog opens.

2.Right-click on a column for service ID for a service with services below, and select Create report > Trace report for services below. The Create trace report dialog opens.

You can also:

1.Right-click on a column for service ID for a service with services below, and select Object > Place component for object.

2.Place the component in the map.

3.Continue with the steps in section Create a trace report.

Trace report for connections below

This report assumes that connections linked to the service are physically running as a sequence rather than parallel. If the connections are parallel, the report Trace report for service may be a better choice.

The service object for the report can be found in several ways, this is one example:

1.Right-click on a Distribution node in the map an select Show > Show customer trace data. The Show customer trace data dialog opens.

2.Right-click on a column for service ID for a service with connections below, and select Create report > Trace report for connections below. The Create trace report dialog opens.

You can also:

1.Right-click on a column for service ID for a service with services below, and select Object > Place component for object.

2.Place the component in the map.

3.Continue with the steps in section Create a trace report.

Trace report for service hierarchy above

This report assumes that there are services (with connections) linked as services above to the start service object. The service above may in itself have service above in several steps. Only one path through the parent hierarchy is presented and you will be presented with all available hierarchy paths. The typical use case for this report is a FTTH oriented design with uplink services linked as services above. The report is started from a service in the lower part of the hierarchy and shows all its uplink services.

The service object for the report can be found in several ways, this is one example:

1.Right-click on a Distribution node in the map an select Show > Show customer trace data. The Show customer trace data dialog opens.

2.Right-click on a column for service ID for a service with services above, and select Show/change attribute. The attribute form opens.

3.Select the Service hierarchy tab.

4.In section Services below, right-click on a service ID and select Create report > Trace report for service hierarchy above.

5.Select a service hierarchy from the drop-down menu and press OK. The Create trace report dialog opens.

You can also:

1.Right-click on a column for service ID for a service with services below, and select Object > Place component for object.

2.Place the component in the map.

3.Continue with the steps in section Create a trace report.

Vertical trace report

See section Vertical trace report below for more information.

The service object for the report can be found in several ways, this is one example:

1.Right-click on a Service in the map and select Show/change attribute. The attribute form opens.

2.Select the Related data tab.

3.In the tree, expand a Connection.

4.Right-click on a connector and select Create report > Vertical trace report. The Create trace report dialog opens.

5.Check the desired checkbox options and press OK.

When your selected object has a graphical component in the map, you can also:

1.In the menu bar, select Settings > Preferences.... The Preferences dialog opens.

2.Select the dpCom tab.

3.Check the Show contacts in auto views checkbox.

4.Press OK.

5.Show node content for a node with an ODF.

6.In the menu bar, select Reports > Trace report > Vertical trace report.

7.Select a connector symbol in the ODF.

8.Check the desired checkbox options and press OK.

If the ODF connectors does not show press Refresh .

Vertical trace report for services below

This report assumes that there are one or more services linked as services below to the selected service. If the selected service has a connection, that service will also be presented in the trace, otherwise only the underlying children are shown. The typical use case for this report is a capacity service that stretch from one node to another via several nodes with active equipment. Another use case is a FTTH oriented design where the start service represents the uplink of an access switch that has underlying services connecting the customer nodes.

The report will show each linked service in a separate tab.

The service object for the report can be found in several ways, this is one example:

1.Right-click on a Distribution node in the map an select Show > Show customer trace data. The Show customer trace data dialog opens.

2.Right-click on a column for service ID for a service with services below, and select Create report > Vertical trace report for services below. The Create trace report dialog opens.

3.Check the desired checkbox options and press OK.

You can also:

1.Right-click on a column for service ID for a service with services below, and select Object > Place component for object.

2.Place the component in the map.

3.In the menu bar, select Reports > Trace report > Vertical trace report for services below.

4.Select the previously placed service in the map.

5.Check the desired checkbox options and press OK.

Vertical trace report for service hierarchy above

This report assumes that there are services (with connections) linked as services above to the start service object. The service above may in itself have service above in several steps. Only one path through the hierarchy is presented and you will be presented with all available hierarchy paths. The typical use case for this report is a FTTH oriented design with uplink services linked as services above. The report is started from a service in the lower part of the hierarchy and shows all its uplink services.

The report will show each linked service in a separate tab.

The service object for the report can be found in several ways, this is one example:

1.Right-click on a Distribution node in the map an select Show > Show customer trace data. The Show customer trace data dialog opens.

2.Right-click on a column for service ID for a service with services above, and select Show/change attribute. The attribute form opens.

3.Select the Service hierarchy tab.

4.In section Services below, right-click on a service ID and select Create report > Vertical trace report for service hierarchy above.

5.Select a service hierarchy from the drop-down menu and press OK.

6.Check the desired checkbox options and press OK.

You can also:

1.In section Services below, right-click on a service ID and select Object > Place component for object.

2.Place the component in the map.

3.In the menu bar, select Reports > Trace report > Vertical trace report for service hierarchy above.

4.Select the previously placed service in the map.

5.Select a service hierarchy from the drop-down menu and press OK.

6.Check the desired checkbox options and press OK.

Trace fiber connections

1.Right-click on an opto cable and select Show/change attribute. The attribute form opens.

2.Select the Related data tab.

3.In the tree, expand a Fiber.

4.Right-click on a fiber and select Trace fiber connections. The Fiber trace is created.

When your selected object has a graphical component in the map, you can also:

1.In the menu bar, select Reports > Trace report > Trace fiber connections.

2.Select a fiber in the map. The Fiber trace is created.

Hierarchical level

Several object types have an attribute called Hierarchical level. This attribute helps describe the purpose of an object, such as whether it is for connecting a customer node or a primary node.

The names and levels are not predefined, they must be entered by an administrator in the Codelist manager tool.

Various tools in dpCom can use this attribute.

Trace report, can use the hierarchical level to limit the trace results. For example, the option can be set to stop at customer connection cables, omitting the last details of the network. Similarly, the report can be configured to stop at a secondary level, meaning a report starting at the customer node will not follow the network all the way up the hierarchies.