Technology Providers Clause Samples

Technology Providers. In addition, notwithstanding Section 2.2 above, Supplier may contract with or use the services of technology service providers as part of the Supplier System (collectively, “Technology Providers”) used by Supplier to deliver the Services without Company’s prior approval except that Supplier shall not contract with or use the services of any Technology Provider that will (a) have access to [***], (b) [***] with any Company Customers/Members, or (c) be [***] without Company’s prior approval (such approval not to be unreasonably withheld, conditioned or delayed), including but not limited to any approval specified in the applicable Statement of Work or an amendment thereto in accordance with Section 13.14. For clarity, no Technology Providers shall be deemed to be “Subcontractors” for purposes of this Agreement. Supplier will ensure that all Technology Providers are bound by substantially similar obligations as Supplier under this Agreement, including obligations of each Technology Provider to provide protections equal to or greater than those set forth in this Agreement with regard to confidentiality, information protection and privacy, to the extent applicable. No use of any Technology Providers will release Supplier for its responsibility for its obligations under this Agreement. Upon request, Supplier will promptly provide Company with a written report identifying all Technology Providers that (a) have access to [***], (b) [***] with any Company Members/Customers, or (c) will be [***]. In the event that, following the effective date of this Agreement, (i) Supplier desires to change its Technology Provider that serves as its hosting provider, (ii) Supplier desires to add or change any other Technology Provider that can access [***], [***] with any Company Members/Customers, or will be [***], or (iii) there is a material change to the services provided by any previously disclosed Technology Provider that can access [***], [***] with any Company Members/Customers, or be [***], Supplier will provide [***] months’ advance notice to Company, unless an emergency or other unplanned event, such as a force majeure event, security breach, denial of service, having attack or other event beyond the reasonable control of Suppler (“Unplanned Event”) makes such advance notice impractical in Supplier’s reasonable discretion. For Technology Providers that cannot access [***], do not [***] with Company Members/Customers and will not be [***], Supplier shall provide Company ...

Technology Providers. It is important to note that Europeana does not directly list Collection Management System vendors as stakeholders. They might be inferred in the category technology organisations, whose stake in Europeana includes technology developments and knowledge exchange. Within Europeana Inside CMS vendors take on a more prominent role than is usually the case in descriptions of the Europeana landscape and they will have to be included separately in the value network. Technology is often implicitly deemed to be a part of the role of content providers and aggregators, as is clear by the explicit mention of developments in technology in the description of e.g. the cultural institutions stakeholder group (▇▇▇▇▇▇▇, ▇▇▇▇▇ & ▇▇▇▇▇▇▇▇, 2012, p. 18). Europeana Inside and its ECK can potentially strengthen the link from content providers to Europeana through the CMS vendors, who will hence get a more prominent role in Europeana’s value network. An important aim of this, as described in the project’s Description of Work (DoW), is to reach the vendors’ broader user-base, including institutions that lack in-house technological expertise to correctly provide metadata to Europeana. For instance, the ECK will facilitate mapping to the most up to date Europeana metadata models in a manner directly linked to the institutions’ software environments. From that perspective, there are two main scenarios’ that should be taken into account: • From a technical standpoint, the aggregator can be considered technical (and organisational) stakeholder. It is the stakeholder that supports the content provider to contribute to Europeana. If the content provider wants the CMS vendor can be involved by supporting them to deliver the content to the aggregator. The vendors know the local situation; they can for example export the metadata from the CMS to a standard metadata format. • The vendor and the ECK can take over some of the roles of an aggregator, for instance for content providers that are not yet part of that aggregation landscape. However it is useful to stress that the project should not lose sight of providing added value for aggregators as an important stakeholder category either. Technical facilitation of the mapping process will also alleviate the workload of many aggregators and increase efficiency to enable them to focus on other essential tasks or aggregate content from a higher number of providers than was previously possible. The ECK can bring added value both to aggregator scen...

Technology Providers. Resident also acknowledges that the communications providers supplying the Technology Package amenities are independent contractors, which Owner may terminate or change in Owner’s sole discretion, that the communications providers are responsible for all repairs or service, and that the Owner makes no representations or warranties with respect to any service, repair or warranty of any communications provider.

Technology Providers. Any identified SUSI member could establish third party cooperation with technology providers (e.g. software manufacturers). Those providers could be eligible Parties, proving they meet the conditions set forth in this MoC. These manufacturers can join the SUSI if they demonstrate their ability to connect to the system via the USP of their choice. This connectivity should be native to the Ground Control Station and not achieved by means of third parties apps or any other third party plug-in that is not fully integrated with the flight control software.