[Equest-users] Energy Recovery Wheel on VAV System - zonal exhaust?

Nicholas Caton via Equest-users equest-users at lists.onebuilding.org
Tue Mar 21 11:55:46 PDT 2017


OK pour a fresh cup of coffee everyone…

Some of this is a continuation & update on the thread hooked in from last year, so I’m opting to more comprehensively addressing the issues in lieu of a more focused response.  Apologies for length, but I am hoping a few others find this worthwhile.

Following is a diagram that reflects my present understanding of actual zonal/system air stream relationships in doe2/eQUEST models.  It’s probably still wrong somewhere (and I know the doe2 reference entries contradict in a spot or two) but I believe it’s accurate for the topics under active discussion.  I advise printing this off to sketch on for some of the examples to follow along (a few copies wouldn’t hurt for future reference):
[cid:image012.png at 01D2A21F.4C325AA0]
Bill’s query is really complex and has a few layers I am guessing are easy to miss, so I’m going to deconstruct and build on a few issues in isolation.  I will eventually conclude with some constructive advice (promise!).

Issue #1:  Getting a grip on exfiltration in eQUEST (this is something we really should lock down first)

The specified situation is:
+ 23,000 Supply Air (100% OA)
- 10,000 Zonal Exhaust
- 13,000 Return Air
(Assume no infiltration for the example)

How much exfiltration is happening (I’m providing a hint with the +/- signs)?  Adding these up from the zones’ perspective:  The CFM available for exfiltration occurring in this design scenario is zero.

Let’s presume your mechanical designer wants to design some degree of pressurization with all building openings closed, and so intends 2,300 CFM of exfiltration @ full flows (10% of Supply).  In the previous example we have no supply air available to exfiltrate, so to account for this we must reduce the operating return airflow by that quantity.

Adjusted setup is:
+ 23,000 OA / SA
- 10,000 ZE
- 10,700 RA
(Assuming no infiltration)

The net effects here are

1.       2,300 of the supplied air into the zones exfiltrates from the building due to fan pressurization.

2.       The ERV does not see that exfiltrated air, so you can only recover heat from (at most): 10,700 + 10,000 CFM = 20,700 CFM.

An aside: the doe2 reference entries suggest you can only achieve exfiltration either by RETURN-CAP-RATIO or by specifying duct losses.  You can more simply specify a return CFM less than the supply CFM directly.  Return airflow inputs take precedence over return capacity ratio inputs in any case.

Another sidebar:  About that ERV Summary report…
[cid:image013.png at 01D2A23A.388AD070]

·         The “exhaust” and other air flows reported at the top of the ERV Summary SIM report are regurgitations of the corresponding inputs for “design” ERV airflows.  Those inputs are ONLY used to indirectly determine ERV fan/wheel power (when you don’t tell it the answer more directly with the kW inputs), and they do not reflect actual ERV airstream rates.

·         AFAIK you have to create a custom hourly report including “ERV Outdoor airflow (CFM)” and “ERV Exhaust airflow (CFM)” for the system to observe the behaviors I’m claiming above.  Here are the variables I have noted for generally evaluating system Airflows:
[cid:image011.png at 01D2A178.8CB02FF0]

·         … and here’s what that looks like in an INP file, for a system named “AHU1.”  You can copy/paste this into the last section of your INP and it’ll work so long as you change the second line to name a system actually in your model (you’ll probably want to rename the report block while you’re at it).

"Assess Airflows Block - AHU1" = REPORT-BLOCK
   VARIABLE-TYPE    = "AHU1"
   VARIABLE-LIST    = ( 17, 20, 21, 22, 292, 293, 222 )
   ..
"Exfiltration Report" = HOURLY-REPORT
   REPORT-SCHEDULE  = "Hourly Report Schedule"
   REPORT-BLOCK     = ( "Assess Airflows Block - AHU1" )
   ..

·         The rest of the ERV Summary report is relatively useful / intuitive:

o   The middle of the report is great for quantifying net annual ERV effects (short of a parametric run to isolate the energy impact by end-use breakdown), and also visualizing when & why you may be seeing counter-productive (“excess”) heat recovery and pre-conditioning

o   The very bottom of the report (2nd page) gives a more detailed accounting of how often freezing/condensing conditions are occurring with the ERV equipment, which paints a little more informative picture than associated ATTN messages for when your model is advising you to address that in design.

Issue #2:  “My zonal exhaust shouldn’t get seen by ERV equipment!”

