Hi Rob,

Hoping for that some other users will also find this feature useful, I strike back again with this functionality requested during ISE2020.

The purpose of this Connection Schedule is to have a report to verify on site, device per device (Product), if all the cables are physically labelled and connected as designed in SD7.

Here is what I have in mind:

An export functionality to generate a spreadsheet that contains all the Ports of all the Products in the project.
Thus there is a line for each Port even if there isn't a cable connected to this Port.

Each line contains:
All Attributes of the Product, Port label and the drawing where the Product is placed.
All Attributes of the Cable.
All Attributes of the Feathers.
An additional field/column "Connected Label" with the content of the Cable Label actually connected (Start Label or End Label) to the Port.
An additional field/column "Direction" with a flag indicating the direction of the drawn cable. Could be like "->" if it's the Start Label that is connected or "<-" if it's the End Label that is connected.
All the Attributes and the Port of the Product where the other end of the cable is connected to. (Maybe the tricky part for you)
 
Unlike the Cable Schedule, the first line with field/column headers should have a unique name (e.g. Product-Description, Cable-Description, OtherEndProduct-Description). By the way if this could be applied to Cable Schedule...

Thank You,
Hughes

Hi Hughes,

Thanks for your post.  We can see value in such a report which could simply be described as "1 row per connected port" and I just have 2 questions:

1. What is the purpose/value of showing unconnected ports?  Architecturally this would, today, be the biggest problem so we'd like to understand if showing all unconnected ports (and there could be a lot) is of critical or real value, or whether it's enough simply to show the ports that are connected.
2. As the last requirement you state "All the Attributes and the Port of the Product where the other end of the cable is connected to."  Given that this effectively turns the connection schedule into the Cable Schedule (just with twice as many rows) is this a critical requirement?  If the purpose of the Connection Schedule report is to check connected ports on-site, the 'other end' data seems surplus to requirements and is anyway found on the Cable Schedule today.  It's not hard to do, it just seems like overkill.

We look forward to your response.

Kind regards,
Rob Robinson
Stardraw.com