My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CC PACKET 10252022
StAnthony
>
City Council
>
City Council Packets
>
2022
>
CC PACKET 10252022
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/20/2022 3:15:48 PM
Creation date
10/20/2022 3:14:34 PM
Metadata
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
126
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
<br />12 <br />CR225-476-758705.v8 <br />(c) Pay the Vendor charges for the actual use of the Fencing. Such payments are to be <br />made directly to the Vendor unless directed otherwise by the Board; <br /> <br />(d) Providing food, water, first aid, and similar support to the Deployment Team as <br />may reasonably be needed; <br /> <br />(e) Contacting the Board or the Board’s designee if there are any issues with the <br />Fencing once it is in place; and <br /> <br />(f) Complying with Board policies and procedures applicable to a Requesting Member, <br />including avoiding any activities that may unreasonably damage the Fencing or <br />expose the Deployment Team to an unreasonable risk. <br /> <br />5.3. Discretionary Deployment. A Member may make a request to the Board for the <br />deployment of the Fencing in the Member’s Governmental Unit for an event or <br />occurrence other than a Critical Incident. The deployment of the Fencing for something <br />other than a Critical Incident is left to the sole discretion of the Board. The Board shall <br />consider all such requests at a meeting and determine whether to approve the Member’s <br />request. The Board shall adopt criteria or standards for determining when to allow the <br />discretionary deployment of the Fencing and the requesting Member’s obligations if the <br />request is approved. The Board may delegate the authority to one or more Directors to <br />determine whether to allow the discretionary deployment of the Fencing based on the <br />criteria established by the Board. <br /> <br />5.4. Non-Member Deployment. The Board shall adopt standards and requirements for <br />determining whether to allow the deployment of the Fencing in response to a Critical <br />Incident that occurred in a non-member Governmental Unit. Nothing in this Agreement <br />obligates the Fencing Consortium to deploy the Fencing to a non-member Governmental <br />Unit. <br /> <br />5.5. No Guarantee. The Members understand and agree the deployment of the Fencing by <br />the Deployment Team is a cooperative undertaking and that the Fencing Consortium <br />cannot guarantee a certain response time or make any representations or warranties <br />regarding response times, the Fencing, its assembly, or effectiveness. The Deployment <br />Team will endeavor to respond as quickly as possible to a Critical Incident and to place <br />the Fencing as shown in the Requesting Member’s Fencing Preplan as provided in this <br />Agreement and in accordance with Board policies and procedures. <br /> <br />5.6. Demobilization. The Member who receives the Fencing in response to a Critical <br />Incident shall work with the Fencing Consortium to determine when to initiate the <br />demobilization of the Fencing from the Deployment Site. For a discretionary deployment <br />of the fence, the demobilization date shall be determined prior to the deployment. The <br />Deployment Team shall be responsible for disassembling the Fencing as part of the <br />demobilization. The Board shall establish such procedures and policies as may be needed <br />to address the demobilization of the Fencing. The Board has the authority to recall the <br />Fencing from a Member if it determines there is a more critical need for the Fencing in <br />87
The URL can be used to link to this page
Your browser does not support the video tag.