5.4.5 Daylighting - Illuminance Reference Points and Daylighting Control Types

[GoogleCodeExporter]

**What NACM Section(s) are relevant to this issue?

5.4.5 - Reference Position for Illuminance Calculations
5.4.5 - Daylighting Control Type

**Explanation of issue:

The ACM prescribes a method for prioritizing/selecting the two 
available Illuminance Reference Positions (control points)
SPACE level.  However the reference method/target simulation tool 
(Energy Plus/Open Studio) allows only two reference positions per 
THERMAL ZONE.

The ACM does not provide guidance on how to address situations in
which a single thermal zone contains multiple daylit spaces, each 
potentially containing two control points.

In addition, the building descriptor Daylighting Control Type is 
specified at the space level.  Aggregating multiple Daylighting
Control Types from the Space level into one at the Thermal Zone level
presents the same problem.  

**Proposed resolution:

Please provide guidance on how to address situations in which a 
Thermal Zone contains multiple daylit Spaces with regard to 
specifying daylighting control points and control types at the 
Thermal Zone Level.

**Please provide any additional information below.

Perhaps a call to outline these issues and possible solutions is warranted?

Original issue reported on code.google.com by lu...@360-analytics.com on 18 Apr 2013 at 11:57

[GoogleCodeExporter]

I think this item may warrant a discussion.  The simplest thing for the first 
release would be to have the software place a restriction of no more than 1 
daylit space per zone. 

Otherwise we could come up with rules that identify representative Reference 
Points for the PDZ and SDZ.

Original comment by JohnJArent on 22 Apr 2013 at 6:25

• Changed state: Discussion

[GoogleCodeExporter]

REVIEW 130917 - 

Currently working on a proposal to address this issue.  Proposal will be 
available by end of September.

Original comment by lu...@360-analytics.com on 17 Sep 2013 at 11:06

[GoogleCodeExporter]

131125 - Updating status to resolved until final ACM language is received.

Original comment by lu...@360-analytics.com on 25 Nov 2013 at 10:50

• Changed state: Resolved

[GoogleCodeExporter]

Placed final daylighting ACM language based on Lukas' proposal in the Dec 23 
version.

Original comment by JohnJArent on 10 Feb 2014 at 6:55

• Changed state: Fixed

[GoogleCodeExporter]

closing issue

Original comment by lu...@360-analytics.com on 18 May 2014 at 12:36

• Changed state: DoneVerified