In any construction project, having an early idea of likely material specifications is helpful to avoid last minute shocks and surprises. It’s particularly relevant to rooflights and roof windows, though, because designing a healthy building means not taking quoted U-values at face value.
The composition of roof glazing units – including overall size, relative areas of glazing and frame, and the thermal performance of the materials used – varies, so U-values quoted in a specification should be based on an actual product or a detailed calculation model.
Unfortunately, there exists an element of misunderstanding and potential confusion when specifying U-values for rooflights. A performance specification may not be clear about whether a whole-unit or centre pane value is required, and some manufacturers are not clear about which they are quoting.
Centre pane U-values address the thermal performance of the glass only. They appear lower because the cold bridging effect of the spacer and edge seal are not accounted for. Where two different types of glass are being considered for the same frame, centre pane values are a useful comparison tool.
Conservation projects make good use of centre pane values, because traditional frame designs offer no meaningful thermal performance but the glass needs to be shown to help achieve regulatory compliance.
In most other circumstances U-values should be for the whole unit, including glazing and frame, but too many manufacturers still rely on quoting centre pane U-values.
Specifiers can find themselves misled if two similar products are declared in different ways and a centre pane value is mistaken as a better performing product.
Explaining their performance claims and being able to back them up is an important role for manufacturers in helping to deliver energy efficient building projects – especially since declarations based on centre pane values go against building regulations.
The ratio of frame to glass has a direct correlation with a product’s thermal performance. The current trend in rooflight specification is for less frame and more glass, but the frame has to accommodate the technology and design features that deliver low U-values. Work to improve the performance of rooflights has actually resulted in ‘chunkier’ products, although each should be assessed on its own merits.
At face value, choosing one large roof window over two smaller ones is typically better in terms of heat loss, because there is more glass and less frame.
Taking a holistic approach to the building design, however, a number of smaller units in different parts of the roof can deliver better illumination of the space. If the goal is to maximise the number of natural daylight hours and limit the use of artificial lighting, then the compromise of more frame is acceptable.
Frames are typically manufactured from timber, plastics, aluminium and steel, or are composites of metal and plastic or wood. The choice of materials is driven by thermal performance requirements, a desire to use sustainable materials, structural performance, or simply the aesthetic.
Working with a manufacturer who can accurately model the performance of different specifications of rooflight and produce calculations to prove those claims – particularly where bespoke products are desirable or a necessity – is an important step towards having confidence in a design and knowing it can be delivered on site.
This topic is explored in our ‘Thermal Performance of Roof Glazing’ white paper, available to download for free here.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
Cookie | Duration | Description |
---|---|---|
SRM_B | 1 year 24 days | Used by Microsoft Advertising as a unique ID for visitors. |
Cookie | Duration | Description |
---|---|---|
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gat_UA-48441660-1 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
calltrk_session_id | 1 year | This cookie is set by the Provider CallRail. This cookie is used for storing an unique identifier for a user browser session. It is used for tracking the number of phone calls generate from the website. |
CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
vuid | 2 years | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. |
Cookie | Duration | Description |
---|---|---|
MUID | 1 year 24 days | Bing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
_clck | 1 year | No description |
_clsk | 1 day | No description |
calltrk_landing | 1 year | This is a functionality cookie set by the CallRail. This cookie is used to store the landing page URL. It helps to accurately attribute the visitor source when displaying a tracking phone number. |
calltrk_referrer | 1 year | This is a functionality cookie set by the CallRail. This cookie is used to store the referring URL. It helps to accurately attribute the visitor source when displaying a tracking phone number. |
CLID | 1 year | No description |
cookie_referer | session | No description |
SM | session | No description available. |
By providing this information, it allows us to forward your enquiry on to your local Technical Specification Manager and enables them to provide you with a formal quotation quicker.