Eqeep configures, builds and tests IFS Cloud with your experts against an approved design. We migrate data and guide go-live from a signed-off Solution Design and a project plan with milestones. CRIM documentation records the decisions on Configuration, Reports, Integrations and Master Data.
What does an IFS implementation involve?
IFS implementation follows analysis and design. Eqeep configures, builds and tests the agreed design with your own experts. We plan the handover to maintenance and support after go-live.
Eqeep is an IFS Specialized Partner in the Benelux. Our IFS Cloud implementation work covers enterprise resource planning (ERP), enterprise asset management (EAM) and field service management (FSM).
How does an IFS implementation run, from design to go-live?
Eqeep reviews the fit-gaps, plans the work, builds the system and tests it with your key users. Your team approves the design and gives the final sign-off before go-live.
Review the fit-gaps before building. Eqeep turns the functional design into a technical design with your key users. Green confirms the standard fit; orange needs a process or configuration choice; red needs a decision on how to proceed. Your team approves the choices in the Solution Design before building starts.
Plan every step to go-live. The Work Breakdown Structure (WBS) sets out the work needed to bring IFS into use. Eqeep uses it to build the schedule, budget and project plan with milestones.
Build the agreed design and record the decisions. Eqeep configures IFS Cloud with your experts, sets up integrations, structures master data and migrates data from the previous system. We record the configuration choices in CRIM documentation covering Configuration, Reports, Integrations and Master Data. What the system supports depends on the design, available data and IFS product.
Test daily tasks with your key users. Eqeep and your key users test the complete solution against the agreed requirements and their daily work. Your key users review the findings; your team gives the final sign-off before go-live.
What do you receive from an IFS implementation?
Key user workshops
Workshops with key users from each department to review their processes and requirements.
Solution Design
A Solution Design that records the agreed IFS configuration and requires your sign-off before building.
Project plan
A project plan that sets out the work and milestones for implementation.
CRIM documentation
CRIM documents covering Configuration, Reports, Integrations and Master Data.
Master data
Master data structured for the agreed processes and industry requirements.
How do key users get involved in an IFS implementation?
Your key users join department workshops, decide on fit-gaps and test the solution before go-live.
If Eqeep has completed analysis with your team, we bring those findings into the workshops. Your people review the design against the work they do.
Key users explain their tasks, challenge assumptions and check the proposed configuration. After go-live, training and education support them in their own roles.
Questions about IFS implementation
How long does an IFS Cloud implementation take?
IFS Cloud implementation time depends on scope, sites, custom code and data quality. Optronica’s historical IFS Field Service Management project took about four months, including migration and integration with AFAS. Analysis and design establishes the plan for your own project. Read the Optronica story.
Is data migration part of the implementation?
Yes. Eqeep migrates data from your previous system during the build, and your key users check it during testing. At Optronica, migration formed part of the approximately four-month IFS Field Service Management project.
We're leaving IFS Applications 10, SAP ECC or JD Edwards. Is that a new implementation?
Moving from SAP ECC or JD Edwards to IFS Cloud is a new implementation. Eqeep plans the design, build, data migration and testing with your team; see SAP ECC6 and JD Edwards migration. For IFS Applications 10, compare a technical upgrade with reimplementation; see technical upgrades.
Can we start directly with implementation?
Yes. Eqeep reviews your existing blueprint or active project through a compact design process with your team. We recommend checking transaction data alongside interviews before building. If an existing project is at risk, see IFS project rescue.
What does an IFS implementation deliver?
Eqeep delivers a signed-off Solution Design, a project plan with milestones, CRIM documentation and master data structured for your industry. Your experts take part in configuration, building and testing. Key users review the solution; your team gives the final sign-off before go-live.
How does Eqeep handle the IFS go-live?
Eqeep plans go-live after testing the solution with your key users. They check the agreed requirements and daily tasks. Your team gives the final sign-off before go-live. After go-live, support and optimisation continue.
What is CRIM documentation?
CRIM stands for Configuration, Reports, Integrations and Master Data. Eqeep records the implementation’s configuration choices in these four documents. Your team can review what was set up and why.
This article describes one of the five phases in our approach. Want to discuss where your organisation stands? Discuss your IFS question.
New articles appear in our newsletter. Subscribe to the newsletter.
