Ecaldima

Modules · Change management

Change without surprises: every intervention knows its impact before it happens.

Change management governs every evolution of your information system: who requests it, which items it affects, who approves it and when it takes place. Conflicts and freeze periods are visible before, not after.

Request a demonstration Download the sheet

  • Affected items calculated from the CMDB
  • Conflicts and freezes detected on submission
  • Review required before closure

01On request

Risk, rollback and conflicts, on the same record.

Risk is assessed by impact and probability, a rollback plan is required before a normal or emergency change can be approved, and a freeze period overlapping the window blocks approval and scheduling.

Risk, rollback and conflicts, on the same record.

02Before acting

The affected items, and those that depend on them, calculated for you.

You designate the target items; their dependants are calculated by following the CMDB relationships, with the path that links them, and can be set aside. A conflict with another change on the same item is flagged on submission.

The affected items, and those that depend on them, calculated for you.

03Day to day

Every intervention window on a single calendar.

Month, week and day views, global or targeted freeze periods, emergency changes spotted at a glance; the release calendar is shown alongside.

Every intervention window on a single calendar.

The board decides, the record remains.

Immediate approval for a standard change, the board for a normal change, the emergency board for an emergency: each decision is kept with its comment, and meetings have their agenda and minutes.

No false alarms during the intervention.

During a change window, monitoring alerts on the items concerned stay visible but open no incident. And a post-implementation review is required before closure: outcome, deviations, lessons learnt.

Ecaldima is now on a par with the major American software vendors.

Our partners

Related modules

  • CMDB You choose the target items; dependent items are calculated by following the relationships in the repository, with the path that links them. A clash with another change on the same item is flagged as soon as the change is submitted.
  • Service Desk The emergency change is created from an open incident, already filled in, and the ticket shows the linked change: the agent knows which intervention is planned and when.
  • Problem management The change that fixes a problem starts from its record, with the root cause already carried over; when the change closes successfully, the record offers to resolve the problem.
  • Major incidents From the war room, the emergency change is created with the title, affected items and ticket already filled in, then goes to the emergency change board; it keeps track of the crisis it came from.
  • Release management A release groups approved changes; each calendar shows the other, and a warning appears if the deployment window falls within a freeze.
  • Project management A project, task or milestone can rely on a change: the milestone moves to “Reached” when the change is closed, with no manual update.
  • Event management: monitoring alerts During a change window, alerts on the items concerned stay visible but open no incident: the intervention does not send false alarms to the Service Desk.
Functional scope Every detail of the module
  • 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)

The essentials of this page in PDF, to keep or pass on.

Download the sheet

Want to see this module on your own processes?

We will build the demonstration around your operational reality.

Request a demonstration