Our drive is to optimise IT Service Delivery through automation and orchestration of workloads and systems

The iCiber Release Cycle © supports the structured approach for Automation and Orchestration of workloads and systems . The six phases are standardised to deliver structured and predictable outcome. At first we start with Identifying the use cases which would result in the highest value (not always money) when being automated. Next to monatery value it also delivers high quality, consistency & auditability. All identified items are part of the automation backlog and will be Categorised. We recognise the following categories:

  • Change (Service Requests, Change Requests)
  • Operations (Health checks, Compliancy checks, Security checks, Desired State check)
  • Intelligent Reporting
  • Incident (Client configuration checks, Automated remediation)

Once we categorised the items and selected the ones with the highest value we start designing the automation flow and will Innovate the execution by adding happy flow and unhappy flow scenarios. This will ensure execution robustness and reliable & auditable outcome. Once the preparation is done, the flow is approved by the case owner, the automation scrum team will start Building the automation using our automation & orchestration platform. Before releasing any product, the outcome, error handling and logging are checked and Evaluated using a DTAP cycle with appropriate approvals per stage. As final step the runback will be Released into production to start collecting the savings and improvements.

From iCiber experience we see time savings, compared to manual execution, of on average 99%. These savings are reported based on the execution logging using the iCiber Framework. Below you can see and example from one of our standard reports.

Pasted Graphic 6.tiff



Share This Post:

Steven Frisart