Mode Transitions Sample Clauses

Mode Transitions. The Mode Manager controls the AOCS operation as specified by its modes and transitions between them. Each mode transition is described as a set of specific actions which should be performed in order for the mode to get changed. Transitions between modes are either autonomous (i.e., decided by the Mode Manager) or commanded by the FDIR Manager after an unrecoverable failure. In case of autonomous transitions, each transition criteria associated to a certain mode is cyclically checked in the active mode. If the condition for mode transition is satisfied, then the mode transition is autonomously performed by the supervision of the Mode Manager. The following sections specify the nominal mode transitions, i.e., autonomous mode transition without any interference of the FDIR Manager.
AutoNDA by SimpleDocs

Related to Mode Transitions

  • Transitional (a) The parties recognise that certain determinations (for example, the annualised amount of HCF and HCV) may have been made to date in respect of a current Financial Year before the variations in this deed were agreed.

  • MASTER CONTRACT TRANSITION Contractor represents and warrants that, in the event this Master Contract or a similar contract, is transitioned to another contractor (e.g., Master Contract expiration or termination), Contractor shall use commercially reasonable efforts to assist Enterprise Services for a period of sixty (60) days to effectuate a smooth transition to another contractor to minimize disruption of service and/or costs to the State of Washington.

  • Transition Seller will not take any action that is designed or intended to have the effect of discouraging any lessor, licensor, customer, supplier, or other business associate of the Company from maintaining the same business relationships with the Company after the Closing as it maintained with the Company prior to the Closing. The Seller will refer all customer inquiries relating to the business of the Company to the Purchaser from and after the Closing.

  • Contract Transition Upon Contract expiration or termination, the Contractor shall ensure a seamless transfer of Contract responsibilities with any subsequent Contractor necessary to transition the Products and services of the Contract. The incumbent Contractor assumes all expenses related to the contract transition.

  • Collocation Transfer of Responsibility Without Working Circuits The Collocation is not serving any End User Customers and does not have active service terminations (e.g., Interconnection trunks or UNE Loops) or 2) Collocation Transfer of Responsibility With Working Circuits – The Collocation has active service terminations, such as Interconnection trunks or is serving End User Customers.

  • OGS Centralized Contract: Terms and Conditions The terms and conditions set forth in this section are expressly incorporated in and applicable to the Contract. Captions are intended as descriptive and are not intended to limit or otherwise restrict the terms and conditions set forth herein. Appendix A Appendix A, Standard Clauses for New York State Contracts, dated January 2014, attached hereto, is hereby incorporated in, and expressly made a part of, this Contract. Appendix B Appendix B, Office of General Services General Specifications, dated January 2015 22772 Project Based Information Technology Consulting (Statewide), attached hereto, is hereby incorporated in, and expressly made a part of, this Contract.

  • 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.

  • Transition Plan In the event of termination by the LHIN pursuant to this section, the LHIN and the HSP will develop a Transition Plan. The HSP agrees that it will take all actions, and provide all information, required by the LHIN to facilitate the transition of the HSP’s clients.

  • DISASTER RECOVERY AND BUSINESS CONTINUITY The Parties shall comply with the provisions of Schedule 5 (Disaster Recovery and Business Continuity).

  • INTEGRATIONS & MODIFICATIONS This Agreement constitutes the whole agreement between the parties. Except as identified in this Agreement, there are no other prior written agreements and no prior or contemporaneous oral agreements that are a part of this Agreement. No modification to this Agreement shall be valid, unless in writing and executed by both parties.

Time is Money Join Law Insider Premium to draft better contracts faster.