This overview applies to the Services provided by Novorender to the Customer for the provisioning, maintenance and cessation of Services from the Customer and to Novorender.
2.1. Novorender responsibilities
2.2. Customer responsibilities
The Novorender Support Desk operates a standard working week (Monday to Friday), available between Monday 09:00 CET and Friday 15:00 CET.
Novorender will nominate a dedicated Professional Solution Architect and/or Key Account Manager to be the first point of contact for the customers appointed Novorender technical owner.
Priority |
Definition |
Examples (Non-exhaustive) |
1 – Urgent |
The service is down or there is a critical impact to business operation. No workaround exists., Novorender will commit full-time resources to resolve the issue. To the extent needed to resolve the issue, Customer and End User will use reasonable efforts supporting Novorender |
1. Customer has no access to Novorender 3D scenes. |
2 – High |
Operation of components of the Novorender cloud platform are severely degraded or business critical aspects of the End Users’ experience are negatively impacted by unacceptable performance. |
1. Login issue for some users. |
3 – Normal |
A light degradation of service with medium to low impact on business operations. Single user can operate normally but with some inconvenience. |
1. Some admin functionality showing unwanted behaviour. |
4 – Low |
Non-service affecting issues and scheduled. |
When submitting a Fault report to Novorender, Customer shall seek to include, the following information to Novorender:
Person to receive feedback
Upon receipt of a reported Fault, Novorender will maintain a record of the Fault (the “Fault Log”), including the time that either Novorender was notified, or that Novorender notified Customer, of the Fault (the “Notification Time”). Each Fault in the Fault Log will be assigned a priority by Novorender; the Fault priority will be based on the criteria shown in Table 1; the Response Time will be based on the priority assigned in accordance with Table 3.
When proactively reporting a Fault to Customer via email, Novorender shall provide, as a minimum, the following information to Customer:
Novorender shall undertake tests to identify the nature of the reported Fault and the results will be passed to Customer as appropriate. If such results indicate a potential Fault within any element of the Service Novorender will initiate appropriate further diagnostic and/or Fault repair activity.
In the event that Novorender investigates a Fault, but finds that the Service is working correctly and/or the Fault is not caused by Novorender, Novorender may, to the extent the tasks is ordered by Customer in writing, charge Customer for its time reasonably spent to help rectify the Fault at its standard rates stated in the Novorender price list or as defined in the Customer contract.
The time taken to rectify a Fault from the Notification Time is the Resolution Time. Novorender will use reasonable endeavors to ensure that all Faults are rectified within the target Resolution Time defined in the table within Section 9.2.
When calculating the actual Resolution Time, Novorender will disregard:
The time that the Fault is rectified, and the Service is restored will be recorded in the Fault Log. When the Fault has been rectified Novorender will notify Customer as appropriate.
Novorender uses the Azure cloud platform, where uptime is integrated into every aspect of the services provided. Novorender gives no service level guarantees when tenants are installed on Customer Premises Equipment (“CPE”).
8.1. Uptime
Uptime, Novorender differentiates between two main service elements:
8.2 High availability
As Novorender is delivered as a cloud related service, a key aspect of our resilient foundation is availability. At Novorender, we consider High Availability as maintaining acceptable continuous performance despite temporary failures in services, hardware, or data centers, or fluctuations in load. Highly available systems are consistently operational over long periods of time.
8.3 Geo-redundant Storage
Azure Storage always stores multiple copies of your data so that it is protected from planned and unplanned events, including transient hardware failures, network or power outages, and massive natural disasters. Redundancy ensures that your storage account meets its availability and durability targets even in the face of failures. At Novorender, we always provide Geo-redundant storage (GRS) copies of your data, which synchronously copies everything three times within a single physical location in the primary region using LRS. It then copies your data asynchronously to a single physical location in the secondary region. Azure guarantees that at least 99.9% (99% for Cool Access Tier) of the time, they will successfully process requests to read data from Redundant Storage (GRS) Accounts. For more information, please refer to Azure Storage Redundancy and SLA for Storage Accounts.
9.1. Response Time
The response time measures how long it takes Novorender to respond to a support request raised via the online support system. Novorender is deemed to have responded when replying to the initial request. This may be in the form of an email or a phone call, to either provide a solution or request further information.
Guaranteed response times depend on the Priority level of the issue.
Proof of Concept/Technical Evaluation customers may expect a longer response time vs Production enabled customers.
Priority |
Novorender Software response time/ outside of office hours |
1 |
6 hours / One business day |
2 |
One business day / Two business days |
3 |
Three business days |
4 |
One week |
9.2. Expected resolution Time
The expected resolution time measures how long it takes Novorender to restore the service, after an issue has been raised and identified. Guaranteed resolution times depend on the Priority level of the issue:
Priority |
Novorender Software response time/ outside of office hours |
1 |
6h / One business day |
2 |
One business day / Two business days |
3 |
One Week |
4 |
One month |
For issues that depend on Microsoft’s resolution, Novorender may prolong the time it takes to resolve the issue.
Novorender has a scale up plan for solving issues based on criticality:
Priority |
Resources |
1 |
All available development resources who can impact a fix. |
2 |
At least the development lead and team for the effected area. |
3 |
Will be on top of backlog. Novorender releases at least 1-3 times a week, and expected resolution will be in next release cycle. |
4 |
Will be on top of backlog behind priority 1-3. If there are no higher criticalities going on at the same time and expected resolution will be in next release cycle. |
If the expected resolution time is not met, priority will be increased by one level. E.g. if priority 3 is not resolved within the next release cycle, this issue will be escalated to priority 2 and so forth.
From time to time Novorender will need to suspend services for planned maintenance. This will be announced by email to the main Customer contact.
Where practical, any suspension of services will be arranged to fall outside normal working hours.
Novorender will use reasonable endeavors to give Customer not less than fourteen (14) days’ notice of any planned works. Such notice shall advice Customer of the works to be undertaken, the planned start and end time of the works and, where relevant, the End Users who will be affected. Customer acknowledges that provision of advance notice may not be possible in the event of an emergency.
Following completion of the planned work, Novorender will report the outcome by email to the main Customer contact.
Any downtime caused by planned maintenance should be excluded from the calculation of the availability of the service.
In the event of Customer being dissatisfied by Novorender’s response to a Service issue, in the first instance Customer must contact the Novorender Support Manager via the Helpdesk, quoting the relevant Fault Reference Number. If, however, Customer is still not satisfied, Customer should contact the Novorender representatives in the below table, in the specified order.
Escalation Level |
Name |
Title |
|
Level 1 |
Rafael Hegre Cabeza |
Head of Product |
rhc@novorender.com |
Level 2 |
David Berg |
VP Business Development |
db@novorender.com |
Level 3 |
Tore Hovland |
Chief Executive Officer |
th@novorender.com |
Novorender must ensure every Novorender Software customer chosen knows about the management Escalation process.