We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Foreground components Sample Clauses

Foreground components. ‌ The MIDIH Collaboration Platform implementation is based on different Open Source components, which need to be integrated and harmonised. For granting a unique access point, the IdM component has been used and customized in order to fulfil the following two main requirements: • sharing and aligning user information between OPENNESS and IDM; • defining an optimized GUI ENGINEERING has integrated, using the APIs provided by IDM, the secure login functionality in the MIDIH Collaborative Platform. With simple steps OPENNESS (OPNS) admin activates and configures the correct integration with FIWARE IdM in Control Panel, setting up client ID, client Secret, Oauth autentication Url and other parameters. In particular: 1. A new user is created in OPNS platform (or user signs-in through OPNS) with its default role; 2. OPNS propagates the user to the IdM user base through IdM open APIs; 3. IdM registers a new user on internal DB for accesses in all the registered applications and specifying default application roles when managed by IdM. OPNS represents the master for information, supports the collaboration among the different stakeholders of a DIH enabling the creation of User Generated Contents, while, on the other side, KeyRock provides a bridge between IdM system at connectivity-level and application- level and authorizing foreign services to access personal data stored in a secure environment. A custom GUI has been developed, in order to make it easier for users to login and the new theme has been integrated within the IDM.
Foreground components. ‌ The main contribution is the set up and configuration provided to create a common, reliable and valuable platform starting from separated microservices. The data-processing (Apache) pipeline and the identification of the most suitable components for each one of the steps inside this pipeline is the main contribution. It will allow MIDIH's cross- border industrial experiments to develop an end-to-end solution for their complex industry cases.
Foreground components. ‌ No specific developments have been realized in the scope of the MIDIH project.
Foreground components. ‌ The MIDIH FI-MIND bridge is aligned with the Smart Industry DAta Model (XXXXX) enabling the integration of the FIWARE cloud with the MindSphere ecosystem. The bridge converts NGSI information described in supported data models in the MindSphere Data Model using MindSphere concepts. The FI-MIND gathers data exposing APIs for: • Receiving NGSI data described with supported data models from a generic external component. • Processing Orion Context Broker notifications for data collecting. Further details are described in the attached factsheet in Annex F.
Foreground components. ‌ The final aim of any collaborative platform is to support knowledge sharing in a multi-actor scenario. To this extend, the developed MIDIH Collaboration Platform involves primitives for human socio-business main activities and collaboration, including idea management, open innovation and cross-enterprise social networks. In particular the DIHIWARE Collaboration Platform aims to realize a one-stop-shop for industrial partners to access technology, knowledge and market and to enable collaborative processes. As further described in D3.1 – “Specification and Design of DIH one-stop-shop Marketplace 1”, the main services that will be offered can be divided into two main categories: the “Access to” services will enable users gather information about skills, technological and business matters (Competencies, Technology, Industrial Experiments, Knowledge, Market), while the “Collaborate with” services will enable dynamic interactions and collaborative creative 1 xxxx://xxx.xxxxxxx.xxx/ processes among users (Open Innovation and Social Networking). These services will be complemented by cross functionalities supporting the general mode of operation, such as Searching Functionalities, Multi-lingual support, Guide for content creation, Workflow monitoring and support. The services portfolio offered by the MIDIH ecosystem will be refined during the project in order to provide additional features. For the first platform release, the attention has been focused on the following subset of functionalities: collection of experimental and didactic facilities, workflow monitoring and support, guide for content creation, multilingual support, collection of latest news, KPIs and statistics overview, funding through private investors. A particularly interesting new MIDIH-specific developments, already presented in the first release of the Platform, is the integration of services intended to monitor and support workflows and business processes: modelling and execution of B2B workflows can be talked to constantly monitor the interaction between users, in order to boost the platform adoption and business achievement by partners. On top of this framework, the definition of KPIs will make it possible to measure and assess relevant parameters, i.e. number of visits, percentage of visits concluded with a business etc.

