Common use of Simple vs Clause in Contracts

Simple vs. complex Acknowledged Incidents. In order to provide adequate technical support, ISB distinguishes simple from complex Acknowledged Incidents. Simple Acknowledged Incidents can be resolved by ISB within a relatively short time period as from the expiration of the Acknowledgement Time, using its existing resources such as [book “iText in action”, existing code samples, API documentation, the operating specifications in the then-current documentation for the Software or Add-On(s)]. Complex Acknowledged Incidents cannot be resolved through ISB’s existing resources, require more time and more elaborate technical support.

Appears in 4 contracts

Samples: License Agreement, License Agreement, License Agreement

AutoNDA by SimpleDocs

Simple vs. complex Acknowledged Incidents. In order to provide adequate technical support, ISB ISC distinguishes simple from complex Acknowledged Incidents. Simple Acknowledged Incidents can be resolved by ISB ISC within a relatively short time period as from the expiration of the Acknowledgement Time, using its existing resources such as [book “iText in action”, existing code samples, API documentation, the operating specifications in the then-current documentation for the Software or Add-On(s)]. Complex Acknowledged Incidents cannot be resolved through ISBISC’s existing resources, require more time and more elaborate technical support.

Appears in 3 contracts

Samples: License Agreement, License Agreement, License Agreement

Simple vs. complex Complex Acknowledged Incidents. In order to To provide adequate technical supportappropriate Technical Support, ISB distinguishes simple from complex Acknowledged Incidents. Simple Acknowledged Incidents can be resolved by ISB within a relatively short time period as from the expiration of the Acknowledgement Time, using its existing resources such as [book "iText in action", existing code samples, API documentation, the operating specifications in the then-current documentation applicable Documentation for the Software or Add-On(s)]Software. Complex Acknowledged Incidents cannot be resolved through ISB’s 's existing resources, require more time and more elaborate technical supportTechnical Support.

Appears in 2 contracts

Samples: itextpdf.com, itextpdf.com

Simple vs. complex Acknowledged Incidents. In order to provide adequate technical support, ISB ISC distinguishes simple from complex Acknowledged Incidents. Simple Acknowledged Incidents can basically be resolved by ISB ISC within a relatively short time period as from the expiration of the Acknowledgement Time, using its existing resources such as [book “iText in action”, existing code samples, API documentation, the operating specifications in the then-current documentation for the Software or Add-On(s)Software]. Complex Acknowledged Incidents cannot be resolved through ISBISC’s existing resources, require more time and more elaborate technical support.

Appears in 1 contract

Samples: Support and Maintenance Agreement for Itext and Itextsharp

AutoNDA by SimpleDocs

Simple vs. complex Complex Acknowledged Incidents. In order to To provide adequate technical supportappropriate Technical Support, ISB ISC distinguishes simple from complex Acknowledged Incidents. Simple Acknowledged Incidents can be resolved by ISB ISC within a relatively short time period as from the expiration of the Acknowledgement Time, using its existing resources such as [book "iText in action", existing code samples, API documentation, the operating specifications in the then-current documentation applicable Documentation for the Software or Add-On(s)]Software. Complex Acknowledged Incidents cannot be resolved through ISB’s ISC's existing resources, require more time and more elaborate technical supportTechnical Support.

Appears in 1 contract

Samples: itextpdf.com

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