With Support & Maintenance, we actively monitor changes in the tech stack together with you and perform proactive maintenance. This allows us to respond immediately to necessary (security) actions and updates. You can also rely on our expertise in the event of incidents and support requests. Although we naturally do everything we can, together with you, to prevent incidents through proper maintenance.
It ensures transparency, accountability, and clarity. It lays the foundation for a reliable collaboration and ensures that your business-critical applications function optimally. And that is essential to the success of your organization. Below you will find the components included in all SIENN Service Level Agreements.
For asking questions, reporting disruptions, and submitting change requests. Depending on your preferences, we can make agreements about the availability of the service desk and the underlying support.
To resolve service disruptions as quickly as possible. For example, if an employee, with the correct permissions, is still unable to use the service properly. We address this in several steps. First, we determine the priority, then the impact, followed by the urgency, and then decide how quickly we need to respond and restore.
To ensure the highest possible quality of your services, we minimize the negative impact of incidents. Has an incident occurred before? Then we take measures to prevent those incidents in the future or reduce their impact. We investigate incidents, identify connections, and implement structural solutions.
For implementing changes in a structured way to improve the quality of the service. At the same time, the risks of service disruption are kept to a minimum. We distinguish between two types of changes: Normal and Emergency. Each with a different approach and timeline.
To handle service requests effectively and efficiently. A Service Request is a question or request from an authorized user to the Service Desk that does not require a change to the service. For example, obtaining information or advice, resetting passwords, or granting access rights.
Ideally, you will notice little when we carry out maintenance. We aim to perform it in a way that causes as little disruption as possible for users. All maintenance activities that may affect the use of a service are of course discussed with you in advance.
These are the two types of maintenance at SIENN:
This takes place as much as possible during scheduled maintenance windows. You will always be informed at least three business days in advance that maintenance is due.
This is required when we need to intervene immediately. In that case, we of course consult with you as soon as possible.
In addition to all security measures taken to ensure that business information is protected, we also keep track of which employees are authorized to submit requests or adjust authorizations. If we discover a security incident or data breach, we will of course inform you immediately.
Expanding and scaling software is necessary when the existing software infrastructure no longer meets the growing needs and requirements of your organization. It is useful to have this option. For example when you have an increase in users, a higher workload, or the need for new functionalities to meet changing business requirements.
Although the exact content of an SLA may vary depending on needs and agreements, there are several common elements that are often included in an SLA for IT. Think, for example, of general information such as contact details and the start date of the agreement. The purpose and objectives, the scope of the services, the service levels, responsibilities for both parties, escalation procedures, and security measures. A well-defined SLA is important for a healthy working relationship between service providers and clients.
Get in touch with us to explore opportunities or request an intake.