Thomas Grevenkamp

Initial Situation

The customer operates several Business Central systems in a multi-organization environment. There was no central monitoring, failed job queue processes went unnoticed, and errors were only discovered reactively after complaints or data issues.

Approach

- Setup of a central monitoring solution for monitoring the BC Job Queue across multiple organizations

- Integration of Azure Application Insights and Log Analytics for structured recording of job runtimes and error events

- Development of KQL queries for targeted analysis of failed jobs and detection of recurring error patterns

- Connection of Grafana for real-time visualization of operational metrics and job status

- Implementation of an automated alerting workflow with Power Automate – upon a failed job, a notification is triggered immediately

Results

- Complete transparency on the status of productive background processes – for the first time in the customer's history

- Significant reduction in response time: errors are now reported in real-time instead of being discovered only after complaints

- Solid monitoring basis for further expansion and additional BC organizations

Technologies

Azure DevOps | Application Insights | Log Analytics | KQL | Grafana | Power Automate | PowerBI | Business Central

| Azure Monitor

Initial Situation

The Navision billing system had reached its capacity limits and was to be migrated to Microsoft Dynamics 365 Business Central, with live operation maintained and no interruption to billing for e-roaming partners.

Approach

- Migration of the business-critical Navision solution to Microsoft Dynamics 365 Business Central

- Data migration with parallel synchronization phase to ensure data consistency during the go-live period

- Go-live of the new BC application in live operation without interruption of productive billing processes

- Further development and stabilization of e-roaming interfaces according to OCPI and OICP

- Performance optimization of data-intensive billing processes after go-live. Runtimes reduced from several hours to under one hour

Results

- Successful migration of a productive billing system without operational interruption

- Data consistency ensured during the transition through a controlled synchronization phase

- Significant performance improvement: import processes from 6 hours to under 1 hour, report runtime from ~180 to ~14 minutes reduced

- Increased scalability and future-proof technical basis for further growth

Technologies

Business Central (AL) | Navision (C/AL) | C# | .NET Framework | Entity Framework Core | Blazor | SQL Server | Azure | Azure DevOps | Azure SQL | AWS | EC2 | TypeScript | REST | JSON | XML | OCPI | OICP

Initial Situation

A strategic corporate decision mandated the central consolidation of all applications on AWS. Existing .NET console applications and manual Excel-based processes needed to be transitioned into a scalable, automatable cloud architecture.

Approach

- Migration of existing .NET applications into a scalable AWS target architecture with multi-account / multi-environment structure

- Redevelopment of .NET console applications as cloud-native services

- Replacement of manual Excel-based processes with AWS Lambda functions

- Setup of containerized services with Docker and introduction of Infrastructure as Code with Terraform

- Development and integration of data stream connections from external sources via SQS, SNS, and REST

Results

- Complete consolidation of the application landscape on AWS within the planned timeframe

- Manual Excel processes replaced by automated Lambda functions – error sources eliminated, maintainability improved

- Modernized cloud architecture with automatable deployment and a solid basis for future growth

Technologies

C# | .NET Core | | .NET Framework | SQL Server | Azure | Azure DevOps | DynamoDB | Docker | Terraform | Entity Framework Core | Blazor | REST | AWS | EC2 | Lambda | SQS | SNS | SES | TypeScript