Test Bed Sample Clauses

Test Bed. 3.4.1 For the purpose of testing the Vendor shall provide the Equipment set forth in the Specifications at [***] to Reliance and such Equipment shall be shipped to the Reliance designated location not later than [***] after the Effective Date of the Broadband Access Equipment Contract if specifically requested for by Reliance in writing.
AutoNDA by SimpleDocs
Test Bed. 3.3.1 For the purpose of testing the Vendor shall provide the Software set forth in the Specifications at [***] to Reliance and such Software shall be shipped to the Reliance designated location not later than [***] after the Effective Date of the Broadband Access Software Contract if specifically requested for by Reliance in writing.
Test Bed. The Urban Partner will create a vehicle infrastructure integration (“VII”) test bed along Xxxxx Drive. • RITA’s Intelligent Transportation Systems Operational Testing to Mitigate Congestion (“ITS-OTMC”) Program • $20.2 million in funds appropriated when needed and available, but in any event no later than the end of Fiscal Year 2009; funding subject to appropriation
Test Bed. Integrator will make available to Okta, at no charge, access to a developer account and/or sandbox instance of the Integrator Product(s) for use by Okta to develop, configure, test, and/or support the Integration(s), which Okta may conduct itself or through a third party. Integrator agrees that Okta and its agents or contractors developing, configuring, and/or testing the Integration(s) will bear no responsibility for, or liability in connection with, any damages or claims arising from such testing.
Test Bed. Purchaser shall have the option (but shall not be obligated), which Purchaser may exercise in writing no later than ***. If Purchaser exercises the Test Bed Option, Contractor shall develop, test and supply the Test Bed in accordance with Section 9.0 of Exhibit A and to meet the specifications set forth in Appendix E.1 of Exhibit B. The delivery schedule and delivery location for the Test Bed shall be set forth in Section 9 of Exhibit A, Statement of Work. The payment terms are set forth in Section 2 of Exhibit E, Payment Plan.
Test Bed specifications Both the short term and the medium term demonstrators require hardware and software components for the vertical integration demonstration, as described in details below. The data plane for the short/medium term demonstrator is composed of servers used to generate traffic, TU/e Ethernet switches used for interconnection and for the medium term demonstrator, one or several Xxxxxxx switches acting as spine switch. An example of a simplified data plane demonstrator test-bed with the hardware components used is given in Figure 10. It is important to note that due to the limited number of hardware components available, such as servers or TU/e Ethernet switches, the demonstrator may have slightly different component deployment as compared to the test-beds shown in Figure 10. Xxxxxxx OCS OF Agent OF Agent OF Agent OF Agent OF Agent OF Agent OF Agent OF Agent TUE Ethernet switch OF Agent OF Agent OF Agent OF Agent OF Agent OF Agent Spine Leaf TOR Server Spine - Leaf Dynamic Data Center Figure 10: Short term and medium term data plane demonstrator test-beds Interoute Testbed and Servers Interoute testbed is located in the production infrastructure of the Interoute Milan PoP where a co- location area is dedicated to host servers and network equipment for the COSIGN demostrator. All Interoute co-location sites are provided with AC & DC power as standard, both of them are designed with N+1 resilience configuration in order to ensure redundancy and guarantee 99.99% power availability. Temperature and humidity control is provided by a heat rejection chiller system with N+1 redundancy configuration that ensure a temperature of 23°C (+/- 3°C) and humidity rate of 50% (+/- 10%). The demonstration testbed provides a dedicated hardware infrastructure that will simulate a virtualized DC environment, where all the software components and hardware equipment can be tested and evaluated. To address this purpose, 3 hardware servers will be made available, each of them with the following specifications: • (2x) 10 Core CPU • 256 GB of Memory • 1TB storage HDD • (4x) 1GbE Ports + (2x) 10Gb-T Ports • iLO Chassis Lights Out Management Card In addition, an Ethernet Switch with 48x1GbE ports + 2x10Gb-T ports can be used to interconnect the servers. The rack space reserved for the testbed equipment is 15 U, 5 of which will be used to host the three servers, the switch and a router, so that a free space of 10 U can be used to accommodate any other device provided by other par...
Test Bed. ‌ The test bed consists of a Dell OptiPlex 7010 PC with the following hardware specifica- tions: CPU Intel(R) Quad Core(TM) i7-3770 CPU @ 3.40GHz RAM 8 GB DDR3 RAM HDD 250 GB, 7200 RPM Serial-ATA and the following software installed: OS Ubuntu 13.04 Server Network emulator Mininet, version 2.1.0+ Virtual switch OVS version 2.1.0 SDN Controllers Floodlight version 0.90, OpenDayLight version 0.1.2-370 The network scenario is emulated using the Mininet framework [Xxxxx et al., 2010]. It uses OS features to instantiate lightweight virtualisation of network hosts, and interconnects them with virtual switches, according to a specified topology configuration. Effectively, what Mininet does, is to abstract this rather complex configuration task of the Operating System (OS), into a matter of high-level programming, which makes it ideal for rapid network prototyping.
AutoNDA by SimpleDocs
Test Bed. The Urban Partner (MTC) will create an open architecture vehicle infrastructure integration test bed in support of a HOT lane tolling application. Evaluation. The Urban Partner (SFMTA) will evaluate the impacts of the parking pricing project. Telecommuting/TDM Projects Local project to be implemented by Urban Partner. In connection with the implementation of the Federal Projects, the Urban Partner (SFCTA) will expand the technical and promotional aspects of San Francisco’s telecommuting and related alternative commute programs. No UPA funding Total Funding $87.29 M SFpark Variable Pricing. SFpark is the name given to the parking pricing system to be implemented by SFMTA. The primary goal of SFpark is to use intelligent parking management technology and techniques, in particular demand-responsive pricing, to manage the on-street and off-street parking supply and demand. SFMTA expects this approach to reduce the number and duration of vehicle trips and reduce double parking and, thereby, reduce congestion. SFMTA views the UPA-funded project as a pilot to test a system that will be more widely deployed throughout San Francisco in the future. The parking technologies to be tested include networked parking meters, parking occupancy sensors, and parking information systems. SFpark is expected to improve SFMTA’s effectiveness in meter maintenance, enforcement, and parking management and provide travelers with better information about parking location, availability, and price to help them make more informed travel choices. The pilot areas for SFpark are highlighted in red (or dark lines) in Figure 2-2. The new system will consist of approximately 6,000 metered on-street parking spaces (about one-quarter of the city’s total supply) and 12,250 parking spaces in fifteen city-operated garages and one lot. Control areas, highlighted in yellow (or light lines) in Figure 2-2, will be equipped with traffic sensors for monitoring use of the parking supply where variable pricing is not implemented. SFMTA’s approach to variable pricing is to adjust parking prices gradually and periodically to achieve targets for parking availability rather than dynamically adjusting pricing based on moment-to-moment changes in parking demand. SFMTA expects that drivers will be able to gradually adjust travel behaviors and choices to respond to new price information over time, whereas dynamic pricing could be potentially confusing for drivers, difficult for SFMTA to administer, and technicall...

