A1.E22 · Equipment & Installed Base

Meter and Equipment Removal

Meter and Equipment Removal is an electric distribution utility planning process executed across FSM/FSM Connect/FSM Mobile with SAP ISU and GIS integration. It is mapped to IFS Equipment & Installed Base and comprises 25 extracted steps covering request intake, validation, site/technical work and cost/work-order handling. Provenance is the client To-Be draw.io planning flows.

59 details worked out · license requiredElectric Utility variantMaster

Execution steps

25 steps

Sign in

The sequence somebody actually follows in IFS Cloud, step by step, written for a person doing the work rather than for a diagram.

Data requirements

16 requirements

Sign in

Every entity this process needs, mapped to its IFS object, marked mandatory or optional, with the source system it comes from. This is the list a data migration is built from.

Configuration decisions

3 decisions

Sign in

The choices this process forces you to make in IFS, named up front. Finding these in week nine of a program is what makes week nine expensive.

KPIs

3 measures

Sign in

What this process is measured on, so the reporting requirement is known before the process is configured rather than after go-live.

Integration points

8 integrations

Sign in

Where this process has to talk to something outside IFS, and what crosses the boundary.

Prerequisites

3 prerequisites

Sign in

What has to be true before this process can run at all: master data, other processes, setup completed elsewhere.

Industry variants

1 variant

Sign in

How this process differs by industry: the parts a utility does differently from a manufacturer, already worked out rather than discovered.

Process diagram

1 BPMN diagram

Sign in

A real BPMN diagram, editable in the platform, not a picture of one. It is the same diagram your team will annotate in the workshop.

Sources

1 citation

Sign in

Where this came from. Every process traces back to IFS documentation and release notes, so a claim about how IFS behaves can be checked rather than believed.

Every process in the library looks like this.

59 details are already worked out for this one process. A license opens them, and the other 619 processes with them.