Implementer runs an IFS Cloud implementation project from registers instead of documents. Risks, issues, change requests, CRIM objects, interfaces, test cycles, cutover tasks and the rest of the Implementation Docs Kit are rows with an owner, a state and a history. The kit templates become views over those rows. It supports a new implementation, a rollout to a new site, and BAU with IFS Cloud updates.
Who it is for and when
IFS Cloud project managers, solution architects and customer PMOs who have a project plan and a set of templates, and who find that the Word and Excel copies drift apart by the second steering meeting. The usual trigger is one of these: a gate decision is coming and nobody can show the evidence, the CRIM log and the interface list disagree, or an update cycle starts and the regression set lives in someone's mailbox.
The promise
You can answer "what is open, who owns it and what did the steering group decide" from one place, and every gate decision points to the rows that support it.
What is included
All 24 kit templates have a register or a generated document behind them. Each is described, with screenshots and the steps a user follows, on its own page:
- Project Management Plan: baselines, milestones and assumptions (IDK-01)
- Scope, organisation and RACI, communication plan (IDK-02, IDK-03, IDK-05)
- Risk register, issue log, change requests (IDK-04, IDK-07)
- Steering group pack with a generated, versioned PDF status report (IDK-06)
- The five qualification gates with 61 checklist items (IDK-08)
- Book of Rules, CRIM log, functional and configuration specifications, interface register (IDK-09, IDK-10, IDK-11, IDK-12, IDK-13)
- Data migration, testing, guides, training (IDK-14 to IDK-19)
- Cutover, go-live readiness, handover, updates, closure (IDK-20 to IDK-24)
Platform functions that apply to all of them:
- One way to change state. A transition runs the same guards whether it comes from the screen, the API or an import, and every change is written to an audit log with the user, the time and the source.
- Approvals with rules per project: who may approve, how many approvers, and what blocks a request.
- Access by project membership and role. A project you do not belong to is not visible to you.
- Polish and English interface, light and dark theme.
- Environment list and matrix: what is installed where, in which IFS version, with read-only OData checks against each environment through its own OAuth2 client.
- Runs in your infrastructure as Docker containers behind a reverse proxy. Sign-in through Microsoft Entra ID.
How it works
- Scoping call and a short fit check against your project mode and the templates you already use.
- Installation in your environment and first-time setup: Entra ID tenant, first administrator, project created with its gates and checklists.
- Loading your project: members and roles, baselines, scope, the risks and CRIM objects you already have.
- Handover: a working session with the project team, then the per-template pages as the reference for daily use.
Price
Start with a 90-day pilot on one project: €9,500, including installation in one environment. The first three pilots cost €6,900. The pilot fee is credited against the first-year licence (up to its price).
Annual licence per project, up to 25 named users, with updates and email support: €12,000 for a new implementation, €7,200 for a rollout, €4,800 for BAU and Evergreen updates. Additional users €25 per month each, a further environment €2,000 per year. Prices are net, in EUR, plus VAT.
Risk reversal
The data stays in your database and your file store. The registers are readable through the API, so leaving is a data export and not a migration project. Support, payment terms and host sizing are on Implementer: commercial terms, support and host requirements.
What it does not do yet
- No Gantt chart. Milestones and baselines are available, the schedule view is not.
- No AI assistant. It is planned, and AI would only draft for human approval.
- No write access to IFS Cloud. The IFS integration reads only.
- DOCX export of generated documents is not available. PDF is.
Next step
Implementer is an independent product and is not an official IFS document or product. IFS is a registered trademark of IFS.

Deutsch (Deutschland)
Polski (PL)