ASHRAE ADDENDA. A Data Communication Protocol for Building Automation and Control Networks

ANSI/ASHRAE Addendum af to ANSI/ASHRAE Standard 135-2010 ASHRAE ADDENDA A Data Communication Protocol for Building Automation and Control Networks Approved by the ASHRAE Standards Committee on June 25, 2011; by the ASHRAE Board of Directors on June 29, 2011; and by the American National Standards Institute on June 30, 2011. This addendum was approved by a Standing Standard Project Committee (SSPC) for which the Standards Committee has established a documented program for regular publication of addenda or revisions, including procedures for timely, documented, consensus action on requests for change to any part of the standard. The change submittal form, instructions, and deadlines may be obtained in electronic form from the ASHRAE Web site (www.ashrae.org) or in paper form from the Manager of Standards. The latest edition of an ASHRAE Standard may be purchased on the ASHRAE Web site (www.ashrae.org) or from ASHRAE Customer Service, 1791 Tullie Circle, NE, Atlanta, GA 30329-2305. E-mail: orders@ashrae.org. Fax: 404-321-5478. Telephone: 404-636-8400 (worldwide), or toll free 1-800-527-4723 (for orders in US and Canada). For reprint permission, go to www.ashrae.org/permissions. 2011 American Society of Heating, Refrigerating and Air-Conditioning Engineers, Inc. ISSN 1041-2336 American Society of Heating, Refrigerating and Air-Conditioning Engineers, Inc. 1791 Tullie Circle NE, Atlanta, GA 30329 www.ashrae.org

ASHRAE Standing Standard Project Committee 135 Cognizant TC: TC 1.4, Control Theory and Application SPLS Liaison: Richard L. Hall David Robin, Chair* Stephen Karg* William O. Swan, III Carl Neilson, Vice-Chair Simon Lemaire David B. Thompson* Bernhard Isler, Secretary* J. Damian Ljungquist* Stephen J. Treado* Donald P. Alexander* John J. Lynch Klaus Wagner Barry B. Bridges* Bryan Meyers J. Michael Whitcomb* Clifford H. Copass Dana Petersen Grant N. Wichenko* Coleman L. Brumley, Jr.* Frank Schubert Christoph Zeller Sharon E. Dinges* Ted Sunderland Scott Ziegenfus *Denotes members of voting status when the document was approved for publication. ASHRAE STANDARDS COMMITTEE 2010 2011 H. Michael Newman, Chair Allan B. Fraser Janice C. Peterson Carol E. Marriott, Vice-Chair Krishnan Gowri Douglas T. Reindl Douglass S. Abramson Maureen Grasso Boggarm S. Setty Karim Amrane Cecily M. Grzywacz James R. Tauby Robert G. Baker Richard L. Hall James K. Vallort Hoy R. Bohanon, Jr. Nadar R. Jayaraman William F. Walter Steven F. Bruning Byron W. Jones Michael W. Woodford Kenneth W. Cooper Jay A. Kohler Craig P. Wray Martin Dieryckx Frank Myers Hugh F. Crowther, BOD ExO William P. Bahnfleth, CO Stephanie C. Reiniche, Manager of Standards SPECIAL NOTE This American National Standard (ANS) is a national voluntary consensus standard developed under the auspices of the American Society of Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE). Consensus is defined by the American National Standards Institute (ANSI), of which ASHRAE is a member and which has approved this standard as an ANS, as substantial agreement reached by directly and materially affected interest categories. This signifies the concurrence of more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that an effort be made toward their resolution. Compliance with this standard is voluntary until and unless a legal jurisdiction makes compliance mandatory through legislation. ASHRAE obtains consensus through participation of its national and international members, associated societies, and public review. ASHRAE Standards are prepared by a Project Committee appointed specifically for the purpose of writing the Standard. The Project Committee Chair and Vice-Chair must be members of ASHRAE; while other committee members may or may not be ASHRAE members, all must be technically qualified in the subject area of the Standard. Every effort is made to balance the concerned interests on all Project Committees. The Manager of Standards of ASHRAE should be contacted for: a. interpretation of the contents of this Standard, b. participation in the next review of the Standard, c. offering constructive criticism for improving the Standard, or d. permission to reprint portions of the Standard. DISCLAIMER ASHRAE uses its best efforts to promulgate Standards and Guidelines for the benefit of the public in light of available information and accepted industry practices. However, ASHRAE does not guarantee, certify, or assure the safety or performance of any products, components, or systems tested, installed, or operated in accordance with ASHRAE s Standards or Guidelines or that any tests conducted under its Standards or Guidelines will be nonhazardous or free from risk. ASHRAE INDUSTRIAL ADVERTISING POLICY ON STANDARDS ASHRAE Standards and Guidelines are established to assist industry and the public by offering a uniform method of testing for rating purposes, by suggesting safe practices in designing and installing equipment, by providing proper definitions of this equipment, and by providing other information that may serve to guide the industry. The creation of ASHRAE Standards and Guidelines is determined by the need for them, and conformance to them is completely voluntary. In referring to this Standard or Guideline and in marking of equipment and in advertising, no claim shall be made, either stated or implied, that the product has been approved by ASHRAE.

