Foreground component Sample Clauses

Foreground component. ‌ The main outcome of T4.4 is the MIDIH d2A: data driven Analytics Platform (cf. Figure 7) which represents new generation of data analytics platforms which are oriented towards understanding the behaviour of the subjected industrial system/process (applying exploratory analytics on past data for getting so called process understanding) in order to enable continuous process improvement. We argue that “traditional” data analytics approaches are primarily focusing on “data understanding”, i.e. extracting the value from data for resolving a particular problem (e.g. predictive maintenance) Therefore, MIDIH d2A Platform enables creation of data-driven behavioural models of industrial systems, derived from past data using advanced data analytics. Such a model can be used for monitoring the real-time operation of the system and supporting quality control (like anomaly detection) and process improvement tasks. Here we will briefly describe each of the components’ roles and their interactions within the system: • Adapters These components are responsible for retrieving and parsing raw input files from clients and storing the resulting instance in the Storage. • Storage As a storage we use Xxxxxxxxx that is a distributed scalable non-relational database for managing large amounts of loosely-structured data. • Data Analytics Different analytics tasks can be performed whereas clustering is most suitable for the learning of the behavioural models. As the result of the clustering procedure models (which contain cluster information) are generated. Clusters can be used to analyze existing patterns in the data, while the model can be used in real-time, for real-time anomaly detection. The clustering procedure is performed periodically, and new models are generated, and the newest model is used for anomaly detection. • Real-time Monitoring This module classifies new instances based on previously generated (newest) model. The goal is to understand real time behaviour of the system,
Sample 1
AutoNDA by SimpleDocs

Related to Foreground component

  • 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 Regarding Foreground, EC-GA Article II.26. - Article II.29. shall apply with the following additions:

  • Foreground IP This subparagraph d. shall not apply to unmodified commercial off‐the‐shelf goods. If Services or goods are developed, modified or redesigned pursuant to this Contract then the paragraphs below apply.

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

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

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

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

  • RE-WEIGHING PRODUCT Deliveries are subject to re- weighing at the point of destination by the Authorized User. If shrinkage occurs which exceeds that normally allowable in the trade, the Authorized User shall have the option to require delivery of the difference in quantity or to reduce the payment accordingly. Such option shall be exercised in writing by the Authorized User.

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