Related to Foreground components

  • Third Party Components The Products and Services may contain third party components (including open source software) subject to separate license agreements. To the limited extent a third party license expressly supersedes this XXXX, such third party license governs Customer’s use of that third party component.

  • Foreground IP This subparagraph d. shall not apply to unmodified commercial off‐the‐shelf Goods. If Goods are developed, modified or redesigned pursuant to this Order, then the paragraphs below apply. i. All Foreground IP shall be the exclusive property of Buyer except as set forth in subparagraph (iv) below. ii. Seller hereby irrevocably assigns to Buyer all right, title and interest in the Foreground IP for no additional charge. Seller shall protect Foreground IP as Proprietary Information and Materials under this Contract and shall mark documents or portions of documents containing Foreground IP as “ITT Proprietary” information or as otherwise directed by Xxxxx in writing. iii. Seller shall, within two (2) months after conception or first actual reduction to practice of any invention and prior to Contract completion, disclose in writing to Buyer all inventions assigned hereunder, whether or not patentable, in sufficient technical detail to clearly convey the invention to one skilled in the art to which the invention pertains. Seller shall promptly execute all written instruments, and assist as Buyer reasonably directs in order to file, acquire, prosecute, maintain, enforce and assign Buyer’s Foreground IP rights. If Seller does not or cannot execute instruments or assist Xxxxx as described above, Seller hereby irrevocably appoints Xxxxx and any of Buyer’s officers and agents as Xxxxxx’s attorney in fact to act on Xxxxxx’s behalf and instead of Seller, with the same legal force and effect as if executed by Xxxxxx, with respect to executing any such written instruments. iv. Subparagraphs ii. and iii. above shall not apply to any Foreground IP to the extent that the development of such Foreground IP was performed with funding received by Buyer under a U.S. Government procurement.

  • SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work. 4.12.2 Product Data are illustrations, standard schedules, performance charts, instructions, brochures, diagrams and other information furnished by the Contractor to illustrate a material, product or system for some portion of the Work. 4.12.3 Samples are physical examples which illustrate materials, equipment or workmanship and establish standards by which the Work will be judged. 4.12.4 The Contractor shall review, approve and submit, with reasonable promptness and in such sequence as to cause no delay in the Work or in the work of the State or any separate contractor, all Shop Drawings, Product Data and Samples required by the Contract Documents. 4.12.5 By approving and submitting Shop Drawings, Product Data and Samples, the Contractor represents that he / she has determined and verified all materials, field measurements, and field construction criteria related thereto, or will do so, and that he / she has checked and coordinated the information contained within such submittals with the requirements of the Work and of the Contract Documents. 4.12.6 The Contractor shall not be relieved of responsibility for any deviation from the requirements of the Contract Documents by the Architect's approval of Shop Drawings, Product Data or Samples under Subparagraph 2.2.7 of these General Conditions unless the Contractor has specifically informed the Architect and the State in writing of such deviation at the time of sub- mission and the Architect and the State has given written approval to the specific deviation. The Contractor shall not be relieved from responsibility for errors or omissions in the Shop Drawings, Product Data or Samples by the Architect's approval thereof. 4.12.7 The Contractor shall direct specific attention, in writing or on resubmitted Shop Drawings, Product Data or Samples, to revisions other than those requested by the Architect on previous submittals. 4.12.8 No portion of the Work requiring submission of a Shop Drawing, Product Data or Sample shall be commenced until the submittal has been approved by the Architect as provided in Subparagraph 2.2.7 of these General Conditions. All such portions of the Work shall be in accordance with approved submittals.

  • OPEN SOURCE COMPONENTS The DS Offerings may include open source components. Whenever notices (such as acknowledgment, copies of licenses or attribution notice) are required by the original licensor, such notices are included in the Documentation of the DS Offerings. Moreover, some open source components may not be distributed and licensed under the terms of the Agreement but under the terms of their original licenses as set forth in the Documentation of the DS Offerings themselves. Source code for open source software components is available upon request. Except for components mentioned in the section EXCLUSIONS below, the warranty and indemnification provided by DS under the Agreement apply to all open source software components and shall be provided by DS and not by the original licensor, but only for the use of the DS Offerings that is in compliance with the terms of the Agreement, and in conjunction with the DS Offerings. The original licensors of said open source software components provide them on an “as is” basis and without any liability whatsoever to Customer.

  • Manufacturing Rights (a) If QED fails to supply Product ordered by ViewRay in accordance with the terms of this Agreement regarding the quantity or quality of Products supplied to ViewRay, then QED shall within fifteen (15) Business Days of said failure present ViewRay with a plan to remedy the problem and shall use Commercially Reasonable Efforts to execute such plan and remedy the problem or QED shall secure an alternative source of supply within a reasonable time at no additional cost to ViewRay. Any such alternative source of supply shall be on terms substantially identical with the terms of this Agreement. If QED is unable to provide a plan to remedy the problem or secure an alternative source of supply within [***] after its initial failure to supply, then QED shall consult with ViewRay and the parties shall work together to remedy the problem. If QED is unable to remedy the supply problem after [***] (or longer as agreed in writing by the parties), commencing with the date upon which such failure to supply began, then ViewRay may at its option, and upon notice to QED, manufacture the Products itself or through a third party in accordance with the provisions of Section 3.10(b). [***] Certain information in this document has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. (b) If ViewRay notifies QED pursuant to Section 3.10(a), above, that ViewRay will manufacture the Products itself or through a third party, QED shall (i) deliver to ViewRay within thirty (30) days media embodying or disclosing all Program technology and Program proprietary or intellectual property rights necessary to enable ViewRay or its designee to manufacture Products conforming with the Specifications; and (ii) provide ViewRay or its designee, upon request, with reasonable assistance in establishing a back-up manufacturing line. ViewRay shall require any third party ViewRay designates to manufacture Products pursuant to this Section 3.10, to agree in writing to observe the terms of this Agreement relating to confidentiality and the manufacture of Products. Notwithstanding any provision of this Section 3.10 to the contrary, in no case shall QED be required to pay ViewRay in respect of any Products purchased by ViewRay from a third party operating a back-up manufacturing line established pursuant to this Section 3.10 or manufactured by ViewRay or its Affiliates pursuant to this Section 3.10.

  • Background Technology List here prior contracts to assign Inventions that are now in existence between any other person or entity and you.

  • Licensed Technology (a) LICENSOR is not aware of any interference, infringement, misappropriation, or other conflict with any intellectual property rights of third parties, and LICENSOR has never received any charge, complaint, claim, demand, or notice alleging any such interference, infringement, misappropriation, or violation (including any claim that LICENSOR must license or refrain from using any intellectual property rights of any third party). To the knowledge of LICENSOR, no third party has interfered with, infringed upon, misappropriated, or otherwise come into conflict with any of the LICENSED TECHNOLOGY. (b) Exhibit A identifies each patent or registration which has been issued to LICENSOR with respect to any of the LICENSED TECHNOLOGY and identifies each pending patent application or application for registration which LICENSOR has made with respect to any of the LICENSED TECHNOLOGY. LICENSEE acknowledges that LICENSOR has previously made available to LICENSEE correct and complete copies of all such patents, registrations and applications (as amended to-date) in LICENSOR’s possession and has made available to LICENSEE correct and complete copies of all other written documentation in LICENSOR’s possession evidencing ownership and prosecution (if applicable) of each such item. (c) Exhibit A identifies each item of LICENSED TECHNOLOGY that is assigned to LICENSOR or that LICENSOR uses pursuant to license, sublicense, agreement, or permission. LICENSOR has made available to LICENSEE correct and complete copies of all such licenses, sublicenses, agreements, patent prosecution files and permissions (as amended to-date) in LICENSOR’s possession. With respect to each item of LICENSED TECHNOLOGY required to be identified in Exhibit A and to the knowledge of LICENSOR: (i) the license, sublicense, agreement, or permission covering the item is legal, valid, binding, enforceable, and in full force and effect; (ii) the license, sublicense, agreement, or permission will continue to be legal, valid, binding, enforceable, and in full force and effect on identical terms following the consummation of the transactions contemplated hereby; (iii) no Party to the license, sublicense, agreement, or permission is in breach or default, and no event has occurred which with notice or lapse of time would constitute a breach or default or permit termination, modification, or acceleration thereunder; (iv) no party to the license, sublicense, agreement, or permission has repudiated any provision thereof; (v) the underlying item of LICENSED TECHNOLOGY is not subject to any outstanding lien or encumbrance, injunction, judgment, order, decree, ruling, or charge; (vi) no action, suit, proceeding, hearing, investigation, charge, complaint, claim, or demand is pending or is threatened which challenges the legality, validity, or enforceability of the underlying item of LICENSED TECHNOLOGY; and (vii) except as provided in Exhibit A, LICENSOR has not granted any license or similar right to the LICENSED TECHNOLOGY within the GENERAL FIELD or PARTHENOGENESIS FIELD.

  • Product Testing No later than [***] prior to a scheduled Delivery ARIAD US shall send to ARIAD SWISSCO the Delivery Documents for review. Following such review, unless within [***] of receipt of the Delivery Documents ARIAD SWISSCO gives written notice of rejection of the Product to be delivered, stating the reasons for such rejection, the Delivery shall proceed, and both Parties shall organize the same. Upon arrival at ARIAD SWISSCO nominated site it shall visually inspect the shipment of the Product to identify any damage to the external packaging. ARIAD SWISSCO may reject any shipment (or portion thereof) of the Product that is damaged by providing to ARIAD US reasonable evidence of damage within [***] after Delivery of such Product. If ARIAD SWISSCO does not so reject any shipment (or portion thereof) of the Product within [***] of Delivery of such Product, ARIAD SWISSCO shall be deemed to have accepted such shipment of the Product; provided, however, that in the case of the Product having any Latent Defect, ARIAD SWISSCO shall notify ARIAD US promptly once it becomes aware that a Product contains a Latent Defect and subsequently may reject such Product by giving written notice to ARIAD US of ARIAD SWISSCO’s rejection of such Product and shipping a representative sample of such Product or other evidence of Non-Conformance to ARIAD US within [***] after becoming aware of such Latent Defect, which notice shall include a description of the Latent Defect.

  • Manufacturing Technology Transfer Except as the Committee ------------ --------------------------------- may otherwise agree in writing, in order to effectuate an orderly transition of the uninterrupted availability of Product to LILLY for purposes contemplated under this Agreement, MEGABIOS, at least ninety (90) days prior to completion of the Project or completion of Phase I Clinical Trials, whichever is earlier, shall transfer to LILLY all information and instructions concerning the manufacturing process and related matters in MEGABIOS' possession which may be necessary for LILLY to manufacture Product (including information regarding obtaining necessary Lipids related thereto) for clinical trials and commercialization as contemplated hereunder including, but not limited to, analytical and manufacturing methods. MEGABIOS shall also provide assistance (in the form of consultation) to LILLY with respect to manufacturing matters for a period of [ * ] months after completion of the initial transfer of information and instructions as provided below. Such transfer and assistance by MEGABIOS will be referred to herein as the "Manufacturing Transfer." All such information, methods and instructions transferred to LILLY under this Section 4.3 shall be referred to herein as the "Manufacturing Information," and shall be maintained in confidence by LILLY pursuant to Section 7.1, except that LILLY's obligation to maintain in confidence such Manufacturing Information shall survive for ten (10) years following expiration or termination of this Agreement. LILLY agrees that it will use all such transferred Manufacturing Information only for the manufacture of the Products and shall not disclose or transfer such Manufacturing Information to any third party manufacturer except as provided in Section 2.10. MEGABIOS shall provide, and bear its costs for, up to [ * ] FTEs for a period of up to [ * ] months [ * ] in aggregate) to accomplish the Manufacturing Transfer. Such FTEs, at LILLY's request, shall include visits to LILLY's facilities by MEGABIOS personnel including up to [ * ] from MEGABIOS' head of manufacturing. MEGABIOS shall furnish any additional reasonable assistance beyond the assistance described above regarding manufacturing matters that LILLY may request and that MEGABIOS is able to provide, for up to [ * ] after the initial transfer of Manufacturing Information, providing that LILLY [ * ] incurred with respect to such additional assistance.

  • SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.