[Thisforewordandthe rationales onthefollowingpagesarenotpartofthisstandard. Theyaremerelyinformativeanddonotcontainrequirementsnecessaryforconformance tothestandard.] FOREWORD Addendum 135af to ANSI/ASHRAE Standard 135-2010 contains a number of changes to the current standard. These modifications are the result of change proposals made pursuant to the ASHRAE continuous maintenance procedures and of deliberations within Standing Standard Project Committee 135. The changes are summarized below. 135F2010afF1.RemoveAnnexCandAnnexD,p.6. 135F2010af#2.ClarifyOptionalityofPropertiesRelatedtoIntrinsicEventReporting,p.7. 135F2010af#3.ClarifyOptionalityofPropertiesRelatedtoChangeofValueReporting,p.8. 135F2010af#4.EnsurethatPulse_RateandLimit_Monitoring_IntervalareAlwaysTogether,p.9. 135F2010af#5.ClarifywhenPriority_ArrayandRelinquish_DefaultareallowedtobePresent,p.10. 135F2010af#6.ClarifywhenSegmentationRelatedPropertiesareAllowedtobePresent,p.11. 135F2010af#7.ClarifywhenVirtualTerminalRelatedPropertiesareAllowedtobePresent,p.12. 135F2010af#8.ClarifywhenTimeSynchronizationIntervalPropertiesareAllowedtobePresent,p. 13. 135F2010af#9.ClarifywhenBackupandRestorePropertiesareAllowedtobePresent,p.14. 135F2010af#10.ClarifywhentheActive_COV_SubscriptionsPropertyisAllowedtobePresent,p.16. 135F2010af#11.ClarifywhentheSlaveProxyPropertiesareAllowedtobePresent,p.17. 135F2010af#12.ClarifywhentheRestartRelatedPropertiesareAllowedtobePresent,p.19. 135F2010af#13.ClarifywhentheLog_DeviceObjectPropertyPropertyisAllowedtobePresent,p.20. 135F2010af#14.ClarifywhentheClockAligningPropertiesareAllowedtobePresent,p.21. 135F2010af#15.ClarifywhentheOccupancyCountingPropertiesareAllowedtobePresent,p.22. 135F2010af#16.AddtheAbilitytoConfigureEventMessageText,p.24. 135F2010af#17.AddanEventDetectionEnable/DisableProperty,p.25. 135F2010af#18.AddtheAbilitytoDynamicallySuppressEventDetection,p.27. 135F2010af#19.AddtheAbilitytoSpecifyaDifferentTimeDelayforTOFNORMALTransitions,p.29. 135F2010af#20.AddtheAbilitytoInhibittheEvaluationofFaultConditions,p.30. 135F2010af#21.SeparatetheDetectionofFaultConditionsfromIntrinsicReporting,p.31. 135F2010afF22.Thissectionwasremovedafterthefirstpublicreview,p.32. 135F2010af#23.EnsurethatEventNotificationsarenotIgnoredduetoCharacterSetIssues,p.33. 135F2010af#24.MaketheEventReportingPropertyDescriptionsConsistent,p.34. 135F2010af#25.IdentifythePropertyineachObjectthatisMonitoredbyIntrinsicReporting,p.42. 135F2010af#26.ChangetheDescriptionoftheReliabilityProperty,p.50. 135F2010af#27.ImproveFaultDetectioninEventEnrollmentObjects,p.54. 135F2010af#28.AddtheAbilityforsomeObjectsTypestoSendOnlyFaultNotifications,p.57. 135F2010af#29.AddaNotificationForwarderObjectType,p.60. 135F2010af#30.ReducetheRequirementsonNotificationFServers,p.69. 135F2010afF31.AddanAlertEnrollmentObjectType,p.71. 135F2010af#32.ImprovetheSpecificationofEventReporting,p.75. Inthefollowingdocument,languagetobeaddedtoexistingclausesofANSI/ASHRAE135@2010and Addendaisindicatedthroughtheuseofitalics,whiledeletionsareindicatedbystrikethrough.Where entirelynewsubclausesareproposedtobeadded,plaintypeisusedthroughout. 1

INTRODUCTION ASHRAESSPCI135hasaddressedanumberofissuesintheBACnetstandardrelatedtoeventsandalarms over the years. Numerous inconsistencies have been identified and clarified through the use of interpretationrequests,buthavenotbeencomprehensivelyaddressedinthestandard.alargerinitiativein the form of three threeiday "Alarm Summit" meetings and many conference calls over the course of 18 monthshasledtothisalarmaddendumthatproposesacomprehensiveresolutionoftheseissues. This introduction provides some background information on the history and development of the Alarm Addendum.Butasitsmainpurpose,thereaderwillbeintroducedtothechangesproposedandguidedin readingtheaddendum. CONTENTS 1 AlarmAddendumHistory...1 2 InitialListofIssues...2 3 AlarmAddendumOverview...3 3.1 Section1toSection15:PavingtheGroundfortheFuture...3 3.2 Section32:GeneralRevisionofAlarmandEventConcepts...3 3.3 Section16toSection28:ParticularChanges...3 3.4 Section29andSection30:NotificationForwarding...4 3.5 Section31:AddanAlertEnrollmentObjectType...5 4 Acknowledgments...5 1. AlarmAddendumHistory Intherecentyears,manychangeproposalsandinterpretationrequestsrelatedtoalarmsandeventshave been brought before the BACnet committee. These documents were seeking for clarifications, extensions andchangestotheeventmechanismsofbacnet.manyofthechangeproposalswerestalledatthepointof recognizingthesignificantamountofworkrequiredtoproposecomprehensivemodificationstotheevent mechanismspecificationofbacnet. InGermantowninApril2008,aninterpretationrequestwasdiscussedthataskedforthepossibilityfora more reasonable notification of fault events. This was the ultimate trigger for the committee to start an initiative called "Alarm Summit" that was dedicated to address all pending issues and to revise the specificationinacomprehensiveandmeaningfulway. In June 2008 during the Salt Lake City meeting, a first Alarm Summit meeting was agreed upon and scheduledforfall2008,rightbeforetheregularcommitteeandworkinggroupinterimmeetingsinatlanta. After two other Alarm Summit meetings, many hours of Objects & Services Working Group (OSIWG) meetingsandmanytelephoneconferences,theosiwghaspreparedthisdraftofthealarmaddendumfor reviewbythecommitteeandthepublic. 2. InitialListofIssues DuringthefirstAlarmSummitmeetingalistofissueswascompiled.Theissuesdiscussedinclude: IClarificationandimprovementoffaultreporting IRevisethestandardtouseamoreformallanguageforthealarmandeventspecification IFreedomtochoosetheeventalgorithmusedforintrinsicreportingbyaparticularobjecttype ISupportofgenericalarmnotifications,notboundtoanalgorithm IExtendedcapabilitiestoinhibittheeventalgorithm IAdditionofastandardmechanismtoforwardeventnotifications IRelaxingtheeventalgorithmstoallowadditionaltransitions IImprovementsofenrollmentandadditionofsubscriptionmechanismfortemporaryclients IClarificationsofalarmsummarizationmechanisms IAlarmacknowledgmentimprovements IImprovementofalarmconfigurationsecurity IMultiplealarmalgorithmsperobject,fordifferentkindsofevents IExtensionsofeventnotificationmessages 2

IAdditionofanalarmescalationmechanism IAlarmgroupingandaggregation IAdditionalpropertiesinalarmgeneratingobjectsforbettervisibilityofalarmconditions IAlarmclassificationimprovements IOtherminorissues Notalloftheseissuesmadeitthroughthedebates,andsomewererearrangedwhileotherswereadded.In addition, it turned out that some of the issues can only be resolved reasonably by some more radical approaches.suchapproacheswereconsideredrisky,timeconsumingandcontentious.itbecameclearthata prioritization is required. As a result, only those issues that are urgent, are fixing major flaws, or are requiredtopavethegroundforthefuturehavebeenaddressedinthisaddendumasafirststep. As a guiding principle, changes were crafted carefully to preserve backward compatibility with existing definitionstothegreatestextentpossible. 3. AlarmAddendumOverview TheAlarmAddendum,ascompletedforitsfirstpublicreview,contains32parts,identifiedbynumbers.In ordertoaddresstheobjectsandpropertiesofthe135i2010versionofthestandard,andthoseofaddenda thatareeitherpublishedormaybeinpublicreviewatthesametimeasthisaddendum,amoregeneric languageisusedtoidentifytheapplicableobjectsandproperties. Asanoverview,thechangesproposedinthesepartscanbesummarizedasfollows. Section1toSection15:PavingtheGroundfortheFuture Thesechangeswillimprovefurthermaintenanceofthestandard.Also,theyaddclarityandconsistencyto definitionsthatwillbecomerelevantinfuturechanges,inparticularforthosechangesthatwillbeneededto goforwardwithissuesnotyetaddressed. Section1:RemoveAnnexCandAnnexD AnnexCandAnnexDarebeingremovedfromthestandardbecausetheydonotprovideinformationthatis not already clear from other parts of the standard and have proven to be problematic in respect to maintenanceofthestandard. Section2toSection15:ClarificationsonPropertyPresence Language on presence requirements of properties is made clear. In general, presence requirements are modifiedsothatitisclearunderwhatconditionspropertiesareallowedtobepresent. Section32:GeneralRevisionofAlarmandEventConcepts Althoughnotbeingthefirstpartoftheaddendum,theconceptandlanguagerevisionofeventreportingisto be found in part 32. This part entirely replaces existing clauses 13.2, 13.3 and 13.4. The changes in functionality are minimal. However, these clauses have been completely rewritten to gain clarity in the definitionofeventreporting.theformercontenthasbeenrearrangedandsomepartswerereassignedto morerelevantclausesofthestandard.thisaddendumpartisalsothekeytobetterunderstandingthemore particularchangesmadetoobjectsandpropertiesrelatedtoeventreporting. One of the main drivers for this general revision is to ensure that event reporting works consistently betweenintrinsicandalgorithmicreporting,includingfaultreporting. IncludedinthissectionisachangetotheLoadControlobjecttogenerateCHANGE_OF_STATEnotifications insteadofcommand_failurenotifications. NewClause13.2:EventReportingConcepts Thenewlanguagefortheconceptsprovidesclearidentification,separationandgeneraldescriptionofevent statedetection,eventnotificationdistribution,alarmacknowledgementandeventsummarization.also,it clearlyseparatesthefaultevaluationforthedeterminationofthereliabilityfromeventstatedetection. NewClause13.3:EventAlgorithms 3

