Invocation Dispatching Sample Clauses

Invocation Dispatching. The following subsection describes how the dispatching between a local and a remote call, with respect to a VDM-RT model as discussed above, is handled when code is generated. The basic idea of call dispatching is illustrated in Figure 6. The CALL FUNC(...) macro is wrapped in another macro which handles the dispatching: if it is a local call then the normal function macro is invoked, otherwise the remote dispatcher is invoked, as described further below. In general, dispatching depends on the object deployment topology inside the system definition, as discussed above. Hence this deployment information must be used when supporting the distributed aspects of VDM-RT. Each CPU implementation receives its own local version of the system definition, generated as a class. This local definition contains both objects deployed to that CPU and a map of which distributed objects are local and which are remote relative to that CPU. Local Remote sendBus(…) CALL_FUNC(…) DistCall(…) Figure 6: Dispatching method call locally or remotely. The dispatching illustrated in Figure 6 is implemented in the code generator by giving each distributed object a unique number with respect to the system definition in a VDM-RT model during initialization. This ensures that all objects can be identified based on the unique ID in the whole distributed model. The motivation for giving each distributed object a unique ID num- ber, starting from 1, will be clarified below. These IDs are assigned based on their order inside the system definition. Furthermore, it should be noted that with respect to any given CPU, the deployed objects are instantiated, while the remote objects only get an ID. For each CPU, based on the distribution inside the system definition, a local map is created indicating whether each object is remote or local. This map is generated as an array of boolean variables called DM, where true indicates a local object, and false a remote object. For example Listing 24 shows the DM array with respect to cpu1: The first position, i.e. location 0 in C arrays, is used for locally created objects during run-time, hence this is always true. Positions 1 to the number of distributed objects are used for indicating the role of a distributed object based on their ID. Hence Listing 24 shows that with respect to cpu1 the object with ID 1 is local (object s1), that with ID 2 is remote (object s2) and that with ID 3 is local (object c). , Listing 24: Distribution map with respect to cpu1 base...
Sample 1
AutoNDA by SimpleDocs

