Formal model Sample Clauses

Formal model. The SLA Formal Model (SLAFM) is aimed to provide a theoretical approach for a contractual vio- lation detection capability for cloud computing ser- vices. A previous draft of the same formalism was discussed in [8], where only a specific scenario has been taken into account. We extend that formal model by adding the modelling of cloud services logs; ac- cording to that, some changes to the modelling of the SLA structure have been added. The model utilizes mathematical formalisms as tuple, set theory, func- tions [3].
AutoNDA by SimpleDocs
Formal model. The Paxos protocol assumes an asynchronous distributed system in which processes com- municate by message passing. The failure model is non-byzantine, which means that pro- cesses may fail only by crashing. The system model also assumes eventually reliable links; there is a time after which every message sent by a correct process to another correct process eventually arrives (i.e. there are no message losses).
Formal model. Xxxxxxx-Xxxxxxx model revisited by Xxxxx A can ask
Formal model. ‌ In this section, we describe a client’s task specification, its utility and conditions of ne- gotiation which include a negotiation protocol, the fundamental time-dependent tactics for a client and the GRA [17] and their level of knowledge about each others’ nego- tiation parameters. In the following chapters, this formal model is extended and/or modified.
Formal model for describing cascading effects‌ A fundamental aspect of the method is the use of a more detailed formal model for describing cascading effects in past events, which is based on the conceptual model illustrated in Figure

Related to Formal model

  • Financial Model 37.1 Unless otherwise agreed between the parties, any amendments to the Financial Model shall reflect, be consistent with and be made only in accordance with the provisions of this Agreement, and shall in all cases be subject to the prior written approval of the Authority (such approval not to be unreasonably withheld or delayed). In the event that the parties fail to agree any proposed amendments to the Financial Model, the matter shall be referred for resolution in accordance with Schedule Part 20 (Dispute Resolution Procedure).

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

  • Model List your model number of the product you are bidding.

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Contract Area, including its abandonment.

  • Formal Grievance Procedure 1. In the event that a complaint cannot be resolved informally, the parties shall pursue the first step in the formal grievance procedure before making any application for arbitration, unless the College and the AAUP agree in writing to alter the procedure or waive one or more of the steps by proceeding directly to arbitration.

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • Adjustment Plan (A) If the Employer introduces or intends to introduce a measure, policy, practice or change that affects the terms, conditions or security of employment of a significant number of employees by classification to whom the Collective Agreement applies;

  • Implementation Schedule TIME IS OF THE ESSENCE with regard to all dates and time periods set forth and/or incorporated herein. Any material modification or deviation from an approved schedule described in this Agreement shall occur only upon approval of the City and RDA, with any such approvals required to be in writing as an amendment to this Agreement, and which approvals shall not be unreasonably withheld. City shall cooperate and act promptly with respect to any and all permits or approvals necessary for completion of the Project. Notwithstanding the above, this Agreement shall not limit the discretion of the City, or any of its duly appointed and authorized governing bodies, boards or entities, in approving or rejecting any aspect of the Project or improvements contemplated on or about the Property.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Work Plan Coordinate a work plan including a list of the proposed meetings and coordination activities, and related tasks to be performed, a schedule and an estimate. The work plan must satisfy the requirements of the project and must be approved by the State prior to commencing work.

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