Theeventalgorithmsarenowdescribedusingmoreformallanguage,aformalmethod,andastyletemplate. The algorithms are generally applicable for both algorithmic and intrinsic reporting, through a defined interface. The event algorithms have been extended to allow additional transitions, while preserving backwardcompatibility. NewClause13.4:FaultAlgorithms Faultalgorithmshavebeenaddedusingthesameformallanguage,formalmethod,andastyletemplateas fortheeventalgorithms.thefaultalgorithmsareusedintheevaluationofreliability,nottheeventstate. Section16toSection28:ParticularChanges Thesechangescomplementobjectandservicespecificationstorealizetheeventreportingconcept,toadd particularfeaturesandtoclarifydetailsofeventreporting. Section16:AddintheAbilitytoConfigureEventMessageText Anewpropertyisaddedtoalleventgeneratingobjectsthatallowsconfiguringtheeventmessagetexttobe conveyedwitheventnotifications. Section17:AddinanIntrinsicReportingEnable/DisableProperty Toallowtheintrinsicreportinginanobjecttobeenabled/disabled,andtoallowtheindicationofwhether ornotanobjectisconfiguredforintrinsicreporting,thepropertyevent_detection_enableisaddedtoall objectstypesthatsupportintrinsicreporting. Section18:AddintheAbilitytoDynamicallySuppressEventDetection Toallowthedetectionofoffnormalconditionstobedynamicallysuppressed,twopropertiesareaddedto alleventiinitiatingobjects.suppressionofoffnormaleventstatescanbecontrolledeitherlocally,orby somevalueinanotherobjectofthedevice. Section19:AddintheAbilitytoSpecifyaDifferentTimeDelayforTOFNORMALTransitions To allow a different time delay to be used for TOINORMAL event transitions, the Time_Delay_Normal property is added to all eventiinitiating objects. The Time_Delay_Normal property is added to the Event EnrollmentobjectasapropertyinsteadofasafieldintheBACnetEventParameterproductioninorderto keepbackwardcompatibility. Section20:AddintheAbilitytoInhibittheEvaluationofFaultConditions To inhibit the detection and reporting of Fault conditions, the Reliability_Evaluation_Inhibit property is addedtoallobjectstypesthatcontainareliabilityproperty. Section21:SeparatetheDetectionofFaultConditionsfromIntrinsicReporting Inobjecttypeswheresomefaultconditionsaredefinedbypropertiesintheobject(i.e.Fault_Values),the properties associated with reliabilityievaluation are separated from intrinsic reporting. This allows an objecttodetectfaultconditionsusingthesepropertieswhentheobjectdoesnotsupportintrinsicreporting. Section22:SpecifytheContentoftheMessageTextinAcknowledgementNotifications Whenacknowledginganeventnotification,theacknowledgingdeviceisgiventheopportunitytoprovide theacknowledgmentsource.toallowforthesharingoftheacknowledgementsource,thischangemandates thatthesourcebedistributedasthemessagetextparameterofacknowledgementnotifications. Section23:EnsurethatEventNotificationsarenotIgnoredduetoCharacterSetIssues ThischangeensuresthateventnotificationsareprocessedevenwhentheMessageTextparameterisinan unknowncharacterset. Section24:MaketheEventReportingPropertyDescriptionsConsistent The unification of the property descriptions helps to ensure that event algorithms and event reporting propertiesarespecifiedandappliedconsistentlythroughoutthestandard. The property descriptions for event reporting properties that are the parameters to an object s event algorithmarechangedtorelyonthedescriptionoftheeventalgorithm,therebynotreplicatingit. Section25:IdentifythePropertyineachObjectthatismonitoredbyIntrinsicReporting 4

In extracting the algorithm descriptions from the object types, the identification of the value(s) that are monitoredbytheeventalgorithmislost.thissectionaddsbackintheidentification,andlinkstheproperty totheeventalgorithmparameterforintrinsicreporting. Section26:ChangethedescriptionoftheReliabilityProperty ThisallowsobjectstouseanyoftheReliabilityvaluesthatareappropriateasdefinedbythecentraltableof ReliabilityvaluesintheClause12overview. Section27:ImproveFaultDetectioninEventEnrollmentObjects ThisimprovesthefaultdetectionintheEventEnrollmentobjectssothatfaultsinthemonitoredobjectand faultsintheeventenrollmentobjectcanbereportedanddistinguished. Section28:ProvideforObjectTypesthatonlySendFaultNotifications TheSchedule,Program,andCredentialDataInputobjecttypesareabletodetectfaultsbutarenotcurrently abletosendnotificationsindicatingthefaults.thischangeaddstheabilityforthoseobjectstodoso.other access control objects may also have a Reliability property, but will become unreliable only to indicate configurationerrors.addingintrinsicreportingwasconsideredtooheavyiweightfortheseobjects. Section29andSection30:NotificationForwarding Notificationforwardingisanewfeatureaddedtotheeventnotificationdistribution. Section29:AddaNotificationForwarderObjectType ThispartaddsanewNotificationForwarderobject.Thisnewobjectaddsimportantfeaturesinnotification distribution. It allows reducing the number of recipient lists, and supports simple devices with limited capabilitiestoparticipateinsophisticateddistributionscenarios.inadditiontotheratherstaticenrollment forevents,itsupportsdynamicsubscriptionforevents. Section30:ReducetheRequirementsonNotificationFServers Toreducethelevelofeffortrequiredtoimplementbasiceventreporting,thenotificationdistribution requirementsarereduced.thischangeworksinconcertwiththeadditionofthenotificationforwarder objectthatmaybeinanotherdevice. Section31:AddanAlertEnrollmentObjectType Thisnewobjectallowsanyobjecttoindicatetheoccurrenceofinterestingeventsthatareunrelatedtothe object sstate,eventstateoreventalgorithm.theeventsreportedthroughthisnewmechanismare consideredstatelessevents,notrelatedtoaneventstatemachine.thereisneitheracknowledgementnor returnfromeventconcepts.theeventidentificationandeventparametersaredeterminedbythevendor indicatedinthenotifications. 4 Acknowledgments Thecommitteewishestothankallcontributorstothisaddendum: CarlNeilson,DeltaControls CliffordH.Copass,JohnsonControls RenéKälin,Siemens BernhardIsler,Siemens ChristophZeller,Sauter RolandLaird,ReliableControls CraigGemmill,Tridium BillSwan,Alerton/Honeywell AttendeesofAlarmSummitMeetings,OSIWGMeetingsandTeleconferences PublicReviewCommenters 5