If your zonal EXHAUST-SOURCE  is “Air Handler,” Zonal Exhaust quantities cannot be directed “around” the ERV (that is, pushed directly to the exterior as some related doe2 reference entries suggest).  Zonal exhaust joins the relief airstream and will be seen at the ERV when ERV is included for the system.

If you instead choose either “Infiltration” or “Balanced Infiltration” for EXHAUST-SOURCE, the zonal exhaust stream is totally divorced from the central system & ERV equipment, and goes straight outside.

I totally agree.  A toggle/checkbox next to the zonal EXHAUST-SOURCE would be a really nice feature.  Something like “this exhaust goes straight outside” vs. “this exhaust is seen at parent system energy recovery equipment.”

For clarity: None of the zonal AIRFLOW-TRACKING options prevent Zonal Exhaust from reaching the ERV… but we’re circle back to that issue later.

Solution #2a:  “So what about David’s suggestion?”

David’s advice to turn zonal exhaust into exfiltration (doe2 terms) is a great idea under a few conditions:

1.       I need to choose zonal EXHAUST-SOURCE = “Air Handler”

2.       I can select zonal AIRFLOW-TRACKING = NONE or TRACK-EXHAUST

Fully addressing the “why:”

Returning to the round numbers in the starting example, what happens if we force return to zero (i.e. don’t enter a return airflow and specify RETURN-CAP-RATIO as 0.0?

Recap for those keeping score:
+ 23,000 Supply Air (100% OA)
- 10,000 Zonal Exhaust
0 Return Air (don’t specify a return airflow & specify RETURN-CAP-RATIO = 0.0)
(Still locking out infiltration for the example)

Results:
+ 23,000 Supply
- 10,000 ERV Exhaust
- 13,000  Exfiltration (great! As expected.)

Say you instead wanted 13,000 CFM seen at the ERV and only 10,000 CFM of zonal exhaust to be excluded from ERV.  Simply specify a smaller amount of return:
                + 23,000 Supply Air (100% OA)
                - 10,000 Zonal Exhaust
                + 3,000 Return Air

Results:
+ 23,000 Supply
+ 3,000 Return
- 13,000 ERV Exhaust (10,000 Zonal Exhaust + 3,000 Return Air)
- 10,000  Exfiltration

Notice for each of these cases, the results from the zones’ perspective are a zero sum, so long as we don’t bring infiltration into the party.

Special considerations for this approach:

1.       Return fan energies are no longer easily accounted for with the usual inputs, because the return fan isn’t engaged for exfiltration quantities

a.       A relatively simple solution: add RA fan power to the supply fan’s kW/CFM input

b.       Acknowledging: a little fan heat contribution is shifted around in doing so (from the return air stream to the supply air stream), but in the macro level I expect this is an acceptably minor concession for most projects.

2.       Might not be a problem per se, but Zonal Exhaust fan energy merits a little extra attention:

a.       SV-A reports match your zonal inputs for exhaust CFM quantities (10,000 CFM in the above 2 examples)

b.       Custom hourly reports however go a little bonkers: zonal exhaust bumps up to 23,000 / 20,000 respectively (appears to be a sum of zonal exhaust + exfiltration).

c.       Resulting zonal exhaust power doesn’t shift with these edits in the SV-A reports, but may merit further investigation to confirm zonal exhaust power is accurate if you’re going down this path.
Solution(s) #2b: “… but I gotta have TRACK-SUPPLY or TRACK-BOTH!”

David’s suggestion works until you specify exhaust tracking supply or exhaust/supply tracking each other (“both”).

Either tracking selection results in zonal exhaust that will bump upward (to 23,000 in the prior examples) to match the supply airstream.  This removes all potential at all hours for exfiltration.  This by extension means all exhaust will pass through the ERV equipment.

3 parting thoughts:

1.       Bill’s proposal in his original query isn’t that crazy… (or at least it’s crazy in a good way!):

a.       Assume the conditions of the zonal exhaust airstream and the conditions of the “central” return airstream are effectively the same

b.       Derate the efficiency of the ERV so that it returns an amount of heat transfer commensurate with a reduced ERV exhaust airflow, as you anticipate.

c.       Share those “derate curve” coefficients with your friends on the lists once you’ve worked it into an expression (please!)

2.        [Speculative territory] You might alternatively sidestep the above limitations with zonal exhaust having to hit the ERV by pooling all zones requiring TRACK-SUPPLY or TRACK-BOTH under a separate (linked) system.

a.       Remove ERV inputs in the linked system serving TRACK-SUPPLY / TRACK-BOTH spaces.  I’m calling this the “lab” system.

b.       Retain ERV inputs in the linked system serving all other zones.  I’ll call this the “corridors” system.

c.       Establish an OA-FROM SYSTEM tie – lab system sources OA from corridors system.

d.       Adjust central airflow inputs (Supply / Return) between both systems to appropriate the correct supply/return/exfiltration to each pool of zones (per the above instruction).

e.       Adjust central fan power inputs between both systems to ensure fan energy is not over/under represented

f.        The link will ensure all current/future edits to the associated schedules, controls, unitary efficiencies, etc… remain consistent (hopefully!)
The usual problem with OA-FROM-SYSTEM “DOAS” applications with dummy zones is that you have to jump through extra hoops to ensure heat in the return/relief aistream gets seen at the DOAS… in this case we make that “problem” work for us:  The ‘corridors’ system will only see internal loads from the child spaces.

3.       Consider runaround loops for heat recovery in lab general/fume exhaust airstreams are not an unheard of (if not super-duper efficient in transfer) – you might actually need/want to weight the total effectiveness for more than one ERV system.

Whichever path you choose, you’ll want to continue  using custom hourly outputs to ensure the intended behaviors are modeled.  Draw up your expectations for SYSTEM vs. ZONAL airflow streams under different conditions (before and after ECM measures), and verify the expected behaviors using those hourly outputs.


~Nick

#ERV, #VAV, #exfiltration, #variable-exhaust, #required-reading-before-your-next-laboratory-model

[cid:image001.png at 01D2A177.0C1700E0]
Nick Caton, P.E., BEMP
  Senior Energy Engineer
  Regional Energy Engineering Manager
  Energy and Sustainability Services
  Schneider Electric

D  913.564.6361
M  785.410.3317
F  913.564.6380
E  nicholas.caton at schneider-electric.com<mailto:nicholas.caton at schneider-electric.com>

15200 Santa Fe Trail Drive
Suite 204
Lenexa, KS 66219
United States

[cid:image002.png at 01D2A177.0C1700E0]



From: Equest-users [mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Bishop, Bill via Equest-users
Sent: Friday, March 17, 2017 3:08 PM
To: David Eldridge <DEldridge at grummanbutkus.com<mailto:DEldridge at grummanbutkus.com>>; Nicholas Caton <ncaton at catonenergy.com<mailto:ncaton at catonenergy.com>>; Lapierre, Patrick <plapierre at bpa.ca<mailto:plapierre at bpa.ca>>; Daniel Knapp <danielk at arborus.ca<mailto:danielk at arborus.ca>>; Miles H. Martschink <miles.martschink at rmf.com<mailto:miles.martschink at rmf.com>>; bfountain at greensim.com<mailto:bfountain at greensim.com>
Cc: equest-users at lists.onebuilding.org<mailto:equest-users at lists.onebuilding.org>
Subject: Re: [Equest-users] Energy Recovery Wheel on VAV System - zonal exhaust?

David,
Yes the RETURN-CAP-RATIO limits flow to the ERV, as long as zone exhaust AIRFLOW-TRACKING is not set to TRACK-SUPPLY or TRACK-BOTH. (I just tried modeling it.) If the zone exhaust tracks supply, there is no return to the air handler, and if there is an ERV it sees the total volume of zone exhaust.

The problem with specifying RETURN-CAP-RATIO or a system RETURN-FLOW that is less than the SUPPLY-FLOW is that fan energy for the return fan is only registered for hours when the system supply flow rate exceeds (SUPPLY-FLOW – RETURN-FLOW). For example, my 100% OA system has 23,000 cfm supply and 13,000 cfm return with the rest going to a lab exhaust fan and some exfiltration. There is no return fan energy reported until the hourly supply flow exceeds 10,000 cfm. Interestingly, the ERV fan power penalty associated with the system supply/return fans (when selecting HVAC-SUPPLY/RETURN for ERV-FANS) does not seem to be influenced by the zonal exhaust fan power even though the energy recovered is influenced by zonal exhaust flow.


~Bill

From: David Eldridge [mailto:DEldridge at grummanbutkus.com]
Sent: Friday, March 17, 2017 2:05 PM
To: Bishop, Bill <bbishop at pathfinder-ea.com<mailto:bbishop at pathfinder-ea.com>>; Nicholas Caton <ncaton at catonenergy.com<mailto:ncaton at catonenergy.com>>; Lapierre, Patrick <plapierre at bpa.ca<mailto:plapierre at bpa.ca>>; Daniel Knapp <danielk at arborus.ca<mailto:danielk at arborus.ca>>; Miles H. Martschink <miles.martschink at rmf.com<mailto:miles.martschink at rmf.com>>; bfountain at greensim.com<mailto:bfountain at greensim.com>
Subject: RE: [Equest-users] Energy Recovery Wheel on VAV System - zonal exhaust?

Does Return-cap-ratio limit the flow to the ERV? Since the dictionary excerpt below shows Return-cap-ratio in the context of exfiltration for your approximation Bill, it wouldn’t matter to you if the “modeled airflow” for recovery came from the zones or the central, since it is 100% OA there wouldn’t be any return – you are just looking for some BTU’s.

There should certainly be an easier (more accurate) way to flag zonal exhausts for inclusion or exclusion from the ERV, I’d suggest that to be added to the features list.

David



David S. Eldridge, Jr., P.E., LEED AP BD+C, BEMP, BEAP, HBDP
Grumman/Butkus Associates



From: Equest-users [mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Bishop, Bill via Equest-users
Sent: Friday, March 17, 2017 12:09 PM
To: Nicholas Caton <ncaton at catonenergy.com<mailto:ncaton at catonenergy.com>>; Lapierre, Patrick <plapierre at bpa.ca<mailto:plapierre at bpa.ca>>; Daniel Knapp <danielk at arborus.ca<mailto:danielk at arborus.ca>>; Miles H. Martschink <miles.martschink at rmf.com<mailto:miles.martschink at rmf.com>>; bfountain at greensim.com<mailto:bfountain at greensim.com>
Cc: equest-users at lists.onebuilding.org<mailto:equest-users at lists.onebuilding.org>
Subject: Re: [Equest-users] Energy Recovery Wheel on VAV System - zonal exhaust?

I am modeling a laboratory air handler system with 100% OA, ERV at the air handler and a separate laboratory exhaust fan. I modeled the laboratory exhaust fan as zonal exhaust and thought I would only get energy recovery from the remaining exhaust at the air handler but this is not the case, as described previously below and as I confirmed using a custom hourly report.
How then to model energy recovery only for the central exhaust and not the zonal exhaust?
The one thing that comes to mind is to derate the design ERV effectiveness based on the % exhaust that returns to the ERV. The figure below (from Trane’s Ronnie Moffitt, in the ASHRAE Handbook S26.11) shows the reduction in energy recovery as a function of bypassed exhaust.
~Bill
[cid:image002.jpg at 01D29F1D.191F37F0]

William Bishop, PE, BEMP, BEAP, CEM, LEED AP | Pathfinder Engineers & Architects LLP
Senior Energy Engineer

[cid:image004.jpg at 01D29F1D.191F37F0]  [cid:image006.jpg at 01D29F1D.191F37F0]



134 South Fitzhugh Street                 Rochester, NY 14608

T: (585) 698-1956                        F: (585) 325-6005

bbishop at pathfinder-ea.com<mailto:wbishop at pathfinder-ea.com>             www.pathfinder-ea.com<http://www.pathfinder-ea.com/>

[http://png-5.findicons.com/files/icons/977/rrze/720/globe.png]Carbon Fee and Dividend - simple, effective, and market-based.


From: Nicholas Caton [mailto:ncaton at catonenergy.com]
Sent: Monday, February 01, 2016 2:23 PM
To: Lapierre, Patrick <plapierre at bpa.ca<mailto:plapierre at bpa.ca>>; Daniel Knapp <danielk at arborus.ca<mailto:danielk at arborus.ca>>; Miles H. Martschink <miles.martschink at rmf.com<mailto:miles.martschink at rmf.com>>; bfountain at greensim.com<mailto:bfountain at greensim.com>
Cc: equest-users at lists.onebuilding.org<mailto:equest-users at lists.onebuilding.org>; Bishop, Bill <bbishop at pathfinder-ea.com<mailto:bbishop at pathfinder-ea.com>>
Subject: RE: [Equest-users] Energy Recovery Wheel on VAV System

Count me as VERY happy to be corrected – thank you Patrick!

This certainly opens up some flexibility that I thought we were locked out of for some time.  I’ll be re-evaluating my framework for these airflow relationships moving forward!

~Nick

NICK CATON, P.E.
Owner

Caton Energy Consulting
  306 N Ferrel
  Olathe, KS  66061
  office:  785.410.3317
www.catonenergy.com

From: Lapierre, Patrick [mailto:plapierre at bpa.ca<mailto:plapierre at bpa.ca>]
Sent: Monday, February 01, 2016 1:08 PM
To: Nicholas Caton; Daniel Knapp; Miles H. Martschink; bfountain at greensim.com<mailto:bfountain at greensim.com>
Cc: equest-users at lists.onebuilding.org<mailto:equest-users at lists.onebuilding.org>
Subject: RE: [Equest-users] Energy Recovery Wheel on VAV System

Actually it’s quite confusing within DOE’s help but I think you are wrong Nick. Zonal exhaust does go throught the central heat exchanger.
Below is the extract from DOE’s volume that points this out :

[cid:image009.png at 01D29F1D.191F37F0]

The last sentence clears it out.
« All exhaust other than exfiltration is assumed to flow throught the ERV. This includes both zonal and central exhaust. »



[cid:image010.jpg at 01D29F1D.191F37F0]

Patrick Lapierre_ing.
plapierre at bpa.ca<mailto:plapierre at bpa.ca>


De : Equest-users [mailto:equest-users-bounces at lists.onebuilding.org] De la part de Nicholas Caton
Envoyé : 1 février 2016 13:51
À : Daniel Knapp <danielk at arborus.ca<mailto:danielk at arborus.ca>>; Miles H. Martschink <miles.martschink at rmf.com<mailto:miles.martschink at rmf.com>>; bfountain at greensim.com<mailto:bfountain at greensim.com>
Cc : equest-users at lists.onebuilding.org<mailto:equest-users at lists.onebuilding.org>
Objet : Re: [Equest-users] Energy Recovery Wheel on VAV System

I’m actually wrestling with re-understanding these issues in parallel with you, Miles.

The DOE-2 entry for EXHAUST-FLOW specifies zonal exhaust doesn’t get back to the air handler for exposure to heat recovery equipment at the system level (I wish it were an option):
[cid:image011.png at 01D29F1D.191F37F0]

This diagram illustrates my current understanding/impression of what plays into the exhaust airflow seen for recovery:
[cid:image012.png at 01D29F1D.191F37F0]

This is however the first I’ve heard that zonal exhaust doesn’t actually work into the balance to determine exhaust/relief exposed to energy recovery.  Some parametric tinkering is certainly in order!

My immediate thought is to wonder if the zonal EXHAUST-SOURCE (i.e. air handler vs. infiltration) could be playing into that observation?  Seems to fit logic…

~Nick

NICK CATON, P.E.
Owner

Caton Energy Consulting
  306 N Ferrel
  Olathe, KS  66061
  office:  785.410.3317
www.catonenergy.com



From: Equest-users [mailto:equest-users-bounces at lists.onebuilding.org<mailto:equest-users-bounces at lists.onebuilding.org>] On Behalf Of bfountain at greensim.com<mailto:bfountain at greensim.com>
Sent: Monday, February 01, 2016 11:22 AM
To: Daniel Knapp
Cc: Miles H. Martschink; equest-users at lists.onebuilding.org<mailto:equest-users at lists.onebuilding.org>
Subject: Re: [Equest-users] Energy Recovery Wheel on VAV System



Sadly Daniel, I do not think this is quite correct.  In the current version of eQUEST/DOE2.2, if you add zonal exhaust the total amount of heat recovery does not change.  I agree that it should -- heat recovery should go down as zonal exhaust is increased, but eQUEST does not currently do this.  I was quite surprised when it was pointed out to me.

  A quick parametric test run where zonal exhaust is added will show that the total heat input will not go up when it should and on the ERV report (in the .sim) the amount of recovered heat will not change.



If however, you set the return fan volume lower than the supply fan volume (on the fan -> flow parameters tab), then the heat recovery capacity will be reduced appropriately.




From: Equest-users [mailto:equest-users-bounces at lists.onebuilding.org<mailto:equest-users-bounces at lists.onebuilding.org>] On Behalf Of Daniel Knapp
Sent: Monday, February 01, 2016 10:42 AM
To: Miles H. Martschink
Cc: equest-users at lists.onebuilding.org<mailto:equest-users at lists.onebuilding.org>
Subject: Re: [Equest-users] Energy Recovery Wheel on VAV System

Zone exhaust is presumed to exhaust directly to the outside without going back to the system, i.e. it is assumed that you are specifying a separate zonal exhaust fan that is not connected to the main VAV system. If you remove the zone exhaust, the system level exhaust will be determined by the outdoor air fraction of the supply air. This outdoor air fraction will depend on the demand for outdoor air from the zones. i.e. the outdoor air is specified at the zone level, and determines the outdoor air supply at the system level.

Hope that helps,
Dan

—
Daniel Knapp PhD, P Phys, LEED AP O+M
danielk at arborus.ca<mailto:danielk at arborus.ca>

Energy Efficiency Expert
Arborus Consulting
76 Chamberlain Ave
Ottawa ON K1S 1V9
(613) 234-7178
—
Daniel Knapp PhD, P Phys, LEED AP O+M
danielk at arborus.ca<mailto:danielk at arborus.ca>

Energy Efficiency Expert
Arborus Consulting
76 Chamberlain Ave
Ottawa ON K1S 1V9
(613) 234-7178

On Feb 1, 2016, at 11:28 AM, Miles H. Martschink <miles.martschink at rmf.com<mailto:miles.martschink at rmf.com>> wrote:

Hello All,

I am trying to model an enthalpy energy recovery wheel on a VAV air handler serving multiple zones, and I cannot seem to get any exhaust air to pass through the wheel. I have specified the design exhaust loads at the Zonal Level and I have also setup the wheel control sequence using values that others on this forum have posted:
•        Operation = OA Exhaust DT
o   DT = 5 degree F
•        Operating Mode = OA Heat/Cool
•        Make up Air Temp Cntrl = Mixed Air Reset
•        Capacity Control = Bypass OA
Whenever I run the model I get an error stating, “Energy Recovery ventilator: S1 Sys (VAVS) has an exhaust flow 50% of the supply flow. Performance may be compromised. OA & Exhaust: 7313. 0.” The total sum of all the Zonal Exhaust Loads in 5505 CFM, and none of this is making it to the wheel. Does anyone have any insight as to what I might be doing wrong here? My end goal is to have the wheel modulate the return airflow in order to match the Outside Air CFM demand by the VAV system. Any input is greatly appreciated.

Thanks,

Miles Martschink, Jr
Mechanical Design Engineer
______________________________

RMF Engineering
Reliability. Efficiency. Integrity.

p: 843.971.9639
www.rmf.com<http://www.rmf.com/>
<image005.png><https://www.linkedin.com/company/rmf-engineering-inc.?trk=nav_account_sub_nav_company_admin><image006.png><https://www.facebook.com/pages/RMF-Engineering/193267750706493?ref=hl>



________________________________
This email has been scanned for email related threats and delivered safely by Mimecast.
For more information please visit http://www.mimecast.com<http://www.mimecast.com/>
________________________________
_______________________________________________
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<mailto:EQUEST-USERS-UNSUBSCRIBE at onebuilding.org>


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170321/0d52a1df/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 255 bytes
Desc: image001.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170321/0d52a1df/attachment-0018.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 8477 bytes
Desc: image002.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170321/0d52a1df/attachment-0019.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 7800 bytes
Desc: image003.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170321/0d52a1df/attachment-0008.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 1254 bytes
Desc: image004.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170321/0d52a1df/attachment-0009.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 1326 bytes
Desc: image005.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170321/0d52a1df/attachment-0010.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 2848 bytes
Desc: image006.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170321/0d52a1df/attachment-0020.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 32965 bytes
Desc: image007.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170321/0d52a1df/attachment-0021.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.jpg
Type: image/jpeg
Size: 1728 bytes
Desc: image008.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170321/0d52a1df/attachment-0011.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 120085 bytes
Desc: image009.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170321/0d52a1df/attachment-0022.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 11269 bytes
Desc: image010.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170321/0d52a1df/attachment-0023.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: oledata.mso
Type: application/octet-stream
Size: 7132 bytes
Desc: oledata.mso
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170321/0d52a1df/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.png
Type: image/png
Size: 20538 bytes
Desc: image011.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170321/0d52a1df/attachment-0024.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.png
Type: image/png
Size: 67594 bytes
Desc: image012.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170321/0d52a1df/attachment-0025.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image013.png
Type: image/png
Size: 20835 bytes
Desc: image013.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170321/0d52a1df/attachment-0026.png>


More information about the Equest-users mailing list