INSURANCENOTON "' F
A- 2022- 073WORKMAYNOTPROGEEU
General Terms and Conditions
ThisSoftwareasa ServiceSubscriptionAgreement (this "Agreement') ismadeandenteredintoasof the effective date set forth below ( the " Effective Date") between:
Effective Date of this Agreement: May 17, 2022
MERIDIAN: CLIENT:
MERIDIAN KNOWLEDGE SOLUTIONS, LLC, City of Santa Ana
a Virginia, limited liability company 20 Civic Center Plaza, M- 24 Santa Ana, CA 92701
Thesetermsand conditionsconstitutethe entirelegalagreementbetweenclientandMeridian KnowledgeSolutions, LLC ("Meridian") concerningthe accessto the proprietaryMeridianLMS softwareprogram, associateddocumentation ("Software") andtheservicesperformedbyMeridianin supportthereof. MERIDIANandCLIENTarealsoreferredto as "Party" or "Parties." A. MERIDIANhasdevelopedcertainsoftwareprogramsandassociateddocumentationwhich MERIDIANmakesavailableto itsCLIENT's ("Subscribers) ona Subscription ("Subscription") basis.
B. CLIENTwishestouseMERIDIAN'S ServicesandSoftwarein itsbusinessoperations.
C. MERIDIANhas agreedto provide, and the CLIENThas agreedto payfor and use MERIDIAN'S ServicesandSoftwaresubjecttothetermsandconditionsofthisAgreement.
D. Intheeventthereareconflictingtermsamongthevariousdocuments, theorderofprecedence is as follows: 1) ThisAgreement, includingSchedule(s); 2) ProjectDocuments; and 3) Exhibit( s).
1. Definitions
a. AuthorizedUser: Employees, agents, and independentcontractorsof the CLIENTwho are authorized to use the Software as described herein.
b. ConfidentialInformation: Informationthatis proprietaryor confidentialof MERIDIANasfurther defined throughout this Agreement.
c. CLIENTData: Datathat is inputby the CLIENTor AuthorizedUsersof the CLIENTintothe Softwarefor the purposeof utilizingthe Software.
d. Documentation: DocumentsmadeavailablebyMERIDIANto theCLIENTfromtimetotimewhich mayincludebutisnotlimitedtodocumentscontainingSoftwaredescriptions, usermanualsand other material related to the Software.
e. EffectiveDate: The day this Agreementtakeseffect.
I. Initial Subscription Term: The initial term of this Agreement. g. InternalBusinessOperations: Theinternalbusinessprocessesof anorganization. Business operationsincludethe day-to-day activitiesof the business. Suchoperationsfacilitatethe achievementof a business' primefunction.
h. StandardBusinessHours: MondaythroughFriday8:00am — 8:00pmEasternTime (ET), excludingMERIDIAN holidays. i. Services: Theaccessto the softwareservices (SoftwareServices, ImplementationServices, collectively, andanySupportprovidedforsuchServices) providedbyMERIDIANtoCLIENTunderthis Agreement. j. Software: Theapplicationprovidedasa partoftheServicesSubscription. k. SubscriptionFees: ThefeespayabletoMERIDIANbytheCLIENTfortheUserSubscriptions. I. Subscription Term: The tens of the Subscription. m. Support: Functional and technical support services as set forth herein. n. SupportPolicy: MERIDIAN'S policyforprovidingsupportinrelationtotheServicesasdescribedherein o. Service Levels: The Service Levelcommitmentsas setforth herein. p. UserSubscription: ThesubscriptionspurchasedtograntAuthorizedUsersaccesstotheServicesas described herein. q. ProductExtensions: AnymodificationtothebaseMeridianLMSapplicationthatisspecifictothe CLIENT's requirementsandscopeasdefinedintheStatementofWorkandanyassociated ChangeOrder. ProductExtensions (also knownas customizations) are prohibitedin thisagreement. r. SoftwareUpdates: MeridiangovemedenhancementsanddefectresolutionsfortheMeridianLMS softwareapplicationinbaseproductform. ThereleaseandapplicationofanySoftwareUpdateisat the sole discretion of Meridian.
2. Subscription
a. SubjecttotheCLIENTpurchasingtheUserSubscription, therestrictionssetforthinthisSection andothertermsandconditionsofthisAgreement, MERIDIANherebygrantstotheCLIENT, a non-exclusive, non -transferablerightto permittheAuthorizedUsersofthe CLIENTto (i) usesuch Services; and (ii) displaysuchServicessolelyforthepurposeofexercisingCLIENT'srightsand performingCLIENT's obligationshereunder. The foregoingsubscriptionis subjectto the restrictionsbelowandtheothertermsandconditionsofthisAgreement. Servicesshallbe used duringtheSubscriptionTermssolelyfor the CLIENT's InternalBusinessOperations. b. Inrelationto the AuthorizedUsers, the CLIENTagreesthat:
I. the maximumnumberof AuthorizedUsersthatit authorizesto accessandusetheServices shallnotexceedthenumberofUserSubscriptionsCLIENThaspurchased; it. CLIENTwillnotallowanyUserSubscriptiontobeusedbymorethanoneindividualAuthorized Userduringanannualsubscriptionterm. Alicensecanbereassignedinitsentiretyuponthe nextannualsubscriptiontermtoanotherindividualAuthorizedUser, inwhichcasetheprior AuthorizedUsershallbeflaggedinactiveandnolongerhaveanyrighttoaccessorusetheServices; iii. MERIDIANwillmonitortheactualnumberofAuthorizedUserstoensurecompliancewithItem 2)(a)(b) above during the annual subscriptionterm.
c. TheCLIENTwillnotintentionallyaccess, store, distributeortransmitanyviruses, Trojansorany andallmaliciouscode, oranymaterialduringthecourseofitsuseoftheServicesthatasoutlined below. Intheeventanyoftheidentifieditemsoccur, CLIENTwillremoveandpromptlynotify MERIDIANimmediatelyifthereispotentialharmtothesoftware.
I. is unlawful, harmful, threatening, defamatory, obscene, infringing, harassingor raciallyorethnically offensive; il. facilitates illegal activity;
iii. depicts sexually explicit images;
iv. promotes unlawful violence;
V.
isdiscriminatorybasedonrace, gender, color, religiousbelief, sexualorientation, disability, or any other illegal activity;
vi. causesdamageor injuryto anypersonor property; or
vli. infringesonthirdpartyintellectualproperty, copyrightor trademarkrights.
MERIDIANreservesthe right, withoutliabilityto theCLIENT, to disablethe CLIENT's accessto any material that breaches the provisions of this clause. d. ItistheCLIENTbestinteresttotestcontentinthestagingsitepriortoloadingitinproductionto ensurethe contentplaysas expectedand recordsany relevantdata. e, Software Support Troubleshootingof third -party or client -developedcontent, as it relates to successfully launching and tracking in the Software.
i. SoftwareSupportTroubleshootingof third -partyor client -developercontent, as it relatesto successfully launching and tracking in the Software.
ii. Meridian's responsibilitiesinclude: reviewingthecourseto determinewhatstatus/callsthe courseispassingtotheLMSandensuringthattheLMShasproperlytakenactiononthose status/calls. For example; the course is responsiblefor passinga completiontothe LMSafter a userhassuccessfullycompletedthecourse. Meridianwill reviewthecourseto determineif thecoursedidpassacompletionstatusandalsoconfirmifMeridianthenappropriatelymarkedthe user as Complete. iii. Customer's responsibilityinclude: providinga userimpactedbyanyreportedcourseware issuethat Meridiancan use to facilitatetesting, providingany answerkeys if the course/contentcontains a test/exam/etc., and providingthe coursewarefiles to facilitate Meridiantroubleshootingas well as providingthe nameof the tool usedto createthe content if applicable.
TheCLIENTshallnotexceptto theextentexpresslypermittedunderthisAgreement:
I. attempt to reproduce, copy, modify, duplicate, create derivativeworks from, frame, mirror, republish, download, display, transmit, or distribute, inwholeor in part, anyportionofthe Softwareand/orDocumentation (asapplicable) inanyformormediaorbyanymeans; ii. attempt to reverse compile, disassemble, reverse engineer or otherwise reduce to human - perceivable form all or any part of the Software;
iii. accessall or anypartof the ServicesandforDocumentationin orderto builda productor servicewhichcompeteswiththeServices, Softwareand/ortheDocumentationprovidedbythis Agreement; V. usethe Services, and/or Documentationtoprovideservicesto thirdparties; or V. subject to the Assignment Section, license, sublicense, sell, rent, lease, transfer, subcontract, assign, distribute, display, disclose, or otherwisecommerciallyexploit, or otherwisemakethe Services, and/or Documentationavailableto anythirdpartyexcepttheAuthorizedUsers, or vi, attempt to obtain, or assist third parties in obtaining, access to the Services, and/or Documentation, other than as provided under this clause. g. TheCLIENTshalluseallreasonableendeavorsto preventanyunauthorizedaccessto, or useof, theServices, and/or theDocumentationand, Intheeventofanysuchunauthorizedaccessor use, promptlynotifyMERIDIAN. TherightsprovidedunderthisSectionaregrantedtotheCLIENTonly and shall notbe consideredgrantedto anysubsidiaryor affiliateof the CLIENT. h. Additional User Subscriptions
1. The CLIENTmay, duringany SubscriptionTerm, purchaseadditionalUserSubscriptionsIn excessofthenumbersetoutinSchedule1andMERIDIANshallgrantaccesstotheServices to such additional Authorized Users in accordance with the provisionsof this Agreement. ii. If the CLIENTwishesto purchaseadditionalUserSubscriptions, theCLIENTshallnotify MERIDIAN in writing, MERIDIAN shall evaluate such request for additional User Subscriptions andrespondtothe CLIENTwithapprovalordisapprovalofthe requestandsuchapprovalnot to be unreasonably withheld.
iii. If MERIDIANapprovesthe CLIENT's requestto purchaseadditionalUserSubscriptions, the CLIENTshall, withinthirty (30) calendardaysof the dateof MERIDIAN'S invoice, pay MERIDIAN the relevant fees for such additional User Subscriptions as set out in Schedule 1 and, if suchadditionalUserSubscriptionsarepurchasedbytheCLIENTpartwaythroughthe InitialSubscriptionTermor anyRenewalPeriod (asapplicable), suchfeesshallnotbe pro- rated for the remainder of the Initial Subscription Term or then current Renewal Period (as applicable).
3. Fees; Payment Terms
a. Fees. In considerationof this Agreement, CLIENT will pay the Subscriptionfees set forth in Schedule2 (the "SubscriptionFees"). Inconsiderationofanyotherproductsprovidedorservices performed underthisAgreement, CLIENT will paythe fees andcharges describedin the applicable Schedule. OntheEffectiveDateofthisAgreement, theSubscriptionFeesshallbepayablewith respectto the InitialSubscriptionTermand at leastthirty (30) calendardayspriorto each anniversaryof theEffectiveDate, theSubscriptionFeesshallbepayablewithrespectto thenext Renewal Period. If, at any time while using the Services, the CLIENT exceeds the amount of storagespace specifiedin Schedule 2, MERIDIANshall chargethe CLIENT, and the CLIENT shall payMERIDIAN'Sthencurrentexcessdatastoragefees. MERIDIAN'Sexcessdatastoragefees are set out in Schedule2 and currentas of the EffectiveDate. MERIDIANshall be entitledto increasethe SubscriptionFees, withrespectof the additionalUserSubscriptionspurchased, and/ortheexcessstoragefeesatthestartofeachRenewalPerioduponthirty (30) calendardays' priornoticetotheCLIENTandSchedule2shallbedeemedtohavebeenamendedaccordingly.
Fees are non -cancellable and non-refundableexcept as otherwise stated herein. b. Payment. AllfeesandexpenseswillbedueandpayabletoMERIDIANwithinthirty (30) calendar daysafterthedateofinvoice. Allfeesandexpenseswillbepaidto MERIDIANinUnitedStates dollars, bywiretransferof fundsto an accountdesignatedby MERIDIANor by checksentto MERIDIANatAttention: AccountsReceivable, MeridianKnowledgeSolutions, LLC, SOIronPoint Circle, Suite100, Folsom, CA95630unlessotherwisespeckedbyMERIDIAN. Allpast -due paymentswill bear interestat the rate of one andone-half percent (1'/2%) per month or the maximumrate allowedby law, whicheveris less. MERIDIANshall have the rightto terminatethe Agreementfor default/causeiftheCLIENTdoesnotpayMERIDIAN'Sundisputedinvoiceswithin thetermscontainedherein. Alloutstandinginvoiceswillbedueandpayableimmediatelyupon suchtermination. IfCLIENTdoesnotpayMERIDIANforanyundisputedoutstandinginvoices, and MERIDIANincursanyadditionalcostsincluding, butnotlimitedtocourtcosts, attorney'sfeesand otherdamages, in the collectionof saidinvoices, MERIDIANshall havethe right to recoverthe additional costs from CLIENT.
c. PCICompliance. IntheeventCLIENTengagesin paymentcardtransactionsas partof the servicesprovidedbyMERIDIAN, CLIENTshallcomplywiththePaymentCardIndustryData SecurityStandard ("PCI-DSS") andanyamendmentsorrestatementsofthePCIDSSduringthe Termof thisagreement. CLIENTacceptsresponsibilityforthesecurityof customercreditcard datain itspossession, evenifallora portionoftheservicesbyMERIDIANaresubcontractedto third parties.
d. Taxes. CLIENTacknowledgesandagreesthatit isresponsibleforthepaymentofallapplicable taxesandduties, including, withoutlimitation, sales, use, excise, valueaddedandfranchisetaxes, associatedwiththisAgreement, the productsprovided, andthe servicesperformedunderthis Agreement, except for taxes based on MERIDIAN'S income. e. TheCLIENTshallon the EffectiveDateprovideto MERIDIANvalid, up-to-dateandcomplete approvedpurchaseorderinformationacceptabletoMERIDIANandanyotherrelevantinformation needed by MERIDIAN to invoice CLIENT.
IfMERIDIANhasnotreceivedpaymentwithinthirty (30) calendardaysaftertheduedateofany undisputedinvoice, andwithoutprejudiceto anyotherrightsand remediesof Meridian, MERIDIAN may, withoutfurtherliabilitytotheCLIENT, disabletheCLIENT's passwords, accountsandaccess toallorpartoftheServices. MERIDIANshallbeundernofurtherobligationtoprovideanyorall of theServiceswhilethe invoice(s) concernedremainunpaid; and MERIDIANshallhavethe right to terminatethe Agreementfor defaultif the CLIENTdoes not pay MERIDIAN'S undisputed invoiceswithinthetermscontainedherein. Alloutstandinginvoiceswill bedueandpayable immediatelyuponsuchtermination. If CLIENTdoesnotpayMERIDIANforanyundisputed outstandinginvoices, andMERIDIANincursanyadditionalcostsincluding, butnotlimitedtocourt costs, attorney'sfeesandotherdamages, inthecollectionof saidinvoices, MERIDIANshallhave the right to recover the additional costs from CLIENT.
4. Proprietary Rights
a. CLIENTacknowledgesand agreesthat the Softwareis protectedby U.S. and international copyright, patent, trademark, tradesecretandotherintellectualpropertyrightsandregistrations.
CLIENTacknowledgesthatall right, titleandinterestin andto the Softwareandall intellectual propertyrightstheretowill be ownedsolelyby MERIDIANandits licensors, asapplicable. CLIENT willnotremove, obliterate, obscureor alteranycopyrightor otherproprietaryrightsnoticethat appearson the Software. Exceptfor the limitedrights expresslygrantedto CLIENTunderthis Agreement, CLIENTis notgrantedanyotherrightsin or to theSoftware. All rightsin andto the SoftwarenotspecificallygrantedhereinarereservedtoMERIDIANanditslicensors, asapplicable.
5. Confidentiality Obligations
a. ConfidentialInformation. "ConfidentialInformation" meansanyand all informationthatis of a confidential, proprietaryortradesecretnaturethatisfurnishedordisclosedbyonePartytothe otherParty underthisAgreement. Withoutlimitingthegeneralityoftheforegoing, "Confidential Information" includestheSoftware (includingtheobjectcodeandsourcecodeformstherecf), the specific businessterms of this Agreementand any other informationthat is markedas Confidential," "Proprietary," 'TradeSecret" orin someothermannertoindicateitsconfidential, proprietaryor trade secretnature. "ConfidentialInformation" will notinclude: (i) informationthat is or becomespubliclyknownthroughno faultof the otherParty ; (ii) information received from a third partythat was disclosedwithoutbreachof any confidentialityobligation; (iii) information approvedfor releaseby writtenauthorizationof a Party ; (iv) informationdevelopedor created independentlyby one Partywithoutreferenceto, or use of, the otherParty's Confidential Information; or (v) informationthatmayberequiredbylaw, regulationoranorderofanycourt, agency or proceeding to be disclosed, provided that the Parry from whom the Confidential Informationis sought will providetheotherParty withwrittennoticeof anysuchrequired disclosureoncethe Partyhasknowledgeof it andwill helpthe otherPartyat theexpenseof the Partytotheextentreasonabletoobtainanappropriateprotectiveorder. b. Non -Disclosure. All ConfidentialInformationwill remainthe propertyof the Partyto whomit originallybelongedandneitherPartywillnotbedeemedbyvirtueofitsaccesstotheotherParty's Confidentialinformationto haveacquiredany rightor interestin or to anysuchConfidential Information, other than as specificallyset forth herein. The Parties agree: (i) to hold the ConfidentialInformationinstrictconfidence; (ii) exceptas expresslyauthorizedinthisAgreement, not to discloseany ConfidentialInformationto any third party otherthan employeesand independentcontractorsof the respectiveParty who have a need to knowthe Confidential InformationforthepurposesofthisAgreementandwhoaresubjecttoaconfidentialityagreement that affords at least as much protection to the Confidential Information as this Section 5; (iii) to use the ConfidentialInformationsolelyandexclusivelyinaccordancewiththetermsofthisAgreement inordertocarryoutthe Party's obligationsandexerciseitsrightsunderthisAgreement; and (iv) to notify the other Party promptly of any unauthorized use or disclosure of the Confidential InformationandtocooperatewithandassisttheotherPartyineveryreasonablewaytostopor minimize such unauthorized use or disclosure.
c. Injunction. ThePartiesagreethatif a courtof competentjurisdictiondeterminesthateitherParty has breached, or attemptedor threatenedto breach, its confidentialityobligationsto the other Party or the other Party's proprietaryrights, the non -breachingParty will be entitled to obtain appropriate injunctive relief and other measures restrainingfurther attempted or threatened breachesof suchobligations. Suchinjunctivereliefor othermeasureswill be in additionto, and notinlieuof, anyotherrightsandremediesavailabletotheParty.
6. Client Data
a. The CLIENT shall own all rights, title and interest in and to all of the CLIENT Data and shall have soleresponsibilityfor thelegality, reliability, integrity, accuracyandqualityoftheCLIENTData. b. MERIDIANshallfollowits commerciallyreasonablebackupproceduresfor CLIENTDataandsaid procedure may be amended by MERIDIAN in its sole discretion from time to time based upon best practices. In the event of any loss or damage to CLIENT Data, the CLIENT's sole and exclusive remedy shall be for MERIDIANto use reasonablecommercialactivities to restore the lost or damagedCLIENTDatafromthelatestback-upof suchCLIENTDatamaintainedbyMERIDIAN in accordance with the backup procedure described herein. MERIDIAN shall not be responsible foranyloss, destruction, alterationordisclosureofCLIENTDatacausedbyanythirdparty (except those third parties subcontracted by MERIDIAN to perform services related to CLIENT Data maintenance and back-up).
c. MERIDIANshall, inprovidingaccesstotheServices, complywithitsPrivacyPolicyrelatingtothe privacyand securityof the CLIENTData availableat http://www.merldianks.com/pdvacy- statement/ or such other Policy as may be given to the CLIENT from time to time, as such document may beamended from time to time by MERIDIAN in its sole discretion.
TheCLIENTshallnot storeor processPersonallyIdentifiableInformation (PII) or Personally Identifiable Health Information ( PHI) within the Software. PII is defined as information that can be usedto uniquelyidentifya single individualand may includean individual's namein combination with a Driver's License, Social Security Number or Credit Card Information. The definition of PII varies dependingon international, federal, state and local laws and the definitioncontained herein shallbeusedforreferencepurposesonlyandshallnotbeconstruedascoveringallpossible definitionsof PII. PHIisdefinedasanyinformationthatis relatedtoanindividual's healthrecord asdefinedbytheHealthInsurancePortabilityandAccountabilityAct (HIPAA). e. PHI/PII Processing - The partiesshallcomply, andwarrantthatthey havecomplied, with implementingallapplicabledataprotectionandprivacylawsandregulationsinanyrelevant jurisdiction (together, the "DataProtectionLaws"), andwhere, inconnectionwiththisAgreement, the SoftwareIs processinginformationrelatedto PHI/PII on behalfof the CLIENT, MERIDIAN shall:
i. Process the PHIIPII only on the written Instructionsof CLIENT; ii. Makeall reasonableeffortsto implementappropriatetechnicalandorganizationalmeasures toprotectthosePHI/PIIagainstaccidentalor unlawfuldestructionoraccidentalloss, alteration, unauthorizeddisclosureor access, in particularwhere the processinginvolvesthe transmissionofdataoveranetwork, andagainstallotherunlawfulformsofprocessing; iii. ReturnordestroyallsuchpersonaldatapromptlyupontheterminationofthisAgreement, or at any time during the term of this Agreement upon written instructions from CLIENT; iv. NotdisclosePHI/PIItoanypersonexceptasrequiredorpermittedbythisAgreementorwith CLIENT' s written consent;
V.
ProvidefullcooperationandassistancetoCLIENTinimplementinganyproceduresrequired inordertocomplywithdataprivacylawstowhich -CLIENTissubject, asadvisedbyCLIENTfrom time to time; vi. NotprocessPHI/PII exceptto theextentreasonablynecessaryto the performanceof thisAgreement; vii. NotifyCLIENTimmediatelyintheeventofanybreachofthesecurityof suchpersonaldata, and cooperatewith CLIENTin anypost- breachinvestigationor remediationefforts; and viii. NotifyCLIENTpromptlyintheeventthatMERIDIANisrequiredbylaw, courtorder, warrant, subpoena, orotherlegalorjudicialprocesstodiscloseanyPHI/PIIto anypersonotherthanCLIENT.
TheCLIENTshallmakeall reasonableeffortsto ensurethatthosePersonalDataareaccurateand uptodateat alltimes, totheextentthatit iswithinCLIENT's abilityto doso.
ThePartiesheretoagree, thattheabovewarrantiesrelatingto PHIandPII areMeridian's sole responsibilities related to the processing and control of CLIENT PHI and PII.
7. European Union Clients
Intheeventthat CLIENTwill accessPII originatingfroma countryin the EuropeanEconomicArea EEA") orfromacountryoutsidetheEEA, MERIDIANshall, ifrequestedbyCLIENT, willcomplywith theapplicablePrivacyLawLegislationincoordinationwiththeEuropeanCommission, relatingto requirementsof the EuropeanUnion's Directiveon DataProtection. CLIENTwarrantsthatit hasthe consentof its employees, independentcontractorsor anyotherindividualwhosePIIis being processedand/ortransmittedwithintheServicesandMERIDIANshallhavenoliabilityshouldCLIENT nothavereceivedsuchconsent. CLIENTwillindemnify, defendandholdMERIDIANharmlessshould anysuchindividualorgroupofindividualsbringanysuitagainstMERIDIANforviolationofanyapplicable law.
8. Limited Warranty / Acceptance
a. MERIDIANwarrantsthatitwillperformtheServicesinamannerconsistentwithindustrystandards reasonablyapplicabletotheperformancethereof. MERIDIANdoesnotwarrantthatClient's use oftheServiceswillbeuninterruptedorerrorfree. ThelimitedwarrantiessetforthinthisAgreement do not applyto any deviationby the Softwarefrom the specificationssetforth in the applicable Schedulethatis causedby, or resultsfrom, (i) improperusageof SoftwareAPIs (Application ProgrammingInterfaces) ortheintroduction/importofcorruptdataintotheSoftwarebyanyone otherthanMERIDIAN; (ii) useoftheServicesforanypurposeotherthanthatauthorizedinthis Agreement; (III) useoftheServicesincombinationwithothersoftware, dataorproductsthatare defectiveor incompatiblewith, or arenotauthorizedbyMERIDIANforusewith, theServices; iv) anymalfunctionof CLIENT's software, hardware, computersor computer -relatedequipment; v) CLIENT'Sfailureto useanyUpdatesmadeavailableby MERIDIAN; or (vi) aneventof Force Majeure ( defined below).
b. Meridiandoesnotandcannotcontroltheflowofdatatoorfromthesoftwareandotherportions oftheinternet. suchflowdependsinlargepartontheperformanceofinternetservicesprovided orcontrolledbythirdparties. attimes, actionsorinactionsofsuchthirdpartiescanimpairordisrupt customer's connectionsto the internet (or portions thereof). althoughmeridianwill use commerciallyreasonableeffortstotakeallactionsitdeemsappropriateto remedyandavoidsuch events, meridiancannotguaranteethatsucheventswill notoccur. accordingly, meridiandisclaims anyandallliabilityresultingfromor relatedtosuchevents. theforegoingwarrantiesaremadein lieuof all otherwarranties, expressandimplied, including, withoutlimitation, anyimplied warrantiesofmerchantabilityorfitnessforaparticularpurpose, andanywarrantiesarisingoutof courseof dealingor courseof performance. exceptas expresslyprovidedherein, thereis no warrantyagainstinterferencewithclient's enjoymentofthe softwareor againstinfringement, the servicesareprovided "asis;' andmeridiandisclaimsanywarrantyastothequality, operationof, accesstoor useofalloranypartof thesoftwareandanywarrantythat (1) theserviceswilloperate uninterruptedor error -free, (it) the resultsarisingoutof the useof the serviceswill be accurate, completeor error -free, or (iii) the serviceswill meetthe needsof clientor its clients, agentsorsuppliers. c. AcceptanceoftheSoftwarewillbeupontheCLIENT's receiptoftheURLfromMERIDIAN, where CLIENT will be provided access to the Software.
9. Other CLIENT Obligations
a. The CLIENT shall provide MERIDIAN with:
I. all necessary cooperation in relation to this Agreement; ii. all necessaryaccesstosuchinformationasmaybe requiredby MERIDIANinorderto render the Services, includingbut not limited to CLIENT Data, security access informationand configuration services;
iii. comply with all applicable laws and regulations with respect to its activities under this Agreement;
iv. carryoutallotherCLIENTresponsibilitiessetoutinthisAgreementinatimelyandefficient manner. Inthe eventof any delaysin the CLIENT's provisionof such assistanceas agreed by the parties, MERIDIANmay adjust any agreed timetable or deliveryschedule as reasonably necessary;
V. ensure that the Authorized Users use the Services and the Documentation in accordance withthetermsandconditionsofthisAgreementandshallberesponsibleforanyAuthorized Users breach of this Agreement;
vi, obtainand maintainall necessarylicenses, consents, and permissionsnecessaryfor MERIDIAN, its employees, subcontractorsand/or agentsto performtheir obligationsunder this Agreement, includingwithout limitation the Services; vii. ensurethatits networkandsystemscomplywiththerelevantspecificationsprovidedbyMERIDIAN from time to time; and viii. be solely responsiblefor procuring and maintainingits network connectionsand telecommunicationslinksfromitssystemsto MERIDIAN'Sdatacenters, andallproblems, conditions, delays, deliveryfailuresandallotherlossor damagearisingfromor relatingto the CLIENT's networkconnectionsor telecommunicationslinksor causedbythe Internet.
10. Indemnification
a. EachParty (the "IndemnifyingParty") agreesto defendtheotherParty, its affiliatesandeachof their respective officers, directors, employees, contractors and agents ( each an " Indemnified Party") fromandagainstanyaction, claim, suit, investigationor otherproceedingbroughtbya thirdparty (a "Claim") tothe extentsuchClaimresultsfromthe IndemnifyingParty's breachofthis Agreementor the negligence, willfulmisconductor fraudor violationof lawon the partof the IndemnifyingParty, its officers, directors, employees, agents or other representativesin connectionwiththis Agreement. The IndemnifyingPartywill indemnifyandhold harmlessthe IndemnifiedParryfromanyliabilities, losses, damages, judgments, awards, fines, penalties, costs andexpenses (includingreasonableattorneys' feesandcostsof defense) incurredbyor levied againstsuchIndemnifiedPartyasaresultofsuchClaimthatinfringesanycurrentlyexistingUnited Statescopyright, patent, trademarkor tradesecretof a thirdparty. b. MERIDIANwill havenoobligationto defendCLIENTwithrespecttoanyclaim, demand, actionor proceeding, described herein, that is based upon:
1) use of otherthan the then -currentreleaseof the Software, if infringementcouldhavebeen avoided by use of the then -current release and the then -current release has been made available to CLIENT; (ii) use of the Services in conjunctionwith CLIENT's data, whereuse with such data gaveriseto theinfringementclaim; (iii) useof the Serviceswithother software, whereuseof such other software gave rise tothe infringement claim; (iv) use of any Services in a mannerinconsistent with its documentation; or (v) use of any Services in a manner that breaches this Contract Agreement. CLIENTwill defendMERIDIANfrom andagainstanyand all liability, damage, lossor expense (includingreasonableattorneys' fees) arisingout of any claim, demand, actionor proceedingbasedon allegationsarisingas a resultof (i) use of the Servicesby CLIENTin conjunctionwithanydata, equipmentor softwarenotprovidedbyMERIDIAN, wheretheServices wouldnotitselfbe infringingor otherwisethesubjectof theclaim; (ii) useof theServicesby CLIENTina mannernotpermittedbythisAgreement; (ill); (iv) useoftheServicesbyCLIENTin any unlawful, improperor inappropriatemanneror for any unlawful, improperor inappropriate purpose; (v) anyclaimofinfringementofanypatentorcopyrightormisappropriationofanytrade secretin whichCLIENTor any affiliateof CLIENThas a pecuniaryor other materialinterest; or vi) breach of any of CLIENT's warranties or covenants.
11. Term and Termination
The term of this Agreement will begin on the Effective Date and shall continue for the Initial SubscriptionTermand, thereafter, shallbeautomaticallyrenewedforsuccessiveperiodsoftwelve 12) months (" Renewal Period"), unless:
i. Eitherpartynotifiestheotherpartyoftermination, inwriting, atleastsixty (60) calendardays beforetheendof theInitialSubscriptionTermor anysubsequentRenewalPeriod, in which case this Agreement shallterminate uponthe expiration ofthe applicable InitialSubscription Term or Renewal Period; or
ii. Otherwiseterminatedin accordancewith the provisionsof this Agreement; and the Initial SubscriptionTermtogether with any subsequent RenewalPeriodsshall constitutethe entire Subscription Term.
b. EitherpartymayterminatethisAgreementimmediatelyuponnoticetotheotherpartyifsuchother partymateriallybreachesa provisionof this Agreementor Schedule, as applicable, and fails to curesuchbreachwithinthirty (30) calendardaysafter receiptof noticeof suchbreachfrom the non -breachingparty. If, in the solejudgmentof the non -breachingparty, suchbreachcannot reasonablybecuredwithinsuchthirty (30) calendardayperiod, thenon -breachingpartymay, in itssolediscretion, grantthebreachingpartyanadditionalthirty (30) calendardayperiodfollowing theexpirationofthefirstthirty (30) calendardayperiodinwhichtocuresuchbreach; providedthat the non -breaching party may terminate this Agreement or such Schedule, as applicable, immediatelyif thebreachingpartyhasfailedtocuresuchbreachwithinsuchsecondthirty (30) calendar day period.
c. EitherpartymayterminatethisAgreementimmediatelyuponnoticetotheotherpartyifsuchother party (1) filesfor or hasfiledagainstit a bankruptcypetitionand suchpetitionis notdismissed Withinsixty (60) calendardays after the filing date, (ii) becomes insolventor (iii) makes an assignment for the benefit of its creditors.
12. Effect of Termination
a. Upon the expiration or termination of this Agreement, I. all rightsgrantedtoCLIENTunderthisAgreementwillimmediatelyterminate; ii. CLIENTwillceaseany furtheruseof the Services.
b. At MERIDIAN'S request, CLIENTwillverifyin writingto MERIDIANthatCLIENThas takenthe actionsdescribedin Section12(a)(ii). MERIDIANmaydestroyor otherwisedisposeofany of the CLIENTDatain itspossessionunlessMERIDIANreceives, nolaterthanten (10) business daysaftertheeffectivedateoftheterminationofthisAgreement, awrittenrequestforthedelivery to the CLIENTof the then most recent back-up of the CLIENTData. MERIDIANshall use reasonablecommercialeffortstodelivertheback-uptotheCLIENTwithinthirty (30) calendardays ofitsreceiptofsuchawrittenrequest, providedthattheCLIENThas, atthattime, paidallfees and chargesoutstandingat and resultingfromtermination (whetheror not due at the dateof termination). TheCLIENTshallpayallreasonableexpensesincurredbyMERIDIANinreturning or disposingof CLIENTData. Theaccruedrightsof the partiesat termination, orthe continuation afterterminationofanyprovisionexpresslystatedtosurviveorimplicitlysurvivingterminationshall notbeaffectedorprejudiced. Therightsandobligationsof eachofthepartiessetforthinSections 2, 3, 4, 5, 6, 7, 8, 10, 12, 13, 14, 17, 18, 20, 21, 23, 24and25andanyotherSectionor Statement hereinthat by its nature is intendedto survivewill survivethe expirationor terminationof this Agreement. AnypaymentsowedbyCLIENTasoftheterminationdateshallbecomeimmediately due and payable.
13. Limitation of Liability
Exceptinthecaseofaninfringementbyclientofanyofmeridian'sproprietaryrights, neitherparty will be liable to the other party for any lost profits, lost data or special, indirect, incidental, consequentialorpunitivedamagesofanynature, foranyreason, including, withoutlimitation, the breachofthisagreementoranyterminationofthisagreement, whethersuchliabilityisasserted onthebasisofcontract, tort (includingnegligenceorstrictliability) orotherwise, evenifsuchparty hasbeenwarnedofthepossibilityof suchdamagesandnotwithstandinganyfailureof essential purposeof any limitedremedyof anykind. exceptas expresslysetforth herein, all remedies, including, withoutlimitation, theterminationofthisagreementandalloftheremediesprovidedby law (and not excludedpursuantto theforegoingsentence) will be deemedcumulativeand not exclusive. in noeventwilltheliabilityofmeridianunderthisagreementexceedthetotalfeespaid by clienthereunderduringthe twelve (12) monthspriorto the dateany claimIs madeagainst MERIDIAN.
14. Government Use/ Procurement
MERIDIANprovides the Service and access to the Softwarefor ultimate U.S. Governmentend use solelyin accordancewith thefollowing: Governmenttechnicaldata andsoftwarerightsrelated to theServiceandtheSoftwareincludeonlythoserightscustomarilyprovidedtothepublicas definedinthisAgreement. Thiscustomarycommerciallicenseis providedinaccordancewithFAR
12.211 (TechnicalData) andFAR 12.212 (Software) and, for Departmentof Defensetransactions, DFAR 252.227-7015 (TechnicalData — CommercialItems) and DFAR227.7202-3 (Rights in CommercialComputerSoftwareorComputerSoftwareDocumentation). Ifagovernmentagency has a needfor rightsnot conveyedundertheseterms, it mustnegotiatewith MERIDIANto determineif thereareacceptabletermsfor transferringsuchrights, anda mutuallyacceptable written addendumspecificallyconveyingsuch rights must be includedin any applicable agreement.
b. Each party shall complywith the export laws and regulationsof the UnitedStatesand other applicablejurisdictionsin providingandusingtheServiceandtheSoftware. Withoutlimitingthe foregoing: (a) eachpartyrepresentsthatit is notnamedonanyU.S. governmentlistof persons orentitiesprohibitedfromreceivingexports; and (b) eachPartyshallnotpermitanyUsertoaccess or use the Serviceandthe Softwarein violationof any U.S. exportembargo, prohibitionor restriction.
15. Assignment
CLIENT may not assign or otherwisetransfer this Agreementor Its rights and obligations hereunderwithoutthepriorwrittenconsentofMERIDIAN, whichconsentwillnotbeunreasonably withheld. Anytransactionorseriesoftransactionsinwhich (i) morethanfiftypercent (50%) of the outstandingvotingstockor membershipinterestsof CLIENTaretransferredto a thirdparty, or it) allor substantiallyallofCLIENT'sassetsaresoldtoathirdparty, willbedeemedanassignment of this Agreement. Any purportedassignmentor othertransferwithoutthe consentof MERIDIAN a) will bevoidandof noforceor effect, and (b) willconstitutea materialbreachofthisAgreement.
16. Force Majeure
Exceptfora party'spaymentobligationshereunder, neitherpartywillbedeemedindefaultofthis Agreementtotheextentthatperformanceofitsobligations, or attemptstocureanybreachthereof, are delayed or preventedby reasonof any act of God, fire, naturaldisaster, accident, terrorist attack, act of government, network or telecommunicationsystem failure, sabotage or anyothercausebeyondthe controlof suchparty ("ForceMajeure"), providedthatsuchparty promptly gives the other party notice thereof. In the event of such Force Majeure, the time for performanceor cure will be extendedfor a periodequal to the durationof the ForceMajeurebut not in excess of six ( 6) months.
17. Severability
Ifa courtof competentjurisdictiondeterminesthatanyprovisionofthisAgreementisillegal, invalid or otherwise unenforceablefor any reason, such provision will be deemed stricken to the extent thatit is illegal, invalidor otherwiseunenforceable. All remainingprovisionswillremaininfullforce andeffectandthisAgreementwillbeinterpretedasif it hadnotcontainedtheseveredprovision.
18. Governing Law
Issuesregardingthevalidity, ownershipor enforcementof anycopyright, patent, trademarkor other proprietaryright licensed or sublicensed hereunderwill be determined underthe applicable lawof theUnitedStatesandtheStateofCalifornia, asapplicable. Withrespecttoall otherissues, this Agreementwill be construedunderand governedby the substantivelawsof the Stateof Californiawithoutresorttoconflictoflawsprinciples. Eachpartyagreesthatanylegalproceeding commencedbyonepartyagainsttheotherpartyunderthisAgreementwillbebroughtinanystate or FederalcourthavingjurisdictionoverOrangeCounty, California. Eachpartysubmitsto such jurisdictionandwaivesanyobjectionto venue or claimof inconvenientforum. ThisAgreementwill not be governedby the United Nations Conventionon Contracts for the InternationalSale of Goods, the applicationof whichis expresslyexcluded.
19. Headings
Captionsandsectionheadingsusedhereinareforreferencepurposesonlyandwillnotcontrolor alter the meaning of this Agreement as set forth in the text.
20. Waiver
a. AwaiverofanyrightunderthisAgreementisonlyeffectiveif it isinwritinganditappliesonlyto thepartytowhomthewaiverisaddressedandtothecircumstancesforwhichit isgiven. b. Unlessspecificallyprovidedotherwise, rightsarisingunderthisagreementarecumulativeanddo not exclude rights provided by law.
21. Notices
Anynoticerequiredtobegivenunderthisagreementshallbeinwritingandshallbedeliveredbyhand or sentbypre -paidfirst-classpostor recordeddeliveryposttotheotherpartyatitsaddresssetoutin thisagreement, orsuchotheraddressasmayhavebeennotifiedbythatpartyforsuchpurposes. A noticedeliveredbyhandshallbedeemedto havebeenreceivedwhendelivered (orrfdeliveryis not inbusinesshours, at9 AMonthefirstbusinessdayfollowingdelivery). Acorrectlyaddressednotice sent by pre -paid first-class post or recordeddelivery post shall be deemed to have been receivedat thetimeat whichit wouldhavebeendeliveredin the normalcourseof post.
If to MERIDIAN: With a copy to: If to CLIENT: ATTN: With a copy to:
ATTN: Contracts ATTN: Legal Lori Schneider, HR Clerk of Council Meridian Department City of Santa Ana City of Santa Ana Knowledge Meridian 20 Civic Center Plaza 20 Civic Center Plaza Solutions, LLC Knowledge M- 24 M- 30
80 Iron Point Solutions, LLC P. O. Box 1988 P. O. Box 1988 Circle 80 Iron Point Santa Ana, CA 92701 Santa Ana, CA 92701 Suite 100, Circle
Folsom, CA Suite 100
95630 Folsom, CA
95630
22. No Partnership or Joint Venture
Nothingin thisagreementis Intendedto or shalloperateto createa partnershipbetweenthe parties, or authorizeeither partyto act as agentfor the other, and neither party shall have the authorityto actinthenameoron behalfofor otherwiseto bindtheotherinanyway (including, butnotlimitedto, themakingofanyrepresentationorwarranty, theassumptionofanyobligation or liabilityandthe exerciseof anyrightor power). ThisAgreementshallnotpreventMERIDIAN fromenteringintosimilaragreementswiththirdparties, orfromindependentlydeveloping, using, sellingorlicensingdocumentation, productsand/orserviceswhicharesimilartothoseprovidedunder this Agreement.
23. Non- Sollcitation
In additionto the obligations set forth in Section5, during the term of this Agreementand for a periodof twelve (12) monthsImmediatelyfollowingthe lastoccurrenceof anyintroductions, interviews, orprovisionofservicesunderthisAgreement, thePARTIESagreenotto solicitor hire, indirectlyordirectly, ineitheranemployeeorindependentcontractorcapacity, anyindividualwho 1) wasintroducedunderthisAgreement; III) thePARTIEShaveinterviewedunderthisAgreement; III) has providedservicesunder this Agreement, or (iv) the PARTIESor its employees, representativesandoragentshavereceivedinformationaboutorastheresultofanyintroduction, interviewor serviceprovidedunderthisAgreement. Shoulda PARTYbreachthis Sectionof the Agreementinanyinstancethe breachingPARTYwill paytheotherPARTYanamountof two (2) times the then currentannualsalary (includingany applicablebonuscompensation) of the individualsolicited. Saidpaymentwill be madewithinfifteen (15) calendardaysofthe breachas notifiedin writingbythe non -breachingPARTY. The Partiesheretofurtheragreethat the limit on liability as defined hereindoes not apply to this Section 23.
24. Disputes and Arbitration
a. Thepartiesagreethatintheeventofadisputeorallegedbreachtheywillworktogetheringood faith to resolve the matter internally by escalating it to higher levels of managementand, if necessary, to use a mutually agreed upon alternative dispute resolution mechanism (other than arbitration) priorto resortingto arbitration. If thepartiesare unsuccessfulat resolvingsaid dispute or alleged breach, then the parties shall seek arbitration. Except as set forth in Section 5, the partiesagreeto submitto bindingarbitrationwithinsix (6) monthsof thelasteventgivingriseto anycontroversyarisingoutofthisAgreementorinvolvingtheconstructionorapplicationofanyof the termsof this Agreementandto waive anystatuteof limitationsto the contrary. Notificationto theotherpartyof awrittenrequestforarbitrationshallcomplywithSection22governingNotices.
Any timelyand properlynoticedrequestfor arbitrationshallbe submittedto bindingarbitration throughtheAmericanArbitrationAssociationpursuantto itsCommercialArbitrationRules. Each partyshallpayforitsownattorneys' feesandcostsforthearbitration. Thepartiesshallsplitequally thecostof thearbitrator. Bothpartiesareentitledto conductdiscoveryin accordancewithany applicablelaw. ThearbitratorshallapplyVirginiaandFederallawto the issuespresentedand shall issue a written memorandum of decision. The decision of the arbitrator shall be final and binding, and the parties waive the right to a jury trial, a trial de novoor appeal except for the purposeof enforcingthe arbitrator's decision. The prevailingpartywill be entitledto recover reasonableattorneys' feesandcostsof anyactionfor enforcement, the amountof any such attomeys' feesandcostsawardto bedeterminedbytheArbitrator. b. Exceptas setforth in Section5 with regardto Injunctiverelief, the partiesexpresslystatethatit is their intent to arbitrate disputes between them. Therefore, this Agreement shall be construed so as to be consistent with applicable Federal and Virginia law and to be enforceable to the maximum extentallowablebylawto providearbitrationastheforumto resolvetheirdisputes. If necessary, anyportionofthis Agreementthatis unenforceableby law shallbestricken, andthe arbitratoror the court, as the case may be, shall have the power to reform this Agreement to the extent necessaryto complywithapplicablelawandto giveeffectto the parties' intentthattheyshall arbitrate their disputes.
25. Publicity
CLIENT grants MERIDIAN permissionto utilize the CLIENT's trademarks, trade names, or other designationsin any promotion, press release or publication subject to CLIENTS advance approvalof saidpromotion, pressreleaseor publication. MERIDIANwill provideproposedpromotion, press releaseorpublicationto CLIENTwithina reasonabletimebutnotlessthantwobusinessdaysprior to draft being made public. CLIENTwill have the right to make any changesthat CLIENT deems reasonably necessary.
26, Entire Agreement
a. Exceptas otherwise providedfor herein, this Agreement constitutes the entire agreement between thepartiespertainingto thesubjectmatterhereofandsupersedesallpriorandcontemporaneous agreements, negotiationsandunderstandings, oralorwritten, betweenthepartieswithrespectto thesubjectmatterhereof. ThisAgreementwill bebindingon and inureto the benefitofthe legal representatives, successorsand permittedassignsof the parties. ThisAgreementmaynot be modified or refined unless amended by both Parties under a written and signed amendment. The issuanceof anyadditionaltermsandconditionsby eitherPartyheretoincludedwith purchase orders or other documents are null and void. In the event of any conflict between these General TermsandConditionsanda provisionof anySchedule, theprovisionoftheSchedulewillcontrol, but only with respect to the subject matter of the Schedule.
27. Service Level Agreement and Software Support
TheServicesprovidedbyMERIDIANunderthisagreementareboundbytheServiceLevelAgreement SLA) as described herein. In the case of an SLA violation, the respective remedies described herein willapply. TheSLApenaltyapplicableinanygivenmonthis subjecttoatotalcumulativepenaltycap of 10% of the current month's hosting service fees ("Service Credits"), Any Service Credits due underthis agreementwill be credited promptly but in no event later than the quarter following the calculation of the Service Credit.
MERIDIANwill be provideda rampup periodof ninety (90) daysfrom softwareGo Live (Production go live date) before any SLA requirements and subsequent remedies go into effect.
SystemAvailability: will mean, withrespectto anyparticularcalendarmonth, theratioobtainedby subtracting Unscheduled Downtime during such month from the total time ( measured in minutes) duringsuchmonth, andthereafterdividingthe differenceso obtainedbythe total timeduringsuch month. Representedalgebraically, SystemAvailabilityfor any particularcalendarmonthis determined as follows:
System Availability = (
Total Monthly Time — Unscheduled Downtime)
Total Monthly Time
Note: "TotalMonthlyTime" isdeemedto includeallminutesintherelevantcalendarmonthexcluding minutes of downtime caused by Scheduled Downtime, only to the extent such minutes are included within the Subscription Agreement Term.
MERIDIANwill undertakecommerciallyreasonablemeasuresto ensurethat SystemAvailability equals or exceeds 99, 70 % duringeachcalendarmonth. MERIDIANwill undertakecommercially reasonablemeasuresto notifyCLIENTin advanceof ScheduledDowntime. Thetimingof Scheduled Downtime is subject to change at MERIDIAN' s sole discretion.
Measurement and Reports: MERIDIANwill monitorSystemAvailabilitymetricson an ongoingbasis.
Allmeasurementsof SystemAvailabilitywill becalculatedona monthlybasisforeachcalendarmonth duringthe termof this agreement. MERIDIANshallprovidethe SystemAvailabilityreportto CLIENT, on an as requiredbasis, when requestedby CLIENT. This reportwill containperformancemetrics againstthe SystemAvailabilitySLA obligationsas depictedherein; and specificto unscheduled downtimeeventsonly.
Remedies: IntheeventSystemAvailabilityisnotequaltoorgreaterthan99.70% fora givenmonth, CLIENTwill beentitledto servicelevelcreditsagainstitssubsequentpaymentobligations (as setforth in this SubscriptionAgreement) accordingto the following chart:
System Availability Available Credit (% of monthly service fee)
99. 70% - 100. 00% No Credit.
95. 000/6- 99. 69% Threepercent (3%) of theapplicablemonthlyhostedservice fees for the applicable calendar month.
90. 00% - 94. 99% Sixpercent (6%) ofthe applicablemonthlyhostedservice fees for the applicable calendar month.
89, 99% Tenpercent (10%) of theapplicablemonthlyhostedservice fees for the applicable calendar month.
CLIENT's creditsunderthissectionareCLIENT's soleandexclusiveremedywithrespectto any UnscheduledDowntimeoranyfailurebyMERIDIANtomeettheServiceAvailabilityrequiredbythis agreement. Themonthlyavailablecreditis cappedatthe lesserof $5,000or thetotalcapassetforth in the SystemAvailability section herein.
1) Exceptions
CLIENTshallnotreceiveanycreditsinconnectionwithanyfailureordeficiencyAvailabilitycaused by or associated with:
I. ForceMajeureeventsbeyondMERIDIAN's reasonablecontrol, including, withoutlimitation, acts of any governmental body, war, insurrection, sabotage, armed conflict, embargo, fire, flood, strikeorotherlabordisturbance, interruptionofordelayintransportation, unavailability of or interruptionor delay In telecommunicationsor third parry services, virus attacks or hackers, failure of third partysoftware (including, without limitation, ecommercesoftware, paymentgateways, chat, statisticsor freescripts) or inabilityto obtainrawmaterials, supplies, or power used in or equipment needed for provision of this Schedule; ii. Failureof accesscircuitsto the ISP Network, unlesssuchfailureis causedsolelybyMERIDIAN; iii. Scheduledmaintenanceand emergencymaintenanceand upgrades; iv. DNS issues outside the direct control of MERIDIAN;
V. Issues with FTP, POP, or SMTP CLIENT access;
vi. False Schedulebreachesreportedas a resultof outagesor errorsof any MERIDIAN measurement system,
A. CLIENTSactsoromissions (oractsoromissionsofothersengagedorauthorizedbyCLIENT), including, withoutlimitation, customscriptingor coding (e.g., CGI, Pad, HTML, ASP), any negligence, willful misconduct, or use of the Servicesin breachof MERIDIAN's Termsand Conditionsand AcceptableUse Policy;
viii. E-mail or webmail delivery and transmission;
ix. DNS ( Domain Name Server) Propagation; and / or
X. Outageselsewhereon the Internetthat hinderaccessto your account. MERIDIANis not responsibleforbrowseror DNScachingthatmaymakeyoursiteappearinaccessiblewhen otherscanstill accessit. MERIDIANwill guaranteeonlythoseareasconsideredunderthe control of MERIDIAN: MERIDIAN server links to the Internet, MERIDIAN'S routers, and MERIDIAN' S servers.
2) Software Support. MERIDIANwill providesoftwaresupportas definedbelow:
i. During Standard Business Hours
ii. Accessforupto three (3) namedsystemadministrators, providedtheirsuccessfulcompletion of Meridian's administratorproficiencytraining
iii. Help desk supportand guidanceon the use of existingbase productfunctions. Effort exceedinga totalof one (1) hourperonefunctionisconsideredTrainingandis notincluded as part of Software Support.
iv. Troubleshooting of CLIENT reported functional and technical issues related to the intended use of the Software.
V. Troubleshootingof third -partyor client -developedcontent, as it relatesto successfully launching and tracking in the Software.
To provideeffectivesupportfor CLIENT submittedsupportrequests, MERIDIANwill categorize issuesbasedupontheissue'sseveritylevelandthetimeitwasreceived. MERIDIANmayrequire additionaldetailsfromCLIENTafterinitialissuesubmissiontohelpresolvetheissue. Additional details regarding severity levels and response time targets are detailed in MERIDIAN's Support Policy.
3) SupportExclusions. Allothersupportthatis notexplicitlydefinedin Section2 SoftwareSupport in this Schedule is excluded.
4) Credit Request and Payment Procedures.
In order to receivea creditfor systemavailabilityas definedin Section27b herein, CLIENT must make a request therefore by sending an email message to [email protected]. Each requestinconnectionwiththisSchedulemustincludeCLIENT'saccountnumber (perMERIDIAN's invoice) andthe datesand times of the unavailabilityof CLIENT's Web siteand mustbe received by MERIDIAN within ten ( 10) business days after CLIENT's Web Site was not available. If the unavailability is confirmed by MERIDIAN, credits will be applied within one week after MERIDIAN's receipt of CLIENT' s credit request.
Notwithstandinganythingtothecontraryherein, thetotalamountcreditedtoCLIENTinaparticular monthunderthisServiceLevelAgreementshallnotexceedthetotalSubscriptionfeepaidby CLIENTfor suchmonthfor theaffectedServices. Creditsareexclusiveofanyapplicabletaxes chargedtoCLIENTorcollectedbyMERIDIANandareCLIENT's soleandexclusiveremedywith respectto anyfailureor deficiencyIn theAvailabilityof Service.
28. Insurance
Meridianshallprocureandmaintainfor thedurationof the contractinsuranceagainstclaimsfor injuriesto personsor damagesto property, whichmay arise from or in connectionwith the performanceof the work hereunder, and the resultsof that work by the Meridian, its agents, representatives, or employees..
A. Minimum Insurance Coverage - Coverage shall beat least as broad as:
I. CommercialGeneralLiability (CGL): InsuranceServicesOffice Form CG 00 01 coveringCGLon an "occurrence" basis, includingproductsand completedoperations, propertydamage, bodilyinjuryandpersonal & advertisinginjurywithlimitsnolessthan 1,000,000peroccurrence. If a generalaggregatelimitapplies, eitherthegeneral aggregatelimitshallapplyseparatelyto this projectllocation (ISO CG 25 03 or 25 04) or the general aggregate limit shall be twice the required occurrence limit.
2. Workers' CompensationinsuranceasrequiredbytheStateofCalifornia, withStatutory Limits, andEmployer's LiabilityInsurancewithlimitofnolessthan $1,000,000per accident for bodily injury or disease.
B. OtherInsuranceProvisions- The insurancepoliciesare to contain, or be endorsedto contain, the following provisions:
f. AdditionalInsuredStatus- TheCity, itsofficers, officials, employees, andvolunteersareto becoveredasadditionalinsuredsontheCGLpolicywithrespecttoliabilityarisingoutof workoroperationsperformedbyoronbehalfoftheMeridianincludingmaterials, parts, or equipmentfurnishedinconnectionwithsuchworkoroperations. Generalliabilitycoverage can beprovidedinthe form of an endorsementto Meridian's insurance (at leastas broad as ISOFormCG 20 10 11 85or bothCG20 10, CG 20 26, CG 20 33, or CG 20 38; and CG 20 37 forms If later revisions used).
PrimaryCoverage- Foranyclaimsrelatedto this contract, Meridian's insurancecoverageshallbe primaryinsuranceprimarycoverageatleastasbroadasISOCG20010413asrespectstheCity, itsofficers, officials, employees, andvolunteers. Anyinsuranceor self-insurancemaintainedby theCity, its officers, officials, employees, or volunteersshallbeexcessof theMeridian's insurance and shall not contribute with it.
Noticeof Cancellation- Eachinsurancepolicyrequiredaboveshallstatethatcoverageshallnot be canceled, exceptwith noticeto the City.
Waiverof Subrogation- MeridianherebygrantstoCitya waiverofanyrighttosubrogation, which anyinsurerofMeridianmayacquireagainsttheCitybyvirtueofthepaymentofanylossunder suchinsurance. Meridianagreesto obtainanyendorsementthatmaybenecessarytoaffectthis waiverofsubrogation, butthisprovisionappliesregardlessofwhetherornottheCityhasreceived a waiver of subrogation endorsement from the insurer.
C. Acceptabilityof Insurers- Insuranceis to be placedwith insurersauthorizedto conduct businessin the state with a current A.M. Best's rating of no less than A:VII, unless otherwise acceptable to the City.
D. Verificationof Coverage- Meridian shall furnish the City with original Certificatesof Insurance including all required amendatoryendorsements (or copies of the applicable policylanguageeffectingcoveragerequiredbythisclause) anda copyofthe Declarations andEndorsementPageof theCGLpolicylistingall policyendorsementsto Citybefore workbegins. However, failuretoobtaintherequireddocumentspriortotheworkbeginning shall not waiveMeridian's obligationto providethem. The Cityreservesthe rightto require complete, certifiedcopies of all required insurancepolicies, includingendorsements required bythese specifications, at any time.
E. Subcontractors- Meridianshallrequireandverifythatallsubcontractorsmaintaininsurance meetingall the requirementsstatedherein, and Meridianshall ensurethat City is an additional insured on insurance required from subcontractors.
F. Special Risks or Circumstances- City reservesthe right to modify these requirements, including limits, based on the nature of the risk, prior experience, insurer, coverage, or other special circumstances.
29. Survival
In the event of any termination of the Agreement, Sections 2, 3. 4, 5, 6, 7, 8, 9, 10, 11, 12, 13,
14. 15, 16, 17. 18, 19, 21, 22, 23, 24, 25, 27, and 28 shall surviveand continuein effect.
MERIDIAN: CLIENT:
MERIDIAN KNOWLEDGE SOLUTIONS,
L gr ra, limited iabili company
By: { % By:
PrintedName:S el- f 1A , -Ftrc-1'& 2TP
By:
Name: Kristine Ridge
Title: CkA I5 ' It T7t5'j-(LgT117C" Title: CityManagerOr- t c92Date:
DS , a. 5 . ^ oa^ . Date:
Signatures continue on the next page]
ATTEST:
Daisy Gomez
Clerk of Council
APPROVED AS TO FORM:
Sonia R. Carvalho
City Attorney
syfu., a A.
Laura A. Rossini
Chief Assistant City Attorney
RECOMMENDED FOR APPROVAL:
son Motsick
Executive Director
HumanResourcesAgency
SCHEDULEI
IMPLEMENTATION SERVICES SET UP AND OPTIONAL SERVICES
STATEMENT OF WORK # SOW- 001
ThisScheduleOne (1) StatementofWork ("SOW) definestheimplementationServicesbeing providedbyMERIDIANto CLIENTunderthetermsandconditionsoftheSoftwareasa Serviceand SubscriptionAgreement; in orderto enableMERIDIANto deliverandCLIENTto receivethose SoftwareServices; andis executedbyandbetweenMERIDIANandCLIENT.
A. Summary of Scope Implementation Professional Services Standard DeliverableSummary
MeridianLMSsoftwarewillbedeliveredtoCLIENTpreconfiguredwithstandardsettingsderived frombestpractices. CLIENTwillbeprovideda limitedsetof softwareconfigurableoptionsthat canbe personalizedto enablethe softwareto meettheirbusinessneeds (i.e. SCORIAsettings, Virtualmeetingsetup, domainconfigurations). MERIDIANwill (1) workwithCLIENTtodetermine howtheseoptionsshouldbe configuredand (2) implementeachoptionbasedontheset of configurableparametersinherentto thesoftware. Configurationwillbe limitedto theproduct capabilitiesoutlinedin thecurrentversionof theMERIDIANmanualsanddocumentationaswell as the scope defined herein.
ThefollowingtablesummarizesthesoftwaresetuptasksthatMERIDIANwillprovideona FFP basis. Details and scope of these services arefurther defined in Section B herein.
Standard Software Setup Tasks
1. Installationof MeridianLMSEnvironments 2, DiscoverySession/JointRequirements Development ( JRD)
3. Configuration & BrandingApplication 4. System Integration
5. Production Installation 6. Training
7. Go Live Support
Additional
8. Historical Data Migration 9. Single Sign -On
10. E-Commerce Integration 11. AdHoc Report Builder Implementation
12. Open Sesame Connection 13. HRIS/User Data Feed
2. Change Control
CLIENTacknowledgesandagreesthatafundamentalguidingprincipleforplanningandexecuting thisprocess, includingtheestablishmentoftheUserrequirements, willbetheutilizationofexisting functionalityoftheMeridianLMSapplicationonanoutoftheboxbasis. Thisfunctionalitywillbe usedto implementanddeploytherequirementsasdefinedhereinandfurtherbytheRequirements documentationtobemutuallydevelopedandapprovedwiththeCLIENT. Theestimatedconsulting fees and the plannedscheduleare basedon this principle. The purposeof the Change Management process is to ensure that requests for Project changes (to requirements or software configuration) are properly recorded, evaluated/assessed, properly dispositioned, and incorporatedintothesoftwareimplementationscopeasrequired, andscheduleswiththeproper priority and deliverable due dates.
8. Scope Details
MERIDIANwill setup CLIENT's solution according to the following in -scope details. Each task is documentedbelow, along with the MERIDIANand CLIENTdeliverablesassociatedwith each task, assumptions, and the acceptance criteria.
Any additionalconfigurations, or e-learningconsultingby MERIDIAN, outsidethe scope defined herein, can be performed by:
a. MERIDIAN Professional Services on a fixed fee or time and materials basis under a separate change request, or
b. CLIENTuponthecompletionof MERIDIANAdministrationtraining.
MERIDIANoffersits DirectLaborRatesas depictedherein. Costestimatesfor anyadditional serviceswill be providedto CLIENT upon CLIENT'S request. Uponexecutionof the Schedule2 ChangeOrder, definingthe additionalworkto be performed, associatedcostandany other relevant information, MERIDIAN will commence work.
1. Standard Setup Tasks: Installation of Meridian LMS Environments.
Thepurposeofthistaskis toestablishthe MeridianLMSpre -productionenvironmentsthatsupport the software implementation frfecycle as outlined further in this SOW and ensure configuration management between software environments. The following software environmentswill be installedwith out of the box settingsas part of this task.
Stage MERIDIAN'SStagingEnvironmentisanenvironmentthatis utilizedtosetuptheExternal) CLIENT software based upon scope defined herein. The Stage environment is availablefor CLIENTAcceptanceTesting, allowingprojectparticipantsand stakeholdersto log in and reviewoverallfunctionality, implementation configurations, product extensions, and integrations that are applicable.
2. Standard Setup Tasks: Discovery SessiontJoint Requirements Development ( JRD) The purposeof thistaskis forthe facilitationofthe Discovery/JointRequirementsDevelopment Sessionto establishMeridianLMSapplicationbranding, systemconfigurations, andintegrations.
Furthermore, thissessionprovideshighlevelbusinessprocessmappingto the MeridianLMS application.
3. Standard Setup Tasks: Configuration and Branding Application The purpose of this task is to configure and test the Meridian LMS software application based upon the completed and approved Requirements Document as defined in task B.2 above.
MERIDIAN Deliverables CLIENT Deliverables
Completethe setup of all agreed upon Graphics per branding checklist software application configurations. specifications.
Setup One (1) branded Meridian LMS
CLIENT specific skin.
Assumptions Acceptance Critcria
Application Branding — MERIDIAN will Configurationscompletedandtestedper deliverone (1) round of final pre -production the Requirements specified in task B. 2 skin mock up to the CLIENT for review and above.
approval prior to setup in the Meridian LMS Meridian LMS application CLIENT Branded CLIENT Stage environment. skin configured and tested, per the Application Branding — MERIDIAN will Requirements specified in task B.2 above. deliver one (1) round of final pre -production
skin review and changes upon applyingto
the Meridian LMS CLIENT Stage
environment.
MERIDIAN will conduct and support five ( 5)
days of Customer Acceptance Testing for
all tasks defined in section B herein.
4. Standard Setup Tasks: System Integration
The purposeof thefollowing task is to setup the inboundto MeridianLMS HRISIntegration. The HRISinboundfeedtransmitsemployeedetailfromCLIENT's HR systemto MERIDIAN (e.g.
Employee Name, Organization, and Job Title).
CLIENT will provide three ( 3) flat files to MERIDIAN, in MERIDIAN's format, for the inbound processing and loading of HRIS data (Organizations, Job Titles, User data). The HRIS/DAILY FEED data (flat files) must follow the specifications designated in MERIDIAN's HRIS templates.
Anyextensionof thefile schema's and/or processing/validationrequirementsmayresultin an expansionofscopeforthistaskandmayrequireadditionalfunding. Meridian's toolto processthe aforementionedflat files performsthe appropriateinsertsand updatesof OrganizationData, Job Titles, then Users, processing all data through the native API's of Meridian LMS.
DIAN Deliverables CLIFNT nr
MERIDIAN Base HRIS template. Backfill and deliveryof the three (3) flat files Configuration of the Meridian LMS HRIS to Meridianfor processing: UserData, Tool based upon the completed Organizations, Job Titles.
Requirements Document specified in task
B. 2 above.
One preproduction load of a subset of
CLIENT productionready data for CAT
purposes.
One productionlead of full user data into
the CLIENT production
environmentwinplionsAcceptance Criteria
One-way HRIS integration inbound to the HRISToolconfiguredandtestedperthe MeridianLMS applicationonly. Requirements specified in task B.2 above, Meridian configure the HRIS and load a in the Meridian LMS CLIENT Stage subset of CLIENT production ready user environment.
data in the Meridian LMS CLIENT Stage One ( 1) final data load in Meridian LMS environmentfor testing purposes. CLIENT Production environment.
MERIDIAN will conduct and support five ( 5)
daysof CustomerAcceptanceTestingfor
all tasks defined in section B herein.
Upon completion of CAT, MERIDIAN will
load a full set of CLIENT production data in
the MeridianLMS CLIENT production
environment.
S. Standard Setup Tasks: Production Installation
The purposeof this task is to complete the installationof the Meridian LMS base application, database, configurations, brandingandintegrationsintothe MeridianLMSCLIENTproduction environment.
Technical support does not extend to other accessible per the Requirements software or hardware support, data specified in task B.2 above, integradon/migration or the resolution of base
product issues.
MERIDIAN will conduct and support five ( 5)
daysof CustomerAcceptanceTestingfor all
tasks defined in section B herein.
6. Standard Setup Tasks: Training
ThepurposeofthistaskistoprovideImplementationReadinessandAdministrativetrainingduring theprojectimplementation. Thedescriptionof thesetrainingsandthenumberof respectivedays is provided below.
Training Types Definitions
ImplementationReadinessTraining (IRT) — two (2) days — ThepurposeofIRTistolevelset terminologyandprovidecoresystemconceptsandfeaturesasitrelatestokeydecisionsthat will be requiredduringthe Discovery/Joint RequirementsDevelopmentSession.
Administrative — two (2) days — ThepurposeofAdministrativetrainingistoprovidethein- depthknowledgenecessaryto supportadministrationsystemfeaturesandfunctionsfor the setupandmanagementof the MeridianLearningManagementSystem.
MERIDIAN•
Conductrequiredtrainingsessionsas Providelist oftrainees, location(s)7nd depicted herein. training equipment in order to facilitate a PrintedStudentGuidesfor upto twelve (12) hands-on training and demonstrationof people. productfeaturesandfunctionality.
Pre -approval of travel reimbursement, if
Assumptions
onsiteinstructorled trainingis required.
Acceptance Criteria
No more than twelve (12) people. Deliveryof the scoped numberof days of Travel costs are not included in the cost. training by type.
ImplementationReadinessTrainingis
provided prior to the Discovery/Joint
Requirements Session.
AdministrativeTrainingistypicallyprovided
towards the end of the implementation.
schedule, prior to the Customer Acceptance
Testinginitiation; butcan be mutuallyagreed
upon.
A minimum of two (2) weeks' notice is required
prior to the schedulingof training in order to
appropriately manage resource schedules and
minimize travel costs/ impacts.
End User Training is not providedwithin the
current scope of services.
Train -the -Trainer Training is not provided
within the current scope of services.
TechnicalTraining is not provided within the
current scope of services.
Training Cancellation Policies
Reschedulingorcancellationsmayresultinacancellationfeeperthefollowingschedule, plusany reasonableandnecessaryexpensesincurredasa resultof preparingtodeliverthetraining describedherein. Notificationof a cancellationor reschedulemust be made to MERIDIANin writing.
Morethan20businessdayspriortotraining — 0% ofstandardTrainingfee. 11-20businessdayspdortotrainingstart— 25% of standardTrainingfee. 6-10businessdayspriortotrainingstart — 50% ofstandardTrainingfee. 0-5 businessdayspriortotrainingstart— 100% ofstandardTrainingfee.
7. Standard Setup Tasks: Go -live Support
Thepurposeof thistask is to provideCLIENTsupportfromtheinitialdeploymentof configurations, branding, andintegrationsintotheMeridianLMSCLIENTProductionenvironment. Thisperiod allowsthe CLIENTto validatethatMeridianLMSapplicationcontainingall configuration, and integrationsintotheProductionenvironment. Furthermore, itis theperiodinwhichtheCLIENTis to finalize administrative configuration settings, new course and content readiness.
8. Additional Tasks: Historical Data Migration
The purposeof this task is to providea Data Migrationwith the standardMeridianLMS implementationservicesas depictedherein. The LegacyData Migration (migrationof user historicaltranscriptdatato MeridianLMS), Meridianwillsupporta one-way, inbound, one-time Productiondatamigrationtoimporthistoricaldatabasedonthemaximumrecordsetofupto100, 000 records.
DIAN Deliverables CLIENT e
MERIDIAN Base Data Migration template. Backfill and delivery ofthe one (1) flat Configuration of the Meridian LMS HRIS Tool file to Meridianfor processing: User based upon the completed Requirements Data, Transcripts.
Document specified in task B. 2 above.
One pre -production load of a subset of
CLIENT productionready data for CAT
purposes.
One production load of full user data into the
CLIENT production environment.
Assumptions Acceptance Criteria
One-way inboundDataMigrationintothe DataMigrationcompletedandtestedper MeridianLMSapplicationonly, the Requirements specified in task B.2 CLIENT cannot change the format of the Data above, in the Meridian LMS CLIENT Migration XLS file template. Stage environment.
Meridian will load a subset of CLIENT One ( 1) final data load in Meridian LMS production ready historical data in the Meridian CLIENT Production environment.
LMSCLIENTStageenvironmentfortesting
purposes.
Content is not included in -scope.
MERIDIAN will conduct and support five ( 5)
days ofCustomerAcceptanceTestingfor all
tasks defined in section B herein.
Upon completion of CAT, MERIDIAN will
perform a one-time full data load of CLIENT
production data in the Meridian LMS CLIENT
production environment.
9. Additional Tasks: Single Sign - On
Thepurposeof thistaskis to provideanActiveDirectoryor SAMLintegrationwiththeMeridianLMS Implementation. Setupis limitedto the MeridianLMSapplicationout -of -the -box solutionfor the integrationof MicrosoftActive Directoryservices/LDAP/SAML2.0.
MERIDIAN Deliverables
If ActiveDirectoryor LDAP: If Active Directory or LDAP:
MapActive Directory (AD) accountsto Provide remote access and credentials MeridianLMS using "sAMAccountName" or to access AD/ LDAP for application other unique identifier. Business Logic to query for
Establish service to query AD. authentication.
Configure IPsec tunnel. Validate AD access in Meridian LMS If SAML 2. 0: CLIENT Stage and Production
Configure SAML Assertion Authentication. environment.
Configure digital certificate for SAML signature SAML 2.0:
validation. Provide SAML Authentication
Configure SSL certificate for Meridian LMS environment. site. Provide digital certificate to enable
SAML digital signature on Meridian LMS
hosting server.
Provide SSL certificate to enable
secured communication between
Meridian LMS and Authentication
provider.
Validate SAML access in Meridian LMS
CLIENT Stage and Production
environment.
AsSUMPtIOTIS Acceptance Criteria
Alternateor multipleDirectoryServicesare out AD/ LDAP/ SAML integration/ access of scope. validated in Meridian LMS CLIENT
Single Sign -On mechanism must be Stage and Production environments; and utilized/ enforced across all domains. per the Requirements specified in task SAML 2.0 Assertion integration assumes user B. 2 herein. accounts already exist in Meridian LMS and
UIDattributes of SAML assertion properly
maps to the Meridian LMS Login ID.
MERIDIAN will conduct and support five ( 5)
daysof CustomerAcceptanceTestingfor all
tasks defined in section B herein.
10. Additional Tasks: eCommerce Integration
The purpose of this task is to provide E-Commerce integration with the Meridian LMS implementation. The Meridian LMS application has native and standard integrationcapabilities with CyberSource, PayPal, Digital River, Authorize.Net and Elavon's e-commerce engine.
Meridianwillsupporttheconfigurationandsetupofoneintegrationto workwithClient's respective merchant account.
e-
Commercefunctionalitywith Client's account
one (1) PaymentGatewayonly).
Merchant Account credentials to support the
required configurations of the Merchant Account
to be used/ integrated with the Meridian LMS
application's a -commerce functionality.
Limitedto one (1) paymentGatewayonly: TBD
AnyotherPaymentvendorsrequiringintegration
are not covered under this scope of work.
MERIDIAN will conduct and support five ( 5) days
of CustomerAcceptanceTestingfor all tasks
defined in section B herein.
11. Additional Tasks: AdHoc
Provide MERIDIAN with the
applicable Merchant Account
credentials.
CLIENT validation of a successful
transaction of purchase through e-
commerce functionality into the live
Merchant account.
Confirmation that the e- commerce
functionalityhasbeencorrectly
configured and is functioning with
Customer' s account information, and
in the Requirements specified in task
B.2 herein.
Thepurposeof thistaskis to installandsetupthe standardAdHocreportingmodulefor the CLIENT. Setupis limitedto the MeridianLMSout of the box solutionfor AdHocmodulethat includesidentifiedbaseproductviewsanddataobjectrelationships.
12. Additional Tasks: Open Sesame Integration
The purposeof this task is to configure and connectto the CLIENT's Open Sesame account of courseware. Setup is limited to the Meridian LMS out of the box solution.
MERIDIAN Deliverables CLIENT Deliverables
Configuration of the Meridian LMS application. Provide MERIDIAN all requested account information.
Assumptions Acceptance Criteria
MERIDIAN will create all needed configurations Confirmation that the Meridian Open and database updates. Sesamefunctionalityhasbeen correctly configured and is functioning per
the Requirements.
13. Additional Tasks: HRISIUser Data Feed
C. Project Schedule
Thescopeoftheimplementationservicesasdepictedhereinis limitedtoaone (1) phasesoftware deployment, estimated to take sixteen ( 16) weeks.
Scheduleis dependent on CLIENT's ability to:
1. Completeall Discoveryand PlanningactivitiesperthemutuallyagreeduponbaselinedProject Plan, Includingbut not limitedto:
a. Data Template Completion.
2. ProvideConfigurationandIntegrationRequirementsina timelymanner.
3. Providefeedbackonall loadeddata in a timelymanner.
4. Execute Customer Acceptance Testing activities per the agreed upon Project Plan.
A draft Project Plan will be provided within one ( 1) week after the Project Kick -Off date. The detailedProject Plan is subjectto modificationduring the softwareimplementationlifecyclewith the mutual agreement of both the CLIENT and MERIDIAN.
D. Roles and Responsibilities
MERIDIANand CLIENTagreeto staff the Projectat levelsand conditionsas set forth in the mutually agreed upon Project Plan. At a minimum, across all tasks as defined in section B.2 above, the Project will be staffed as follows:
MERIDIAN Resources
Role Responsibilities
Acts as Meridian' s single Deployment Project Management point of contact Stages. experience managing
throughout the project. Discovery. teams, issues,
Develops and manages Execute. project schedules
project plan. Deploy. and financials.
Manages project issues Warranty. Meridian LMS
and mitigates risk on Workstreams configuration skills. behalf of Meridian. Project Mgmt. Process definition
Prepares for and Software skills.
conducts status Setup.
meetings. Meridian
Provides status reports University.
andfinancialtracking.
Project Manager Conducts Requirement
Confirmation Workshops.
Participates in and
coordinates design,
configuration,
development, testingand
deployment activities.
Note: In most cases, the
Meridian Project Manager is
not fully dedicated to one
specific customer
deployment since the
responsibility does not
require a full- time resource.
Conduct Requirement Deployment Meridian LMS
Confirmation workshops Stages. product features &
to gather in -scope Discovery. functionality expert.
product extension Execute. Industry Business
Technical Solutions
requirements for Warranty. Process expert.
Architect complex projects only. Workstreams SQL database skills.
Drives the joint project Software SQL queryskills.
team to a solution to Setup. Process definition
meet all requirements in skills,
the most efficient and Data analysis skills.
constructive manner.
Participates in execution Data conversion
of software development skills.
and testingactivities.
Facilitates end -user and Deployment Meridian LMS
system admin Stages. product configuration
RequirementsGathering Discovery. skills.
Sessions. Execute. In-depth Industry and
Confirms configuration Deploy. process knowledge.
requirements. Warranty. SQL query skills.
Identifiesgapsand Workstreams. Process definition
Implementation works with integrated Software skills.
Consultant team to develop Setup. Data analysis skills. resolutions.
Performs data
conversion and migration
activities.
Configures and tests
software per defined
requirements.
Establishes technical Deployment Meridian LMS
environments. Stages. development expert.
Extends software for Discovery. SQL database skills.
requirements not Execute. SQL query skills.
Application supported by out -of -the- Deploy. NET development Developer box features & Warranty. skills.
configurations. Workstreams. Meridian LMS
Configures/ Develops Software technical
integrations with the Setup. infrastructure skills.
product per defined
requirements.
Analyzes and assesses Workstreams. In-depthIndustry
client' s maturity level and Post knowledge,
skill sets. Deployment. In- depth knowledge
Assesses client' s of industrybestAccount Manager businessprocessesand practices. goals. Strategicplanning.
Creates Project/ Account
recommendations to Management.
drive the maturityand
the business forward.
Establishes and tracks Process definition
strategic initiatives. and development
skills.
Enablement and
communications
expert.
Delivers Implementation Deployment Meridian LMS
Readiness and LMS Stages. product features &
Administratortraining. Discovery, functionalityexpert.
Tailorstrainingdelivery Execute. In-depth knowledge
Meridian Trainer to meet customer' s WOrkstreams of industry best business requirements Meridian practices.
and/ or configuration University.
decisions.
Finalizestraining
logistics.
E. Cost Estimate
Item Description
Standard Software Setup
Cost
28, 875, 00
Training 6,000. 00
Historical Data Migration 14, 190. 00
Single Sign - On 4, 960. 00
eCommerce Integration 6, 270. 00
HRIS/ User Data Feed 10, 066. 00
AdHocSetup 4, 290. 00
Open Sesame Integration 1 320. 0
Total Software Set up Fees 1 $75,960.00
ASSUMPTIONS:
1. AllServicesareanestimatebasedontheunderstandingofthe scopeofwork. Implementation Servicesmayvary basedon increaseddomains, useraudience, and scope, or timechanges.
Any additionalServicesthat are identifiedthrough the workbookprocess (additional modifications, integrations, professionalservicessupportor consulting) canbe addedto this Agreement as needed or in a later CO SOW.
2. All pricingfor additionalscopesof workis validfor ninety (90) calendardaysfrom the dateof submission to the CLIENT.
3. TravelcostsarenotincludedintheCostEstimateandwillbeinvoicedperMERIDIAN'Scurrent travel guidelines.
F. Out of Scope
The following is currently deemed outside of the scope for this implementation:
Migrations, integrations, modificationsto thesystemthatare notexplicitlyincludedin the scopeof this SOW.
Customreports, localization, documentation, or onlinehelp.
Contentcleansing, migration, or uploadingunlessspecificallyidentified.
Consultingor professionalservices not specifiedin the implementationtasks (i.e. courseware development, courseware troubleshooting, SCORM, HW/SW configurations or internal network setup or maintenance).
AdvancedGraphicaldesignor otheradvanced (e.g. flash) GUIsupport.
Editabletrainingmaterialssuchas instructorandstudentguides.
G. Change Management
MERIDIANrecognizesthat changesare a normalpart of the projectlife cycle. Changesto the scope or timeline of the Services contemplated by this Agreement will require a formal Change OrderStatementofWork ("Schedule2") to be submittedbythe MERIDIANProjectManagertothe CLIENT. Changesin scope may Includean increasein cost and/or timelineandwill be specified in each change request. Prior to beginningthe change request, CLIENTmust execute the Schedule2ChangeOrder. MERIDIANrequiresformalchangeacceptancebeforebeginningwork onanychanges. ChangeswithinthedefinedscopeofthecontractneedapprovalbytheCLIENT ProjectManagerandtheMERIDIANProjectManager. Acceptanceforscopechanges, aregiven whenboththeCLIENTProjectManagerandthe MERIDIANProjectManagerformallyapprove the change by signing off on Schedule2 so that miscommunicationsare avoided. Project change procedure is as follows:
I. Identifychange (can originatefrom the CLIENT Project Manageror the MERIDIANProject Manager);
ii. MERIDIAN completes Change Request Form;
III. MERIDIANProjectManagerdeterminesthe impactof the proposedchange (schedule, resources, time, and/ or cost);
iv. MERIDIANProjectManagersubmitsSchedule2 to the CLIENTProjectManagerfor review/ approval.
V. MERIDIANProjectManagerreceivesapprovalfrom the CLIENTProjectManagerwithin three ( 3) business days; and
vi. MERIDIANProjectManagermodifiesor, if necessary, re -baselinesthe ProjectSchedule and Plan to include the approved change.
vii. Work begins as agreed upon to incorporate change; or, viii. MERIDIANProjectManagerworkswith the CLIENTProjectManagerto either adjustthe requirements or revise the workload distribution, documentingall changes on a revised Change Request Form.
Change Management Criteria are as follows:
I. Any change that is outside the scope of effort defined in Schedule 1; ii. Anyadditionaldeliverableor servicenotdefinedin Schedule1, or changesto anaccepted deliverable;
iii. Any subsequent modifications to an approved Change Request; iv. Modifications to the technical or managementapproachdefined in Schedule 1; V. Anychangein workloadorenvironmentor applicationinventory; vi. Anyadditionalactivityortasknotdefinedin Schedule1for a planneddeliverable; vii. A contradiction to items, assumptions or responsibilities stated in Schedule 1; viii. A delayin turnaroundof approvals, information, answerstoquestions; and ix. Time lost due to reasonssuchas unavailabilityof equipment, software, or accessto environment/infrastructureneededbythe projectteam.
H. Acceptance Management
In an effort to avoid schedule delays stemming from delayed approvals of dependenttasks, MERIDIANandCLIENTwillmutuallydefinea reasonableacceptancereviewperiodthatdoesnot jeopardizetheprojectdurationasoutlinedwithintheprojectmanagementsupportperiod. Delays inacceptingprojectdeliverablescouldresultinascheduleslippageequalingasmuchasoneday foreverydayacceptancereviewisdelayed. Belowarethemethodsusedtoverifyandvalidateeach of the defined deliverable( s).
I. Deliverable Review and Approval. MERIDIANwill providedeliverablesto the CLIENT.
Documentationdeliverableswill be provided to CLIENT in electronicform. A Deliverable Acceptance Form will be submittedto the CLIENT Project Managerfor each deliverable.
CLIENT will provide MERIDIAN with one set of consolidated comments. MERIDIAN will provideaCLIENTQualityControl (QC) sheetthat mayhelptheCLIENTcollateall comments prior to deliveringto MERIDIAN. The deliverablewill be deemedacceptablewhen it satisfies the acceptance criteria specified for each deliverable or service or within ten (10) calendar daysif noresponseis received. TheDeliverableAcceptancewillbesignedandreturnedto MERIDIANuponreviewofthedeliverablewithinthemutuallydefinedperiodasstatedupon under acceptance management. In the event that the CLIENT rejects a deliverable, MERIDIANwill resubmitthe deliverableto the CLIENTwith the requiredchangeswithina mutually agreed upon timeline.
ii. Acceptance Authority. CLIENTwill specifya single point of contactwith deliverable acceptance/sign off authority. Sign off acceptanceis requiredfor deliverableby the approvingauthority, priorto movingany customizationsto the productionsite. iii. Withholding Acceptance. CLIENT shall not unreasonablywithholdacceptance. If Acceptanceis not grantedor rejectedwithinthe mutuallyagreedupon timeframe, automatic Acceptancewill be granted. In the eventthat failureto provideAcceptanceextendsthe timeframeoftheimplementationactivitieswithintherespectiveSchedule1, CLIENTmaybe liable for additional Project Management time in order to extend the schedule. iv. 30 DayPost -Delivery Warranty. Aftersign -off approvalhasbeenreceived, andMERIDIAN hasdeliveredthefiles, CLIENTwillhavethirty (30) calendardaysinwhichto reportany production errors to the Project Manager. MERIDIAN will assess the error and correct as longastheerroriswithinthescopeoftheoriginaltaskcompleted. Afterthirty (30) calendar daysfromthedatethefilesweredeliveredto theCLIENT, MERIDIANwillprovidea cost estimatefor anyerrors/revisionsrequestedunlessthosecostsarecoveredunderseparate sectionsofthisAgreement. Thiswarrantyis onlyintermsof theworkperformedunderthe Exhibit A.
I. Invoicing Schedule
MERIDIAN will invoice Services based on the following deliverable milestoneswithin the implementation timeline.
i. Contract Execution [ 30%] — Upon Contract Execution, thirty percent (30%) ofthe SOW fee will be invoiced.
ii. Delivery to CLIENT Stage Environment [ 40%] — At the point of all programmatic deliverablesbeing releasedto the CLIENTStageEnvironmentfor CLIENTreview, the second forty percent (40%) of the SOW fee will be invoiced.
III. Delivery to Production [ 30%] — At the pointof all programmaticdeliverablesbeing deliveredforapplicationtothe ProductionEnvironment, thirtypercent (30%) ofthe SOWfee will be invoiced.
J. Additional Services — Labor Rates
Labor Category
Application Architect I
2021 Commercial Rate
194. 12
Application Architect II 222. 33
Application Architect III 250. 54
Application Developer 1 143. 67
Application Developer II 193. 58
Labor Category
Application Developer III
2021 Commercial$
225. 37
Computer Programmer 89. 60
Computer Systems Analyst I 81. 91
Computer Systems Analyst 11 119. 55
ComputerSystemsAnalystIF, 176. 74
Functional IT Consultant 1 156. 57
Functional IT Consultant II 184. 67
Functional IT Consultant III 186. 85
Functionalrr ConsultamIV $ 237. 21I
Functional ITConsultantV 5333. 36 Information
Technology Director 226. 59 Information
Technology Director ll 254. 31 Information
TechnologyDirector III 305. 17 Principal
IT ReengineeringAnalyst 207. 82 Principal
Systems Engineer/Architect 189. 09 Program
Manager 291. 69 Project
Manager 165. 17 Project
Manager ll 185. 19 Project
Manager 111 222. 21 Project
Manager IV 245. 86 QA/
QC Specialist1 92. 48 QA/
QC SpecialistII 246. 19 QA/
qC SpecialistIII 190. 02 Sen'
or"' Re- engineeringAnalyst 140. 42 Software
Testing Engineering138. 48 Software
Trainer 130. 80 Sr.
TechnicalDocumentationSpecialist 156. 59 Sr.
QualityAnalyst 229. 28 Web
Designer1 89. 79 Web
Designer11 109. 75 Web
Designer111 129. 71 K.
AuthorizationBy
signingbelow, CLIENTis authorizingMERIDIANto moveforwardwith thedevelopmentand testingof therequestedfunctionality, as detailedwithin this document. CLIENT agrees that the requirements, as documentedherein, meet or exceedthe expectationof therequestedfunctionality. Once signed, this pageshouldbe faxedor emailedto MeridianKnowledgeSolutions, LLC: To the attentionof: ContractsFax #:
703. 322. 9568 Email
legal aAtrustvin.com
MERIDIAN: CLIENT:
MERIDIAN KNOWLEDGE SOLUTIONS, 1-LC, CtgofSarftArra
a Virginia, limited liability cc pany
a
BY: „
t 1 • l—fi2 60J[ZZPrintedName: ri3 ' ne, KIat F, PrintedName: S Title-G•r / 1ea+wgar aTitle: C- H LFF I4fl M IN t'>T2r4TI0t5 Date: t Date: FPI C&<
ATTEST:
alsy, Gomez
Clerk Council
APPROVED AS TO FORM:
Sonia R. Carvalho
City Attorney
Laura k. Rossini
ChiefAssistantCityAttorney
RECOMMENDED FOR APPROVAL:
ZZ-= - J90on Motsick
Executive Director
HumanResourcesAgency
SCHEDULE2
Software as a Service Subscription Term and Fees
Subscription Term and Fees
a. Software: Meridian LMS
b. Modules/ Components. The following additionalmodules and componentsare included/enabled:
i. Dominknow
iL Ad Hoc Report Builder
III. OptionalContentAdd -on, OpenSesamePlus100: $47,055peryearona3-yearterm discounted by 2% if paid all three (3) years in advance). c. Languages. The following language packs are included/enabled:
i. English ( US) [ included]
d. Initial Subscription Term
The initial term of this subscriptionwill be 3 years commencingfrom the Effective Date of this Agreement.
e. Renewal Period Terms
Uponexpirationof the InitialSubscriptionTerm, this Agreementwill be renewablein subsequent one-yeartermsbasedon thethencurrentpricingfor the Applications. Modules/Components, and Languages listed above.
f. Number of Authorized Users. Maximum of 1500 internal active users AuthorizedUsers" is definedas thetotal numberof useraccountsthathave accesstothe system during the annual subscription term.
g. Additional User Subscription Fees
Additional "AuthorizedUsers" canbeaddedat anytime duringthe InitialTermor RenewalPeriod TermsbasedonthethencurrentSubscriptionpricingfor additionalusers h. Bandwidth and Storage
Thefollowingbandwidthandstoragelimitationsareincludedas partof thisAgreement. Any additionalbandwidthorstoragerequiredbyCLIENTwillbesubjecttocurrentpublishedpricelist.
Bandwidth: 100GB/month (1.2TS/annually— measuredannually) Additionalcontentstorageis pricedat $500annuallyfor 100GB.
Bandwidthwill be measuredbasedupontotal in/out traffic. Bandwidthwill be monitoredon a monthly basis in relation to the commitment levels, however bandwidth will be measuredbasedupontotalusageovertheannualterm. Overagefeesmayapplygoconsumingmore bandwidth.
Subscription Fees
The following subscriptionfees apply to this Agreement: If annual subscriptionfees for multiple years of theInitialSubscriptionTermare paid in advanceand theCLIENTcancelsin accordance with the GeneralTermsand Conditions §11(b) after thefirst year of the InitialSubscriptionTerm but prior to the start of the nextannualterm, the remainingsubscriptionfee for the Initial Subscription Term will be refunded to the CLIENT.
Subscription Fees
Period of performance Fees Invoice date
5/ 18/2022 — 6/ 30/ 2022 3, 576. 89 On execution
7/ 1/2022 — 6/ 30/ 2023 30, 362. 00 On execution
7/ 1/2023 — 6/ 3012024 30, 362. 00 On execution
711/2024 — 6/ 30/ 2025 30, 362. 00 On execution
Total subscription fees for 3 years and 43 days: $94,662.89 Setup Fee
Thefollowingset up feesapply to this Agreement, and are definedin ScheduleOne (1) of this agreement: $ 75, 960
Signatures are on the next page]
MERIDIAN: CLIENT:
MERIDIAN KNOWLEDGE SOLUTIONS, City of Santa Ana
LLC, a Vir inia, limited liability company / -
By: S s
C` PrintedName: Kr; gj;nt (,d eBy: / Title:GA, AdLA04e Printed Name: r ftI° F4C 1 M'•-) YCf6 3t2CDate: 0
Title: Cl—) IEH I JM IN I5Tx( 4-rtQ 5
Date: Or-+rjCkF4 ATTEST:
Daisy Gomez
Clerk of Council
APPROVED AS TO FORM:
Sonia R. Carvalho
City Attorney
By:rf0AAna
Laura A. Rossini
Chief Assistant City Attorney
RECOMMENDED FOR APPROVAL:
J soon Motsick
ExecutiveDirector
Human ResourcesAgency
CHANGE ORDER TO SCHEDULE 1
STATEMENT OF WORK # CO- 001 ( TEMPLATE)
IMPLEMENTATION OF THE MERIDIAN LMS
FOR City of Santa Ana
Thisis a ChangeOrderto Schedule1 — Statementof Work # SOW-001, datedMay 17, 2022 , and defineschangesto theworkto beprovidedunderthetermsandconditionsofthe ContractAgreement signed between MERIDIAN and CLIENT.
A. Effective Date of this Change Order
This ChangeOrderis effectiveuponits executionby MERIDIANand CLIENT. The estimated ChangeOrdercommencementdateis May17, 2022,
B. Summary of Changes to the Scope of Implementation Professional Services CLIENThasrequestedthefollowingchangesto the LMSimplementationin support ofAdditional content add - on.
C, Authorization
By signing below, CLIENTis authorizingMERIDIANto move forwardwith the developmentand testing of the requestedfunctionality, as detailed within this document. CLIENT agrees that the requirements, as documented herein, meet or exceed the expectation of the requested functionality.
Oncesigned, this pageshouldbefaxedor emailedto MeridianKnowledgeSolutions, LLC:
To the attention of: Contracts
Fax #: 703- 322- 9568
Email conlractsCcDmeridianks corn
SIGNATURE PAGE
MERIDIAN:
MERIDIAN KNOWLEDGE SOLUTIONS, LLC,
a Virginia, limited liability company
By:
Printed Name:
Title:
Date:
CLIENT:
City of Santa Ana
PrintedName: Krigknc , e
Title: C;41 ^lletyteofDate: _ (
ATTEST:
Daisy Gomez
Clerk of Council
APPROVED AS TO FORM:
Sonia R. Carvalho
City Attorney
By.
Laura A. Rossini
Chief Assistant City Attorney
FOR APPROVAL:
Z- Z - Ja n o sicc
ecutive Director
Human ResourcesAgency
Ejhjubmmz!tjhofe! EBUF!)NN0EE0ZZZZ*
DFSUJGJDBUF!PG!MJBCJMJUZ!JOTVSBODF cz!Bohjf! Bohjf! UIJT!DFSUJGJDBUF!JT!JTTVFE!BT!B!NBUUFS!PG!JOGPSNBUJPO!POMZ!BOE!DPOGFST!OP!SJHIUT!VQPO!UIF!DFSUJGJDBUF!IPMEFS/!UIJT DFSUJGJDBUF!EPFT!OPU!BGGJSNBUJWFMZ!PS!OFHBUJWFMZ!BNFOE-!FYUFOE!PS!BMUFS!UIF!DPWFSBHF!BGGPSEFE!CZ!UIF!QPMJDJFTBdfwfep! CFMPX/!!UIJT!DFSUJGJDBUF!PG!JOTVSBODF!EPFT!OPU!DPOTUJUVUF!B!DPOUSBDU!CFUXFFO!UIF!JTTVJOH!JOTVSFS)T*-!BVUIPSJ\[FE SFQSFTFOUBUJWF!PS!QSPEVDFS-!BOE!UIF!DFSUJGJDBUF!IPMEFS/ Ebuf;!3133/17/33! BdfwfepJNQPSUBOU;!!Jg!uif!dfsujgjdbuf!ipmefs!jt!bo!BEEJUJPOBM!JOTVSFE-!uif!qpmjdz)jft*! nvtu!ibwf!BEEJUJPOBM!JOTVSFE!qspwjtjpot!ps!cf!foepstfe/ Jg!TVCSPHBUJPO!JT!XBJWFE-!tvckfdu!up!uif!ufsnt!boe!dpoejujpot!pg!uif! qpmjdz-!dfsubjo!qpmjdjft!nbz!sfrvjsf!bo!foepstfnfou/!!B!tubufnfou!po28;26;54!.18(11( uijt! dfsujgjdbuf!epft!opu!dpogfs!sjhiut!up!uif! dfsujgjdbuf!ipmefs!jo!mjfv!pg!tvdi!foepstfnfou)t*/ DPOUBDUQSPEVDFS OBNF;
GBYQIPOF B0D-! Op*; B0D-!Op-!Fyu*;
F.NBJM
BEESFTT;
JOTVSFS) T*! BGGPSEJOH! DPWFSBHFOBJD!$
JOTVSFS! B!;
JOTVSFEJOTVSFE JOTVSFS! C!;
JOTVSFS! D!;
JOTVSFS! E!;
JOTVSFS! F!;
JOTVSFS! G!;
DPWFSBHFTDFSUJGJDBUF! OVNCFS; SFWJTJPO!OVNCFS;
UIJT!JT!UP!DFSUJGZ!UIBU!UIF!QPMJDJFT!PG!JOTVSBODF!MJTUFE!CFMPX!IBWF!CFFO!JTTVFE!UP!UIF!JOTVSFE!OBNFE!BCPWF!GPS!UIF!QPMJDZ!QFSJPE JOEJDBUFE/!!OPUXJUITUBOEJOH!BOZ!SFRVJSFNFOU-!UFSN!PS!DPOEJUJPO!PG!BOZ!DPOUSBDU!PS!PUIFS!EPDVNFOU!XJUI!SFTQFDU!UP!XIJDI! UIJT DFSUJGJDBUF!NBZ!CF!JTTVFE!PS!NBZ!QFSUBJO-!UIF!JOTVSBODF!BGGPSEFE!CZ!UIF!QPMJDJFT!EFTDSJCFE!IFSFJO!JT!TVCKFDU!UP!BMM! UIF!UFSNT- FYDMVTJPOT!BOE!DPOEJUJPOT!PG!TVDI!QPMJDJFT/!MJNJUT!TIPXO!NBZ!IBWF!CFFO!SFEVDFE!CZ!QBJE!DMBJNT/ BEEMTVCS QPMJDZ!FGGQPMJDZ!FYQJOTS UZQF! PG! JOTVSBODFMJNJUTQPMJDZ!OVNCFSMUS) NN0EE0ZZZZ*)NN0EE0ZZZZ* JOTEXWE DPNNFSDJBM!HFOFSBM!MJBCJMJUZDPNNFSDJBM!HFOFSBM!MJBCJMJUZ FBDI! PDDVSSFODF% EBNBHF! UP!SFOUFEDMBJNT. NBEFPDDVS% QSFNJTFT!)Fb!pddvssfodf* NFE! FYQ!) Boz! pof! qfstpo*%
QFSTPOBM!'!BEW!JOKVSZ%
HFO(M!BHHSFHBUF!MJNJU!BQQMJFT!QFS; HFOFSBM! BHHSFHBUF%
QSP. QPMJDZMPDQSPEVDUT!.! DPNQ0PQ! BHH% KFDU
PUIFS;
DPNCJOFE!TJOHMF!MJNJUBVUPNPCJMF!MJBCJMJUZ% Fb! bddjefou* BOZ! BVUP CPEJMZ!JOKVSZ!)Qfs!qfstpo*%
PXOFETDIFEVMFE CPEJMZ!JOKVSZ!)Qfs!bddjefou*% BVUPT! POMZBVUPT OPO. PXOFEIJSFEQSPQFSUZ! EBNBHF
Qfs! bddjefou* BVUPT! POMZBVUPT! POMZ
VNCSFMMB!MJBC FBDI! PDDVSSFODF% PDDVS
FYDFTT!MJBC DMBJNT. NBEFBHHSFHBUF%
EFESFUFOUJPO%
QFSPUI. XPSLFST!DPNQFOTBUJPOXPSLFST!DPNQFOTBUJPO TUBUVUFFSBOE!FNQMPZFST(!MJBCJMJUZBOE!FNQMPZFST(!MJBCJMJUZ Z! 0!OBBOOZZQQ!!SSPPQQSSJJFFUUPPSS00QQBBSSUUOOFFSS00FFYYFFDDVVUUJJWWFF F/M/! FBDI! BDDJEFOU% O! 0!BPGGJDFS0NFNCFS!FYDMVEFE@PGGJDFS0NFNCFS!FYDMVEFE@ Nboebupsz! jo! OI* F/M/!EJTFBTF!.!FB!FNQMPZFF%
Jg!zft-!eftdsjcf!voefsJg!zft-!eftdsjcf!voefsJg!zft-!eftdsjcf!voefs F/M/!EJTFBTF!.!QPMJDZ!MJNJU% EFTDSJQUJPO!PG!PQFSBUJPOT!cfmpxEFTDSJQUJPO!PG!PQFSBUJPOT!cfmpx EFTDSJQUJPO!PG!PQFSBUJPOT!0!MPDBUJPOT!0!WFIJDMFT!!)BDPSE!212-!Beej ujpobm!Sfnbslt! Tdifevmf-!nbz!cf! buubdife!jg! npsf! tqbdf!jt! sfrvjsfe* DFSUJGJDBUF!
IPMEFSDBODFMMBUJPOTIPVME!BOZ!PG!UIF! BCPWF! EFTDSJCFE!QPMJDJFT!CF! DBODFMMFE! CFGPSFUIF! FYQJSBUJPO!EBUF! UIFSFPG-!OPUJDF!XJMM!CF! EFMJWFSFE! JO BDDPSEBODF!XJUI!UIF! QPMJDZ!
QSPWJTJPOT/ BVUIPSJ\[FE!
SFQSFTFOUBUJWF2:99.3126!BDPSE!DPSQPSBUJPO/!!Bmm!sjhiut!sftfswfe/ BDPSE!36!)3127014* Uif! BDPSE!obnf!boe!mphp!bsf!sfhjtufsfe!nbslt!pg!BDPSE