01 · Starting point
Situation
Business-critical applications are more than a server or a database. Specialist applications, middleware, databases, interfaces, vendor approvals and operating processes form a web of dependencies that must keep working reliably throughout changes and migrations.
Constraints
- Live operation of business-critical applications
- Dependencies between application, middleware, database and infrastructure
- Several internal units, customers and vendors in the same change process
02 · Responsibility
My scope of responsibility
In this long-running framework contract with variable utilisation I was responsible for operational stability, technical development and the migration of selected applications. I combined platform analysis with change control, vendor coordination and support through to go-live; shorter specialist engagements ran in parallel at times.
- I mapped technical dependencies between applications, middleware, databases and connected services.
- I planned and supported migrations through test, change and go-live up to the handover into data-centre operations.
- I coordinated technical work packages with customers, vendors and internal IT units.
03 · Technical work
Documented scope of work
Key decisions
Plan migrations consistently from the business application and its dependencies. A technically successful individual component is worthless if interfaces, data flows or operational handovers are not brought along.
Standardise recurring checks and fault analysis. PowerShell-based routines make complex states comparable faster and reduce inconsistent manual diagnosis.
- PowerShell scripts supported administrative workflows and structured fault analysis.
04 · Technical context
Technology in use
Windows Server
Windows-based components were part of operating selected business applications.
Citrix
Citrix was part of the supported application and delivery contexts.
PowerShell
PowerShell was used for administrative workflows and structured fault analysis.
SQL
Database dependencies were analysed in connection with applications and migrations.
Middleware
Middleware dependencies were documented for operations, changes and migrations.
ITSM / Remedy
Orders, changes and technical dependencies were steered through ITSM and Remedy processes.
05 · Factual basis
Evidence and limits
Operations, migration, automation and ITSM tasks for selected business-critical applications are documented.
Names, internal service levels and specific operating metrics of the applications remain confidential.
- Engagement period
- June 2015 to December 2025
- Scope of responsibility
- Operations, migration, automation and ITSM control
Lesson from the engagement
With critical business applications, success is decided not by the individual technology but by the quality of the dependency analysis and the operational handover.
Confidentiality note: Names and internal details of the supported applications are not published.