Active Development Sample Clauses
Active Development. Notwithstanding anything to the contrary, including Section 3.5.4, if Lilly is researching, developing, manufacturing, commercializing or otherwise exploiting any compound or product comprising an AOC that is Directed Against a Collaboration Target during the Term and Lilly is not Actively Developing any Compound or Product that is Directed Against such Collaboration Target, then such Collaboration Target will be deemed a Discontinued Target and the terms of Section 4.7 will apply; provided, however, that the foregoing shall cease to apply following the First Commercial Sale of a Product Directed Against such Collaboration Target. “Actively Developing” means that Lilly or any of its Affiliates or Sublicensees are engaging in or have engaged within the preceding [* * *] in one or more of the following activities for a Compound or Product: pre-clinical research and development; formulation development; study/protocol design activity; protocol preparation; vendor selection; awaiting protocol approval from the applicable institutional review board or Regulatory Authority; patient recruitment; patient enrollment; patient treatment, evaluation and monitoring in Clinical Trials; data collection and analysis; auditing of vendors, clinical sites, manufacturing facilities and storage facilities; report writing for any pre-clinical or clinical study or manufacturing activity; communicating or negotiating with Regulatory Authorities; regulatory file(s) being drafted or pending (including preparation of one or more applications for Regulatory Approval); awaiting a response from the applicable Regulatory Authorities (including with respect to pending applications for Regulatory Approval); pricing or reimbursement approvals pending; manufacturing investment work; packaging development; manufacturing scale-up and validation; awaiting go/no go decision from a formal research and development committee within Lilly or such Affiliate or Sublicensee to initiate or continue any of the preceding activities; negotiating contracts with Third Parties to implement any of the foregoing activities (e.g., clinical trial agreements, services agreements, manufacturing and supply agreements); publication writing; seeking licensing partners; endeavoring to overcome circumstances outside of Lilly’s or its Affiliate’s, or Sublicensee’s reasonable control (including supply, regulatory and other issues) that impair the ability of Lilly or its Affiliate or Sublicensee to perform any of the fore...
Active Development. Notwithstanding anything herein to the contrary, Celgene’s exclusivity (including any […***…]), rights and licenses will expire with respect to a Collaboration Sequence Pair if Celgene ceases active research and development of the Antibody generated from and incorporating such Collaboration Sequence Pair or Product(s) incorporating such Antibody.
Active Development. DS’ exclusivity, rights and licenses under the Commercial License will automatically expire if DS ceases all research and development of the Antibodies and Products for a period of […***…].
Active Development. The ARC model checker was last updated in June 2013. The report on the ex- tension to generate minimal cuts was published in October 2011. As there is commonality between the authors of this report and the ARC tool developers it is assumed that there is continued support for these features in the ARC tool. The input is an AltaRica model, which is assumed to be a textual file with a .alt extension. The file specifies components as nodes which have “containers” for defining states, events, transitions and subnodes. The textual input format for the model checker can generated by the Artisan Studio API to translate from a SysML model. 5▇▇▇▇▇://▇▇▇▇▇▇▇▇.▇▇▇▇▇.▇▇/forge/ 6▇▇▇▇▇://▇▇▇▇▇▇▇▇.▇▇▇▇▇.▇▇/forge/projects/arc AltaRica models are more focused on states and state transitions than hierarchi- cal descriptions, so state machines (or possibly activity diagrams) appear to be the closest SysML diagrams to an AltaRica model. Whilst an AltaRica model is based on a labelled transition system (which should translate from SysML state machines relatively easily) there are features of the language that would need fur- ther investigation such as flows and synchronisation vectors. The fault modelling aspects also require “tags” (which could be modelled by stereotypes in SysML) to be added to the model. The analysis is aimed at systems with many states and to ensure scalability the results are limited to minimal cuts and minimal sequences. It is therefore not possible to obtain the complete fault tree or FMEA tables and quantitative analysis is not considered.
Active Development. The tool is being used in the MAENAD3 EU project and is actively supported. The latest version of the tool was released in October 20124. The tool may be executed from the command line and takes, as an input, an an- notated model in the form of an XML file. This file uses a schema file (written in XSD) to define the syntax required by HiP-HOPS. Documentation is available which describes the required XML syntax. The HiP-HOPS tool provided may be run within Matlab/Simulink, in which annotated system models may be de- fined. These models are, however, simply output as XML. Therefore HiP-HOPS is compatible with an external modelling tool. Given the XSD schema mentioned above, we may generate an XML file using an external modelling tool. Using the Artisan Studio API we may translate the model to an XML file. Alternatively, we could consider translating the underlying XMI file to the HiP-HOPS XML file, though this would require Artisan Studio to output profiled data to the XMI file. The format of HiP-HOPS input files appears straightforward to replicate given a SysML model. The system model aspect is simply a hierarchical description, with a system com- posed of components, linked by their ports. Each component may be further de- fined as a system. This architectural structure could be modelled in the internal block diagram (IBD) of SysML. The additional failure annotations may be pro- vided by a SysML profile. HiP-HOPS generates (synthesises) fault trees, given an annotated system model. These trees are created by combining the local failure data of system components and subsystems. The fault trees are analysed to first obtain minimal cut sets, and then used for quantitative analysis and the FMEA. The FMEA indicates the causes of system failures by individual component failures. 3▇▇▇▇://▇▇▇.▇▇▇▇▇▇.▇▇/ 4According to the last modified date of the executable file available on the website. Note that
Active Development. Zymeworks will have the right to terminate BeiGene’s licenses and rights under this Section 2.1 with respect to any BeiGene Sequence Pair if (a) BeiGene ceases to use such BeiGene Sequence Pair to research, develop and commercialize Licensed Antibodies and/or Products derived from such BeiGene Sequence Pair through the application of the Zymeworks Platform, (b) Zymeworks provides BeiGene with written notice and (c) BeiGene fails to resume its use of such BeiGene Sequence Pair to research, develop and commercialize Licensed Antibodies and/or Products derived from such BeiGene Sequence Pair through the application of the Zymeworks Platform on or before […***…] after its receipt of such written notice.21 21 Competitive Information – Commercially Sensitive Terms.
Active Development. ▇▇▇ will use commercially reasonable efforts (i) to conduct the research activities assigned to ▇▇▇ under the Research Program Plan; and (ii) to develop and launch Products.