Defined scope.
Organised work.

Project delivery, ongoing maintenance or support for an existing IT team. The model depends on needs and responsibility for the environment.

Cooperation models

Three ways
to organise work.

01

Project and deployment

A defined objective, scope and acceptance criteria. A model for new infrastructure, migration, modernisation or deploying a specific service.

02

Ongoing maintenance

Administration of selected systems and request handling under agreed rules. The scope may include updates, monitoring and reviews.

03

Support for an IT team

Consultation and specialist work in a selected area. Responsibilities and collaboration are agreed before work begins.

Workflow

From needs
to acceptance.

01

Understanding needs

Objectives, current environment, constraints and dependencies.

02

Scope and offer

Work items, responsibilities, schedule and acceptance conditions.

03

Delivery and verification

Configuration or deployment, followed by tests against agreed criteria.

04

Documentation and next steps

Handover of agreed documentation and definition of maintenance arrangements.

Pricing follows
the scope.

An offer requires information about systems, locations, dependencies and expected support. Availability, deadlines and documentation needs are also considered.

Access rules, maintenance windows, SLA levels and reporting are defined for the agreed scope.

Contact

Let’s discuss the scope.

Deployment, modernisation or maintenance?
The starting point is your infrastructure requirements.

Get in touch