- Owners and Builders
The NatHERS Software Accreditation Protocol outlines in detail the requirements and processes for the accreditation of new software tools and new versions of previously accredited tools.
If you are the owner of an energy rating tool and are interested in getting your software accredited, please contact the NatHERS National Administrator following review of the NatHERS Software Accreditation Protocol.
A review of the Software Accreditation Protocol is currently underway as agreed by the NatHERS Steering committee (the Energy Efficiency Advisory Team (EEAT)) as one response to the 2016 NatHERS Governance and Operational Review.
To facilitate this review a discussion paper was developed and feedback was invited at the end of 2016. This feedback is being considered and further information about the progress of the review, and opportunities for comment, will be published on the NatHERS website as it becomes available.
The review of the Protocol is aimed at better documenting the principles and functional specifications of the NatHERS software tools, clarifying software tool requirements and regulatory obligations applying to changes to the software tools, as well as review the software accreditation process.
Under details set out in the Software protocol, all software must:
To ensure calculations are accurate, representative of Australian conditions and are comparable across different types of housing, the Software Protocol requires all NatHERS accredited software tools to meet strict performance standards and requirements for variables including (but not limited to):
For more information about some of these parameters, see How NatHERS Star Ratings are Calculated.
In order for any new software to become NatHERS accredited it must firstly be rigorously tested. During testing, independent assessors, approved by the NatHERS Administrator, compare the results of multiple simulated NatHERS ratings against the benchmark software tool, Accurate Version 220.127.116.11.
Each simulation is run using the new software tool developer’s own procedures and processes, as specified in its user manuals and guidance materials.
The results of each simulation are then compared against the results obtained by the benchmark tool when performing the same simulation.
All the individual simulations must achieve the following minimum result:
Furthermore, at least 95 per cent of the individual simulations must achieve the following more stringent result: