Workarounds Sample Clauses
The Workarounds clause defines the procedures and permissions for implementing temporary or alternative solutions when a problem or defect arises in a product or service. Typically, this clause outlines the conditions under which a workaround may be used, such as when a permanent fix is not immediately available, and may specify responsibilities for documenting and communicating the workaround to relevant parties. Its core practical function is to ensure continuity of operations and minimize disruption while a long-term solution is being developed, thereby managing risk and maintaining service levels.
Workarounds. A defect can also be remedied by Fraunhofer by providing information on how to remedy or circumvent the consequences of the defect (known as a workaround), provided that any impaired usage that remains as a result is reasonable for the corporate user.
Workarounds. NP shall attempt to provide Workarounds wherever appropriate in response to Escalations until a Modification can be created. Appropriate documentation/integration notes are required. Information regarding Workarounds shall be submitted by NP to SunConnect.
Workarounds. If nexxtsoft offers the customer a new program version or program parts in order to avoid or eliminate defects or in order to avoid the malfunction of other programs, the system or equipment, the customer is obligated to adopt and install these on his hardware in accordance with nexxtsoft’s installation guidelines – if possible and as soon as reasonable for him to do so. Whether the adoption and installation of the workaround is reasonable for the customer, depends on if the customer can use the software for the contractual purpose accordingly and if he will incur costs through the implementation of the workaround.
Workarounds. Due to the nature of the HIPAA and HITECH requirements, as your Business Associate, LuxSci has a great deal of responsibility in ensuring that your use of its services is such that ePHI is safeguarded. As a result, LuxSci imposes the restrictions of Section 2. There are various ways to increase the usability of the system in the face of these necessary security requirements. Identified below are our recommendations. Customer is not required to implement any of the recommendations presented below; they are all optional. Failure by Customer to implement any of the recommendations identified in this Section 3 does not void or negate any obligation or responsibility of LuxSci or Customer under this or the Business Associate Agreement.
3.1 TLS-only Secure Delivery: (Enabled by default) SecureLine permits enabling TLS-only delivery as an option for outbound email encryption. Recipient domains hosted by LuxSci or whose email servers support a sufficiently secure version of SMTP over TLS, can be delivered to "normally" without the required use of more complex outbound encryption mechanisms (i.e. PGP, S/MIME, or Escrow). I.e., all messages to such recipients would be sent via "regular email"; however, that regular email would be delivered over a secure channel either locally
Workarounds. Relevant workarounds delivered as part of prior year subscriptions will be carried over from Customer’s existing ▇▇▇▇. The spirit of the workarounds will be preserved, but execution of the workarounds may vary depending on how the specific edits apply to ▇▇▇▇.
Workarounds. Use many non-participant data sources, they were there
Workarounds. To the extent that Licensor demonstrates that access to certain areas of its sites or facilities would constitute a breach of its confidentiality undertakings to its other collaborators, Licensor may (instead of providing access to such certain areas) put in place reasonable workarounds to enable Novartis or its designated auditor to have access to resources and information reasonably required in order to carry out the audit. Licensor shall not refuse to provide access to a Record based on its confidentiality status.
Workarounds. Provide Workarounds as appropriate. If the Service Provider implements a Workaround to Resolve an Incident it will, promptly following implementation of the Workaround, implement a Final Resolution for the Incident.