[Equest-users] Using C-ACTIVITY-DESC in keyword expressions to assign LPD, equipment loads etc.

wafik adbelkarim abdelkarim.wafik at gmail.com
Mon Jul 28 13:27:25 PDT 2014
Previous message: [Equest-users] Using C-ACTIVITY-DESC in keyword expressions to assign LPD, equipment loads etc.
Next message: [Equest-users] IBPSA NYC Summer Networking Event
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
dear all,
i am very thankful for all of you, thank you indeed.

Wafik


On 29 July 2014 00:11, Melissa Crowe <MCrowe at engsolutions.com> wrote:

> Thanks Bill  and Jeremy McClanathan
>
> This is approach makes my day.
>
> Thanks
>
> Melissa
>
>
>
> *From:* Bishop, Bill [mailto:bbishop at pathfinder-ea.com]
> *Sent:* Monday, July 28, 2014 12:19 PM
> *To:* Greenberg, Ari; Singhal, Harshul; Jeff Haberl; wafik adbelkarim
> *Cc:* equest-users at lists.onebuilding.org
>
> *Subject:* [Equest-users] Using C-ACTIVITY-DESC in keyword expressions to
> assign LPD, equipment loads etc.
>
>
>
> The space description “C-ACTIVITY-DESC”, as shown below, can be referenced
> by keyword expressions.
>
>
>
>
>
> For example, to assign LPD by space type, follow these steps:
>
> 1.      As always, save your project and work from a new copy whenever
> trying something that may be hard or impossible to undo if you pull an
> “oops”.
>
> 2.      Enter consistent space descriptions based on the first four
> characters of the description. (“Office – open” and “Office – Enclosed”
> will both be treated as “offi” because the BDL expression mechanism uses
> four characters.) This is the most time-consuming step.
>
> 3.      Enter the following string as a User-Defined Default Expression
> for LIGHTING-W/AREA:
>
> if(#RV(#L("LIGHTING-SCHEDUL",0))!=0) then unused
>
> else switch(#L("C-ACTIVITY-DESC"))
>
> case "acti": 0.8
>
> case "clas": 1.4
>
> case "offi": 1.0
>
> default: 1.2
>
> endswitch
>
> endif
>
>
>
> (Add or replace case statements, and the default value as applicable to
> your project’s space types. I kept the DOE-2 default expression in the
> example above, and then added the switch statement.)
>
>
>
> This appears in the input file as the following:
>
> SET-DEFAULT FOR SPACE
>
>    LIGHTING-W/AREA  = (
>
> {if(#RV(#L("LIGHTING-SCHEDUL",0))!=0) then unused
>
> else switch(#L("C-ACTIVITY-DESC"))
>
> case "acti": 0.8
>
> case "clas": 1.4
>
> case "offi": 1.0
>
> default: 1.2
>
> endswitch
>
> endif
>
> } )
>
>    ..
>
>
>
> 4.      “Restore default” to the LIGHTING-W/AREA values of each space to
> apply the values from the keyword expression. You can do this manually by
> right-clicking in the field for each space or by deleting lines in the
> input file. I use the NoteTab Light text editor and the regular expression
>
> “^   LIGHTING-W/AREA.*$” to delete all space LPD assignments (being
> careful not to delete the keyword expression just entered above), as
> follows:
>
>
>
> 5.      Repeat these steps as desired for other keywords, such as
> EQUIPMENT-W/AREA, LIGHTING-SCHEDULE, AREA/PERSON etc. Be creative!
>
> 6.      Do a happy dance.
>
>
>
> H/T to Jeremy McClanathan for helping me with this previously.
>
>
>
> Regards,
>
> Bill
>
>
>
> *From:* Greenberg, Ari [mailto:agreenberg at CANNONDESIGN.COM
> <agreenberg at CANNONDESIGN.COM>]
> *Sent:* Monday, July 28, 2014 11:21 AM
> *To:* Bishop, Bill; Singhal, Harshul; Jeff Haberl; wafik adbelkarim
> *Cc:* equest-users at lists.onebuilding.org
> *Subject:* RE: [Equest-users] space renaming
>
>
>
> Hi Bill,
>
>
>
> Using a keyword expression to automatically assign LPD by space type
> sounds like a neat trick that would save some time.  Would you mind sharing
> a little more about how to set this up?
>
>
>
> Thanks,
>
> Ari
>
>
>
> Ari Greenberg, LEED AP BD+C
>
> [image: cid:image001.png at 01CEFD8A.E416B290]
> 100 Cambridge St., Suite 1400
> Boston, Massachusetts 02114
> T 617.517.6224 • M 857.231.1076
> cannondesign.com
>
>
>
> [image: http://thinkbeforeprinting.org/struct/signature-1.gif]
>
>
>
> *From:* Equest-users [mailto:equest-users-bounces at lists.onebuilding.org
> <equest-users-bounces at lists.onebuilding.org>] *On Behalf Of *Bishop, Bill
> *Sent:* Monday, July 28, 2014 11:07 AM
> *To:* Singhal, Harshul; Jeff Haberl; wafik adbelkarim
> *Cc:* equest-users at lists.onebuilding.org
> *Subject:* Re: [Equest-users] space renaming
>
>
>
> You can easily justify over 100 zones on larger projects (say 50,000 ft2
> or more), especially if they are not multi-story with identical floor
> plans. Most of the modeling I do uses Appendix G methodology, where
> lighting power density is assigned by space type. I use a keyword
> expression to assign LPD based on the space type, as assigned via the
> C-ACTIVITY-DESC space keyword. This makes it easy to accurately model LPD
> and to provide documentation for LEED submissions. However, it only works
> if you define zones as the smaller of the HVAC zone or the space type. (You
> can’t combine a classroom, bathroom and storage room into one space even if
> they are effectively one HVAC zone.)
>
>
>
> Regards,
>
> Bill
>
>
>
> *William Bishop, PE, BEMP, BEAP, CEM, LEED AP **|** Pathfinder Engineers
> & Architects LLP*
>
> *Senior Energy Engineer*
>
> [image: ASHRAE Certified logo - greenshot 2]
>
>
>
> 134 South Fitzhugh Street                 Rochester, NY 14608
>
> *T: (585) 698-1956*                        F: (585) 325-6005
>
> bbishop at pathfinder-ea.com <wbishop at pathfinder-ea.com>
> www.pathfinder-ea.com
>
> [image: earth for signature]Sustainability – the forest AND the trees.
>
>
>
>
>
> *From:* Equest-users [mailto:equest-users-bounces at lists.onebuilding.org
> <equest-users-bounces at lists.onebuilding.org>] *On Behalf Of *Singhal,
> Harshul
> *Sent:* Monday, July 28, 2014 10:50 AM
> *To:* Jeff Haberl; wafik adbelkarim
> *Cc:* equest-users at lists.onebuilding.org
> *Subject:* Re: [Equest-users] space renaming
>
>
>
> I also feel 476 spaces are way too much. I can understand that some
> projects have different floor plates & plans and it can end up resulting
> more number of zones. But trust me the more number of zones, more
> complicated it gets. I did one project with almost 150 zones (multi family
> high rise building) and later when I moved to detailed mode  it was a pain
> to make changes for spaces/zones.
>
>
>
> I would suggest rather creating separate zones for *same user type spaces
> facing same façade*, you can combine them as one single zone each floor.
> For corner rooms/spaces, create separate spaces. Try to keep it under 100
> atleast.
>
>
>
> *Harshul Singhal*
> Project Consultant
> Thornton Tomasetti
> 386 Fore Street, Suite 401
> Portland, ME  04101
> *T* 207.245.6060  *F* 207.245.6061
> *D* 207.245.6074
> HSinghal at ThorntonTomasetti.com
> www.ThorntonTomasetti.com
>
> *From:* Equest-users [mailto:equest-users-bounces at lists.onebuilding.org
> <equest-users-bounces at lists.onebuilding.org>] *On Behalf Of *Jeff Haberl
> *Sent:* Monday, July 28, 2014 9:09 AM
> *To:* wafik adbelkarim
> *Cc:* equest-users at lists.onebuilding.org
> *Subject:* Re: [Equest-users] space renaming
>
>
>
> Hello Wafik.
>
>
>
> One question you might ask is why you have 476 spaces in EQUEST?
>
>
>
> Normally, a space is needed only if that zone has a unique load, usage,
> external exposure or HVAC system. Otherwise, it is more common to use a
> simplified zoning. For example, 5 zones are normally used for a rectangular
> building of more than 50 ft in depth. At most, for a multistory building,
> three floors can be used, one for the top floor, one for the middle floors,
> and one for the ground floor.
>
>
>
> Hence, you might consider reducing the number of zones before proceeding.
>
>
>
> Jeff
>
>
>
> Jeff S. Haberl, Ph.D., P.E.inactive, FASHRAE, FIBPSA
>
> Department of Architecture
>
> Texas A&M University
>
> College Station, Texas 77845-3581
>
> Office: 979-845-6507, Lab: 979-845-6065
>
> Fax: 970-862-2457, jhaberl at tamu.edu, www.esl.tamu.edu
>
>
> On Jul 26, 2014, at 3:19 PM, "wafik adbelkarim" <
> abdelkarim.wafik at gmail.com> wrote:
>
> good day every body,
>
>
>
> what  is the fastest and easiest way to rename about 476 space in eQUEST
> model.
>
> instead of going one by one then doing the same for the thermal zones!
> whats the best way to name both  using the wizard without having any
> errors?
>
> is there is any shortcuts?
>
>
>
> regards,
>
> Wafik
>
> _______________________________________________
> Equest-users mailing list
> http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org
> To unsubscribe from this mailing list send  a blank message to
> EQUEST-USERS-UNSUBSCRIBE at ONEBUILDING.ORG
>
>
>
> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
>
>
>
> The information in this email and any attachments may contain
>
>
>
> confidential information that is intended solely for the
>
>
>
> attention and use of the named addressee(s). This message or
>
>
>
> any part thereof must not be disclosed, copied, distributed
>
>
>
> or retained by any person without authorization from the
>
>
>
> addressee. If you are not the intended addressee, please
>
>
>
> notify the sender immediately, and delete this message.
>
>
>
> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20140729/7b4d8ac6/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.jpg
Type: image/jpeg
Size: 2181 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20140729/7b4d8ac6/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.gif
Type: image/gif
Size: 566 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20140729/7b4d8ac6/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 74551 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20140729/7b4d8ac6/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 58955 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20140729/7b4d8ac6/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 2832 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20140729/7b4d8ac6/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 6945 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20140729/7b4d8ac6/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 3066 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20140729/7b4d8ac6/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 65511 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20140729/7b4d8ac6/attachment-0004.png>
Previous message: [Equest-users] Using C-ACTIVITY-DESC in keyword expressions to assign LPD, equipment loads etc.
Next message: [Equest-users] IBPSA NYC Summer Networking Event
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Equest-users mailing list