Contract example Sample Clauses

Contract example. ‌ Using the same model parameters and functions from Section 5.1, the optimal contract procedure is found through the contract procedure presented before. The restrictions used on this example were: !(ɸc)={UA , bP } Start ki = kmax Pi = Pmax 𝜇in i = 𝜇in min no yes VIII k <k i min yes no 𝜇in𝑖<𝜇in max no yes VI Pi>Pmin no UA ≥ 𝑢D yes ^ bP ≥-bmax Final contract parameters ϕc = 𝑘𝑖, 𝑃𝑖, 𝜇in 𝑖 IX X End Contract i ɸc ={ki, Pi, 𝜇in i } Pi= Pi-𝚫P 𝜇in i = 𝜇in i+𝚫t Pi= Pmax ki= ki-𝚫k Pi= Pmax 𝜇in i = 𝜇in min 𝑘 – Infrastructure performance 𝜇in – Mean time of inspection P – Penalty fee bP – Principal’s balance UA – Agent’s utility SP – Principal’s strategies SA – Agent’s strategies Figure 6.1: Contract’s procedure flow diagram Minimum value for the agent’s utility over construction cost: u¯/cc = 1.1 Principal’s budget (i.e., minus the minimum principal’s balance): bmax = $400 These example uses the results found in Section 5.3, therefore, the changes on the variables in each iteration will depend on the range of values considered on the sensitivity analysis. For example, the maximum Penalty Fee used on Section 5.3 was $ 100, thus, this will be the first value for the penalty fee on the contract. Table 6.2 shows the value of the contract parameter and restrictions on some iterations. Table 6.2: Contract procedure example Iteration P µin k UA/cc bP 1 100 1 90 0.89 -156 2 50 1 90 0.97 -310 3 20 1 90 1.02 -394 4 100 2 90 0.94 -200 : : : : : : 29 50 2 70 1.04 -225 30 20 2 70 1.10 -342 We can see on Table 6.2 that after 30 iterations, the optimal contract parameters are: φc = { P = $20 , µin = 2 years , k = 70 } These parameters form the contract with the highest expected value for the utilities of both entities, taking into account their decisions and their participation constrains.
AutoNDA by SimpleDocs
Contract example. ‌ Using the same model parameters and functions from Section 5.1, the optimal contract procedure is found through the contract procedure presented before. The restrictions used on this example were: !(ɸc)={UA , bP } Start ki = kmax Pi = Pmax 4in i = 4in min no yes VIII k <k i min yes no 4in9<4in max no yes VI Pi>Pmin no UA ≥ CD yes ^ Final contract parameters ϕc = '$, -$, 4in 9 X End Contract i ɸc ={ki, Pi, 4in i } Pi= Pi-FP

Related to Contract example

  • Contract Exhibit J Quarterly Sales Report If a conflict exists among any of the Contract documents, the documents shall have priority in the order listed below:

  • Contract Task Order A-E shall be assigned work via a task order by COUNTY which shall subsequently be referred to as the “Contract Task Order” (hereinafter “CTO”). A CTO for each project shall be developed by A-E in conjunction with COUNTY Project Management staff. The COUNTY Project Manager shall manage all A-E’s work including monitoring the CTO work schedule, quality of deliverables, review of invoiced amounts, adherence to set budget, and internal review of submittal packages. A-E shall follow all requirements as outlined in the CTO; this general Scope of Work, the project specific Scope Statement, and the Architect-Engineer Guide (Rev July 2018). The CTO shall include a detailed Scope Statement, describing tasks to be performed with a specific list of deliverables for each task, schedule of work and cost to complete the work. The schedule of work shall allow enough time for meetings with COUNTY Management staff to review the work progress, provide technical and policy direction, resolve problems and ensure adherence to the work completion schedule. The CTO shall include a cover sheet provided by COUNTY Project Management staff with the appropriate signature blocks and contract information. Once both Parties agree, and all Parties have signed the CTO, COUNTY Management staff shall provide A-E with a Notice to Proceed (NTP) to begin work. A-E shall submit all plans, reports and other documents produced under the CTO to the assigned COUNTY Project Manager within the timeframe indicated in the CTO or as directed by COUNTY Project Management staff.

  • Contract Changes Changes may not be made in the terms and conditions of this contract without the agreement and written permission of the Director of Housing.

  • CONTRACT SCOPE Pursuant to this Master Contract, Contractor is authorized to sell and provide only those Goods and/or Services set forth in Exhibit A – Included Goods/Services for the prices set forth in Exhibit B – Prices. Contractor shall not represent to any Purchaser under this Master Contract that Contractor has contractual authority to sell or provide any Goods and/or Services beyond those set forth in Exhibit A – Included Goods/Services.

  • Purchase Order Flip via Ariba Network (AN) The online process allows suppliers to submit invoices via the AN for catalog and non- catalog goods and services. Contractors have the ability to create an invoice directly from their Inbox in their AN account by simply “flipping” the purchase order into an invoice. This option does not require any special software or technical capabilities. For the purposes of this section, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider of MFMP the right and license to use, reproduce, transmit, distribute, and publicly display within the system the information outlined above. In addition, the Contractor warrants and represents that it is authorized and empowered to and hereby grants the State and the third-party provider the right and license to reproduce and display within the system the Contractor’s trademarks, system marks, logos, trade dress, or other branding designation that identifies the products made available by the Contractor under the Contract.

  • Shift Rotation Routine shift rotation is not an approach to staffing endorsed by the Employer. Except for emergency situations where it may be necessary to provide safe patient care, shift rotation will not be utilized without mutual consent. If such an occasion should ever occur, volunteers will be sought first. If no one volunteers, the Employer will rotate shifts on an inverse seniority basis until the staff vacancies are filled.

  • CONTRACT SUM 9.1.1 The Contract Sum is stated in the State-Contractor Agreement and, including authorized adjustments thereto, is the total amount payable by the State to the Contractor for the performance of the Work under the Contract Documents.

  • Contract Pricing Contractor is required to post a copy of the complete Contract pricelist, in Excel AND PDF format, on their website.

  • Price Schedule, Payment Terms and Billing, and Price Adjustments (a) Price Schedule: Price Schedule under this Contract is set forth in Exhibit B.

  • Contract Type OASIS SB is a family of Multiple Award, Indefinite Delivery, Indefinite Quantity (MA-IDIQ) task order contracts for Government-wide professional service based requirements which is available for use by all Federal agencies and other entities as listed in the current General Services Administration (GSA) Order, OGP 4800.2I, Eligibility to Use GSA Sources of Supply and Services. OASIS SB allows for all contract types at the task order level (e.g., Cost-Reimbursement (all types), Fixed-Price (all types), Time-and-Materials, and Labor-Hour). Task orders may also combine more than one contract type (e.g., FFP/Cost, FFP/Labor Hour etc.). Additionally, task orders may include incentives, performance based measures, multi-year or option periods, and commercial or non-commercial items.

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