Constraints on the Experimenters Use Sample Clauses

Constraints on the Experimenters Use. The SoftFIRE infrastructure is composed by loosely integrated platform under different administrative domains. In addition, the different platforms are ran for experimental purposes and they are not yet considered a mass production tool. This means that bugs and issues in the platform behaviour can occur and will occur. Actually, the scope of the experiments is also to support the tune up and the assessment of the platform as a whole. The Platform is still under development and it has a basic set of functionalities that have to be tuned up and it is missing a number of features that will be progressively added in the future. SoftFIRE is by no means to be considered a product and so the usual support for software development cannot be granted. Even if SoftFIRE aims at programmers, not all the features to allow for a fast programming approach are provided. This is due to differences in the component testbeds and to security controls imposed by different administrative domains. The programming phases could result cumbersome and not particularly attractive; however they may improve along the lifetime of the project. Service level agreements (SLA) do not apply during the experimentation phases. Because this is a period to test and explore SoftFIRE, the experimenters should not run production applications on the infrastructure Platform during the trial. The SoftFIRE project reserves the right to discontinue at any time the service if the use is not consistent with the purpose of SDN/NFV and/or violate any aspects of infrastructure security or shall conflicts any ongoing experimentation. During the running period of the experiments, the SoftFIRE project will put in place a team that will support the experiments in their work on the platform. As said this is not offered as a professional service and its working will be on the base of best effort. The entire infrastructure should be considered more a sort of α-test platform. Possible downs could occur without notice or due to overload caused by parallel experiments. SoftFIRE will offer expertise available by email (with possible follow-up by phone) and two hours per day during the experimentation phase in order to collect issues and provide responses. We’ll try to provide most of the answers by 24 hours (typically next morning or afternoon). Some issues could be not solvable due to the short time of the experiment period or due to the need to intervene on the platform. The supporting time will work with experimente...
Sample 1See All (4)
AutoNDA by SimpleDocs
Constraints on the Experimenters Use. Note: Section 6.1 has been already presented in section 3.1
Sample 1

Related to Constraints on the Experimenters Use

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

  • Exception Where Databases Contain Sufficient Information A Reporting Financial Institution is not required to perform the paper record search described in subparagraph D.2. of this section if the Reporting Financial Institution’s electronically searchable information includes the following:

  • Implementation of and Reporting on the Project A. The Grantee shall implement and complete the Project in accordance with Exhibit A and with the plans and specifications contained in its Grant Application, which is on file with the State and is incorporated by reference. Modification of the Project shall require prior written approval of the State.

  • Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

  • GEOGRAPHIC AREA AND SECTOR SPECIFIC ALLOWANCES, CONDITIONS AND EXCEPTIONS The following allowances and conditions shall apply where relevant: Where the company does work which falls under the following headings, the company agrees to pay and observe the relevant respective conditions and/or exceptions set out below in each case.

  • Erosion and Sediment Control The Contractor shall install and maintain erosion and sediment control devices to prevent adjacent streets, storm drains and property from accumulations of soil, sediment, or dust which result from his work. Devices installed to control sediment and prevent erosion shall comply with the requirements of the Georgia Tech Project Superintendent. The Contractor is responsible for monitoring downstream conditions throughout the construction period and clearing any debris, sediment, and dust caused by the progress of the Work. The Contractor shall inspect, maintain, and clear erosion and sediment control devices at least weekly unless otherwise directed by the Georgia Institute of Technology Construction Manager. At the conclusion of the Work, the Contractor shall remove all installed devices and restoring the site to the satisfaction of the Georgia Tech Construction Manager.

  • Development Phase contractual phase initiated with the approval of ANP for the Development Plan and which is extended during the Production Phase while investments in xxxxx, equipment, and facilities for the Production of Oil and Gas according to the Best Practices of the Oil Industry are required.

  • Collaboration on Compliance and Enforcement A Competent Authority will notify the other Competent Authority when the first-mentioned Competent Authority has reason to believe that an error may have led to incorrect or incomplete information reporting or there is non-compliance by a Reporting Financial Institution with the applicable reporting requirements and due diligence procedures consistent with the Common Reporting Standard. The notified Competent Authority will take all appropriate measures available under its domestic law to address the errors or non-compliance described in the notice.

  • Programming Phase 2.2.1.2. Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • DEMONSTRATIONS/SAMPLES 9.1 Bidders shall demonstrate the exact item(s) proposed within seven (7) calendar days from receipt of such request from the Owners.

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