Business Model Implementation in Runtime System Landscapes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Implementing a new business model in a complex runtime system landscape without disrupting existing models is challenging, as companies seek to avoid additional system landscapes due to cost concerns while ensuring minimal risk to production systems.
Innovation Solution
A system that allows the implementation of an additional business model on an existing productive system landscape by using a landscape cloner to generate snapshots, modifying them to include the new model, and deploying the delta through a testing and deployment module, ensuring minimal impact on existing models and allowing independent maintenance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a dual system landscape is used to separate new implementation from maintenance, then production risks are reduced, but system costs increase
Solution Approach 1:
The system separates the new business model implementation into a distinct development system that is cloned from the productive system. This segmentation allows independent development and testing without affecting the productive system, reducing production risks while avoiding the need for a complete dual landscape architecture.
Solution Approach 2:
A landscape cloner is used to create a copy of the productive system's snapshot for development purposes. This copying mechanism enables the new business model to be implemented and tested in isolation, then deployed back to the productive system without requiring permanent separate infrastructure, thus reducing costs while maintaining reliability.
2Reliability
If a second system landscape is created for new business model implementation, then implementation risks are isolated, but implementation costs increase
Solution Approach 1:
The system dynamically creates and destroys development system snapshots as needed during the implementation lifecycle. Instead of maintaining a permanent second landscape, the system activates development environments only when needed for specific implementation tasks, then deactivates them, optimizing resource utilization while maintaining risk isolation.
Solution Approach 2:
The landscape cloner creates preliminary snapshots of the productive system before new business model implementation begins. These pre-prepared copies enable safe development and testing activities to be performed in advance without affecting the productive system, isolating implementation risks while using minimal resources.
3Adaptability or versatility
If the productive system is modified to include the new business model, then system versatility improves, but system stability may be compromised
Solution Approach 1:
A deployment system acts as an intermediary between the development system and the productive system. It manages the integration of the new business model by controlling the deployment process, ensuring that changes are properly validated and coordinated before being applied to the productive system, thus maintaining stability while enabling versatility.
Solution Approach 2:
The system implements feedback mechanisms where the deployment system monitors the integration of new business models into the productive system. This feedback allows for validation and adjustment of changes before full deployment, ensuring that system stability is maintained while achieving the desired business model versatility.
Data Source
AI summary
A system for adding an additional business model to an existing productive runtime system landscape is described. An additional business model is implemented on an existing productive system landscape that includes an existing business model. The productive system is maintained independently from the implementing of the additional business model on the existing productive system landscape. The additional business model is deployed in the existing business model combined within the existing productive system landscape.