The URL can be used to link to this page

Browse Search

Home My WebLink About20242445.tiffConf vacl-O# 8rco 1 BOARD OF COUNTY COMMISSIONERS PASS -AROUND REVIEW PASS AROUND TITLE: PulsePoint DEPARTMENT: PS Communications DATE: 03/20/23 PERSON REQUESTING: Tina Powell Brief description of the problem/issue: The Greeley Fire Department(GFD) is looking to purchase a product called PulsePoint. This product sends out a "CPR -needed" alert to trained people when it has been identified by dispatch that someone is unconscious and not breathing. This also notifies the trained person of the nearest location of an AED. This will require a partnership with Dispatch as it interfaces with the Central Square CAD. Public Safety IT has been involved in the project. There is no cost to Weld County for the product and causes no extra work for our dispatchers. What options exist for the Board? (include consequences, impacts, costs, etc. of options): Approve involvement in the project for Dispatch Deny involvement in the project for Dispatch Recommendation: It is our recommendation to approve the involvement. This is a great project to get the quick notification out that CPR is needed. It interfaces easily with our Central Square CAD and does not put any extra workload on our dispatchers. Perry L. Buck, Pro-Tem Mike Freeman, Chair Scott K. Jame Kevin D. Ross Lori Seine ConSW-}da QA to/Z4 Aoorove Schedule Work Session -ate 6e2,0x,(6,0,4(&ki-) q//bp'/- Other/Comments: 2024-2445 CM 002q Puise-_. t PulsePoint Foundation PO B.12594 Pleasanton, CA 94588-2594 Contact Name Email Bill To Name Bill To Tina Powell tpowell@weld.gov Weld County Communications Center 1551 N 17th Ave Greeley, CO 80631 United States Quote Number PPF-00010879 Created Date 08/22/2024 Expiration Date 10/31/2024 Prepared By Kraig Erickson Phone (218) 384-1123 Email kraig.erickson@pulsepoint.org Weld County Communications Center Ship To Name 1551 N 17th Ave Ship To Greeley, CO 80631 United States PulsePoint Respond Implementation Project- Includes PulsePoint Read-only CAD connection installation, configuration, testing, validation, AED registry organization, technical admin training, digital materials, and proj mgmnt of launch. PulsePoint Respond - Tier 2: Annual Subscription for covered population size 300K - 750K. Includes PulsePoint Respond License, unlimited use of all Responder Types, AED Registry, Maintenance / Support of CAD Interface, admin and end -users. Order will be processed upon PulsePoint Foundation's acceptance of signed quote, signed Statement of Work, and Customer Purchase Order or payment. Upon acceptance, Customer will be invoiced for Implementation Fee. Customer will not be invoiced for Annual Subscription Fee until Soft Launch, which is when Annual Subscription Term begins. Please return signed Quote, Statement of Work, and Payment to the PulsePoint representative listed above or mail to: PulsePoint Foundation PO Box 12594 Pleasanton, CA 94588-2594 Authorized Customer Representative Signature Tina Powell Name Director of PS Comm 9/6/24 Date Title Total Price USD USD 10,000.00 USD 8,000.00 1.00 1.00 10,000.00 USD 8,000.00 USD 28,000.00 Authorized PulsePoint Foundation Representative /< Signature Kraig Erickson Name VP, Community Engagement 08-22-2024 Title Date BOARD OF COUNTY COMMISSIONERS r j� .r ` V4PE. * . NTY, COLD; • ► t> rry L Buck, Pro—Tem SEP 1 6 2024 g quote, Customer agrees to Terms of Use and Addendum 1 that follow. G'? -12, PULSEPOINT STANDARD SUBSCRIPTION TERMS AND CONDITIONS This Software and Services Agreement (the "Agreement") applies to and governs access to and use of the PulsePoint Respond System and is entered into between the PulsePoint Foundation, a California 501 (c)(3) non-profit corporation, ("The Foundation"), and the contracting entity ("Customer"). 1. PULSEPOINT RESPOND ("System") Licensed Software. The Licensed Software (as hereinafter defined) is a software -as -a -service ("SaaS") pre- arrival solution designed to support public safety agencies working to improve communications with citizens and off -duty personnel to improve cardiac arrest survival rates via mobile applications. The primary purpose of the Licensed Software is to provide: (1) community members the ability to receive notifications of CPR -needed medical events occurring in public places, (2) designated responders the ability to receive notifications of time -sensitive medical events occurring in public and private places, (3) location of publicly accessible defibrillators, and (4) increased awareness of local emergency activity. (the "Licensed Software"). The Foundation owns all rights to the Licensed Software. 2. SYSTEM SERVICES. System Support. The Foundation provides web -based, email, and telephone System Support (collectively, the "System Support") at no additional cost to designated contacts of Customer. System Support consists of help with System navigation or troubleshooting arising from the use of the System, as designed. System Support excludes supporting Customer procured hardware, operating systems, and Internet connectivity. Web -based System Support is provided through web -based, self-help educational resources available within the System 24/7/365. The Foundation provides numerous educational resources which should be used before requesting email or telephone System Support. These include user guide(s), training videos, and frequently asked questions (FAQs). Tiered email and telephone System Support is available to supplement Web -based System Support. The Foundation's Support Center is staffed during prime Customer business hours, Monday — Friday, 7AM — 6PM PT, excluding major holidays. During "non -prime" hours (6PM — 7AM PT Monday — Thursday, and 6PM PT on Friday through 7AM PT the following Monday, and on major holidays), inquiries regarding major system outages and interface issues are supported by technical staff. General support inquiries started outside of prime hours will be addressed the next business day. 3. CUSTOMER REQUIREMENTS. 3.1 CAD Integration. Customer must provide a CAD integration environment as further defined in a separate Statement of Work that includes implementation of the Licensed Software. 3.2 Named User Identification and Authentication. The System requires a unique user name and password for the individual Customer representative ("Named User") to access the System. Customer is responsible for administration and management of the Named User account, including the appropriate technical and administrative safeguards to prevent unauthorized access. The Foundation shall have no responsibility for unauthorized access to Customer's data or Confidential Information (as hereinafter defined) that results from Customer's failure to prevent unauthorized access. 4. LICENSE AND FEES. 4.1 License. Subject to the terms and conditions of this Agreement, The Foundation hereby grants to Customer a non-exclusive, non -transferable (except as provided in this Agreement) license to use the System for lawful business purposes. 4.2 Fees. 4.2.1 Subscription Fees. Customer agrees to pay the Subscription Fees as set forth in applicable Quote. Subscription Fees include: System, Data Center Services, System Maintenance, Upgrades, and System Support. Subscription Fees will be invoiced annually. 4.2.2 Professional Services Fees. Customer agrees to pay Professional Services Fees as set forth in applicable Professional Services Engagements. 4.2.3 Payment Terms. Payment terms to the Foundation shall be NET 30 to ensure uninterrupted System service V.240701 Page 1 and support. 4.2.4 Taxes. The Foundation is required to collect sales tax from products and services provided to customers in certain states. The Foundation reserves the right to invoice the Customer those taxes now or at any time in the future, which are imposed upon the sale or delivery of items purchased or licensed. If a certificate of exemption or similar document or proceeding is to be made in order to exempt the sale from sales or use tax liability, Customer will obtain and purchase such certificate, document or proceeding. Customer is required to provide a certificate of exemption in order for The Foundation to correctly identify Customer's tax status. 5. TERM AND TERMINATION. 5.1 Term Initiation. This Agreement takes effect upon receipt of order and continues through the conclusion of the subscription term or any subsequent renewal subscription terms. The subscription term (the "Term") begins on Customer's Soft Launch (as herein defined) Date or 120 days from signature date on Quote, whichever comes first, and continues for duration of Term set forth in executed Quote. Soft Launch ("Soft Launch") is the first day Customer's incident data is available in the production environment. In the case of renewal, the subsequent of which Term is the first day after expiration of the previous Term. 5.2 Term Renewal. This Agreement shall automatically renew upon expiration of the then current Term, at the current System price list for the same Term, unless Customer notifies The Foundation of its intention for nonrenewal by written notification at least 45 days prior to the end of the then current Term, or unless The Foundation requires a new Agreement to be executed by the parties. If The Foundation requires a new Agreement, it will be provided to Customer at least 60 days prior to the end of the then current Term. Customer may decline to enter into a new Agreement in its sole and absolute discretion; and if Customer so declines, then Customer shall not be responsible for any Subscription Fees after the then current Term. 5.3 Termination. Either party may terminate the Agreement upon the other party's material breach of this Agreement, if within 30 days of receipt of written notification of breach; the breaching party has failed to cure its breach. The Foundation may terminate service immediately upon Termination of the Agreement. In the event of early Termination due to material breach by Customer, Customer shall be responsible for remaining Subscription Fees for the then current Term. In the event of early Termination due to material breach by The Foundation, Customer shall not be responsible for future Subscription Fees beyond the effective date of the termination of this Agreement. Notwithstanding anything in this Section 5 or in this Agreement to the contrary, Customer may terminate this Agreement and Customer obligations hereunder during the initial Term or any subsequent renewal Term, without cause, for any reason, or for no reason, and in Customer's sole and absolute discretion. Upon Termination, all of Customer's licenses and rights to the System shall terminate, and Customer shall immediately cease use of the System. 6. PROPRIETARY RIGHTS OF THE FOUNDATION IN THE LICENSED SOFTWARE AND DOCUMENTATION. 6.1 Nature of Rights and Title. Customer acknowledges that the System and documentation supplied by The Foundation to Customer are proprietary and shall remain the sole and exclusive property of The Foundation and nothing in this Agreement shall be construed as transferring any aspect of such rights to Customer or any third party. 6.2 Unauthorized Acts. Customer agrees to notify The Foundation promptly of the unauthorized possession, use, or knowledge of any item supplied under this Agreement and of other proprietary information made available to Customer under this Agreement, by any person or organization not authorized by this Agreement to have such possession, use or knowledge. Customer's compliance with this subparagraph 6.2 shall not be construed in any way as a waiver of The Foundation's right, if any, to recover damages or obtain other relief against Customer for its negligent or intentional acts in regard to The Foundation's proprietary rights, or for breach of Customer's contractual obligations under this Agreement. 6.3 Remedies. If Customer attempts to use, copy, license, sub -license or otherwise transfer the Licensed Software or access to the System supplied by The Foundation under this Agreement, in a manner contrary to the terms of this Agreement or in competition with The Foundation or in derogation of The Foundation's proprietary rights, V.240701 Page 2 whether or not these rights are explicitly stated, determined by law, or otherwise, The Foundation shall have the right to obtain injunctive relief enjoining such action, in addition to any other remedies available to the Foundation under this Agreement, applicable law or in equity. Customer acknowledges that monetary damages would be inadequate. 6.4 Infringement Indemnification. The Foundation shall indemnify, defend and hold harmless Customer from and against any and all loss, cost, damage or liability, including reasonable attorneys' fees and expenses, arising out of or relating to any claim or cause of action for patent, copyright, and/or other intellectual property infringement (each, an "Infringement Claim") asserted against Customer by virtue of the System, Software or documentation or Customer's use or possession of the System, Software or documentation pursuant to this Agreement. The Foundation shall defend or settle at its sole expense all suits and proceedings arising out of the foregoing; provided that Customer gives The Foundation prompt notice of any such Infringement Claim of which it learns. In all events, Customer shall have the right to participate at its own expense in the defense of any such suit or proceeding through counsel of its own choosing. In the event that any Infringement Claim is asserted by a third party with respect to the System or Customer's use thereof, then and in that event, Customer may terminate its use of the System and/or this Agreement without payment of any contracted fees for services or periods not provided. 7. CONFIDENTIALITY AND DATA USE. 7.1 Confidential Information. The parties agree that any Confidential Information provided under this Agreement shall be held and maintained in strict confidence. Each party agrees to protect the Confidential Information of the other party in a manner consistent with the protections used to protect its own Confidential Information, including, without limitation, informing its employees of its obligations under this Agreement and taking such steps as are reasonable in the circumstances, or as reasonably requested by the other party, to prevent any unauthorized disclosure, copying or use of Confidential Information. Confidential Information means any proprietary material that the disclosing party designates as confidential (collectively, the "Confidential Information"). Confidential Information shall also include, without limitation, all information in any form which relates to the business, expertise and/or operations of the disclosing party, including without limitation, information in any form generally understood to be trade secret, proprietary or confidential and/or that is related to products and services, commercial and financial information, system functionality charts and descriptions, program code logic, trade secret information, and information about health care providers, customers and/or business partners. Confidential Information shall also include Protected Health Information as defined in HIPAA and its rules and regulations promulgated here under. The Foundation will not use Confidential Information except as expressly provided in this Agreement. Confidential Information does not include information that (i) is already known to the receiving party at the time it is disclosed and has not been obtained wrongfully, (ii) becomes publicly known without the fault of the receiving party, (iii) is independently developed by the receiving party, (iv) is approved for release in writing by the disclosing party, (v) is disclosed without restriction by the disclosing party to a third party, or (vi) is disclosed pursuant to applicable statutory or other legal or accreditation obligation beyond the control of the receiving party. 7.2 Unauthorized Disclosure. The recipient of any Confidential Information shall, upon discovery of any unauthorized use or disclosure of such Confidential Information, or any other breach of these confidentiality obligations by the recipient, fully cooperate with the disclosing party to assist the disclosing party to regain possession of the Confidential Information and prevent the further unauthorized use or disclosure of the Confidential Information. 7.3 Data Use. Customer agrees to provide The Foundation certain Data ("Data"), identified in the Statement of Work and signed by Customer, for the purposes of making the System function as designed. Customer Data is comprised of both Public Data ("Public Data"), and Non -Public Data ("Non -Public Data"). Public Data may be provided to community members to fulfill the primary purpose as described in Section 1 and is limited to public data subject to routine disclosure. Non -Pubic Data may contain additional data elements not considered public data subject to routine disclosure. Non - Public Data is intended primarily for use by Customer employees. Customer is responsible for administration and management of these user accounts, including the appropriate technical and administrative safeguards to prevent unauthorized access. The Foundation shall have no responsibility for unauthorized access to Non -Public Data or Confidential Information that results from Customer's failure to prevent unauthorized access. 7.3.1 Third -Party Data Use. The Foundation may make available certain third -party services whereby The Foundation may share Customer data on Customer's behalf. Customer can choose to opt -in to these services, which may require Customer to complete external agreements with third -party partners, prior to The Foundation V.240701 Page 3 making Customer Data available outside of the System. 7.3.2 Nationwide Third -Party Data Use. Customer understands and agrees that The Foundation may sham Public Data received from Customer with certain third -party services if the third -party receives aggregate Public Data across other customers of The Foundation for uses deemed to be in the interest of public safety and consistent with The Foundation's Data Use Policy. This policy includes review of third -party usage by an oversight panel consisting of PulsePoint customers and leading public safety trade association(s). Any Nationwide Third -Party Data Use will be disclosed to Customer. 7.3.3 Performance and Statistical Data. The Foundation recognizes the importance in identifying issues and improvements surrounding the functionality, integration, performance, and reliability of the System. Customer agrees that The Foundation may collect, maintain, and use technical information related to the System, including, but not limited to, its usage, functionality, integration, performance, and reliability. The Foundation may use this information to improve its products or to provide customized services or technologies. 8. LIMITED WARRANTY. For the duration of this Agreement (the "Warranty Period"), The Foundation will investigate, document and deliver any amendments or alterations to the Licensed Software or other System components that may be required to correct errors which significantly affect performance. THE LIMITED WARRANTY SET FORTH IN THIS AGREEMENT IS THE ONLY WARRANTY MADE BY THE FOUNDATION. THE FOUNDATION EXPRESSLY DISCLAIMS, AND CUSTOMER HEREBY EXPRESSLY WAIVES, ALL OTHER WARRANTIES EXPRESS, IMPLIED OR STATUTORY, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE. THE FOUNDATION DOES NOT WARRANT THAT THE LICENSED SOFTWARE OR SYSTEM WILL MEET CUSTOMER'S REQUIREMENTS OR THAT THE OPERATION OF THE LICENSED SOFTWARE WILL BE UNINTERRUPTED OR ERROR -FREE, OR THAT, EXCEPT AS REQUIRED HEREIN TO ADDRESS ERRORS THAT SIGNIFICANTLY AFFECT PERFORMANCE, ERRORS IN THE LICENSED SOFTWARE OR SYSTEM WILL BE CORRECTED. THE FOUNDATION'S LIMITED WARRANTY IS IN LIEU OF ALL LIABILITIES OR OBLIGATIONS OF THE FOUNDATION FOR ANY CLAIMS AND/OR DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE INSTALLATION, USE OR PERFORMANCE OF THE LICENSED SOFTWARE OR SYSTEM. 9. LIMITATION OF LIABILITY. THE FOUNDATION'S LIABILITY FOR ANY ACTIONS, CLAIMS OR DAMAGES ARISING OUT OF OR RESULTING FROM THIS AGREEMENT OR THE SYSTEM IS LIMITED TO THE AMOUNTS PAID BY CUSTOMER IN THE TWELVE-MONTH PERIOD PRECEDING THE CLAIM. IN NO EVENT SHALL THE FOUNDATION HAVE ANY LIABILITY FOR ANY SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOST PROFITS, LOSS OF DATA OR COSTS OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, ARISING IN ANY WAY OUT OF THIS AGREEMENT UNDER ANY CAUSE OF ACTION. THE FOUNDATION WILL NOT BE LIABLE FOR LOSS, CORRUPTION OR COMPROMISE OF THE CONFIDENTIALITY OF CUSTOMER -PROVIDED DATA. 10. REFERENCE AND SPONSORSHIP. Customer agrees that The Foundation may identify Customer as a customer or user of the System on its website, App Store page and similar sites, and other marketing materials, and describe the project and the services provided by the Foundation to Customer. Nothing herein constitutes an endorsement of The Foundation by Customer. 11. GENERAL. 11.1 Assignment. This Agreement and any related obligation of one party, may not be assigned in whole or in part without the prior written consent of the other party, which shall not be unreasonably withheld. Any attempt by either party to assign any of the rights, duties or obligations of this Agreement without such consent shall be void. After and upon approved assignment, this Agreement shall bind and inure to the benefit of the parties and their respective successors, assignees, transferees, and legal representatives. 11.2 Amendment. This Agreement can only be modified by a written agreement duly signed by persons authorized to sign agreements on behalf of Customer and The Foundation, and variance from the terms and conditions of this Agreement in any order or other written notification from the Customer will be of no effect. V.240701 Page 4 11.3 Severabillty. If any provision or provisions of this Agreement shall be held to be invalid, illegal or unenforceable, the validity, legality and enforceability of the remaining provisions shall not in any way be affected or impaired thereby. 11.4 Entire Agreement. Customer acknowledges that its authorized representative has read this Agreement, understands it, and agrees on behalf of Customer to be bound by its terms and conditions. Further, Customer agrees that this Agreement constitutes the complete and exclusive statement of the agreement between the parties, which supersedes all proposals or prior agreements, oral or written, and all other communications between the parties relating to the subject matter of this Agreement, and other communications made or required pursuant to the terms of this Agreement shall be in writing and shall be (i) personally delivered, sent by nationally recognized courier service, or sent by certified mail, return receipt requested, and shall be deemed to have been received upon the earlier of actual receipt or five (5) business days after deposit with the nationally recognized courier service or deposit in the mail; (ii) sent by facsimile and deemed to have been received on the date of the facsimile confirmation; (iii) sent by electronic means and shall be deemed to have been received upon return of a read receipt. 11.5 Notices. Unless another address for a party has been specified by providing notice as set forth herein, such notices, demands, requests and other communications permitted or allowed under this Agreement must be sent to Customer at the address set forth on the signed Quote and to The Foundation, Attn: Legal, PO Box 12594, Pleasanton, CA 94588-2594. V.240701 Page 5 PulsePoint Software and Services Agreement Addendum 1 Whereas the PulsePoint Foundation and Customer desire to amend the PULSEPOINT SOFTWARE AND SERVICES AGREEMENT (the "Agreement"), this Amendment ("Addendum 1") identifies that the parties agree that the Agreement is amended as follows: Section 5.2 Term Renewal. Replace first sentence as follows: "This Agreement shall automatically renew upon expiration of the then current Term, at the current System price list for the same Term, subject to budget appropriations, unless Customer notifies The Foundation of its intention for nonrenewal by written notification at least 45 days prior to the end of the then current Term, or unless The Foundation requires a new Agreement to be executed by the parties." Section 5.3 Termination. Append last sentence as follows: "...and only responsible for prorated annual Subscription Fees up to the effective date of the termination of this Agreement if full annual Subscription Fee has already been paid." Section 6.2 Unauthorized Acts. Replace last sentence as follows: "Customer's compliance with this subparagraph 6.2 shall not be construed in any way as a waiver of The Foundation's right, if any, subject to the extent permitted under Colorado law, to recover damages or obtain other relief against Customer for its negligent or intentional acts in regard to The Foundation's proprietary rights, or for breach of Customer's contractual obligations under this Agreement." Section 7.3 Data Use. Append last sentence as follows: "...unless prohibited or allowed from disclosure under the Colorado Open Records Act, C.R.S. 24-24-72-201 et seq." Section 9. LIMITATION OF LIABILITY. Append last sentence as follows: "...unless caused by willful, intentional, or negligent acts by Foundation." Section 9.1 Insurance. Add this section as follows: "Foundation is required to have cybersecurity/privacy insurance in the amount of $1,000,000 occurrence and $1,000,000 aggregate in effect during each subscription period. Foundation shall provide proof of such coverage by means of a Certificate of Insurance, and must have Weld County endorsed as an additional insured along with waiver of subrogation rights." Section 11.6. Independent Contractor. Add this section as follows: "Foundation is an independent contractor as described in section 8-40-202(2), C.R.S., and is not entitled to workers' compensation benefits and, further, is obligated to pay federal and state income tax on moneys earned pursuant to this Agreement. " Section 11.7 Governmental Immunity. Add this section as follows: "No term or condition of this contract shall be construed or interpreted as a waiver, express or implied, of any of the immunities, rights, benefits, protections or other provisions, of the Colorado Governmental Immunity Act §§24-10-101 et seq., as applicable now or hereafter amended." This Addendum 1 is effective in concurrence with Agreement after latest authorized signature date on Quote: 240822.KJE PulsePpint A Message from Our President We are very excited to partner with you to help improve cardiac arrest outcomes in your community. Before we begin, I would like to share our unique and proven approach to building your CPR response network. Achieving the goal of PulsePoint Responders routinely beginning CPR and retrieving a nearby AED, prior to the arrival of advanced care, requires a significant number of local app users. Communities with a high density of app users greatly improve the odds of having at least one responder nearby that can quickly walk to the incident and provide care. While we are proud of being thought of as the "CPR app," our importance and utility to the community and your agency goes much deeper. PulsePoint keeps your community informed of emergency activity in real time. Residents use this information on a daily basis to know when there is an accident on their commute, or if the smoke they smell is an approaching wildfire. They'll share the routine usefulness of the app with neighbors, family and friends — and in turn they'll help build and sustain an engaged and reliable network of CPR -trained individuals. This combination is crucial to achieving broad community adoption and sustaining a lifesaving program. In addition to providing a real time filtered incident feed and CPR alerts in public places, PulsePoint is committed to first responders and providing actionable information both on -duty and off. PulsePoint Verified Responder Pro is the professional version of PulsePoint Respond, providing advanced functionality for agency personnel. Professional verified responders are shown all calls in the jurisdiction along with complete address information and routing for all incident types. These employees also receive CPR needed alerts for both public and private activations. Verified Responder is an option and your Project Lead will know if Verified Responder is part of this implementation. Given this mission we encourage you to fully review this Statement of Work to understand how PulsePoint can best serve your agency and community. Sincerely, ?04,w Richard Price, President PURPOSE 9:411 �rt LAC D4 I Vegetation Fire N 50TH ST E & E.AVE'NUE N, PALMS PERU CCItt EI3t WW1 Water Rescue CLARK AVE E E DEL At tO SLVo, LA) -PTt. COPT17 Pact EMT E.?) E30 f• Vehicle Fire S WILMINGTON AVE o W VICTORIA S "E116 011, Wires Down 31930 CASTMMC RD, CAST•. c. •AJ'w E149 Medical Emergency LA ALBAOR, WHIT TIER, CA 154 STE Hazmat investigation Y: 190TH ST S VAN P r3tt 191312 ' Medical Emergency s BEACH ELVD & W IMPERIAL h:. • •E1?4 twat 5191 Expanded Traffic Collis:on NHS SO 13S 14./..Y. CCr.' • 40116O •I4VC Controlled Burn/Prescribed. 9:t.t . ACTivE RECENT HHIFR OP NEEDED! 9 Medical Emergency S:41 AM STH FAIRWAY. HILTON HEAD ISLAND. SC t, •1 Traffic Collision 1.tAUWLtiNC RDa SOL SLAT? _,RP. r:1 CPR NEEDED! ... a.aa, PALMETTO DUNES GOLF COURSE 4TM FAIRWAY. HILTON HEAD ISLAND I'm ' >nding, guide mr tlAftstes..Altt) PD S SOL SLAT: d,7 PA 8t f 1 tnl tdl 1P‘3 Medical Emergency • VIE: 3 c Medical Emergency PADDLE 304: t'J, 2992.°•, SC .•r (15I ..., 444 AM 352 AM . .ttILEE ND LAC -D7 4)) Confirmed Vegetation Fire 575 LOS LUC%ES DR, PACIFIC PALISADES. CA •n CC': "COPTI2?COPIIT _tt)3 Stun o Navigate PulsePoint Respond is a mobile app and cloud -based, 9-1-1 dispatch connected service that alerts CPR -trained citizens and off -duty professional responders to someone nearby having a sudden cardiac arrest. The goal of PulsePoint is to initiate CPR earlier and more often and increase the use of automated external defibrillators (AED) prior to emergency responders arriving on scene. With a survival rate of only about 10%, studies have shown that early CPR and AED use can double or triple chances of survival from cardiac arrest. "Sudden Cardac Arrest is not just a job for emergency responders but rather a community -based issue that rsquires a community -based response. In no other medical situation is there such a vital reliance on the community." — In terna tiona l Association of Fire Chiefs 2 PulsePoint Statement of Work — New Implementation v8.2020 OPERATIONAL OVERVIEW PulsePoint interfaces with the public safety communications center through a technical integration described in Schedule A. When the center dispatches a cardiac arrest incident in a public place, an alert is simultaneously sent to community app subscribers in the immediate proximity of the victim. PulsePoint Verified Responders, as identified by the agency, receive alerts in both public locations and private homes. Professional Verified Responders (agency employees) are shown a complete incident list with additional capabilities. PulsePoint also creates more awareness of publicly available AEDs so that these devices can be located in the critical time of need by responders and dispatchers. The PulsePoint AED Registry provides complete control over Public Access Defibrillation (PAD) programs. Tightly integrated with both the PulsePoint Respond and PulsePoint AED apps, the PulsePoint AED Registry provides a simple workflow to manage critical registry tasks. CRITICAL SUCCESS FACTORS Engagement Achieving the goal of PulsePoint responders routinely beginning CPR and retrieving a nearby AED prior to the arrival of advanced care requires a significant number of local app users. Communities with a high density of app users greatly improve the odds of having at least one responder within the cardiac arrest activation radius. Having deployed PulsePoint in thousands of communities over the last ten years, we have learned that an app experience that provides daily value to the user is the most important factor in achieving meaningful engagement rates. Community marketing is present in all stages of a well -planned PulsePoint deployment. Effective outreach starts at launch — but sustained marketing is essential for broad community adoption. Our marketing team is always available to brainstorm ideas and assist your staff with execution. Real Time Interface Timely "CPR -needed" alerts are crucial to the effectiveness of PulsePoint, every minute that passes without CPR reduces the chances of survival by 10%. Real-time data is at the heart of a lifesaving interface. PulsePoint provides a well -supported set of managed services to address special interface requirements, including: ■ Public/Private location determination ■ Ability to suppress incidents by type or location ■ Normalization of incident types for consistent display in the app ■ Categorization of incident data for community and employee use ■ Dynamic activation radiuses based on population density, response times, or other local conditions PulsePoint Statement of Work— New Implementation v8.2020 AGENCY ROLES AND RESPONSIBILITIES Pre -Implementation One of the most important steps in a successful implementation is assembling a team ready to complete the necessary internal tasks required to bring PulsePoint to the community. All members on the project team should gain familiarity with both PulsePoint apps and the PulsePoint user community before the project officially begins. 1. Download and begin use of the PulsePoint Respond and PulsePoint AED mobile apps. 2. Review the PulsePoint.org website and follow PulsePoint on Twitter to pulsepoint and/or Facebook @pulsepoint Project Lead The Project Lead is the point person who can connect the vision across all departments, be available when necessary, possess strong organizational skills, have experience implementing enterprise software, have the ability to pull in resources as needed, and possess the authority to make workflow changes. Ideally this person is a project champion who closely monitors milestones and key tasks and effectively manages the diverse internal project team. Key responsibilities of the Project Lead include: + Point of contact for PulsePoint Project Manager. + Manage project deliverables such as call types, dispatch status codes, and shapefiles. + Authority and ability to engage subject matter experts as needed. + Ensure all project team members understand project purpose, timelines, responsibilities, and communications plan. + Attend and actively participate in all mutually scheduled weekly or biweekly project status calls. + Once in the sandbox testing environment assign a small test team to verify the PulsePoint interface meets its design specifications and other requirements. + Provide final acknowledgment of project completion and authorize Soft Launch. Implementation Team In addition to the Project Lead, the Project Team typically includes: + Executive Champion - to provide leadership, prioritize resources, and support the purpose of the project. + Technical Lead - responsible for assisting with the dispatch system integration. + AED Registry Lead - familiar with PAD program or other AED initiatives. + Marketing Lead - public information or outreach personnel that will facilitate the community announcement of PulsePoint by the agency including sustained marketing efforts. + Sponsor/aligned organizations - help to bring PulsePoint to the community (if applicable). PulsePoint Statement of Work— New Implementation v8.2020 PULSEPOINT ROLES AND RESPONSIBILITIES An experienced project manager and specialized subject matter experts will be assigned to work with your project team to successfully execute the implementation plan. Project Manager + Primary point of contact for agency Project Lead and coordinator of implementation plan. + Facilitate remote project kickoff call and lead weekly project status meetings. + Assist with PulsePoint system admin setup and training. + Provide a comprehensive test plan to ensure the application is functioning as designed. Technical Interface Lead + Primary engineering point of contact for dispatch system vendor and agency Technical Lead. + Configure environment as detailed in Schedule A. + Configure and test interface components. + Troubleshoot and assist with technical problem resolution. AED Registry Lead + Initial bulk upload of known AED locations, if available. + Provide orientation and training on PulsePoint AED app, registry admin and supporting resources. + Deploy strategies to engage community and internal resources to help build and maintain the AED registry. Community Outreach and Graphic Design Lead + Design a comprehensive marketing campaign for both an internal (employee and stakeholder) and external (public) launch. + Assistance with marketing activities and logistics, including launch day planning, media releases, community outreach campaigns, and long-term adoption strategies. PulsePoint Insights Analytics Lead + Post soft launch — Registration, orientation and training on PulsePoint Insight, the on -demand business intelligence tool designed to provide actionable information on PulsePoint performance in your community. PulsePoint Statement of Work— New Implementation v8.2020 PROJECT IMPLEMENTATION Support and participation from your project team is essential to a successful implementation. As the customer you agree to have all equipment, connections and facilities prepared and ready for implementation in accordance with the mutually agreed upon project schedule. Typical Project Timeline PHASE ONE (2-4 weeks) Kick Off Technical Call Install PHASE TWO t68weeks) AED Orientation & Training ACID ('l'g;stryi PHASE THREE (On -going) On Going Community Engagement Agency Preparation Download the PulsePoint Respond App Have your entire project team download the PulsePoint Respond app by searching "pulsepoint" in the App Store or on Google Play. Ask that they follow a few neighboring agencies or agencies similar to your own. This will allow your internal project team to become familiar with the app and be prepared to configure PulsePoint for your agency. Many aspects of the of the implementation process will be viewed and tested in a pre- production "sandbox" environment directly within the app. Obtain Any Required CAD Vendor Interfaces or Modules Your CAD vendor may require an interface or other components to integrate with PulsePoint. The earlier this is known and in place the better, as the technical implementation typically cannot begin until this requirement is completed. Project Kick-off Call The Project Kick-off Call marks the formal start of your PulsePoint implementation. After introductions the PulsePoint Project Vianager and Technical Interface Lead will layout project milestones and timelines, discuss key roles and respcnsibilities and propose a standing meeting schedule. This is also a forum for initial questions and level -setting. During this call your Project Manager will ask for the following information: 6 PulsePoint Statement of Work — New Implementation v8.2020 ■ Register your Agency o The agency Project Lead should register the agency(s) at https://admin.pulsepoint.org/signup.php Note: This process will create agency -level login credentials - this is not a personal login. Incident Types and Descriptions o Your PulsePoint implementation requires a complete listing of all fire and medical incident type codes utilized by your agency. These incident types, or nature codes, are normalized to PulsePoint standard incident types and categorized for use in the community version and professional Verified Responder (employee) version of the app. The incident type codes along with associated descriptions should be provided in a spreadsheet format (not as a .pdf). In addition, if you are not using a standardized EMD protocol (such as ProQA) also identify a definitive list of unconscious/unresponsive medical code types that would indicate the likely need for CPR. Note: Incidents of a confidential or sensitive nature will be limited to employees (i.e., Verified Responders) and suppressed in the community version of the app. Personal information such as patient name, SSN, birth date, etc. are never transmitted or known to PulsePoint. No law enforcement incidents of any type are allowed in the app. Your Project Manager will fully review this with you during agency validation and testing. ■ Dispatch Status Codes and Descriptions o Your PulsePoint implementation requires a complete listing of unit dispatch status codes. These status codes are normalized to PulsePoint dispatch statuses for use in the app. Please provide the codes along with associated descriptions in a spreadsheet format. ■ Shapefile(s) o Your PulsePoint implementation requires a GIS shapefile that defines the jurisdictional boundaries. Your GIS staff or planning department will likely be familiar with this common data format. If your implementation will include distinct agencies, gather the shapefiles for the service area of each entity. Note: If your service areas mirror standard municipal boundaries, PulsePoint maybe able to obtain your shapefile(s) for you. PulsePoint Statement of Work— New Implementation v8.2020 Interface Configuration The interface configuration process varies depending on the interface method as defined in Schedule A. Typical tasks include installation and configuration, normalizing agency incident types to standard PulsePoint incident types, and data validation and testing in our sandbox (test) environment. Full QA will be conducted by our engineering team to insure proper configuration. Agency Validation and Testing After installation and configuration is complete, but before the interface is moved from the sandbox/test environment, the Agency Validation and Testing phase begins. During this phase a limited but representative group of agency users begin active use and testing of the app. This group is provided secure web and app access to view agency data as it will appear in the future public release. Anomalies and exceptions reported by this team are closely tracked with updates provided during the project status meetings. AED Registry AED registry tasks include identification of existing AED location sources such as school districts and local government entities, bulk upload of know devices in your community, admin orientation and training, workflow roles and responsibilities, and introduction to community outreach strategies and resources. If your CAD vendor or EMD solution provider support the PulsePoint AED API, dispatch center staff can inform callers of nearby AEDs. These integrations are identified and configured during this phase. Note: The AED registry phase is not dependent on other milestones and may be completed any time prior to soft launch. Soft Launch Once validation and testing has been successfully completed and approved, PulsePoint will move the interface from the protected sandbox environment to the public production (live) environment. This step is typically done two to three weeks prior to a community/public launch and allows for an internal announcement to agency personnel and stakeholders. This also allows for final validation and testing prior to the public launch. Public Launch PulsePoint will help plan and coordinate your public launch activities. The public launch is generally conducted by trusted voices in your community and often involves public safety, civic leadership and local media. Project Closure Project closure occurs the first business day after completion of the implementation process, unless otherwise specified. The Project Manager will review the status of all implementation tasks and verify satisfactory completion of the project. PulsePoint Statement of Work — New Implementation v8.2020 Ongoing Maintenance and Support Once the project is closed, PulsePoint provides ongoing technical and operational support per the terms of the PulsePoint Subscription Agreement. This includes CAD system updates and version changes that impact the interface; however, implementation of a new CAD system (vendor change) will require a new interface and project. Please make sure to involve PulsePoint early in a CAD conversion process to allow enough time to quote and plan a professional services project and ensure service continuity. Support can be obtained at support@pulsepoint.org. PulsePoint Statement of Work— New Implementation v8.2020 PulsePoint Statement of Work — New Implementation SCHEDULE A - PULSEPOINT CONNECT: DIRECT READ Technical Phase for PulsePoint Connect: CAD Direct Read This interface estzblishes a SQL Server Linked Server connection to the live CAD database or near real-time data warehouse. This method typically does not require a separate interface or direct involvement from the CAD vendor. CAD System • • • • • . PulsePoint Connect . HTTPS (TLS vi .2 or greaser) Outbound Only . . . . . • . OS Messaging tor Alerts . • Android Messaging for Alerts . . . . . . . . ► PulsePoint 1 api.pulsepoint.org • • • • • PulsePoint Insights analytics . . • PulsePoint OS App PulsePoint Android App • . . . . . . 16 ... • . . . • • • . . . . . . . . . . . . • . • . . . . . . . . • • • . . . • • Data Security All PulsePoint API communication is over HTTPS with a minimum supported security protocol of TLS v1.2 to ensure data privacy end -to -end over the internet. Unsecured HTTP and legacy SSL protocols are not supported. API account authertication is performed via a combination of HTTP Basic Auth and a globally unique agency assigned API key. Authentication and key validation are done over a secure encrypted handshake. PulsePoint API servers are firewalled and port limited to HTTPs/SSL (port 443) for API communication and SSH (port 22) for secure encrypted terminal access by vetted engineers. 10 PulsePoint Statement of Work — New Implementation Only monitored SSH private/public keypairs are used for terminal access to PulsePoint servers. No password based terminal access is allowed. Data is stored on Amazon RDS database instances within an AWS account VPC (Virtual Private Cloud). Data 'at rest' is encrypted with the industry standard AES-256 encryption algorithm via a secured keypair. Access to data backups stored on Amazon RDS servers are secured with AWS Identity Access Management (IAM) policies and restricted to a limited number of vetted individuals. PULSEPOINT CONNECT TECHNICAL SPECIFICATIONS Real -Time CAD Data Access PulsePoint Connect requires real-time, read-only access to CAD data. PulsePoint Connect can be configured to use either a true real-time CAD data warehouse or the live CAD system via a linked server connection. Real- time in this case means that PulsePoint Connect can reliably access CAD data within 30 seconds from when an event occurred (e.g., Call Received Date/Time). PulsePoint Connect Server Requirements PulsePoint Connect runs on a server that your agency will furnish and maintain. The interface sends outbound only (https) messages to PulsePoint. This server should be dedicated to running PulsePoint Connect, if possible. The server requirements are: Windows® Server 2016 or Windows® Server 2019 4GBofRAM 40 GB disk space ■ PulsePoint Connect does not store data, so the disk space requirement remains fixed Dual -core CPU at a minimum Server can be a VMWare session Server needs access to real-time CAD data (read-only) Administrator rights on the provided server to install and configure the PulsePoint Connect application and service Fully patched (Windows Update process run) PulsePoint Connect server Access to the Internet to communicate with PulsePoint over https port 443 PulsePoint Connect Installation PulsePoint Connect services are installed remotely once the customer -provided server environment is ready. This is accomplished via either VPN access to the PulsePoint Connect server or by designating a technical staff member(s) to assist in establishing GoToAssist (http://www.gotoassist.com/) sessions. 11 PulsePoint Statement of Work — New Implementation During the PulsePoint Connect installation process, the agency's CAD Database Administrator will need to provide the server name or server IP address, and the CAD database/data-warehouse user ID and password. With these three items a SQL Server linked server connection can be established with the CAD database/data-warehouse. PulsePoint Connect Data Flow Diagram PulsePoint Connect utilizes a series of lightweight stored procedures that are optimized to minimize impact on customer systems. These stored procedures provide a dynamic interface that provides timely and targeted data for use in the system. QueryOPI ncidentUpload Stored Procedure . . . . QueryOPUnitUpload Stored Procedure • • • • QueryClosedlncidentUpload Stored Procedure . . • • PPC Application finds new transaction data . • • • FindOPPulsePoint Stored Procedure • • • • PPC Application checks for new transaction data • • • . • • . . . . . . . . . . . • • . • • . . • . • . . . . . . . • • • ; II. ♦ . • • • • • • • • • . . • • • . • 12 CAD Data Source • • • • Linked Server (Read-only) • • • • • • . . • • • PulsePoint Connect (PPC) Application + DB SQL Server Express • . • PulsePant SaaS (AWS-hosted) outbound only via HITPs/SSL (port 443) PuisePoint Statement of Work - New Implementation AGENCY PROJECT LEAD Please provide the name and contact information for your Agency Project Lead. Name X711 S 6(Y1 t'GC 1'7 / S S (' k} Title Proc // aryl i V au/t7 Email �f c r!i CJ . �f U Phone ( 9 7Q LT/ W - a S-1 40 AGENCY AGREEMENT The signature below approves this Statement of Work and authorizes the Agency Project Lead to proceed with this project as delineated in this document. Name r f.ma I Title ()1 G -f' Ck O' CeJ^tki7/IUP/ / KC. -75 ax Agency (JC t c .6-214A311,1 Email ti l,(Tr 17 () r ( (161i, j Date _44,,atvo ATTEST: BOARD OF COUNTY COMMISSIONERS Weld my Clerk to the = oard WELD COUNTY, COLORADO eputy CI Buck, Pro-Tem SEP 1 6 2024 Do you use a �*� �- dal _, patch system? [X] ProQA Paramou [ ] PowerPhone Total Response [ ] APCO Intellicomm [ ] Other .920.2 ACORO® CERTIFICATE OF LIABILITY INSURANCE DATE (MM/OD/YYYY) 08/22/2024 THIS CERTIFICATE IS ISSUED AS A MATTER OF INFORMATION ONLY AND CONFERS NO RIGHTS UPON THE CERTIFICATE HOLDER. THIS CERTIFICATE DOES NOT AFFIRMATIVELY OR NEGATIVELY AMEND, EXTEND OR ALTER THE COVERAGE AFFORDED BY THE POLICIES BELOW. THIS CERTIFICATE OF INSURANCE DOES NOT CONSTITUTE A CONTRACT BETWEEN THE ISSUING INSURER(S), AUTHORIZED REPRESENTATIVE OR PRODUCER, AND THE CERTIFICATE HOLDER. IMPORTANT: If the certificate holder is an ADDITIONAL INSURED, the policy(ies) must have ADDITIONAL INSURED provisions or be endorsed. If SUBROGATION IS WAIVED, subject to the terms and conditions of the policy, certain policies may require an endorsement. A statement on this certificate does not confer rights to the certificate holder in lieu of such endorsement(s). PRODUCER CF&P Insurance Brokers 101 Ygnacio Valley Road Ste. 200 Walnut Creek, CA 94596 CONTACT Jenne Fullmer PHONE I FAX (a/C. No. EXn: 925-956-7717 WC, No): ADDRESS: Jenne@cfpinsurance.com INSURER(S) AFFORDING COVERAGE NAIL # INSURER A : Underwriters at Lloyd's,London 15792 INSURED PulsePoint Foundation P.O. Box 12594 Pleasanton, CA 94588 INSURER B : INSURER C : INSURER D : INSURER E : INSURER F : VERAGES CERTIFICATE NUMBER: REVISION NUMBER: THIS IS TO CERTIFY THAT THE POLICIES OF INSURANCE LISTED BELOW HAVE BEEN ISSUED TO THE INSURED NAMED ABOVE FOR THE POLICY PERIOD INDICATED. NOTWITHSTANDING ANY REQUIREMENT, TERM OR CONDITION OF ANY CONTRACT OR OTHER DOCUMENT WITH RESPECT TO WHICH THIS CERTIFICATE MAY BE ISSUED OR MAY PERTAIN, THE INSURANCE AFFORDED BY THE POLICIES DESCRIBED HEREIN IS SUBJECT TO ALL THE TERMS, EXCLUSIONS AND CONDITIONS OF SUCH POLICIES. LIMITS SHOWN MAY HAVE BEEN REDUCED BY PAID CLAIMS. LTR TYPE OF INSURANCE TN ADDL SUER INSR WVD POLICY NUMBER POLICY EFF (MM/DD/X) POLICY EXP (P71NC0 Y I LIMITS A 1 L COMMERCIAL GENERAL 'mown, CLAIMS -MADE OCCUR y y ESN1040016833 07/13/2024 07/13/2025 Esc, occURRENCE $ 5,000,000 =75,77 $ 250,000 MED EXP (Any one person) $ 10,000 PERSONAL & ADV INJURY $ GENERAL AGGREGATE $ 5,000,000 GEN'LAGGREGATE LIMITAPPLIESPER: 1 .POLICY PRO LOC _......: JECT OTHER: PRODUCTS - COMP/OP AGG $ 5,000,000 AUTOMOBILE MANY AUTO OWNED SCHEDULED _. AUTOS ONLY AUTOS HIRED NON -OWNED I..,.AUTOS ONLY/ AUTOS ONLY ESN 1040016833 07/13/2024 07/13/2025 COMBINEDSINGLELIMIT (Ea accident) $ 5,000,000 BODILY INJURY (Per person) $ BODILY INJURY (Per accident) $ PROPERTY DAMAGE (Per accident) $ Deductible $ 1,000 UMBRELLA LIAR OCCUR EXCESS LIAR CLAIMS -MADE EACH OCCURRENCE $ AGGREGATE $ ,: RETENTION $ PER OTH- STATUTE ER WORKERS COMPENSATION AND EMPLOYERS' LIABILITY ‘12 / N ANYPROPRIETOR/PARTNER/EXECUTIVE OFFICER/MEMBEREXCLUDED? (Mandatory in NH) If yes, describe under DESCRIPTION OF OPERATIONS below N/A` E.L. EACH ACCIDENT $ E.L. DISEASE - EA EMPLOYEE $ E.L. DISEASE - POLICY LIMIT $ A A Cyber/Errors & Omissions Cyber Crime ESN1040016833 ESN1040018833 07/13/2024 07/13/2024 07/13/2025 07/13/2025 Limit/Aggregte Deductible Lin-Ht/Aggregate $5,000,000 $5,000 $250,000 DESCRIPTION OF OPERATIONS / LOCATIONS / VEHICLES (ACORD 101, Additional Remarks Schedule, may be attached if more space is required) Board of County Commissioners of Weld County and its Officers/Employees are included as additional insured as respects work performed by the named insured. Waiver of subrogation applies. TE HOLDER CANCELLATION SHOULD ANY OF THE ABOVE DESCRIBED POLICIES BE CANCELLED BEFORE Weld County THE EXPIRATION DATE THEREOF, NOTICE WILL BE DELIVERED IN 1150 O ST ACCORDANCE WITH THE POLICY PROVISIONS. Greeley, CO 80631 AUTHORIZED REPRESENTATIVE I ACORD 25 (2016/03) © 1988-2015 ACORD CORPORATION. All rights reserved. The ACORD name and logo are registered marks of ACORD tr ct Entity Information Entity Name* Entity ID* PULSE POINT FOUNDATION @00048993 Contract Name * PULSEPOINT AED NOTIFICATION Contract Status CTB REVIEW Contract Description * COUNTYWIDE AED NOTIFICATION PROGRAM Contract Description 2 Contract Type* AGREEMENT Amount* $28,000.00 Renewable* YES Automatic Renewal YES Grant IGA Department COMMUNICATIONS Department Email CM- Communications@weldgo v.com Department Head Email CM-Communications- DeptHead@weldgov.com County Attorney GENERAL COUNTY ATTORNEY EMAIL County Attorney Email CM- COUNTYATTORNEY@WEL EY@WEL D.GOV If this is a renewal enter previous Contract ID If this is part of a MSA enter MSA Contract ID Contract ID 8669 Contract Lead * TPOWELL Contract Lead Email tpowell@weld.gov New Entity? Parent Contract ID Requires Board Approval NO Department Project # Requested BOCC Agenda Due Date Date* 09/12/2024 09/16/2024 Will a work session with BOCC be required?* NO Does Contract require Purchasing Dept. to be included? NO Note: the Previous Contract Number and Master Services Agreement Number should be left blank if those contracts are not in OnBase Contract Dates Effective Date 09/16/2024 Review Date* 08/01/2025 Renewal Date* 09/16/2024 Termination Notice Period Committed Delivery Date Expiration Date Contact Information Contact Info Contact Name Contact Type Contact Email Contact Phone 1 Contact Phone 2 Purchasing Purchasing Approver Purchasing Approved Date CONSENT 09/06/2024 Approval Process Department Head TINA POWELL DH Approved Date 09/06/2024 Final Approval BOCC Approved BOCC Signed Date BOCC Agenda Date 09/16/2024 Finance Approver CONSENT Legal Counsel CONSENT Finance Approved Date Legal Counsel Approved Date 09/06/2024 09/06/2024 Tyler Ref* AG 091624 Originator TPOWELL Hello