135F2010af#1.RemoveAnnexCandAnnexD. Rationale AnnexCandAnnexDarebeingremovedfromthestandardbecausetheydonotprovideinformationthatis notalreadyclearfromotherpartsofthestandard,andtheyhaveproventobeproblematicwithrespectto maintenanceofthestandard. [ReplaceAnnexC,p.698] ANNEXCFFORMALDESCRIPTIONOFOBJECTTYPESTRUCTURES(INFORMATIVE) ThisannexwasremovedfromthestandardbyAddendum135I2010af. [ReplaceAnnexD,p.723] ANNEXDFEXAMPLESOFSTANDARDOBJECTTYPES(INFORMATIVE) ThisannexwasremovedfromthestandardbyAddendum135I2010af. 6

135F2010af#2.ClarifyOptionalityofPropertiesRelatedtoIntrinsicEventReporting. Rationale The standard is not clear on whether or not properties that are related to intrinsic event reporting are allowedtobeincludedinobjectinstancesthatdonotsupportintrinsicreporting. The majority of these properties are not allowed except when intrinsic reporting is supported. The propertiesthatareallowedtobepresentinanobjectthatdoesnotsupportintrinsicreportingare: Adjust_Value,Fault_Values,Feedback_Value,Limit_Monitoring_Interval,Pulse_Rate, Occupancy_Count,Occupancy_Count_Enable. Thechangesareappliedtoallobjectstypesdefinedinthestandardandalladdendathatsupportintrinsic reporting. NotethatEventEnrollmentandNotificationClassobjectsdonotsupportintrinsicreporting(theyplayother rolesineventreporting)andassuchthissectiondoesnotapplytotheseobjecttypes. [AddFootnotetoevery"Table12FX.Propertiesof..."forobjecttypesthatallowsupportofintrinsic reporting,andapplyfootnotetoeverypropertythatiscurrentlyfootnotedasrequiredforintrinsic reporting,except:adjust_value,fault_values,feedback_value,limit_monitoring_interval,occupancy_count, Occupancy_Count_Enable,Pulse_Rate.] [Notethateachobjecttypethatsupportsintrinsicreportingalreadyhasafootnotexasshownbelow,orone ofsimilarwording,andthischangeaddsfootnotey.] [NotethatEventEnrollmentandNotificationClassobjectsdosupportintrinsicreporting(theyplayother rolesineventreporting)andassuchthissectiondoesnotapplytothoseobjecttypes.] PropertyIdentifier PropertyDatatype ConformanceCode Event_Enable BACnetEventTransitionBits O x,y) xthesepropertiesarerequirediftheobjectsupportsintrinsicreporting. y)these)properties)shall)be)present)only)if)the)object)supports)intrinsic)reporting.) [ChangeFootnote4toTable12F36,,AccessPointproperties,p.313] 4Thesepropertiesarerequiredtobepresentiftheobjectsupportsintrinsicreporting. [ChangeFootnote3toTable12F31,EventLogproperties",p.287] 3Thesepropertiesarerequiredtobepresentiftheobjectsupportsintrinsicreporting. [ChangeFootnote4toTable12F35,TrendLogMultipleproperties,p.305] 3Thesepropertiesarerequiredtobepresentiftheobjectsupportsintrinsicreporting. 7

135F2010af#3.ClarifyOptionalityofPropertiesRelatedtoChangeofValueReporting. Rationale The standard is not clear on whether or not properties that are related to change of value reporting are allowedtobeincludedinobjectinstancesthatdonotsupportchangeofvaluereporting. This change clarifies that none of these properties are allowed in an object that does not support COV reporting. The changes are applied to all objects types defined in the standard and all addenda that support COV reportingthroughthesubscribecovservice. [ChangeFootnotextoevery"Table12FX.Propertiesof..."forobjecttypesthatidentifypropertiesrequired forcovreporting.] xthispropertyisrequiredif,)and)shall)be)present)only)if,theobjectsupportscovreporting. 8

135F2010af#4.EnsurethatPulse_RateandLimit_Monitoring_IntervalareAlwaysTogether. Rationale Limit_Monitoring_Interval is required in order to calculate Pulse_Rate but has no useful purpose if Pulse_Rateismissing.Thischangeensuresthat,ifoneispresent,thentheotherwillalsobepresent. [AddFootnotetoTable12F1,p.147] Table12F1.PropertiesoftheAccumulatorObject PropertyIdentifier PropertyDatatype ConformanceCode Pulse_Rate Unsigned O 1,4,x ) Limit_Monitoring_Interval Unsigned O 4,x ) 1ThispropertyisrequiredtobewritablewhenOut_Of_ServiceisTRUE. 4Thesepropertiesarerequirediftheobjectsupportsintrinsicreporting. x)if)one)of)these)properties)is)present,)then)both)shall)be)present.) ) [ChangeClause12.1.23,p.154] 12.1.23Limit_Monitoring_Interval Thisproperty,oftypeUnsigned,specifiesthemonitoringperiodinsecondsfordeterminingthevalueof Pulse_Rate. The use of a fixed or sliding time window for detecting pulse rate is a local matter. This propertyisrequiredifthisobjectsupportsintrinsicreporting. 9

