26R1 for a 150-700 person manufacturer

• IFS Expert Inc. (principal) • 8 min read • IFS Cloud 26R1

IFS Cloud 26R1 went generally available on 28 May 2026. If your site still describes "IFS Cloud" as a static platform, you are a release behind. This note is the use / ignore / not-yet map we now include in the Executive Assessment. It is not a feature dump.

IFS's own 26R1 story is about control and traceability in the operational margin, not another 200-feature list. That is the right instinct for a mid-market plant. The mistake is treating every named 26R1 item as equally relevant to a discrete manufacturer with a one-person IFS bench.

Use now (if the process exists)

  • MRP simulation. Test demand against constraints before you freeze a plan. Useful where planners currently run a shadow spreadsheet.
  • CPQ. Only if you already sell configured product and the quote-to-order path is painful.
  • First-article inspection. Real if you already do FAI. 26R1 calls out AS9102C. Do not invent an aerospace program you do not run.
  • Work safety / permits. If permits currently live in email, this is operational, not EHS brochureware.
  • Technician execution portals and Service Projects. For installed-base service, not for a pure make-to-stock shop.
  • Copilots already in the estate. Sales Quotation, Shipment Order, Customer Order. Formless interaction if you are on 25R2+. Token consumption is a governance question, not a toy.
  • CRM for Microsoft Teams. Only if sales already lives in Teams and the CRM record in IFS is the source of truth.

Ignore for now (unless you are actually in that business)

  • Aviation JIT inventory, fault troubleshooting, asset configuration transfer.
  • EAM compatible units and FERC reporting.
  • IFS Zero as an emissions operating system. It launched with 26R1. For most 150-700 person manufacturers the honest job is still "stop doing emissions in six spreadsheets," not a Scope 3 OS. We will brief. We will not productize Zero delivery until we have done the work.
  • IFS.ai Operational Intelligence as an add-on across ERP/EAM/SCADA/historians. Interesting. Not a first sprint.
  • Nexus Black. IFS's lab. Not a boutique SKU.

Prerequisite data, or do not bother

Copilots and Digital Workers fail on dirty customer, part, and location data. If address, UoM, and order-status definitions are still tribal, spend the next 30 days on BPA and master data, not on enabling a worker. That is also why Crystal-to-RDL and reporting definitions belong on the 26R1 path: the worker can only act on what the data says.

Evergreen is now the support model

Cadence is twice-yearly Cloud releases plus monthly service updates. 25R1 (Apr 2025) to 25R2 (Nov 2025) to 26R1 (May 2026). Staying current is an adoption problem, not a heroic upgrade program. If you cannot name a 26R1 owner inside the plant, the Fractional Solutions Architect engagement exists for that.

The offer

Executive Assessment, CA$130 per hour. Two weeks. Written brief. Includes this use / ignore / prerequisite map for your operating model. If the map says a Digital Worker is plausible, the IFS.ai Readiness Sprint is the next engagement. If it says BPA, that is the Workflow Automation Sprint.

Sources

Request an Executive Assessment

CA$130 per hour. Two weeks. Written brief, including the 26R1 use / ignore / prerequisite map for your operating model.

Request an Executive Assessment