Guide: after go-live, keep the system current
IFS Cloud updates arrive on a regular rhythm. You plan each one so that tailored objects and interfaces keep working.
This page applies to the Maintained after go-live stage.
Project manager guide
Take every IFS update through the same checked cycle, with a recorded decision and a confirmed backup before production.
- Agree the update policy.
- Do now: Open Updates. Choose the rhythm, the roles, the environments and the freeze periods. Send the policy for approval.
- Why: A policy turns every update into routine work instead of a debate.
- The app checks: The policy needs approval. The calendar shows conflicts between cycle windows, data refreshes and freeze periods.
- Next: Open a cycle for the next release.
- Plan the cycle.
- Do now: Create an update cycle for the release. Name the coordinator, link the verification environment and set the window.
- Why: One cycle gives you one record of what was checked and decided.
- The app checks: Only the system owner, IT manager, customer project manager or a supplier design role can plan it. Verification runs in an active environment that is not production.
- Next: Check the impact.
- Check CRIM objects and interfaces.
- Do now: Start verification. Re-verify each delivered CRIM object and each interface that is kept or new. Record every result.
- Why: Every tailored object can break in an update.
- The app checks: The cycle shows the latest result of each check, and the IFS check of the interfaces. A person records the results.
- Next: Retest on TEST.
- Retest the regression pack.
- Do now: Create a regression cycle from the pack and run it. Fix the open defects.
- Why: The pack is the list of scenarios that must still work.
- The app checks: The cycle can be submitted only when its linked regression cycle is closed.
- Next: Ask for the decision.
- Decide and approve.
- Do now: Submit the cycle. Write the decision and the reason.
- Why: Your decision protects production and explains later why you updated or waited.
- The app checks: In a BAU project IT governance approves. Otherwise the system owner and then the steering group chair decide.
- Next: Record the backup.
- Back up, update production and log it.
- Do now: Record the production backup. A second person confirms it. Then apply the update and record it.
- Why: The backup is your way back if the update fails.
- The app checks: The person who recorded the backup cannot confirm it. Apply is possible only after the confirmation.
- Next: Start again with the next release.
Related topics
Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.
Last updated: