DCDRS AND KMT MODIFICATION/VESION UPDATE/REVISED HARDWARE PROCESS Sample Clauses

DCDRS AND KMT MODIFICATION/VESION UPDATE/REVISED HARDWARE PROCESS. To design, develop, produce and test modifications/version updates/revised hardware for the DCDRS and KMT as a result of T23 SSB CB9500(5) to (9) (REF 6 to 10) and/or BR2170(1) chapter 21 Annex 21I (REF 3) updates and/or hardware/software obsolescence. The modifications/version updates, may comprise of hardware and/or validated, verified, functionally and non functionally tested and version controlled software updates and shall adhere to current UK & EC Maritime Health & Safety legislation and appropriate referenced documentation. In accordance with the Authority agreed Configuration Management Process, to carry out the update all relevant software, hardware, safety, and test documentation to reflect the DCDRS and/or KMT modification/version updates. Also the update of all drawings affected by the changes (As tasked). The configuration upkeep of this information is paramount to maintaining a current recorded representation of each boat DCDRS and KMT installation. Modifications/version updates that can be undertaken by Ship Staff are to include Modification/version update embodiment instructions as part of the deliverable. These instructions will also detail a step-by-step in-situ test and setting to work data, to confirm correct operation of new or revised facilities. When applicable, to carry out EMC testing and obtain EMC certification of revised DCDRS Hardware in accordance with the requirements of XXX XXXX 59-411 parts 1 to 5 (REF 26). The installation, test, trial and setting to work of the DCDRS and/or KMT modification/version updates, by the Attendance on Ship as stipulated in paragraph 2.4.11 In the event of an obsolescent generated DCDRS change to assess the range and scale of the new DCDRS articles to maintain ARM requirements and recommend to the Authority on-board, base spares and buffer stock provisioning.
Sample 1
AutoNDA by SimpleDocs

Related to DCDRS AND KMT MODIFICATION/VESION UPDATE/REVISED HARDWARE PROCESS

  • OGS Centralized Contract Modifications OGS, an Authorized User, or the Contractor may suggest modifications to the Centralized Contract or its Appendices. Except as specifically provided herein, modifications to the terms and conditions set forth herein may only be made with mutual written agreement of the Parties. Modifications may take the form of an update or an amendment. “

  • INTEGRATION/MODIFICATION This Agreement constitutes the entire understanding and agreement between the Company and the Executive regarding its subject matter and supersedes all prior negotiations and agreements, whether oral or written, between them with respect to its subject matter. This Agreement may not be modified except by a written agreement signed by the Executive and a duly authorized officer of the Company.

  • CENTRALIZED CONTRACT MODIFICATIONS A. OGS, an Authorized User, or the Contractor may suggest modifications to the Centralized Contract or its Appendices. Except as specifically provided herein, modifications to the terms and conditions set forth herein may only be made with mutual written agreement of the Parties. Modifications may take the form of an update or an amendment. “

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

  • Flexible Work Schedule A flexible work schedule is any schedule that is not a regular, alternate, 9/80, or 4/10 work schedule and where the employee is not scheduled to work more than 40 hours in the "workweek" as defined in Subsections F. and H., below.

  • Alternative Work Schedule An alternate forty (40) hour work schedule (other than five (5) uniform and consecutive eight (8) hour days in a seven (7) day period), or for hospital personnel an eighty (80) hour workweek in a fourteen (14) day period and other mutually agreed upon schedules that comply with applicable federal and state law. Employee work schedules normally include two (2) consecutive days off.

  • Authorized User’s Statement of Work A competitive Mini-Bid is required for every transaction under this Centralized Contract. An Authorized User must prepare a detailed Statement of Work using Appendix F, Attachment 1, Mini-Bid Template. The Authorized User must distribute the Mini-Bid to all qualified Vendors per Lot(s) (unless a Vendor has removed itself from consideration via the Appendix F, Attachment 5, Mini-Bid Participation Interest Template). Contact information, organized by Lot, will be available on the OGS website for this Contract. An Authorized User shall conduct its Mini-Bid in accordance with the requirements set forth in Appendix F, Attachment 2, How to Use this Contract. The following terms and conditions shall apply to each Mini-Bid issued by an Authorized User:  An Authorized User may require the execution of unique forms, such as Confidentiality Non- Disclosure agreements; and  An Authorized User is required to make tentative award and non-award notifications to each Contractor who submitted a response to the Mini-Bid. Additionally, the minimum time, excluding the date of release, between issuance of the Mini-Bid by the Authorized User to the Mini-Bid Opening is as follows:  Xxx 0 Xxxx-Xxxx: Xxxx (0) Xxxxxxxx Xxxx  Xxx 0 Mini-Bids: Ten (10) Business Days

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • CONTRACTOR’S SUBMISSION OF CONTRACT MODIFICATIONS In connection with any Contract modification, OGS reserves the right to:  request additional information  reject Contract modifications  remove Products from Contract modification requests  request additional discounts for new or existing Products

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