Implementer · IFS Cloud implementation management
Know who approved what, and on what evidence, in every IFS Cloud project
Key takeaways
- A project kept in files has no owner, state or history per fact; Implementer keeps each fact as a register row that has all three.
- The 24 templates of the Implementation Docs Kit (IDK) become views of those rows, generated on demand as versioned PDFs with a checksum.
- Three modes cover the life of a system: new implementation (five gates, 61 checklist items), rollout, and BAU with Evergreen updates.
- Implementer reads IFS Cloud over OData with a read-only account and never writes to it; the AI assistant only drafts, and a person approves.
- A live demo with fictitious data runs in 15 minutes and shows who decided what, when and on what basis.
An IFS Cloud project manager is asked the same questions in every steering group: which version of the migration plan is current, who approved this change, are we really ready for go-live. The answers sit in files and mailboxes, so each one takes an afternoon to reconstruct, and an audit takes longer. Implementer is the application that answers them from registers instead. It is installed in your own infrastructure, it is an independent product and not an IFS product, and this article describes what it does and what it does not.
1.Why do project facts get lost when they live in files?
A file records a fact once and has no way to say whether the fact is still true. A migration plan saved in three copies has three versions of the truth and no field that says which one the two owners agreed. The same mechanism produces the other questions every project manager knows:
- “Who approved this change, and when?” The approval is an email, and the email is in one inbox.
- “Are we ready for go-live?” Everyone has an opinion and nobody has the evidence next to the claim.
- “The update broke our customisation again.” Nothing recorded which environments differed before the update.
- “The test evidence is in someone’s inbox.” At an audit the search through mailboxes starts.
- “The consultant who knew that has left.” The reason behind a decision left with the person.
2.What is a register, and what happens to the IDK documents?
A register is a table in which every row has an owner, a state and a history. In Implementer a baseline, a risk, a CRIM item, a change request and a test result are rows. The 24 IDK templates stay in use as documents, and each one is generated on demand from the rows as a versioned PDF with a checksum, so the document for the steering group is never assembled by hand.
| Files | Registers in Implementer | |
|---|---|---|
| Current version | The copy saved last | One row with a version history |
| Approval | An email thread | A decision recorded with the person and the time |
| Go-live readiness | Opinions in a meeting | 42 criteria, with evidence references kept in the gates |
| Steering group document | Assembled before each meeting | Generated from the rows, versioned, with a checksum |
Single registers are described in the series on this site, for example the Project Management Plan (IDK-01), Change Requests and Change Control (IDK-07), Qualification Gate Checklists (IDK-08) and the CRIM Log (IDK-10).
3.Which project situations does Implementer cover?
Implementer has three modes, because the same register behaves differently in a first implementation, a second site and a running system.
- New implementation. Five gates with 61 checklist items, closed with evidence and acceptances by people.
- Rollout. What is common to all sites stays common, and local differences are recorded separately.
- BAU and Evergreen. IFS updates are managed cycles with a regression pack and a drift check.
The go-live readiness review has 42 criteria in nine groups. A person marks the criteria that have no register and gives a reason, and the approval of the review is a decision by named people, as described in the Go-Live Readiness Decision (IDK-21).
4.What does Implementer do with your IFS and your users?
Implementer reads IFS Cloud over OData with a read-only account, one account per environment, and never writes to IFS. Authorisation is checked in three places: in the API, in row-level security in PostgreSQL and in the filter of the AI search. The application runs in your infrastructure as signed container images behind one reverse proxy, without root and with a read-only file system, and users sign in with Microsoft Entra ID.
The AI assistant is optional, an administrator enables it, and it depends on a local model. It produces drafts only. Nothing is approved until a person accepts it.
5.How do you see it work in 15 minutes?
The Implementer demo is a running instance with fictitious data of a company called Alfa Metal S.A., and nothing in it touches a real IFS Cloud. The path:
- Dashboard and gates. Where the project stands and what blocks the next gate.
- Registers and permissions. CRIM and risks, and the reason shown when an action is blocked.
- One change with its audit trail. A risk that materialises creates a linked issue.
- Steering group. The pack generated from the registers.
- Go-live or updates. The readiness review, or an update cycle with the environment matrix.
The demo does not show your data, your IFS or your Entra ID. Microsoft Teams notifications and the Microsoft 365 calendar have not been tested on a production tenant, so do not judge them by the demo; they are checked in a pilot in your infrastructure.
6.Frequently asked questions
Who is Implementer for?
Implementer is for IFS Cloud project managers, PMO offices and solution architects, on the customer side or at an implementation partner.
Does Implementer write to our IFS Cloud?
No. Implementer reads IFS Cloud over OData with a read-only account and has a separate account for each environment. Nothing is installed in IFS, so an IFS update has no Implementer object to break.
Can the AI assistant in Implementer approve anything?
No. The assistant only prepares drafts that a person accepts or rejects. It is optional, an administrator enables it, and it runs on a local model.
How does an Implementer engagement start?
It starts with a 30-minute scoping call and a 15-minute demo, followed by a pilot at a fixed price in your infrastructure. The amounts are published on implementer.ifs-erp.com.
7.About the author
Dariusz Myśliwiec is an independent IFS Cloud consultant with 18 years on IFS, and the person who builds Implementer. You talk to the consultant who builds it, not a sales layer.
Clients of the IFS practice: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm · RADPOL · ATLAS.
Independent product, not an IFS product or document. IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
15 minutes, one path
Open the demo and follow one change from the request to the decision. You will see who decided, when, and on what basis. Prefer to talk first? Book a 30-minute scoping call. No pitch: you talk to the consultant who builds it. More about the product is on the Implementer page.

Deutsch (Deutschland)
Polski (PL)