Scenarios. A roommate has invited a member of the opposite sex back to his/her room. How would you handle the situation? • You have a couple of roommates who do not participate in any apartment-related activities. They separate themselves from the group and spend time in their room(s). What would you do to build unity in your apartment? • A certain roommate has poor personal hygiene practices and seldom showers or performs any self-care. Sometimes the roommate’s body odor is offensive to you and others in the apartment. How would you approach this roommate and what would you do to help? • One roommate is casual about keeping curfew and often comes in late. You’ve tried to teach this roommate in a lighthearted, casual way but he/she has not changed his/her behavior. What do you do now? • On Sundays you’ve noticed that a roommate or two violate dress and grooming standards for church meetings. For example, the skirt is shorter than it is on weekdays or the facial hair is more prominent on Sundays than on any other day of the week. What would you do? • You notice that a roommate has some edgy posters, DVDs, and reading material in his/her room. He/she is often up late on the computer and you suspect that he/she is involved in viewing pornography. What action would you take? • Your neighbors are planning a costume party that is reported to include a DJ, black lights, and “crazy” music. You’ve been invited but feel that the party is not going to reflect BYU-Idaho standards for dress and behavior. What would you do? • You are aware of a roommate who is engaging in activities of self-harm. He/she has had a rough home life and you know that he/she is struggling emotionally, psychologically, and spiritually. How would you address this situation? • A friend is planning a co-ed camping trip next weekend. You are invited to attend. This is not a campus- or xxxx-sponsored event and you know that it compromises a university standard. What would you do? • An engaged roommate has his/her fiancée over for several hours every day. They eat lunch and dinner together (often leaving a mess) and have taken up “residency” on the couch. There is seldom a time that the fiancée is not present. You’re beginning to feel uncomfortable in your own apartment. What would you do? • You have two roommates who seem to always be watching TV shows or movies that portray sexuality, intense violence, and/or use profanity including taking the Lord’s name in vain. You’re a bit scared to approach these roomm...
Scenarios. The Parties hereby agree that all Scenarios existing as of the Effective Date, and not subject to use or license restrictions in any agreement between VirTra and a third party, are accurately described in Exhibit H, and are considered part of the VirTra Software and the Integrated Software hereunder. Where VirTra develops or has developed additional Scenarios after the Effective Date, VirTra shall promptly notify Modern Round, and such additional Scenarios shall be deemed part of VirTra Software. Modern Round may from time to time develop its own Scenarios, which shall be owned solely by Modern Round, and Modern Round shall have no obligation to use any Scenarios provided by VirTra; provided, however, that any [****]. VirTra hereby agrees that it shall develop and deliver additional Scenarios as set forth in the Development Plan during the Term of this Agreement.
Scenarios. Three scenarioswere identified which are both scientifically challenging and com- mercially relevant. They represent comprehensive sets of challenges in an illus- trative way, so that robotics experts can easily relate their own research to them. The scenarios build on each other. – The first scenario of ECHORD is the human-robot co-worker. In this scenario, the traditional idea of pre-programmed robots was dropped, and the robot interacts with a human towards achieving a common goal. This scenario is especially relevant for future industrial applications, where the (physical or sensor-based) fences between robots and humans disappear. – The second scenario is the hyper-flexible cells scenario. This scenario envisages not only one or more highly dexterous and cooperative robots, but also the hardware and software integration of the robots with an automatic warehouse system and the other devices present in the cell. – The third scenario is the cognitive factory. This scenario aimed at taking the classical concept of the flexible manufacturing systems to a new level. The final goal is to create environments which configure themselves and are fault-tolerant, and which contain autonomous robots jointly participating in the production process with their human counterparts.
Scenarios. This section presents an evolved description of the scenarios from D3.1 with a mapping to the presented FLAME architecture and the use cases above. Throughout all scenarios, we will represent each media component by a unique FQDN using the naming convention <COMPONENT_ACRONYM>.xxxxxxxx_xxxx.xxxxx.xx Furthermore, each relationship connector between two media components illustrates a direction representing the component that initiates and the component which serves. This information flow is reflected in the naming of the require service level agreement between two media components, i.e.: <SERVING_MEDIA_COMPONENT><INITIATING_MEDIA_COMPONENT>
Scenarios. Here different scenarios can be designed. The scenarios are defined by their variations to the reference sce- xxxxx that has been defined in the Demands, Supply, Storages and Introduction and setup parts. You can choose how many scenarios you want to make, as well as how many variations should be made in each scenario. Figure 26 Screenshot of the “Scenarios” in Simulation interface • How many scenarios do you want to make?: Set how many scenarios you want to make. The matrix below will adjust accordingly. Note, changing either number of scenarios or variations resets the matrix below. • How many variations do you want to make?: Set how many variations you want to make on the refer- ence in each scenario. The matrix below will adjust accordingly. It is important to remember that some technologies are defined by more than one input, such as electricity storage, and it is important to include all relevant inputs of a technology that one wants to change. Note, changing either number of scenarios or variations resets the matrix below.
Scenarios. All experiments will be run in four different scenarios. No RINA Network: This scenario uses triggers from the operators OSS/NMS (here simulated by a skeleton application) to benchmark the DMS strategy execution. All developed strategies will be tested for speed and scale. The DMS will be a stand-alone DMS as shown in Figure 11. Minimum RINA Network: This scenario uses the minimum RINA network (2 hosts, 2 border routers, 1 interior router, cf. Figure 13) with an associated strategy for the experiment. The DMS will be a full configuration as shown in Figure 12. Medium Size RINA Network: This scenario uses a medium size RINA network, for instance the European network used in experiment 3 as shown in Figure 21 and an associated strategy for the experiment. The DMS will be a full configuration as shown in Figure 12. Milestone Month Description MS1 M16 DMS Software with Strategy Executor, OSS/NMS trigger, MA/Demonstrator Integration MS2 M17 Strategy for experiment defined and tested MS3 M18 Strategy for experiment defined and tested MS4 M19 Strategy for experiment defined and tested MS5 M20 Strategy for experiment defined and tested MS6 M21 reference experiment with measurements on LMI reference server MS7 M22 continuous experiments for scenario 1 (benchmarking) MS8 M24 continuous experiments for scenario 2 (minimal RINA network) MS9 M26 continuous experiments for scenario 3 (medium size RINA network) MS10 M28 continuous experiments for scenario 4 (large size RINA network) Table 1: Milestones for experiment 1 DRAFT Large Size RINA Network: This scenario uses a large size RINA network, for instance the US network used in experiment 3 as shown in Figure 22 and an associated strategy for the experiment. The DMS will be a full configuration as shown in Figure 12.
Scenarios. Scenarios were used in two ways during the testing process, either as functional structures to test all aspects of a component, or as reflection of a real-world SLA monitoring situation. Scenarios of the first type were created for all of the sub-languages of the SLA DSL. They were not based on actual SLAs and focused purely on testing every aspect of the language. Two scenarios of the second type were also constructed. They do not test each individual step of the language, but they do validate the interaction between all components in the architecture. The scenarios are based on the running example of Section 3.1, one for import and one for export orders. The SLA used for the export scenario can be seen in Listing 8.1. The scenarios’ SLAs define the following for a fictitious logistics service:
Scenarios. For the long-term simulation, the effects of water management measurements were assessed by hind casting the lake’s water quality both with and without the implemented measures of an increased flushing regime and the increased removal of phosphate of the WWTP that discharges in the lake. Additionally, the effect of increased temperatures (deduced from climate scenarios of the Royal Dutch Meteorological Institute (KNMI) and set on +0.9°C (G) and +2.6°C (W+)) was superposed on the original run and on the run with no increased efficiency of the WWTP to investigate whether or not increased temperatures are of importance in comparison with the taken measure. In the short-term runs three scenario types were performed: only an increase in temperature, only a change in nutrient concentrations and the combination of those two types of scenarios. Temperature scenarios that were used were: 1. +0.9°C (G), 2. +1.3°C (G+), 3. +1.8°C (W) and 4. +2.6°C (W+) (KNMI climate scenarios). Nutrient scenarios were set for both increased and reduced concentrations of nitrogen and/or phosphorous relative to the reference run. Increased nutrient concentrations stands for increased eutrophication due to climate change and reduced nutrient concentrations for water management efforts. Increased nutrient concentrations were set on +10% nitrogen and/or +10% phosphorous and reduced nutrient concentrations on -10% nitrogen and/or -10% phosphorous The combined effect of temperature increase and change in nutrient concentrations resulted in six scenarios, being: 1. +0.9°C and -10% nitrogen reduction, 2. +0.9°C and -10% phosphorus reduction, 3 +0.9°C and -10% nitrogen and -10% phosphorus reduction, 4. +2.6°C and -10% nitrogen reduction, 5. +2.6°C and -10% phosphorus reduction, 6 +2.6°C and -10% nitrogen and - 10% phosphorus reduction, Boundary conditions As this model study is meant merely to explore the relative contribution of climate change and water management measures to the water quality, some simplifications are made. Changes in solar radiation patterns, precipitation patterns, residence time (both climate and management induced), macrophyte growth and dynamic grazing were not taken into account.
Scenarios. These scenarios describe some aspects of the accidents analysed in the earlier sections. They are provided in order to allow a ship simulator to reproduce the general conditions present in the discussed accidents, however, they do not necessarily reproduce the root causes of the accidents themselves. As has been discussed, many accidents are caused by human error, poor maintenance, and other factors that cannot be replicated in a simulator. Therefore the scenarios developed have been limited to weather and environmental conditions, vessel particulars to allow for handling and performance characteristics to be simulated, operational conditions such as speed and loading conditions, route taken, and a generic sequence of important events for each accident type. Some of the events and conditions leading up to the accident are taken from the preconditions of the time sequence models, in particular the enabling circumstances of the preconditions. It is not possible to simulate levels of human skill, fatigue, or organisational shortcomings and it is not expected that human errors will be deliberately repeated so aspects such as these have not been included. It is also true that some of the accidents are more relevant to this exercise than others or more easily set up in the simulator, for this reason one accident of each type has been selected. For the grounding case, the Nanny scenario has been selected as the navigation at night with an unlit range beacon and narrow entry to Chesterfield Narrows at night after having to pass the Xxxxxx is more complex than the alternative grounding case. For the ice collision, the Explorer scenario has been selected as it is more relevant than the Saputi collision where an earlier turn could have avoided the event. For the collision scenario, only one suitable convoy collision was identified due to a lack of detailed accident reports and so the Mesabi Miner case is used.
Scenarios. 1. The employer sends its employees to take testing at an onsite facility or during working hours. Each employee is entitled to regular wages and fringes per contract for time required. The PIPE Committee will reimburse the contractor for the actual cost of the test and the equivalent of the stipend.
