Background components Sample Clauses

Background components. ‌ The MindSphere SDK for Java enables Java developers to work with the MindSphere IoT platform easily. It provides a Java client implementation for the RESTful MindSphere Platform APIs. The FI-MIND includes the MindSphere SDK for Java v1 in order to: • Authenticate the client (MindSphere credentials). • Create the Digital Twin on the MindSphere cloud, registering new assets (devices) and aspects (variables). • Send timeseries data for registering value updates coming from the Orion Context Broker.
Sample 1
AutoNDA by SimpleDocs
Background components. ‌ The FIWARE OPC UA Agent is based on the reference implementation of the FIWARE Backend Device Management Generic Enabler, IDAS3, delivered by Telefonica I+D. IDAS provides a collection of Agents – i.e., independent processes that are typically executed in the proximity of IoT devices and that are responsible for bridging a specific IoT protocol to the NGSI standard (e.g. the IDAS distribution includes off-the-shelf Agents for LwM2M and MQTT). To this end, IDAS links the NGSI southbound API of the FIWARE Orion Context Broker to the northbound API of the IoT application stack, by providing a software library (the IoT Agent Lib)) for developing custom Agents that may extend the bridging capabilities of IDAS to other protocols. On the south bound interface, another exploited background asset is the OPC-UA JavaScript Library: among all the components available in the Node.js platform, it is the most interesting, as it offers both a client component (used in the OPC-UA JavaScript Wrapper) and a server one, that can be used to send data from the IoT devices in the shop floor to the OPC-UA JavaScript Wrapper. 3 xxxxx://xxxxxxxxx-xxxxxx.xxxxxx.xxx/enablers/backend-device-management-idas
Sample 1
Background components. ‌ The MIDIH MindSphere Custom Agent is based on MASAI, which is an open source component based on FIWARE Generic Enablers that provides an infrastructure to support continuous data collection from IoT based resources and normally is installed at companies’ premises level. Its mission is to gather the data from the shop floor IoT devices and provide it to any Data Collector Platform or Framework. FIWARE exposes to developers Data Context elements or entities (JSON objects) with attributes and metadata with a uniform REST API, which allows MASAI to be an open source software stack aiming to bring Data-level interoperability to the complexity of standards and protocols in the world of IoT today. XXXXX is able to expose all IoT devices information and commands using the Data Context API (NGSI9/10 - Next Generation Service Interface) for communicating devices with NGSI brokers or any other piece that uses the NGSI protocol. Therefore, XXXXX is dedicated for the collection of data from the shop floor acting as a middleware between the IoT data producers in the shop floor and the data consumers, which can be external services. In addition, the open cloud platform from Siemens, MindSphere, is a powerful IoT operating system with data analytics and connectivity capabilities, tools for developers, applications, and services. It helps to evaluate and utilize the manufacturer’s data and to gain breakthrough insights. Driving the performance and optimization of their assets. MindSphere is a commercial platform which requires the payment of a license for its use.
Sample 1
Background components. ‌ The DIHIWARE Platform is grounded on two main Open Source pillars: Liferay and OPENNESS. In particular, Liferay1 has been selected since it is a widely used Open Source and state-of-the- art Content Management System. Liferay Portal is a free and open source enterprise portal software product written in Java. Liferay includes a built-in web content management system allowing users to build websites and portals as an assembly of themes, pages, portlets/gadgets and a common navigation. The second background component exploited to develop the MIDIH Collaboration Platform is OPENNESS2, an asset developed and managed by the ENGINGEERING R&D Department. This Open Source platform is able to support the collaboration among different stakeholders, such as DIH, competence centres, technology providers (SMEs), manufacturing industries (SMEs), business consultants, funding agencies, venture capitalists. In the scope of the MIDIH Collaboration Platform, the “Access to” and “Collaborate with” services defined in D3.1 – “Specification and Design of DIH one-stop-shop Marketplace 1” have been implemented by collaborative business processes supported by this specific IT tool. OPENNESS (OPEN Networked Enterprise Social Software) represents a platform fully developed using open source technologies, and leveraging principles related to Open Innovation, Collective Intelligence, Enterprise Social Software. The platform enables the development, integration and delivery of services and collaborative environments based on models of social networking and collective intelligence and provides in SaaS mode (Software- as-a-Service) features and services such as management and development of the community, knowledge management and collective experience and applications, enabling collaborative working and social analytics.
Sample 1
Background components. ‌ The FIWARE3 Catalogue provides an enhanced OpenStack-based cloud environment plus a rich set of open standard APIs and OSS components that enables to the full adoption of Future Internet technologies such as Internet of Things, Big Data Analytics, Service Marketplaces, Advanced multi-media, User Interaction, and Privacy and Security Management. It aims at the creation of a sustainable ecosystem of Cloud-ready generic components – aka Generic Enablers (GE) – that may be used as the foundational building blocks of Future Internet solutions in any area, effectively supporting the new wave of digitalization of EU industry and society. The Identity Management – KeyRock is the FIWARE Generic Enabler, that covers a number of aspects involving users' access to networks, services and applications, including secure and private authentication from users to devices, networks and services, authorization & trust management, user profile management, privacy-preserving disposition of personal data, Single 3 xxxxx://xxx.xxxxxx.xxx Sign-On (SSO) to service domains and Identity Federation towards applications. The Identity Manager is the central component that provides a bridge between IdM systems at connectivity-level and application-level. For end users, the IdM provides a convenient solution for registering with applications since it gives them a means to re-use attributes like address, email or others, thus allowing an easy and convenient management of profile information.
Sample 1
Background components. ‌ The functionality of the Marketplace module integrated into the MIDIH Collaboration Platform is implemented using the FIWARE/TMForum Business API Ecosystem GE4, which is the result of the collaboration between FIWARE and the TMForum. In this regard, the Business API Ecosystem GE is a joint component made up by integrating the FIWARE Business Framework with a set of standard APIs (and its reference implementations) provided by the TMForum in its TMF API ecosystem. Business API Ecosystem GE provides sellers the means for managing, publishing, and generating revenue of their products, apps, data, and services. The APIs of this component are designed to enable repeatable and flexible integration among operations and management systems, making it easier to create, build and operate complex innovative services.
Sample 1
Background components. ‌ The OPENNESS platform includes several search and retrieval features to help a user quickly find information, or just to browse through content, people, and teams. Universal Search manages interactive search by inserting filters on the search bar. The users can search for specific words by simply entering the search terms to see content containing all the specified words in any order. They can find resources by person, title and content, and benefit from suggestions shown in real-time in the search box when typing the query. Furthermore, it also shows a set of tips to enrich the query that take into account the user's activities in the community.
Sample 1
AutoNDA by SimpleDocs

