Electrical Design Software | Elecdes Design Suite by Scada Systems Ltd

Cable Schedule Report

General

Plant cable optimisation requires a cable list to analyse. The cable list is generated when you compile the connection reports for your Elecdes project inside EBASE. If you are constructing only a Paneldes model and have no schematic drawings included in your Elecdes project, EBASE will produce you a blank report into which you can manually enter the cables.

The cable schedule must reside in your Elecdes project directory. The file must be named "YourElecdesProjectCABSCH.DBF". For example, if your Elecdes project is called "ProjectOne", then the cable schedule database will be named "ProjectOneCabsch.dbf ".

Viewing / Editing

How to view wire and cable reports

Field usage in the Cable Schedule

Most of the fields in cable schedule can be regarded as INPUT data (cablefactor etc.). Only the compulsory fields are required to correctly optimise the cable routes. There are fields in the file that are only used for materials data (e.g. TYPE).

A number of fields in this file are designated as the report fields for the Paneldes routing function. i.e. They will contain REPORT data after route optimisation has occurred (e.g. cable length and route).

There are also optional fields in which data may be entered to provide more information to improve the routing optimisation results.

Compulsory fields

Whether you use the cable schedule generated by Elecdes, or manually perform the data entry, you must ensure the following fields have correct data:

FieldDescription
CABLENAMEThe unique name of the cable.
PNLNO_APanel tagname for one end of the cable.
DEV_TBLK_ADevice tagname for one end of the cable.
PNLNO_BPanel tagname for the other end of the cable.
DEV_TBLK_BDevice tagname for the other end of the cable.

Optional fields

Data entered into the following fields will provide more information to improve the routing optimisation results.

POWER This field should contain a number representing the power compatibility of the cable. You can define the compatibility for each number 0...32768. Sensitivity to electromagnetic interference is the usual use for the power number. Paneldes will only route cables through raceway with the appropriate power number.
CABLFACTR

Filling factor for this cable. This may represent any cable attribute your local regulations require e.g. weight, cross sectional area. The raceway fill percentage is calculated as follows:

Summation of the cablefactor for all cables contained in a raceway / The raceway's cablefactor.

This field should contain a number e.g. 3.6, 0.1, 2.400.

You can also use the NEC code to calculate raceway fill for trays and conduits.

MINBNDRAD Bend radius for this cable. If the chosen route has any segments bending at a smaller radius than this value, a warning will appear in the details field.
DRUMSIZE The length of conductor available on a single drum.

Report fields

After routing, route data will be placed in the existing cables list database (Cable Schedule). Paneldes will only add or overwrite data in existing records of the file, in the following fields:

FieldDescription
EST_LEN Optimal cable length using the chosen route.
ROUTE

Tagname of the Paneldes route for this conductor, chosen by the route optimisation function (if not filled in by route optimise function, then no route was found on your model, for this conductor).

The details of the chosen route can be found in the Route List.

DETAILS

Information about the route: alternate route used, route was overfilled, route bends too tightly. If the optimisation function placed your cable in a route other than the shortest found route OR in an overfilled, small bend radius route, you will need to alter your model.

See Route optimisation errors and warnings.

WARNINGS

Warnings about problems with finding a valid route.

See Route optimisation errors and warnings.

See also

Cable report database in more detail.

How to tune your model for wire and cable routing

Routing functions description

Route optimisation reports

Route optimisation errors and warnings