AIA BIM and Digital Data - 2013

Guide, Instructions and Commentary
to the 2013 AIA Digital Practice Documents

AIA Document E2032013, Building Information Modeling and Digital Data Exhibit
AIA Document G2012013, Project Digital Data Protocol Form
AIA Document G2022013, Project Building Information Modeling Protocol Form
INTRODUCTION
PurposeofthisGuide,InstructionsandCommentary
StructuralRevisionstoAIAsDigitalPracticeDocuments
RevisionstothisGuide
HowtousethisGuide
GUIDANCE
AIADocumentE2032013,BuildingInformationModelingandDigitalDataExhibit
Article1GeneralProvisions
Article2TransmissionandOwnershipofDigitalData
Article3DigitalDataProtocols
Article4BuildingInformationModelingProtocols
Article5OtherTermsandConditions
AIADocumentG2012013,ProjectDigitalDataProtocolForm
Article1GeneralProvisionsRegardingUseofDigitalData
Article2DigitalDataManagementProtocols
Article3TransmissionandUseofDigitalData
AIADocumentG2022013,ProjectBuildingInformationModelingProtocolForm
Article2LevelofDevelopment
Article3ModelElements
RESOURCES
INTRODUCTION
PurposeofthisGuide,InstructionsandCommentary
Astheuseofbuildinginformationmodeling(BIM)andothertypesofDigitalDatahascontinuedtoevolve
inthedesignandconstructionindustryinrecentyears,theindustryhasbeguntoaskpracticalquestions
regardinghowtheseconceptsandtoolsshouldbeimplemented.Inanefforttoprovideguidance,the
AmericanInstituteofArchitects(AIA)publisheditsfirstDigitalDatadocuments,AIADocuments
E2012007,DigitalDataProtocolExhibit,andC1062007,DigitalDataLicensingAgreement,inOctober
2007.E2012007isanexhibittoanagreementthatallowsthepartiestoestablishtheproceduresthey
agreetofollowwithrespecttothetransmissionorexchangeofDigitalData,includinginstrumentsof
service.UnlikeE2012007,C1062007isnotanexhibitandisinsteadastandaloneagreementbetween
Guide, Instructions and Commentary to the 2013 AIA Digital Practice Documents. Copyright 2013 by The American Institute of Architects.
All rights reserved.
Rev. 052213
twopartieswhootherwisehavenoexistinglicensingagreementfortheuseandtransmissionofDigital
Data,includingInstrumentsofService.1FollowingthereleaseofE2012007,theAIAaddressedthe
increasinguseofBIMwiththepublicationofAIADocumentE2022008,BuildingInformationProtocol
Exhibit.LikeE2012007,E2022008isanexhibitthatisattachedtothepartiesagreement.E2022008is
usedtoestablishtherequirementsformodelcontentatfiveprogressivelevelsofdevelopment,andthe
authorizedusesofthemodelcontentateachlevelofdevelopment.E2022008alsoassignsauthorshipof
eachmodelelementbyprojectphase,definestheextenttowhichmodelusersmayrelyonmodelcontent,
clarifiesmodelownership,setsforthBIMstandardsandfileformats,andprovidesthescopeof
responsibilityformodelmanagementfromthebeginningtotheendoftheproject.
DigitalpracticeandtheuseofBIMarerapidlyevolvingareasoftheindustry.TypicallyAIAContract
Documentsarerevisedonatenyearcycle.However,giventhepaceatwhichuseofDigitalDatainthe
constructionindustryischanging,atenyearreviewcyclefortheDigitalPracticedocumentswouldhave
beentoolong,tomaintainameaningfultoolforindustryparticipants.Accordingly,in2011theAIA
undertooktoagainevaluatecontinueddevelopmentandadoptionofdigitalpracticeandBIM.Asaresultof
thisevaluation,theAIAcreatedanupdatedandreconfigurednewsetofDigitalPracticedocumentsthat
includesAIADocumentE2032013,BuildingInformationModelingandDigitalDataExhibit;AIA
DocumentG2012013,ProjectDigitalDataProtocolForm;andAIADocumentG2022013,Project
BuildingInformationModelingProtocolForm.ThisGuide,InstructionsandCommentarytothe2013AIA
DigitalPracticeDocuments(theGuide)isintendedtoprovideanindepthlookatthissetofDigital
Practicedocuments,andtoprovideguidanceonhowthedocumentsareintendedtobeused.
StructuralRevisionstoAIAsDigitalPracticeDocuments
TheupdatednewsetofDigitalPracticedocumentsincludesasubstantialamountofcontentfrom
E2012007andE2022008.Thecontent,however,hasbeenrestructured,editedandexpandedupon.This
processhasalsoresultedinasetofdocumentsthatarestructurallydifferentfromtheirpredecessors.
E2032013isanexhibitthatisintendedtobeattachedtoanagreementatthetimetheagreementis
executed.E2032013consistsofgeneralprovisions(i.e.,purposestatement,definitions)thatwouldnot
normallychangeastheprojectproceeds.Italsoprovidesaplaceforthepartiestoidentifywhichparty,ifany,
willbechargedwithDigitalDatamanagementormodelmanagementresponsibilities.Accordingly,tothe
extenttheseresponsibilitiesaffectthescopeofservices;theyareincludedasapartoftheinitialagreement.
TheprimarypurposeofE2032013istoinitiate,attheoutsetofaproject,asubstantivediscussionabout
theextenttowhichDigitalDataandBIMwillbeutilized,andhowDigitalDataandmodelscanbeusedand
reliedupon.Onceageneralunderstandingisreached,theprojectparticipantsuseE2032013todocument
theagreeduponexpectationsregardingscopeandanticipatedAuthorizedUsesofDigitalDataandBIM.
ThepremiseisthattherewillbeasingleversionofE2032013negotiatedforaprojectandthatversionwill
beincludedasanexhibittoeachcontractontheproject.Accordingly,thetitlepageforE2032013does
notreferenceaspecificagreement.TheagreementstowhichE2032013ismadeanexhibitwillincludea
referencetothedatedversionoftheincorporatedE2032013.Forexample,inB1012007,theOwnerand
ArchitectwouldlistandincorporateE2032013inArticle13.Throughthisprocess,thevariousProject
ParticipantsbegintheProjectwithacommonunderstandingofhowDigitalDataandBIMwill,generally,be
utilizedontheproject.TotheextentProjectParticipantsareutilizingAIAagreementsthatreference
WhileC1062007wasupdatedaspartoftheAIAs2013revisionstoitsDigitalPracticedocuments,theonlysubstantivechangeto
thedocumentwastoaddafillpointallowingthePartiestoclearlyidentifytheDigitalDatasubjecttothelicensegrantedinthe
agreement.Therefore,C1062013isnotdiscussedindetailinthisGuide.
E2012007orE2022008,itwillbenecessarytodeleteorotherwisemodifythosereferences.E2032013,
G2012013andG2022013aresubstitutesfor,andreplaceE201andE202.
HavingsetthebaselineregardingDigitalDataandBIMexpectations,E2032013thenrequirestheProject
Participants,[a]ssoonaspracticalafterexecutionoftheagreement,tomeetanddecideuponthenecessary
andrelevantprotocolsforthedevelopmentanduseofDigitalDataandBIM.Onceagreedto,theprotocols
arememorializedinG2012013andG2022013.AIADocumentG2012013isusedtodocumenttheagreed
uponDigitalDataprotocolswhileG2022013isusedtodocumenttheModelingprotocols.G2012013and
G2022013arenotexpresslyincorporatedintotheprojectparticipantsagreements,however;thetermsof
theE2032013(attachedtoeachProjectParticipantsagreement)requireeachpartytofollowtheprotocols
onceestablished,andasupdatedfromtimetotime.
TheseparationoftheexhibitandprotocolsisadeparturefromtheapproachtakeninE2012007andE202
2008,inwhichthedetailedprotocolsarepartoftheexhibit.Thereareanumberofbenefitstothisnew
approach.E203nolongerrequirestheProjectParticipantstonegotiateandfinalizethedetailedDigitalData
andModelingprotocolsatthesametimetheymaketheirinitialdecisionsregardingwhetherandhowtouse
DigitalDataandBIM.Byseparatingtheprotocolsfromtheexhibit,theProjectParticipantsareabletofirst
discussanddocumenttheirgeneralexpectationsregardinguseofDigitalDataandBIMontheProject.
Subsequently,theprotocolsarenegotiatedandagreeduponatatimethatmakesthemostsenseforthe
Project(e.g.,afterthekeydesignandconstructioncontractsarenegotiated,andafteralltherelevantProject
Participantsareonboard).Further,becausetheprotocolssetforthinG2012013andG2022013arenota
partoftheunderlyingagreement,theycanbemodifiedandadjustedasnecessarywithouttheneedto
separatelyandformallyamendeachpartysagreement.
WhileE2032013requirestheProjectParticipantstofollowthemostrecentprotocols,enforcementofthat
obligationmayultimatelydependontheabilityofaProjectParticipanttoprovethattheotherProject
Participantsagreedtotheprotocolsseekingtobeenforced.Accordingly,inutilizingG2012013andG202
2013,theProjectParticipantsshoulddevelopanacceptableprocesstodocumentthereceiptof,and
agreementto,eachversionoftheprotocolsbyeachProjectParticipant.Suchaprocesswillprotectagainsta
ProjectParticipantultimatelyclaimingthatitneversaw,oragreedto,thelatestversionoftherelevant
protocolsandthereforeisnotboundbythem.ThereareavarietyofwaystheProjectParticipantsmight
documentreceiptandagreement.(SeediscussionatE203,Sections3.2.2and4.5.3below.)
RevisionstothisGuide
ThisGuidenotonlyallowstheAIAtoprovideguidanceonhowtousetheexistingdocuments,italsoprovides
theabilitytoaddressnewtopicsastheydevelop.ThisGuidewillbeupdatedasnecessarytoreflectchanging
industrystandards.Therevisiondateofthisdocumentisincludedinthelowerrighthandcornerofthe
document.PleasecheckbackperiodicallytoconfirmthatyouhavethelatestversionofthisGuide.
HowtoUsethisGuide
ThefollowingisasectionbysectionanalysisanddiscussionofAIADocumentsE2032013,G2012013and
G2022013.Foreachsectionofthedocuments,theGuidereproducesthetextoftheunderlyingdocument,
whichisdirectlyfollowedbyadetaileddiscussion.Inadditiontothegeneraldiscussion,theGuidealso
providessuggestedalternatelanguageforcertainsectionstoaddressvariousprojectspecificneeds.The
suggestedlanguageisindentedfromthebodytextoftheGuide.
Togotospecificsectionsofinterestinthisguide,clickBookmarklinksortopicsintheTableofContents.To
viewbookmarks,clicktheBookmarkbutton
onthelefthandNavigationpane.
(backtoTableofContents)
GUIDANCE
Guidance,InstructionsandCommentaryto
E2032013istheanchoroftheAIAsnewsetofDigitalPracticedocumentsandsetsthestageforthe
developmentofDigitalDataandModelingprotocolsfortheProject.Itiscomprisedoffivearticles:
Article1 GeneralProvisions
Article2 TransmissionandOwnershipofDigitalData
Article3 DigitalDataProtocols
Article4 BuildingInformationModelingProtocols
Article5 OtherTermsandConditions
Article1describestheoverallpurpose,containskeyprovisionsrelatedtotheflowdownofobligationsand
establishesasetofstandarddefinitionsfortermssuchasDigitalData,LevelofDevelopment,AuthorizedUse,
Party,ProjectParticipant,etc.thatwillbeusedthroughouttheDigitalPracticedocuments.Termsthatare
definedinE203Article1arecapitalizedthroughoutthisGuide.
Article2addressestopicsrelatedtothetransmissionofDigitalData,includingtreatmentofconfidential
DigitalData.
Article3addressesthePartiesintentiontoutilizeDigitalData,andtosubsequentlyestablishprotocols
regardingitstransmissionanduse.Ifnecessary,inArticle3thePartieswillalsoidentifywhowillbecharged
withtheresponsibilityofmanagingacentralizedelectronicdocumentmanagementsystemfortheProject.
Article4addressesthePartiesintentionsforBIMutilizationontheProjectand,ifnecessary,the
subsequentcreationofapplicableprotocols.Article4alsoprovidesaplacetoidentifywhowillbecharged
withModelmanagementresponsibilities.
Asstatedabove,theactualprotocolsrequiredtobeestablishedpursuanttobothArticle3andArticle4are
notsetforthinE2032013instead,theprotocolsforDigitalDataaredescribedinG2012013,andthe
protocolsforBIMinG2022013.
Article5providesaspaceforthePartiestoindicateanyotherprovisionsthatwillapplytotheiruseof
DigitalDataorBIMontheProject.
E2032013Section1.1
1.1ThisExhibitprovidesfortheestablishmentofprotocolsforthedevelopment,use,transmission,and
exchangeofDigitalDatafortheProject.IfBuildingInformationModelingwillbeutilized,thisExhibitalso
providesfortheestablishmentoftheprotocolsnecessarytoimplementtheuseofBuildingInformation
ModelingontheProject,includingprotocolsthatestablishtheexpectedLevelofDevelopmentforModel
ElementsatvariousmilestonesoftheProject,andtheassociatedAuthorizedUsesoftheBuilding
InformationModels.
Rev. 052213
Guide,InstructionsandCommentaryto
Article1ofE2032013beginswithaseriesofsectionsexplainingthegeneralpurposeofthedocument,
howthetermsoftheexhibitrelatetotheunderlyingAgreementintowhichitisincorporated,howitis
applicableacrosstheProject,andthepotentialimpactsubsequentprotocolsmayhaveontheParties
scopesofservices,scopesofwork,andrelatedcompensation.Section1.1establishestheintentand
purposeofE2032013.
E2032013Section1.2
1.2ThePartiesagreetoincorporatethisExhibitintotheiragreementswithanyotherProjectParticipants
thatmaydevelopormakeuseofDigitalDataontheProject.Priortotransmittingorallowingaccessto
DigitalData,aPartymayrequireanyProjectParticipanttoprovidereasonableevidencethatithas
incorporatedthisExhibitintoitsagreementfortheProject,andagreedtothemostrecentProjectspecific
versionsofAIADocumentG2012013,ProjectDigitalDataProtocolFormandAIADocumentG202
2013,BuildingInformationModelingProtocolForm.
AprimarypurposeoftheseDigitalPracticedocumentsistoencouragetheusefulsharingofDigitalData,by
providingtheProjectParticipantsawaytoestablishtheframeworkandexpectationsregardingthecreation,
sharinganduseofDigitalDataontheProject.DigitalDataisdefinedinE2032013toincludeBuilding
InformationModeling.Tobeeffective,thesubsequentlyagreeduponprotocolsandstandardsmustbe
recognizedbyalltheProjectParticipantsthatwillcreateandusetheDigitalData.Accordingly,theParties
agreethattheywillincorporatetheExhibitintoallotheragreementsontheProject.(G2012013Section1.1
containsafillpointtolistoftheProjectParticipantsthathaveattachedtheExhibittotheiragreement.)
Section1.2requirestheParties(inallinstancesthetermPartiesreferstothepartiestotheunderlying
AgreementtowhichE2032013isattached)toincorporateE2032013intoeachofthePartysother
agreementsfortheProject.Forexample,ifanownerandarchitectnegotiateandattachanE2032013to
AIADocumentB1012007,StandardFormAgreementbetweenOwnerandArchitect,thearchitectwould
berequiredtoincorporatethesameE2032013intoeachofitsconsultantagreements.Similarly,the
OwnerwouldberequiredtoincorporateE2032013intoitsagreementwiththeContractor,whowouldin
turnberequiredtoincorporateE2032013intoitsSubcontractoragreements.Throughthisflowdown
process,E2032013permeatestheentireProject.
TheintentisthatE2032013willbeincorporatedintotheunderlyingAgreementwhentheAgreementis
executed.InB1012007,E2032013canbeincorporatedbyreferencingitinSection13.2.2ofArticle13,
ScopeoftheAgreement.Currently,B1012007includesareferencetoE2012007(notethatB1012007
doesnotreferenceE2022008becauseE2022008waspublishedafterB1012007).AsE2032013is
intendedtoreplaceE2012007(andE2022008),theexistinglanguagecanbedeletedandreplacedwith
languagereferencingE2032013bynameanddate.Anexampleofsuchlanguagewouldbeasfollows:
13.2.2AIADocumentE2032013,BuildingInformationModelingandDigitalData
Exhibit,dated________.
TheprocessforincorporatingE2032013intoAIAContractDocumentsstandardformOwner/Contractor
agreementswouldbesimilar.InAIADocumentA1012007,StandardFormAgreementbetweenOwner
andContractorwherethebasisofpaymentisaStipulateSum,E2032013canbeincorporatedby
referenceinSection9.1.7.1.AsisthecaseinB1012007,thecurrentreferencetoE2012007shouldbe
deletedandreplacedwithlanguagereferencingE2032013bynameanddate.Thesuggestedlanguage
aboveforB1012007wouldbesufficientinA1012007aswell.
ItisalsopossiblethatthePartieswouldneedtoincorporateE2032013aftertheinitialexecutionofthe
Agreement.Inthatcase,thePartieswouldexecuteanamendmenttotheAgreement.Foramendmentsto
Owner/Architectagreements,theAIApublishesAIADocumentG8022007,Amendmenttothe
ProfessionalServicesAgreement.InthespaceprovidedinG8022007belowthewordsAsfollows,the
PartiescaninsertlanguageindicatingthattheAgreementisbeingamendedtoincorporateE2032013.An
exampleofsuchlanguagewouldbeasfollows:
TheAgreementisamendedtoincorporate AIADocumentE2032013,Building
InformationModelingandDigitalDataExhibit,dated________.
IftheincorporationofE2032013willresultinanadjustmenttocompensationorcontracttime,G802
2007allowsthePartiestoindicateanyadjustments.
Foramendmentstoconsultantagreements,theAIApublishesG8032007,AmendmenttotheConsultant
ServicesAgreement.G8032007issetupsimilarlytoG8022007andthesuggestionsabove,andexample
language,wouldapplytoG8032007aswell.
IfthePartiesneedtoamendanOwner/Contractoragreement,thePartiescanuseAIADocumentG701
2001,ChangeOrder.InthespaceprovidedbelowthephraseTheContractischangedasfollowsthe
PartiescaninsertlanguageindicatingthattheContractisbeingamendedtoincorporateE2032013.An
exampleofsuchlanguagewouldbeasfollows:
TheContractisamendedtoincorporateAIADocumentE2032013,BuildingInformation
ModelingandDigitalDataExhibit,dated________.
Similarly,iftheincorporationofE2032013willresultinanadjustmenttocompensationorcontracttime,
G7012001allowsthePartiestoindicateanyadjustments.
ItshouldbenotedthatthegeneralflowdownprovisionsofsomeoftheAIAContractDocuments,including
theAIAArchitect/ConsultantAgreement(C4012007)andtheContractor/SubcontractorAgreement
(A4012007)mayarguablyalreadypassalongtheobligationsoftheE2032013iftheexhibitis
incorporatedintotherelevantPrimeAgreementpriortothetimethesubagreementsareexecuted.
Relyingonsuchaflowdown,however,ispossiblyambiguous.However,includinglanguageinthe
AgreementexplicitlyincorporatingE2032013islikelytheclearestwaytoassurethatthedocumentis
incorporatedindownstreamagreements.Giventherelativenoveltyofthesedocuments,andthevarious
nuancespresentedonaprojectbyprojectbasis,usersmaywishtoconsultwithanattorneytodetermine
thebestwaytoincorporateE2032013intotheiragreements.
ItmayalsobethecasethataModelwillonlybesharedamongsttheProjectParticipantsononesideofa
Project(e.g.,onlythedesignteamwillbesharingtheModel).E2032013canbeutilizedinsuchascenario
andthereareafewoptionsavailabletouserstoachievethisresult.Someoptionsareoutlinedbelowinthe
discussionpertainingtoE2032013Section4.1.AnothersolutionwouldbetoonlyincorporateE2032013
intotheArchitect/ConsultantandConsultant/Subconsultantagreements.Accordingly,E2032013andthe
relatedprotocolformscouldbecompleted,buttheywouldonlyapplytothedesignteam.Toachievethis
result,however,thisSection1.2wouldneedtobemodified.Ascurrentlydrafted,ifE2032013were
attachedtotheArchitect/Consultantagreement,theArchitectwouldbeobligatedtoincorporateE203
2013intoitsagreementwiththeOwner,whichwouldtriggertheOwnersobligationtoincorporateE203
2013intoitsagreementwiththeContractor.Accordingly,Section1.2wouldneedtoclarifythatE2032013
isnottobeincorporatedintheArchitect/Owneragreement,butthattheArchitectandConsultantwill
incorporateE2032013intheirdownstreamagreementsonly.
E2032013Section1.2.1
1.2.1ThePartiesagreethateachoftheProjectParticipantsutilizingDigitalDataontheProjectisan
intendedthirdpartybeneficiaryoftheSection1.2obligationtoincorporatethisExhibitintoagreements
withotherProjectParticipants,andanyrightsanddefensesassociatedwiththeenforcementofthat
obligation.ThisExhibitdoesnotcreateanythirdpartybeneficiaryrightsotherthanthoseexpressly
identifiedinthisSection1.2.1.
ThissectionisintendedtoprotectthePartiesinsituationswheresomeProjectParticipants,withwhomthe
Partiesdonothaveadirectcontractualrelationship,failtoincorporatetheexhibitintotheiragreements
withconsultantsorcontractors(pleaseseethediscussionbelowrelatedtoE2032013Section1.4.12fora
discussionofthedifferenceindefinitionsforthetermsPartiesandProjectParticipants).Asnoted
above,itisE2032013thatcreatesthecontractualobligationstofollowtheagreeduponDigitalDataand
Modelingprotocols.Therefore,itisnecessarythatthetermsofE2032013beapplicabletoalltherelevant
ProjectParticipantsthroughoutthenetworkofagreementsontheProject.IfaPartyfailstoincorporatethe
Exhibit,asrequiredinSection1.2,intoanyagreementwithaconsultantorcontractor,thatconsultantor
contractormaynotbeobligatedtocomplywithdevelopedprotocols.Therefore,theprotectionsthatthe
protocolsprovideupstream(restrictionsonAuthorizedUses)maybelost.
Toillustratetheconcernthatisbeingaddressed,considerthefollowingexample.IftheOwnerand
ArchitectincorporateE2032013intotheirAgreement,viaSection1.2,theybothagreetoincorporatethe
E2032013intotheirdownstreamagreementswithotherProjectParticipants.IftheOwner,however,fails
toincorporateE2032013intoitsagreementwiththeContractor,theOwnerhasbreachedacontractual
dutytotheArchitectandwouldberesponsibletotheArchitectforresultingdamages.So,forexample,if
thecontractor,unawareofrestrictionscontainedintheprotocols,usedsomeportionoftheDigitalData
suppliedbytheArchitectforapurposenototherwisesanctionedintheprotocols,andsubsequently
broughtaclaimagainsttheArchitectfordamagesarisingfromrelianceontheDigitalDatatheArchitect
provided,theArchitectwouldhaveaclaimagainsttheOwnerforitsfailuretoincorporateE2032013.
Accordingly,theArchitectreceivessomelevelofprotectiontotheextentitcanshowsomedamageasa
resultoftheOwnersbreachofthisprovision.
Alternatively,considerascenariowheretheOwnersatisfiesitsobligationsandincorporatesE2032013
intoitsAgreementwiththeContractorbuttheContractorfailstoincorporateE2032013intoits
agreementswithitssubcontractorsandconsultants.Thereafter,oneofthoseconsultantsor
subcontractorsreliesontheDigitalDatainamannerthatisinconsistentwiththeprotocols,resultingin
someinjurytoathirdparty.ThethirdpartythenbringsaclaimagainsttheArchitect.
Inthisinstance,intheabsenceofSection1.2.1,theArchitectwouldlikelyhavenorecourseagainstthe
ContractorbasedontheContractorsfailuretosatisfytheSection1.2obligationtoincorporateE2032013
downstream,becausetheArchitecthasnocontractualrelationshipwiththeContractor.TheArchitects
contractualrelationshipiswiththeOwner,whosatisfieditsobligationbyincorporatingE2032013intoits
AgreementwiththeContractor.
However,Section1.2.1wascreatedtogivealltheProjectParticipantstheabilitytoenforcetheobligations
underSection1.2againstalltheotherProjectParticipants.Intheexampleabove,theArchitect,asathird
partybeneficiary,wouldthereforehavethesameprotectionagainsttheContractor,forcontractualbreach
ofSection1.2,asitdoesagainsttheOwner.TheArchitectmightthenbringaclaimforbreachofcontract
againsttheContractor,andseektorecoveranyamountspaidonthethirdpartyclaimasdamagesarising
fromtheContractorsbreach.
AnotheroptiontoprotectagainstfailureofdownstreamincorporationofE2032013wouldbetoutilize
somekindofabroadindemnificationlanguage.Anexampleofsuchlanguagewouldbeasfollows:
1.2.1IfaPartyfailstoincorporatethisExhibitintoitsagreementswithanyotherProject
ParticipantsthatmaydevelopormakeuseofDigitalDataforthisProject,thatParty
agreestoindemnifyandholdharmlesstheotherProjectParticipantsandtheir
contractors,consultants,agentsandemployees,tothefullestextentpermittedbylaw,
fromandagainstclaims,damages,losses,andexpenses,includingbutnotlimitedto
attorneysfees,arisingoutoforresultingfromsuchProjectParticipantsuseofDigital
DatainconsistentwiththetermsofthisExhibit.
Anyindemnificationlanguageincluded,however,shouldbereviewedcloselywithlegalandinsurance
counselasindemnificationprovisionsarenotoriouslydifficulttoenforce,andinsomecircumstancesmay
createanuninsurableobligation.Inmanyjurisdictions,antiindemnificationstatuteslimitthevalidityand
enforceabilityofindemnificationprovisionsincontracts.Thesuggestedlanguagecontainsan
indemnificationunderwhichtheindemnitorsobligationcoverstheindemniteeslossestotheextent
causedbytheuseofDigitalData,inconsistentwiththetermsoftheexhibit,byanyoftheindemnitors
consultantsorcontractorsthatdonothavetheE2032013attachedtotheiragreement.Assuch,the
indemniteesobligationsmaybetriggeredbyanactthatdoesnototherwiseconstitutenegligenceontheir
part.Accordingly,itisunclearwhateffect,ifany,antiindemnificationsstatuesmayhaveonthe
enforceabilityofsuchanindemnity.Moreover,manyProjectParticipantshaveageneralaversiontobroad
indemnificationprovisionsandseektohavethemstrickenasamatterofroutine.
E2032013Section1.3
1.3AdjustmentstotheAgreement
1.3.1IfaPartybelievesthatprotocolsestablishedpursuanttoSections3.2or4.5,andmemorializedin
AIADocumentsG2012013andG2022013,willresultinachangeinthePartysscopeofworkorservices
warrantinganadjustmentincompensation,contractsum,scheduleorcontracttime,thePartyshallnotify
theotherParty.FailuretoprovidenoticeasrequiredinthisSection1.3shallresultinaPartyswaiverofany
claimsforadjustmentsincompensation,contractsum,scheduleorcontracttimeasaresultofthe
establishedprotocols.
1.3.2Uponsuchnotice,thePartiesshalldiscussandnegotiaterevisionstotheprotocolsordiscussand
negotiateanyadjustmentsincompensation,contractsum,scheduleorcontracttimeinaccordancewith
thetermsoftheAgreement.
1.3.3NoticerequiredunderthisSection1.3shallbeprovidedwithinthirtydaysofreceiptofthe
protocols,unlessotherwiseindicatedbelow:
(IfthePartiesrequireanoticeperiodotherthanthirtydaysofreceiptoftheprotocols,indicatethenotice
periodbelow.)
E2032013isintendedtobenegotiatedearlyintheProject,whenthePartiesexpectationsforuseofDigital
Dataaremostlikelynotfullyrefined.E2032013onlyrequiresidentificationofthegeneralanticipatedusesof
DigitalData,subjecttorefinementandgreaterdetailintheprotocolsthataresubsequentlyestablishedin
G2012013andG2022013.Accordingly,negotiatedfeesandcontractsumsthePartiesincludeinthe
AgreementarebasedonthegeneralstatementsofanticipateduseforDigitalDataandnotonthefully
developedprotocols.OncethePartiesbegintoidentifyspecificstandardsandtaskstobeperformedaspart
oftheprotocols,itisquiteconceivablethatthefullydevelopedrequirementsmayexceedinitialexpectations
regardingscope.Totheextentthespecificprotocolsandrequirementsrepresentachangetoinitial
expectations,adjustmentsincompensationand/orcontracttimeshouldbeconsideredandnegotiated.
IfaPartybelievesthattheprotocols,onceestablished,necessitateanadjustmentincompensation,
scheduleorcontracttime,thatPartymustprovidenoticetotheotherParty.Thestandardlanguagein
Section1.3statesthatsuchnoticemustbeprovidedwithin30daysofreceiptoftheprotocols;however,
thePartiesarefreetoinsertadifferentnoticeperiodtobetterfittheuniquecharacteristicsoftheirProject.
Oncenoticeisprovidedadjustmentstocompensation,scheduleorcontracttimearemadeinaccordance
withtheprovisionsoftheAgreement.Accordingly,ifE2032013isattachedtoanA1012007,theOwner
andContractorwouldfollowtheChangeOrderprovisionssetforthinA2012007.UnderB1012007,the
OwnerandArchitectwouldthenundertaketonegotiateanamendment.
WhiletheunderlyingcontractswillcontroltheprocessformakingadjustmentsbasedontheDigitalDataor
Modelingprotocols,usersmustbeawarethatE2032013addsaproceduralconditionprecedenttothe
processes.APartymustfirstprovidethenoticerequiredunderthisSection1.3.Failuretoprovidenotice
withinthetimeperiodsetforthinSection1.3willresultinthePartywaivingtheabilitytoseekany
adjustmentsrelatingtotheestablishedprotocols.
ThisissueofexpandedscopewillmostlikelycomeintoplaywhentheprotocolsissuedaspartofG201
2013andG2022013arecomparedtothePartiesoriginalstatementsinE2032013regardingthe
AnticipatedTypesofDigitalData(E2032013Section3.1)aswellasthoseregardingtheAnticipated
BuildingInformationModelingScope,AuthorizedUses,andAncillaryModelingActivities(E2032013
Sections4.2,4.3and4.4respectively).ThegoalincompletingE2032013shouldbetoavoidhavingto
renegotiatefeesoncetheprotocolsareestablished,becausesuchaneffortcandetrimentallyimpact
Projectrelationships.TotheextentuserscanprovideasmuchdetailandclarityaspossibleinE2032013,
withregardtotheanticipatedscopeofmodelinganduseofotherDigitalData,thegreaterlikelihood
subsequentdisputesoverfeescanbeavoided.
Asnoted,E2032013establishesthePartiesinitialexpectationsregardinguseofDigitalData,including
Modeling.WhenthoseprotocolsareestablishedandsetforthinG2012013andG2022013,however,
eachPartywouldbewellservedtoreviewtheprotocolscloselyinconjunctionwiththeoriginalstatements
inE2032013todetermineiftheyshouldpursueanadjustmentincompensationortime.
E2032013Section1.4
1.4Definitions
Definedtermsarecapitalizedthroughoutthedocument.Thedefinedtermsarecoordinatedforusewith
standardAIAContractDocuments.TotheextentE2032013isusedinconjunctionwithnonAIAagreements,
thedefinitionsmayneedtobemodifiedtocoordinatewiththetermsusedinsuchdocuments.
1.4.1BuildingInformationModel.ABuildingInformationModelisadigitalrepresentationoftheProject,
oraportionoftheProject,andisreferredtointhisExhibitastheModel,whichtermmaybeusedherein
todescribeaModelElement,asinglemodelormultiplemodelsusedintheaggregate,aswellasotherdata
setsidentifiedinAIADocumentG2022013,ProjectBuildingInformationModelingProtocolForm.
ThedefinitionofBuildingInformationModelsetforthinthissectionislargelyconsistentwithcurrent
industryunderstandings.Forexample,theNationalBIMStandarddefinesaBuildingInformationModelas
"adigitalrepresentationofphysicalandfunctionalcharacteristicsofafacility,"adefinitionexplicitlycrafted
toencompassmultiplefilesaswellasinformationbeyond3Dgeometry.
TodevelopModelprotocolsitisimportantthattheProjectParticipantshaveagoodunderstandingofwhat
willbeconsideredpartoftheProjectsModel.BecauseaModelislikelytocontainalargenumberoffiles,
andbecausethereareoftenmultiplewaysofrepresentingagivenpieceofProjectinformation,itwillbeup
totheProjectParticipantstoexplicitlydeterminewhichfilesarepartoftheModel.Thishasimplicationsfor
awiderangeofissues,includingdeterminingtheresponsibilitiesforDigitalDataandModelmanagement
anddefininghowinformationwillberepresentedwithintheModelandwhatinformationcanbereliedon
inusingtheModel.InE2032013itisassumedthattheModelwillconsistofanumberofinterrelatedfiles
anddatabases.G2022013Section1.2providesaplaceforexplicitlylistingthesefiles.
1.4.2BuildingInformationModeling.BuildingInformationModelingorModelingmeanstheprocess
usedtocreatetheModel(s).
ThereisanentireprocessinvolvedinthecreationofModels(e.g.training,collaboration,sharingofinformation,
clashdetection).ThetermBuildingInformationModelingorModelingisusedtorefertothatprocess.
1.4.3ModelElement.AModelElementisaportionoftheModelrepresentingacomponent,systemor
assemblywithinabuildingorbuildingsite.
TheconceptofwhatconstitutesaModelElementissignificant.InestablishingprotocolsforModeling,
ProjectParticipantsaretaskedwithorganizingthedevelopmentoftheModel.AModelconsistsofmany
componentpartspotentiallydevelopedbymanydifferententitiesorindividuals.Inordertoassign
responsibilityformanagingandcoordinatingthedevelopmentoftheModeltotheappropriateProject
Participant,andassigntheLevelofDevelopment,theModelneedstobebrokendownintocomponent
parts.TheModelElementsrepresentthesecomponentparts.
ItshouldalsobenotedthataModelElementisaportionoftheModel.Therefore,basedonthedefinition
ofModelasdiscussedabove,theModelElementmaynotconsistsolelyofagraphicalrepresentation.
10
TheModelElementwillalsoincludeanyotherdatasetstheProjectParticipantshavedecidedwillbepart
oftheModel,assetoutinG2022013Section1.2.
1.4.4 Level of Development. TheLevelofDevelopment(LOD)describestheminimumdimensional,spatial,
quantitative,qualitative,andotherdataincludedinaModelElementtosupporttheAuthorizedUses
associatedwithsuchLOD.
EachModelElementdevelopsatadifferentrate.TheLevelofDevelopment(LOD)frameworkallowsthe
ProjectParticipantstounderstandtheprogressionofaModelElementfromconceptualideatoprecise
definitionanddescription.TheLODofagivenModelElementinformstheotherProjectParticipantsabout
howdevelopedtheinformationisexpectedtobe,andtheextenttowhichthatinformationcanberelied
upon,ataparticularpointintimeinthedevelopmentoftheModel.IdentifyingtheLODforeachModel
Element,alongitsdevelopmentpath,helpspreventsotherProjectParticipantsfromusingtheModel
ElementinanunintendedmannerorinferringgreaterprecisionthantheModelElementAuthorintends.
SeetheGuidetopicsunderG2022013,Article2,foradetaileddiscussionofLevelsofDevelopment.
1.4.5AuthorizedUses.ThetermAuthorizedUsesreferstothepermittedusesofDigitalData
authorizedintheDigitalDataand/orBuildingInformationModelingprotocolsestablishedpursuanttothe
termsofthisExhibit.
AlargeamountofinformationcanbeincludedinaModelElement,regardlessofwhetherornotithas
beenfullythoughtthroughbyitsauthor.Theapproachtothisissuehasoftenbeentoprohibitrelianceon
anyinformationfromtheModel,throughtheuseofabroaddisclaimer.Inessence,thepositiontakenis:
becausesomeoftheinformationisnotreliabledontrelyonanyofit.
TheintentbehindestablishinganAuthorizedUseistochangethepositiontobecausesomeofthe
informationisnotreliableyoucanonlyrelyontheinformationthatIexplicitlysayyoucan.Thisallows
ProjectParticipantstotransmitinformationthroughModelsforspecificallyintendedpurposes,while
preventingunintendedreliance.TheG2022013ModelElementTableprovidesavehiclefordefining
AuthorizedUses,ModelElementbyModelElementandmilestonebymilestone.
1.4.6ModelElementAuthor.TheModelElementAuthoristheentity(orindividual)responsiblefor
managingandcoordinatingthedevelopmentofaspecificModelElementtotheLODrequiredforan
identifiedProjectmilestone,regardlessofwhoisresponsibleforprovidingthecontentintheModel
Element.ModelElementAuthorsaretobeidentifiedinSection3.3,ModelElementTable,ofG2022013.
AModelElementAuthor(MEA)isidentifiedtoprovideasinglepointofcontactfordevelopmentofeach
ModelElement,atanidentifiedProjectmilestone,inordertoaccomplishtheorganizeddevelopmentof
theModel.AseachModelElementevolves,theidentityoftheMEAmaychange.Forexample,when
developmentofaModelElementmovesfromthedesignphasetotheconstructionphasetheMEAmay
switchfromsomeoneonthedesignteamtoacontractororsubcontractor.Forexample,inthe
developmentofthestructuralsystem,thedesignatedMEAmaychangefromthearchitecttothestructural
engineerandfinallytothesteelfabricator.
11
ThedesignationofanMEAdoesnotchangewhoisinresponsiblechargeforthedesign.Thatresponsibilityisset
bytheProjectParticipantsscopesofworkintheiragreements.TheidentificationoftheMEAmaybeunrelated
totheindividualorentitythatisinresponsiblechargeoftheunderlyingdesign.Forexample,whilethestructural
engineermustbeinresponsiblechargeofallthestructuralengineeringonaproject,theArchitectmaybelisted
astheMEAbecausetheyarecoordinatingthedevelopmentoftheModelElementduringthedesignstages.
TheMEAisdefinedasanindividualorentitytoallowflexibility.Onsomeprojectsconsultantsortrade
contractorsmaybeidentified.Onothers,individualpeoplewithinthosefirmsmaybenamedinorderto
facilitatecommunicationandcoordination.
1.4.7DigitalData.DigitalDataisinformation,includingcommunications,drawings,specificationsand
designs,createdorstoredfortheProjectindigitalform.Unlessotherwisestated,thetermDigitalData
includestheModel.
DigitalDataisdefinedbroadly,andisintendedtoincludealltypesofdatastoredortransmittedviadigital
means.Itisimportanttonotethatunlessstatedotherwise,DigitalDataincludesModels.Accordingly,even
thoughArticle2ofE2032013onlyusesthetermDigitalData(andnotModels),theprovisionsofArticle2
applyequallytoallDigitalData,includingModels.
1.4.8ConfidentialDigitalData.ConfidentialDigitalDataisDigitalDatacontainingconfidentialorbusiness
proprietaryinformationthatthetransmittingpartydesignatesandclearlymarksasconfidential.
ThissectionprovidesaspecificdefinitionofConfidentialDigitalData.Careshouldbetakentomakesureit
isconsistentandcoordinatedwithanysimilardefinitionsintheAgreement.Thisdefinitionrelatesdirectly
toSection2.2.ThatsectionaddressesthePartiesresponsibilitieswithregardtoConfidentialDigitalData.
AnychangesormodificationsmadeinSection1.4.8willaffectSection2.2.
1.4.9WrittenorInWriting.InadditiontoanydefinitionintheAgreementtowhichthisExhibitis
attached,forpurposesofthisExhibitandtheAgreement,writtenorinwritingshallmeanany
communicationpreparedandsentusingatransmissionmethodsetforthinthisExhibit,ortheprotocols
developedpursuanttothisExhibit,thatpermitstherecipienttoprintthecommunication.
ThissectionclarifiesthemeaningofthetermsWrittenorInWritingastheyrelatetoanincreasingly
digitalworld.ThisclarificationisnecessarybecauseE2032013isanexhibitthatwillbeattachedtoa
completeagreement.Itisverypossiblethattheunderlyingagreementwillusetheseterms,anddosoina
contextthatdidnotcontemplatemeansoftransmissionintheageofDigitalData.
E2032013Section1.4.10
1.4.10WrittenNotice.InadditiontoanytermsintheAgreementtowhichthisExhibitisattached,for
purposesofthisExhibitandtheAgreement,writtennoticeshallbedeemedtohavebeendulyservedif
transmittedelectronicallytoanaddressprovidedinthisExhibitortheAgreementusingatransmission
methodsetforthinthisExhibitthatpermitstherecipienttoprintthecommunication.
12
ThissectionisaclarificationoftermsthatmaybeusedintheAgreementinacontextthatdidnot
contemplateanenvironmentwhereDigitalDataistheprimarymeansofcommunication.
E2032013Section1.4.11
1.4.11PartyandParties.ThetermsPartyandPartiesrefertothesigningpartiestotheAgreement.
SeeE2032013Section1.4.12discussion.
E2032013Section1.4.12
1.4.12ProjectParticipant.AProjectParticipantisanentity(orindividual)providingservices,work,
equipmentormaterialsontheProjectandincludestheParties.
WhileE2032013willgenerallybeattachedtoanagreementbetweentwospecificParties,itsintended
impactgoesbeyondjustthosetwoParties.Inordertobeeffective,theDigitalPracticedocumentsmust
guideandimpacttheactionsandbehaviorofthevariousparticipantsontheProjectthatwillutilizeDigital
Data.Accordingly,indescribingvariousresponsibilities,E2032013andtheassociatedprotocoldocuments
oftenneedtorefertothelargergroupofProjectParticipants.Thissectionprovidesthedefinedterm
ProjectParticipanttoaddressthatneed.
Insomeinstances,however,thereisalsoaneedtorefertothespecificPartiestotheAgreementtowhich
E2032013isattached.ThedutiesandobligationscreatedinE2032013contractuallyflowbetweenthe
actualPartieswhohavesignedtheAgreement,notalloftheProjectParticipants.(Theexceptiontothisruleis
thelimitedthirdpartybeneficiaryprovisioninSection1.2.1.)Therefore,E2032013alsohasadefinitionfor
Parties,inSection1.4.11,inordertodistinguishthesignatoriestotheAgreementfromalltheotherProject
Participants.Thedefinitionsmakeclear,however,thatthetermProjectParticipantincludestheParties.
Further,whentheE203standardlanguagereferstothecapitalizedtermAgreement,itisreferencingthe
specificagreementtowhichE203isattached.Accordingly,thetermsoftheE2032013areonlybindingon
thePartiestotheAgreement.ThisiswhyidenticalversionsoftheE2032013mustbeincorporatedinto
alltheotherProjectParticipantsagreements.EachProjectParticipantbecomesaPartywhenE2032013
isattachedtotheiragreement.Theytherebybecomesubjecttothesameobligationsandrestrictionsasall
theotherProjectParticipantsthathaveE2032013attachedtotheiragreements.Bywayofexample,
whereE2032013isattachedtoanA1012007,theOwnerandtheContractorarethePartiesandare
boundbythetermsofE2032013.TheArchitect,however,isnotaPartytotheA1012007andisaProject
Participantinthecontextofthatagreement.SincetheidenticalE2032013isattachedtotheB1012007,
towhichtheArchitectisaParty,theArchitectisboundbythesameobligationsastheContractor.
Article2TransmissionandOwnershipofDigitalData
E2032013Section2.1
2.1ThetransmissionofDigitalDataconstitutesawarrantybythePartytransmittingDigitalDatatothe
PartyreceivingDigitalDatathatthetransmittingPartyisthecopyrightowneroftheDigitalData,or
otherwisehaspermissiontotransmittheDigitalDataforitsuseontheProjectinaccordancewiththe
AuthorizedUsesofDigitalDataestablishedpursuanttothetermsofthisExhibit.
13
InexchangingDigitalData,thePartyreceivingDigitalDatamusttrustthatitisfreetoreceiveandusethe
informationprovided.Accordingly,Section2.1placesadutyonthetransmittingPartytowarrantthatitis
eitherthecopyrightholderoftheinformationbeingtransferredorhaspermissionfromthecopyright
holdertotransmittheinformationforuseontheProject.
ItshouldbenotedthatE2032013doesnotspecificallyaddressownershipoftheModel.Itisassumedthat
E203willbeusedinconjunctionwithotherAIAContractDocumentsstandardformagreements,which
generallyprovidethatcopyrightownershipoftheInstrumentsofService(whichwouldincludeaModel)
resideswiththeindividualorentitythatcreatedthem.AIAContractDocumentsalsogenerallyrequirethe
copyrightholdersoftheInstrumentsofServicetogranttheOwneralicensetousetheInstrumentsof
ServicefortheProject.Accordingly,thedigitalpracticedocumentsaresilentonownershipbecauseitis
assumedthetopicisaddressedintheAgreement.
E2032013Section2.2
2.2IfaPartytransmitsConfidentialDigitalData,thetransmissionofsuchConfidentialDigitalData
constitutesawarrantytothePartyreceivingsuchConfidentialDigitalDatathatthetransmittingPartyis
authorizedtotransmittheConfidentialDigitalData.IfaPartyreceivesConfidentialDigitalData,the
receivingPartyshallkeeptheConfidentialDigitalDatastrictlyconfidentialandshallnotdiscloseittoany
otherpersonorentityexceptassetforthinSection2.2.1.
SeeSection2.2.1discussion.
2.2.1ThereceivingPartymaydiscloseConfidentialDigitalDataasrequiredbylaworcourtorder,
includingasubpoenaorotherformofcompulsorylegalprocessissuedbyacourtorgovernmentalentity.
ThereceivingPartymayalsodisclosetheConfidentialDigitalDatatoitsemployees,consultantsor
contractorsinordertoperformservicesorworksolelyandexclusivelyfortheProject,providedthose
employees,consultantsandcontractorsaresubjecttotherestrictionsonthedisclosureanduseof
ConfidentialDigitalDataassetforthinthisExhibit.
ConfidentialDigitalDataisdefinedinE2032013Section1.4.8asDigitalDatacontainingconfidentialor
businessproprietaryinformationthatthetransmittingpartydesignatesandclearlymarksasconfidential.
ItisimperativethatboththePartytransmittingandthePartyreceivingConfidentialDigitalData
understandsitsresponsibilitieswithregardtosuchinformation.Section2.2establishesthePartiesrightsin
transmittingConfidentialDigitalDataandobligationsinmaintainingitsconfidentiality.Section2.2.1,
however,clearlyestablishescertainreasonableexceptionstotherequirementthatConfidentialDigital
Databekeptstrictlyconfidential.
E2032013Section2.3
2.3BytransmittingDigitalData,thetransmittingPartydoesnotconveyanyownershiprightintheDigital
DataorinthesoftwareusedtogeneratetheDigitalData.Unlessotherwisegrantedinaseparatelicense,
thereceivingPartysrighttouse,modify,orfurthertransmitDigitalDataisspecificallylimitedtodesigning,
constructing,using,maintaining,alteringandaddingtotheProjectconsistentwiththetermsofthisExhibit,
andnothingcontainedinthisExhibitconveysanyotherrighttousetheDigitalData.
14
Thesharingoffilesisofconcerntomanyprofessionalsduetothefearoflosingcontrolover,ownershipof,and/or
copyrightinthefilesshared.Becausethevalueofmanydigitaldocuments,specificallyModels,isincreasedwithfile
sharingandcollaboration,itisnolongerfeasibletowithholdaccess.Therefore,toencourageandprotectthe
owneroftheDigitalData,itiscriticalthatthereceivingpartyunderstandsandagreestothelimitsofuse.
E2032013Section2.4
2.4WhereaprovisioninthisArticle2conflictswithaprovisionintheAgreementintowhichthisExhibitis
incorporated,theprovisioninthisArticle2shallprevail.
E2032013isintendedtobeincorporatedasanexhibitintotheAgreementbetweentheParties.Many
suchagreementsmayalreadycontainlanguageregardingthetransmissionofcopyrightedmaterialsand
theuseofconfidentialinformation.Toavoidtheriskofconflictingprovisions,Section2.4statesthatthe
termsoftheExhibitsetforthinArticle2willhaveprecedence.Itshouldbeunderstood,however,thatthe
termsofArticle2applyonlytoDigitalData.TermsintheAgreementaddressingnonDigitalDatawouldnot
necessarilybeinconflictwiththetermsofArticle2.
Regardlessofthisstatement,however,theexistenceoftwospecificrequirementsortermspertainingto
thesameissues,oneinthemainbodyoftheAgreementandtheotherintheattachedE2032013,may
createconfusionandambiguity.Accordingly,theExhibitandtheAgreementshouldbereviewedand
coordinatedtotheextentpractical.
Article3DigitalDataProtocols
E2032013Section3.1
3.1AnticipatedTypesofDigitalData.TheanticipatedtypesofDigitalDatatobeusedontheProjectare
asfollows.
(IndicatebelowtheinformationontheProjectthatshallbecreatedandsharedinadigitalformat.IftheParties
indicatethatBuildingInformationModelingwillbeutilizedontheProject,thePartiesshallalsocompleteArticle4.)
LocationofDetailed
Description
Applicability
(Section3.1.1below
totheProject
orinanattachmenttothis
(IndicateApplicable
exhibitandidentified
AnticipatedDigitalData
ornotApplicable)
below)
ProjectAgreementsandModifications
Projectcommunications
Architectspreconstructionsubmittals
ContractDocuments
Contractorssubmittals
Subcontractorssubmittals
Modifications
Projectpaymentdocuments
NoticesandClaims
BuildingInformationModeling
15
TherangeofpotentialtypesandusesofDigitalDataisvirtuallylimitless.Thisbreadthofpossibilitiesis
perhapsthegreatestbenefitofusingDigitalDataontheProject,buttheseendlessoptionsandchoicesalso
representrisk.AlackofunderstandingamongtheProjectParticipantsontheanticipatedusesforDigital
Dataincreasesthelikelihoodoflatermisunderstandingsandconflicts.TheProject,anditsparticipants,
couldsufferfrominefficientanduncoordinateduseofDigitalData,unintendeduseofDigitalData,the
inabilitytouseincompatibleDigitalData,andunrealizedexpectationsamongProjectParticipants.
TocompleteSection3.1,ProjectParticipantsshouldconsiderhowDigitalDataisexpectedtobeutilizedand
shared.Section3.1isintendedtobecompletedattheinitiationoftheProject,beforeadefinitivelistofall
expectationscanbeestablished,however,themorespecifictheidentificationoftheanticipateduses,thebetter.
ThissectionfurtherservesasalaunchingpointforProjectParticipantstodiscussanddifferentiatebetween
theusesofDigitalDatathatareincludedinthefeesorcontractsumatthetimetheAgreementand
E2032013areexecuted,andanysubsequentlyestablishedusesthatmayrequirethePartiestoundertake
additionalefforts,assumeadditionalrisksorprovideadditionalvaluetotheProject.Seethediscussionfor
E2032013Section1.3.
ThefirstcolumnofthetableisprepopulatedwithcommonlyusedtypesofdataidentifiedinG2012013
althoughusersshouldmodifyitasnecessarytomeettheirspecificProjectneeds.Theusershouldindicate
inthesecondcolumnwhethertheDigitalDataisanticipatedtobeusedontheProjectandthenusethe
thirdcolumntoindicatewherethecharacteristicsandanticipateduseoftheDigitalDataaredescribedin
moredetail.RememberthattheintentistoestablishageneralunderstandingofthescopeofDigitalData
usesothatexpectationsareinalignmentandscopeandfeearenegotiatedproperly.Theactualprotocols
forhowthedigitaldatawillbeusedarelatercapturedinG2012013.
Whiletheprefilledlistislikelytobesufficientformanyprojects,thetableisflexibleandallowsother
anticipateddigitaldatatobeaddedtomeetspecificprojectrequirements.Examplesincludethefollowing:
Surveys
Energyanalyses
Costestimating
Submittalapprovals
CAD
Photographs
Video
ThelistofusesidentifiedinthissectionshouldultimatelybecoordinatedwithG2012013wherethe
protocolsforsharingtheDigitalDataaredescribed.
NotethatifthePartiesintendtouseBuildingInformationModelingontheProject,whichappearsinthe
standardtextofthelist,theparentheticalinstructionstatesthatthePartiesshouldindicatesuchintention
inSection3.1andcompleteArticle4todescribetheuniquecharacteristicsofModeldevelopment,useand
sharing.TheprotocolsgoverningDigitalDataunderArticle3mayrelatetoBIM,butthePartiesmustalso
completeArticle4tofullyexplainandaddresstheirexpectationswithregardtoBIM.
16
3.1.1InsertadetaileddescriptionoftheanticipatedDigitalDataidentifiedinSection3.1,ifnotfurther
describedinanattachmenttothisExhibit.
Section3.1.1providesafillpointforthePartiestoprovideadetaileddescriptionofthetypesofDigitalData
tobeusedontheProject.ThePartiesshoulddescribetheanticipatedscopeofservicesinasmuchdetailas
possible.Doingsowillreducethelikelihoodofalaterdisputesrelatingtothenatureandtypesof
informationthatwouldbedigital.
E2032013Section3.2
3.2AssoonaspracticalfollowingexecutionoftheAgreement,thePartiesshallfurtherdescribetheusesof
DigitalData,andestablishnecessaryprotocolsgoverningthetransmissionandAuthorizedUsesofDigitalData,
inconsultationwiththeotherProjectParticipantsthatareexpectedtoutilizeDigitalDataontheProject.
Section3.2requiresthePartiestomeettoestablishDigitalDataprotocolsassoonaspracticalfollowing
executionoftheAgreement.
E2032013purposelydoesnotestablishtheseprotocolswhentheagreementbetweenthePartiesis
executed.ThewayDigitalDataisused,andthebenefitsthatwillresult,willvarybasedontheteam,the
projectdeliverymethod,andtheprojectitself.Becauseofthesevariables,itisimpracticalforthisExhibitto
identifyaspecifictimefortheestablishmentoftheprotocols,favoringinsteadassoonaspractical
followingexecutionoftheAgreement.Whilethenotionofassoonaspracticalfollowingexecutionofthe
Agreementwillvaryfromprojecttoproject,theProjectParticipantsshouldendeavortoestablishthe
protocolsbeforesignificantdataexchangesbegin,toavoiduncoordinatedandinefficientuseofDigital
Data.ItshouldalsobenotedthatanyuseofDigitalDatabyaProjectParticipantpriortotheagreementto
anddocumentationoftheDigitalDataprotocolsinG2012013willbeattheProjectParticipantssolerisk
pursuanttoSection3.4.1.
IdentifyingspecificDigitalData,itsuses,andthemethodsforsharingandarchivingisaccomplishedby
completingtheDigitalDataprotocolsinG2012013.CompletingtheinitialG2012013andmodifyingitas
necessarytoreflectchangingprojectrequirementswillensurethataclearunderstandingofroles,
responsibilitiesandusesareevidenttoallProjectParticipants.
Recognizingthatatthetimecontractsaretypicallyexecuted,aprimarypurposeofE2032013istoallow
thePartiestoadequatelydefinetheirexpectationsregardingtheuseofDigitalDataandtomoreclearly
definethePartiesscopeofservicesandcompensation.Thereafter,andconsistentwiththeparametersset
intheE2032013,thePartiesfleshoutthespecificdetailsregardingDigitalDatainG2012013.
ThisapproachisnotsodifferentfromtheapproachoftentakenwithregardtoLEEDrelatedservices.A
buildingownermayincludeinitsprogramthegoalofobtainingacertainLEEDrating.Often,however,the
specificstepstoreachthatgoalarenotestablishedatthetimetheOwner/Architectagreementis
executed.Typically,theOwner,ArchitectandContractorhavenotyetdeterminedwhichLEEDelementsto
pursue,andthosedetailsoftengetworkedoutastheProjectproceeds.
17
3.2.1UnlessanotherProjectParticipantisidentifiedbelow,theArchitectshallprepareanddistributeto
theotherProjectParticipantsDigitalDataprotocolsforreview,revisionandapproval.
(IfaProjectParticipantotherthantheArchitectshallberesponsibleforpreparingdraftandfinalDigital
Dataprotocols,identifythatProjectParticipant.)
AssigningtheresponsibilitytopreparewrittenDigitalDataprotocolstoasingleProjectParticipantcreatesan
advocateforthedevelopmentoftheprotocolsandisintendedtoensurethatthetaskiscompleted.Section
3.2.1establishestheArchitectasthedefaultentityresponsibleforpreparingthewrittenprotocols.The
Architectisdesignatedbecause,formostprojects,theArchitectislikelybettersituatedintheearlystagesof
theProjecttoassesstheentirerangeofDigitalDatanecessarytoseetheProjecttoitscompletion.However,
ifsomeoneotherthantheArchitect,orifmultipleProjectParticipants,willberesponsibleforpreparing
writtenprotocols,thoseProjectParticipantsmustbeidentified.Forexample,ifanOwnersrepresentativehas
establishedprotocolsfordocumentmanagement,orifaConstructionManagerisresponsibleformanaging
Projectinformation,itmaymakemoresensetohavethatProjectParticipantpreparethewrittenprotocols.
3.2.2TheagreeduponDigitalDataprotocolsshallbesetforthinAIADocumentG2012013andeachProject
ParticipantshallmemorializetheiragreementinwritingtosuchDigitalDataprotocols.
Section3.2.2establishestheexpectationthattheProjectParticipantswillapprovetheDigitalData
protocolsandwillmemorializetheiragreementinwritinginG2012013.(SeeE203Section1.4.9for
discussionofthedefinedterminwriting.)
AstheenforcementoftheprotocolsmayultimatelydependontheabilityofaProjectParticipanttoprove
thattheotherProjectParticipantsagreedtotheprotocols,Section3.2.2alsorequireseachProjectParticipant
tomanifest,inwriting,theiragreementtotheDigitalDataprotocols.Therearearangeofpossibilities
availabletouserswithregardtothemechanismthroughwhichProjectParticipantscanmanifesttheir
agreementtotheprotocols.ThemostobviousoptionistorequireeachProjectParticipanttosign
G2012013.Lessformaloptionsmayalsobeavailablesuchasrequiringinitials.Further,asprojectWeb
sitesgrowinpopularity,theprotocolsmaybedistributedonsuchWebsitesandProjectParticipantsmay
berequiredtocheckaboxthattheyhaveagreedtothelatestversionsoftheprotocols.
3.2.3TheParties,togetherwiththeotherProjectParticipants,shallreviewand,ifnecessary,revisethe
DigitalDataprotocolsatappropriateintervalsasrequiredbytheconditionsoftheProject.
AstheProjectprogresses,theProjectParticipantswilllikelybegintoadjusthowtheyshareanduseDigitalData.
Needsmaychange,efficienciesmaybediscovered,andnewProjectParticipantsmayjointheProject.Regardless
ofthereasons,Section3.2.3anticipatesthelikelihoodthattheestablishedprotocolswillneedtoberevised.
E2032013Section3.3
3.3ThePartiesshalltransmit,use,storeandarchiveDigitalDatainaccordancewiththeDigitalData
protocolssetforthinthelatestversionofAIADocumentG2012013agreedtobytheProjectParticipants.
Thislanguagecreatesacontractualobligationtofollowtheprotocolsastheyareestablishedandagreedto
bythePartiesandotherProjectParticipants.Asnotedabove,however,theenforcementoftheprotocols
18
mayultimatelydependontheabilityofaProjectParticipanttoprovethattheotherProjectParticipants
agreedtotheprotocols.Accordingly,inutilizingG2012013,theProjectParticipantsshoulddevelopan
acceptableprocesstodocumentthereceiptof,andagreementto,eachversionoftheprotocolsbyeach
ProjectParticipant.SuchaprocesswillprotectagainstaProjectParticipantultimatelyclaimingthatitnever
saw,oragreedto,thelatestversionoftherelevantprotocolsandthereforeisnotboundbythem.
E2032013Section3.4
3.4UnauthorizedUse
3.4.1PriortoEstablishmentofDigitalDataProtocols
IfaPartyreceivesDigitalDatapriortotheagreementto,anddocumentationof,theDigitalDataprotocols
inAIADocumentG2012013,thatPartyisnotauthorizedtouseorrelyontheDigitalData.Anyuseof,or
relianceon,suchDigitalDataisatthatPartyssoleriskandwithoutliabilitytotheotherPartyandits
contractors,consultants,agentsandemployees.
ThepremiseoftheDigitalPracticedocumentsisthattheProjectParticipantsarewillingtoshareDigital
DatabecausetheprotocolsestablishclearexpectationsandrestrictionsregardingtheAuthorizedUsesof
theDigitalData.Nevertheless,itmaybenecessary,orbeneficialtotheProject,forDigitalDatatobeshared
priortotheestablishmentoftheprotocols.Astheprotocolsarenotyetestablished,theassociated
AuthorizedUseshaveyettobeestablished.Accordingly,whereDigitalDataissharedpriorto
establishmentoftherequiredprotocolsanyuseoftheDigitalDataisatthesoleriskofthePartyusingthe
DigitalDatawithoutliabilitytotheotherPartyoranyofitsconsultants,contractors,agents,and
employees.ThisprovisionreinforcesthenotionthatDigitalDatashouldonlybeusedandreliedonafterthe
protocolsgoverningitsusehavebeendiscussedandagreedtobytheProjectParticipants.
IfthePartiesbelieveadditionalprotectionisnecessary,indemnificationlanguagecouldbeaddedtothe
endofthissection.Anexampleofsuchlanguageisasfollows:
Tothefullestextentpermittedbylaw,suchPartyshallindemnifyandholdharmlessthe
otherPartyanditscontractors,consultants,agentsandemployeesfromandagainstclaims,
damages,lossesandexpenses,includingbutnotlimitedtoattorneysfees,arisingoutofor
resultingfromsuchPartysuse,transmission,orrelianceonsuchDigitalData.
AsnotedaboveindiscussingE2032013Section1.2.1,anyindemnificationlanguageshouldbereviewedclosely
withlegalandinsurancecounselasindemnificationprovisionsarecomplexandnotoriouslydifficulttoenforce.
3.4.2FollowingEstablishmentofDigitalDataProtocols
Followingagreementto,anddocumentationof,theDigitalDataprotocolsinAIADocumentG2012013,ifa
PartyusesDigitalDatainconsistentwiththeAuthorizedUsesidentifiedintheDigitalDataprotocols,that
useshallbeatthesoleriskofthePartyusingtheDigitalData.
Oncetheprotocolsareestablished,theProjectParticipantshaveallagreedtouseDigitalDataconsistent
withtheprotocols.UseinconsistentwiththeDigitalDataprotocols,whichincludetheAuthorizedUses,is
atthesoleriskofthePartyusingtheDigitalData.
IfthePartiesbelieveadditionalprotectionisnecessary,theymayconsiderincludinganindemnification
obligationattheendofthissection,suchasthefollowing:
19
Further,tothefullestextentpermittedbylaw,thePartyusingtheDigitalDatashall
indemnifyandholdharmlesstheotherPartyanditscontractors,consultants,agentsand
employeesfromandagainstclaims,damages,lossesandexpenses,includingbutnot
limitedtoattorneysfees,arisingoutoforresultingfromsuchPartysuseoftheDigitalData
inconsistentwiththeAuthorizedUsesidentifiedintheDigitalDataprotocols.
Forthereasonsnotedabove,however,indemnificationcanbeacomplicatedlegalconcept,and
indemnificationlanguageshouldbereviewedcloselywithlegalandinsurancecounsel.Generallyspeaking,
themorebroadlywrittentheindemnity,thelesslikelythatitwillultimatelybeenforceable.
3.5.1CentralizeddocumentmanagementsystemuseontheProjectshallbe:
(Checktheappropriatebox.IfthePartiesdonotcheckoneoftheboxesbelow,thedefaultselectionshallbe
thatthePartieswillnotutilizeacentralizedelectronicdocumentmanagementsystemontheProject.)
ThePartiesintendtouseacentralizedelectronicdocumentmanagementsystemontheProject.
ThePartiesdonotintendtouseacentralizedelectronicdocumentmanagementsystemonthe
Project.
Theuseofcentralizeddocumentmanagementsystemsisbecomingincreasinglyprevalentfortodays
projects.Thesesystemsrangeincomplexityfromasimplerepositorythatallowsthosewithaccesstoview,
useandmodifyprojectrelatedelectronicdatafiles,torobustdocumentmanagementproductsthatadd
featureslikeaccessrights,documenttrackingandversioncontrol.Notallprojectswillutilizeacentralized
electronicdocumentmanagementsystemorprogram.Ifoneistobeused,however,themanagementof
thatProjectwidesystemmayresultinadditionalscopeforsomeoralloftheProjectParticipants.
Accordingly,inSection3.5.1,thePartiesshouldindicatetheirexpectationsregardingtheuseofsucha
systemorprogram.IfthePartiesfailtocheckoneoftheboxes,thedefaultshallbethatacentralized
electronicdocumentmanagementsystemorprogramwillnotbeusedontheProject.
3.5.2IftheProjectParticipantsintendtoutilizeacentralizedelectronicdocumentmanagementsystem
ontheProject,theProjectParticipantsidentifiedinSection3.5.3shallberesponsibleformanagingand
maintainingsuchsystem.TheProjectParticipantsresponsibleformanagingandmaintainingthecentralized
electronicdocumentmanagementsystemshallfacilitatetheestablishmentofprotocolsfortransmission,
use,storageandarchivingofthecentralizedDigitalDataandassisttheProjectParticipantsidentifiedin
Section3.2.1aboveinpreparingDigitalDataprotocols.Uponagreementto,anddocumentationof,the
DigitalDataprotocolsinAIADocumentG2012013,theProjectParticipantsidentifiedinSection3.5.3shall
manageandmaintainthecentralizedelectronicdocumentmanagementsystemconsistentwiththe
managementprotocolssetforthinthelatestversionofG2012013approvedbytheProjectParticipants.
IfthePartiesdeterminethatacentralizedmanagementsystemwillbeusedontheProject,Section3.5.3
providesanopportunitytoidentifytheProjectParticipant(s)thatwillberesponsibleformaintainingit.The
identifiedProjectParticipantsarerequiredtofacilitate,withtheotherProjectParticipants,theestablishment
oftheprotocolsrelatingtothecentralizedelectronicdocumentmanagementsystemandtoassisttheProject
ParticipantidentifiedunderSection3.2.1inpreparinganyrelatedDigitalDataprotocols.
TodevelopthecentralizedDigitalDatamanagementsystemprotocols,theProjectParticipantstaskedwith
managingDigitalDatashouldconsiderhowtobestfacilitatecommunicationandtransferoftheDigitalData
20
toallrelevantProjectParticipants,aswellasthearchivalrequirementsthatensuretheintegrityofrecord
copies.Examplesofotheritemstoconsiderincludethefollowing:
WhoneedstohaveaccesstotheDigitalData,atwhatpoint,andwithwhatlevelofpermissions?
HowtocontroltheintegrityoftheDigitalDataasitisbeingused,andlimittheabilityofediting
tothosewhohavepermission?
HowdoesthemanagerestablishaccesstoProjectParticipantsthatarenotactiveusersofDigital
Data,butmayberequiredtoobserveprogress?
AtwhatpointsduringtheProjectarerecordcopiesoftheDigitalDatatobearchived?
3.5.3UnlessresponsibilityisassignedtoanotherProjectParticipant,theArchitectshallberesponsiblefor
managingandmaintainingthecentralizedelectronicdocumentmanagementsystem.Iftheresponsibilityfor
managementandmaintenancewillbeassignedtoanotherProjectParticipantatanidentifiedProjectmilestone,
indicatebelowtheProjectParticipantwhoshallassumethatresponsibility,andtheProjectmilestone.
(IdentifytheProjectParticipantresponsibleformanagementandmaintenanceonlyifthePartiesintendto
utilizeacentralizedelectronicdocumentmanagementsystemontheProject.)
ResponsibleProjectParticipant
ProjectMilestone
WhenthePartieshaveagreedtouseacentralizeddatamanagementsystem,Section3.5.3assignsthe
managementresponsibilityofthatsystemtotheArchitect.IfProjectcircumstancessuggestanotherProject
Participantmightbebettersuited,thePartiesarerequiredtoidentifythosewhowillberesponsible.The
tableincludedinSection3.5.3allowstheresponsibilitytobeassignedbasedontheProjectmilestones
acknowledgingthat,throughoutthecourseoftheProject,theremaybedifferentindividualsorentities
bettersuitedtomanagethecentralizedDigitalData.Forexample,whenaProjectshiftsfromthedesign
phasestotheconstructionphase,itmaybeappropriateforthemanagementofsharedDigitalDatatoshift
fromtheArchitecttotheContractor.Inthatinstance,thetablemightbecompletedinthisway:
Responsible Individual or Entity

