01Understand the application
Technical needs follow from the components used and expected usage.
Operating model
Prepare software operations together
We connect application setup with planning for its operation. This establishes who provides the infrastructure and who takes on each task.
02Define account ownership
Account ownership and the billing recipient are determined before setup.
03Assign tasks
People are assigned responsibility for maintenance and operating questions.
04Prepare handover
Documentation and agreed access support ongoing administration.
Service
Hosting also involves ongoing upkeep
The operating environment includes the application, database, access paths and the services it actually needs. An AI application may also require model access or additional computing resources. The operating plan assigns provisioning, updates, backups, monitoring and incident handling to the responsible parties.
Provisioning and ongoing support need to fit together.
Accounts and responsibilities
Two ways to organise operations
The account model determines who holds contracts with infrastructure providers and receives invoices. Technical tasks are explicitly agreed regardless of that choice.
| Model | Organisation | To establish |
|---|---|---|
| Managed operation | T-NEX organises the agreed infrastructure and support. | Service scope, contracting parties and handover |
| Operation in the client account | Your institution holds the infrastructure accounts and receives provider invoices directly. | T-NEX access and allocation of operating tasks |
Operating tasks
Tasks that can be included in the scope
Potential services include server and database operation, access setup, backup and recovery procedures, and agreed monitoring and maintenance. For AI workloads, computing capacity and any GPU resources are planned according to the model and expected use. Choices follow the application’s requirements and the preferred account model.
01Set up the environment
Provision the application and database in the agreed environment.
02Prepare releases
Define how a checked change reaches operation.
03Set up monitoring
Monitor agreed components and name alert recipients.
04Plan backups
Define backup scope and how restoration will be handled.
05Coordinate maintenance
Maintain certificates and software dependencies within the agreed scope.
06Enable handover
Prepare the documentation and agreed access needed for a handover.
Your institution’s requirements
Review the specific environment
Assessment of the proposed environment includes data flows, storage locations, participating providers and administrative access. It also covers responsibility allocation, technical backup and recovery procedures, and the approach to a later provider change. The institution receives the information agreed for this scope to incorporate into its operating and control processes.
| Topic | Information | Ownership |
|---|---|---|
| Contract and account | Contracting parties and account holders | Before setup |
| Data processing | Data types, services and configured storage locations | Per application |
| Access | Authorised people and required technical access | By task |
| Operating documentation | Agreed tasks and available evidence | By service scope |
Service scope
Agree operations for the specific need
Choosing a data centre does not establish a complete operating service. The engagement defines the tasks T-NEX takes on and the prerequisites provided by your institution.
Service boundary
Availability, recovery objectives and specific operating requirements are assessed and agreed for the particular project.
Operating documentation
Hand over knowledge about the environment
The documentation describes the agreed system setup and responsible people. The material your team receives is defined with the operating scope.
Overview of the application and its services
Responsibilities for agreed operating tasks
Documentation for changes and handover
The documentation refers to the environment actually configured.
About operations
Frequently asked questions
Establish operations before launch
Describe your application and your institution’s requirements. We will discuss the technical environment and support needed.
Discuss operationsOperating services are defined for your project.
Sources & further reading
In-depth articles
- DORA for financial entities: duties and implementation
DORA since 17 January 2025: scope, ICT risk, incident reporting and third parties, with primary sources and implementation checks.
- DORA register of information: content and submission
The DORA register of information: record contracts, identifiers and supply chains using the EU templates and BaFin requirements.
- NIS2 vs DORA: what applies to banks and their IT?
NIS2 and DORA for banks: compare scope, BSI registration, reporting deadlines and ICT providers, with references to Germany’s BSIG.