Ensure high system availability
In an IT system landscape, availability is the ability of a system to be functional when used in order to perform specific business operations. Imagine you go to the supermarket; you buy your groceries and you decide to use the self-pay, once you get in front of the scanner, you
notice that the system has an error and you are not able to use it, meaning that you need to either ask for assistance or go to the normal line to pay for your groceries. This will be an example of the non-availability of a system.
What is system availability?
System availability is calculated by dividing uptime by the total sum of uptime and downtime.
Availability = Uptime / (Uptime + Downtime)
In our example, the supermarket is open for 8 hours, and we lost 30 minutes by not being able to use the self-pay.
Availability = Uptime / (Uptime + Downtime) = 8 hrs / (8hrs + 0.5 hrs) = 8 / 8.5 = ~94%
What are the effects of non-availability for SAP IBP?
- End users lose confidence in the tool,
- Critical operations might be impacted (i.e., if the Supply Plan is released at a specific date and time, non-availability of the system can impact the production, capacity plan),
- Incorrect inputs/outputs (i.e., snapshots might not be taken at the right moment, which may cause incorrect performance indicators to be captured),
- Loss of data (i.e., if the Data Agent in CPI-DS is not configured considering high availability, integration jobs may fail),
- Manual rework (additional work from planners to correct any bug that the non-availability has generated)
What are some causes for poor availability in SAP IBP?
- Increase in the number of users
- Increase in the amount of data
- New change request coming through
- External systems dependencies
- Bug fixes, Quarterly updates
- Technical Complexity
- Downtimes for configuration transports, system activation, maintenance
How to improve SAP IBP application availability?
- Always think about scaling (i.e., if you start with the implementation of SAP IBP Demand Planning, consider to roadmap if other applications will be required)
- Think Failure in mind (i.e., data loads from the external system could increase, which can cause integration jobs to fail due to higher limits being reached)
- Mitigate Risk (Ensure that plans are available to respond to availability issues in a predictable and defined way)
- Monitor availability (by keeping track of your downtime you can analyze your system performance)
- Optimization (i.e., if new functionalities are available to improve runtimes, make a plan to install them)
Krypt is an SAP preferred partner and has assisted in the success of global businesses across industries & geographies. We have helped businesses through the successful integration & implementation of SAP IBP, SAP GTS, SAP TM, and SAP EWM.
Krypt is offering up to 8 hours of Free Consulting via Krypt Concierge; check out our Krypt Concierge brochure to learn how we can help you in your SAP IBP journey.
And, to know more about our products/services, please request a free demo or contact us.
Follow us on:
Image Credit: Pixabay