135F2010af#5.ClarifywhenPriority_ArrayandRelinquish_DefaultareallowedtobePresent. Rationale ClarifythatthepresenceofPriority_ArrayandRelinquish_Defaultindicatecommandabilityofavalueobject. [ChangeFootnotextoevery"Table12FX.Propertiesof..."containingPriority_ArrayandRelinquish_Default properties] PropertyIdentifier PropertyDatatype ConformanceCode Priority_Array BACnetPriorityArray O x Relinquish_Default REAL O x xthese)properties)are)required)if,)and)shall)be)present)only)if,)ifpresent_valueiscommandable, thenbothofthesepropertiesshallbepresent.) [ChangeClauses"12.X.Y1Priority_Array"propertydescriptioninallvalueobjects.] [Notethattheword optional mayormaynotbepresent.ifpresent,itshallbestricken.] 12.X.Y1Priority_Array This[optional]propertyisareadIonlyarraythatcontainsprioritizedcommandsthatareineffectfor thisobject.seeclause19foradescriptionoftheprioritizationmechanism.ifeitherthepriority_array property or the Relinquish_Default property are present, then both of them shall be present. If Present_Valueiscommandable,thenPriority_ArrayandRelinquish_Defaultshallbothbepresent. [ChangeClauses"12.X.Y2Relinquish_Default"propertydescriptioninallvalueobjects.] [Notethattherearecurrently2differentformsoftextforRelinquish_Defaultpropertydescriptions.Thetwo differentformsareshownbelowidentifyingtheresultingchanges.inthesecondcase,thedatatypevaries dependingontheobjecttypeandthedatatypeshownisonlyanexample.thischangesunifiesthelanguage forallrelinquish_defaultproperties.] [Notethattheword optional mayormaynotbepresent.ifpresent,itshallbestricken.] [version1] 12.X.Y2Relinquish_Default This [optional] property is the default value to be used for the Present_Value property when all commandpriorityvaluesinthepriority_arraypropertyhaveanullvalue.seeclause19.ifeitherthe Relinquish_Default property or the Priority_Array property are present, then both of them shall be present. If Present_Value is commandable, then Priority_Array and Relinquish_Default shall both be present. [version2] 12.X.Y2Relinquish_Default This[optional]property,oftypeBACnetDateTime,isthedefaultvaluetobeusedforthePresent_Value property when all command priority values in the Priority_Array property have a NULL value. See Clause19.IfeithertheRelinquish_DefaultpropertyorthePriority_Arraypropertyispresent,thenboth ofthemshallbepresent.ifpresent_valueiscommandable,thenpriority_arrayandrelinquish_default shallbothbepresent. 10

135F2010af#6.ClarifywhenSegmentationRelatedPropertiesareAllowedtobePresent. Rationale Clarify that Max_Segments_Accepted and APDU_Segment_Timeout shall only be present if the device supportssegmentation. [ChangeFootnote1toTable12F13,p.196] 1 Required if These)properties)are)required)if,)and)shall)be)present)only)if, segmentation of any kind is supported. [ChangeClause12.11.27,p200] 12.11.27APDU_Segment_Timeout The APDU_Segment_Timeout property, of type Unsigned, shall indicate the amount of time in millisecondsbetweenretransmissionofanapdusegment.asuggestedvalueforthispropertyis5000 milliseconds.thisvalueshallbenonizeroifthedeviceobjectpropertycallednumber_of_apdu_retries isnonizero.seeclause5.3.ifsegmentationofanykindissupported,thentheapdu_segment_timeout propertyshallbepresent. In order to achieve reliable communication, it is recommended that the values of the APDU_Segment_Timeout properties of the Device objects of all intercommunicating devices should containthesamevalue. 11

135F2010af#7.ClarifywhenVirtualTerminalRelatedPropertiesareAllowedtobePresent. Rationale Clarify that VT_Classes_Supported and Active_VT_Sessions shall be present only if the device supports VirtualTerminalservices. [ChangeFootnote2toTable12F13,p.196] 2 If one of the properties VT_Classes_Supported or Active_VT_Sessions is present, then both of these propertiesshallbepresent.bothpropertiesarerequired,)ifsupportforvtservicesisindicatedinthe PICS.)These)properties)are)required)if,)and)shall)be)present)only)if,)the)VT)Services)are)supported. [ChangeClause12.11.21,p199] 12.11.21VT_Classes_Supported The VT_Classes_Supported property is a List of BACnetVTClass each of which is an enumeration indicatingaparticularsetofterminalcharacteristics.agivenbacnetdevicemaysupportmultipletyp esofbehaviorsfordifferingtypesofterminalsordifferingtypesofoperatorinterfaceprograms.ata minimum,suchdevicesshallsupportthe"defaultiterminal"vticlassdefinedinclause17.5. If one of the properties VT_Classes_Supported or Active_VT_Sessions is present, then both of these propertiesshallbepresent.bothpropertiesarerequiredifsupportforvtservicesisindicatedinthe PICS. [ChangeClause12.11.22,p199] 12.11.22Active_VT_Sessions The Active_VT_Sessions property is a List of BACnetVTSession each of which consists of a Local VT SessionIdentifier,aRemoteVTSessionIdentifier,andRemoteVTAddress.Thispropertyprovidesa networkivisibleindicationofthosevirtualterminalsessions(vtisessions)thatareactiveatanygiven time.wheneveravirtualterminalsessioniscreatedwiththevtiopenservice,anewentryisaddedto the Active_VT_Sessions list. Similarly, whenever a VTIsession is terminated, the corresponding entry shallberemovedfromtheactive_vt_sessionslist. If one of the properties VT_Classes_Supported or Active_VT_Sessions is present, then both of these propertiesshallbepresent.bothpropertiesarerequiredifsupportforvtservicesisindicatedinthe PICS. 12

135F2010af#8.ClarifywhenTimeSynchronizationIntervalPropertiesareAllowedtobePresent. Rationale ClarifythatTime_Synchronization_Interval,Align_IntervalsandInterval_Offsetshallbepresentonlyifthe devicesupportsoneofthetimesynchronizationrecipientlistproperties. [ChangeFootnote5andFootnote14ofTable12F13,p.196] 5 If this property is present, then Time_Synchronization_Interval, Align_Intervals and Interval_Offset shallbepresent.ifpresent,thispropertyshallbewritable.... 14IfThese)properties)are)required)if,)and)shall)be)present)only)if,)eitherTime_Synchronization_Recipients orutc_time_synchronization_recipientsispresent.,thenthispropertyshallbepresent.andif) present,)these)properties)shall)be)writable. 13

135F2010af#9.ClarifywhenBackupandRestorePropertiesareAllowedtobePresent. Rationale Clarify that Configuration_Files, Last_Restore_Time, Backup_Failure_Timeout, Backup_Preparation_Time, Restore_Preparation_Time,Restore_Completion_TimeandBackup_And_Restore_Stateshallonlybepresent ifthedevicesupportsthebackupandrestoreprocedures. [ChangeFootnote7andFootnote8toTable12F13,p.196] 7 Thesepropertiesarerequiredif,)and)shall)be)present)only)if,thedevicesupportsexecutionofthe backupandrestoreprocedures. 8 Thisproperty)shallbepresentis)required)if,)and)shall)be)present)only)if,andwritableifthedevice supportsexecution)of)thebackupandrestoreprocedures.if)present,)this)property)shall)be)writable.) [AddfootnotetoentryinTable12F13,p.196] Table12F13.PropertiesoftheDeviceObjectType PropertyIdentifier PropertyDatatype ConformanceCode Backup_And_Restore_State BACnetBackupState OO 7 [AddFootnotextoTable12F13,p.196] Table12F13.PropertiesoftheDeviceObjectType PropertyIdentifier PropertyDatatype ConformanceCode Backup_Preparation_Time Unsigned16 O x Restore_Preparation_Time Unsigned16 O x Restore_Completion_Time Unsigned16 O x xthese)properties)are)required)if,)and)shall)be)present)only)if,)the)device)supports)execution)of)the)backup) and)restore)procedures)as)described)in)clause)19.1)and)cannot)respond)to)subsequent)communications) within)the)minimum)value)it)will)accept)in)its)apdu_timeout)property. [ChangeClause12.11.37,p.201] 12.11.37Last_Restore_Time This optional property, of type BACnetTimeStamp, is the time at which the device's image was last restoredasdescribedinclause19.1.thispropertymustbesupportedifthedevicesupportsthebacnet backupandrestoreproceduresasdescribedinclause19.1. [ChangeClauses12.11.51through12.11.54,p.203] 12.11.51Backup_Preparation_Time $ Thisoptionalproperty,oftypeUnsigned16,indicatestheamountoftimeinsecondsthatthedevice mightremainunresponsiveafterthesendingofareinitializedeviceiackatthestartofabackup procedure.thedevicethatinitiatedthebackupshalleitherwaittheperiodoftimespecifiedbythis propertyorbepreparedtoencountercommunicationtimeoutsduringthisperiod.theuseofthisvalue isdescribedinmoredetailinclause19.1. Thispropertyisrequiredifthedevicesupportsexecutionofthebackupandrestoreproceduresand cannotcompletebackuppreparationwithintheminimumvalueitwillacceptinitsapdu_timeout property. 14