Related to Invocation Dispatching

  • Dispatching CONTRACTOR shall provide qualified and trained personnel to: • Schedule and assign drivers and vehicles in accordance with the service hour schedules and scheduled trips for each day; • Assist drivers while they are in service to carry out the assigned trips on-time, providing address assistance and telephoning passengers as needed; • Monitor the performance of scheduled trips, reassigning trips and/or adjusting the number of vehicles in service as needed to ensure on-time performance in the most efficient manner; and, • Ensure that unanticipated service demands, passenger and vehicle accidents, other events and general service delivery are handled and performed in accordance with OoA policies and procedures. Dispatching staff are to be on-duty from the time the first SNEMT vehicle is in service until the last SNEMT vehicle is out of service. Dispatch staff will also ensure that: • All voice radio communications that pertain to SNEMT comply with FCC rules and regulations, and that regulations are enforced; • Average hold times on ride check calls are maintained at no more than two (2) minutes; and The OoA “no stranded passengers” policy is enforced.

  • Available Relief for a Force Majeure Event 11.7.1 Subject to this Article 11:

  • Notifications of Outages and Maintenance In the event that a Registry Operator plans maintenance, it will provide notice to the ICANN emergency operations department, at least, twenty-­‐four (24) hours ahead of that maintenance. ICANN’s emergency operations department will note planned maintenance times, and suspend Emergency Escalation services for the monitored services during the expected maintenance outage period. If Registry Operator declares an outage, as per its contractual obligations with ICANN, on services under a service level agreement and performance requirements, it will notify the ICANN emergency operations department. During that declared outage, ICANN’s emergency operations department will note and suspend emergency escalation services for the monitored services involved.

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

  • Notification of Force Majeure Event 11.5.1 The Affected Party shall give notice to the other Party of any event of Force Majeure as soon as reasonably practicable, but not later than seven (7) days after the date on which such Party knew or should reasonably have known of the commencement of the event of Force Majeure. If an event of Force Majeure results in a breakdown of communications rendering it unreasonable to give notice within the applicable time limit specified herein, then the Party claiming Force Majeure shall give such notice as soon as reasonably practicable after reinstatement of communications, but not later than one (1) day after such reinstatement. Provided that such notice shall be a pre-condition to the Affected Party’s entitlement to claim relief under this Agreement. Such notice shall include full particulars of the event of Force Majeure, its effects on the Party claiming relief and the remedial measures proposed. The Affected Party shall give the other Party regular (and not less than monthly) reports on the progress of those remedial measures and such other information as the other Party may reasonably request about the Force Majeure Event.

  • Dispatch and Scheduling 4.3.1 The Power Producer shall be required to schedule its power as per the applicable Regulations / Requirements / Guidelines of CERC / GERC / SLDC / RLDC and maintain compliance to the Grid Code requirements and directions, as specified by SLDC / RLDC from time to time. Any deviation from the schedule will attract the provisions of applicable Regulation / Guidelines / Directions and any financial implication on account of this shall be to the account of the Power Producer.

  • Weekend Scheduling It is the policy of the Employer to schedule those nurses who so desire every other weekend off, with the exception of those nurses who have signed an authorization to work consecutive weekends. Nurses who have volunteered to work consecutive weekends may withdraw such authorization upon two (2) weeks’ written notice prior to the date a new schedule must be posted.

  • Force Majeure, Notice of Delay, and No Damages for Delay The Contractor will not be responsible for delay resulting from its failure to perform if neither the fault nor the negligence of the Contractor or its employees or agents contributed to the delay and the delay is due directly to acts of God, wars, acts of public enemies, strikes, fires, floods, or other similar cause wholly beyond the Contractor’s control, or for any of the foregoing that affect subcontractors or suppliers if no alternate source of supply is available to the Contractor. In case of any delay the Contractor believes is excusable, the Contractor will notify the Department or Customer in writing of the delay or potential delay and describe the cause of the delay either (1) within 10 days after the cause that creates or will create the delay first arose, if the Contractor could reasonably foresee that a delay could occur as a result, or (2) if delay is not reasonably foreseeable, within five days after the date the Contractor first had reason to believe that a delay could result. The foregoing will constitute the Contractor’s sole remedy or excuse with respect to delay. Providing notice in strict accordance with this paragraph is a condition precedent to such remedy. No claim for damages will be asserted by the Contractor. The Contractor will not be entitled to an increase in the Contract price or payment of any kind from the Department or Customer for direct, indirect, consequential, impact or other costs, expenses or damages, including but not limited to costs of acceleration or inefficiency, arising because of delay, disruption, interference, or hindrance from any cause whatsoever. If performance is suspended or delayed, in whole or in part, due to any of the causes described in this paragraph, after the causes have ceased to exist the Contractor will perform at no increased cost, unless the Department or Customer determines, in its sole discretion, that the delay will significantly impair the value of the Contract to the State of Florida or to Customers, in which case the Department or Customer may (1) accept allocated performance or deliveries from the Contractor, provided that the Contractor grants preferential treatment to Customers with respect to commodities or contractual services subjected to allocation, or (2) purchase from other sources (without recourse to and by the Contractor for the related costs and expenses) to replace all or part of the commodity or contractual services that are the subject of the delay, which purchases may be deducted from the Contract quantity, or (3) terminate the Contract in whole or in part.

  • Physical Distancing 1. The District shall limit occupancy of bathrooms, elevators, locker rooms, staff rooms, offices, warehouses, and conference rooms, and any other shared work or school spaces to provide no less than six (6) feet of distancing. Adjacent bathroom stalls may be used. The District shall post signs with occupancy limits conspicuously at the entrance to each room.

  • Entitlement to Force Majeure relief An Affected Party is entitled to Force Majeure relief if and to the extent that:

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