SANDOZ
Enabling Controlled Change in a Regulated Pharma Environment
Industry: Pharmaceuticals
Engagement: Ongoing
Scope: SAP S/4HANA Greenfield Implementation with SAP Cloud ALM
The Challenge
Our client, a global pharmaceutical company, initiated a greenfield SAP S/4HANA implementation in a highly regulated GxP environment.
In pharma, change is not just about delivery speed. It is about:
- Full traceability from requirement to deployment
- Strict documentation standards
- Audit readiness at all times
- Clear segregation of duties
- Controlled testing and validation
- Transparent approval workflows
In a regulated environment, every requirement, configuration change, test case, and transport must be documented and reproducible.
The client needed a structured and compliant ALM setup to support:
- End-to-end implementation governance
- Controlled change processes
- Documentation aligned with regulatory expectations
- Audit-proof traceability
- Scalable governance for global rollout
SAP Cloud ALM was selected as the Application Lifecycle Management platform — and CloudALMexperts was engaged to take ownership of the Cloud ALM implementation and governance design.
Our Role
CloudALMexperts is responsible for the design and implementation of SAP Cloud ALM for implementation, with a strong focus on:
- Requirements Management
- Change & Deployment Management
- Test Management
- Traceability & Documentation
- Implementation governance model
Our role goes beyond configuration. We are shaping how change is controlled across the entire S/4HANA program.
The Cloud ALM Implementation Focus
1. Structured Requirements & Full Traceability
In a pharma environment, traceability is not optional.
We established:
- Requirement hierarchy aligned with business processes
- Linkage between requirements, user stories, test cases, and transports
- Approval workflows ensuring controlled sign-off
- Documentation standards aligned with validation expectations
This ensures every delivered object can be traced back to an approved requirement.
2. Change Management as the Core Control Mechanism
The main focus of the engagement is Change Management within SAP Cloud ALM for Implementation.
We implemented:
- Controlled change types
- Role-based approval flows
- Clear transition gates between phases
- Audit-ready documentation trails
- Integration between change, task, and testing objects
In a regulated environment, uncontrolled change equals compliance risk. Cloud ALM is being used as the backbone of controlled transformation.
3. Test Management & Validation Support
Testing in pharma must support validation standards.
We designed:
- Structured test preparation cycles
- Linked test cases to requirements
- Clear defect management processes
- Evidence documentation strategy
This ensures validation documentation is embedded in the process — not created manually afterward.
4. Governance Model for a Greenfield S/4HANA Program
A greenfield program creates both opportunity and risk.
We helped define:
- Implementation phases aligned with SAP Activate
- Governance boards and approval gates
- Change control procedures
- Role definitions and responsibilities
- Integration with development and release cycles
The result is a structured implementation backbone that scales with the program.
Current Status (Ongoing Engagement)
The project is ongoing, and SAP Cloud ALM is actively being used to:
- Control implementation scope
- Manage change and approvals
- Drive testing cycles
- Ensure structured documentation
- Prepare for future audit requirements
CloudALMexperts continues to act as the SAP Cloud ALM authority within the program — ensuring the platform is not just implemented, but embedded into daily operations.
Value Delivered So Far
- Controlled and compliant change management
- Strong traceability across implementation artifacts
- Reduced compliance risk
- Structured governance in a complex global program
- Increased transparency across workstreams
Why This Matters
In regulated industries like pharmaceuticals, SAP Cloud ALM is not just a project tool. It becomes a compliance enabler.
Without structured change governance, implementation risk increases significantly.
By embedding SAP Cloud ALM at the heart of the S/4HANA transformation, the client ensures audit readiness, controlled deployments, end-to-end traceability, and sustainable governance beyond go-live.
Client Overview
H&M Group is one of the world’s largest fashion retailers, operating across multiple markets with complex supply chain, finance, and retail system landscapes.
SAP plays a central role in supporting global business processes — making structured change and release management critical to operational stability.
The Context
At H&M, SAP Solution Manager was used as the central Application Lifecycle Management platform, with a strong focus on ChaRM (Change Request Management).
The landscape was large.
The release cycles were complex.
The business impact of failure was high.
Even minor change errors could affect:
- Retail operations
- Logistics flows
- Financial postings
- Store operations across markets
This was not about configuring ChaRM.
This was about running enterprise-scale release governance from the customer side.
The Challenge
The environment included:
- Multiple parallel development tracks
- High release frequency
- Cross-functional dependencies
- Global rollout complexity
- Strict separation of duties
Key challenges included:
- Ensuring release transparency
- Preventing transport conflicts
- Coordinating approvals across stakeholders
- Maintaining stability during peak business periods
- Balancing agility with control
In global retail, downtime is not theoretical.
It is revenue impact.
The Role
Working on the customer side, responsibility included:
- Running ChaRM-based release cycles
- Coordinating change approvals
- Governing transport sequencing
- Aligning development and business readiness
- Ensuring structured go-live procedures
This required both technical understanding and governance discipline.
Release management was treated as a control function — not an administrative task.
Governance Approach
Changes were grouped into controlled release waves with:
- Defined scope boundaries
- Clear approval checkpoints
- Transport sequencing rules
- Pre-go-live validation
No uncontrolled deployments.
Transport Governance & Risk Control
ChaRM was used not only for documentation, but for:
- Enforcing approval workflows
- Preventing unauthorized transport imports
- Ensuring correct sequencing
- Creating traceability between change and deployment
This reduced production risk significantly.
Business Alignment
Release planning was aligned with:
- Business calendars
- Peak retail seasons
- Financial closing periods
- Market rollout schedules
Governance was aligned to business reality — not just IT timelines.
The Result
The structured ChaRM governance model delivered:
- Controlled enterprise release cycles
- Reduced transport conflicts
- Improved transparency for stakeholders
- Strong audit traceability
- Stable go-lives across complex landscapes
Most importantly:
Release governance became predictable instead of reactive.
Strategic Insight
Large SAP landscapes do not fail because of missing features.
They fail because of uncontrolled change.
This engagement built deep practical experience in:
- Enterprise release governance
- Transport control in complex landscapes
- Cross-functional coordination
- Change transparency under pressure
Why This Matters Today
As organizations transition toward SAP Cloud ALM, many underestimate what structured change governance really requires.
Tools change.
Governance principles do not.
Experience running enterprise ChaRM from the customer side provides critical insight when designing future lifecycle governance models — including transitions toward SAP Cloud ALM.
Closing Perspective
Enterprise SAP environments require more than configuration skills.
They require structured control, release discipline, and business-aligned governance.
That is the difference between technical setup — and operational stability.
More Clients...