12.11.52Restore_Preparation_Time Thisoptionalproperty,oftypeUnsigned16,indicatestheamountoftimeinsecondsthatthedeviceis allowedtoremainunresponsiveafterthesendingofareinitializedeviceiackatthestartofarestore procedure.therestoringdeviceshalleitherwaitorbepreparedtoencountercommunicationtimeouts duringthisperiod.theuseofthisvalueisdescribedinmoredetailinclause19.1. Thispropertyisrequiredifthedevicesupportsexecutionofthebackupandrestoreproceduresand cannotcompleterestorepreparationwithintheminimumvalueitwillacceptinitsapdu_timeout property. 12.11.53Restore_Completion_Time Thisoptionalproperty,oftypeUnsigned16,indicatestheamountoftimeinsecondsthatthedeviceis allowedtoremainunresponsiveafterthesendingofareinitializedeviceiackattheendofarestore procedure.therestoringdeviceshalleitherwaitorbepreparedtoencountercommunicationtimeouts duringthisperiod.theuseofthisvalueisdescribedinmoredetailinclause19.1. Thispropertyisrequiredifthedevicesupportsexecutionofthebackupandrestoreproceduresand cannotrespondtosubsequentcommunicationswithintheminimumvalueitwillacceptinits APDU_Timeoutproperty. 12.11.54Backup_And_Restore_State $ Thisoptionalproperty,oftypeBACnetBackupState,indicatesaserverdevice'sbackupandrestorestate. TheuseofthisvalueisdescribedinmoredetailinClause19.1. 15

135F2010af#10.ClarifywhentheActive_COV_SubscriptionsPropertyisAllowedtobePresent Rationale ClarifythatActive_COV_SubscriptionsshallonlybepresentifthedevicesupportsexecutionofSubscribeCOV orsubscribecovproperty. [ChangeFootnote9toTable12F13,p.196] 9 Thispropertyisrequiredif,)and)shall)be)present)only)if,thedevicesupportsexecutionofeitherthe SubscribeCOVorSubscribeCOVPropertyservice. [ChangeClause12.11.39,p.201] 12.11.39Active_COV_Subscriptions TheActive_COV_SubscriptionspropertyisaListofBACnetCOVSubscription,eachofwhichconsistsofa Recipient, a Monitored Property Reference, an Issue Confirmed Notifications flag, a Time Remaining valueandanoptionalcovincrement.thispropertyprovidesanetworkivisibleindicationofthosecov subscriptions that are active at any given time. Whenever a COV Subscription is created with the SubscribeCOVorSubscribeCOVPropertyservice,anewentryisaddedtotheActive_COV_Subscriptions list.similarly,wheneveracovsubscriptionisterminated,thecorrespondingentryshallberemoved fromtheactive_cov_subscriptionslist. This property is required if the device supports execution of either SubscribeCOV or SubscribeCOVPropertyservice. 16

135F2010af#11.ClarifywhentheSlaveProxyPropertiesareAllowedtobePresent. Rationale Clarify that Slave_Proxy_Enable, Manual_Slave_Address_Binding, Auto_Slave_Discovery and Slave_Address_BindingshallonlybepresentifthedeviceiscapableofbeingaSlaveIProxy. [ChangeFootnotestoTable12F13,p.196] Table12F13.PropertiesoftheDeviceObjectType PropertyIdentifier PropertyDatatype ConformanceCode Slave_Proxy_Enable BACnetARRAY[N]ofBOOLEAN O 10 Manual_Slave_Address_Binding ListofBACnetAddressBinding O 10,12 Auto_Slave_Discovery BACnetARRAY[N]ofBOOLEAN O 10,11 Slave_Address_Binding ListofBACnetAddressBinding O 10,12 10Thispropertyshallbepresentis)required)if,)and)shall)be)present)only)if,andwritableifthedeviceis capableofbeingaslaveiproxydevice. 11Thispropertyshallbepresentifis)required)if,)and)shall)be)present)only)if,thedeviceiscapableofbeing aslaveiproxydevicethatimplementsautomaticdiscoveryofslaves. 12ThispropertyshallbepresentifthedeviceiscapableofbeingaSlaveIProxydeviceThis)property)shall) be)writable)if)the)device)is)directly)connected)to)an)ms/tp)network. [ChangeClause12.11.40,p.201] 12.11.40Slave_Proxy_Enable Thisproperty,oftypeBACnetArrayofBOOLEAN,isanindicationwhether(TRUE)ornot(FALSE)the device will perform SlaveIProxy functions for each of the MS/TP ports represented by each array element.thispropertyshallbepresentifthedeviceiscapableofperformingthefunctionsofaslavei Proxydevice.Thevalueofthispropertyshallberetainedoveradevicereset. [ChangeClause12.11.41,p.201] 12.11.41Manual_Slave_Address_Binding This property, of type List of BACnetAddressBinding, describes the manually configured set of slave devicesforwhichthisdeviceisactingasaslaveproxyasdescribedinclause 16.10.2.Thisproperty shallbepresentifthedeviceiscapableofperformingthefunctionsofaslaveiproxydevice.ifpresent, andthedeviceisdirectlyattachedtoanms/tpnetwork,thenthispropertyshallbewritable. Thispropertyisusedtomanuallyconfigureasetofslavedevicesforwhichthisdevicewillbeaproxy. ThispropertyallowsaSlaveProxythatdoesnotsupportautomaticslavediscoverybeconfiguredwitha setofslavesforwhichthisdevicewillbeaproxy.italsoallowsaslaveiproxydevicetobeaproxyfor Slavedevicesthatdonotsupportthespecialobjectinstanceof4194303asdescribedinClause12.The valueofthispropertyshallberetainedoveradevicereset.whenenabled,theslaveiproxydeviceshall periodicallycheckeachdevicethatisinthislist,andnotintheslave_address_bindinglist,byreading the device's Protocol_Services_Supported property from the device's Device object using the ReadPropertyservice.IfthedevicerespondsandindicatesthatitdoesnotexecutetheWhoIIsservice,it shallbeaddedtotheslave_address_bindingproperty.theperiodatwhichthedevicesarecheckedisa localmatter. [ChangeClause12.11.42,p.202] 17

