| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
technical_support_agreement [2018/09/27 17:24]
rijk [Terms & Conditions] |
technical_support_agreement [2020/02/26 10:57] (current)
rijk [What is not] |
| ====== Technical Support Agreement ====== | ====== Technical Support Agreement ====== |
| |
| This agreement is between Datraverse B.V, [[Legal|legal guardian]] of the SavaPage Community, registered in The Netherlands with trade registration number 39068966, and //registered// SavaPage Community [[Roles|Members and Visitors]]. The agreement covers the Technical Support for the SavaPage Software as [[Software Packages|packaged]] and released by Datraverse. Community Support is a joint effort of Datraverse and //Community Partners//. | This agreement is between Datraverse B.V, [[Legal|legal steward]] of the SavaPage Community, registered in The Netherlands with trade registration number 39068966, and //registered// SavaPage Community [[Roles|Residents and Visitors]] (referred to as Member in general). The agreement covers the Technical Support for the SavaPage Software as [[Software Packages|packaged]] and released by Datraverse. Community Support is a joint effort of Datraverse and //Community Partners//. |
| | |
| ---- | |
| |
| ===== What is supported ===== | ===== What is supported ===== |
| |
| //Datraverse may suggest work-arounds or, where it is judged that there is a defect in the software, make alterations to the SavaPage software to address issues raised.// | //Datraverse may suggest work-arounds or, where it is judged that there is a defect in the software, make alterations to the SavaPage software to address issues raised.// |
| |
| ---- | |
| |
| ===== What is not ===== | ===== What is not ===== |
| * Integration with third party products, unless this integration is part of SavaPage. | * Integration with third party products, unless this integration is part of SavaPage. |
| * Disaster recovery. | * Disaster recovery. |
| * Any //operational// support scenario supported according to the [[https://wiki.datraverse.com/doku.php?id=services:operational:support-matrix|Datraverse Operational Support Matrix]]. | * Processes or services that are provisioned by the Member's IT staff to their own internal or external clients and used by themselves, to run themselves as a business. |
| |
| //These additional services can be provided though as [[Service Level Agreement|SLA Contract]] by Datraverse, or other Deployment Partners, on request.// | //These additional services can be provided though as [[Service Level Agreement|SLA Contract]] by Datraverse, or other Deployment Partners, on request.// |
| |
| ---- | |
| |
| ===== Fair use ===== | ===== Fair use ===== |
| |
| A fair usage policy applies to this agreement. When a Member or Visitor raises an excessive number of support requests, Datraverse has the right to reduce the level of support provided or will recommend that the Community Member or Visitor purchases training or consultancy services from a //Deployment Partner//. | A fair usage policy applies to this agreement. When a Resident or Visitor raises an excessive number of support requests, Datraverse has the right to reduce the level of support provided or will recommend that the Community Resident or Visitor purchases training or consultancy services from a //Deployment Partner//. |
| | |
| ---- | |
| |
| ===== Location ===== | ===== Location ===== |
| |
| Technical Support is available via the https://support.savapage.org site. Support is provided //remotely// in English or Dutch. If possible and needed, telephone or [[https://wiki.datraverse.com/doku.php?id=howto:vnc|screen sharing tools]] may be used. Deployment Partners in your region will be able to provide //on-site// support by separate SLA contracts. | Technical Support is available via the https://support.savapage.org site. Support is provided //remotely// in English or Dutch. If possible and needed, telephone or [[https://wiki.datraverse.com/doku.php?id=howto:vnc|screen sharing tools]] may be used. Deployment Partners in your region will be able to provide //on-site// support by separate SLA contracts. |
| |
| ---- | |
| |
| ===== Process ===== | ===== Process ===== |
| Please follow these steps when you want support for an issue: | Please follow these steps when you want support for an issue: |
| |
| - A //Member// should first consult his assigned Deployment or Integration Partner on any issue. Members who have Datraverse as Deployment Partner can directly proceed with the Step 3. | - A //Resident// should first consult his assigned Deployment or Integration Partner on any issue. Residents who have Datraverse as Deployment Partner can directly proceed with the Step 3. |
| - Deployment and Integration Partners provide Level 1 support and may resolve the issue right away. When Level 2 support is needed either the Partner or Member can open a support ticket via the https://support.savapage.org site. | - Deployment and Integration Partners provide Level 1 support and may resolve the issue right away. When Level 2 support is needed either the Partner or Resident can open a support ticket via the https://support.savapage.org site. |
| - When you "Open a New Ticket" you must first sign in with your community credentials. Partners and Members received their credentials when they joined the community. | - When you "Open a New Ticket" you must first sign in with your community credentials. Partners and Residents received their credentials when they joined the community. |
| - Visitors can obtain credentials by sending a request to **[[Join|join]]** for a restricted period. | - Visitors can obtain credentials by sending a request to **[[Join|join]]** for a restricted period. |
| - Issues from Members are handled with higher priority than those from Visitors. | - Issues from Residents are handled with higher priority than those from Visitors. |
| - Support requests will be assigned a ticket number that should be used on all related correspondence. | - Support requests will be assigned a ticket number that should be used on all related correspondence. |
| |
| //The Community Support Team aims to respond to a request within 24 hours.// | //The Community Support Team aims to respond to a request within 24 hours.// |
| |
| ---- | |
| |
| ===== Confidentiality ===== | ===== Confidentiality ===== |
| |
| //Neither Datraverse or the Community Member must make public or disclose any of this confidential information.// | //Neither Datraverse or the Community Member must make public or disclose any of this confidential information.// |
| |
| ---- | |
| |
| ===== Liability ===== | ===== Liability ===== |
| |
| The Community Member (referred to as Member) is responsible for the right exploitation of the software. Member is obliged to make backup copies of data and the software. In no event will Datraverse be liable to Member or to any third party for any special, incidental, punitive or consequential damages (including loss of use, data, business or profits) or for costs of procuring substitute services, arising out of or in connection with this agreement or the services or any work product provided by Datraverse, however caused and regardless of the theory of liability, even if Datraverse has been advised of the possibility of such damages. Datraverse total liability to Member, from all causes of action and all theories of liability, will be limited to and will not exceed the amounts paid to Datraverse by Member under the orders giving rise to any liability hereunder. | The Community Resident or Visitor (referred to as Member) is responsible for the right exploitation of the software. Member is obliged to make backup copies of data and the software. In no event will Datraverse be liable to Member or to any third party for any special, incidental, punitive or consequential damages (including loss of use, data, business or profits) or for costs of procuring substitute services, arising out of or in connection with this agreement or the services or any work product provided by Datraverse, however caused and regardless of the theory of liability, even if Datraverse has been advised of the possibility of such damages. Datraverse total liability to Member, from all causes of action and all theories of liability, will be limited to and will not exceed the amounts paid to Datraverse by Member under the orders giving rise to any liability hereunder. |
| | |
| ---- | |
| |
| ===== Terms & Conditions ===== | ===== Terms & Conditions ===== |
| Standard Terms and Conditions of Datraverse B.V. are applicable to this agreement as filed by ICT~Office with the Chamber of Commerce for the Central Netherlands under number 30174840. The conditions can be downloaded in PDF format as [[https://wiki.datraverse.com/doku.php?id=services:tac|English]] or [[https://wiki.datraverse.com/doku.php?id=services:tac-nl|Dutch]] version. | Standard Terms and Conditions of Datraverse B.V. are applicable to this agreement as filed by ICT~Office with the Chamber of Commerce for the Central Netherlands under number 30174840. The conditions can be downloaded in PDF format as [[https://wiki.datraverse.com/doku.php?id=services:tac|English]] or [[https://wiki.datraverse.com/doku.php?id=services:tac-nl|Dutch]] version. |
| |
| Nothing in this agreement is intended to replace the ICT~Office Terms and Conditions and the [[https://www.gnu.org/licenses/agpl.html|GNU AGPLv3 License]] that applies to the SavaPage Software. In case of conflicts the AGPL License and ICT~Office Terms and Conditions takes precedence (in that order). This agreement is between Datraverse and SavaPage Community Members and Visitors only. Other third parties may have separate arrangements with Members. These arrangements are excluded from this agreement. | Nothing in this agreement is intended to replace the ICT~Office Terms and Conditions and the [[https://www.gnu.org/licenses/agpl.html|GNU AGPLv3 License]] that applies to the SavaPage Software. In case of conflicts the AGPL License and ICT~Office Terms and Conditions takes precedence (in that order). This agreement is between Datraverse and SavaPage Community Residents and Visitors only. Other third parties may have separate arrangements with Community Members. These arrangements are excluded from this agreement. |