Case Scenarios Sample Clauses

Case Scenarios. In order to see how the contract’s main variables affect the players utilities, it is necessary to propose different scenarios, changing the value of parameters in different ranges. However, not all variables will change in the scenarios. On the contrary, there are parameters that remain constant throughout the project (as mentioned on Section 5.1). Each scenario presented provides results for further analysis on the variables behavior. For this purpose, 6 variables were defined to take into account for all scenarios: Due to the randomness of the variables and strategies, each realization will be composed of 500 iterations of the problem. The number of iterations was verified with variables’ standard deviation convergence, hence, the mean value is a good estimation of the variables distribution. Table 5.1: Computed variables to analyze the model’s behavior Analyzed parameters UP Principal’s utility UA Agent’s utility bP Vˆ V¯ Principal’s monetary balance Mean perceived infrastructure performance Real infrastructure performance IP Inspections with penalty
AutoNDA by SimpleDocs
Case Scenarios. In this section we exemplify the on-off model de­ duced from the SLA and other parameters as described in Sections 4, 5 and 6. A discussion of the sensitivity of the parameters is provided. First we want to recall the main approximations and assumptions used. Appendix A validates the approxi­ mation of the independence of number of failures and the accumulated down times and discusses the insen­ sitivity to fluctuations in the failure intensity. The main assumptions are related to the dependability SLOs given in Section 3.1. Note that SLAs typically define the max­ imum number of failures. In Sections 7.1 and 7.2 we deal with the problem under the assumption of a con­ stant failure intensity, i.e., a homogeneous failure pro­ cess. In Section 7.4 the result from a simulation study is shown, demonstrating that the results obtained are insensitive to fluctuations in the failure intensity. The model of the deployment cost is as given in Section 5. A compensation is assumed to be paid if one or several of the SLOs are violated during an observation interval as described Section 4.

Related to Case Scenarios

  • Screening 3.13.1 Refuse containers located outside the building shall be fully screened from adjacent properties and from streets by means of opaque fencing or masonry walls with suitable landscaping.

  • Geometric visibility The visibility of the illuminating surface, including its visibility in areas which do not appear to be illuminated in the direction of observation considered, shall be ensured within a divergent space defined by generating lines based on the perimeter of the illuminating surface and forming an angle of not less than 5° with the axis of reference of the headlamp. The origin of the angles of geometric visibility is the perimeter of the projection of the illuminating surface on a transverse plane tangent to the foremost part of the lens of the headlamp.

  • Laboratory Testing All laboratories selected by UPS Freight for analyzing Controlled Substances Testing will be HHS certified.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Unbundled Channelization (Multiplexing) 5.7.1 To the extent NewPhone is purchasing DS1 or DS3 or STS-1 Dedicated Transport pursuant to this Agreement, Unbundled Channelization (UC) provides the optional multiplexing capability that will allow a DS1 (1.544 Mbps) or DS3 (44.736 Mbps) or STS-1 (51.84 Mbps) Network Elements to be multiplexed or channelized at a BellSouth central office. Channelization can be accomplished through the use of a multiplexer or a digital cross-connect system at the discretion of BellSouth. Once UC has been installed, NewPhone may request channel activation on a channelized facility and BellSouth shall connect the requested facilities via COCIs. The COCI must be compatible with the lower capacity facility and ordered with the lower capacity facility. This service is available as defined in NECA 4.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.

  • Treatment Program Testing The Employer may request or require an employee to undergo drug and alcohol testing if the employee has been referred by the employer for chemical dependency treatment or evaluation or is participating in a chemical dependency treatment program under an employee benefit plan, in which case the employee may be requested or required to undergo drug or alcohol testing without prior notice during the evaluation or treatment period and for a period of up to two years following completion of any prescribed chemical dependency treatment program.

  • Random Drug Testing All employees covered by this Agreement shall be subject to random drug testing in accordance with Appendix D.

  • Mileage Measurement Where required, the mileage measurement for LIS rate elements is determined in the same manner as the mileage measurement for V&H methodology as outlined in NECA Tariff No. 4.

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