Related to Test Bed

  • Measurement Should the State terminate this contract as herein provided, no fees other than fees due and payable at the time of termination shall thereafter be paid to the Engineer. In determining the value of the work performed by the Engineer prior to termination, the State shall be the sole judge. Compensation for work at termination will be based on a percentage of the work completed at that time. Should the State terminate this contract under paragraph (4) or (5) above, the Engineer shall not incur costs during the thirty-day notice period in excess of the amount incurred during the preceding thirty days.

  • Stability Testing Patheon may be requested to conduct stability testing on the Products in accordance with the protocols set out in the Specifications for the separate fees and during the time periods set out in Schedule C to a Product Agreement. Patheon will not make any changes to these testing protocols without prior written approval from Client. If a confirmed stability test failure occurs, Patheon will notify Client within one Business Day, after which Patheon and Client will jointly determine the proceedings and methods to be undertaken to investigate the cause of the failure, including which party will bear the cost of the investigation. Patheon will not be liable for these costs unless it has failed to perform the Manufacturing Services in accordance with the Specifications, cGMPs, and Applicable Laws. Patheon will give Client ail stability test data and results at Client’s request.

  • Testing Landlord shall have the right to conduct annual tests of the Premises to determine whether any contamination of the Premises or the Project has occurred as a result of Tenant’s use. Tenant shall be required to pay the cost of such annual test of the Premises; provided, however, that if Tenant conducts its own tests of the Premises using third party contractors and test procedures acceptable to Landlord which tests are certified to Landlord, Landlord shall accept such tests in lieu of the annual tests to be paid for by Tenant. In addition, at any time, and from time to time, prior to the expiration or earlier termination of the Term, Landlord shall have the right to conduct appropriate tests of the Premises and the Project to determine if contamination has occurred as a result of Tenant’s use of the Premises. In connection with such testing, upon the request of Landlord, Tenant shall deliver to Landlord or its consultant such non-proprietary information concerning the use of Hazardous Materials in or about the Premises by Tenant or any Tenant Party. If contamination has occurred for which Tenant is liable under this Section 30, Tenant shall pay all costs to conduct such tests. If no such contamination is found, Landlord shall pay the costs of such tests (which shall not constitute an Operating Expense). Landlord shall provide Tenant with a copy of all third party, non-confidential reports and tests of the Premises made by or on behalf of Landlord during the Term without representation or warranty and subject to a confidentiality agreement. Tenant shall, at its sole cost and expense, promptly and satisfactorily remediate any environmental conditions identified by such testing in accordance with all Environmental Requirements. Landlord’s receipt of or satisfaction with any environmental assessment in no way waives any rights which Landlord may have against Tenant.

  • Cost of Metering The Issuer shall not be obligated to pay any costs associated with the routine metering duties set forth in this Section 2, including the costs of installing, replacing and maintaining meters, nor shall the Issuer be entitled to any credit against the Servicing Fee for any cost savings realized by the Servicer as a result of new metering and/or billing technologies.

  • Measurement and Monitoring Tools Contractor shall implement measurement and monitoring tools and procedures reasonably designed to measure its performance of the Services and assess such performance against any applicable service levels. Contractor shall provide LAUSD with a monthly report of service level performance under any applicable Work Order. Upon LAUSD’s request, Contractor shall provide LAUSD with access to the measurement and monitoring tools described herein, and to any information that they generate.

  • Acceptance Testing At the time of installation of a LIS trunk group, and at no additional charge, acceptance tests will be performed to ensure that the service is operational and meets the applicable technical parameters.

  • Tests 7.7.1 If the Contract Documents, laws, ordinances, rules, regulations or orders of any public authority having jurisdiction require any portion of the Work to be inspected, tested or approved, the Contractor shall give the Architect timely notice of its readiness so the Architect may observe such inspection, testing or approval. The Contractor shall bear all costs of such inspections, tests or approvals conducted by public authorities.

  • Financial testing The financial covenants set out in Clause 20.2 (Financial condition) shall be tested by reference to each of the financial statements and/or each Compliance Certificate delivered pursuant to Clause 19.2 (Compliance Certificate).

  • Product Testing Upon request, Customer shall provide Operator a laboratory report for each Product delivery by Customer or Customer’s supplier. Operator will not be obligated to receive Contaminated Product for throughput across the Berths, nor will Operator be obligated to accept Product that fails to meet the quality specifications set forth in the arrival notice.

  • Performance Tests Contractor shall perform Performance Tests in accordance with Section 11.2 of the Agreement and Attachment S.

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