ModelIFS

An IFS implementation is only as good as the process model it is configured from.

Most programs configure the software and write the process down afterwards, if at all. ModelIFS is the other order: a leveled reference model of IFS Cloud service management, with the industry variants already worked out, that your repository is cut from and your configuration traces back to.

865
Approved processes
175 more in review
36,477
Details worked out
Steps, data, decisions, KPIs
15
Industry verticals
2,237 variants attached
865
BPMN diagrams
Editable, not screenshots

Read from the library as this page loaded. Unreviewed content is excluded from every figure on this site.

The argument

The cost is not the software. It is starting from nothing.

An IFS program spends its first months turning conversations into a process document, and its next months discovering the configuration decisions nobody made. Both are avoidable, and neither is avoided by buying a better license.

Leveled, not listed

Level 1 down to the execution step, so a workshop can be held at the altitude the room needs, and a decision taken at Level 3 stays attached to the Level 1 process it belongs to.

The questions come first

4,710 workshop questions are already drafted against the processes they belong to. The first session is a structured review of known options, not open discovery.

Variants, not exceptions

Utilities do not run field service the way manufacturers do. Those differences are recorded as variants of one process rather than as 19 separate libraries that drift apart.

A repository per client

A program works in its own copy: scoped, versioned and traceable back to the reference model. Every divergence carries a recorded reason, which is the first question every upgrade asks.

Managed from day one

9,826 data requirements are mapped to their IFS objects and marked mandatory or optional. That is the migration scope, available before anybody builds a spreadsheet for it.

Checkable

2,787 citations back to 1,519 IFS documents and release notes. Every statement in the model can be verified against its source.
The library

Browse all of it. Every name, every count.

You do not need an account to see what is in here. The structure and the process names are open; the worked-out content behind them is what a license opens.

All 14 domains and 100 categories
Open samples

Two are open all the way through

One global backbone process and one industry variant, with nothing held back: every step, every data requirement, every decision and every workshop question. Evaluate the depth of the model directly.

Trusted by service organizations running IFS
IFS
Enbridge
Tetra Pak
Spencer Technologies
Seven Seas Water Group
ST Engineering
Olameter
Lely
Hexagon Agility
TDC Net
Telstra
Hunter Water
In their words

Delivered by the team behind 45+ IFS Service Suite implementations.

“Service NextGen brought the deep IFS Service Suite experience and the program discipline we needed. They felt like part of our team from day one, not a vendor.”
Matt Gutschow, Director, Customer Service Programs, Hexagon Agility
Part of the Service NextGen platform for IFS Cloud

One platform. Three products.

ModelIFS is the source of record. AdoptIFS and LearnIFS read from it, so change management and training are built from the same processes the program is configured from.

Implemented by Service NextGen, IFS Service Suite partner, 45+ implementations.

Built for regulated, asset-intensive operators

Enterprise controls, included.

SCIM provisioning

Users and seats managed from your own directory through the SCIM 2.0 endpoint.

OData API

Read the repository from your own reporting and integration tools over OData v4.

Versioned content

Every process, template and course carries a full change history.

Role-based access

Internal and client users are separated by design and enforced with row-level security. Clients see their own repository only.

Isolated client repositories

Each engagement works in its own scoped copy of the model, traceable to the reference.

Start your program from the model.

865 processes and 36,477 defined details are ready today. A 40-minute session against your program’s scope. No slides.