Operating Structure & Protocols Sample Clauses

Operating Structure & Protocols. It is further agreed that command will be structured in accordance with the Incident Command System (ICS) of the National Incident Management System (NIMS), and that if the emergency/disaster is multi-jurisdictional, a Unified Command will be employed when practical. a. It is further agreed that when any personnel or equipment is deployed under the terms of this agreement, the authorized representative of the aiding municipality shall report to the requesting municipality’s authorized representative. Orders by the requesting municipality will be given to the aiding municipality who will then give orders or direction to their personnel and then remain in communication with the requesting municipality. The aiding municipality may be under the direct control of an officer of the requesting municipality only by mutual agreement. b. In all cases and at all times, the person in charge shall have the right and responsibility to ensure that all personnel are asked to perform only those tasks or operations that are consistent with their training and are in accordance with their home protocols and accepted safe practices. c. Visiting personnel shall remain under the control of “command” until the requesting municipality releases said personnel and equipment or until said personnel are recalled by the aiding municipality. Such personnel and equipment shall be released as soon as reasonably possible and returned to the aiding municipality. d. Lastly, it is agreed that each assisting emergency response organization will operate in accordance with its home district protocols and each emergency response person will operate according to the protocols of his/her own organization, and within the scope of his/her own training and certification, or under the supervision of a person with appropriate training and certification. In no event shall the aiding municipality be required to perform in a way inconsistent with their home protocols or inconsistent with accepted safe practices.
Sample 1
AutoNDA by SimpleDocs

Related to Operating Structure & Protocols

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Project Changes 1.8.1. All changes shall be administered per the UGC. 1.8.2. Upon authorization by the Owner, the Owner or Architect/Engineer will prepare and issue all changes to the Contract affecting cost, scope and/or time as a formal Change Order to the Contract on the standard University of Texas MD Xxxxxxxx Cancer Center Change Order form. The Change Order may include separate change issues, identified as Change Proposals and field orders. 1.8.3. Upon authorization by the Owner, Change Proposals may be issued to the Architect/Engineer for pricing by the Contractor. Contractor shall submit pricing to the Owner within twenty-one (21) days and pricing shall be indicated on the standard Owner "Change in Work Cost Analysis" ("Cost Analysis") form provided in the Pre-Construction Conference Brochure. Contractor may not include a Change Proposal within a Change Order unless the Owner has accepted the Change Proposal. 1.8.3.1. The Contractor shall summarize all costs for each change at each level of subcontractor and supplier by preparing the "Cost Analysis" form, and shall provide each subcontractor's cost summary on separate "Cost Analysis" forms as backup. Additional support documentation from both the Contractor and Contractor’s subcontractors is encouraged, but such will not replace use of the standard form. 1.8.3.2. When the Contractor believes it is entitled to a time extension, Contractor shall so state as part of Contractor’s response to the Change Proposal, including a justifica- tion for a time extension. Owner may grant time extensions only if a Change Proposal affects the activities on the Longest Path of an Owner approved Work Progress Schedule; i.e., when the Work impacts the "Contract Substantial Completion Date". 1.8.3.3. If the Owner’s Project Manager and Contractor cannot mutually agree upon a fair and reasonable cost and time settlement, the Owner’s Project Manager may: 1) Reject the quotation and void the Change Proposal, 2) Issue instructions to the Contractor to proceed on a time and material basis for a price to be determined later not to exceed a fixed maximum dollar and time, or 3) Issue a Unilateral Change Order. 1.8.3.4. The Owner’s Construction Inspector and/or Owner’s Project Manager may issue field orders directly to the Contractor for minor changes to the Contract, which can be negotiated in the field. Pricing backup is at the discretion of the Owner’s Construction Inspector, but pricing backup is required for any field order, the pricing backup is to be outlined on the "Cost Analysis" form. When the Owner and Contractor have signed the field order, the Work is authorized and the field order may be included in the next Change Order. 1.8.4. Request for payment for Change Order work may be submitted only after the Change Order has been fully executed.

  • Infrastructure Infrastructure serves as the foundation and building blocks of an integrated IT solution. It is the hardware which supports Application Services (C.3.2) and IT Management Services (C.3.3); the software and services which enable that hardware to function; and the hardware, software, and services which allow for secure communication and interoperability between all business and application service components. Infrastructure services facilitate the development and maintenance of critical IT infrastructures required to support Federal government business operations. This section includes the technical framework components that make up integrated IT solutions. One or any combination of these components may be used to deliver IT solutions intended to perform a wide array of functions which allow agencies to deliver services to their customers (or users), whether internal or external, in an efficient and effective manner. Infrastructure includes hardware, software, licensing, technical support, and warranty services from third party sources, as well as technological refreshment and enhancements for that hardware and software. This section is aligned with the FEA/DoDEA Technical Reference Model (TRM) which describes these components using a vocabulary that is common throughout the entire Federal government. A detailed review of the TRM is provided in Section J, Attachment 5. Infrastructure includes complete life cycle support for all hardware, software, and services represented above, including planning, analysis, research and development, design, development, integration and testing, implementation, operations and maintenance, information assurance, and final disposition of these components. The services also include administration and help desk functions necessary to support the IT infrastructure (e.g., desktop support, network administration). Infrastructure components of an integrated IT solution can be categorized as follows:

  • Developer Attachment Facilities Developer shall design, procure, construct, install, own and/or control the Developer Attachment Facilities described in Appendix A hereto, at its sole expense.

  • Project Implementation The Borrower shall:

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Quality control system (i) The Contractor shall establish a quality control mechanism to ensure compliance with the provisions of this Agreement (the “Quality Assurance Plan” or “QAP”). (ii) The Contractor shall, within 30 (thirty) days of the Appointed Date, submit to the Authority’s Engineer its Quality Assurance Plan which shall include the following: (a) organisation, duties and responsibilities, procedures, inspections and documentation; (b) quality control mechanism including sampling and testing of Materials, test frequencies, standards, acceptance criteria, testing facilities, reporting, recording and interpretation of test results, approvals, check list for site activities, and proforma for testing and calibration in accordance with the Specifications for Road and Bridge Works issued by MORTH, relevant IRC specifications and Good Industry Practice; and (c) internal quality audit system. The Authority’s Engineer shall convey its approval to the Contractor within a period of 21 (twenty-one) days of receipt of the QAP stating the modifications, if any, required, and the Contractor shall incorporate those in the QAP to the extent required for conforming with the provisions of this Clause 11.2. (iii) The Contractor shall procure all documents, apparatus and instruments, fuel, consumables, water, electricity, labour, Materials, samples, and qualified personnel as are necessary for examining and testing the Project Assets and workmanship in accordance with the Quality Assurance Plan. (iv) The cost of testing of Construction, Materials and workmanship under this Article 11 shall be borne by the Contractor.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!