The parts your sector does differently, already written.
A generic process model is a starting point nobody actually starts from. Every implementation eventually discovers that utilities do not run field service the way manufacturers do. Those differences are 330 industry-specific processes and 2,237 variants in here already, attached to the processes they change.
Every sector process, by vertical and domain
The same tree as the standard tab, pivoted: sector first, domain second, process third. The count on each row is how much worked-out detail sits inside it.
Industry models with content today
Each of these carries processes written specifically for it, on top of the standard model underneath. Open one to see the domains it covers and the processes inside.
Telecommunications
Asset Management · Projects · Engineering
Oil & Gas
Asset Management · Business Enablers · Human Capital Management
Construction
Projects · Engineering · Human Capital Management
Gas Utility
Asset Management · Business Enablers · Human Capital Management
Electric Utility
Asset Management · Business Enablers · Supply Chain
Water Utility
Asset Management · Business Enablers · Procurement
Water Treatment
Asset Management · Supply Chain · Business Enablers
Manufacturing Aftermarket
Supply Chain · Asset Management · Engineering
HVAC & Building Services
Asset Management · Procurement · Engineering
Data Center Operations
Asset Management · Engineering · Business Enablers
Medical Device Service
Engineering · Asset Management · Business Enablers
Equipment Dealers & Rental
Supply Chain · Asset Management · Finance
Facilities Management
Asset Management · Business Enablers · Finance
Defense & Aerospace Sustainment
Asset Management · Manufacturing · Engineering
Defined, and not yet written
These verticals exist in the model with no sector-specific content behind them yet. The standard model still applies to them in full. What is missing is the variant work, which is usually what a first engagement in that sector funds.
- Field Service
- Manufacturing
- Aviation
- Robotic Support Services
Everything you can see here is real and current, the names, the structure and the counts come straight out of the ModelIFS library and change as it grows. What sits behind the license is the worked-out content itself: the execution steps, the data each one needs, the configuration decisions, the KPIs, the integration points, the workshop questions and the diagrams. That is the part you would otherwise spend a program building from nothing.
Sign in to open it