Data Arrival Delays Sample Clauses

Data Arrival Delays. ‌ The problem of continuous task allocation and execution becomes even more complex if a continuous task depends on other tasks in terms of a data. That is, one task needs data from other task(s) to run, where each task sends its results as a stream to the other task(s) [2]. If at least one task is interrupted due to the end of its allocated time 2Note that these strategies can be applicable to both data independent and dependent tasks. slot or a resource failure, then the other tasks which directly or indirectly depend on this task will be affected. A direct dependence means that the other task either directly depends on an interrupted task’s data or directly sends its data to this task, not via other tasks as in the case of an indirect dependence. What happens if a task does not receive necessary data in time, given that it has to be run continuously? What happens if the receiving task has been interrupted and the data from its sending tasks is not processed any more? Here, we focus on data arrival delays for inter-dependent tasks, because such delays may lead to an interruption of the data receiving tasks due to a large error in their esti- mations, causing an additional reason for task interruption, which is especially relevant for continuous tasks. If continuous tasks are inter-dependent, then an interruption of one task may lead to an interruption of other tasks, which is different from the case when tasks are considered to be data independent. Any interruption in those condi- tions causes a much larger utility loss for a client, and therefore a client might need an additional mechanism to obtain resources apart from a new resource negotiation with the GRA. The consideration of delays in data arriving at one task from another task are in- troduced in the literature in different domains e.g., a data transfer delay through a network (e.g. wireless sensor networks [20]), a data delay due to a multi-agent coor- dination decision computation (e.g. web monitoring [21]), etc. A delay can also be a result of the interruption of a sending task, and this type of delay has received less attention in the literature, as the majority of continuous-task processing systems claim to be fault-tolerant, for example, migrating a task from a failed computing resource to another resource [22]. However, at the time when a task has to be re-allocated, there might be no available computing resources. Another approach can be task replication (i.e. running task replicas on the...
Sample 1
AutoNDA by SimpleDocs

Related to Data Arrival Delays

  • Conversion of Live Telephone Exchange Service to Analog 2W Loops The following coordination procedures shall apply to “live” cutovers of VERIZON Customers who are converting their Telephone Exchange Services to SPRINT Telephone Exchange Services provisioned over Analog 2W unbundled Local Loops (“Analog 2W Loops”) to be provided by VERIZON to SPRINT.

  • Excusable Delays Except with respect to defaults of subproviders, the Engineer shall not be in default by reason of any failure in performance of this contract in accordance with its terms (including any failure to progress in the performance of the work) if such failure arises out of causes beyond the control and without the default or negligence of the Engineer. Such causes may include, but are not restricted to, acts of God or the public enemy, acts of the Government in either its sovereign or contractual capacity, fires, floods, epidemics, quarantine restrictions, strikes, freight embargoes, and unusually severe weather.

  • Operation Delays STATE shall have the authority to delay or suspend the operations of PURCHASER and contractors of PURCHASER, wholly or in part, under this contract for such period or periods necessary due to fire hazard conditions, severe weather occurrence, surveying for threatened or endangered species listed under the state or federal Endangered Species Act, or any other activity STATE determines to be necessary for identification, management, or protection of a threatened or endangered species. PURCHASER agrees to cooperate with surveying efforts of STATE or its contractors. In no event shall STATE be liable for any costs incurred by PURCHASER by reason of delay or suspension under this section, including but not limited to costs of additional move-in/move-out of equipment and personnel, extra fire and equipment security, and insurance or bonding expenses.

  • Mechanical Breakdowns 15.1 Any mechanical problems associated with the Vehicle must be reported to Apollo as soon as possible in order to give Apollo the opportunity to rectify the problem during the rental period. Equipment failure must also be reported to Apollo.

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate Xxxxx’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • SPECIAL DELIVERY INSTRUCTIONS All shipments will be FOB destination (as specified on Ordering Entity Purchase Order).

  • Excusable Delay The Contractor is entitled to an equitable adjustment of time, issued via Change Order, for delays caused by the following:

  • Transmission Delivery Service Implications Network Resource Interconnection Service allows Interconnection Customer's Large Generating Facility to be designated by any Network Customer under the Tariff on Transmission Provider's Transmission System as a Network Resource, up to the Large Generating Facility's full output, on the same basis as existing Network Resources interconnected to Transmission Provider's Transmission System, and to be studied as a Network Resource on the assumption that such a designation will occur. Although Network Resource Interconnection Service does not convey a reservation of transmission service, any Network Customer under the Tariff can utilize its network service under the Tariff to obtain delivery of energy from the interconnected Interconnection Customer's Large Generating Facility in the same manner as it accesses Network Resources. A Large Generating Facility receiving Network Resource Interconnection Service may also be used to provide Ancillary Services after technical studies and/or periodic analyses are performed with respect to the Large Generating Facility's ability to provide any applicable Ancillary Services, provided that such studies and analyses have been or would be required in connection with the provision of such Ancillary Services by any existing Network Resource. However, if an Interconnection Customer's Large Generating Facility has not been designated as a Network Resource by any load, it cannot be required to provide Ancillary Services except to the extent such requirements extend to all generating facilities that are similarly situated. The provision of Network Integration Transmission Service or firm Point-to-Point Transmission Service may require additional studies and the construction of additional upgrades. Because such studies and upgrades would be associated with a request for delivery service under the Tariff, cost responsibility for the studies and upgrades would be in accordance with FERC's policy for pricing transmission delivery services. Network Resource Interconnection Service does not necessarily provide Interconnection Customer with the capability to physically deliver the output of its Large Generating Facility to any particular load on Transmission Provider's Transmission System without incurring congestion costs. In the event of transmission constraints on Transmission Provider's Transmission System, Interconnection Customer's Large Generating Facility shall be subject to the applicable congestion management procedures in Transmission Provider's Transmission System in the same manner as Network Resources. There is no requirement either at the time of study or interconnection, or at any point in the future, that Interconnection Customer's Large Generating Facility be designated as a Network Resource by a Network Service Customer under the Tariff or that Interconnection Customer identify a specific buyer (or sink). To the extent a Network Customer does designate the Large Generating Facility as a Network Resource, it must do so pursuant to Transmission Provider's Tariff. Once an Interconnection Customer satisfies the requirements for obtaining Network Resource Interconnection Service, any future transmission service request for delivery from the Large Generating Facility within Transmission Provider's Transmission System of any amount of capacity and/or energy, up to the amount initially studied, will not require that any additional studies be performed or that any further upgrades associated with such Large Generating Facility be undertaken, regardless of whether or not such Large Generating Facility is ever designated by a Network Customer as a Network Resource and regardless of changes in ownership of the Large Generating Facility. However, the reduction or elimination of congestion or redispatch costs may require additional studies and the construction of additional upgrades. To the extent Interconnection Customer enters into an arrangement for long term transmission service for deliveries from the Large Generating Facility outside Transmission Provider's Transmission System, such request may require additional studies and upgrades in order for Transmission Provider to grant such request.

  • Transmission and Routing of Telephone Exchange Service Traffic PURSUANT TO SECTION 251(c)(2) ............................... 14 4.1

  • Recovery of Schedule Delays During Last Sixty Days of Contract Time At any time during the last sixty days of the Contract Time that the Design Professional finds that the Contractor is behind schedule per the Contract Time, as amended, the Design Professional shall notify the Contractor in writing. Within seven days of the date of the Design Professional's notice, the Contractor shall prepare and deliver to the Design Professional and Owner a written plan explaining how the Contractor intends to bring the Project back on schedule. The Contractor's plan must provide sufficient detail to allow the Design Professional and Owner to determine the proposal's feasibility.

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