Architect
Contractor
Project Milestone
ProjectInception
CommencementofConstruction
Article4BuildingInformationModelingProtocols
E2032013Section4.1
4.1IfthePartiesindicateinSection3.1thatBuildingInformationModelingwillbeusedontheProject,
specifybelowtheextenttowhichthePartiesintendtoutilizeBuildingInformationModelingandidentify
theprovisionsofthisArticle4governingsuchuse:
ThePartiesshallutilizeBuildingInformationModelingontheProjectforthesolepurposeof
fulfillingtheobligationssetforthintheAgreementwithoutanexpectationthattheModelwillbe
relieduponbytheotherProjectParticipants.Unlessotherwiseagreedinwriting,anyuseof,
transmissionof,orrelianceontheModelisatthereceivingPartyssolerisk.Theremaining
sectionsofthisArticle4shallhavenoforceoreffect.
ThePartiesshalldevelop,share,useandrelyupontheModelinaccordancewithSections4.2
through4.10ofthisExhibit.
21
Section4.1requiresthePartiestoidentifytheintendedscopeofuseofBIMviaacheckbox.
IfthePartieschoosethefirstcheckbox,thePartieswillonlyuseModelinginternallytofacilitatethecompletionof
theirunderlyingcontractualobligations.UnderthisoptiontheModelispreparedwithouttheexpectationthatit
willbesharedwithandrelieduponbytheotherProjectParticipants.IftheModelisinfactshared,subsequentuse
of,orrelianceon,theModelisatthesoleriskofthePartyreceivingtheModel.TheremainingSectionsofArticle4
donotapplybecausetheyaretailoredtoaddresstheuniqueissuesthatarisewhentheModelispreparedwiththe
expectationthatitwillbesharedwiththeotherProjectParticipants.Itshouldalsobenotedthatincheckingthe
firstbox,thePartiesarguablyindicatetheywillnotbesharingtheirownmodelswiththeirownconsultantsor
subcontractors.IfmodelsaretobesharedononesideoftheProject(i.e.,amongstthedesignteamonly),thetext
ofE2032013willneedtobemodified(seealsodiscussionaboveatE2032013Section1.2),orthesecondbox
shouldbecheckedandtheG2022013protocolcarefullycompleted(seediscussionbelow.)
Bychoosingthesecondcheckbox,thePartiesagreethattheModelwillbedeveloped,shared,used,and
reliedoninaccordancewithSections4.2through4.10,whichallowforthesubsequentestablishmentof
theModelingprotocolsthatwillbesetforthinG2022013.EvenifthePartiescheckbox2,theycanstill
exertasignificantamountofcontroloverhowtheModelissharedandrelieduponontheProject.
If,forexample,thePartiesonlyintendtoallowthearchitectanditsconsultantstoshareandrelyonthe
Model,E2032013andG2022013couldbecraftedinsuchawaythattheAuthorizedUsesonlyrelate
specificallytotheprovisionofdesignservices.TheAuthorizeUses,forexample,wouldnotpermit
fabricationordetailedcostestimating.So,whiletheModelwillbesharedandreliedon,theultimatescope
ofrelianceanduseislimitedtothedesignteam.Evenifoneofthecontractorsendedupreceivingthe
Model,bythetermsofE2022013attachedtotheirAgreement,theyagreedtofollowthesetforthin
G2022013.TheprotocolswouldlimitrelianceontheModelElementstoonlydesignrelatedservices.
Accordingly,pursuanttoE2032013Section4.7,anyuseinconsistentwiththoseAuthorizedUseswouldbe
atthecontractorssolerisk.
AnotheroptionwouldbetoaddlanguagetooneoftheoptionsclarifyingthattheModelwillonlybe
sharedduringthedesignoftheprojectandonlyamongthedesignteam.Usersareencouragedtomodify
andrevisethestandardlanguagetofittheirspecificneeds.
UsersshouldnotethatthestandardlanguageobligatestheParties,andnottheProjectParticipants,to
develop,share,useandrelyupontheModelinaccordancewiththetermsofE2032013.Thisisbecause,
asisdiscussedaboveinthedefinitionsofPartiesandProjectParticipants,E2032013isonlybindingonthe
Partiestotheunderlyingagreement.E2032013,however,isintendedtobeincorporatedintoevery
agreementontheProject.Accordingly,eachProjectParticipantbecomesboundbyacommonsetof
obligationsandprotocolsbyvirtueofE2032013beingincorporatedintoitsProjectAgreement.
UsersshouldalsounderstandtheimpacttheirselectioninSection4.1canhaveoncompensation.E203
2013Section1.3statesthattheestablishmentoftheprotocolsmayresultinanadjustmentin
compensationifsuchprotocolsresultinachangetotheoriginallyanticipatedscopeofworkorservices.If
thePartieschoosethefirstbox,thePartyutilizingModelingretainscompletecontroloverthescopeofBIM
servicesandthelevelofdevelopmentitputsintotheModel,asitisonlyusingModelingasatooltofulfill
itsobligationsintheunderlyingAgreement.Compensationwillbebasedonthatexpectation.
22
IfthePartiesagreethatModelswillbeusedformorethanjustthePartiesinternalpurposes,theParties
recognizethatModelswillbesharedwithandusedbyotherProjectParticipantsforcertainidentified
AuthorizedUses.ThePartiesfurtheragreetosubsequentlyestablishprotocolsthatwillcontrol
developmentof,useofandrelianceontheModel.Underoption2,theassumptionisthattheModelwill
bereliedonbytheotherProjectParticipantsforcertainAuthorizedUses.ThismeansthattheModeling
PartiesmustdeveloptheModelsufficientlytomeetsuchexternalneedsanduses.Thisamountofeffort
maybeinconsistentwiththelevelofdevelopmentaPartywouldnormallyprovideifModelingwasonly
usedasatooltofulfillitsownobligationsandthereforewarrantanadjustmentincompensation.
E2032013Sections4.3,4.4and4.5requirethePartiestoestablishtheiranticipatedscopesofworkor
servicesrelatedtoModelingbeforetheprotocolsareestablished.TheclearerthePartiesareinthose
sections,theeasieritwillbetodetermineifachangeinscopehasoccurredwhentheprotocolsare
subsequentlyestablished,thusreducingthepossibilityforconflict.
E2032013Section4.2
4.2AnticipatedBuildingInformationModelingScope.IndicatebelowtheportionsoftheProjectfor
whichModelingwillbeusedandtheanticipatedProjectParticipantresponsibleforthatModeling.
ConsistentwiththegeneralscopingpremiseoftheE2032013,Section4.2providestheopportunityto
broadlydefinehowModelingwillbeusedontheProjectandwhowillberesponsibleforsuchModeling.
PartiesmustbeawareoftheportionsoftheProjectthatareinthescopetobemodeled,andthose
portionsthatwillbereferenced,diagrammed,orotherwisedocumentedwithoutModelingforexample:
1)
2)
3)
TheProjectModelswillincludestructuralandarchitecturalModels.
MechanicalandPlumbingModelElementswillonlybedevelopedinthemechanicalroomsand
forpipeslargerthan2inchesindiameter.
ElectricalLightingModelElementswillbemodeled,aswellasracewaysandductbanksandall
conduitslargerthan2inches.AllsmallerconduitsandwiringshallbesymbolicLOD100only.
Inadditiontoindicatingwhatwillbemodeled,itisalsoimportanttoindicatewhowillbedoingthe
modeling.Again,theamountofModelingaProjectParticipantexpectstoperformontheProjectdirectly
impactstheirscopeofservices.Accordingly,itservestheentireProjecttobeasclearaspossibleinthe
ProjectAgreementsastotheModelingexpectationssoastoavoidscopedisputeslaterintheProject.
WhileE2032013providesflexibilityontheinformationtobeincludedinthissectionandtheformatin
whichitisprovided,thefollowingisanexampleofhowtocompletethissectionutilizingatableformat:
AnticipatedModelingScope
TheProjectModelswillincludestructuraland
architecturalModels.
ProjectParticipantResponsible
AQAArchitects
MechanicalandPlumbingModelElementswillonly
bedevelopedinthemechanicalroomsandfor
pipeslargerthan2inchesindiameter.
SDSEngineering
ElectricalLightingModelElementswillbemodeled,
aswellasracewaysandductbanksandallconduits
largerthan2inches.Allsmallerconduitsandwiring
shallbesymbolicLOD100only.
AQAArchitects
23
AsnotedaboveinthediscussionofSection4.1,ifthesubsequentlyestablishedprotocolsvaryfromthe
anticipatedModelingscopesetforthinthissection,theremaybeaneedtoadjustcompensation,contract
sumorcontracttime.
E2032013Section4.3
4.3AnticipatedModelAuthorizedUses.IndicatebelowtheanticipatedAuthorizedUsesoftheModelfor
theProject,whichAuthorizedUseswillbeagreeduponbytheProjectParticipantsandfurtherdescribed
foreachLODinG2022013.
WithoutclearlydefinedanticipatedAuthorizedUses,theextenttowhichonePartyanticipatesusing
ModelsmaynotalignwiththeotherProjectParticipantsexpectations,resultingindisputesoverscopeand
compensation.AclearunderstandingamongtheProjectParticipantsoftheanticipatedAuthorizedUsesfor
theModelwillpreventcomplicationslaterintheProject.TotheextentthePartiescanidentifythe
anticipatedAuthorizedUsesatProjectinceptiontheywillbeabletoavoidmanyoftheseproblems.
ThissectionrecordstheanticipatedAuthorizedUsesfortheModels.Thislistwilleventuallybeincluded
withintheLevelofDevelopmentdefinitionsfoundinG2022013asthedefinedAuthorizedUseswhenthe
ProjectParticipantswillprovidemuchmoredetailontheAuthorizedUses.Forafurtherdiscussiononthe
AuthorizedUsesandLevelsofDevelopment,pleaserefertotheportionoftheGuideaddressingArticle2of
G2022013below.
ExamplesofAuthorizedUsesthatmightbeinsertedinSection4.3include,butarenotlimitedto,thefollowing:
ConstructionSequencing
ConstructionCoordination.
MaterialTakeoffsinsupportofcostestimating
Fabrication
E2032013Section4.4
4.4AncillaryModelingActivities.IndicateadditionalModelingactivitiesagreeduponbytheParties,but
notincludedinG2022013,ifany.
(DescribeanyModelingactivities,suchasrenderings,animations,performancesimulations,orothersimilar
use,includingtheanticipatedamountandscopeofanysuchModelingactivities.)
UserswillutilizethissectiontodescribeotherexpectedModelingactivities.Generally,theseModeling
activitieswillnotcarrywiththemanexpectationofrelianceforparticularuse,whichisthefocusofthe
AuthorizedUsesinSection4.3.Eventhoughrelianceisnotanissue,thePartiesneedtobeawareofwhat
thetotalscopeofexpectationsiswithregardtoallModelingactivities.Section4.4allowsthepartiesto
discussandnegotiatetheirexpectationsabout,forexample,thenumberofrenderingsthatwillbedone,or
howmanyanimationswillbecreatedfromtheModel.
E2032013Section4.5
4.5ModelProtocols
AssoonaspracticalfollowingexecutionoftheAgreement,thePartiesshall,inconsultationwiththeother
ProjectParticipantsthatareexpectedtoutilizeBuildingInformationModelingontheProject,further
describetheAuthorizedUsesoftheModelandestablishnecessaryprotocolsgoverningthedevelopmentof
theModelutilizingAIADocumentG2022013.
24
ThissectionrequiresthePartiestomeettoestablishModelingprotocolsassoonaspracticalfollowing
executionoftheAgreement.LikeE2032013Section3.2relatingtotheDigitalDataprotocols,Section4.5
purposelydoesnotestablishtheModelprotocolswithinE2032013.Thereasonsfor,andbenefitsof,such
anapproachareidenticaltothosediscussedaboveforE2032013Section3.2.
4.5.1TheModelprotocolsshalladdressthefollowing:
IdentificationoftheModelElementAuthors;
.2 DefinitionofthevariousLODfortheModelElementsandtheassociatedAuthorizedUsesfor
eachdefinedLOD;
.3 IdentificationoftherequiredLODofeachModelElementateachidentifiedProjectmilestone;
.4 IdentificationoftheconstructionclassificationsystemstobeusedontheProject;
.5 TheprocessbywhichProjectParticipantswillexchangeandsharetheModelatintervalsnot
reflectedinSection3.3,ModelElementTable,ofAIADocumentG2022013;
.6 TheprocessbywhichtheProjectParticipantswillidentify,coordinateandresolvechangesto
theModel;
.7 DetailsregardinganyanticipatedasdesignedorasconstructedAuthorizedUsesfortheModel,
ifrequiredontheProject;
.8 AnticipatedAuthorizedUsesforfacilitiesmanagementorotherwise,followingcompletionofthe
Project;and
.9 OthertopicstobeaddressedbytheModelingprotocols:
(IdentifyadditionaltopicstobeaddressedbytheModelingprotocols.)
.1
Thissectionisintendedasanillustrativelistoftopicstoconsiderforprotocols.ThePartiescanmodifyand
supplementthislistasnecessarytofittheneedsoftheirProject.Onceagreedto,theitemslistedwillbe
furtherdevelopedasprotocolsinG2022013.
ThetermsasdesignedandasconstructedrecordModelsasusedinSection4.5.1.7arebasedonthe
useofthetermsasdesignedandasconstructedrecorddrawingsinB1012007.Theinstructionsto
B1012007defineasdesignedrecorddrawingsastherecordofeverythingtheArchitectdesignedforthe
Project,andincludetheoriginalConstructionDocumentsplusalladdenda,ArchitectsSupplemental
Instructions,ChangeOrders,ConstructionChangeDirectivesandminorchangesinthework.The
instructionsdefineasconstructedrecorddrawings(orasbuilts)astherecordoftheProjectas
constructedbasedoninformationtheContractorprovidestotheOwnerunderthecontractfor
construction.BecausetheAsconstructedRecordDrawingswillbebasedontheContractorsmarkups,the
ArchitectisnotresponsiblefortheaccuracyorcompletenessoftheAsconstructedRecordDrawings.
4.5.2UnlessresponsibilityisassignedtoanotherProjectParticipantidentifiedbelow,theArchitectshall
prepareanddistributeModelingprotocolstotheotherProjectParticipantsforreview,revisionandapproval.
(IfaProjectParticipantotherthantheArchitectshallberesponsibleforpreparingdraftandfinalModel
protocols,identifythatProjectParticipant.)
ThissectionrequirestheArchitecttoprepareModelingprotocols,unlessanotherProjectParticipantis
identified.ThediscussionaboveforE2032013Section3.2.1,withtheArchitectpreparingtheDigitalData
protocols,applieshereaswell.
25
4.5.3TheagreeduponModelingprotocolsshallbesetforthinAIADocumentG2022013andeach
ProjectParticipantshallmemorializetheiragreementinwritingtosuchModelprotocols.
Section4.5.3establishestheexpectationthattheProjectParticipantswillapprovetheModelingprotocols
andwillmemorializetheminG2022013.Theimportanceofrecordingagreementisidenticaltothe
discussionaboveforE2032013Section3.2.2.(SeealsodiscussionatE2032013Section1.4.9,forthe
definitionoftheterminwriting.)
4.5.4TheParties,togetherwiththeotherProjectParticipants,shallreview,andifnecessary,revisethe
ModelingprotocolsatappropriateintervalsasrequiredbytheconditionsoftheProject.
AsisthecasewiththeDigitalDataprotocols,theProjectParticipantswilllikelyneedtorevisetheModeling
protocolsastheProjectproceeds.Thismaybebecauseneedschange,efficienciesarediscovered,or
additionalProjectParticipantsmaybeinvolved.Regardlessofthereasons,Section4.5.4allowsforthe
possibilitythattheestablishedprotocolswillberevised.Section4.5.4statesthattheProjectParticipants
willrevisitandrevisetheestablishedModelingprotocolsasnecessary.
E2032013Section4.6
4.6ThePartiesshalldevelop,useandrelyontheModelinaccordancewiththeModelingprotocolsset
forthinthelatestversionofAIADocumentG2022013,whichdocumentshallbeincludedinorattachedto
theModelinamannerclearlyaccessibletotheProjectParticipants.
Section4.6requiresthePartiestodevelop,useandrelyontheModelinaccordancewiththemostrecent
setofestablishedprotocols.ThislanguagecreatesacontractualobligationtofollowtheModelingprotocols
astheyareestablishedandagreedtobythePartiesandotherProjectParticipants.Asnotedabove,
however,theenforcementoftheprotocolsmayultimatelydependontheabilityofaProjectParticipantto
provethattheotherProjectParticipantsagreedtotheprotocols.Accordingly,inutilizingG2022013,the
ProjectParticipantsshoulddevelopanacceptableprocesstodocumentthereceiptof,andagreementto,
eachversionoftheprotocolsbyeachProjectParticipant.SuchaprocesswillhelpprotectagainstaProject
Participantultimatelyclaimingthatitneversaworagreedtothelatestversionoftherelevantprotocols
andthereforeisnotboundbythem.
Section4.6alsorequiresthePartiestoincludeacopyofthelatestversionofG2022013intheModelso
thatitisaccessibletotheProjectParticipants.Thisrequirementiseasilyaccomplishedwithcurrent
softwarecapabilitiesandensuresthatanyProjectParticipantthatreceivesaModelwillalsoreceivethe
ModelprotocolsgoverningtheuseoftheModel.
E2032013Section4.7
4.7UnauthorizedUse
4.7.1PriortoEstablishmentofModelProtocols
IfaPartyreceivesanyModelpriortotheagreementto,anddocumentationof,theModelingprotocolsin
AIADocumentG2022013,thatPartyisnotauthorizedtouse,transmit,orrelyontheModel.Anyuse,
transmissionorrelianceisatthatPartyssoleriskandwithoutliabilitytotheotherPartyandits
contractors,consultants,agentsandemployees.
26
Section4.7.1ismodeledafterE2032013Section3.4.1andtherelateddiscussionisequallyapplicablehere.
AsnotedintheSection3.4.1discussion,insomeinstancesthePartiesmaybelievethatadditionalprotection
iswarrantedandmaydecidetoincludeanindemnificationobligation.Thefollowingisanexampleofsuch
indemnificationlanguage:
Tothefullestextentpermittedbylaw,thereceivingPartyshallindemnifyandhold
harmlesstheotherPartyanditscontractors,consultants,agentsandemployeesfrom
andagainstclaims,damages,losses,andexpenses,includingbutnotlimitedtoattorneys
fees,arisingoutoforresultingfromthereceivingPartysuse,transmission,orrelianceon
suchModels.
AsnotedinthediscussionforE2032013Section1.2.1,however,anyindemnificationlanguageshouldbe
reviewedcloselywithlegalandinsurancecounselasindemnificationprovisionsarecomplexand
notoriouslydifficulttoenforce.
4.7.2Followingagreementto,anddocumentationof,theModelingprotocolsinAIADocumentG2022013,
ifaPartyusesorreliesontheModelinconsistentwiththeAuthorizedUsesidentifiedintheModeling
protocols,suchuseorrelianceshallbeatthesoleriskofthePartyusingorrelyingontheModel.APartymay
relyontheModelElementonlytotheextentconsistentwiththeminimumdatarequiredfortheidentified
LOD,evenifthecontentofaspecificModelElementincludesdatathatexceedstheminimumdatarequired
fortheidentifiedLOD.
ThejustificationforSection4.7.2isthesameasthevirtuallyidenticalprovisionsinSection3.4.2.Uponthe
documentationoftheModelingprotocols,thePartieshaveagreedthatthesharedModelscanbeusedand
reliedupononlyassetforthintheAuthorizedUsesintheprotocols.Useandrelianceinconsistentwiththe
protocolsremainsunauthorized.Accordingly,Section4.7.2statesthataftertheprotocolsareestablished,
anyuseoftheModelinconsistentwiththeprotocolsisatthesoleriskofthePartyusingtheModel.This
sectionalsoclarifiesthattotheextenttheModelcontainsinformationthatexceedstherequiredLOD,the
useorrelianceisstillcontrolledbytheAuthorizedUsesassociatedwiththerequiredLODassetforthinthe
G2022013,Section3.3ModelElementTable.Forexample,ifanLOD200ModelElementcontainsspecific
informationregardingthelocationandtypeoflightfixturetobeused,theinformationcanonlyberelied
onconsistentwithanLOD200.G2022013Section2.3.1definesLOD200tomeanthattheModelElement
isrepresentedasagenericsystem,object,orassemblywithapproximatequantities,size,shape,location,
andorientation.Therefore,eventhoughtheinformationregardingthelightfixtureisspecific,becausethe
ModelElementisindicatedtobeattheLOD200level,theinformationcannotbereliedonasspecificand
insteadcanonlybereliedontotheextentappropriateforgenericinformation.
IfthePartiesbelieveadditionalprotectionfromtherisksofunauthorizeduseisnecessary,theymayconsider
includinganindemnificationobligationfollowingthefirstsentenceinthesection.Thefollowingisanexample
ofsuchlanguage:
Further,tothefullestextentpermittedbylaw,thePartyusingorrelyingontheModelshall
indemnifyandholdharmlesstheotherPartyanditscontractors,consultants,agentsand
employeesfromandagainstclaims,damages,lossesandexpenses,includingbutnot
limitedtoattorneysfees,arisingoutoforresultingfromsuchPartysuseoftheModel
inconsistentwiththeAuthorizedUsesidentifiedintheModelingprotocols.
27
ForthereasonsnotedaboveinthediscussionforSection1.2,however,indemnificationisacomplicated
legalconceptandindemnificationlanguageshouldbereviewedcloselywithlegalandinsurancecounsel.
E2032013Section4.8
4.8ModelManagement
4.8.1TherequirementsformanagingtheModelincludethedutiessetforthinthisSection4.8.Unless
assignedtoanotherProjectParticipant,theArchitectshallmanagetheModelfromtheinceptionofthe
Project.IftheresponsibilityforModelmanagementwillbeassignedtoanotherProjectParticipant,or
changeatanidentifiedProjectmilestone,indicatebelowtheidentityoftheProjectParticipantwhowill
assumethatresponsibility,andtheProjectmilestone.
ResponsibleProjectParticipant
ProjectMilestone
MaintainingrecordsandarchivesoftheModelcomeswithalevelofresponsibilitythattheProject
ParticipantsshouldbeawareofattheonsetoftheProject.OtherProjectParticipantswillberelyingonthe
individual(s)orentity(ies)chargedwithmanagingandmaintainingtheModel.Thismayrequireanincrease
inscopeofworkfortheProjectParticipantschargedwiththisresponsibility.Theincreaseinscopeisa
factorthatmayaffectcompensationandshouldbeincludedintheAgreement.Accordingly,Model
managementisincludedinE2032013asopposedtotheG2022013.
ThissectionrequiresthePartiestoidentifytheProjectParticipantsthatwillberesponsibleformanaging
theModel.AsisthecasewiththeDigitalDatamanagementrole,theProjectParticipantresponsiblefor
managingtheModelmayshiftastheProjectprogresses.
ThestandardlanguagestatesthattheArchitectwillmanagetheModelfromtheinceptionoftheProject
andthatthePartiesmayidentifyanotherProjectParticipantthatwillsubsequentlyassumethose
responsibilities.TheArchitectisthedefaultasitistheProjectParticipantthatwillmorelikelythannotbe
engagedinthemostModelingactivitiesatthebeginningoftheProject.
4.8.2ModelManagementProtocolEstablishment.TheProjectParticipantresponsibleformanagingthe
Model,inconsultationwiththeotherProjectParticipantsthatareexpectedtoutilizeBuildingInformation
ModelingontheProject,shallfacilitatetheestablishmentandrevisionofModelmanagementprotocols,
includingthefollowing:
.1 Modeloriginpoint,coordinatesystem,precision,fileformatsandunits
.2 Modelfilestoragelocation(s)
.3 ProcessesfortransferringandaccessingModelfiles
.4 Namingconventions
.5 ProcessesforaggregatingModelfilesfromvaryingsoftwareplatforms
.6 Modelaccessrights
.7 Identificationofdesigncoordinationandclashdetectionprocedures
.8 Modelsecurityrequirements
.9 Other:(IdentifyadditionalModelmanagementprotocolstobeaddressed.)
28
TheSection4.8.2listisnotintendedtobeexhaustiveandisonlyintendedasasuggestionofcommon
protocolstoconsiderinmanagingaModel.ThestandardlistappearinginthisSection4.8.2correspondsto
thelistofprotocolsinG2022013Section1.7.TotheextenttheSection4.8.2listismodifiedtofitthe
particularneedsoftheProject,similarrevisionsshouldbemadetotheG2022013Section1.7list.
4.8.3OngoingResponsibilities.TheProjectParticipantresponsibleformanagingtheModelshalldoso
consistentwiththeModelmanagementprotocols,whichshallalsoincludethefollowingongoing
responsibilities:
.1 Collectincomingmodels:
.1 Coordinatesubmissionandexchangeofmodels
.2 Createandmaintainalogofmodelsreceived
.3 ReviewmodelfilesforconsistencywithSection4.8.2.1through4.8.2.5
.4 Maintainarecordcopyofeachmodelfilereceived
.2 AggregateModelfilesandmakethemavailableforAuthorizedUses.
.3 MaintainModelArchivesandbackupsconsistentwiththerequirementsofSection4.8.4below
.4 ManageModelaccessrights
.5 Other:(Identifyadditionalresponsibilities.)
Section4.8.3providesalistofcommonModelmanagementresponsibilitiesthatwillbeperformedonan
ongoingbasis.Thelistedresponsibilitiesarenotintendedtobeexhaustive.Itshouldbenoted,however,
thattheresponsibilitiesincludedinSection4.8.3willbecomeapartoftheAgreementandtherefore
becomecontractualresponsibilitiesfortheProjectParticipantassignedtomanagetheModel.
Ataminimum,theProjectwillrequireaModelmanagementactivitytocollect,coordinateandaggregate
Models.Thecomplexityofthistaskwillvaryfromprojecttoproject,butcouldpotentiallyincludea
sophisticatedcollaborationWebsitetofacilitatethetask.Muchdependsonthelevelofsophisticationof
theProjectParticipants,andthelevelofrelianceoneachother'swork.
Theresponsibilityfordataintegrity,includingbackups,periodicandmilestonearchiving,andlogsof
interaction,iscriticaltomaintainingthevalueandintegrityofthedatawithintheModel.
Otherresponsibilitiescouldinclude:
PreparationofvisualizationModelsonaregularbasis
PreparationofModeldataforsubmissiontoreviewingauthorities
Creatingaggregatedmaterialtakeoffs
PreparingconstructionsequencingModels
PreparingModelsubsetsforspecialtyusebyconsultantsorsubcontractors
4.8.4ModelArchives.TheindividualorentityresponsibleforModelmanagementassetforthinthis
Section4.8shallcompileaModelArchiveattheendofeachProjectmilestoneandshallpreserveitwithout
alterationasarecordofModelcompletionasofthatProjectmilestone.
29
ThissectionrequirestheProjectParticipantresponsibleformanagingtheModeltocompileandpreserve
anarchiveattheendofeachProjectmilestone.TheProjectmilestonesareidentifiedintheModelElement
tableofSection3.3inG2022013.ThePartyresponsibleformanagingtheModelisrequiredtocreateand
maintainthearchiveconsistentwiththeestablishedprotocols.
AlthoughthedefaultrequirementisthattheModelbearchivedattheconclusionofeachProject
milestone,ifsomeotherintervalfitsbetter,giventheuniquecharacteristicsofeachProject,thatshouldbe
discussedandotherarchivedatesagreedtobytheProjectParticipants.
E2032013Section4.8.4.1
4.8.4.1AdditionalModelArchiverequirements,ifany,areasfollows:
Section4.8.4.1consistsofablankfillpointthatwillallowthePartiestoincludeanyadditionalarchive
requirementsnecessarytosatisfytheuniquecharacteristicsoftheirProject.
E2032013Section4.8.4.2
4.8.4.2TheproceduresforstoringandpreservingtheModel(s)uponfinalcompletionoftheProjectare
asfollows:
ThissectionprovidesaplaceforthePartiestoidentifythemannerinwhichtheModelwillbestoredand
preserveduponfinalcompletionoftheProject.
Someoftheissuesthatshouldbediscussedincludehowlongthearchivefileswillberetained,howlongeachof
thePartiesandProjectParticipantswillbeabletohaveaccesstothearchivefiles,whobearstheresponsibility
andcostofmaintainingthearchivefiles,howthosearchivefilescanbeused,andwhatprocessesshouldbe
establishedforthedestructionofanyarchivefilesoncetherequiredretentionperiodhaselapsed.
E2032013Section4.9
4.9PostConstructionModel
TheservicesassociatedwithprovidingaModelforpostconstructionuseshallonlyberequiredif
specificallydesignatedinthetablebelowasaPartysresponsibility.
(DesignatebelowanyanticipatedpostconstructionModelandrelatedrequirements,theProjectParticipant
responsibleforcreatingoradaptingtheModeltoachievesuchuses,andthelocationofadetaileddescription
oftheanticipatedscopeofservicestocreateoradapttheModelasnecessarytoachievesuchuses.)
LocationofDetailed
Descriptionof
Requirementsand
Applicability
Services
toProject
Responsible (Section4.10beloworinan
(Applicableor
Project
attachmenttothisexhibit
PostConstructionModel
NotApplicable)
Participant
identifiedbelow)
4.9.1 Remodeling
4.9.2 WayfindingandMapping
4.9.3 Asset/FF&EManagement
4.9.4 EnergyManagement
4.9.5 SpaceManagement
4.9.6 MaintenanceManagement
30
ThissectionisutilizedonlyifthereareadditionalrequirementsforModelingbeyondthosenecessaryfor
designandconstructionexecutionasdescribedinSection3.3ofG2022013.Theserviceslistedinthis
sectionareinadditiontotraditionalbasicservices,andmaybeperformedbyanyoftheProjectParticipants
designatedintheSection4.9table.
ThissectionisdifferentfromrecordModelactivitiesorotherLODinthatthecharacteristicsofModelsused
forpostconstructionactivitiescanvarygreatly.WhilethepostconstructionModelmaybeasubsetor
extractionoftheconstructionModel,thegraphicalformat,dataformat,andspecificscopeofeffortvaries
greatlywiththeintendedpostconstructionModeluse.Accordingly,theModelingrequirementsforPost
ConstructionModelUsesdonotfitwellsimplyunderanLODdescriptionwithintheG2022013.For
example,therepresentationofwallsanddoorsforwayfindingissignificantlydifferentfromthatofenergy
managementandrequireadifferentlevelofscopedescriptiontoclarifytheintent.
TherowsofthetablelistthePostConstructionModeluses,theapplicabilitytotheProject,theresponsible
ProjectParticipant,andthelocationofthedetaileddescriptionoftherequiredservices.
Inthefirstcolumn,PostConstructionModels,commonpotentialPostConstructionModelUsesarelisted.
ThelistisastartingpointandthePartiescanaddotherpotentialusesasdesiredbytheOwner.Currently
therearenowellestablishedstandardsforeachoftheseuses,andeachOwnerorsoftwareinterfacewill
haveauniquescopeofhowtheModeldataisdevelopedandutilized.Accordingly,toclarifyexpectations,
thePartiesshouldprovideasmuchdetailaspossibleindescribingtheanticipatedservicesnecessaryto
provideaModelforpostconstructionuse.
TheApplicabilitytoProjectcolumnisspecificallyusefultoclarifyscopeandnonscopeitems.While
deletingalinemightotherwisebethesimplestwaytodeleteanonscopeitem,indicatingspecificallythat
itisnotapplicabletotheProjectistheclearestwaytoclarifyexpectations.Theaffirmativestepofmarking
anitemasnotapplicablerecordsthatthePartiesdiscussedtheissueandaffirmativelydecidedthatitwas
notapplicable.Ifthesectionweremerelyleftblank,therecouldlaterbeadisputeastowhetherthescope
waseverdiscussed.
TheResponsibleProjectParticipantistheProjectParticipantwhowillexecutetheworkontheModelas
requiredtomeetthedefinedscopeofservices.Thismaybethearchitect,engineer,contractor,fabricator
ormaterialsupplier.BecauseE2032013isintendedtobeaflowdowndocument,itisimportantthatthe
responsibleProjectParticipanthavethisdocumentattachedtotheirrelatedagreements,otherwise,itisa
nonbindingobligation.ForadetaileddiscussionabouttheprocessforincorporatingE2032013intothe
Projectagreements,pleaserefertothesectionoftheGuidediscussingE2032013Section1.2.
Thelastcolumn,LocationofDetailedDescriptionofRequirementsandServicesisutilizedtoindicate
wheretherequirementsandscopeofservices/workarerecorded.ItmaybeinSection4.10beloworan
attacheddocument.Itmayalsoindicateanexternalreferencestandard.Iftheownerhasestablisheda
standardthenitiseasilyreferencedhere.
Indescribingthescopeoftherequirementsandservices,eitherinE2032013Section4.10orasaseparate
attachmenttothisExhibit,anynumberofmethodscanbeutilized.Onetechniquewouldbetoestablisha
separatetable,mirroringthelistofmodelcontentintheG2022013Section3.3,ModelElementtable,for
31
eachofthePostConstructionModels.EachlinecouldfurtherdesignatetheresponsibleProjectParticipant
forthatindividualpieceofcontent,andprovideanotethatclearlydescribestherequirementsandscope
forthatlineofcontent.ThistechniquemayrequireaseparatetableforeachPostConstructionModel,but
mayalsobethebestwaytoestablishclearexpectationsofanownersrequirement.
ThePartiesshouldalsotakenoteofthepotentialrelationshipbetweentheidentifiedpostconstruction
Modelsandthepermissions,giventotheOwnerintheAgreement,forusesofthePartiesintellectual
property.ForexampleB1012007Section7.3givestheOwneralicensetousetheArchitectsInstruments
ofService(whichwouldincludetheModel)forconstructing,using,maintaining,alteringandaddingtothe
Project.ThislanguagemaybesufficientlybroadtoencompasstheidentifiedPostConstructionModel
uses,butitmaynot.
E2032013Section4.10
4.10InsertadetaileddescriptionoftherequirementsforeachPostConstructionModelidentifiedin
Section4.9andtheanticipatedservicesnecessarytocreateeachPostConstructionModel,ifnotfurther
describedinanattachmenttothisExhibit.
Section4.10providesafillpointforthePartiestoprovidethescopeofserviceswithrespecttoeachpost
constructionModeluseidentifiedinSection4.9.Asisalwaysthecase,thePartiesshoulddescribethe
anticipatedscopeofservicesinasmuchdetailaspossible.Doingsowillreducethelikelihoodofalater
disputeoverthescopeofservices.
Article5OtherTermsandConditions
E2032013Article5OtherTermsandConditions
OthertermsandconditionsrelatedtothetransmissionanduseofDigitalDataareasfollows:
Article5providesaspaceforthePartiestoprovideanyadditionaltermsandconditionsrelevanttoDigitalData.
32
G2012013allowstheProjectParticipantstodocumenttheDigitalDataprotocolsfortheProject,exclusive
ofspecificModelingrequirements,whichareaddressedingreaterdepthinG2022013,ProjectBuilding
InformationModelingProtocolForm.Theprotocolsareestablishedintheformdocuments,ratherthanin
theAgreement,becauseitislikelythattheprotocolswillchangeastheProjectprogresses.Iftheprotocols
wereincludedintheagreements,theProjectParticipantswouldneedtoamendalloftheiragreements
everytimetheprotocolschanged,whichwouldbeundulyburdensome.Itshouldbenoted,however,that
eventhoughtheprotocolsarenotpartoftheAgreementlanguage,E2032013,atSection3.3,
contractuallyrequiresthePartiestofollowtheprotocolsonceestablished.
ItisexpectedasthatastheProjectcircumstanceschange,theProjectParticipantwilljointlyreviseand
issueupdatedversionsofG2012013.ThiswouldbethecaseanytimeinformationcontainedinG2012013
isrevisedorexpanded.Accordingly,G2012013providesaspaceonthecoverpagetoallowthePartiesto
designateaversionnumberandadate,todifferentiatebetweennewerandolderversions.Becausethe
formcontentmaychangeovertheProjectsduration,theversionnumber,date,preparer,anddistribution
fieldsshouldbeupdatedasneeded.Forexample,astheProjectmovesintoconstruction,thelistofProject
Participantsresponsibleforcreating,transmittingandreviewingDigitalDatawilllikelygrowandchange
significantly,andthedistributionlistshouldreflectthecurrentProjectParticipants.
UsersmustalsobeawarethatpursuanttoE2032013Section1.3,iftheprotocolsestablishedinG201
2013willresultinachangeinthescopeofworkorserviceswarrantinganadjustmentincompensation,
contractsum,scheduleorcontracttime,theusermustsatisfythenoticerequirementsetforthin
Section1.3.3inordertorequestanadjustment.ThestandardprovisioninE2032013Section1.3requires
30dayswrittennotice,althoughusersarepermittedtoprovideadifferenttimeperiodforthenotice
requirement.RefertothediscussionofE2032013Section1.3formoredetail.
Article1GeneralProvisionsRegardingUseofDigitalData
G2012013Section1.1
1.1ListeachProjectParticipantthathasincorporatedAIADocumentE2032013,BuildingInformation
ModelingandDigitalDataExhibit,dated________,intoitsagreementfortheProject:
ProjectParticipant
Discipline
TheSection1.1table,whencompleted,providesacompletelistofeachProjectParticipantthathas
incorporatedE2032013intotheirProjectAgreement.ItisimportantforeachProjectParticipantthatwill
utilizeDigitalDatatoincorporateE2032013intotheiragreementsbecauseE2032013Section3.3provides
thecontractualobligationtousetheDigitalDataconsistentwiththeprotocolsestablishedinG2012013.If
DigitalDataisprovidedtoaProjectParticipantthathasnotincorporatedE2032013intoitsagreement,the
protectionsagainstunauthorizeduseestablishedintheprotocolscouldbelost.Itwillalsobeimportantfor
theProjectParticipantstokeepthistableupdatedandissueupdatedversionsofG2012013everytimea
newProjectParticipantisaddedtothislist.
Rev. 052213
33
G2012013Section1.2
1.2ProjectParticipants.ForeachProjectParticipantlistedinSection1.1,identifyandprovidecontact
informationfortheindividualsresponsibleforimplementationoftheDigitalDataprotocols.
ProjectParticipant
IndividualResponsible
ContactInformation
TheProjectParticipanttablefoundinSection1.2isacontinuationofthediscussionanddecisionmaking
processthatbeginsinSection1.1.Thissectionrequiresthedocumentuserstoidentify,foreachProject
Participant,theindividualsresponsibleforimplementationoftheDigitalDataprotocols.Thistableprovided
canbeexpandedasneeded.
AtypicalProjectmaybeginwiththeOwnerandArchitectsharingdigitalprogramming,designconcepts,
andbudgetinginformation.AstheProjectprogresses,additionalconsultants,contractorsandpossiblysub
contractorsandsuppliersmaybeadded.Asprojectsmovethroughspecificphases,theassignmentof
DigitalDataresponsibilitiesmaychangewithinanorganization.Careshouldbetakentokeepthistable
currentandaccuratetomaintaintheseamlesstransferofinformation,whichwillrequiretheissuanceof
updatedversionsofG2012013asnecessary.
Thefollowingisanexampleofhowthistablemaybefilledout:
ProjectParticipant
AQAArchitects
SDSEngineering
FMDConstruction
JohnSmith
SusanBrown
DavidMorse
ContactInformation
JSmith@AQA.com;2125552323
SBrown@SDSENG.com;3015550987
DMorse@FMDcon.com;2125553477
G2012013Section1.3
1.3TermsinthisdocumentshallhavethesamemeaningasthoseinAIADocumentE2032013.
Bythiscrossreference,theProjectParticipantsrecognizetheuseoftheterminologyfoundinE2032013,
includingsuchtermsasDigitalDataandProjectParticipant.Termswithspecializedmeaningsare
generallydefinedandcapitalizedinAIAContractDocuments.
Article2DigitalDataManagementProtocols
G2012013Section2.1.1
2.1.1ElectronicDocumentManagementSystem.If,pursuanttoSection3.5.1oftheProjectspecific
versionofAIADocumentE2032013,theProjectParticipantsindicatedanintenttouseacentralized
electronicdocumentmanagementsystemontheProject,therequirementsforthecentralizedelectronic
documentmanagementsystemareasfollows:
(Therequirementsforthesystemshalladdress,amongotherthings,accesstoandsecurityofDigitalData.)
Thissectionrequiresidentificationofanycentralizedelectronicdocumentmanagementsystemor
program.Thereareawidevarietyofoptionsastotheselection,creationandmanagementofsuchProject
basedsystems.ThepotentialimpactonaProjectParticipantsnormalmethodsfordocumentstorageand
managementmakesthismatteranimportanttopicfordiscussion.
34
Theselectedcentralizedelectronicdocumentmanagementsystem,ifany,canbeassimpleorcomplexas
theProjectforwhichitisbeingused.Often,thetypeandvolumeofsharedDigitalDataandthenumberof
ProjectParticipantswillsuggesttheoptimalsolution.SomethingassimpleasasharedFTPsitewherefiles
canbepostedandaccessedmaybeallthatisneededforcertainProjects.AsProjectcomplexityincreases,
asystemwithadditionalcapabilitiessuchascommenting,versioncontrol,accessloggingandother
featuresmaybebeneficialtoserveasacentralizedProjectrecordthatallProjectParticipantscanaccess
andutilize.Itmayalsobeappropriatetomaintainseparatesystemsfordistincttypesofelectronic
documents.Forexample,drawingdatamaybeononesystemmanagedbytheArchitectwhile
correspondenceandnongraphicdataismaintainedontheOwnerssystem.Article2providestheProject
Participantswithanopportunitytosetforththespecificrequirementsofanysuchmanagementsystem.
Becauseavailablesoftwareandsystemrequirementscontinuallyevolve,itisimportanttogainacceptance
fromtheProjectParticipantsontheappropriatesystemfortheProject.Whatmaybestandardpracticefor
oneProjectParticipantmayrequireaconsiderablelearningcurveforothers.Accordingly,due
considerationshouldbegiventosystemcostandthelevelofeffortnewusersmayneedtogetuptospeed.
ForthebenefitoftheProject,suchconsiderationsshouldoccurasearlyaspossible.
Examplesofissuesthatmayneedtobeaddressedinthissectionduringtheidentificationoftheappropriate
systemcouldincludethefollowing:
AccessrightstosubmittalsorotherrecordsaftertheProjectisconcluded,includingtimeperiod
forsuchaccess
Rightstopost,alter,viewandarchivethedata
Ownershipofsuchadocumentmanagementsystem
WhencompletingArticle2,inadditiontoconsideringtheoperationofthecentralizedelectronicdocument
managementsystem,thePartiesshouldalsofocusondocumentingwhatthesystemisintendedtoachieve
andhowthesystemwillimpacttheroleoftheProjectParticipants.Forexample,theselectionofa
proprietarysoftwaresystemasthemanagementsystemmayrequireuserstopurchasealicenseorimpact
theirabilitytogainaccessfromoffsite.
Article2containsaseriesoffillpointsrelatingtosystemdocumentation,startup,andongoing
requirements.Althoughusingthefillpoint(s)isrecommended,itmaybeappropriatewherelargeamounts
ofinformationwillbeprovided,toincludeasummaryoftheinformationinG2012013andalsoreference
aseparatedocumentcontainingmoredetailedinformation.
2.1.2SystemStartupRequirements.Initialtrainingandotherstartuprequirementstobeimplemented
withrespecttotheuseormanagementofDigitalData,ifany,areasfollows:
(Describeindetailanyinitialtrainingorotherstartuprequirements.)
ThissectionrequiresthePartiestodescribetrainingrequiredforanycentralizedelectronicdocument
managementprogramorsystemutilizedontheProject.Ifthesystemselectedin2.1.1aboveisasimple
Webbasedfilesharingutility,thetrainingandaccessrequirementsmaybenegligible.Anexampleofsuch
languagewouldbeasfollows:
TheArchitectwillprovideaonehalfdayDigitalDataorientationforallProjectParticipants.
35
Ifthesystemiscomplex,significantstartupeffortsmaybenecessary.Anysuchoutsidetraining,special
hardware,orsoftwarerequirementsshouldbestated.Additionally,trainingmaybenecessarytobring
otherProjectParticipantsuptospeedonaparticularprogramtobeabletoworkwiththeothers.Ifthe
selectedsystemisalreadyinusebysomeoftheProjectParticipants,theneedfortrainingmaynotbe
evenlydistributedamongtheotherProjectParticipants.
2.1.3OngoingSystemRequirements.Ongoingtrainingorsupportprogramstobeimplementedwith
respecttotheuseormanagementofDigitalData,ifany,areasfollows:
(Describeindetailanyongoingtrainingorsupportprogramstobeimplemented.)
IndividualProjectParticipantsmayemploystaffwiththeexpertisetoprovidetrainingormaintenancefor
selectedsystems,inwhichcasetheircontractscopeandcompensationmayrequireamendmentifthey
becomeresponsibleforprovidingsuchservices.Somesystemsaremaintainedbyoutsidevendorsonafee
basis,orrequireindependentdigitalresources.IftheseitemsarepartoftheProjectrequirements,they
shouldbedescribedintermsofwhowillprovidetheservices,whichProjectParticipantwillengagethe
vendor,andhowlongtheserviceswillbeinplace.
G2012013Section2.2
2.2DigitalDataStorageRequirements.TheproceduresandrequirementsforstoringDigitalDataduring
thecourseoftheProject,ifany,areasfollows:
(DescribeindetailtheproceduresandrequirementsforstoringDigitalDataduringthecourseoftheProject.)
Thepotentialtopicsunderthissectionarequitenumerous.DigitalDatamaybestoredonasingleProject
Participantsserver,onmultipleProjectParticipantsservers,hostedbyanoutsideprovider,ora
combinationofthesemethods.TheProjectParticipantsshoulddiscusshowtheDigitalDatawillbestored,
savedandaccessedbyeveryoneinvolved.ItwouldservetheProjectwelltohaveadetailedexplanationof
howthisisachievedwhilealsomaintainingthefreeflowandintegrityofDigitalData.Furthermore,the
requirementsestablishedinthissectionneedtobecoordinatedwithanycentralizedelectronicdocument
managementsystemidentifiedinSection2.1.1above.
G2012013Section2.3
2.3DigitalDataArchivingRequirements.Theproceduresandrequirementsforarchivingandpreserving
DigitalDataduringthecourseoftheProjectandfollowingfinalcompletionoftheProject,ifany,areasfollows:
(DescribeindetailtheproceduresandrequirementsforarchivingandpreservingDigitalDataduringthe
courseoftheProjectandfollowingcompletion.)
ThissectionrequiresidentificationofproceduresandrequirementsforstoringDigitalDataduringthe
ProjectandaftertheProjectiscompleted.Therearenumerousapproachesforaccomplishingthistask.A
commonsolutionistorequirearchivingofallProjectDigitalDataatspecifiedProjectmilestonesrecognized
byallProjectParticipants;orarchivingrequirementsbetweentwoPartiescouldoccurinparallelwith
deliverablesasspecifiedintheiragreements.Howeverthescheduleandprocessofarchivingaredecided,
theProjectParticipantsshouldunderstandthatthisarchivebecomesaProjectrecordandanyagreedto
processshouldprovideappropriatemeasurestomaintainsecurity,accessandintegrity.
36
Someoftheissuesthatshouldbediscussedincludethefollowing:(1)howoftentheDigitalDatawillbe
archived,(2)howlongthearchivefileswillberetained,(3)howlongeachoftheProjectParticipantswillbe
abletohaveaccesstothearchivefiles,(4)whowillbeartheresponsibilityandcostofmaintainingsuch
archivefiles,(5)howthearchivefilescanbeused,and(6)whatprocessesshouldbeestablishedforthe
destructionofanyarchivefilesoncetherequiredretentionperiodhaselapsed.
G2012013Section2.4
2.4OtherDigitalDataManagementprotocolrequirements,ifany,areasfollows:
(Describeindetailanyotherrequirements.)
ThissectionprovidesaplacefortheProjectParticipantstoidentifyanyotherrequirementsforDigitalData
management,ifany.
Article3TransmissionandUseofDigitalData
Article3isusedtodefinethetransmissionmethodsandAuthorizedUsesoftheProjectsDigitalData.The
assumptionofthisarticleisthatvirtuallyeveryProjectcommunicationcanbetransmittedandusedin
digitalform,althoughitiscertainlynotarequirement.Article3iscomposedoftwosections:atableto
identifytheDigitalDatathatwillbetransmittedandused,andasectionthatprovidesdefinitionsofthe
termsusedinthetable.WithsomanyDigitalDataandcommunicationoptionsavailable,itiscriticalto
establishwhichsystemormethodwillbeusedforeachfunctionsoastostreamlineworkprocesses
betweenProjectParticipantsandpreventlossofDigitalDataintegrityduetoincompatibility.
G2012013Section3.1
Section3.1consistsoftheDigitalDataProtocoltable,whichiscomposedoffivecolumns:
DigitalData.ThiscolumnidentifiestheProjectdocument,record,orcommunicationthatisgoverned
bytheprotocol.TheDigitalDatacolumnisprepopulatedwiththeProjectitemsthataremostlikely
tobefoundontheProject.Becauseeveryprojectisunique,however,thelistshouldbeconsideredas
astartingpointandtheProjectParticipantsshouldadd,clarify,anddeleteitemstoreflectthespecific
Projectscircumstances.
DigitalDataFormat.Thisisgenerallyasoftwarespecificdesignation,orafiletypethatiscompatible
withmultiplesoftwareplatforms.Animportantissuetoconsideristheabilitytomodifythefilewhen
selectingDigitalDataformats.CertainDigitalDatawill,byvirtueofitsphaseintheProject,require
modificationasapartofitsAuthorizedUse,whileotherDigitalData,suchasagreements,shouldbe
transmittedinaformatthatpreventsmodification.
TransmissionMethod.Thetransmissionmethodisthemeansbywhich,eitherelectronicorphysical,
theDigitalDatawillbeexchangedbetweentheProjectParticipants.Recordablemedia,email,File
TransferProtocol(FTP),aswellasavarietyofproprietarysoftwareinterfacesthatemploysimilar
strategiesarelikelycandidatesforuseasatransmissionmethod.Thetransmissionmethodshould
provideanappropriatelevelofverificationoftransmittalandreceiptcommensuratewiththetypeof
DigitalDatabeingtransmitted.
37
AuthorizedUses.TheAuthorizedUsesindicatethepermittedusesfortheDigitalDatathatistransmitted.
Asexamples,Section3.2listsfourpossibleoptionsforAuthorizedUses,fromthelimited(StoreandView),
tothecomplete(Modifyasrequired).ThedistinctionsallowtheusertocontrolthewaytheDigitalData
willbeviewed,reproduced,distributed,incorporatedormodifiedbyotherProjectParticipants.Many
Projectvariableswilldeterminetheappropriaterestrictionoruseofthetransmittedfile.Notealsothat
someDigitalDatamayhavemorethanonepermitteduse.AuthorizedUsesshouldnotbeinconflictwith
theunderlyingagreementsbetweenthePartiesutilizingthisprotocol.Forexample,theArchitects
InstrumentsofServicehavespecificusesandownershiprightssetforthintheprimeagreement.
Notes.TheNotescolumnallowstheusertoprovideclarificationoftheitemscontainedintheprevious
columns.Forexample,thetableassumesthatthereisnospecificauthorofthelistedDigitalData,butifan
itemwillbeauthoredbyaparticularPartyorProjectParticipant,thenotescolumncanbeusedto
designatethatresponsibility.Anotherexamplemaybetonotethatahardcopyistofollowall
transmissionsofaparticulartypeofDigitalData.Further,thenotescouldbeusedtocaptureparticular
nuancesthatcannototherwisebecapturedintheAuthorizedUsescolumn.Rememberthatitisnot
necessary,however,torerecordresponsibilitiesthataredelineatedelsewhereintheProjectagreements.
AnimportantconcepttounderstandabouttheSection3.1tableisitsflexibility.Whilethetableispre
populatedwithdatathatislikelytobeconveyedinadigitalformat,bynomeansshouldoneconstruethat
thisiseitherthelimitofDigitalDataorthatalloftheitemsinthetablemustbeprovidedindigitalformat.For
example,asmallscaleorsimpleprojectmightonlyutilizeDigitalDataforcommunicationsviaemailwiththe
balanceexecutedutilizingtraditionalcommunicationmeans.Inthisinstance,theusercandesignateinthe
Section3.1tablethattheotheritemswillbeprovidedinanondigitalformat,asshownbelow:
DigitalData
3.1.1 ProjectAgreementsand
Modifications
3.1.2 Projectcommunications
Generalcommunications
Meetingnotices
Agendas
Minutes
Requestsforinformation
DigitalData Transmission Authorized