12.11.42Auto_Slave_Discovery Thisproperty,oftypeBACnetArrayofBOOLEAN,isanindicationwhether(TRUE)ornot(FALSE)the device will perform automatic slave detection functions for each of the MS/TP ports represented by eacharrayelement.thispropertyshallbepresentifthedeviceiscapableofperformingthefunctionsof aslaveiproxydevice.thevalueofthispropertyshallberetainedoveradevicereset. Slave detection shall be accomplished by the proxy device using ReadProperty services to read, at a minimum,thedeviceobject'sprotocol_services_supportedpropertyforeachmacaddressoneachport whereauto_slave_discoveryforthatportistrue.thereadpropertyserviceshallusethespecialobject instanceof4194303asdescribedinclause12.ifthedeviceisfoundtosupportexecutionofthewhoiis service,itisignored;otherwise,thedeviceshallbeaddedtotheslave_address_bindingproperty.the slave detection algorithm shall be repeated periodically. The period at which it is repeated is a local matter. [ChangeClause12.11.43,p.202] 12.11.43Slave_Address_Binding Thisproperty,oftypeListofBACnetAddressBinding,describesthesetofslavedevicesforwhichthis deviceisactingasaslaveiproxyasdescribedinclause 16.10.2.Thispropertyshallbepresentifthe device is capable of performing the functions of a SlaveIProxy device. If present, and the device is directlyattachedtoanms/tpnetwork,thenthispropertyshallbewritable. ThesetofdevicesdescribedbytheSlave_Address_Bindingpropertyconsistsofthosedevicesdescribed in the Manual_Slave_Address_Binding and those devices that are automatically discovered. When enabled,theslaveiproxydeviceshallperiodicallycheckeachdeviceinthislistbyreadingthedevice's Protocol_Services_Supportedpropertyfromthedevice'sDeviceobjectusingtheReadPropertyservice. Ifthedevicefailstorespond,orindicatesthatitexecutesWhoIIs,itshallberemovedfromthelist.The periodatwhichthedevicesarecheckedisalocalmatter. 18

135F2010af#12.ClarifywhentheRestartRelatedPropertiesareAllowedtobePresent. Rationale Clarify that Last_Restart_Reason, Time_Of_Device_Restart, Restart_Notification_Recipients shall only be presentifthedevicesupportsexecutionofsubscribecovorsubscribecovproperty. [ChangeTable12F13,p.196] Table12F13.PropertiesoftheDeviceObjectType PropertyIdentifier PropertyDatatype ConformanceCode Last_Restart_Reason BACnetRestartReason O 13 ) Time_Of_Device_Restart BACnetTimeStamp O 13 Restart_Notification_Recipients ListofBACnetRecipient O 13,x ) 13Thesepropertiesarerequiredifthedevicesupportsexecution)of)therestartprocedureasdescribedin Clause19.3. x)this)property)is)required)if,)and)shall)be)present)only)if,)the)device)supports)execution)of)the)restart) procedure)as)described)in)clause)19.3.) [ChangeClauses12.11.44,..12.11.46,p.202] 12.11.44Last_Restart_Reason This property, of type BACnetRestartReason, indicates the reason for the last device restart. This propertyshallbepresentifthedevicesupportsthebacnetrestartprocedureasdescribedinclause 19.3.See)clause)19.3)for)a)description)of)the)restart)procedure.)Thepossiblevaluesforthispropertyare: UNKNOWN COLDSTART WARMSTART DETECTED_POWER_LOST DETECTED_POWERED_OFF HARDWARE_WATCHDOG SOFTWARE_WATCHDOG SUSPENDED 12.11.45Time_Of_Device_Restart Thedevicecannotdeterminethecauseofthelastreset. AReinitializeDevicerequestwasreceivedwitha'ReinitializedStateof Device' of COLDSTART or the device was made to COLDSTART by someothermeans. AReinitializeDevicerequestwasreceivedwitha'ReinitializedStateof Device'ofWARMSTARTorthedevicewasmadetoWARMSTARTby someothermeans. Thedevicedetectedthatincomingpowerwaslost. Thedevicedetectedthatitspowerswitchwasturnedoff. Thehardwarewatchdogtimerresetthedevice. Thesoftwarewatchdogtimerresetthedevice. Thedevicewassuspended.Howthedevicewassuspendedorwhatit meanstobesuspendedisalocalmatter. This property, of type BACnetTimeStamp, is the time at which the device was last restarted. This propertyshallbepresentifthedevicesupportsthebacnetrestartprocedureasdescribedinclause 19.3.)See)Clause)19.3)for)a)description)of)the)restart)procedure. 12.11.46Restart_Notification_Recipients TheRestart_Notification_Recipientspropertyisusedtocontroltherestrictionsonwhichdevices,ifany, are to be notified when a restart occurs. The value of this property shall be a list of zero or more BACnetRecipients. If the list is of length zero, a device is prohibited from sending a device restart notification.thedefaultvalueofthepropertyshallbeasingleentryrepresentingabroadcastonthe localnetwork.ifthepropertyisnotwritable,thenitshallcontainthedefaultvalue.ifthelistisoflength oneormore,adeviceshallsendarestartnotification,butonlytothedevicesoraddresseslisted.this propertyshallbepresentifandonlyifthedevicesupportsthebacnetrestartprocedureasdescribedin Clause19.3.See)Clause)19.3)for)a)description)of)the)restart)procedure. 19

135F2010af#13.ClarifywhentheLog_DeviceObjectPropertyPropertyisAllowedtobePresent. Rationale Clarify that Log_DeviceObjectProperty shall not be present if the Trend Log is monitoring a nonibacnet property. [ChangeTable12F29,p.272] Table12F29.PropertiesoftheTrendLogObjectType PropertyIdentifier PropertyDatatype ConformanceCode Start_Time BACnetDateTime O 1,2 Stop_Time BACnetDateTime O 1,2 Log_DeviceObjectProperty BACnetDeviceObjectPropertyReferen O 1x ) ce Log_Interval Unsigned O 1,3 x) This) property) is) required) if,) and) shall) be) present) only) if,) the) monitored) property) is) a) BACnet) property.$$ 20

