Instances Clause Samples

Instances. Data about the location of facilities and of customers, costs, demand and contract terms were randomly generated based on the following assumptions and parameter values. • The shipper operates two warehouses. • The warehouses and customer areas are randomly uniformly located in a 2-dimensional (1000×1000) grid. • The carriers’ facilities are randomly located in a (700 × 700) centered area of the grid. • For each carrier e, the size of Ie is randomly chosen from the uniform discrete distribution on an interval [i−, i+]: U [i−, i+] (see Table 2). • Customers can only be served from carriers’ facilities that are within an Euclidean distance of 500 units. No carrier can supply all customers. • The long-haul cost and cross-docking services Fi,l for operating facility i at capacity level l is of the form Fi,l = Ci + Ti,l, where Ci is the fixed operational cost of facility i, and Ti,l is the cost charged by the carrier for (full truckload) shipment requiring l trucks from the shipper’s warehouses to facility i and for operating it at level l. • The fixed operational cost Ci is set randomly from a discrete uniform distribution U [500, 1000]. • For a given operating level l, the variable cost Ti,l for long-haul transportation is proportional to the Euclidean distance from facility i to the closest warehouse. As a function of the level l, it is modelled by a staircase function with decreasing marginal costs. • The cost charged by the parcel delivery company for transporting one unit of good from facility i to customer area k, that is, Ui,k, is taken equal to the Euclidean distance from i to k. • The planning horizon is subdivided into three demand seasons, starting with low, then high, and finally mid season. For each customer region k ∈ K and each period t ∈ T , the demand quantity t (in weight units) is issued from a uniform distribution which depends on the season: U [0.1, 0.4] in low season, U [0.35, 0.65] in mid season, and U [0.6, 0.9] in high season. • In a given instance, all contracts have the same fixed duration He ∈ {2, 3, 4}, for all e ∈ E. • Each carrier has enough available capacity to meet the demand of all customer areas that can be served from its facilities. Σ

Instances. An instance for purposes of this Article is defined as an occasion starting with two (2) or more hours regardless of duration.

Instances. The rights and remedies provided herein are cumulative of, and not exclusive of, any rights or remedies provided by law, in equity, or in any other agreement or Loan Document, all of which Lender may pursue at any time and from time to time.

Instances. 3.3. You hereby agree and acknowledge that the Fees are non-refundable in any case

Instances. No consent by Landlord to any assignment or sublease shall be deemed to release Tenant from its obligations hereunder and Tenant shall remain fully liable for performance of all obligations under this Lease.

Instances. This view displays a list of all discovered Instances related to the selected host. The default view shows the combined CPU usage by all the instances on the selected host. The graph uses color to represent each instance. If you hover over a color on the graph, a pop-up identifies the instance associated with that color. 1 Select one or more check boxes. 2 Click the Apply button on the embedded view task bar. FAQts tab‌‌ The FAQts tab is provided in the OpenStack Environment view through a navigation tab and is available for some particular object types in OpenStack Explorer. In OpenStack Explorer, on the Topology tab, that appears on the navigation panel, select an availability zone or host. Through three embedded views (the Categories, Question, and Answer views), the FAQts view enables you to ask questions and provides the answers to those questions.

Instances. An instance for purposes of this Article is defined as an occasion starting with four (4) or more hours regardless of duration.

Instances. The license granted to You under this Agreement is limited to the number of Instances set forth in the Order Form. Each Instance gives You the right to authorize up to 200 Seats, 2,000,000 Lines of Code, and 50 Builds per Hour. Any usage in excess of the aforementioned limitations (i) will not be supported under this Agreement, (ii) is subject to limitation by Code Climate, and (iii) is at risk of termination. You may purchase additional Instances at the same price listed in the Order Form to increase the number of Seats, Lines of Code, and/or Builds per

Instances. Notwithstanding anything to the contrary contained in this appendix, each running instance (physical and/or virtual) of the Service Software must be licensed. An “instance” of Service Software is created by executing the Service Software’s setup or install procedure. An “instance” of Service Software is created by duplicating an existing instance. References to the Service Software include “instances” of the Service Software. Customer “runs an instance” of software by loading it into memory and executing one or more of its instructions. Once running, an instance is considered to be running (whether or not its instructions continue to execute) until it is removed from memory.