[Equest-users] How to do LPD calculations in eQUEST

Wed Jun 29 04:58:47 PDT 2016

I am not understanding the question. You can input the lighting power as kW or as W/ft2 – the results will be the same. You can input both kW and W/ft2 and the total lighting power will be the sum of the two. Note, in the LV-B report, the lighting power is always reported as LPD (W/ft2) regardless of how you do the input. The Lighting dialog reports the total lighting power as you input:

[cid:image004.png at 01D1D1DC.10604550]

[cid:image005.png at 01D1D1DC.10604550]

[cid:image006.png at 01D1D1DC.10604550]

[cid:image003.png at 01D09C46.E75BA0D0]
Christopher Jones, P.Eng.
Senior Engineer

WSP Canada Inc.
2300 Yonge Street, Suite 2300
Toronto, ON M4P 1E4
T +1 416-644-4226
F +1 416-487-9766
C +1 416-697-0056

www.wspgroup.com<http://www.wspgroup.com/>

From: Equest-users [mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Sharad Kumar via Equest-users
Sent: Wednesday, June 29, 2016 2:56 AM
To: equest-users; equest-users-request at lists.onebuilding.org
Subject: Re: [Equest-users] How to do LPD calculations in eQUEST

Hi Rathna,

Could you please tell me the findings from the following equations.
The thing without doing it in eQUEST 3.65 is that LOCAL("LIGHTING-KW")*1000/LOCAL("AREA") may result in some other things as i know.

Actually i am unable to get the findings.
The things that i am able to interpret is that you will have the LPD ( watts per square feet) from this as per you.

Could you please tell me how without inputting kW one can get the results anyhow. This seems to me to be me miscalculation and mis-interpretation as per me as if you will input kW as power then there is left no means to calculate the LPD as watts per square feet as this is not within the limitations of eQUEST anyhow.

Thanks,
Sharad.Kumar|Engineer.
Green Horizon Consulting LLP.
Gurgaon.
India
.........................................................................................................................................................................................................................

Hi Sharad,

Alternatively, once you enter the lighting power KW, you can just use the user expression : LOCAL("LIGHTING-KW")*1000/LOCAL("AREA"), the LPD will get updated by itself.

Regards,
Rathnashree
.............................................................................................................
.............................................................................................................

You can also use a BDL expression to do the same thing automatically and eliminate a step. For example:

10*(#L("AREA"))

Where “10” is the wattage of the installed lights in the space and “#L(“AREA”)” grabs the area of the space in which the lighting load is being applied.

I hope this helps.

Sincerely,
incerely,

[Image removed by sender. ARCH | NEXUS]<http://www.archnexus.com/>

DAVID W. GRIFFIN II

BEMP
ENERGY ANALYST

2505 E Parleys Way
Salt Lake City, UT 84109

Office 801.924.5028

archnexus.com<http://www.archnexus.com/>

[Image removed by sender. Twitter]<https://twitter.com/arch_nexus>[Image removed by sender. Facebook]<https://www.facebook.com/pages/Architectural-Nexus/179588705397563?ref=ts&fref=ts>[Image removed by sender. Youtube]<https://www.youtube.com/channel/UCYRPWKF-yp-AUiI8ia2XfKw?feature=mhee>[Image removed by sender. LinkedIn]<https://www.linkedin.com/company/architectural-nexus>

[Note about the above e-mail]:

Thanks Griffin, but the above message can help only when the lighting load is 10 watts for one fixture but my post has been in general like  any lighting power calculations can be done by my way.
Your way is to help with one lighting load but as per my e-mail the lighting fixtures and their number can help to do the calculations.
Also one thing is missing that the window dialogue (as shown in my snap-shots) has both lighting load as watts per square feet and kW which can be input as one at one time.

Thanks,
Sharad.Kumar|Engineer.
Green Horizon Consulting LLP.
Gurgaon.
India

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20160629/932bf1fd/attachment-0005.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6574 bytes
Desc: image001.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20160629/932bf1fd/attachment-0020.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 67946 bytes
Desc: image004.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20160629/932bf1fd/attachment-0021.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 68260 bytes
Desc: image005.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20160629/932bf1fd/attachment-0022.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 72953 bytes
Desc: image006.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20160629/932bf1fd/attachment-0023.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.jpg
Type: image/jpeg
Size: 429 bytes
Desc: image007.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20160629/932bf1fd/attachment-0010.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.jpg
Type: image/jpeg
Size: 341 bytes
Desc: image008.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20160629/932bf1fd/attachment-0011.jpg>