Demand model Sample Clauses

Demand model. In a previous section, the abstract resource notation was introduced but a demand model specification is also needed. Prior to the definition of any mechanism, it is important to have a good idea of the demand for resources in the allocation mechanism. This way, it is easier to tailor the mechanism design decision so as to provide meaningful allocations to the users, facilitating trade, resulting in the efficient operation and high utilization of the system. As already introduced in DJRA2.1, users require sets of heterogeneous resources to meet their needs, such as some virtual routers and a certain amount of bandwidth over the communication links that interconnect them. Obviously, the scarcity level of these resources is expected to vary significantly. To simplify the presentation, our assumptions are: • Resources that are under-demanded are given for a fixed price to the users, which is publicly announced and known to all. • The price of the remaining resources for which there is a competition, should be dynamically decided by the market mechanism, so as to reflect their scarcity and actual value. This is both economically sound and allows the market to have both meaningful prices and efficient resource allocations. The potential decision on these prices will be elaborated in the following sections where the FEDERICA mechanism is fully specified. Another feature, which must also be taken into account by the FEDERICA mechanism, is that the user demands can be either flexible or not, in terms of the resource allocations demanded/received. If a user requests a certain set of resources for experimental purposes and the experiment must be repeated under identical conditions, the set of resources must be permanently allocated, and the user demand is not flexible. This imposes stringent requirements for the resource allocation mechanism that should be able to provide this kind of service, and is henceforth referred to as “guaranteed”. Alternatively, for other users it may be acceptable to allocate even a subset of alternative resources later in a flexible way. This service should also be made possible and is referred to as “best effort”. Lastly, it is also desirable to allow users that initially demand guaranteed service to denote to the resource allocation mechanism that ´best effort´ service is also acceptable when the resource prices are too high for the user to obtain the guaranteed service.
Sample 1
AutoNDA by SimpleDocs
Demand model. The projected demand for early care and education services will be based on both the number of children in the City, the proportion of those children needing child care and “capture rates” of different types of care (based on current use as well as stated demand from the survey analysis). Root will incorporate the demographic data and projections collected in the previous task with estimated capture rates for the use of early care and education services from the household survey into a spreadsheet-based childcare demand model. The model will project the demand for services over the next five and ten years by age, type of care (i.e., type of care/facility, full-time versus part-time, evening and weekend care), and income level (to account for cost sensitivity). The model would estimate total number of potential childcare consumers in the city (both residents and in-commuters).
Sample 1

Related to Demand model

  • Alternate Work Schedule An alternate work schedule is any work schedule where an employee is regularly scheduled to work five (5) days per week, but the employee’s regularly scheduled two (2) days off are NOT Saturday and Sunday.

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

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

  • Alternate Work Schedules Workweeks and work shifts of different numbers of hours may be established for overtime-eligible employees by the Employer in order to meet business and customer service needs, as long as the alternate work schedules meet federal and state law. When there is a holiday, employees may be required to switch from their alternate work schedules to regular work schedules.

  • Alternative Work Schedules Alternative work schedule means an approved schedule for an Employee that deviates from the work week described in Section 1, Section 2, or a schedule that deviates from a worksite’s normal schedule. Employees who work a “shift work schedule” as part of a rotating group of individuals who must continuously maintain a 24-hour operation or facility are not eligible for an alternative work schedule.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Milestone schedule Please state the status and progress of each Milestone and identify any completed Milestone(s) for the previous calendar quarter.

  • Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.

  • Program Review The Contracting Officer or other authorized government representative may hold semi- annual program review meetings. Such meetings will be held via telecom or video teleconferencing. However, the Government reserves the right to request a meeting in person. The meetings will include all BPA holders, representatives from prospective customer agencies, a combination of current and prospective customer agencies, or individual BPA holders. Some Federal Government Agencies and any approved State, Local and Tribal agencies may establish a central program management function. Such users may require their primary suppliers to participate in agency program review meetings on a periodic basis, at no additional cost to the Government.

  • For Lump Sum Change Order The payment and extension of time (if any) provided by this Change Order constitutes compensation in full to the Contractor and its Subcontractors and Suppliers for all costs and markups directly and indirectly attributable to the Change Order herein, for all delays related thereto and for performance of changes within the time stated.

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