Start with Operations and migrate the rest at your own pace. We map your real use of Solman, design the transition and operate it.
We've operated SolMan since its earliest versions, including the 7.2 ramp-up.
Our operation on SolMan 7.2 holds PCoE certification.
We operate SolMan with more than 300 connected client systems across the region.
SAP will not develop new versions after 7.2. Mainstream support ends in late 2027 and extended maintenance runs to 2030. After that, only customer-specific maintenance: no evolution, no new functionality.
Cloud-native and focused on cloud and hybrid landscapes. It receives mainstream maintenance beyond 2030, and SAP confirmed it will not build new on-premise ALM products. The direction is clear: migrate in an orderly way, starting with Operations.
SAP Cloud ALM does not include ITSM. SAP points to a third-party ITSM — you need to decide what replaces it and how it integrates.
In Cloud ALM, change control moves to Deployment Management. The path depends on how you use ChaRM today.
We follow SAP's roadmap based on the SAP Activate methodology. It doesn't have to be one big project: you advance by fronts, at your own pace, while SolMan is still supported.
We run the SAP Readiness Check for ALM on your SolMan. It shows your real use —scenarios, capabilities, change volume— and classifies each capability: available in Cloud ALM, on the roadmap, out of Cloud ALM, or via third parties.
With the results we define scope, strategy and a transition plan. We prioritize Operations as the first front.
We configure the use cases in Cloud ALM and run the Selective Data Transfer in stages —processes, documents, libraries— with validation. You choose what to bring and can redesign it in the same step.
We add fronts according to what the business needs and what the Readiness Check prioritized — without stopping operations.
Agrosuper —a food holding with sales over US$1.1 billion and more than 14,000 employees— was dealing with ERP incidents rooted in the code quality of its custom developments: when the code failed, systems went down, and that hit business continuity and sales. Novis implemented the integrity and quality checks that control every development before it reaches production, to give the business the continuity and confidence it requires. That control is a permanent business need, not a one-off tool: the platform changes from SolMan to SAP Cloud ALM; the discipline, and who operates it, do not.
Working with them is very easy, thanks to the experience, the professionalism and the quality of the people they have within the organization.
Essbio —one of Chile's largest water utilities, with close to 1.2 million customers across four regions— manages a constant flow of changes to its systems, driven by new regulations and by the business areas. It needed visibility and strict control over what goes to production, with minimal operational impact. A previous tool did not deliver the expected results, and Novis implemented the one that did solve the problem — in the middle of the pandemic and fully remotely.
The Novis team was very well coordinated, we had weekly meetings, and they were accurate in the proposed solution as well as in the planning of the delivery dates.
We run the diagnosis on your SolMan and design a staged transition plan, starting with Operations — without stopping your current operation.