Transformation and engineering position
My focus is to combine transformation architecture with hands-on engineering—creating practical, reusable and secure solutions aligned with SAP extensibility, clean-core principles, enterprise security and long-term architecture standards.
Enterprise AI direction
My current exploration includes custom SAP AI agents, ABAP Cloud wrappers and read-only POCs for diagnostics, code review, monitoring, RCA, summarisation and recommendations, with traceability and human oversight designed into the operating model.
Working method: problem → evidence → options → decision → impact.
Context-first architecture: make facts, assumptions and risks visible; compare realistic alternatives; define control and publication boundaries; connect recommendations to operational or business outcomes. I am deliberately sceptical of architecture that looks impressive but cannot be operated, governed, measured or recovered when it fails.
Stage 1SAP engineering foundation
- Context
- Enterprise SAP development and system behaviour.
- Technical focus
- Hands-on ABAP development, debugging and runtime understanding.
- Architecture perspective
- Engineering decisions must survive production reality.
- Enterprise impact
- Reliable delivery and a durable technical foundation.
- Next stage
- Business process and integration depth.
Stage 2Business-process and integration depth
- Context
- Connected SAP processes across utilities, finance and integration.
- Technical focus
- SAP IS-U, finance integration, APIs, interfaces and enterprise messaging.
- Architecture perspective
- Architecture must follow process, data and ownership boundaries.
- Enterprise impact
- Stronger end-to-end diagnosis and solution design.
- Next stage
- Performance, diagnostics and production ownership.
Stage 3Performance, diagnostics and production ownership
- Context
- Complex production behaviour, failures and operational pressure.
- Technical focus
- Runtime analysis, RCA, jobs, locks, dumps, integration waits and recovery.
- Architecture perspective
- Observability and recovery are product capabilities.
- Enterprise impact
- Faster isolation of bottlenecks and more defensible recommendations.
- Next stage
- Technical leadership and delivery governance.
Stage 4Technical leadership and delivery governance
- Context
- Multi-team delivery across releases and enterprise constraints.
- Technical focus
- Development governance, transports, quality, planning and coordination.
- Architecture perspective
- Good architecture includes decision rights and release discipline.
- Enterprise impact
- More controlled delivery and clearer accountability.
- Next stage
- S/4HANA transformation architecture.
Stage 5S/4HANA transformation architecture
- Context
- Greenfield, Brownfield and conversion programs.
- Technical focus
- Custom-code remediation, integration, migration, extensibility and conversion controls.
- Architecture perspective
- Transformation needs explicit trade-offs and clean-core direction.
- Enterprise impact
- Reusable transformation patterns and lower long-term change risk.
- Next stage
- Cloud-ready extensibility and clean core.
Stage 6Cloud-ready extensibility and clean core
- Context
- Modern SAP extension and API patterns.
- Technical focus
- RAP, ABAP Cloud, Fiori, OData and API-led design.
- Architecture perspective
- Extensibility should reduce future change cost and protect upgradeability.
- Enterprise impact
- More maintainable and policy-aligned extension models.
- Next stage
- Enterprise AI and custom agent architecture.
Stage 7Enterprise AI and custom agent architecture
- Context
- Practical AI applied to SAP evidence and operational decisions.
- Technical focus
- Read-only agents, wrappers, MCP, evidence, prompt traceability and model abstraction.
- Architecture perspective
- AI value depends on governed enterprise context.
- Enterprise impact
- Safer experimentation and more explainable intelligence patterns.
- Next stage
- Independent architecture and publication platform.
Stage 8Independent architecture and publication platform
- Context
- Public architecture research and reusable professional knowledge.
- Technical focus
- Structured publications, product concepts, release governance and privacy-conscious delivery.
- Architecture perspective
- Publish reusable learning without exposing restricted implementation.
- Enterprise impact
- A durable professional platform for research, collaboration and public evidence.
- Next stage
- Controlled evolution through future releases.