Format
Method
Uses
EM
EM
PDF
PDF
EM
EM
EM
EMA
EMA
EMA
Notes
(Enter#)
R
S
S
S
R,I
NonDigitalData
Alternatively,userscandeletethesectionsfromthetablethatdonotapply,asintheexamplebelow.
DigitalData
3.1.1 ProjectAgreementsand
Modifications
3.1.21Projectcommunications
Meetingnotices
Agendas
Minutes
DigitalData Transmission Authorized

Format
Method
Uses
EM
EM
PDF
PDF
EM
EM
EM
EM
EM
EM
R
S
S
S
R,I
Notes
(Enter#)
38
Ontheotherhand,becausetheinformationispresentedinaneditabletable,itiseasytoaddadditional
rowstoincludeotherDigitalDatathataProjectmightrequire,asisdonebelow.
DigitalData
3.1.21Projectcommunications
Meetingnotices
Agendas
Minutes
DraftforReview
FinalforRecord
DigitalData
Format
EM
EM
PDF
MSW
PDF
EM
Transmission
Method
EM
EM
EM
EMA
EMA
EM
Authorized
Uses
R
S
S
M
S
R,I
Notes
(Enter#)
TheSection3.1tableisintendedtobecompletedutilizingshorthandabbreviationsandNotesthatare
definedinSection3.2.EachcolumnintheSection3.1tablehasacorrespondinglistofdefinitionsthatare
intendedtosimplifythecompletionoftheSection3.1table.StandardizingtheDigitalDataFormat,
TransmissionMethodandPermittedUsesbenefitsalloftheProjectParticipantsbycreatingauniform
expectationforcommunication.
G2012013Section3.2
3.2DigitalDataProtocolTableDefinitionsandNotes
Section3.2isusedtodefinetheshorthandelementsthatpopulatetheDigitalDataProtocolTable.Except
fortheDigitalDatacolumn,eachofthecolumnshasacorrespondingsectioninSection3.2thatshouldbe
completed.Section3.2servesasthekeytotheabbreviations,acronyms,initialismsandnotesusedinthe
Section3.1table.
Section3.2providestermsthatarecommonlyusedandabbreviationsforthoseterms.Thisdoesnotmean
thattheProjectParticipantsmustuseanyorallofthesuggestedterms.Thelistsshouldbecustomizedto
matchthespecificpracticeandrequirementspresentedbytheworkathand.Themostimportant
considerationincompletingthesesectionsoftheformistoavoidneedlesslyrestrictingtheflowof
information.Thereisanaturaltendencytoovercompletethetablewithveryspecificsoftwarerequirements,
transmissionproceduresandusagepermissionsthatmaynotsupporttheflowofcommunicationthatis
criticaltoprojectsuccess.Additionally,thetableinsection3.1shouldnotbeviewedasacompletelistof
DigitalDataavailableorrequiredfortheProject.Thelistshouldbeviewedasasubsetofdeliverablesrequired
andismeanttoestablishefficienciesincommunicationbetweenProjectParticipantswherepossible.
DigitalDataFormat
TodaysprojectsgenerateDigitalDatainamyriadofformats.Architects,consultingengineers,contractors
andotherswillcompletetheworkutilizingavarietyofhardwareplatformsandsoftwareapplications.The
DigitalDataFormatsectionisintendedtoestablishthecompatibilityofagivenpieceofDigitalDataamongst
theProjectParticipants.Themostubiquitousexampleofthiswouldbeemailwhichisalmostuniversally
compatibleacrossplatformsandapplications.Atwoorthreeletterabbreviationmaybeusedinthetable:
EMEmail
39
Manycommunicationsarelikelytobeconducteddirectlyviaemail.Forcommunicationsrequiringamore
formalpresentation,forexamplemeetingminutes,adocumentattachedtoanemailmayberequired.In
ordertoassurethatallProjectParticipantscanutilizethatDigitalData,aMicrosoftWordCompatible
formatmayberequiredintheinstancewhereaneditablefileisdesired:
MSWMicrosoftWordCompatible
Ifanoneditableformatisdesired,theusermightutilizethisdesignation:
PDFPortableDocumentFormat;AdobeAcrobatorcompatible
ForcertainDigitalData,compatibilitymaynotbegoodenough.Inthoseinstances,uniformitymaybethe
mostimportantcharacteristic.Forexample,inaBIMenvironment,boththesoftwareandtheversionmust
beuniformamongsttheparticipantsinordertomaximizethebenefitsthattoolaffords.Inthisinstancethe
designationmightbeasfollows:
RVTAutodeskRevit2011
Anotherexamplewhereuniformitymaybeimportantistheelectronicreviewofshopdrawings.Some
commonlyusedsoftwareplatformstracktheannotationsofaseriesofreviewersandalloweachtobe
distinguishedfromtheothers,buttheProjectcanonlybenefitifalloftheProjectParticipantsutilizethe
samesoftwaretool.Inthisinstancethedesignationmightbeasfollows:
BBMBluebeamRevu
TheDigitalDataformatmayalsodependonthespecificAuthorizedUse.Nevertheless,thetableandthis
Section3.2aresufficientlyflexibleforuserstodevelopaformatthatissufficienttoaddresstheirneeds.
TransmissionMethod
ThevariousmethodsbywhichDigitalDatamaybetransmittedarecontinuouslychanging.Theentriesthat
areprovidedinthissectionarethemostprevalentpossibilities,butofcoursetheusercanaddanddelete
tosuittheProjectsspecificrequirements.Thoughtshouldbegiventotheimportanceofverification,both
transmittalandreceipt,ofanyspecificitemofDigitalDatatransmission.Forsomeitemsitmaybe
importanttorecordwhentheDigitalDatachangedhands.Thepreviouslymentionedelectronicshop
drawingreviewprocessisanexcellentexampleofaninstancewherethiskindofaccountingisimportant.
TheTransmissionMethodselectedforsubmittalsshouldprovidethiscapability.
SomeProjectsmayutilizeWebbasedprojectmanagementsoftwaretowhichalloftheProjectParticipantshave
access,providingtheabilitytodownloadanduploadDigitalDataaswellasprocessRequestsforInformation
throughthesoftwareitself.Byemployingprojectmanagementsoftware,theProjectParticipantsshouldtake
careinestablishingwhowillmanagethesoftware,howtheDigitalDatawillbehosted(internallyorbyanentity
externaltotheProject)aswellaswherethosecostswillbeassigned.Thisshouldbecoordinatedwithany
centralizedelectronicdocumentmanagementsystemreferencedinG2012013Article2.
Filesizeisanotherimportantconsiderationinselectingatransmissionmethod.Almosthandinhand,
internetspeedshaveincreasedwiththefilesizesgeneratedbyvarioussoftwareproducts.Nonetheless,
mostemailsystemsplacelimitsonindividualattachmentsandoverallmailboxsizes.Utilizingemail
attachment(EML)asameansofdispersinglargefilesisprobablynotthemosteffectivemeansavailable.
40
Lastly,whenconsideringTransmissionMethod,considertheattentionthattheDigitalDatawarrants.Emailis
theprevalentmeansofprojectcommunicationanditisnotuncommonforlargeprojectstogeneratetens,if
nothundredsofthousandsofemails.Determininghowtodifferentiatecriticalinformationfrommoreroutine
informationisverydifficult.Rememberthatthegoalistocommunicatewithappropriatedocumentation.
AuthorizedUsesofDigitalData
TheAuthorizedUsesoptionssettherulesforuseof,andrelianceon,theDigitalDatabytheProject
ParticipantreceivingoraccessingtheDigitalData.NotethatitisverypossiblethatsomeProjectDigital
DatamaybedistributedtomultipleProjectParticipants,eachofwhommayhaveadifferentpermitteduse.
Ifthatisthecase,theProjectParticipantswouldbewellservedtomakeuseoftheNotescolumnto
indicatesuchdistinctionsandnuancesregardingtheAuthorizedUses.
Notes
NotesshouldbedesignatednumericallyinthetableanddescribedindetailintheNotesfillpointin
Section3.2.Thisconventionprovidesflexibilityincompletingthetable.Aspreviouslydiscussed,
responsibilityforauthorshipisalikelytopictobeincludedinthenotescolumnasshowninthisexample:
Digital Data
3.1.2 Projectcommunications
Minutes
Data Format
PDF
Transmission
Method
EMA
Authorized
Uses
Notes
(Enter#)
Wherenote1isdefinedinSection3.2asfollows:
1. Author:DesignPhaseArchitect;ConstructionPhaseContractor
41
E2032013recordsthePartiesintentionsregardingtheuseofModelingontheProject,theAnticipated
UsesoftheModelandotherbasicassumptionsabouttherolesandresponsibilitiesoftheParties.E203
2013alsocontractuallyobligatesthePartiestodiscuss,establish,andfollowprotocolsforthedevelopment
anduseofModelsontheProject.G2022013isanextensionof,andconsistentwith,thoserecorded
intentions.Theprotocols,however,arenotincludedintheactualAgreementbecauseitisverylikelythat
theprotocolswillneedtoevolveastheProjectprogressesandmoreProjectParticipantsutilizetheModel.
RequiringtheProjectParticipantstoamendalloftheiragreementseverytimetheprotocolschangewould
beburdensomeandunrealisticfromapracticalstandpoint,andwouldprovidenorealbenefit.
ItisexpectedasthatastheProjectcircumstanceschange,theProjectParticipantwilljointlyreviseand
issueupdatedversionsofG2022013.ThiswouldbethecaseanytimeinformationcontainedinG2022013
isrevisedorexpanded.Accordingly,asisthecasewithG2012013,G2022013includesafillpointtoallow
thePartiestodesignatearevisionnumberanddatetodifferentiatebetweennewerandolderversionsof
theBuildingInformationModelingprotocols.
UsersmustalsobeawarethatpursuanttoE2032013Section1.3,iftheprotocolsestablishedinG202
2013willresultinachangeinthescopeofworkorserviceswarrantinganadjustmentincompensation,
contractsum,scheduleorcontracttime,theusermustsatisfythenoticerequirementsetforthinSection
1.3.3inordertorequestanadjustment.ThestandardprovisioninE2032013Section1.3requires30days
writtennotice,althoughusersarepermittedtoprovideadifferenttimeperiodforthenoticerequirement.
G2022013Section1.1
1.1ForeachProjectParticipantthathasincorporatedtheProjectspecificAIADocumentE2032013,
BuildingInformationModelingandDigitalDataProtocolExhibit,dated________,intoitsagreementforthe
Project,identifyandprovidethecontactinformationforindividualsresponsibleforimplementationofthe
Modelingprotocols.If,foranyProjectParticipant,morethanoneindividualwillberesponsiblefor
implementationoftheModelingprotocols,listeachindividualseparatelyanddescribetheunique
ModelingRoleassignedtoeachindividual.
ModelingRole
ProjectParticipant
ContactInformation
EachProjectParticipantintheModelingprocesshasaroleandresponsibility.Completingthetableinthis
sectionclearlyarticulatesthoserolesandprovidesthecontactinformationtofacilitatethisimportantpart
oftheplanningprocess.TheProjectParticipantistheentitythathasincorporatedE2032013intoits
AgreementandisfortheidentifiedModelingRole.TheIndividualResponsibleistheactualnamedperson,
andtheprimarypointofcontactforthatparticularModelingRole.ContactInformationshouldinclude
informationsuchasaddress,andmoreimportantly,correspondenceinformationdeemedappropriatefor
timelyandefficientcommunication,suchastelephonenumbers,mobilenumbers,andemailaddresses.
Thistableisakeyexampleoftheevolutionarynatureofthisdocument.IntheearlystagesoftheProject,the
informationmaybelimitedtogeneralscopesofworkandthedesignationofafirmsresponsibility.Asthe
Rev. 052213
42
designprogressesandModelingbegins,thetablewillbepopulatedwithspecificresponsibleindividualsand
thelistofModelingRoleswillgrow.
ThetablecanbeextendedtocontainanynumberofindividualsthathaveaseparateModelingRole.Itmay
bethatasinglefirmallocatesresponsibilityfordifferentportionsofModelingprotocolstomultiple
individuals.Eachwouldberecordedonaseparateline.ThekeyistoclearlyindicatetoalltheProject
Participantswhothegotopersonisforeachareaofresponsibilityandcontactthatperson.
G2022013Section1.2
1.2ThisdocumentestablishestheModelingprotocolsfortheProject.Forpurposesoftheseprotocols,
theModeliscomprisedofthefollowinginformationandotherdatasets:
(Indicatedisciplines,separatemodels,andotherdatathatwillbeincludedwithintheModelandgoverned
bytheModelingprotocols.)
InadditiontothefundamentalModelElementswithintheportionsoftheProjectthataremodeled,the
Modeliscomprisedofseparatedatasetsandothernongeometricdata.Section1.2allowstheProject
ParticipantstodefineexactlywhatisincludedintheModelforpurposesoftheModelingprotocols.This
sectionisnecessarygiventhevastamountofdifferentinformationthatcanbeincludedin,attachedto,or
referencedinModels.LargeandcomplexProjectswillalsolikelyresultinmultipleModels,oraggregations
ofModelsthatincludediscreteportionsoftheProject.Section1.2allowstheProjectParticipantstowork
fromacommonunderstandingastowhatisincludedintheModelandtherefore,whatisgovernedand
definedbytheModelingprotocols.Accordingly,whenaProjectParticipantindicatesthataModelElement
isdevelopedtoaLevelofDevelopment(LOD)300,theotherProjectParticipantsunderstandthatallthe
variousitemslistedinthissection,whichareconsideredtobepartoftheModelElement,arealso
developedtoLOD300(SeealsogeneraldiscussionofLODdefinitionsG2022013Article2.)
Indeterminingwhatshouldbeincluded,itmaybeworthwhiletoaddresstheexpectedAuthorizedUsesof
theModel,whichwillhelpestablishtheappropriateLODlevel.Inmanyinstances,theAuthorizedUsewill
informwhatinformationshouldbeincludedintheModel.Usersshouldalsobeawarethatthissectionmay
beapproacheddifferentlydependingontherelativesizeand/orcomplexityoftheProject.
ExamplesofinformationthatmaybeincludedinSection1.2areasfollows:
ArchitecturalModels
MEPModels
StructuralEngineeringModels
LinkedCostdatabases
Specifications
OperationsandMaintenanceManuals
EnergyEfficiencyRelatedInformation
EnergyAnalysisModels
G2022013Section1.3
1.3CollaborationProtocols.TheProjectParticipantsprotocolsforthecollaborativeutilizationofthe
Model,ifany,includingcommunicationsprotocols,acollaborationmeetingscheduleandcolocation
requirements,areasfollows:
43
Thecollaborationstrategyhasbeenmadeafillpointsothatindividualteamscanrecordtheirpreferences
forprojectinitiation,ongoingcollaboration,andregularformsofcommunication.Keepinmindthatthese
activitiesarelimitedtothecollaborativeusesoftheModel.Thedocumentanticipatestheneedfor
establishingameansofcommunicatingchangestotheModel,schedulingmeetingsfortheProject
ParticipantstodiscussthetechnicalaspectsofModelingandthepotentialofphysicalcolocation.Other
itemsthatmightbeincludedhereincludedatahostingstrategies,wideareanetworkingorotheractivities
ortechnicalimplementationsthatfacilitatecollaborativeutilizationoftheModel.IfaProjectParticipant
hasapreestablishedcollaborationstrategy,itmaybereferencedasnecessaryinthissection.
Thissectioncanbeasdetailedasisnecessarytodescribethestrategy,ormaybeusedasthepointto
recordreferencetoaseparatedocument.
BecausesomeofthesedecisionscanhaveasignificantimpactontheProjectParticipantsactivities,strategies
orcollaborationrequirementsshouldbefullydescribed.IfthestrategyfortheProjectincludesProject
Participantsbeingcolocated,space,equipment,lodgingandotherfactorswillneedtobeaddressed.
G2022013Section1.4
1.4TechnicalRequirements.ThetechnicalrequirementsrelatingtotheutilizationofBuildingInformation
Modeling,includingspecificsoftwareandhardwarerequirementsareasfollows:
TheProjectParticipantswillutilizeSection1.4todescribeanysoftwareandhardwarerequirementsforthe
ModelingfortheProject.Ataminimum,thesoftwareandreleaseversionthatwillbeusedforModeling
shouldbeestablished,butitislikelythattherewillbeavarietyofusesfortheModel,someofwhichmay
requirespecificsoftwarecapabilities.Usessuchassharedvisualization,fabrication,constructionmodel
aggregation,energyperformanceanalysis,schedulingandestimatingareallpossibleinstanceswherea
specifictechnicalcompatibilitymaybeimportant.
Projectspecifichardwarerequirementsshouldalsobeindicatedhere,especiallyifitisasharedpieceof
hardwaresuchasthoseusedonsiteorprovidedforacolocationteam.Anotherexamplewouldbethe
anticipateduseofmobiletechnologiesforcollaborationsoftware,visualrecordingandrecordsaccess.
G2022013Section1.5
1.5TrainingandSupport.Theparametersforanytrainingorsupportprogram(s)thatwillbe
implementedwithrespecttoanycollaborationstrategyortechnicalrequirementsaresetforthbelow:
BecausetheuseofModelingisstillintheadoptionphaseswithintheindustry,thecollaborative
opportunitiesitpresentsareevolving.WhileindividualProjectParticipantswillhavetrainingandworkflow
processanalysistocompleteinordertoparticipatefullyintheProject,theProjectParticipantsasagroup
mayalsoneedtocompleteasimilarundertakinginordertocollaborateaseffectivelyaspossible.The
processesandunderlyingsoftwaremayrequiretraining,support,andspecificcapabilitiestoimplement
andmaintain.Forexample,theProjectParticipantsmaychoosetohavetheentireteam,includingkey
subcontractorsandownerrepresentatives,participateinaModelingorientationclassdesignedtoset
expectationsforgeneralModeluses.Or,theOwnermayhaveaspecificoperationsandmaintenance
programthattheArchitectandtheContractorarerequiredtounderstandandtoalignwithastheModelis
produced.IftheProjectParticipantsdonotanticipateanynewtrainingorsupporttoimplementthe
collaborationstrategiesthisshouldbenotedaswell.
44
G2022013Section1.6
1.6ModelStandard.TheModelshallbedevelopedinaccordancewiththefollowingModelStandard,ifany:
StandardsservedanimportantroleintheadoptionofComputerAssistedDesign.Itisunclear,however,
whatrolestandardswillplaywithregardtoModeling.Thereare,infact,proposedindustrywidestandards
beingdeveloped,andsomeindustryprofessionalsandownershavedevelopedtheirownModeling
standards.TheNationalBuildingInformationModelStandardsorNBIMS,maybecomeawidelyused
standardasitdevelops.Otherentitiesmayproducesimilarorcompetingstandardsandthemarketplaceis
continuallyevolving.
TotheextentthataspecificstandardisutilizedacrosspartsortheentirespectrumoftheProject,itshouldbe
recordedhere.Thisclarifiesexpectations,andreducesinefficiencywhencoordinatedearly.ModelStandards
shouldbecoordinatedwithAuthorizedUsesandsoftwareandhardwarerequirementstoassurecompatibility.
G2022013Section1.7
1.7ModelManagementProtocolsandProcesses.ThefollowingModelManagementProtocolsand
ProcessesshallapplytotheProjectonlyifspecificallydesignatedinthetablebelowasbeingapplicable.
(DesignatetheModelManagementProtocolsandProcessesapplicabletotheProjectinthesecondcolumn
ofthetablebelow.Inthethirdcolumn,indicatewhetherthedetaileddescriptionoftheModelManagement
ProtocolorProcessislocatedinSection1.8orinanattachedexhibit.Ifinanexhibit,identifytheexhibit.)
LocationofDetailed
Applicabilityto
Description
Project
(Section1.8beloworin
(Applicableor
anattachmenttothis
ModelManagementProtocols
NotApplicable) exhibitidentifiedbelow)
1.7.1 Modeloriginpoint,coordinatesystem,precision,
fileformatsandunits
1.7.2 Modelfilestoragelocation(s)
1.7.3 ProcessesfortransferringandaccessingModelfiles
1.7.4 NamingConventions
1.7.5 ProcessesforaggregatingModelfilesfromvarying
softwareplatforms
1.7.6 Modelaccessrights
1.7.7 Designcoordinationandclashdetection
procedures
1.7.8 Modelsecurityrequirements
E2032013Section4.8.2listsanumberofpotentialModelmanagementprotocolsandprocesses.Thetable
inG2022013Section1.7correspondstotheE2032013Section4.8.2listofpotentialModelmanagement
protocolsandprocesses.InpreparingtheModelingprotocols,theProjectParticipantsshouldutilizethis
tabletoidentifytheModelmanagementprotocolsandprocessesthatapplytotheProject.Further,asthe
Modelmanagementprotocolsandprocessesmaybeverydetailed,thetableallowstheProjectParticipants
toidentifywherethedetaileddescriptionofeachapplicableModelmanagementprotocol/processis
located.SuchadescriptioncaneitherbesetforthinSection1.8orinaseparatedocumentthatis
referencedinthethirdcolumnintheSection1.7table.Again,careshouldbetakentocoordinatethese
protocolswithestablishedstrategies,training,formats,etc.
45
G2022013Section1.8
1.8InsertadescriptionofeachModelManagementProtocolandProcessidentifiedinSection1.7,ifnot
furtherdescribedinanexhibitattachedtothisdocument:
TotheextenttheProjectParticipantsindicateinthetablethatthedetaileddescriptionofaModel
managementprotocolorprocessisprovidedinSection1.8,thissectionprovidesanopenfillpointforsuch
information.Ifanacceptabledescriptionalreadyexists,itcanbecopiedintoSection1.8orareferencecan
beprovidedtoanattacheddocumentinsertedinthetable.AsuseofG2022013increasesovertime,itis
anticipatedthatpreviouslydevelopeddescriptionsofprotocolsandprocesseswillbecomestandardizedfor
someProjectParticipantsandmuch,ifnotall,ofthistablecanbecoveredinareferenceddocument.
G2022013Section1.9
1.9TermsinthisdocumentshallhavethesamemeaningasthoseinAIADocumentE2032013.
Bythiscrossreference,theProjectParticipantsrecognizetheuseoftheterminologyfoundinE2032013,
includingsuchtermsasModel,ProjectParticipant,LevelofDevelopment,andAuthorizedUse.
TermswithspecializedmeaningsaregenerallydefinedandcapitalizedinAIAContractDocuments.
Article2LevelofDevelopment
G2022013Section2.1
2.1TheLevelofDevelopment(LOD)descriptions,includedinSection2.2throughSection2.6below,
identifythespecificminimumcontentrequirementsandassociatedAuthorizedUsesforeachModel
Elementatfiveprogressivelydetailedlevelsofcompleteness.ThePartiesshallutilizethefiveLOD
descriptionsincompletingtheModelElementTableatSection3.3.
TheLODframeworkutilizedinG2022013isdesignedtoaccomplishtwoobjectiveswithregardto
Modeling.TheLODframeworkallowstheProjectParticipantstoefficientlycommunicatetooneanother
theextenttowhichaModelElementhasbeendevelopedbyvirtueofthedefinedminimumModelcontent
requirementforeachLOD.ItalsoallowstheProjectParticipantstocommunicatetheextenttowhicha
ModelelementmaybeusedandreliedonbyvirtueoftheidentifiedAuthorizedUsesoftheModel.
Accordingly,theLODframeworksetsthefloorforModelcontentandtheceilingforModeluse.
Withregardtothefirstobjective,communicatingtheextentofdevelopment,itisimportanttorecognize
thedifferencebetweenthedetailofaModelElementandthedevelopmentofaModelElement.Ina
Model,itiseasytomisinterpretthemeaningofthelevelofdetailatwhichaModelElementisrepresented.
Toillustrate,considertraditionalhanddrawings.Handdrawingsrangefrompenstrokesonanapkinto
detaileddrawingswithdimensionscalledout.Thedetailedhanddrawingcarrieswithitthedesigners
significantthoughtandeffortinprovidingthatdetail.Therefore,itissafetoassumethatbecausethe
designertookthetimeandaffirmativesteptodrawanitemwithgreatprecisionandtoincludeextensive
additionaldetails(dimensioning,notes,etc.),thedesignerhasthoroughlyevaluatedandvettedthe
informationsuchthatitissufficientlydevelopedforitsintendedpurposes.
46
InaModel,however,itisinappropriatetoassumethatbecauseaModelElementisdepictedinextensive
detail,ithasbeensufficientlydevelopedforparticularuses.Thecommonuseoflibraryobjectsas
placeholdersinModelingservesasagoodexampleofwhythisisthecase.Adesignermaypullavery
detailedlightfixturefromanavailableobjectlibraryandplacethatobjectintheModel,butonlyasa
placeholder.Theobject,however,containsextensivedetail(i.e.,themanufacturername,modelnumber,
etc.)andispreciselylocateddespitethefactthatthedesignerhasnotfullyevaluatedanddecidedupon
thisinformation.Inotherwords,whilethelevelofdetailisextremelyhigh,thelevelofdevelopmentis
extremelylow.Therefore,unlikemoretraditionaldrawings,thevisuallevelofdetailisinsufficientto
accuratelycommunicateaModelElementslevelofdevelopmentasthedetailcanbemisleading.
TheProjectParticipantscanutilizetheLODframeworktoovercomethisissue.Asisdiscussedbelowinmore
detail,eachLODallowstheProjectParticipantstodescribethecontentrequirementsassociatedwiththe
LOD.Forexample,thestandardlanguageforLOD200indicatesthatthe[t]heModelElementisgraphically
representedwithintheModelasagenericsystem,object,orassemblywithapproximatequantities,size,
shape,location,andorientation.NongraphicinformationmayalsobeattachedtotheModelElement.
Therefore,evenifaModelElementisextremelydetailed,ifitisidentifiedtoonlybeatLOD200,itisclearthat
thedetailedinformationcontainedintheModelElementhasnotbeenfullydeveloped.Rather,thecontent
hasonlybeendevelopeduptothepointofbeingagenericsystem,object,orassembly.
ThesecondobjectivefortheLODframework,communicatingtheextentofuseandreliance,isintendedto
addressthefactthatthepossibleusesofaModel(andalltheinformationincludedintheModel)are
potentiallylimitless.Thishascausedsignificantconcerntodesignprofessionalsthattheirworkmaybeused
forunintendedpurposes.Thisconcernhasledtotheproliferationofonerousdisclaimersessentiallystating
that,whiletheModelisbeingshared,itcannotbeusedorreliedon.Toaddressthisissue,theLOD
frameworkallowstheProjectParticipantstoidentifyAuthorizedUsesfortheModelcontentateachLOD.
AnyProjectParticipantusingaModelElementcanlooktothedefinedAuthorizedUsesinG2022013to
knowtheextenttowhichitcanuseandrelyontheinformationintheModelElement.
ItshouldalsobenotedthatthereisnointendedcorrespondencebetweenanLODandtraditionaldesign
phases.Systemsprogressatdifferentratesthroughthedesignprocessforexample,designofthe
structuralsystemisusuallyaheadofthedesignofinteriorconstruction.AtSchematicDesign,themodel
willincludemanyelementsatLOD200,butwillalsoincludemanyatLOD100,aswellassomeat300,and
possiblyeven400.Similarly,thereisnosuchthingasanLODmodel.Modelswillinvariablycontain
elementsatvariousLODs.
InArticle2,theProjectParticipantsdefinetheactualLevelsofDevelopmentthatwillbeusedonthe
Project.EachofthefivestandardLevelsofDevelopmentconsistoftwocomponents:
ModelElementContentRequirements.Thesesectionsprovideadescriptionoftheminimal
contentrequirements,intermsofrepresentationwithintheModel,neededtoqualifyasthe
LOD.ForanelementtoqualifyasagivenLOD,alltherequirementsforthatLODmustbemet.For
example,atLOD300,bothspecificassemblyandfinallocationmustbedetermined.
AuthorizedUses.ThesesectionsdescribetheextenttowhichreliancecanbeplacedonaModel
Element,forcertainidentifieduses.TheAuthorizedUsesincludedinthestandardtextofG2022013
47
aresuggestionsandbasedonsomeofthemorecommonModeluses.Documentusersshouldmodify
andrevisetheAuthorizedUsestofittheirparticularneeds.TheAuthorizedUsesshouldbe
coordinatedwiththelistofAnticipatedModelAuthorizedUsesprovidedinSection4.3ofE2032013.
Itisalsoimportanttounderstand,however,thattheLODframeworkandrelatedAuthorizedUses
specifiedinthesedocumentsaretiedtoProjectMilestones.Asomewhatcommonperceptioninthe
industryisthat,intheprocessofcreatingvariousModelElements,theyaretaggedwithanLOD.
WhilethismaybeausefulexerciseintheprocessofcreatingandrevisingModelElements,sucha
tagdoesnotautomaticallycarrywithittheAuthorizedUseslistedinthesedocuments.Thisis
becausetheLODframeworkinthesedocumentsdescribesModelElementscontentrequirements
andtherelatedAuthorizedUsesatdefinedpointsintimeonly.Thosedefinedpointsintimearethe
agreeduponProjectMilestonessetforthintheG2022013Section3.3ModelElementTable.
TheLODdefinitions,asdevelopedbytheAIAandincludedinArticle2,aregainingacceptanceasstandard
definitionsintheindustry.RecentlytheBIMForum2utilizedtheAIAsLODdefinitionsinitsLevelofDevelopment
(LOD)Specificationdocument.TheLODSpecificationutilizestheAIAsLODdefinitionsandgraphicallyillustrates
characteristicsofModelElementsofdifferentbuildingsystemsatdifferentLevelsofDevelopment.TheLOD
Specificationiscurrentlyindraftformandisavailabletodownload(bimforum.org/lod).3
G2022013Section2.2
2.2LOD100
2.2.1ModelElementContentRequirements.TheModelElementmaybegraphicallyrepresentedinthe
Modelwithasymbolorothergenericrepresentation,butdoesnotsatisfytherequirementsforLOD200.
InformationrelatedtotheModelElement(i.e.,costpersquarefoot,tonnageofHVAC,etc.)canbederived
fromotherModelElements.
AtLOD100,ModelElementsareintheformofnarratives,programinformation,etc.AnLOD100Model
Elementisnotgeometricallymodeled,butmaybeincludedinaModelasasymbolthatdoesnotrepresent
actualgeometry.ItisalsopossiblethattheModelElementisnotindividuallyrepresentedintheModelin
anygraphicalsense,butitsexistencecanbederivedfromotherModelElementsthataregraphically
representedintheModel.Forexample,theexistenceofamechanicalsystemcanbederivedfromthe
squarefootquantityassociatedwiththefloorslabthatisrepresentedintheModelatLOD200.
LOD100elementsareextremelyusefulearlyinthedesignprocess.Theyenablethedesignertoembeda
greatdealofintelligenceregardingsuchthingsasapproximatecostsandsystemcapacitiesinaModel
consistingofnothingmorethanfloors,andthentoquicklyderiveoverallcostsandcapacitiesastheModel
ischanged.SomeModelElementsmayremainatLOD100throughtotheendoftheProject.Seethe
discussionunderCostEstimatingbelow.
TheBIMForumisanorganizationformedtofacilitateandacceleratetheadoptionofbuildinginformationmodeling
inthedesignandconstructionindustry.Formoreinformation,visitbimforum.org.
3
TheAIAlicensedtheuseofitscopyrightedLODdefinitionstotheBIMForumtoadvanceacceptanceofa
standardizedsetofLODdefinitionsinthedesignandconstructionindustry.
48
ExamplesofLOD100ModelElements:
Structural.Aunitquantityofpoundsofsteelpersquarefootlinkedtofloororroofelements.
Architectural.ArchitecturalelementsatLOD100arenotgeometricallymodeled.Informationis
innarrativeform,includingsuchitemsasspaceusesandtheirareas,allowancesforcirculation
space,andtypesandqualitylevelsoffinish.Elementssuchaselevatorsandstairwaysmaybe
includedonlyinthenarrative,ormaybeplacedina3Dmodelasnongeometricsymbols.The
latterapproachprovidestheabilitytospecifycountsandapproximatelocationsofelements
withouthavingtomodelspecificgeometriesearlierthannecessary.
InteriorConstruction.Aunitcostpersquarefootoffloorarealinkedtofloorelements,stairways
indicatedbysymbols
HVAC.Aunitquantityoftonsofcoolingcapacitypersquarefootlinkedtofloorelements,
terminalunitsindicatedbysymbols.
Electrical.Aunitquantityofwattspersquarefootpowerconsumptionlinkedtofloorelements.
Conveyance.Acommonpracticeforestimatingelevatorsistoincludeacostforthemachineandacost
perstop.ThiscanbefacilitatedwithanLOD100symbolforthemachineandoneforanelevatorstopon
eachfloor.
2.2.2AuthorizedUses
2.2.2.1Analysis.TheModelElementmaybeanalyzedbasedonvolume,areaandorientationby
applicationofgeneralizedperformancecriteriaassignedtootherModelElements.
2.2.2.2CostEstimating.TheModelElementmaybeusedtodevelopacostestimatebasedoncurrent
area,volumeorsimilarconceptualestimatingtechniques(e.g.,squarefeetoffloorarea,condominiumunit,
hospitalbed,etc.).
2.2.2.3Schedule.TheModelElementmaybeusedforProjectphasinganddeterminationofoverall
Projectduration.
2.2.2.4OtherAuthorizedUses.AdditionalAuthorizedUsesoftheModelElementdevelopedtoLOD100,
ifany,areasfollows:
Analysis.LOD100ModelElementscanonlybeanalyzedataveryconceptuallevel,andonlythrough
referencetoModelElementsathigherLevelsofDevelopment.Forexample,iftheHVACsystemisstillat
LOD100,spacevolumesmightbedeterminedfromotherModelElementsmodeledatahigherLODin
ordertohelpdeterminetheventilationairvolumerequirements.
CostEstimating.LOD100canbeextremelyusefulforthispurpose.TherearemanyModelElementsthat
neverneedtobemodeledin3D,butforwhichenoughinformationispresentintheModeltosupport
accuratecostestimating.Paint,forexample,isalmostnevergraphicallyrepresentedintheModel,but
informationaboutitcanbelinkedtoorderivedfromwallModelElements,allowingaccuratequantitiesto
bedetermined.TheModelElementtableinArticle3canshowthattheseModelElementswillremainat
LOD100throughtheentiredesignprocess.Thisisinvaluableinmanagingeveryonesexpectationsasto
whatwillandwillnotbegraphicallymodeled.IfCostEstimatingisanAuthorizedUse,theestimating
methodsusedwillbeconceptual(i.e.,costperfloorsquarefoot,perhotelkey,perhospitalbed,etc.)
becauseofthenatureoftheModelElementcontentatLOD100.
49
Schedule.LOD100ModelElementscanbecoupledwithmeasurementsandcountsofModelElementsat
higherLevelsofDevelopmenttogeneratehighlevelphasingschedulesandoverallProjectduration.With
respecttoModelElementsatLOD100,however,giventheconceptualnatureoftheinformation,theycan
onlybescheduledingeneralorconceptualterms.
OtherAuthorizedUses.LOD100,likeallthesubsequentLODdefinitions,includesafillpointtoallowfor
theadditionofotherAuthorizedUsesanticipatedbytheProjectParticipants.
G2022013Section2.3
2.3LOD200
2.3.1ModelElementContentRequirements.TheModelElementisgraphicallyrepresentedwithinthe
Modelasagenericsystem,object,orassemblywithapproximatequantities,size,shape,location,and
orientation.NongraphicinformationmayalsobeattachedtotheModelElement.
Ingeneral,LOD200elementsaregenericplaceholders.Thisisthelowestlevelatwhichageometric
representationofaModelElementwillappear.Bycontrast,inLOD100,aModelElementmaybe
graphicallyrepresentedbyasymbol,butitwilllackanygeometry.ForanLOD200ModelElement,thesize,
shape,location,orientation,andanydataassociatedwiththeModelElementareapproximate.LOD200
elementsareusefulbothearlyinthedesignprocesswhenspecificshavenotyetbeendetermined(the
designationofLOD200tellsdownstreamusersthattheelementmaychange)andinfinalModelswhen
selectionofcertainitems,suchaslightingfixtures,islefttoothersorismetbyarangeofchoices.
Inadditiontothegeometricrepresentation,theLOD200ModelElementmayalsoincludenongraphic
information.ThemostcommontypeofnongraphicinformationattachedtoModelElementsiscost
information.Thereareseveralwaysofattachingthisdata.Manyauthoringtoolsincludefieldsforsuch
informationwithintheobjectsthemselves,andtherearealsoseveraltoolsthatallowobjectstobelinked
tolineitemsinaseparatedatabase.Otherexamplesofnongraphicinformationthatmaybeincludedinan
LOD200ModelElementarethermalcharacteristicsofenvelopecomponents,weightofanobject,
manufacturer/modeldata,andhyperlinkstooperationandmaintenancemanuals.
Examples:
Structural.Thestructuralgridandapproximatestructuraldepths(perhapsbasedonrulesofthumb)
areshown.ThisisaprimeexampleofthenecessityofcoordinatingcarefullywiththeG2022013
Section3.3ModelElementtable.Structuralelementsareusuallyselectedfromalibraryofobjects.
Forexample,AW14X34,selectedbecauseitisclosetowhatislikelytobeneededandplaced
approximately,looksexactlylikeaW14X34thathasbeenfullyengineeredandplacedinitsfinal
location.ThedesignationofLOD200tellseveryonethat,despiteitslevelofdetail,theModel
Elementisstillgenericandshouldonlybereliedonassuch.
Architectural:
Wallsandroofs:modeledas3Dobjects,butthickness,composition,andlocationarenot
finalized.
Windowpenetrations:modeled,butdimensionsandlocationsarenotfinalized.
HVAC.ThepurposeofHVACModelElementsatLOD200isprimarilytoverifyearlyinthedesign
processthatspacessuchasaboveceilingplenums,shafts,andmechanicalroomsarelargeenough.
50
Equipmentandductworkaremodeledwithasmuchaccuracyasisreasonablypossibleinorderto
reservespace,butwiththecaveatthatsizeandlocationmaychangeasthedesignprogresses.Often
onlylargeitemsorthoseincongestedspacesaremodeledatLOD200smalleritemsmaybe
deferreduntiltheycanbemodeledathigherLevelsofDevelopment.
Electrical.Lightingfixturescanbemodeledasgeneric3Dobjectstobegindeterminationoflayoutand
identificationofcoordinationissues.Switchgearandmajorpanelscanalsobemodeledasgeneric3D
objectstoaidinsizingandlayoutofequipmentroomsandidentificationofaccessrequirements.
2.3.2AuthorizedUses
2.3.2.1Analysis.TheModelElementmaybeanalyzedforperformanceofselectedsystemsbyapplication
ofgeneralizedperformancecriteriaassignedtotherepresentativeModelElements.
2.3.2.2CostEstimating.TheModelElementmaybeusedtodevelopcostestimatesbasedonthe
approximatedataprovidedandquantitativeestimatingtechniques(e.g.,volumeandquantityofelements
ortypeofsystemselected).
2.3.2.3Schedule.TheModelElementmaybeusedtoshowordered,timescaledappearanceofmajorelements
andsystems.
2.3.2.4Coordination.TheModelElementmaybeusedforgeneralcoordinationwithotherModel
Elementsintermsofitssize,locationandclearancetootherModelElements.
ifany,areasfollows:
Analysis.AnyanalysisbasedonLOD200elementswillnecessarilybeveryapproximate.ModelElementsat
thisLODareusefulforcomparisonofoptions,suchasrelativeeffectsofbuildingorientationonHVACload.
CostEstimating.WherecostsofLOD100elementsarebasedonmeasurementofotherModelElements,at
LOD200theModelElementbeingestimatedcanbemeasuredorcounteddirectly.Forexample,atLOD
100thecostofinteriorwallsisbasedonfloorarea,whereasatLOD200theactualquantitiesofwallscan
bemeasured.BecausetheModelElementsareapproximateinsizeandgenericincomposition,cost
estimatesbasedonLOD200shouldbestatedasarangeratherthanasspecificnumbers.
Schedule.SchedulingisaidedatLOD200byestablishingquantitiesanddurationsforinstallationaswellas
leadtimesforequipment.
Coordination.Becausefinalsizeandshape,aswellasdetailssuchasaccessrequirementsandanchorage
arenotyetknown,coordinationismostlylimitedtoreservationofspaceandperhapsapproximaterouting
ofmajorelements.
G2022013Section2.4
2.4LOD300
Modelasaspecificsystem,object,orassemblyintermsofquantity,size,shape,location,andorientation.
NongraphicinformationmayalsobeattachedtotheModelElement.
51
LOD300ModelElementsarespecificassemblies,suchasspecificwalltypes,engineeredstructural
members,systemcomponents,etc.ThedesignoftheModelElementisdevelopedintermsofcomposition,
size,shape,locationandorientation.Constructabilityandcoordinationofotherbuildingcomponentsmay
requirechangetosomeModelElementsaftertheyaredesignatedLOD300,butsuchchangesshouldbe
minimizedasmuchaspossible.Otherinformationsuchascost,thermalcharacteristics,specifications,
warranty,andoperationandmaintenanceinstructionmaybeattachedtotheelement.
Examples:
Structural.Columns,beams,andjoistsarerepresentedattheiractualengineeredsizes,shapes,and
locations.Flanges,basesandjoistwebscanberelieduponforspatialcoordinationwithotherelements
suchaspipingandductwork,butLOD300doesnotusuallyincludeconnectiondetailssuchasgusset
plates,whichcanimpactcoordination.Ifthereiscongestionnearaconnection,thatconnectionshould
betakentoahigherLODinordertoassurecoordination.Smallerdetailssuchasbolts,stiffenersand
bracingwillnotbemodeledatthislevel.Datasuchassteeltonnageandconcretevolumecanbe
derivedaccurately.
Architectural.Wallsandroofsarerepresentedattheiractualthickness.Thecomponentlayers(GWB,
studs,etc.)maynotberepresented,butinthatcasetheymustbeincludedinthenongraphical
informationattachedtotheModelElement.Ifthatisthecase,thenongraphicalinformationrelating
tocomponentlayersshouldbelistedaspartoftheModelinG2022013Section1.2.
HVAC.Ductworkisrepresentedattheactualengineeredsizeandlocation,includingspacefor
insulationandlocationofaccessoriessuchasturningvanes,dampersandaccesshatches.Assembly
andinstallationdetailssuchasflangesandhangersmaynotbeshown.DatasuchasCFMandweight
maybeincludedintheattachednongraphicaldata.
Electrical.Equipment,switchgearandpanelsarerepresentedattheiractualsizesandlocations,and
requiredaccessspaceandclearancesareshown.Fixturesanddevicesareaccuratelylocatedattheir
actualconfiguration.
OneofthechallengesthattheindustryfacesasModelingbecomesincreasinglyprevalentisthe
differentiationoftheLevelofDevelopmentofaModelElementfromthebroaderrangeofinformationthat
maybecontainedintheModelpertainingtothatModelElement.AModelthatisdevelopedsufficientlyto
derivetraditionalconstructiondocumentswillappropriatelyincludeModelElementswithLevelsof
Developmentrangingfrom100to300.LevelofDevelopmentdefines,mostimportantly,themaximum
reliancethatadesignatedusermayplaceuponagivenModelElement.WhencompletingtheModelElement
tableinG2022013Section3.3,ProjectParticipantsshouldconsiderfirstwhatrelianceisnecessarytomeet
theProjectsneedsandthenderivetheLevelofDevelopmentnecessarytoachievethatoutcome.
Withthatinmind,considerthattheelectronicdatasetthatcomprisesaModelwillincludeagreatdeal
morethanthegraphicalinformationthatisthethreedimensionalrepresentationoftheProject.(Thedata,
includingnongeographicinformation,thatcomprisesaModelisestablishedinG2022013Section1.2)For
example,doorhardwareismostlikelytoberepresentedintheModelwithmetadataembeddedasa
characteristicofthegraphicallyrepresenteddoor.AtabularorscheduledModelElementwilldisplaythe
informationwithaveryhighdegreeofspecificityandreliance.ModelElementswiththischaracteristic
shouldusetheNotescolumnofthetabletoidentifythehighlevelofreliancefromnongraphicalcontent.
52
AnotherimportantissueisthecontentofthetwodimensionalrepresentationsoftheContractDocuments.
TwodimensionalviewsoftheModel,whichformanyProjectswillcontinuetoformthebasisofthe
constructioncontract,includeannotations,lineworkandotherdatathatdonotfitcomfortablywithinLOD
definitions.Forexample,acurtainwallwindowsilldetailmightincludedimensionaldetailandanchorage
characteristicstypicalofanLOD400foraModelElementthatisotherwiserepresentedintheModelat
LOD200or300.Generallyspeaking,thepresenceofthedetaildoesnotcausethecurtainwallsystemtobe
definedintheModelElementtableasLOD400,norrequirethatotherModelElementsofthecurtainwall
bemodeledtoLOD400.TheModelElement,inthiscasethecurtainwall,shouldbemodeledtotheLevel
ofDevelopmentnecessarytoachievethereliancethattheProjectParticipantsagreeisnecessary.The
detailisprovidedtocommunicatetheintentofthedesigninaspecificlocationorwaythatsupplements
themoregeneralLevelofDevelopment.
ItmustbekeptinmindthatdesignationofaModelElementasLOD300isastatementthatitisreliablefor
theLOD300AuthorizedUses.TheseusesaresubstantiallymoredetailedthanthoseatLOD200,so,ifall
thecontentrequirementsinthedefinitionarenotyetmet,thedesignationmustbeleftat200.
2.4.2AuthorizedUses
2.4.2.1Analysis.TheModelElementmaybeanalyzedforperformanceofselectedsystemsbyapplication
ofspecificperformancecriteriaassignedtotherepresentativeModelElement.
2.4.2.2CostEstimating.TheModelElementmaybeusedtodevelopcostestimatessuitablefor
procurementbasedonthespecificdataprovided.
2.4.2.3Schedule.TheModelElementmaybeusedtoshowordered,timescaledappearanceofdetailed
elementsandsystems.
2.4.2.4Coordination.TheModelElementmaybeusedforspecificcoordinationwithotherModelElements
intermsofitssize,locationandclearancetootherModelElementsincludinggeneraloperationissues.
ifany,areasfollows:
Analysis.TheaccuracyofanLOD300ModelElementissufficienttoperformdetailedanalysessuchas
HVACloaddeterminationandstructuralsimulation.Theseprocesses,though,arecarriedoutthrough
specializedsoftware,andmayrequireadditionalnongraphicaldata.Manyanalysisprogramsdonot
supporttheimportofModels,inwhichcase,theModelElementwillhavetoberemodeledinthespecific
programsformat.
CostEstimating.LOD300ModelElementscanbemeasuredandcountedaccurately,andspecificunit
pricescanbeapplied,givinganaccuratecostforthelineitemsrepresentedbytheelement.
Schedule.TheModelElementcontainssufficientinformationtodevelopthetasksneededtoconstructit
andtheirdurations.
Coordination.Coordinationofmostmajorbuildingsystemscanbeperformedthroughclashdetection
cycles.Theremaybeinstancessuchashighlycongestedareasorbulkystructuralconnections,however,
whereahigherLODisneededinordertoassureclearances.
53
G2022013Section2.5
2.5LOD400
Modelasaspecificsystem,objectorassemblyintermsofsize,shape,location,quantity,andorientation
withdetailing,fabrication,assembly,andinstallationinformation.Nongraphicinformationmayalsobe
attachedtotheModelElement.
AdesignationofLOD400indicatesthatdetailbeyondthatincludedinLOD300istobeprovided,similarto
thekindofdetailthatistraditionallysuppliedinshopdrawings.Structuralconnections,slabedgeembeds,
curtainwalldetails,andotheritemsrequiringspecialfabricationfallintothiscategory.AModelElement
qualifiesasLOD400onceallinformationnecessaryforfabricationandinstallationhasbeenresolved.
Notethatfabrication,asthetermisusedhere,referstoprojectspecificfabricationratherthan
manufactureofstandardcomponents.So,anLOD400storefrontModelElementwouldincludethedetail
necessarytoinstallit,butnottomanufactureit.AnLOD400custommetalrailingModelElementwould
includedetailnecessaryformanufacture.
Examples:
Structural:
Steel:ModelElementincludessuchdetailsasbracing,stiffeners,masonrysupports,lintels,etc.
Elevatedconcreteslabs:ModelElementincludesrebar,accuratedecking,etc.
Slabongrade:includesgravelbaseandvaporbarrier.
Concreteblock:showsifcellsaregroutedandanyreinforcingwithin.
Architectural:
Walls:metalandwoodstudsandblockingareshown
Glassandglazing:thicknessandairspace,ifappropriate,areshown.
WindowandDoorprofilesaremanufacturerspecificandindicateconnections,flashingsand
accessories.
HVAC:ModelElementsincludeductandpipeflanges,hangers,seismicbracing,etc.Requiredaccess
clearancesaremodeled.
2.5.2AuthorizedUses
2.5.2.1Analysis.TheModelElementmaybeanalyzedforperformanceofsystemsbyapplicationofactual
performancecriteriaassignedtotheModelElement.
2.5.2.2CostEstimating.CostsarebasedontheactualcostoftheModelElementatbuyout.
2.5.2.3Schedule.TheModelmaybeusedtoshowordered,timescaledappearanceofdetailedspecific
elementsandsystemsincludingconstructionmeansandmethods.
2.5.2.4Coordination.TheModelElementmaybeusedforcoordinationwithotherModelElementsin
termsofitssize,locationandclearancetootherModelElements,includingfabrication,installationand
detailedoperationissues.
ifany,areasfollows:
54
OnlyselectedModelElementsrequiringsignificantdetailwillbetakentoLOD400.TheAuthorizedUsesare
similartothoseforLOD300,butmoreprecisionisprovided.
G2022013Section2.6
2.6LOD500
2.6.1ModelElementContentRequirements.TheModelElementisafieldverifiedrepresentationin
termsofsize,shape,location,quantity,andorientation.Nongraphicinformationmayalsobeattachedto
theModelElements.
TheLOD500filedverifiedrepresentationmaybeviewedasanasbuiltModel.WhenanasbuiltModelis
required,obviouslynoteveryaspectoftheProjectisfieldverified.LOD500providesforspecificindication
ofwhichelementswillbefieldverified.Thisallowstheownertobeclearonwhatisandisnotverified,and
allowswhoeverisresponsibleforproducingtheasbuiltModeltodetermineandpricetheeffortinvolved.
Forobviousreasons,anLOD500elementisthelaststageofrepresentationforthatModelElement.The
enduserwillbeabletorelyupontheModelElementsaccuracyforusebyotherownerinitiatedprograms
andsystemsthatcommunicatewiththeModelsoftware.ModeldatathatinanearlierLODindicated
optionalselectionsisreplacedbythefinalinstalledchoice.
ModelElementsdonotnecessarilyneedtobebroughtuptoLOD400beforegoingtoLOD500.Likewise,
notallModelElementswillbedevelopedtobeLOD500inordertobeappropriatefortheasbuiltModel.A
ModelElementrepresentingpaintmightneverbedevelopedbeyondLOD100,buttheownermaywant
thecolorfieldverifiedincertainareas.
ItisimportantnottoconfusethePhaseorProjectmilestonewiththeactoffieldverification.IftheProject
milestoneiscalled"RecordModel"thentheintersectionofModelElementscontainstheinformationfor
anLODandfortheModelElementAuthor.SomeModelElementsmightnotrequirefieldverification,and,
iftheydidnotchangeduringconstruction,thatwouldnotchange.ThoseModelElementswouldremainat
theLODtowhichtheywerepreviouslydevelopedfora"recordmodel"orasbuiltphase.IfaModel
Elementisrequiredtobefieldverified,thenthematrixwouldindicatethemasLOD500andtheModel
ElementAuthorwouldreviewtheProjectsiteagainsttheModelandfieldverifytheModelElement.There
mightalsobechangeordersorfieldchangesduringconstructionthatnecessitatechangestotheModel,in
whichtheModelElementswouldbeupdated,andrecordedasLOD500andthematrixupdatedtoshow
thatcondition.TheModelElementAuthorinbothcaseswouldlikelybethecontractororsubcontractoror
installerwhotherebytakesresponsibilityforthefieldverificationoftheModelElement.
Simplystated,aProjectmilestonecalled"recordmodel,"wouldconsistofamixtureofModelElementsat
LOD100,200,300and400thatarenotfieldverifiedandamixtureofLOD500ModelElementsthathave
beenfieldverified.TheProjectmilestoneofa"RecordModel"isanimperfectactivity,notunlikea"Record
Drawing,"asitrepresentsthelevelagreedtobytheOwner,ArchitectandContractorastotheappropriate
amountofeffortforrecordingandinvestigatingaModelthatisprudentfortheOwnersuseoftheModel
afterconstruction.
2.6.2AuthorizedUses
SpecificAuthorizedUsesoftheModelElementdevelopedtoLOD500,ifany,areasfollows:
55
TheAuthorizedUseofafinalasbuiltModelwillcarryonintothefuture.Potentialusesmightinclude:the
Projectrepositoryofexistingconditions,specificationsandapprovedproductdata;operationand
maintenanceofthebuildingeitherthroughownerdevelopedorthirdpartyoperatedfacilitymanagement
software;managementofscheduledandreactionarymaintenanceprogramsthatcanbecataloguedand
archivedthroughoutthelifeofthebuilding;andfuturerenovationsusingtheModelasabaselinefor
designingfuturemodifications,suchasinacommercialbuildingthatmayhaveaturnoveroftenants.
Article 3 Model Elements
3.1.RelianceonModelElements
3.1.1AtanyparticularProjectmilestone,aProjectParticipantmayrelyontheaccuracyandcompleteness
ofaModelElementonlytotheextentconsistentwiththeminimumdatarequiredfortheModelElements
LODforthatProjectmilestoneasidentifiedbelowintheModelElementTable,evenifthecontentofa
specificModelElementincludesdatathatexceedstheminimumdatarequiredfortheidentifiedLOD.
OneoftheprimaryobjectionstosharingModels(orevenCADdrawings)isthattheycanappeartobeata
higherLevelofDevelopmentthantheoriginatoroftheModelintends.SeethediscussionforG2022013
Section2.1above.
Section3.1.1putstheProjectParticipantsonnoticethat,regardlessofwhetheraModelElementlookslike
ithasbeendevelopedtoahigherLOD,usersoftheModelElementcanonlyrelyoninformationattheLOD
statedintheModelElementtable.Thus,iftheModelElementtablestatesthatthewallsareatLOD200,
eventhoughthedetailoftheModelElementexceedsthecontentrequirementforanLOD200,the
engineerknowsthattheymaychangeintypeandlocation,andcandeferfinaldesignoftheductworkin
tightspacesuntillater.
3.1.2CoordinationandModelRefinement
WhereconflictsarefoundintheModel,regardlessofthephaseoftheProjectorLOD,theProject
ParticipantthatidentifiestheconflictshallpromptlynotifytheModelElementAuthorsandtheProject
ParticipantidentifiedinAIADocumentE2032013Section4.8asbeingresponsibleforModelmanagement.
Uponsuchnotification,theModelElementAuthor(s)shallactpromptlytoevaluate,mitigateandresolve
theconflictinaccordancewiththeprocessesestablishedinSection1.7.7,ifapplicable.
Modelinghasinherentcoordinationbenefitsoverotherdesigntools.AsmoreProjectParticipantsmake
useofsharedModeldata,potentialconflictsarelikelytobediscoveredbysomeoneotherthantheperson
responsiblefortheModelElement.Section3.1.2addressestheprocesstobefollowedinsuchinstances.
First,anyProjectParticipantthatidentifiesaconflictmustpromptlynotifyboththeModelElementAuthor
andwhoeverisprovidingoverallModelmanagement.Aclassicexampleistheaboveceilingconflict.The
ModelElementAuthor(perhapstheHVACengineer)mayseektochangetheceilingheightwhenthereare
otherProjectconsequencestoconsider.BoththeentitymanagingtheModelandtheModelElement
56
Authorneedtobepartoftheinitialnotification.TheModelElementAuthorforotheraffectedModel
Elementsmayalsoneedtobebroughtintotheconversation.
Second,uponnotificationtheModelElementAuthor(withassistance,oratleastconcurrencefromthe
entitymanagingtheModel)hasaresponsibilitytopromptlyresolvetheconflictconsistentwiththe
protocolsestablishedinG2022013Section1.7.7fordesigncoordinationandclashdetectionprocedures.
G2022013Section3.2
3.2TableInstructions
3.2.1TheModelElementtableinSection3.3indicatestheLODtowhicheachModelElementshallbe
developedtoateachidentifiedProjectmilestoneandtheModelElementAuthor.
3.2.2AbbreviationsforeachModelElementAuthortobeusedintheModelElementTableareasfollows:
(ProvideabbreviationssuchasAArchitect,orCContractor.)
TheModelElementTableisintendedtobeflexibleandeachProjectwillhaveitsownuniquerequirements
toidentifytheModelElementAuthor.Ifthetableisusedwithinasmallfirm,employeeinitialsorindication
oftheconsultingfirmmaybeallthatisneeded.Withgreatercomplexity,otherindicationscanbeused.
G2022013Section3.3
3.3ModelElementTable
TheModelElementTableistheheartofG2022013andwillbeofgreatestvalueifitaccuratelyreflectsthe
inputandexpectationsoftheProjectParticipants.Sufficienttimeandeffortshouldbeallocatedtothe
processofcompletingtheModelElementTablebecausetheinterrelatedactivitiesandrelianceare
importanttothesuccessoftheProjectandtheProjectParticipants.
EachhorizontalrowinthetablecorrespondstoaModelElementabuildingsystem,assembly,or
componenti.e.,physicalobjectsinthebuilding.EachmajorverticalcolumncorrespondstoaProject
milestone.AttheintersectionofeachModelElementlineandProjectmilestonecolumnarethreecellsof
data.Theseare,inorder,theLevelofDevelopment(LOD),ModelElementAuthor(MEA),andNotes.Thus
foreachModelElementattheconclusionofagivenProjectmilestone,theProjectParticipantswillknow
whoisdoingwhat,when,andwithanyadditionalinformationincludedinthenotes.
Thetablehastwoprimarypurposes:
a)
Todefinereliance:toassurethatusersofModelsdonotinfermoreprecisionorinformationthan
thedesignerofthesystemorcomponentintendsatagivenpointinthedesignprocess,and
b) Tocoordinatebetweendisciplines:togivetheProjectteamanoverviewofwhoneedsto
providewhatinformationatwhattimeinordertomeetmilestones.
Thereareseveralapproachestothetaskoffillingoutthetable.OnethatworkswellistofillouttheLOD
andMEAcellswiththeArchitectsinhousestandardsforphasecompletion,andthenadjustasnecessary
fortherequirementsofotherdisciplines.BeginningwiththeArchitectsstandardhastheadvantageof
minimizingchangestotheusualworkflow.
TheidentificationoftheMEAforeachModelElementforeachProjectmilestoneisinmanywaysa
communicationtool.ForconflictsitprovidesamapbywhichsubsequentMEAsandtheentityresponsiblefor
57
managingtheModelcannavigatebackthroughModeldevelopmenttoidentifytherelevantMEA(s)toobtain
thebestresolutiontotheconflict.TheMEA(s)maynotbetheultimatedecisionmakersontheresolutionor
theentitiesthatactuallychangethemodel.Thatwillbedonebytheindividualorentityresponsibleforthe
change.Intheexampleofanaboveceilingconflict,theMEAfortheductwork(HVACengineer)may
participateintheresolutionthatisultimatelydecidedbytheresponsibledesignentity(thearchitect).
DeterminingtheProjectMilestones.ThefirststepincompletingtheModelElementTableistodetermine
thepointsintheProjectsdevelopmentatwhichtheModelshouldreachameasurablecondition.
Traditionally,inarchitecturalpractice,thesemilestonescorrespondwiththeconclusionofthephasesof
theservicesSchematicDesign,DesignDevelopment,ConstructionDocuments,etc.andreflectthe
creationofdeliverablesandothermaterialsthatdefinetheProject.
TheModelElementTableallowstheinsertionofProjectmilestonesthatbestfittheProjectParticipants
needs.Forexample,theremightbeaninterimsubmittalduringaphaseoftheworkwheretheModel
wouldbeusedtodevelopaGuaranteedMaximumPricecostestimate.ItwillbeimportantfortheProject
ParticipantstounderstandtheLevelofDevelopmentandreliancecharacteristicsoftheModelatthis
ProjectMilestone.Inthiscasethecolumnheadingsmightlooklikethis:
CarefullyconsidereachProjectmilestone.TheModelconstantlyevolvesthroughthelifeoftheProjectand
eachuniquemilestoneinvolveseffortsthatmayormaynotbeadequatelyrepresentedinthe
compensationstructure.
ConstructionClassificationSystem.Oncethemilestoneshavebeenestablished,thenextstepistoidentify
theModelElementsthatwillberepresentedbytheModel.TheTableinSection3.3canbecreatedinthree
differentformats.ThefirstformatutilizestheCSIUniFormatclassificationsystemasthedefaultsystemto
identifyModelElements.4
UniFormatisusefulbecauseitisbasedonlocations,systems,andassemblieswithinabuilding.AModel
ElementcanalwaysbeassignedauniqueUniFormatcode,whileitmaycomprisemultipleCSI
MasterFormatcodes(whichrelatetothetradesneededtoproducethesystemorassembly).The
breakdownforthelineitems,however,canbepartofonanysystembasedscheme.
UniFormatisproducedjointlybyTheConstructionSpecificationsInstitute(CSI)andConstruction
SpecificationsCanada(CSC).U.S.copyrightisheldbyCSIandCanadiancopyrightbyCSC.AllRightsReserved.Formore
information,visitcsinet.org/uniformat.
58
ThesecondformatutilizesOmniClassTable21.5Table21isanothersystembasedschemeconsistingofa
numberofdifferentelements.AccordingtotheOmniClassWebsite,theOmniClasselementsrepresenta
majorcomponent,assembly,orconstructionentitypartwhich,initselforincombinationwithotherparts,
fulfillsapredominatingfunctionoftheconstructionentity(ISO120062).Predominatingfunctionsinclude,
butarenotlimitedto,supporting,enclosing,servicing,andequippingafacility.Functionaldescriptionscan
alsoincludeaprocessoranactivity.
ThefinalformatavailableallowstheusertocreatetheModelElementTablewithoutanyprefilledsystem
foridentifyingtheModelElements.ThisallowstheuserstocustomizethelistofModelElementstofittheir
specificneedsandutilizetheirownsystemofidentifyingModelElements.
Theselectionoftheclassificationschemetobeusedisanimportantonethatshouldconsiderthevariables
oftheProject,suchasthecomplexityoftheclassificationsystem,thenumberofdifferingusers,andtheir
familiaritywiththeclassificationsystem.IfmuchoftheModelcontentwillbeevaluatedbyanotheruse,
suchasacostestimatingprogramorenergymodelprogram,therightclassificationmaybetheonethat
translateswelltootherprograms.Inotherwords,thereisnosinglebestsystemforclassificationofthe
Modelcontent.ProjectParticipantsshouldseekthebestfitfortheProjectcircumstances.Itshouldalsobe
notedthatregardlessoftheclassificationsystemused,G2022013allowsuserstotailortheModel
ElementsintheModelElementTabletofittheirspecificneeds.
ThefollowingisanexampleofatablethathasbeeneditedtoaddadditionalModelElementstothe
preexistingUniFormatelements.
AnotheruseoftheModelElementTableistodefinewhatwillnotbeincludedintheModeltomakeclear
toallProjectParticipantswhattheycanexpecttofindintheModel,andwhattheywillhavetolookforin
othersourcesofinformation.TheexamplebelowshowstheinitialismNMusedtoindicateModel
Elementsthatarenotintendedtobemodeled.Carefullyconsiderthedifferencebetweenconstruction
elementsthataretobeincludedintheProject,butnotmodeled,versuselementsthatarenotinthe
Project.Projectelementsmaybeadequatelydesignedorspecifiedindatasuchasspecificationsornon
modeldrawings,schedulesorotherdata.TheModelElementtableisprimarilyintendedtodefineand
coordinatetheprogressivedevelopmentofModeldataovertheProjectMilestones.Assuch,itisa
OmniClassisproducedbyCSI(hereinafterTheOmniClassSecretariat)initsroleasSecretariatfortheOmniClass
DevelopmentCommittee.U.S.copyrightisheldbyTheOmniClassSecretariat.AllRightsReserved.Formore
informationonOmniClass,visitomniclass.org.OmniClassisintendedtobeanopenstandard;however,certain
limitationstoitsuseapply.Formoreinformation,visitomniclass.org/license.
59
somewhatlimitedsubsetofalltheProjectdataandthisshouldbediscussedwithalltheProject
Participants.ForexampleanestimatormayrelyontheLODoftheModelElementsbutmayalsohaveto
lookoutsidetheModeltocompletetheestimate.
AssigningtheLevelofDevelopment.Withthemilestonesandconstructionclassificationsystemsetinthe
Table,theModelElementAuthorandLODcannowbeassigned.
SomeModelElementsmaynotbedevelopedbeyondalowerLODsimplybecauseitisnotusefultothe
Project.DoorHardwaremaynotbemodeled,fireextinguishercabinetsmayneverbemodeledhigherthan
LOD200,andtypicallightfixturesmayremainmodeledasgraphicsymbolsonly.Carefulcoordinationofthe
neededLODinconsiderationoftherelianceandAuthorizedUsesofalltheProjectParticipantsisthemost
importantsingletaskofcompletingtheG2022013.
Atitscore,theModelElementTableisintendedasacommunicationtooltoaidintheefficient
developmentoftheModelacrossdisciplinesandtofacilitateModelsharingamongsttheProject
Participants.Itshouldbenotedthat,fordesignprofessionals,theLODdesignationsintheModelElement
Tablearenotintendedtodefine,replace,oraltertheapplicablestandardofcare.
Further,usersshouldunderstandthattheAIAsLODdefinitionsareintendedtoreflectthegenerally
acceptedandcurrentstandardsintheindustry.ItmaybenecessarytomodifytheAIALODdefinitions
and/ortosupplementtheminordertofittheparticularneedsoftheProject.Forexample,theBIMForums
LevelofDevelopment(LOD)SpecificationreferencedaboveadoptstheAIAsstandardLODdefinitionsand
suggestsanadditionalLOD350.AccordingtoBIMForum,LOD350canbeusedtodefinemodelelements
sufficientlydevelopedtofacilitatecoordinationbetweendisciplinese.g.,clashdetection/avoidance,
layout,etc.Therequirementsforthislevelarehigherthanthosefor300,butnotashighasthosefor400.
ThusitwasdesignatedLOD350.6IfusersfeelthisinterimLOD,oranyotherLODdefinition,isappropriate
foruseontheirProject,itcanbeeasilyinsertedintoG2022013.
AddingClarifyingNotestotheTable.Inmanyinstancesadditionalinformationwouldbeusefulregarding
someoftheModelElements.TheModelElementtableprovidesspacetorelatelongernotestoanumerical
orotherkeyplacedinthenotescells.
Therearetwolevelsofnotescontainedwithinthetable.Onthefarright,thenotescolumnprovidesinformation
fortheModelElement,regardlessoftheProjectphaseormilestonepoint.Forexample,apreselectedelevator
manufacturercanbeidentifiedorasustainableobjectivefordaylightingcanbenotedinthewindowslineitem.
TheLODSpecificationiscurrentlyindraftformandisavailabletodownload(bimforum.org/lod).
60
Thenotescolumnsforeachindividualmilestoneallowformodificationofthespecificationforeach
ModelElementforthatmilestoneonly.Forexample,aModelElementmighthaveanLODof200,with
anotethatindicatesthatitmaybeusedforLOD300costestimatingpurposes.Thisisalsoagood
placetoidentifythegranularityatwhichtheModelElementisrepresented.Forexample,atanearly
milestone,electricalconduitmightberepresentedonlywhereitis2orlarger,whereasatalater
milestoneconduit1andlargermightberepresented.
G2022013Section3.4
3.4ModelElementTableNotes
Notes:(Listbynumbershownontable.)
TotheextenttheProjectParticipantsutilizethenotescolumnsintheModelElementtable,Section3.4
providesaspacetolistthenotesandtheirmeaning.
61
RESOURCES
ThelistandlinksbelowprovideresourcesrelevanttoBuildingInformationModelingandDigitalPractice.
SuggestionsforresourcesarewelcomeforsubsequenteditionsofthisGuide.
buildingSMARTalliance.ThebuildingSMARTallianceisacounciloftheNationalInstituteof
BuildingSciencesdevotedtohelpingtomaketheNorthAmericanrealpropertyindustrymore
efficientbyleadingthecreationoftoolsandstandardsthatallowprojectstobebuiltelectronically
beforetheyarebuiltphysicallyusingBuildingInformationModeling.Aspartofitsefforts,the
buildingSMARTalliancehasdevelopedaNationalBuildingInformationModelingStandard,whichitis
currentlyrevising.Formoreinformation,visitbuildingSMARTalliance.org.
BIMForum.TheBIMForumisanorganizationformedtofacilitateandacceleratetheadoptionofbuilding
informationmodelinginthedesignandconstructionindustry.Formoreinformation,visitbimforum.org.
PennStateUniversitysComputerIntegratedConstruction(CIC)ResearchProgram.TheCIC
ResearchProgram'sgoalistodevelopanddisseminatestructuredproceduresfortheadoptionand
implementationofBIMonProjectsandinOrganizations.Infurtheranceofthiseffort,theCIC
ResearchProgramhaspublishedsignificantamountsofresearchrelatedtoModelingaswellasa
detailedBIMExecutionPlanandaplanningguideforownersinterestedinimplementingBIMon
projects.Formoreinformation,visitPennStatesBIMPlanningWebsite(bim.psu.edu).
GeneralServicesAdministrations3D4DBIMProgram.AccordingtoGSAsWebsitetheprimarygoal
oftheNational3D4DBIMProgramistopromotevalueaddeddigitalvisualization,simulationand
optimizationtechnologiestoincreasequalityandefficiencythroughoutGSAprojectlifecyclesandbeyond.
Thelongtermobjectiveistouseinnovative3D,4D,andBIMtechnologiestocomplement,leverage,and
improveexistingtechnologiestoachievemajorqualityandproductivityimprovements.Formore
information,visitGSAs3D4DBIMWebsite(gsa.gov/portal/category/21062).
AIAsTechnologyinArchitecturalPracticeKnowledgeCommunity(TAP).TAPservesasaresource
forAIAmembers,theprofession,andthepublicinthedeploymentofcomputertechnologyinthe
practiceofarchitecture.TechnologyinArchitecturalPracticemonitorsthedevelopmentofcomputer
technologyanditsimpactonarchitecturepracticeandtheentirebuildinglifecycle,includingdesign,
construction,facilitymanagement,andretirementorreuse.Formoreinformation,visittheAIAsTAP
Website(network.aia.org/TechnologyinArchitecturalPractice).
AIAsCenterforIntegratedPractice(CIP).CIPistheAIA'sonlineclearinghousethatcontainsuseful
reports,relevantindustryevents,contractualinformation,podcastsanddiscussionforumsnecessaryto
leadtheindustrytowardcollaborativedesignpractices.ThepurposeoftheCIPistohelpremove
barrierstocollaboration,serveasacollectorandconductorofprojectdeliveryoutcomesandresearch,
anddevelopresourcesandtoolsforAIAmembers,theprofession,andthepublic.Formore
information,visittheAIAsCIPWebsite(network.aia.org/CenterforIntegratedPractice).
Rev. 052213
62

AIA BIM and Digital Data - 2013

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

AIA BIM and Digital Data - 2013

Diunggah oleh

Hak Cipta:

Format Tersedia

Guide, Instructions and Commentary

to the 2013 AIA Digital Practice Documents

Responsible Individual or Entity

DigitalData Transmission Authorized

DigitalData Transmission Authorized

Anda mungkin juga menyukai