How it works

The model comes first. Everything downstream reads from it.

An IFS Cloud program makes several hundred configuration decisions. ModelIFS names them before the program starts and keeps them in a structured repository, so change management and training are built from the same source as the design.

4,710
Workshop questions
Written before the workshop
3,928
Configuration decisions
Named, not discovered
9,826
Data requirements
Mapped to IFS objects
3,679
Integration points
Known at design time
The argument

Not starting from zero is the whole point

Two programs can license the same IFS Cloud footprint and have entirely different first six months. What they start with decides it.

Starting from zero

A blank workshop agenda. Somebody senior spends three months turning conversations into a process document that is out of date before it is signed off, and the configuration decisions surface one at a time, each one a small surprise with a cost attached.

Starting from the model

865 processes already leveled, with 4,710 workshop questions already drafted. The first workshop is a review of known options, not a discovery session.

And then it is yours

Your repository is a copy, not a link. You change what does not fit and the model underneath stays intact, so every divergence is visible and explained, which is the first question every upgrade asks.
The sequence

Model, then adopt, then learn

These are three products because they are three jobs. They are one platform because the second and third are impossible without the first.

  1. ModelIFS

    Decide what the process is

    A repository is cut from the reference model, and the fit/gap work happens against something concrete. What comes out is not a slide deck. It is a structured knowledge base of how your organization is going to run, process by process, with the data and the decisions attached.

  2. AdoptIFS

    Move the people onto it

    Change management needs to know who is affected by which process. That is a question the repository can answer and a document cannot. Personas map to processes, readiness is measured per person, and the communications plan is built from the same source as the design.

  3. LearnIFS

    Train against the real thing

    Training content built from the process library says what your people will actually do, not what the software can do in general. When a process changes, the material that teaches it is already linked to it, so you know what to re-record instead of guessing.

The library is not a document set. It is the knowledge base that makes the change management and the training possible. Everything downstream reads from it.

Provenance

Every claim traces back

A reference model is only useful if you can check it. Each process carries citations to the IFS documentation and release notes it was built from.

2,787
Source citations
1,519
Distinct sources
865
BPMN diagrams

Content still in review is not published. 175 processes currently in review are excluded from the library and from every figure on this site.

See the structure. Then see inside it.

The library is open to browse in full: every domain, every category, every process name and how much is defined inside each one.