AMS Next Gen
From ticket queue to operations decision system.
SAP Operations Decision System
Support should reduce future support.
AMS Next Gen is my operating model for SAP support and continuous improvement. The goal is not to close more tickets. The goal is to restore business flow, remove repeat demand, make changes safer, turn known work into reusable procedures, and use operations evidence for better architecture and business decisions.
The operating loop
Every serious AMS activity should move through the same logic. Skipping a step usually creates the next ticket.
Start with the work, not the library
A user rarely wakes up wanting to browse AMS theory. They have an incident, a risky change, a repeated workaround, an architecture question, or a cost problem.
Six capability clusters
SAP modules are a domain filter, not the operating model. These clusters describe what AMS must be able to do across O2C, P2P, master data, integrations, warehouse, finance, and platform work.
Run & Recover
Restore business flow with evidence, control, and clean verification.
Lead question: What is happening, what is the impact, and what is the safest recovery path?
Prevent & Learn
Turn repeated pain into knowledge, prevention, and reusable assets.
Lead question: Why did this happen again, and what will make the next occurrence cheaper or impossible?
Change & Improve
Move from request queues to evidence-based improvement decisions.
Lead question: Is this change worth doing, how risky is it, and how will we prove the outcome?
Architecture & Automation
Reduce operational load through clean boundaries, observability, and automation.
Lead question: What should remain in SAP, what can move out, and what can become an executable procedure?
Control & Govern
Make ownership, risk, contracts, security, and vendor boundaries explicit.
Lead question: Who decides, what evidence is required, and where is the human approval boundary?
Value & Strategy
Connect AMS work to cost, trust, maturity, product direction, and business decisions.
Lead question: What value does this operating model create, and what should stop consuming capacity?
Maturity is a change in behaviour
A team is not mature because production is currently quiet. Maturity means the operating system needs less hero work and creates better decisions from the evidence it already has.
Firefighting
We react. Knowledge and control depend on people.
Controlled Operations
Evidence, ownership, recovery, and change gates are explicit.
Preventive AMS
Repeats become Problems. Knowledge and prevention reduce demand.
Automated Operations
Known work becomes procedures, controls, observability, and safe automation.
Decision Platform
Operations evidence improves architecture, investment, and business decisions.
One knowledge stack, different jobs
AMS becomes useful when diagnosis, process context, skills, datasets, and executable procedures reinforce each other instead of living as separate site sections.
Knowledge explorer
The original AMS bytes remain stable source material. This layer reorganises them by capability and maturity so the library behaves more like a system.
Chat-First AMS: One Conversation, One Trace
Stop treating support like email archaeology. Run AMS through structured chats that automatically produce the evidence trail.
Metrics That Hurt (in a Good Way)
If your metrics don’t change behavior, they are decorative. Modern AMS uses indicators that expose waste, risk, and fake progress.
Stable SAP Core, Free Edges
The mistake is not SAP itself. The mistake is letting SAP define how expensive, slow, and locked-in your whole landscape becomes.
No Fiori Dependency: AMS Runs on Signals, Not Screens
User interfaces age fast. Signals, events, and data contracts age slowly. AMS should operate on the latter.
Don’t Carry Problems Forward: SAP AMS as a Load-Killing System
Old AMS accumulates pain and calls it backlog. Modern SAP AMS deletes load permanently.
Contain Custom Code: Stop Z-Code from Owning AMS
Most SAP AMS pain is not caused by SAP standard. It’s caused by unmanaged custom code quietly becoming critical infrastructure.
Standard Changes, Automated Execution
Speed in SAP AMS doesn’t come from shortcuts. It comes from removing choice where choice is unnecessary.
AI-Augmented Diagnosis: Faster Thinking, Fewer Guess Cycles
SAP incidents are rarely hard because they are complex. They are hard because diagnosis starts blind.
Choose What NOT to Fix: Data-Driven AMS Triage
If you try to fix everything in SAP, you end up fixing nothing well. Modern AMS is ruthless about priority — using data, not emotion.
AMS Contracts That Don’t Lie: SLAs, SLOs, and Penalties With Teeth
Classic SAP AMS uses SLAs like makeup. Modern AMS uses measurable reliability targets tied to business flows — and penalties that punish the right behavior.
Team Topology for SAP AMS: Fewer Handovers, Faster Fixes
Most SAP AMS slowness is not technical. It’s organizational latency: handovers, unclear ownership, and ‘not my module’.
Approval Without Paralysis: Decision Gates That Actually Work
Approvals are not control. They are latency. Real control comes from clear gates, data, and reversible decisions.
Coordination Without Noise: How SAP AMS Talks Under Pressure
Most outages get worse because communication collapses. Too many messages, no shared truth, and zero decision rhythm.
Incentives That Shape Behavior: Teams, Bonuses, and Penalties
You get the AMS you pay for. If incentives reward speed and silence, you’ll get fragile fixes and hidden problems.
Vendor and Internal Team Alignment: One System, Not a Battlefield
SAP AMS fails fastest when internal IT, vendors, and business optimize against each other instead of the system.
Risk, Audit, and Control Without Slowing the System
Audit pressure usually makes SAP AMS slower and more defensive. Done right, it actually makes it calmer and cheaper.
Upgrade and Release Insulation: Keep AMS Calm While SAP Changes
SAP releases don’t kill AMS. What kills AMS is when every upgrade becomes a surprise generator.
Training That Pays Back: SAP AMS Enablement as a Ticket-Killer
Most AMS training is a one-off slideshow. Modern AMS training is a system that steadily deletes recurring demand.
Handover Without Amnesia: Make Knowledge Survive People
AMS collapses not when systems change, but when people change. Bad handovers recreate the same incidents with new names.
Knowledge Base as an Engine: Built for RAG, Not for Reading
A classic SAP KB is dead text. A modern AMS knowledge base is an execution engine for humans, bots, and AI.
Ideas Pipeline: Turning SAP AMS Pain into Improvements
Good ideas don’t appear in workshops. They leak out of incidents, workarounds, and repeated frustration — if you know how to capture them.
Continuous Learning Loop: AMS That Gets Smarter Every Month
If AMS knowledge doesn’t compound, you’re paying forever for the same lessons.
Exit Without Shock: AMS as a Controlled SAP Lock-In Reducer
You don’t escape SAP by rewriting it. You escape SAP by slowly making it less central — without breaking the business.
AMS as a Platform: Agents, Open Stack, and Composable Ops
When AMS stays a process, it caps its value. When AMS becomes a platform, it compounds.
Security and SoD as a First-Class AMS Flow
In classic SAP AMS, security is a gate at the end. In modern AMS, security is a continuous flow that prevents incidents instead of reacting to them.
Effort Estimation That Doesn’t Lie: Size, Risk, and Coordination Cost
In SAP AMS, bad estimates don’t just miss deadlines — they create chaos: wrong priorities, broken approvals, and hidden risk.
Problem vs Change Portfolio: Stop Letting Changes Starve Prevention
SAP AMS usually drowns not because of too many incidents, but because Problems and Changes fight for the same oxygen — and Problems always lose.
Backlog Hygiene: Keep SAP AMS Clean or It Will Rot
A dirty backlog is silent technical debt. It consumes attention, hides priorities, and creates fake urgency.
Boards and Scorecards: Executive Visibility Without Theater
Most AMS reporting is designed to look busy. Modern AMS boards are designed to force decisions.
Handover & Transition at Scale: Zero-Drama AMS Transfers
Most AMS transitions fail quietly. Not on day one — three months later, when the same incidents return and nobody remembers why.
Crisis Mode (P0): Lead the System, Not the Noise
In a real SAP P0, technical skill matters less than control of flow, attention, and decisions.
Financial Transparency: Know Where AMS Money Actually Goes
If you can’t explain why AMS costs what it costs, you can’t reduce it without breaking something important.
Demand Forecasting & Capacity Planning: Stop Scheduling Surprises
SAP AMS feels ‘overloaded’ when demand is unmanaged and capacity is planned as if tomorrow will be like yesterday.
AMS as a Product: Roadmap, Value Promises, and ‘Stop Doing’ Lists
If SAP AMS is treated as a service desk, it stays expensive forever. If it’s treated as a product, it becomes predictable, improvable, and cheaper over time.
Master Data in AMS: Treat Data Quality as Production Reliability
In SAP, master data is not ‘data’. It’s executable configuration. Bad data behaves like bad code — it breaks flows, creates incidents, and burns AMS capacity.
Change Intake & Agreement: Stop Negotiating Chaos
Most SAP AMS pain starts before any work begins — at intake. Vague requests turn into scope creep, rework, and unsafe changes.
Conflict-Proof AMS: Multi-Vendor Reality Without Blame Games
Conflicts in SAP AMS don’t come from bad people. They come from unclear boundaries, mixed incentives, and missing evidence.
Verification & Acceptance: Prove the Change Worked (or Don’t Close It)
Most SAP AMS work fails quietly at the end: changes are ‘done’, but nobody can prove the business is safer or faster.
Knowledge → Automation → Agent Loop: Make Fixes Compound
If a fix lives only in a human’s head, AMS pays for it forever. Modern AMS turns fixes into reusable assets.
AMS Culture Rules: Behavior That Makes the System Work
Processes don’t fail first in SAP AMS. Behavior does. Culture is the invisible control plane.
AMS Operating System: How All Pieces Work as One
Modern SAP AMS fails when parts are optimized in isolation. It succeeds when everything is wired into a single operating system.
Executive One-Pager: Modern SAP AMS in 5 Minutes
This AMS is designed to reduce risk and cost at the same time — without betting the business on big rewrites.
Anti-Patterns Catalog: What Kills SAP AMS Faster Than Bugs
Most AMS disasters are not caused by SAP defects. They are caused by repeated bad patterns that everyone quietly tolerates.
From Support to Trusted Advisor: Introducing New Capabilities Without Noise
New SAP or adjacent capabilities fail not because they are bad, but because AMS introduces them like features — instead of decisions.
Vendor Segmentation & Operating Boundaries: How to Run Multi-Vendor AMS Cleanly
Multi-vendor AMS only works when boundaries are real: defined surfaces, measurable contracts, controlled access, and a single arbitration layer.
Decision Support Factory: Making Reliable Estimates for Business Choices
The fastest way to become a trusted AMS provider is to stop answering with opinions — and start delivering decision packs that survive scrutiny.
AMS Maturity Levels: From Firefighting to Decision Platform
Most SAP AMS teams believe they are mature because systems are running. Real maturity starts when the system improves itself.
AMS Reputation Metrics: Measuring Trust, Not Ticket Volume
Reputation in AMS is not what people say in meetings. It’s what they do before problems appear.
AMS as Risk Buffer: Absorbing Business Uncertainty Without Breaking SAP
SAP breaks not because change exists, but because risk is unmanaged. Modern AMS exists to absorb uncertainty — not to pretend it isn’t there.
RAG-First Documentation: From Diagrams to Living Text Structures
Classic SAP documentation dies the moment reality changes. Diagrams freeze assumptions. Text structures evolve.
TCO & ROI in Modern AMS: Measuring What Actually Matters
AMS cost is not what you pay the vendor. It’s what the system forces you to repeat.
What I expect from a Lead
- Separate symptom, evidence, hypothesis, decision, and action.
- See the business process behind the SAP object and the integration behind the symptom.
- Protect recovery speed without turning production into an uncontrolled laboratory.
- Convert repeated work into a Problem, a procedure, a control, or an architecture improvement.
- Make vendor, business, data, and technical ownership explicit before escalation starts.
- Explain cost, risk, and trade-offs in language a business owner can use.
AI belongs inside the loop
AI is not a separate AMS tower. It can extract evidence, suggest hypotheses, challenge a decision, generate diagnostic checks, compare incidents, draft communication, and turn a proven fix into a reusable procedure. The human boundary stays around risky production actions, business decisions, and changes that alter data, configuration, code, access, or message sequencing.