Implementer help

Every help topic of the Implementer application, grouped by project stage.

System and project configuration

  • Guide: set up the system and the project: Do this once per installation and once per project, before phase 1. It makes the app safe to use and the project ready for people.
  • Approval rules: See who must approve which change. The rules come from the methodology pack.
  • Privacy and erasure: Ask to erase a person’s data, and approve such requests. Records that the law requires stay, in anonymous form.
  • Methodology pack upgrade: Move the project to a newer version of the methodology pack. See what changes before you confirm.
  • Notifications: Choose how you are told about approvals, gates and other events. Project administrators set the channels of the project.
  • My profile: Connect your Microsoft 365 calendar so Implementer can find a free time for meetings, and create tokens for Excel and Power BI. Both are optional.
  • Project members: Add people to the project and give each one a role. Roles decide what they can see and do.
  • API tokens: Let a reporting tool read project data without a person signed in. A token only reads, and it expires.
  • New project: Create a project and choose its kind. Only a platform administrator can do this. The kind shapes the whole project.
  • Administration: System settings for the whole installation: sign-in, storage, AI, IFS connections and the methodology packs.
  • First-time setup: Set up a new installation step by step. When done, the first admin signs in.
  • Licence: The signed licence file of this installation. The app checks it offline and sends nothing anywhere.
  • Error log: Server failures and errors reported by browsers. Administrators use it to find the cause of a problem and to brief support.
  • AI policy: Decide which external model providers this project may use, and with which data. Without an approved policy all AI runs locally.
  • AI providers and models: Register external model providers and choose the local chat and embedding models.
  • Extensions: Install services that receive a signed notice when something happens in a project that allows them.
  • Sign in: Sign in with your company account. The app does not keep your password.

Phase 1: Initiate project

  • Guide: phase 1, Initiate project: Both teams start. You set up the plan, the scope and the controls, and you close the phase at the Project initiated gate.
  • Plan and baselines: The project schedule with milestones and four baselines. A baseline is a signed copy you measure against.
  • Scope: What the project delivers and what it does not. Includes benefits, processes, data, interfaces and exclusions.
  • Organisation and RACI: Who is on the project, what role each person plays and who is responsible for each activity.
  • Steering group: Meetings, decisions, actions and the status report. This is where the project is governed.
  • Communication plan: Who needs to hear what, how often and from whom. Includes the stakeholder list and the meeting calendar.
  • Environments: PROD, TEST, training and other IFS environments. See the version of each and what is planned next.

Phase 2: Confirm prototype

  • Guide: phase 2, Confirm prototype: You build key processes on customer sample data and confirm the solution scope. The Solution confirmed gate closes the phase.
  • CRIM log: CRIM stands for configuration, report, integration and modification. Every tailored object gets a line here, so its update and test cost stays visible.
  • Interface register: List every link between IFS and another system. Decide what happens to the old system at go-live.
  • Book of Rules: The agreed business rules for each process area, with their exceptions and open questions. The process owner signs it.

Phase 3: Establish solution

  • Guide: phase 3, Establish solution: You finish design, build and tests. The phase ends with acceptance testing and the Solution established gate.
  • Defects: A defect is a fault found in testing. Log it, rate its severity and follow it until it is fixed and checked.
  • Data migration: Plan what data moves, clean it, and load it in cycles until the customer accepts it.
  • Specifications: Write down what you will build before you build it. One kind covers links and changes. The other covers settings and reports.
  • Testing: Test cycles, scenarios, runs and defects. Ends with the acceptance test (SAT) and the operational readiness test (ORT).
  • Step-by-step guides: Short guides that show users how to do a task in IFS Cloud. Used for tests, training and support.

Phase 4: Implement solution

  • Guide: phase 4, Implement solution: You train users, rehearse the cutover and pass the operational readiness test. The Go live authorised gate closes the phase.
  • Training: Who needs training, which courses, and when. Attendance is personal data, so only a few roles see it.
  • Cutover: The plan to move from the old system to IFS Cloud. You rehearse it with full data. Durations come from the rehearsals.
  • Go-live readiness: The paper the steering group reads before it authorises go-live. It scores the readiness criteria and ends in one decision.

Phase 5: Go live

  • Guide: phase 5, Go live: You run the cutover, retire the old system, hand over to support and close the project. The Go live complete gate closes the phase.
  • Handover to support: Give the support team everything it needs. They check the pack and accept it.
  • Project closure: Close the project cleanly. Give every open item an owner outside the project and record what you learned.

Phase 6: Maintained after go-live

Every stage

  • How an IFS Cloud project runs: An IFS Cloud project has five phases. Each phase ends with a gate. The steering group opens the gate, and only then does the next phase start.
  • New project, rollout or BAU: The app supports three kinds of work. You choose one when you create the project. The kind decides which phases and screens you see.
  • Roles and who may do what: Your role decides what you can see and do. Some actions need a second person. Nobody approves their own work.
  • Dashboard: Your overview of the project. See where you are, what is late and what waits for you.
  • Registers and boards: A register is the single list of one kind of object, such as risks or change requests. Show it as a board or as a list.
  • Object panel: The side panel for one item. It has fields, links, attachments and the full history.
  • Risk register: Track what could go wrong, how likely it is and what you will do about it.
  • Issue log: An issue is a problem that exists now. Log it, give it an owner and close it with a result.
  • Change requests: Use a change request when scope, date, budget or a modification must change. No work starts before approval.
  • Approvals inbox: All decisions that wait for you, in one list. Approve, reject or send back with a reason.
  • Delegations: Hand your approvals to someone else for a set time, for example during leave.
  • Qualification gates: A gate closes a phase. The team shows evidence for each checklist item. The steering group then approves, approves with conditions, or rejects.
  • Documents: IDK documents built from the registers. You do not type tables into them. You change the register, and the document follows.
  • Content search: Find items by what their fields say, not only by their key. You see only the types you may read.
  • Audit log: Every change to project data, with who, when and where it came from.
  • Scheduling meetings: Find a time that suits the participants, for example for a user acceptance test session. The server proposes times and a person confirms one.
  • Import a register from CSV: Load a list you already keep in Excel into a register. Nothing is saved until you confirm the last step.
  • Export project data: Download the registers of the project as one zip archive. Excel and other tools can open it. Use it for your own analysis or for an exit.
  • Transport register: A transport is a package of IFS configuration that moves between environments. The app records it and checks the rules. It never applies anything to IFS.
  • Reports: Run ready-made reports or build your own. A report reads the registers, so it is always up to date.
  • Calendar: Dated items of the project, day by day. Open an item to change its date in its own register.
  • Ask the project: Ask questions in plain words. Answers use only the documents and registers you may see, with sources.

Last updated: