Re: [EnergyPlus_Support] Re: Quick path to learn HVAC detailed modeling approach, is there an

I have a user interface that I developed that does these things, plus others.

The interface lives entirely in SketchUp. I use SketchUp to create my building geometry (it is faster than OpenStudio). I can import Schedules and other EnergyPlus idf objects that have no obvious graphical representation. Unlike the idf editor, I can change the name of a schedule (or any other referenced object), and it updates everywhere.

As far as HVAC is concerned, I can draw my HVAC system as a one-line drawing. "Composite" components, such as a ZoneHVAC:FanCoil, which requires a fan, a heating coil and a cooling coil, automatically know what components are required and create the proper node connections for each object. If more than one object is available (such as Coil:Heating:Gas or Coil:Heating:Water), the user can select which type to use. If I have fan coils in ten zones, I can create one fancoil in my interface and then apply it to each zone. If I need to change one of the input parameters of the fancoil (or one of the "child" objects), I can change that input either for all applied zones, or just for the zones selected.

The program generally knows what nodes need to be added to an OutdoorAir:Nodelist, and when certain node fields should be filled in. All nodes and objects are given intelligent names. For example, exporting the idf for a ZoneHVAC:TerminalUnit:VariableRefrigerantFlow assigned to one zone yeilds... I'll put it at the end of the message, because it is long...

AirLoopHVAC: If I need one VAV system per floor in my building, I can create one in the graphical interface, and then select "replicate one per floor." The program figures out what zones are assigned to the airloop terminal boxes and creates one AirLoopHVAC system (and all components), for each floor.

I can also create multiple energy efficiency measures within the model. With the EEMs, I can change any input that could be changed with the idf "Parametric" objects.

Lastly, I can have more than one HVAC system in the model. This means that in the same model, I have have my proposed and baseline HVAC systems. I simply select which one I want to export to idf along with the geometry, schedules, materials, etc.

I started creating this when openstudio was still a buggy SketchUp geometry plug-in, DesignBuilder was expensive and clumsy and Simergy and N+++ were whispered rumors. I have thought at times of sharing the software, but I am not sure what that would look like. I have spent too much time and effort to give it away, but once this discussion started, I couldn't not share.

Thanks,

Karen

**********************************IDF TEXT FOR ZoneHVAC:TerminalUnit:VariableRefrigerantFlow**********************************

ZoneHVAC:TerminalUnit:VariableRefrigerantFlow,

2 07 Res VRV, !- Name

Always On, !- Terminal Unit Availability schedule

2 07 Res VRV Terminal Unit Air Inlet Node Name, !- Terminal Unit Air Inlet Node

2 07 Res VRV Terminal Unit Air Outlet Node Name, !- Terminal Unit Air Outlet Node

autosize, !- Supply Air Flow Rate During Cooling Operation

0.0, !- Supply Air Flow Rate When No Cooling is Needed

autosize, !- Supply Air Flow Rate During Heating Operation

0.0, !- Supply Air Flow Rate When No Heating is Needed

0.0, !- Outdoor Air Flow Rate During Cooling Operation

0.0, !- Outdoor Air Flow Rate During Heating Operation

0.0, !- Outdoor Air Flow Rate When No Cooling or Heating is Needed

Always Off, !- Supply Air Fan Operating Mode Schedule Name

BlowThrough, !- Supply Air Fan placement

Fan:OnOff, !- Supply Air Fan Object Type

2 07 Res VRV Fan, !- Supply Air Fan Object Name

OutdoorAir:Mixer, !- Outside Air Mixer Object Type

2 07 Res VRV OA Mixer, !- Outside Air Mixer Object Name

Coil:Cooling:DX:VariableRefrigerantFlow, !- Cooling Coil Object Type

2 07 Res VRV CC, !- Cooling Coil Object Name

Coil:Heating:DX:VariableRefrigerantFlow, !- Heating Coil Object Type

2 07 Res VRV HC, !- Heating Coil Object Name

4.39624853458382, !- Zone Terminal Unit On Parasitic Electric Energy Use

2.93083235638921; !- Zone Terminal Unit Off Parasitic Electric Energy Use

Fan:OnOff,

2 07 Res VRV Fan, !- Name

Always On, !- Availability Schedule Name

0.6, !- Fan Efficiency

124.544478569632, !- Pressure Rise

autosize, !- Maximum Flow Rate

0.8, !- Motor Efficiency

1.0, !- Motor In Airstream Fraction

2 07 Res VRV OA Mixer Air Outlet Node, !- Air Inlet Node Name

2 07 Res VRV Fan Air Outlet Node, !- Air Outlet Node Name

, !- Fan Power Ratio Function of Speed Ratio Curve Name

, !- Fan Efficiency Ratio Function of Speed Ratio Curve Name

General; !- End-Use Subcategory

Coil:Cooling:DX:VariableRefrigerantFlow,

2 07 Res VRV CC, !- Name

Always On, !- Availability Schedule Name

autosize, !- Rated Total Cooling Capacity

autosize, !- Rated Sensible Heat Ratio

autosize, !- Rated Air Flow Rate

VRFTUCoolCapFT, !- Cooling Capacity Ratio Modifier Function of Temperature Curve Name

VRFACCoolCapFFF, !- Cooling Capacity Modifier Curve Function of Flow Fraction Name

2 07 Res VRV Fan Air Outlet Node, !- Coil Air Inlet Node

2 07 Res VRV CC Air Outlet Node; !- Coil Air Outlet Node

Coil:Heating:DX:VariableRefrigerantFlow,

2 07 Res VRV HC, !- Name

Always On, !- Availability Schedule

autosize, !- Rated Total Heating Capacity

autosize, !- Rated Air Flow Rate

2 07 Res VRV CC Air Outlet Node, !- Coil Air Inlet Node

2 07 Res VRV Terminal Unit Air Outlet Node Name, !- Coil Air Outlet Node

VRFTUHeatCapFT, !- Heating Capacity Ratio Modifier Function of Temperature Curve Name

VRFACCoolCapFFF; !- Heating Capacity Modifier Function of Flow Fraction Curve Name

OutdoorAir:Mixer,

2 07 Res VRV OA Mixer, !- Name

2 07 Res VRV OA Mixer Air Outlet Node, !- Mixed Air Node Name

2 07 Res VRV Outdoor Inlet, !- Outdoor Air Stream Node Name

2 07 Res VRV Outdoor Outlet, !- Relief Air Stream Node Name

2 07 Res VRV Terminal Unit Air Inlet Node Name; !- Return Air Stream Node Name

On Dec 9, 2013 11:01 AM, "Jason Glazer" <jglazer@xxxxxxxx> wrote:

Jeremiah,

Lightweight to the developer yet still helpful to the user.
Finding the right user interface that is both is a
challenge. The ideas of "only fit if they should", "include
the other components" and "are directional" seem like a good
start for understanding the user's needs. Can you (or anyone
else) think of any other?

Jason

On 12/7/2013 9:35 PM, Jeremiah Crossett wrote:
>
>
> Jason,
> As I work through node connections in IDF editor I thought
> back to your offer here-
> Yes it would be very useful, it might be drag and drop with
> simple icons and nodes that are directional so that they can
> only fit if they should and automatically include the other
> components. One thing is for sure-- the current system is
> the most difficult part of E+, so a lightweight tool to
> simply it would be really great.
> /
> /
> **
> **
> **
> Jeremiah D. Crossett*| Senior Analyst | Phase Change
> Energy Solutions*
> *
> *
> 120 E. Pritchard St. | Asheboro, NC 27203
> | Mobile 503-688-8951*
> **www.phasechange.com <http://www.phasechange.com/> **
> *
> **
> **
> **
> **
>
>
>
> On Tue, Nov 12, 2013 at 1:30 PM, Jason Glazer
> <jglazer@xxxxxxxx <mailto:jglazer@xxxxxxxx>> wrote:
>
> As a software developer who has been on the EnergyPlus
> development team for many years, I have been thinking about
> what kind of software could be developed to make the process
> of assembling and editing the HVAC systems easier. I know
> for some that a complete icon based graphical system may be
> the perfect answer. Tools like Simergy and DesignBuilder and
> OpenStudio are already heading in that direction and are
> continuing to get better and better. But I keep coming back
> to the idea of a very light weight program that could be
> useful. "Very light weight" meaning a small hobby project
> for me or a small group. Probably with a grid or
> hierarchical list etc., nothing too fancy.
>
> It seems like the mechanics of changing node names and
> adding names of objects to various lists are very easy to
> automate. The problem is how to tackle the problem and be
> useful and at the same relative simple. If anyone has and
> ideas for a light weight but useful program for helping with
> EnergyPlus HVAC, please let me know? Maybe include a mockup
> of the interface.
>
> Thanks
>
> Jason
>
> On 11/12/2013 10:57 AM, Humphrey, Neal wrote:
> >
> >
> > Hisham and others,
> >
> > As others have mentioned, itâ??s key to realize that
> > EnergyPlus was designed with the calculation process in
> > mind, not the user input. Definitely start with a
> template
> > and then start modifying as Jeremiah suggests. Even this,
> > however, is not very straightforward to learn how to do.
> >
> > For me, the most useful thing I did for learning how to
> > modify existing HVAC systems was I took a big flip-chart
> > piece of paper and created a very detailed map of all the
> > HVAC components and their relevant inputs. The SVG
> file is a
> > very simple representation of the system that doesnâ??t
> tell
> > you enough about the multiple objects that need to be
> > modified to edit it.
> >
> > My process was to start somewhere in the loop (at the
> > cooling