Development Platform Clause Samples

Development Platform. Customer may utilize the Development Platform to create an Application to run on the Platform Services. Customer’s use of the Development Platform is governed by the terms of the Agreement subject to the restrictions set forth in Sections 4.2.1 to 4.2.2 below. Customer’s development of an Application must meet the best practices development guidelines set forth in the User Guide. Each Customer Application shall at all times materially conform to policies and best practices set forth in the User Guide. Prior to the deployment of any Customer Applications in a production or non-production environment of the Platform Services, Customer must conduct security and functional tests of each Customer Application and submit the results of such tests to BMC for review. BMC reserves the right to reject Customer’s deployment request of a Customer Application based on the results of Customer’s security and functional tests. Additionally, BMC reserves the right, during the term of the Agreement, to request Customer conduct additional security and functional tests and provide the results of said tests to BMC for review. Notwithstanding the foregoing, Customer must ensure that at all times Customer Applications are secure.
View SourceView Similar (7)
Development Platform. The GitLab development platform hosted at the French National Institute of Nuclear and Particle Physics - in2p3 (1) - was chosen and made available for the whole ESCAPE community. The idea of establishing this service and making it available was not to substitute the development platforms already used by each institution/group. It provides however a common place to gather the common developments, ideas, guidelines and templates for the community, as well as a development platform for new developments if needed by an institution/group and shows the potential integration of this development platform in the software lifecycle. Two main reasons led us to choose the self-hosted GitLab platform rather than GitHub (despite its popularity). First, GitHub's services are based on a closed source and are privately owned (the platform was bought by Microsoft in 2018), and second, the GitLab platform is hosted by one of the ESCAPE consortium members. Table 1: comparison of GitHub or GitLab as web services and a self-hosted GitLab solution Advantages Drawbacks GitHub or GitLab as a service - Free for open source - No setup - Integration with lot of services - Huge community - Data stored outside the E.U. - No control over the data & conditions of use - No control of accounts Self-hosted GitLab - Private projects - Control - Open source - Private projects - Control - Open source A GitLab group was created (2) where the developments under the ESCAPE2020 project WP3 are currently being collected. Within this group a 'template project' was created (3). The objectives of this template project are: 1. Provide the main guidelines for developing a new Open Source project (within the ESCAPE context), 2. Have a web platform where the new implementations discussed within the ESCAPE work packages can be tested, and 3. Show a 'real' use case development example. The project will be reused and customized as per the individual needs of ESCAPE partners. The idea behind a template is that any user can make a copy of it (clone or fork the repository) and start making changes / continue developing from the state of this work. The main components a repository must contain are:  An open source license file (the license and provenance model will be covered in D3.7);  Various README files with instructions/explanations of the different packages within the project and their usage. Within these files the contribution guidelines (instructions) are also explained in detail;  A setup.py file to...
View Source

Related to Development Platform

  • Development Program RWJPRI shall be [**] and have [**] in consultation with the JDAC, to select LICENSED COMPOUNDS which shall then be designated PRODUCTS for further DEVELOPMENT by RWJPRI and marketing by ORTHO and its AFFILIATES. RWJPRI shall provide KOSAN with written notice of its decision to select a LICENSED COMPOUND for DEVELOPMENT. Once a PRODUCT has been selected for further DEVELOPMENT, RWJPRI, with the advice of the JDAC, shall have the [**] right to develop the PRODUCT through STAGES O, I, II and III and shall have the [**] right to prepare and file, and shall be the owner of, all applications for MARKETING AUTHORIZATION throughout the world. During such DEVELOPMENT efforts, KOSAN will assist RWJPRI as may be mutually agreed, at RWJPRI's expense, in chemical development, formulation development, production of labeled material and production of sufficient quantities of material for STAGE O and initial STAGE I studies. RWJPRI shall exercise diligent efforts, commensurate with the efforts it would normally exercise for products with similar potential sales volume and consistent with its overall business strategy, in developing such PRODUCT in accordance with the DEVELOPMENT PLAN established by RWJPRI. In the course of such efforts RWJPRI shall, either directly or through an AFFILIATE or SUBLICENSEE to which the license shall have been extended, take appropriate steps including the following: (i) in consultation with the JDAC, select certain LICENSED COMPOUNDS for STAGE O DEVELOPMENT; and (ii) establish and maintain a program reasonably designed, funded and resourced to obtain information adequate to enable the preparation and filing with an appropriate and properly empowered national regulatory authority all necessary documentation, data and [**] CERTAIN INFORMATION IN THIS EXHIBIT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE COMMISSION. CONFIDENTIAL TREATMENT HAS BEEN REQUESTED WITH RESPECT TO THE OMITTED PORTIONS. other evidence required for IND non-rejection to commence and conduct human clinical trials of such PRODUCT. (iii) proceed following IND non-rejection to commence PHASE I, II, and III clinical trials, associated studies and such other work which RWJPRI reasonably deems to be required for subsequent inclusion in filings for MARKETING AUTHORIZATION; (iv) after such submissions are filed prosecute such submissions and file all reasonably necessary, reports and respond to all reasonable requests from the pertinent regulatory, authorities for information, data, samples, tests and the like.

  • Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Concession Area, including its abandonment.