SCSI Experts in Germany

Short description: Lead a group-wide project to establish standardized cloud governance for Microsoft Azure, including policies, security and compliance controls, automation, and cost and operations control while preserving the autonomy of decentralized business units within regulatory boundaries.

Tasks and activities:

Overall responsibility for the design, setup, and implementation of an enterprise-wide cloud governance structure (Azure), incl. target picture, roadmap, and operating model.

Management of internal and external stakeholders (C-level, IT, Security, Compliance, Cloud Architecture, DevOps) incl. decision-making and escalation management.

Planning and facilitation of workshops on cloud strategy, governance principles, and the design of areas such as Identity, Connectivity, and Platform Management.

Definition, implementation, and rollout of cloud policies (Azure Policy / custom policies), security standards, and compliance requirements (including GDPR, ISO 27001, BSI C5).

Building a cloud governance framework aligned with the Azure Cloud Adoption Framework (CAF), incl. landing zone and guardrail concepts.

Introduction of automation solutions for governance, security, and cost control (policy/control automation, IaC, CI/CD-based control mechanisms).

Implementation of cloud security and compliance monitoring mechanisms as well as continuous improvement processes.

Establishment and operationalization of FinOps in an enterprise environment (central and decentralized FinOps teams), incl. cost management strategies, reporting, and guardrails.

Integration of governance policies into DevOps processes (e.g. CI/CD principles for security and compliance checks, GitLab Runner concept in spokes, GitLab CI/CD for CAF landing zones).

Implementation of access concepts incl. RBAC design and "break glass" mechanisms (emergency access) as well as certificate automation (ACME / step-ca).

Achievements:

Created a unified, auditable governance and control set for Azure (policies, standards, compliance mapping) and thus laid the foundation for scalable cloud usage in a regulated environment.

Established repeatable automation for governance, security, and cost control (IaC + CI/CD), reducing manual effort and implementation risks.

Improved operational and decision-making capabilities across central and decentralized units (clearer roles, responsibilities, escalation paths, balance between autonomy and group requirements).

Significantly increased workload compliance for lift-and-shift migrations.

Technologies used:

Microsoft Azure Policy, custom policies.

Terraform, OpenTofu, Terragrunt.

step-ca (ACME).

Entra ID.

Azure Firewall.

Azure networking, hub-and-spoke architecture.

Azure vWAN (evaluation).

Azure Front Door, Azure Application Gateway.

Azure ExpressRoute.

Azure Key Vault.

NetBox.

GitLab (on-premises).

Infrastructure, concepts used:

Cloud shared responsibility model.

Hub-and-spoke connectivity / central shared services (from a hub-spoke context).

Central governance with decentralized delivery (business unit autonomy with guardrails).

Methods used:

Scrum.

Stakeholder management (C-level to engineering).

Cloud governance, Azure Cloud Adoption Framework (CAF).

DevOps, CI/CD.

Cost and FinOps approaches: tagging/chargeback models, budget/alert concepts, reserved instances/savings plans vs. on-demand scenarios, sensitivity analyses.

RBAC, "break glass" concepts.

ACME / certificate automation.

GitLab Runner concept in spokes, GitLab CI/CD pipelines for CAF landing zones.

The customer is undergoing a comprehensive transformation. All SAP ECC landscapes worldwide are being migrated to SAP S/4HANA, with the goal of introducing a standard template worldwide.

The program also includes the “RISE with SAP” migration and modernization program, which may involve migrating the landscapes of selected country installations to the SAP Private Cloud.

On the stakeholder side, the program reporting line extends to the company’s executive board and that of the implementation partner.

Fiserv Germany’s ERP landscape currently includes several non-standard SAP tools and applications that extend the functionality of the ECC environment and can often be integrated into downstream systems. As part of the transition to SAP S/4HANA, it is essential to assess the core functionality, integration points and future viability of these applications in order to determine their alignment with the target architecture.

The focus of the work is on providing expert advice and assessment to define the scope, strategy and roadmap for transitioning Fiserv Germany’s SAP ECC system to SAP S/4HANA.

The recommended best practices from SAP are followed and a structured approach is used to ensure a smooth transition with minimal disruption while maximizing business value.

This assessment forms the basis for a successful SAP S/4HANA transformation and ensures alignment with industry best practices, regulatory compliance and future scalability.

Migration Strategy Definition – assessment of available transition approaches based on business objectives, technical feasibility and SAP Best Practices.

Technical Readiness Assessment – conducting a system analysis to assess compatibility, custom code impact, data volume management, integration points and infrastructure readiness for SAP S/4HANA.

Business Process Impact Analysis – reviewing the latest business process documentation to define the scope and effort required to implement the necessary functions in SAP S/4HANA and to identify opportunities for process optimization.

Roadmap for Non-SAP Systems and Applications – assessment of third-party and legacy applications regarding their integration with SAP S/4HANA and recommendation of consolidation, migration or replacement strategies.

Deployment & Implementation Planning – defining a phased approach for implementation, including project schedules, risk mitigation strategies and key milestones aligned with business priorities.

This transformation takes place in phases: the Discovery phase leads to the Explore phase, which is followed by the Design phase and finally implementation.

Program management

Change management

Requirements management

Transition management

Stakeholder management

Risk management

Comprehensive coordination

Integration of a safety shutdown into the firmware of the MISCEO product after a specific limit value (capping) for the dispensing quantity is reached.

Familiarization with the product and its firmware (C code and functional operation).

Identification of the code sections required for the change.

Implementation of the enhancement.

Testing and documentation (source code only).

Target platform: Embedded firmware without an operating system.

Tools: Eclipse, C.