Learn

Glossary: IDK, CRIM, gate, BoR, Evergreen and more

This glossary defines the terms used on this site: IDK, CRIM, Book of Rules (BoR), gate, rollout, BAU, Evergreen, register, hypercare, projection, OData and RLS.

What do the terms mean?

The definitions describe how the words are used in Implementer and in the Implementation Docs Kit. They are written for this site and are not official IFS definitions.

IDK (Implementation Docs Kit)

IDK is a set of 24 independent templates for IFS Cloud implementation projects, numbered IDK-01 to IDK-24, published by Dariusz Myśliwiec at IFS-ERP. Implementer runs each template as a register or a generated document. See the IDK kit page.

CRIM

CRIM stands for configuration, report, integration and modification. A CRIM object is a requirement that needs work in IFS Cloud, and the CRIM log (IDK-10) is the hub of the project. Each object links to its specification, interface, test scenarios, handover and update review, and carries a tailoring level that drives update effort: standard, configuration, interface extension or modification.

Book of Rules (BoR)

The Book of Rules (IDK-09) is the register of business rules per process area, with decisions, exceptions, open questions and sign-off by the process owner. A rule that cannot be met by standard IFS Cloud becomes a CRIM candidate.

Gate

A gate is a decision point at the end of a project phase. The IDK uses five qualification gates: Project Initiated, Solution Confirmed, Solution Established, Go Live Authorised and Go Live Complete. They have 14, 13, 11, 13 and 10 checklist items, 61 in total. A gate decision is Approved, Approved with conditions or Not approved, and conditions become tasks with an owner, a due date and a verifier.

Go-live readiness

The go-live readiness review (IDK-21) has 42 criteria in nine groups, most of them read from testing, migration, cutover and training records. The decision is Go, Go with conditions or No-go.

Register

A register is a table of rows that each have an owner, a state and a history, such as risks, issues, CRIM objects, interfaces or test cycles. In Implementer registers are the source of truth and documents are generated views over them.

Project mode, rollout, BAU and Evergreen

A project has a mode: new implementation (all five phases and gates), rollout (extending a live solution to another site, country or business unit) and BAU (business as usual after go-live). Evergreen is the IFS Cloud model of continuous service and release updates, and in Implementer each update is a managed cycle.

Cutover

Cutover is the controlled switch from the old systems to IFS Cloud, planned in IDK-20 with runbook tasks, rehearsals, a go/no-go checkpoint and a point of no return.

Hypercare

Hypercare is the period of intensive support just after go-live. Implementer records it in the handover (IDK-22) with its window and on-call roles.

Projection and OData

An IFS Cloud projection is the API surface through which IFS exposes data. OData is the protocol used to read it. Implementer reads projections through OData for the environment matrix and drift checks, with OAuth2 client credentials, and never writes. Implementer also offers its own read-only OData feed with personal tokens.

RLS (row-level security)

Row-level security is a PostgreSQL feature that restricts which rows a database user can read or change. Implementer uses it as one of three authorisation layers, next to the API and the AI retrieval filter. See security and trust.

Audit trail

The audit trail is the log that records who changed what, when, and from which source: UI, API, AI, import or sync.

Where do you go next?

Read the FAQ, the product page or book a scoping call.

Last updated:

Ready for a pilot?

A 30-minute scoping call and a 15-minute demo on demo data.

Book a scoping call