Related to Background 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.

  • Background Screening VENDOR shall comply with all requirements of Sections 1012.32 and 1012.465, Florida Statutes, and all of its personnel who (1) are to be permitted access to school grounds when students are present, (2) will have direct contact with students, or (3) have access or control of school funds, will successfully complete the background screening required by the referenced statutes and meet the standards established by the statutes. This background screening will be conducted by SBBC in advance of VENDOR or its personnel providing any services under the conditions described in the previous sentence. VENDOR shall bear the cost of acquiring the background screening required by Section 1012.32, Florida Statutes, and any fee imposed by the Florida Department of Law Enforcement to maintain the fingerprints provided with respect to VENDOR and its personnel. The parties agree that the failure of VENDOR to perform any of the duties described in this section shall constitute a material breach of this Agreement entitling SBBC to terminate immediately with no further responsibilities or duties to perform under this Agreement. VENDOR agrees to indemnify and hold harmless SBBC, its officers and employees from any liability in the form of physical or mental injury, death or property damage resulting from VENDOR’s failure to comply with the requirements of this section or with Sections 1012.32 and 1012.465, Florida Statutes.

  • Background Data The Disclosing Party's Background Data, if any, will be identified in a separate technical document.

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

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

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

  • Background IP Each Party will own all right, title and interest in its Background IP.

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