Roof setbacks define how much distance there must be between the system and the edges of the roof. This could due to a jurisdictional requirement, a fire code requirement, or a company design guideline.
You can easily define roof setbacks by clicking on Settings in the top right hand corner of your Site Model. In 2D mode, you are able to specify a setback for each of the following edge types: Eave, Ridge, Valley, Hip, and Rake. Additionally, you can specify setbacks around Obstructions, as well as a general setback that will be applied to all edges that have no edge type specified.
Note that for setbacks to be properly displayed, you will need to make sure that the edges in question have a Edge Type specified. You can set this by right-clicking on an edge and selecting a type in the drop down menu from the properties box that appears. Aurora can also auto-detect edge types for you. To do this, click on Analyze Roof Structure in the top toolbar.
Once you have defined your setbacks, Aurora will respect these setbacks in all assisted design steps (e.g. when filling a roof face with modules). Furthermore, the Validation Report will alert you, if any modules violate your setback requirements.
Aurora lets you pre-define jurisdictional requirements (including setbacks), so that you don't have to enter the same setback requirements over and over again.
If you are an admin, you can pre-define local (on the basis of an address) or state-wide jurisdictional requirements in your account settings.
If you do this, any new project created within your organization (by any user) will automatically pull in the relevant setback requirements for its location. Users can then override the setback values in the project, if necessary.
Note that address-based (local) jurisdictional requirements take precendent over state-wide ones. If the project is between two local jurisdictions, it will select whichever one is closer.