APPENDINCES

Map symbols

Device database forms

Backup circuit ruleset

When linking a backup circuit, you can use various predetermined rulesets. These environment-specific rulesets can be configured in the Circuit backup rule manager.

Default rulesets that can be activated: 

No same premises

This ruleset specifies whether any telecom premises between the compared circuits can be the same.

Notable features:

• The user receives a notice if there are same telecom premises reserved for both circuits compared (primary and backup circuits) either in the logical or physical reservations.
• It is possible for the user to see conflicting telecom premises on the list. You can see the ID, name, and type of the conflicting item.
• The user has the option to open conflicting components of the circuit reservations on a group display list.
• If no type of telecom premises has been selected, the comparison will be made regardless of the type of the telecom premises.

Distance value:

• The required distance in meters.
• Consider only the types of telecom premises specified in the field.
• If the locations of the reserved telecom premises for comparable circuits are closer than the specified distance value, the user will be notified when saving the circuits.
• Conflicted telecom premises can be viewed on the list. The user has the option to open conflicting components of the circuit reservations on a group list.

Not same devices

This ruleset determines whether any device between the circuits compared can be the same.

Notable features:

• For example, customers device (CPE) or backbone router can be focused on a certain device type and considered this way.
• If no type of telecom premises has been selected, the comparison will be made regardless of the type of the telecom premises.
• The user receives a notice if there are same devices reserved for both circuits compared (primary and backup circuits) either in the logical or physical reservations.
• Information about the conflicted devices can be viewed on a group list. This information includes the ID, name, and type of the device.

Not same connectors

For example, the customer connector device can be the same, but the gate has to be different than the local loop.

Notable features:

• The user receives a notice if there are same connectors reserved for both circuits compared (primary and backup circuits) either in the logical or physical reservations.
• Information about the conflicted connectors can be viewed on a group list. This information includes the ID, name, and type of the device.

Not same cables

The circuits compared cannot have the same cables.

Notable features:

• If no type of cable role has been selected, the comparison will be made regardless of the role type of the cable.
• The user receives a notice if there are same cables reserved for both circuits compared (primary and backup circuits) either in the logical or physical reservations.
• Information about the conflicted devices can be viewed on a group list. This information includes the ID, name, and type of the device.

Distance values:

The backup circuit cannot use the cables of the local loop and the distance between these must be at least n meters.

• Required distance value in meters.
• Consider only the types of cables specified in the field.
• If the locations of the cables for comparable circuits are closer than the given distance value, the user will be notified when saving the circuits.
• Information about the conflicted cables can be viewed on a group list. This information includes the ID, name, and type of the device.
• Conflicting cables on the list (ID, role, and type), and the option to show the conflicting components of an allocated connection on a group list [OK/Show grouplist options]?

Not same threads

Notable features:

• The user receives a notice if there are same threads reserved for both circuits compared (primary and backup circuits) either in the logical or physical reservations.
• Information about the conflicted cables can be viewed on a group list. This information includes the ID, name, and type of the device.