Skip to content

Platforms & implementation

Operations & support

After go-live we stay at your side: with support, maintenance, service packages and blocks of hours for your platforms, integrations and software, with individually agreed SLAs if you need them.

People who know your system

We look after what we built with you, with no lengthy onboarding and no anonymous hotline.

Maintenance and updates

We keep platforms, integrations and software up to date, install updates and deal with errors.

Service packages and blocks of hours

We take over ongoing care completely, or you book a block of hours for change requests and adjustments.

SLAs to match your needs

Service hours, response times and escalation paths are agreed individually, depending on how critical your systems are.

Go-live is only the beginning

An integration, a CMDB or a new platform has to run reliably every day. Updates arrive, interfaces change, requirements grow. We stay on it and make sure your solution keeps working long after the launch.

What we look after

  • Integrations: monitoring processes and agents in Frends, fixing errors, installing updates, renewing expiring certificates and credentials, and adapting interfaces when a connected system changes.
  • CMDB: keeping sources and reconciliation rules up to date so that the data in your CMDB is correct.
  • Atlassian: administering Jira, Confluence and Jira Service Management, maintaining configuration and apps. This also covers governance with clear rules for projects, spaces, permissions and fields, archiving old projects and regular licence optimisation: which users, editions and apps do you really need?
  • Documents and signatures: Therefore™, sproof sign and SmartSuite in day-to-day operation.
  • Software: maintaining and developing custom software and XISUITE.

Service packages: we take care of everything

With a service package, we take over the ongoing care of your solution completely: maintenance, updates, monitoring, change requests and adjustments. For example, we look after your integrations in Frends, or take on the administration of Jira and Confluence including governance and licence optimisation. We agree the scope with you, from individual integrations to the whole platform.

Blocks of hours for change requests

Not every change needs a project of its own. A block of hours gives you a contingent to use flexibly for change requests and adjustments, such as a new workflow in Jira, an additional field or a change to an integration.

SLAs to match your needs

For business-critical systems, we agree a service level agreement. Service hours, response times per priority and escalation paths are set individually, depending on how critical your systems are.

How we take over operations

  1. Take stock

    Which systems, integrations and processes are involved, and who is responsible for them today?

  2. Agree the package and SLA

    Scope, service hours and response times that match your requirements.

  3. Take over

    Set up access, monitoring and documentation so that we can respond quickly.

  4. Support and improve

    Updates, regular check-ins and further development in day-to-day operation.

If your requirements change, we adjust the package and SLA together.

You stay independent

Your systems remain your systems. We document what we build and train your team if you want to take over tasks yourself.

Frequently asked questions

Can’t find your question? Ask us directly: Contact

Which systems can you look after for us?

The platforms and integrations we implement, such as Frends, Atlassian, CMDB data flows, Therefore™, sproof sign and SmartSuite, plus custom software and XISUITE. Whether we can also take over systems that others have built is something we clarify after a look at your environment.

What response times apply?

We agree them individually in a service level agreement (SLA), with service hours, response times per priority and escalation paths, depending on how critical your systems are to your business.

What does a service package include?

We define the scope together. Typical elements are maintenance and updates, monitoring of the integrations, error analysis and fixes, change requests and adjustments, and regular check-ins. That way you do not have to look after day-to-day operations yourself.

How do blocks of hours work?

You book a contingent of hours and use it flexibly for change requests and adjustments, such as a new workflow in Jira, an additional field or a change to an integration. We agree the size of the block together.

Can we take over tasks ourselves later?

Yes. We document what we build and train your team if you want to take over parts of the operation yourself. You stay independent of us.

How do we report an incident?

Through the channels we set out in the service package or SLA, for example by email, phone or a ticket portal. Without a separate agreement, you can reach us by phone and email as usual.

Frends iPaaS

As the largest Frends partner in the DACH region, we connect your systems and automate processes with the low-code integration platform Frends, starting with a proof of concept.

CMDB & data integration

We build your CMDB and keep it up to date automatically with Frends, no matter which systems the data comes from and whether the target is Jira Assets or another solution.

Atlassian

From the first idea to a scaled enterprise system: we plan, implement and support Jira, Confluence and Jira Service Management, in the cloud or on Data Center.

Training

Training for Jira, Confluence, Jira Service Management and Frends: for whole teams, on specific use cases, as an introductory session or workshop, whenever you need it.

Let’s talk about your plans.

Whether it’s a first idea, a project already under way or an existing IT landscape: we listen, put things into context and show you concrete next steps.

Your contacts: Christian, Tobias and Michael, the founders of AmberTech Solutions.