Foreground components Sample Clauses

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. Figure 11 – FIWARE and MindSphere Data Models
Sample 1
AutoNDA by SimpleDocs
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.
Sample 1
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.
Sample 1
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 Figure 2 – OPENNESS - IDM Interaction 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:
Sample 1
Foreground components. ‌ No specific developments have been realized in the scope of the MIDIH project.
Sample 1

Related to Foreground components

  • Program Components Activities and services delivered under this Program Element align with Foundational Programs and Foundational Capabilities, as defined in Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf) as well as with public health accountability outcome and process metrics (if applicable) as follows:

  • 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.

  • Software Components At any time during the contract period of performance, the Government may require the Contractor to remedy any failure of the software to comply with the requirements of this contract. Support shall consist of correction of errors, provision of modifications, improvements, and other products the original manufacturer makes available to the Government without charge. The Government shall also be provided full documentation of changes and/or modifications to the software provided to meet the Government's requirements.

  • 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.

  • 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.

  • Product Technical Support & Maintenance Licensee shall have the option of electing the Product technical support and maintenance (“maintenance”) set forth in the Contract by giving written notice to Contractor any time during the Centralized Contract term. Maintenance term(s) and any renewal(s) thereof are independent of the expiration of the Centralized Contract term and will not automatically renew. Maintenance shall include, at a minimum, (i) the provision of error corrections, updates, revisions, fixes, upgrade and new releases to Licensee, and (ii) Help Desk assistance with locally accessible “800” or toll free, local telephone service, or alternatively on-line Help Desk accessibility. Contractor shall maintain the Products so as to provide Licensee with the ability to utilize the Products in accordance with the Product documentation without significant functional downtime to its ongoing business operations during the maintenance term. Authorized User shall not be required to purchase maintenance for use of Product, and may discontinue maintenance at the end of any current maintenance term upon notice to Contractor. In the event that Authorized User does not initially acquire or discontinues maintenance of licensed Product, it may, at any time thereafter, reinstate maintenance for Product without any additional penalties or other charges, by paying Contractor the amount which would have been due under the Contract for the period of time that such maintenance had lapsed, at then current NYS net maintenance rates.

  • Vendor Development Rights To the extent not inconsistent with Customer’s rights in the Work Product or as set forth herein, nothing in this Contract shall preclude Vendor from developing for itself, or for others, materials which are competitive with those produced as a result of the Services provided hereunder, provided that no Work Product is utilized, and no Intellectual Property Rights of Customer therein are infringed by such competitive materials. To the extent that Vendor wishes to use the Work Product, or acquire licensed rights in certain Intellectual Property Rights of Customer therein in order to offer competitive goods or services to third parties, Vendor and Customer agree to negotiate in good faith regarding an appropriate license and royalty agreement to allow for such.

  • For Product Development Projects and Project Demonstrations  Published documents, including date, title, and periodical name.  Estimated or actual energy and cost savings, and estimated statewide energy savings once market potential has been realized. Identify all assumptions used in the estimates.  Greenhouse gas and criteria emissions reductions.  Other non-energy benefits such as reliability, public safety, lower operational cost, environmental improvement, indoor environmental quality, and societal benefits.  Data on potential job creation, market potential, economic development, and increased state revenue as a result of the project.  A discussion of project product downloads from websites, and publications in technical journals.  A comparison of project expectations and performance. Discuss whether the goals and objectives of the Agreement have been met and what improvements are needed, if any.

  • Biological Samples If so specified in the Protocol, Institution and Principal Investigator may collect and provide to Sponsor or its designee Biological Samples (“Biological Samples”). 12.2.

  • 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.

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