Overview
A Project represents the highest level aspect of a Hero model. It holds high level data about the Project such as its Name, Type, as well as Site Information & Certification Notes.
It then holds either one Dwellingsor many Dwellings, as well as the various Levels that act as reference planes throughout the Project.
Most Project information is entered in the Project Data-Grid tab, with some aspects such as Levels & Project North dealt with in the Visual View.
These are expanded upon in further detail below:
Project Information:
Project Attribute | Description | Edited Within |
---|---|---|
Name | The name of the Project. Used for organisational purposes & tracking within the Hero Web-Portal | Project Data-Grid |
Reference Number | Reference Number for the Project, typically an Assessor’s own project numbering scheme. Used organisationally within the Hero Web-Portal. | Project Data-Grid |
Type | The Project Type including:
Note in the future Hero may combine the Existing Rating & Proposed Rating into a single Hero file but for now these are modelled as separate Hero Projects (i.e. two Hero files)
| Project Data-Grid |
Address (Street Address, Suburb) | The Project’s Street Address. | Project Data-Grid |
Post Code | The Project’s Post-Code. Used within the NatHERS Certificate and also to determine the NatHERS Climate Zone that can be used for the Project | Project Data-Grid |
Lot / DP # | Lot or Deposited Plan Number for the Project as per the existing or future Title. Used so that NatHERS Energy-Ratings can relate to specific addresses regardless of future changes to addresses etc, and will potentially make it easier for future search & retrieval of Energy-Rating information by future owners or occupants. For Multi-Dwelling Projects, the Lot Number is entered on a Dwelling by Dwelling basis and can be found & edited within the Dwelling Data-Grid | Project Data-Grid (Dwelling Data-Grid for Multi-Dwelling Projects) |
Certificate Notes | An area available for the User to Document any additional information to be added to the NatHERS Certificate as per NatHERS & AAO Requirements. Typical uses of this section is to document any assumptions made for the project, any substitutions or deviations away from standard NatHERS Technical Note guidance etc. | Project Data-Grid |
User Internal Notes | An area available for Users to record their own information relating to the Project for their own purposes such as for QA or organisational purposes. | Project Data-Grid |
Site Information
Site Attribute | Description | Edited Within |
---|---|---|
Climate Zone | The available NatHERS Climate Zones for the Project as determined by the Post-Code. The Climate Zone determines the Weather File that will be used for Chenath Simulations | Project Data-Grid |
Site Exposure | An attribute that describes the site context of the Project & that effects simulated wind-speeds within the Simulation. These are defined within the NatHERS Technical Notes Options include:
| Project Data-Grid |
Project North Arrow | The Direction of North on the Plans as relating to the way the Project is modelled in the Visual View. Effects all Model objects within the Project and accounts for the fact that some Plans similarly have a Project North arrow in a direction other than directly up the page For further information see Visual View Top Toolbar | Visual View |
Engagement Details
Site Attribute | Description | Edited Within |
---|---|---|
Plan Created By | The Designer or Architect who designed & documented the Project | Project Data-Grid |
Plan Document Name & Revision | The details of the Plans, Drawing, Specification and/or Documentation that were used to conduct the NatHERS Assessment for the Project, such as Plan package name, or file name, or revision. Allows Certifiers & Surveyors to ensure that the correct Design Drawings were used in the NatHERS Assessment. | Project Data-Grid |
Conflict of Interest | Defines the relationship of the NatHERS Assessor & the Client and whether there are any Conflicts of Interest as per NatHERS & AAO recommendations. |
Dwellings
The Project holds one or many Dwellings, which are the separate individual homes or townhouses or apartments within the Project.
Even a Single House Project within Hero still has 1 Project and 1 Dwelling within the Data Model, whereas a Multi-Dwelling Project may contain many Dwellings.
A Class 2 Multi-Dwelling Project may also contain a Common Area Dwelling which is a non-simulated Dwelling that holds Common Area Zones such as Common Corridors & Carparks.
Further Information: Dwellings
Levels
The Project holds one or more Levels which are Reference Planes that act to organise Model data both visually & within the Data-Grid.
Further Information: Levels