What are the 11 functions of ISA‑95?

ISA‑95 does not define a single, official list of exactly 11 functions. The standard defines functional categories and models (especially at Level 3, Operations Management) and then decomposes those into many activities. Different vendors and authors sometimes group or compress these activities into a list they call the “11 ISA‑95 functions,” but that list is not canonical and varies across sources.

What ISA‑95 actually standardizes

ISA‑95 provides:

• A reference functional hierarchy (Levels 0–4).
• Information models that describe what data is exchanged between business systems (e.g., ERP) and manufacturing systems (e.g., MES/SCADA).
• Activity models for Level 3 (Operations Management) that group work into four major operations areas.

At Level 3, ISA‑95 organizes functions into these core categories, not 11 fixed items:

• Production Operations Management
• Maintenance Operations Management
• Quality Operations Management
• Inventory Operations Management

Each of these is then broken down into activities such as definition, dispatching, execution, data collection, tracking, and analysis. Depending on how you count or group these activities, you might end up with 8, 10, 11, or more “functions.” That counting is interpretive, not standard.

Examples of how people arrive at “11 functions”

To illustrate where the “11” comes from, some practitioners:

• List the four operations areas above, then split each into 2–3 subfunctions (for example, Production Scheduling, Production Dispatching, Production Tracking), and stop when they reach 11.
• Start from the ISA‑95 activity diagrams and pick a subset that lines up with a particular MES product’s modules, then label those as the 11 ISA‑95 functions.

These lists can be useful for internal communication or vendor comparisons, but they are derived interpretations, not a normative part of the standard.

How to use ISA‑95 functions in a real plant

In a regulated, brownfield environment, it is usually more practical to work from the ISA‑95 activity models than to chase a specific “11 functions” list:

• Map current systems (ERP, MES, historians, QMS, CMMS, LIMS, bespoke tools) to the ISA‑95 Level 3 activities. Many plants already have some production, maintenance, quality, and inventory functions split across multiple systems.
• Identify gaps and overlaps. For example, you may discover that “Production Tracking” is duplicated between MES and a custom database, or that “Quality Analysis” is largely manual.
• Plan incremental changes. Full replacement of existing MES or ERP modules is often high risk due to validation requirements, integration complexity, and downtime constraints. Using ISA‑95 as a reference, you can target specific functions or interfaces for upgrade or consolidation while maintaining traceability.

Because of long equipment lifecycles and regulatory expectations for validated systems, treating ISA‑95 as a reference model for interfaces and responsibilities is usually more sustainable than attempting to reorganize all systems into a predefined “11 functions” structure.

Key takeaway

If a vendor or consultant references “the 11 ISA‑95 functions,” ask them to:

• Show exactly how they derive their list from the ISA‑95 models and activities.
• Map each of their named functions back to the standard’s Production, Maintenance, Quality, and Inventory Operations Management activity models.
• Explain how their interpretation fits, or conflicts, with how your existing ERP, MES, QMS, CMMS, and other systems are already partitioning responsibilities.

This approach keeps the discussion grounded in the actual standard while acknowledging that a fixed set of “11 functions” is a simplification, not a requirement of ISA‑95.