Upload
gabuchia
View
17
Download
2
Embed Size (px)
DESCRIPTION
Anzrs v3 01-2012 Changelog
Citation preview
This document lists all the changes that have been made since the previous version of ANZRS (Version 2., June 2011)Note: This document does not have a code because it does not form part of the official ANZRS pack. (For reference purposes only.)
REVIT FAMILY CREATION PACK ‐ CHANGE LOG Version 3 [01-2012]
ANZRS_CHANGE LOG, VERSION 3 © COPYRIGHT RESERVED HTTP://WWW.ANZRS.ORG PG 1/4
This document lists all the changes that have been made since the previous version of ANZRS (Version 2., June 2011)Note: This document does not have a code because it does not form part of the official ANZRS pack. (For reference purposes only.)
REVIT FAMILY CREATION PACK ‐ CHANGE LOG Version 3 [01-2012]
This document lists all the changes that have been made since the previous version of ANZRS (Version 2., June 2011)Note: This document does not have a code because it does not form part of the official ANZRS pack. (For reference purposes only.)
REVIT FAMILY CREATION PACK ‐ CHANGE LOG Version 3 [01-2012]
This document lists all the changes that have been made since the previous version of ANZRS (Version 2., June 2011)Note: This document does not have a code because it does not form part of the official ANZRS pack. (For reference purposes only.)
REVIT FAMILY CREATION PACK ‐ CHANGE LOG Version 3 [01-2012]
This document lists all the changes that have been made since the previous version of ANZRS (Version 2., June 2011)Note: This document does not have a code because it does not form part of the official ANZRS pack. (For reference purposes only.)
REVIT FAMILY CREATION PACK ‐ CHANGE LOG Version 3 [01-2012]
This document lists all the changes that have been made since the previous version of ANZRS (Version 2., June 2011)Note: This document does not have a code because it does not form part of the official ANZRS pack. (For reference purposes only.)
REVIT FAMILY CREATION PACK ‐ CHANGE LOG Version 3 [01-2012]
This document lists all the changes that have been made since the previous version of ANZRS (Version 2., June 2011)Note: This document does not have a code because it does not form part of the official ANZRS pack. (For reference purposes only.)
REVIT FAMILY CREATION PACK ‐ CHANGE LOG Version 3 [01-2012]
This document lists all the changes that have been made since the previous version of ANZRS (Version 2., June 2011)Note: This document does not have a code because it does not form part of the official ANZRS pack. (For reference purposes only.)
REVIT FAMILY CREATION PACK ‐ CHANGE LOG Version 3 [01-2012]
This document lists all the changes that have been made since the previous version of ANZRS (Version 2., June 2011)Note: This document does not have a code because it does not form part of the official ANZRS pack. (For reference purposes only.)
REVIT FAMILY CREATION PACK ‐ CHANGE LOG Version 3 [01-2012]
REFREF.
C1S VERSION 2 VERSION 3 COMMENTSC1S VERSION 2 VERSION 3 COMMENTS
G l A d d t i l t i l dGeneral Amended terminology to include f t th f f freference to other forms of reference
geometry namely reference lines andgeometry, namely reference lines and reference pointsreference points.
3.01 Heading: Reference to Reference Heading of this item has been Heading has been renamed to reduce gPlanes
grenamed to 'Dimension to Reference
gconfusion.
Elements '. Note: The term 'Reference Elements ' includes reference planes, reference lines
d f i tand reference points.
4.02 • Use Reference planes as a Altered terminology to include pframework to which geometry is
gyreference to other forms of reference g y
aligned and locked. geometry, namely reference lines and reference points. Referred to as 'R f El t ''Reference Elements'
U 'R f El t ' ( f• Use 'Reference Elements' (reference l t l d)planes are most commonly used) as a
framework to which geometry isframework to which geometry is aligned and lockedaligned and locked.
6.05 Modified Issue (currency format) 6.05 'Modified Issue (currency format)' has been merged with 6.04 'Modified I (d t )'Issue (date)'
6.06 6.06 Parametric Behaviour 6.05 Parametric Behaviour 6.06 has become 6.05
C2 / C2s VERSION 2 VERSION 3 COMMENTSC2 / C2s VERSION 2 VERSION 3 COMMENTS
G l D t d h Th f C2 d t ( C2 )General Document code change: Section C2 is now C2s
The former C2 document (now C2s) serves as the accompanying summarySection C2 is now C2s serves as the accompanying summary sheet to the new C2 Checklistsheet to the new C2 Checklist.This document includes both complianceThis document includes both compliance and optional discipline-specificand optional discipline-specific requirementsrequirements.
New The new C2 Checklist has been Discipline specific compliance checklistNew Document
The new C2 Checklist has been designed to accompany the C2s
Discipline-specific compliance checklist. Only compliance requirements are listed inDocument designed to accompany the C2s
Summary SheetOnly compliance requirements are listed in this checklistSummary Sheet. this checklist.
C3 / C3s VERSION 2 VERSION 3 COMMENTSC3 / C3s VERSION 2 VERSION 3 COMMENTS
General Document code change: The former C3 document (now C3s)General Document code change:Section C3 is now C3s
The former C3 document (now C3s) serves as the accompanying summarySection C3 is now C3s serves as the accompanying summary sheet to the new C3 Checklistsheet to the new C3 Checklist.This document includes both complianceThis document includes both compliance and optional discipline-specificand optional discipline-specific requirements.requirements.
New The new C3 Checklist has been Discipline specific compliance checklistNew Document
The new C3 Checklist has been designed to accompany the C3s
Discipline-specific compliance checklist. Only compliance requirements are listed inDocument designed to accompany the C3s
Summary SheetOnly compliance requirements are listed in this checklistSummary Sheet. this checklist.
10 01 The description and comments field10.01 The description and comments field for 10 01 'Justification' has beenfor 10.01 'Justification' has been updated to improve the explanation ofupdated to improve the explanation of this requirementthis requirement.
C4/C4s VERSION 2 VERSION 3 COMMENTSC4/C4s VERSION 2 VERSION 3 COMMENTS
G l D t d h Th f C4 d t ( C4 )General Document code change:S ti C4 i C4
The former C4 document (now C4s) th iSection C4 is now C4s serves as the accompanying summary
sheet to the new C4 Checklistsheet to the new C4 Checklist.This document includes both complianceThis document includes both compliance and optional discipline specificand optional discipline-specific requirementsrequirements.
New The new C4 Checklist has been Discipline specific compliance checklistNew Document
The new C4 Checklist has been designed to accompany the C4s
Discipline-specific compliance checklist. Only compliance requirements are listed inDocument designed to accompany the C4s
Summary SheetOnly compliance requirements are listed in this checklistSummary Sheet. this checklist.
ANZRS_CHANGE LOG, VERSION 3 © COPYRIGHT RESERVED HTTP://WWW.ANZRS.ORG PG 1/4
1.01 Heading: 'Annotation Symbols' Title changed from Annotation
ANZRS_CHANGE LOG, VERSION 3 © COPYRIGHT RESERVED HTTP://WWW.ANZRS.ORG PG 2/4
g y gSymbols to Nesting of Annotation Symbols vs. Detail Components
1 01 Requirement: Requirement:1.01 Requirement:Use Generic Annotation template for
Requirement:Where filled regions are required forUse Generic Annotation template for
all MEP 2D symbols in preference toWhere filled regions are required for symbolic representation:all MEP 2D symbols in preference to
the Detail Component templatesymbolic representation:• Use a nested Generic Annotationthe Detail Component template. • Use a nested Generic Annotation family for symbolic display of thefamily for symbolic display of the family where display size is set family where display size is set relative to printed output (e.g. a GPO relative to printed output (e.g. a GPO or light switch), or;or light switch), or;• Use a nested Detail Component Use a nested Detail Component where the family's size is relative to ythe model (e.g. a 1200mm long linear ( g glight fixture)g )
1.01 Impact: Impact:1.01 Impact:Ensures 2D symbols remain the
Impact:Using a nested Generic Annotation Ensures 2D symbols remain the
same size on sheet regardless of Using a nested Generic Annotation family will ensure that a 2D symbol same size on sheet regardless of
drawing scale. These annotation family will ensure that a 2D symbol remains the same size on sheet d a g sca e ese a otat o
families can then be nested into the e a s t e sa e s e o s eet
regardless of view scale. These various physical fitting families.
gannotation families can then be re-p y gused in other families. (e.g. other single-point light fixtures).Nested geometry is often required b fill d i hi hbecause filled regions, which are
f l f b li di l tuseful for symbolic display are not a ailable ithin 3D familiesavailable within 3D families.If filled regions are not required andIf filled regions are not required, and the symbolic display of a familythe symbolic display of a family should be determined relative to theshould be determined relative to the model symbolic linework may bemodel, symbolic linework may be sufficient without the use of nestedsufficient without the use of nested families at all.families at all.
8 01 Comments: Comments:8.01 Comments:E g Load Classification: Power Uses
Comments:Load classification types includeE.g. Load Classification: Power Uses
the demand factors set in electricalLoad classification types include HVAC Lighting Motor Other andthe demand factors set in electrical
settings under Power Extend theseHVAC, Lighting, Motor, Other and Powersettings under Power. Extend these
to suit the AUS/NZ standardsPower.Note: where the electrical connector'sto suit the AUS/NZ standards. Note: where the electrical connector s Load Classification value is set asLoad Classification value is set as 'Power', the Demand factor'sPower , the Demand factor s calculation method settings may not calculation method settings may not suit regional regulatory standards. In suit regional regulatory standards. In such cases, this item is exempt from such cases, this item is exempt from ANZRS compliance until feature pchanges in the software resolve this.gImpact: Allows for calculation of pmaximum demands for each Load Classification within the project. Also i t D d F t li dincorporates Demand Factors applied t L d Cl ifi tito Load Classifications.
8.01 Requirement: Requirement:qSystem types are automatically
qSystem types are automatically y yp y
specified from the connectors that the y yp y
specified from the connectors that the ppipe/duct/conduit/cable tray are
ppipes or ducts are connected into.
connected into.
8 01 Comments:8.01 Comments:Note: Cable trays and conduits do notNote: Cable trays and conduits do not have a System Type parameterhave a System Type parameter. They can make use of the parameterThey can make use of the parameter Service Type applied instead withinService Type applied instead within the project environmentthe project environment.
C5 VERSION 2 VERSION 3 COMMENTSC5 VERSION 2 VERSION 3 COMMENTS
Plumbing FlushingTechnology ANZRS has This was necessary to match the MEPPlumbing Equipment
FlushingTechnology_ANZRS has been recreated as a new parameter
This was necessary to match the MEP Shared Parameters (C7)Equipment been recreated as a new parameter
(with new GUID)Shared Parameters (C7)
(with new GUID)
M lti l N Sh d P t dd dMultiple Categories
New Shared Parameter added:CreatedByPhoneNo ANZRSCategories CreatedByPhoneNo_ANZRS
Multiple CreatedByURL_ANZRS(Text) Shared Parameter changed to URL Multiple Categories
CreatedByURL_ANZRS(Text) superseded by
Shared Parameter changed to URL format.g p y
CreatedByURL_ANZRS (URL)y _ ( )
ANZRS_CHANGE LOG, VERSION 3 © COPYRIGHT RESERVED HTTP://WWW.ANZRS.ORG PG 2/4
C7 VERSION 2 VERSION 3 COMMENTS
ANZRS_CHANGE LOG, VERSION 3 © COPYRIGHT RESERVED HTTP://WWW.ANZRS.ORG PG 3/4
C7 VERSION 2 VERSION 3 COMMENTS
P t P t G ithi Sh d C lC d fiParameter G ithi
Parameter Groups within Shared P t fil l fi d
CamelCase and prefix were never i dGroups within
SP fileParameter file are no longer prefixed with ‘MEP’ no longer in CamelCase
requiredSP file with ‘MEP’, no longer in CamelCase,
and now in plural form consistentlyand now in plural form consistently.The parameter groupThe parameter group 'MEPFireAlarmDivice' now renamed Typographical error fixed'MEPFireAlarmDivice' now renamed to 'Fire Alarm Devices'
Typographical error fixedto 'Fire Alarm Devices'
El t i l Li C tPh 1 ANZRS T b i t t ith i tiElectrical Equipment
LineCurrentPhase1_ANZRS superseded by
To be more consistent with existing Revit terminology; applies only whenEquipment superseded by
ApparentLoadPhase1 ANZRSRevit terminology; applies only when power is 3 phaseApparentLoadPhase1_ANZRS power is 3-phase
Electrical LineCurrentPhase2 ANZRS To be more consistent with existingElectrical Equipment
LineCurrentPhase2_ANZRS superseded by
To be more consistent with existing Revit terminology; applies only when Equipment superseded by
ApparentLoadPhase2 ANZRSRevit terminology; applies only when power is 3-phaseApparentLoadPhase2_ANZRS power is 3 phase
Electrical LineCurrentPhase3_ANZRS To be more consistent with existing Equipment
_superseded by
gRevit terminology; applies only when
ApparentLoadPhase3_ANZRS power is 3-phase
Electrical ActivePower ANZRS superseded by To be more consistent with existingElectrical Equipment
ActivePower_ANZRS superseded by ApparentLoad ANZRS
To be more consistent with existing Revit terminology; applies only whenEquipment ApparentLoad_ANZRS Revit terminology; applies only when power is single-phasepower is single-phase
El t i l N i f B ll tL d ANZRS B ll tL d ANZRS it t h ld bElectrical E i t
New version of BallastLoad_ANZRS t d ith GUID
BallastLoad_ANZRS unit type should be W tt t N bEquipment created, with new GUID Wattage, not Number.
Mechanical FCU(s)Served_ANZRS replaced with ec a caEquipment
CU(s)Se ed_ S ep aced tnew parameter q p pFCU_s_Served_ANZRS , in _ _ _accordance with C7 MEP SP tables
Multiple CreatedByURL ANZRS(Text) Shared Parameter changed to URLMultiple Categories
CreatedByURL_ANZRS(Text) superseded by
Shared Parameter changed to URL formatCategories superseded by
CreatedByURL ANZRS (URL)format.
CreatedByURL_ANZRS (URL)
Pl bi Fl hi t h l ANZRS l d T hi l fi d (l 'T'Plumbing E i t
Flushingtechnology_ANZRS replaced ith t
Typographical error fixed (lowercase 'T' i 'T h l ' Mi t h d ith it lfEquipment with new parameter
FlushingTechnology ANZRS inin 'Technology'. Mismatched with itself as it existed in other discipline specificFlushingTechnology_ANZRS , in
accordance with naming standardas it existed in other discipline-specific SP listsaccordance with naming standard SP lists.
C8 VERSION 2 VERSION 3 COMMENTSC8 VERSION 2 VERSION 3 COMMENTS
Curtain Existing subcategory: Changed subcategories: Now written in plural formPanels Threshold Thresholds
Detail Items Existing subcategory: Changed subcategories: Now written in plural formDetail Items Existing subcategory:Lightest Line
Changed subcategories:Lightest Lines
Now written in plural formLightest Line Lightest Lines
Mechanical - New subcategory:Mechanical Equipment
- New subcategory:BoilersEquipment Boilers
M h i l N bMechanical E i t
- New subcategory:Chill d BEquipment Chilled Beams
Mechanical - New subcategory:Mechanical Equipment
New subcategory:Chilled Water SetsEquipment Chilled Water Sets
Mechanical - New subcategory:Mechanical Equipment
- New subcategory:Condensing UnitsEquipment Condensing Units
Mechanical E i t
- New subcategory:C li TEquipment Cooling Towers
Mechanical - New subcategory:Mechanical Equipment
New subcategory:Variable Air Volume TerminalsEquipment Variable Air Volume Terminals
Multiple CreatedByURL ANZRS(Text) Shared Parameter changed to URLMultiple Categories
CreatedByURL_ANZRS(Text) superseded by
Shared Parameter changed to URL formatCategories superseded by
CreatedByURL ANZRS (URL)format.
CreatedByURL_ANZRS (URL)
G l W t th t b t iGeneral We note that some subcategories ('Clearance Zones') listed are not('Clearance Zones') listed are not directly useable This doesn't detractdirectly useable. This doesn't detract from the performance or operations offrom the performance or operations of the software so for the time being wethe software, so for the time being we have retained them (possible versionhave retained them (possible version and feature changes might makeand feature changes might make them usable in the future).them usable in the future).
ANZRS_CHANGE LOG, VERSION 3 © COPYRIGHT RESERVED HTTP://WWW.ANZRS.ORG PG 3/4
R2 VERSION 2 VERSION 3 COMMENTS
ANZRS_CHANGE LOG, VERSION 3 © COPYRIGHT RESERVED HTTP://WWW.ANZRS.ORG PG 4/4
R2 VERSION 2 VERSION 3 COMMENTS
6 03 Add d f l it6.03 - Added for clarity:I l i f th f ti l t i llInclusion of the functional type in all cases is better for overallcases is better for overall consistency Exceptions for specificconsistency. Exceptions for specific software features or categories createsoftware features or categories create confusion and may only apply for aconfusion and may only apply for a limited time Moreover family fileslimited time. Moreover, family files found outside of Revit are morefound outside of Revit are more recognizable (for what they are) byrecognizable (for what they are) by their filename.their filename.
6.05 Removed: To be more consistent with R2 6 036.05 Removed:Where the RMCSG recommends not
To be more consistent with R2 6.03Where the RMCSG recommends not using the category unless it is also using the category unless it is also the same as the Functional Type the same as the Functional Type field, we recommend including the field, we recommend including the category only where the object catego y o y e e t e objectcategory is not used/handled by a g y ycategory-specific tool (e.g. doors, g y p ( gwindows).
NOTESNOTES
REQUEST FOR INDUSTRY ASSISTANCE: We need more Industry feedback to improve this list and to better explain issues to be y p pconsidered when creating discipline sympathetic content. Please provide clear examples and explanation of issues through the feedback form on the ANZRS website.
It i i i th t th d t d d ill i th i d t f th d i t i l t t ti i iIt is our vision that these proposed standards will receive the promised support from the dominant commercial content creation companies in A t li N Z l d ll th R it itAustralia, New Zealand as well as the Revit user community.It is our intent that the criteria provided within this document pack will become the minimum benchmark of all shared and sold contentIt is our intent that the criteria provided within this document pack will become the minimum benchmark of all shared and sold content throughout Australia and New Zealand A content creator can only claim to provide ANZRS compliant content if the compliance requirementsthroughout Australia and New Zealand. A content creator can only claim to provide ANZRS-compliant content if the compliance requirements listed in this document are met on the respective components that they selllisted in this document are met on the respective components that they sell.
Refer to the Update Letter that is in the front section of this pack. It outlines other improvements to this ANZRS Pack Version 3.Refer to the Update Letter that is in the front section of this pack. It outlines other improvements to this ANZRS Pack Version 3.
ANZRS_CHANGE LOG, VERSION 3 © COPYRIGHT RESERVED HTTP://WWW.ANZRS.ORG PG 4/4