Managed Services

A business system needs attention every working day: legislation changes, the vendor releases updates, new employees have questions and the business asks for a new report. Managed services keep the system current and available, at a cost that is known in advance.

What is covered

• Incidents. Errors that stop or slow down the work of users are registered, classified by urgency and resolved within the agreed time.
• Questions. How to enter an operation, why a report shows a figure, how to close the month.
• Updates. New releases of the standard configurations and of the platform are tested on a copy of your database first and installed at an agreed time.
• Changes on request. Reports, print forms, access rights and settings.

How it works

1. Onboarding. We examine the system, the changes made to it and its documentation, and agree the service levels and the people who may submit requests.
2. One point of contact. Every request is registered, gets a number and a responsible specialist.
3. Priorities. Requests are classified by how much they block the work. Response and resolution times depend on the class and are fixed in the contract.
4. Monthly report. What was requested, how fast it was resolved, what repeats, and what we suggest changing so that it stops repeating.

Dedicated specialists

When the volume of work is steady, a 1C developer or consultant joins your team full time or part time. The specialist works on your tasks and by your plan. We remain responsible for the specialist's qualification and for the review of the work.

When to talk to us

• The system was implemented by another supplier or by an employee who has left.
• Updates have not been installed for a long time and installing them now looks risky.
• Your own 1C staff cannot keep up with requests, or there is nobody to replace them.
• The cost of support is hard to predict.

Questions clients ask

Can you support a system that you did not build?

Yes. We begin with an examination: which changes were made to the standard configuration and in what condition the data and the documentation are. After that we say what can be supported as it is and what should be put in order first.

Our configuration is heavily changed and has not been updated for years. What can be done?

We compare it with the vendor's version, list the changes and plan the update in steps. Changes that are still needed are moved into extensions, the rest are removed.

How do we see what the support gives us?

From the monthly report. It shows the requests, the time to a solution and the problems that repeat, with a proposal on how to remove their cause.

Result

The system stays current with legislation and available to users, at a cost known in advance.