Operations, support and further development
After deployment, work on a system changes. Bugs, new requirements and changes in connected tools need attention. We agree on an operating model, points of contact and the path from a request to a tested change.
Discuss your briefDoes this sound familiar?
- When an issue occurs, nobody knows who should respond or where to report it.
- Updates are postponed because there is no tested deployment procedure.
- Backups exist but the recovery procedure has not been tested.
- New requests are handled without shared priorities or documentation.
From a process to a solution.
The scope follows your brief. Together, we will prepare these steps and deliverables:
- An agreed scope of operational responsibility and support.
- Monitoring, updates and backups to suit the operating model.
- An incident reporting procedure and agreed response times.
- Testing and deployment of changes using a documented procedure.
- Ongoing planning for further development.
Experience from a real project.
Questions about the solution.
What response times do you provide?
We agree on response times and support scope based on the system's criticality, operating hours and capacity. The agreement also distinguishes incidents, routine requests and planned development.
Can you take over a solution from another supplier?
We first assess its technical condition, documentation, licences and available access. We can then propose the conditions for taking it over and the changes it needs.
Have a process
that needs to change?
Let’s start with how you work today. We’ll choose the technology around it.