The library is open to browse. The work inside it is the product.
You can walk the whole structure without an account: 14 domains, 100 categories and all 865 approved process names, with the counts of what is defined inside each. A license opens the content itself, 36,477 defined details, and your own repository cut from them.
Itemized, with today's counts
Execution steps
5,469The sequence somebody follows in IFS Cloud, written for the person doing the work.
Data requirements
9,826Every entity mapped to its IFS object, marked mandatory or optional, with its source system. The list a data migration is built from.
Configuration decisions
3,928The choices each process forces, named in advance instead of found in week nine.
Workshop questions
4,710What to ask the business, drafted before the workshop. The difference between a design session and a discussion.
KPIs
3,772What each process is measured on, so the reporting requirement is known before configuration rather than after go-live.
Integration points
3,679Where a process crosses the boundary out of IFS, and what goes across it.
Prerequisites
2,856What must already be true before a process can run: master data, setup, other processes.
Industry variants
2,237How the process differs by sector, attached to the processes it changes.
BPMN diagrams
865Real diagrams, editable in the platform. The same ones your team annotates in the workshop.
Source citations
2,787Traceability back to 1,519 IFS documents and release notes, so a claim can be checked rather than believed.
These figures are read from the library as this page loads. They go up.
A license includes the repository, not only the reading
The content is one half of what a license is for. The repository is the other.
Your own repository
The modules downstream
It keeps arriving
Review a published process first.
Two processes are open end to end, one standard and one industry variant, so you can see exactly what the content looks like before talking to anyone.