Ecaldima

Modules · Change management

Change without surprises: assess, approve, schedule.

Change management governs every change to your information system: who requests it, which items it affects, who approves it and when it takes place. Each change keeps its decision and its review.

Request a demonstration

Benefits

  • Impacts known before actingThe items affected, and those that depend on them, are worked out from the relationships in the CMDB.
  • Clear, traceable decisionsThe board decides from the record or in session; each decision is kept with its comment.
  • Conflicts avoidedChanges that overlap on the same item are flagged as soon as they are submitted, and freeze periods are respected.
  • Lessons retainedA post-implementation review is required before closure: outcome, deviations and lessons learned.

How it works

01

Request

Change type, description, justification, rollback plan and a risk assessed by impact and likelihood.

02

Assess

The affected items are identified; their dependants are calculated and can be set aside.

03

Approve

Immediate approval for a standard change, the board for a normal change, the emergency board for an emergency.

04

Implement

The change is scheduled in a window, carried out, then closed after its review.

Related modules

  • CMDB The impact assessment follows the relationships in the repository.
  • Service Desk An incident can be linked to a change, and an emergency change can be created from an open incident.
  • Problem management A problem is resolved by a change; the link can be read from both sides.
  • Major incidents A major incident can lead to a pre-filled emergency change.
  • Release management A release groups approved or scheduled changes.
  • Project management A project or a milestone can rely on a change.

Functional scope

  • Three change typesStandard, normal and emergency, each with its own approval rules; further types can be created, named in each language.
  • Governed life cycleFrom request to closure; a rollback plan is mandatory before a normal or emergency change is approved.
  • Approval workflowsApproval by a board or by a multi-level workflow, with conditions on risk, deadlines and delegation.
  • Impact on the repositoryAffected items and dependants calculated automatically, with the path that links them.
  • Calendar and freezesMonth, week and day views, global or targeted freeze periods, detection of scheduling conflicts.
  • Board meetingsAgenda, decisions taken in series, minutes and a frozen closure.
  • Management reportingSuccess rate, emergency changes, rollbacks, approval time, risk matrix and a Kanban board.
  • RemindersThe requester and the owner are notified before the implementation window starts.

Integrations

  • CMDB repository, for the impact assessment
  • Process engine, for approval workflows
  • E-mail and in-application notifications, with editable templates
  • AI assistance to assess risk and draft text, when the AI module is configured

Prerequisites

  • The approval board and emergency board groups, to be designated
  • The CMDB repository, so that impact can be calculated (optional)

Want to see this module on your own processes?

We will build the demonstration around your operational reality.

Request a demonstration