Scenario 1 Sample Clauses

Scenario 1. PTC exploits the Programme Intellectual Property on a For-Profit Basis alone (or in collaboration with a Distributor or marketing/sales agent under which PTC retains overall control of worldwide commercialization).
AutoNDA by SimpleDocs
Scenario 1. If Seller breaches a CHP PPA with the Buyer, and Xxxxx has another PPA with Seller, then cross default could be triggered; provided that another PPA means a PPA between the specific Seller, as signatory and as referenced in Section 4.2.8.4.2, and the specific IOU Buyer, as signatory to such PPA. Another PPA is a contract between the Buyer and Seller for electric power, and not a contract for other goods or services.
Scenario 1. In the event that the Net Settlement Fund exceeds the total of the Amounts Allegedly Withheld for all Claimants submitting Valid Claims, Claimants submitting Valid Claims will be paid their Amount Allegedly Withheld, regardless of the Payment Group (defined below) to which they are assigned. Any remaining amount left in the Net Settlement Fund will be paid to the Cy Pres Recipients identified in § 1.11.
Scenario 1 incident report from a Railway Operator. There aren’t many public incidents in this sector, but in May of 2018, the Danish state rail operator was hit by a DDoS cyberattack, causing a breakdown which prevented train passengers across the country from buying tickets on that day. This scenario, presented in Figure 23, represents information sharing of a cyber-security incident in the network of a RST, the steps and procedures to inform the community without compromising the reputation of the victim nor the operator, supporting CSIRT operations and threat intelligence.
Scenario 1. 60% GLF (long term) This water balance will be based on a 60% GLF. All input information is as per document [122] The Consultant shall take into consideration the decommissioning and phasing out of ash dam 1, 2 and 3 in the water balance.
Scenario 1. Advertising based on location If the user has enabled the location sensor, the client application periodically sends some location updates, providing new GPS coordinate data. When the platform receives a location update related to a particular user, it checks what are the commercial POIs around this user and try to match the POI advertising profile with the user profile for the following profile fields: • User profile age versus advertising profile age interval (User profile age must be inside the advertising profile age interval • User profile Age interval versus advertising profile age interval (User age interval must be inside the advertising age interval. • User gender versus advertising profile gender. • The POI must have one keyword that is part of the User profile hobby list • The POI coordinates and the size parameter must form a circle that “contains” the user location coordinates If multiple POIs match the above criteria, the platform selects the one that has the highest number of matches between the list of POI keywords and the list of hobbies. The second criterion is the proximity of the POI for the user. By default the user does not receive advertising notifications. He must enable its reception in the client application settings. The POI advertising is enabled when a user enters an area centered on the POI. Each time, a notification is sent to an identity, the platform remembers it to avoid pushing multiple times the same notification. If the user leaves the area and re-enter it again, he might receive the notification related to that specific site again. Once the POI is selected, a notification is sent to the user related to the commercial POI. Note that only the best POI is selected and pushed but as one POI advertising notification cannot be sent multiple times unless the user exits and re-enters the advertising zone, advertising for other POI might be sent as well later on, when location is updated. Strategies on pushing advertising might be refined to be well accepted by the end user.
Scenario 1. Demonstrator #4 The assessment of the operational scenario outlined by the Demonstrator #4 is quite straightforward: looking at the standard scenarios defined by ENAC (see section 3.4.2.3), the foreseen operations fits almost perfectly with S04 and S05 (depending on the mass of the RPAS). Being at the moment not yet defined the RPAS model to be used in demonstrator #4, this section will illustrate technical prescriptions and operational limitations for the two mass categories: less or equal to 4 kg and up to 25 kg. Standard Scenario S04: RPAS with a MTOM below or equal to 4 kg, without an inoffensive nature (art. 12), operated in extra-urban areas and over construction sites or linear infrastructures, e.g. highways, power lines, railways, gas pipelines Technical prescriptions: RPAS on-board lights: front-right green light, front-left red light, rear white light (in the case of night VLOS) Operational limitations Flight conditions: VLOS Maximum Altitude: 150 m in daylight VLOS / 50m in night VLOS Maximum distance from the pilot: 500 m from the pilot in daylight VLOS / 100m in night VLOS Maximum speed: 5 m/s Maximum wind speed: 5 m/s Minimum buffer size: 30 m (from other buildings/infrastructures) Minimum buffer size when “geofencing6” function available: 15 m Minimum buffer size for tethered operations: 5 m Conditions Operations should be conducted:  In accordance with the operations manual defined by the operator and the flight manual provided by the manufacturer  By a pilot with adequate qualification  In accordance with the flight rules and access to the airspace The operator is responsible to check whether flight limitations are in place in the area of the operations. Standard Scenario S05: RPAS with a MTOM in between 4 and 25 kg, without an inoffensive nature (art. 12), operated in extra-urban areas and over construction sites or linear infrastructures, e.g. highways, power lines, railways, gas pipelines Technical prescriptions  RPAS on-board lights: front-right green light, front-left red light, rear white light (in the case of night VLOS)  Independent flight termination system, other than the command and control system  Command and control system with geofencing and data link recovery functionalities
AutoNDA by SimpleDocs
Scenario 1. EASA has issued a design approval to a UK DAH and TCCA validation is in progress. The procedure for continued validation is:
Scenario 1. If the Transferring Customer transfers to a Retail Electricity Supplier (RES) that is an Affiliate of the Seller, the Buyer shall be entitled to RCOA Reduction provided that: a) That the Transferring Customer was an existing captive customer of the Buyer prior to COD. LOT NO. / REQUIREMENTS LOT NO. 1 LOT NO. 2 LOT NO. 3
Scenario 1. If yi  (1  ui )Ki . From equations (4.1), (4.2) and (4.3), it can be derived that:  (1 ui ) Ki si  E[Qu ]    (D  y ) f (D )d (D )  [(1  u )K yi (1 ui ) Ki  y ][1  F ((1  u )K )]  = [(1  u ) K  y ]    Fi ( Di )dDi yi E[Qo ]  0  i  (1 di ) Xx  i  E[Qu ]  
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!