We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Event model Sample Clauses

Event model. Figure 8 - Events dispatched and consumed by the EventProcessor Interface Note: to ease extensibility, the architecture will manage events in an agnostic way. Specifically, the contents of the events will not be considered as part of the routing task, instead classified will be based purely on TypeId and Version.
Sample 1
Event model. This section of the data model describes the modeling of the events inside the HUMAN system. The events stored inside this part of the data model are the low frequency data and commands which are used in the system. Examples of low frequency data are the request for intervention made by the Intervention Manager, the outputs of the Short Term Reasoning Engine and of the Long Term Reasoning Engine when a deviation is detected, updates regarding advancements in the task execution, start / end of a working shift. As a disambiguation note, the modeling of the event is not intended to replicate the Message Schema used to exchange data through the Middleware nor to store all the exchanged data on the middleware. It is important to note that the events that are saved are the low frequency, meaning that data coming from the sensors are not stored in this way.
Sample 1
Event model. The “event” entity in 4SECURail will describe a cyber-security incident, threat, vulnerability or risk, and will be used as the information unit to be shared with other organisations for intelligence purposes. This event model will therefore be flexible to admit a large variety of fields for supporting security teams to identify the different events that they might face.
Sample 1
Event model. According to the [MISP data standard], an event is a simple meta structure scheme where attributes and meta-data are embedded to compose a coherent set of indicators. An event can be composed from an incident, a security analysis report or a specific threat actor analysis. The event model is therefore flexible to admit a large variety of fields for supporting security teams to identify the different events that they might face. The meaning of an event only depends of the information embedded in the event. The following sections summarise the data model used in 4SECURAIL. The information about the data model used is detailed at the MISP standard website (xxxxx://xxx.xxxx-xxxxxxxx.xxx/). 9.3.1.1 Core of the event
Sample 1

Related to Event model

  • Additional Features Additional Features are invoiced at the start of the first Contract Year following the Contract Year in which such Additional Features are activated.

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

  • DATA LOSS The Company does not accept responsibility for the security of Your account or content. You agree that Your use of the Website or Services is at Your own risk.

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

  • Additional Event of Suspension Section 4.01. Pursuant to Section 6.02 (l) of the General Conditions, the following additional event is specified, namely, that a situation has arisen which shall make it improbable that the Program, or a significant part thereof, will be carried out.

  • Enhanced Extended Links (EELs) 5.2.1 EELs are combinations of unbundled Loops and unbundled dedicated transport as defined in this Attachment, together with any facilities, equipment, or functions necessary to combine those Network Elements. BellSouth shall provide Southern Telecom with EELs where the underlying UNEs are available and in all instances where the requesting carrier meets the eligibility requirements, if applicable. 5.2.2 High-capacity EELs are combinations of loop and transport UNEs or commingled loop and transport facilities at the DS1 and/or DS3 level as described in 47 CFR 51.318(b). High-capacity EELs must comply with the service eligibility requirements set forth in 5.2.4 below. 5.2.3 By placing an order for a high-capacity EEL, Southern Telecom thereby certifies that the service eligibility criteria set forth herein are met for access to a converted high-capacity EEL, a new high-capacity EEL, or part of a high-capacity commingled EEL as a UNE. BellSouth shall have the right to audit Southern Telecom’s high-capacity EELs as specified below. 5.2.4 If a high-capacity EEL or Ordinarily Combined Network Element is not readily available but can be made available through routine network modifications, as defined by the FCC, Southern Telecom may request BellSouth to perform such routine network modifications. The request may not be used to place fiber. Each request will be handled as a project on an individual case basis. BellSouth will provide a price quote for the request, and upon receipt of payment by Southern Telecom, BellSouth shall perform the routine network modifications.

  • Pricing Errors Any material errors in the calculation of net asset value, dividends or capital gain information shall be reported immediately upon discovery to the Company. An error shall be deemed "material" based on our interpretation of the SEC's position and policy with regard to materiality, as it may be modified from time to time. Neither the Trust, any Fund, the Distributor, nor any of their affiliates shall be liable for any information provided to the Company pursuant to this Agreement which information is based on incorrect information supplied by or on behalf of the Company or any other Participating Company to the Trust or the Distributor.

  • Extraordinary Events Regarding Common Stock In the event that the Company shall (a) issue additional shares of the Common Stock as a dividend or other distribution on outstanding Common Stock, (b) subdivide its outstanding shares of Common Stock, or (c) combine its outstanding shares of the Common Stock into a smaller number of shares of the Common Stock, then, in each such event, the Purchase Price shall, simultaneously with the happening of such event, be adjusted by multiplying the then Purchase Price by a fraction, the numerator of which shall be the number of shares of Common Stock outstanding immediately prior to such event and the denominator of which shall be the number of shares of Common Stock outstanding immediately after such event, and the product so obtained shall thereafter be the Purchase Price then in effect. The Purchase Price, as so adjusted, shall be readjusted in the same manner upon the happening of any successive event or events described herein in this Section 4. The number of shares of Common Stock that the Holder of this Warrant shall thereafter, on the exercise hereof as provided in Section 1, be entitled to receive shall be adjusted to a number determined by multiplying the number of shares of Common Stock that would otherwise (but for the provisions of this Section 4) be issuable on such exercise by a fraction of which (a) the numerator is the Purchase Price that would otherwise (but for the provisions of this Section 4) be in effect, and (b) the denominator is the Purchase Price in effect on the date of such exercise.

  • Price Adjustment Civil works contracts of long duration (more than 18 months) shall contain an appropriate price adjustment clause.

  • Aircraft Basic Price The Aircraft Basic Price is listed in Table 1 and is subject to escalation in accordance with the terms of this Purchase Agreement.

Most Referenced Clauses

Most Referenced Definitions