Tim Linenbrink
My feedback
15 results found
-
5 votesTim Linenbrink
supported this idea
·
-
2 votesTim Linenbrink
shared this idea
·
-
8 votesTim Linenbrink
supported this idea
·
-
4 votesTim Linenbrink
shared this idea
·
-
118 votes
An error occurred while saving the comment Tim Linenbrink
supported this idea
·
-
27 votesTim Linenbrink
supported this idea
·
-
56 votesTim Linenbrink
supported this idea
·
-
16 votesTim Linenbrink
supported this idea
·
-
45 votesTim Linenbrink
supported this idea
·
-
2 votesTim Linenbrink
shared this idea
·
-
3 votesTim Linenbrink
shared this idea
·
-
12 votes
An error occurred while saving the comment Tim Linenbrink
commented
Yes, the import and export via comma delimited text files. I can get you samples if you like.
An error occurred while saving the comment Tim Linenbrink
commented
I think it would be a tall order to add all of the SKM Power Tools functionality to Design Master My request is not because SKM manipulates schedules better than DM, infact it does not. Many industrial facilities use SKM to maintain the model and analysis their distribution system do they can do arc-flash labeling, damand and harmonic analysis. It would be a benefit to be able to roll the schedules from a design package into an analysis package rather than have to re-key all the loads from every panel schedule.
Tim
Tim Linenbrink
shared this idea
·
-
3 votesTim Linenbrink
supported this idea
·
-
93 votesTim Linenbrink
supported this idea
·
-
29 votesTim Linenbrink
supported this idea
·
The intention of adding a lighting control panel (LCP) type to design master would be to communicate some basic information on the lighting controls to plan reviewers, contractors, etc.
It would not be pragmatic to accommodate all the functionality that can be found in commercial LCPs. Any representation would be very basic, there would be no control associated with the actual lighting. There would be no load calculations for the LCP as those are already in the panel schedule.
It would be convenient if there was a warning on a relay being over loaded but that would not be a deal-killer.
It would be helpful, but not necessary, to have the panel accommodate the nominal number of pole positions commercially available, e.g., 8-poles, 16-poles, etc. Again, not a deal killer.
Functionality it would be necessary to create a new “panel type” with the data elements listed below. The existing database schema accommodates most of these. It be necessary to create a method for associating lighting circuits with the relays in the LCP.
Any “higher level” lighting controls would have to be handled by the user in the associated notes field.
Attributes:
By enlarge the existing DM database schema would support the elements needed to represent the LCP:
In the Panel Table
Attribute DM Table/Field
1) Voltage Rating tblPanel.VOLTS
2) Panel Description tblPanel.sDescription
3) SCCR tbpPanel.AIC
4) NEMA Rating tbPanel.??? ( new field or use NOTE1 or NOTE2)
5) Mounting tlbPanel.MOUNTG
6) Voltage Barrier – Y/N tbPanel.??? ( new field or use NOTE1 or NOTE2)
In the Circuits table:
Attribute DM Table/Field
1) Relay Number tblCircuit.iCirNum
2) Circuit Description tblCircuit.CIR_DESC_1
3) Relay Type tblCircuit.s_CIR_DESC_FIXED_1
(e.g., Normally Closed, Normally Open)
4) Number of Poles tblCircuit.iPoles
(or create a relay type in tblBreaker)
5) Relay Rating tblCircuit.VOLTS
6) Voltage tblCircuit.VOLTS
7) Circuit Controlled tblCircuit.HR_CIR
8) Control Note tblCircuit.??? (new text field possibly) to identify if a circuit is time clock or photocell controlled, has an override switch hours of operation, etc.