135F2010af#14.ClarifywhentheClockAligningPropertiesareAllowedtobePresent. Rationale ClarifythatAlign_IntervalsandInterval_Offsetshallnotbepresentinlogobjectsthatdonotsupportclock aligning. [ChangeFootnote5toTable12F29,TrendLogpropertytable,p.272] 5Thesepropertiesarerequiredtobepresentif,)and)shall)be)present)only)if,theobjectsupportsclockI alignedlogging. [ChangeFootnote3toTable12F35,TrendLogMultiplepropertytable,p.305] 3Thesepropertiesarerequiredtobepresentif,)and)shall)be)present)only)if,theobjectsupportsclockI alignedlogging. [ChangeClause12.25.28,p.277] 12.25.28Align_Intervals This optional property, of type BOOLEAN, specifies whether (TRUE) or not (FALSE) clockialigned periodicloggingisenabled.ifclockialignedperiodicloggingisenabledandthevalueoflog_intervalisa factorof(thatis,divideswithoutremainder)asecond,minute,hourorday,thenthebeginningofthe periodspecifiedforloggingshallbealignedtothesecond,minute,hourorday,respectively. ThispropertyisrequirediftheobjectsupportsclockIalignedlogging.Thispropertyhasnoeffectonthe behaviorofthetrendlogobjectifthelogging_typepropertyhasavalueotherthanpolled. [ChangeClause12.25.29,p.277] 12.25.29Interval_Offset This optional property, of type Unsigned, specifies the offset in hundredths of seconds from the beginningoftheperiodspecifiedforlogginguntiltheactualacquisitionofalogrecordbegins.theoffset usedshallbethevalueofinterval_offsetmodulothevalueoflog_interval;i.e.,ifinterval_offsethasthe value 31 and Log_Interval is 30, the offset used shall be 1. Interval_Offset shall have no effect if Align_IntervalsisFALSE. ThispropertyisrequirediftheobjectsupportsclockIalignedlogging. [ChangeClause12.30.14,p.308] 12.30.14Align_Intervals This optional property, of type BOOLEAN, specifies whether (TRUE) or not (FALSE) clockialigned periodicloggingisenabled.ifclockialignedperiodicloggingisenabledandthevalueoflog_intervalisa factorof(thatis,divideswithoutremainder)asecond,minute,hourorday,thenthebeginningofthe periodspecifiedforloggingshallbealignedtothesecond,minute,hourorday,respectively. ThispropertyisrequirediftheobjectsupportsclockIalignedlogging.Thispropertyhasnoeffectonthe behaviorofthetrendlogmultipleobjectifthelogging_typepropertyhasavalueotherthanpolled. [ChangeClause12.30.15,p.308] 12.30.15Interval_Offset This optional property, of type Unsigned, specifies the offset in hundredths of seconds from the beginningoftheperiodspecifiedforlogginguntiltheactualacquisitionofalogrecordbegins.theoffset usedshallbethevalueofinterval_offsetmodulothevalueoflog_interval;i.e.,ifinterval_offsethasthe 21

value 31 and Log_Interval is 30, the offset used shall be 1. Interval_Offset shall have no effect if Align_Intervals=FALSE. ThispropertyisrequirediftheobjectsupportsclockIalignedlogging. 22

135F2010af#15.ClarifywhentheOccupancyCountingPropertiesareAllowedtobePresent. Rationale Clarify that Occupancy_Count, Occupancy_Count_Enable, and Adjust_Value shall not be present in Access Zoneobjectsthatdonotsupportoccupancycounting. [ChangeFootnote4toTable12F37,p.329] 4 These properties are required if,) and) shall) be) present) only) if, the object supports occupancy counting. [ChangeClause12.32.11,,p.331] 12.32.11Occupancy_Count Thisoptionalproperty,oftypeUnsigned,isusedtoindicatetheactualoccupancycountofazone.Ifthe valueoftheoccupancy_count_enablepropertyisfalse,thenthispropertyshallhaveavalueofzero. ThevalueoftheOccupancy_CountpropertymaybeadjustedbywritingtotheAdjust_Valueproperty. The Occupancy_Count propertyshallbewritablewhenout_of_service is TRUE. When Out_Of_Service becomesfalse,itisalocalmatterastowhatvaluethispropertyissetto. Ifoccupancycountingissupportedbythisobject,thenthispropertyshallbepresent. Thispropertyisrequiredifintrinsicreportingissupportedbythisobject. [ChangeClause12.32.12,p.332] 12.32.12Occupancy_Count_Enable Thisoptionalproperty,oftypeBOOLEAN,indicateswhetheroccupancycountingisenabled(TRUE)or not(false). If this property has a value of FALSE, then the Occupancy_State property shall have a value of DISABLED. When this property changes from FALSE to TRUE it is a local matter as to what value the Occupancy_Countpropertyissetto. Ifoccupancycountingissupportedbythisobject,thenthispropertyshallbepresent. Thispropertyisrequiredifintrinsicreportingissupportedbythisobject. [ChangeClause12.32.13,p.332] 12.32.13Adjust_Value Thisoptionalproperty,oftypeINTEGER,shalladjusttheOccupancy_Countpropertywhenwritten. Thefollowingseriesofoperationsshallbeperformedatomicallywhenthispropertyiswrittenandthe valueoftheoccupancy_count_enablepropertyistrue: (1) ThevaluewrittentoAdjust_ValueshallbestoredintheAdjust_Valueproperty. (2) If the value written is nonizero, then this value shall be added to the value of the Occupancy_Count property. If the value written is negative and the resulting value of the Occupancy_Countpropertywouldbelessthanzero,thentheOccupancy_Countpropertyshall besettozero.ifthevaluewritteniszero,thenthevalueoftheoccupancy_countpropertyshall besettozero. 23

WhenthispropertyiswrittenandthevalueoftheOccupancy_Count_EnablepropertyisFALSE,thenthe Adjust_Valuepropertyshallbesettozero. If Adjust_Value has never been written or the Occupancy_Count_Enable property is FALSE, then this propertyshallhaveavalueofzero. Ifoccupancycountingissupportedbythisobject,thenthispropertyshallbepresentandwritable. Thispropertyisrequiredifintrinsicreportingissupportedbythisobject. 24

135F2010af#16.AddtheAbilitytoConfigureEventMessageText. Rationale Inordertoallowtheinteroperableconfigurationofthemessagetextthatissentwithaneventnotification, theevent_message_texts_configpropertyisaddedtoallobjecttypesthatarecapableofeventreporting. Thechangesareappliedtoallobjectstypesdefinedinthestandardandalladdendathatsupportintrinsicor algorithmiceventreporting. [Addentrytoevery"Table12FX.Propertiesof..."forobjecttypesthatareallowedtosupportintrinsic reporting.] Table12FX.Propertiesof... PropertyIdentifier PropertyDatatype ConformanceCode ) ) ) Event_Message_Texts_Config) BACnetARRAY[3])of)CharacterString) O y ) y)these)properties)shall)be)present)only)if)the)object)supports)intrinsic)reporting.) [AddentrytoTable12F14,p.205] Table12F14.PropertiesoftheEventEnrollmentObjectType PropertyIdentifier PropertyDatatype ConformanceCode ) ) ) Event_Message_Texts_Config) BACnetARRAY[3])of)CharacterString) O) ) [AddnewClause12.X.Ytoallobjecttypesthatareallowedtosupportintrinsicoralgorithmicreporting.] 12.X.Y Event_Message_Texts_Config Thisproperty,oftypeBACnetARRAY[3]ofCharacterString,containsthecharacterstringswhicharethe basisforthe'messagetext'parameterfortheeventnotificationsoftoioffnormal,toifault,and TOINORMAL events, respectively, generated by this object. The character strings may optionally containproprietarytextsubstitutioncodestoincorporatedynamicinformationsuchasdateandtime orotherinformation. [ChangeClause21,p615] BACnetPropertyIdentifier::=ENUMERATED{ eventimessageitexts (351), ) eventwmessagewtextswconfig)) ) (352),) IIseeeventImessageItexts (351), ) WW)see)eventWmessageWtextsWconfig) (352),)... } 25