Industry variants

A generic process model is a starting point nobody starts from.

Every IFS program reaches the same moment: somebody says “that is not how we do it in our industry,” and they are right. It usually happens late, in a design workshop, and the work then happens anyway at the highest possible cost and with the least possible evidence. ModelIFS carries sector differences as variants of the standard model, so industry requirements are reviewed at design rather than discovered at UAT.

330
Industry processes
38% of the library
2,237
Industry variants
Attached to standard processes
14
Verticals with content
4 more defined
535
Standard processes
Underneath all of them
The cost of generic

What a sector-blind model makes you pay for twice

None of this is exotic. It is the ordinary arithmetic of discovering an industry requirement late.

Discovery time you already spent

A workshop that surfaces a sector-specific process is a workshop that mostly re-derives what every other operator in that sector already does. The output is real and the effort was avoidable.

Rework, not configuration

An industry requirement found after the design is signed off does not add work, it replaces work. The configuration built on the generic assumption comes out again, and so does the training written against it.

Requirements nobody raised

The dangerous ones are not the requirements the room argues about. They are the ones nobody thinks to mention because everyone in that industry assumes them. They surface at UAT, from a user, as a defect.
How it is modeled

Variants of one process, not sixteen libraries

This is the design decision that makes the whole thing maintainable, and it is worth explaining because the obvious alternative fails slowly.

The obvious way, and why not

Copy the library once per industry and edit each copy. It works for about a year. Then a fix to a core process has to be applied 18 times, someone misses one, and the copies drift until nobody can say which is right. A library that disagrees with itself is worse than no library.

One process, many variants

535 standard processes carry 2,237 variants between them. A variant is attached to the process it changes and says what differs and for which sector. Alongside them sit 330 processes that exist only in an industry, because some things genuinely have no generic equivalent. Fix the core once and every sector gets the fix.

If your sector is not on the list

The standard model applies to you in full: 535 processes with everything defined. The variant layer is built as part of the engagement and becomes part of the model, so your next upgrade and the next operator in your sector both inherit it.

Defined and not yet written: Field Service · Manufacturing · Aviation · Robotic Support Services

Your industry, on day one.

Where the variant work is done, you start from it. Where it is not, it is built once and maintained in the model.