Independent IFS Cloud practice · Implementation
Key takeaways
Most articles about ERP business impact are written from the brochure. This one is written from the projects. I have spent seventeen years inside IFS, from Apps 7.5 through Cloud, and the pattern that repeats is not that companies pick the wrong system. They pick a capable one and then implement it in a way that throws the capability away: a template nobody reuses, an automation layer nobody trusts, reports rebuilt one for one from the old system because nobody had the authority to delete any of them.
So this is not a list of what IFS Cloud can do. It is a walk through the places where a decision taken during implementation determines whether the platform pays for itself or just replaces one kind of manual work with another. Where a topic deserves its own treatment, I have linked to the longer piece on the ifs-erp.com blog rather than compressing it into two sentences here.
Grouping sites so they share parts, defaults and process setup is sold as a speed feature. It is really a consistency feature, and the speed is a side effect. When site four inherits the purchasing parameters that sites one to three already run on, you are not just saving a week of configuration. You are removing the possibility that site four quietly does receiving differently, which is what costs you two years later when someone tries to compare performance across the group and finds the numbers are not measuring the same event.
The catch is that a cluster only helps if the template being cloned is one somebody defended. Rolling out a bad standard quickly is worse than rolling it out slowly, because a slow rollout at least gives each site a chance to object. I ask for the template to be signed off by the person who will own the process across all sites, not by the site that happened to go first. That is also where the multi-site purchasing decisions belong: whether demand consolidates centrally, and how stock moves between sites once it has.
Further reading: centralised purchasing in IFS Cloud, distribution orders between sites, and from planning to go-live.
IFS Cloud gives you three tools that cover most of what people used to write code for, and knowing which one to reach for is the whole skill. A Quick Report reads data out: a saved query for a list or an extract, with no logic. A Custom Field stores something the standard data model does not. A Custom Event reacts when a row changes, and can hand off to a Workflow that routes an approval, sends a notification, or calls out to another system.
The failure mode is predictable. Teams discover Custom Events, like them, and attach one to everything. Six months later there is an event layer nobody can explain, firing on saves that were never meant to be significant, and the business has learned to ignore the notifications it produces. The second failure mode is subtler: reaching for a Custom Event when the requirement is actually a scheduled check. An event fires when a row changes. It cannot fire because a row has not changed, which is exactly what an unconfirmed order or an untouched receipt is.
Where the requirement crosses a system boundary, the answer is usually an interface rather than an in-system automation. IFS Cloud's OData projections are the normal integration surface, and keeping the orchestration outside IFS keeps that logic out of your ERP, where it would otherwise become one more thing to retest at every release.
Further reading: Custom Events explained, Quick Reports vs Custom Fields vs Custom Events, IFS Cloud API integration, orchestrating IFS Cloud with n8n. Work that has already been built once sits in the configurations and interfaces sections of the marketplace.
IFS Cloud ships R1 and R2 every year. That cadence is the biggest single change in how you should think about customisation, and it is where legacy habits do the most damage. On Apps 9 or 10 an upgrade was an event you prepared for over months, so carrying technical debt between them felt survivable. On Cloud it arrives twice a year, and anything built outside the Extensibility Framework has to be checked, and often reworked, on that same rhythm.
The boundary is simple to state and easy to cross by accident. Extending the data model with Custom Fields, adding logic through Custom Events and Workflows, adapting screens through configuration: all inside the contract, all carried forward. Touching a core object, or building a report or an interface directly against an internal view rather than a published projection, puts you outside it. Nothing stops you at the time. The bill arrives at the next release, and at every release after that.
I have watched this go wrong in both directions. Companies that refuse all extension end up with a shadow layer of spreadsheets doing the work the system was not allowed to do, which is worse, because at least a customisation is visible. The honest position is that some extension is necessary, and the only real question is whether it is built where the platform will maintain it for you.
Further reading: update-safe extensions, the true cost of customisation, clean core in an SCM context, the upgrade tax, the upgrade readiness checklist, and what a release actually brings, with 25R2 purchasing as the worked example. Scoped modification work is listed under marketplace modifications.
Ask a buyer what goes wrong and you get something dramatic: a late shipment, a line stopped for a missing part. Look in the data and the costly problems are the undramatic ones, because nothing in the system objects to them.
| What is sitting there | Why nobody sees it | What it turns into |
|---|---|---|
| A released PO the supplier never acknowledged | The order is valid and open. No field says "ignored" | A delivery date everyone planned around that was never agreed |
| Goods received, invoice never matched | Both records are individually correct | An accrual that grows quietly until period end |
| A supplier price that moved between orders | The new price applies cleanly, exactly as configured | Margin erosion found during an annual review |
| A buyer who stopped ordering from a usual source | Every individual order is legitimate | Concentration risk, or a supplier problem nobody escalated |
All of this is detectable, and all of it is readable through standard OData projections on a read-only account. That means a monitor can look for it daily without touching a record, installing an object, or adding anything the next release has to be checked against. It is the design principle behind the SCM Automation Pack, and the reason the five-day exception scan exists as a way to see what is already in your own data before committing to anything ongoing.
On the physical side the same principle applies to warehouse work. Picking strategy and packing proposals are configuration decisions that quietly set your throughput ceiling, and they are rarely revisited after go-live.
Further reading: unconfirmed purchase orders, what unmatched receipts do at period end, supplier price changes, advanced picking strategies, the packing proposal.
Anomaly detection, demand forecasting and predictive maintenance are genuinely useful, and they all rest on the same unglamorous foundation: whether your master data is good enough for a model to learn from. A forecast built on lead times copied out of the legacy system in 2019 and never reviewed will be precise, confident and wrong, and it will be harder to challenge than a human guess because it arrives with a number attached.
The second thing the demo leaves out is what happens to the output. Detection is the easy half. The half that decides whether any of it pays off is routing: who receives the signal, how it reaches them, and what happens when they do nothing. An alert stream with no named owner and no escalation is a mailing list, and people unsubscribe from mailing lists in their heads long before they do it in the client.
That is why I design exception rules around the recipient rather than the condition. One deduplicated digest per owner per day beats forty individual notifications that are each technically correct. And a rule that cannot state in one sentence what the recipient is supposed to do about it does not ship.
Further reading: alert fatigue and exception design, the cost of missed exceptions, detecting supplier behaviour change, the data attention gap, assumed vs confirmed records, read-only OData monitoring.
Crystal Reports layouts from Apps 9 and 10 do not carry across to IFS Cloud. That is the fact that matters for your plan, whatever any vendor's support calendar says, and it is usually discovered later than it should be, because reporting gets treated as a workstream that can start once the real configuration is done.
IFS Cloud splits the job across different tools. Quick Reports handle lists and extracts: saved queries, no layout ambition, self-service for anyone who can be trusted with a data set. Laid-out business documents are produced through IFS Cloud's own report layout tooling. Analysis and dashboards belong in the reporting and analytics layer rather than in a printed report at all. Trying to recreate a 200-item Crystal inventory inside any one of these is how reporting becomes the critical path.
The work that actually saves you time is triage, and it is a business job rather than a technical one. Pull the usage data first. Most report inventories contain a long tail nobody has run in two years, a middle band that exists because one person likes the format, and a small core the business genuinely runs on. Rebuild the core properly, convert the middle band to Quick Reports or a dashboard, retire the tail. The conversation about retiring the tail is the hard part, which is why it needs to start early and needs someone senior to close it.
Further reading: when a Quick Report is the right answer, and the reports section of the marketplace.
Permission sets in IFS Cloud are capable enough to express proper segregation of duties. Whether they end up doing so is decided in the first six weeks of the project, when someone is under time pressure and the fastest way to unblock testing is to grant a broad set to a group and move on. That grant is almost never revisited, because nothing breaks. It surfaces at the first external audit, when a tester asks who can both create a supplier and approve a payment to it, and the honest answer takes a fortnight to assemble.
Design the role model against the process rather than the org chart, and build it while the process design is still fresh in everyone's head. It costs days then and weeks later. The same applies to standards work: if you operate under ISO requirements, the evidence those audits want is largely a by-product of decisions you are already taking, provided you record them as you go instead of reconstructing them afterwards.
Further reading: RBAC and segregation of duties, permission sets in IFS Cloud, ISO standards in IFS Cloud, and the security section of the marketplace. My own view on the wider ownership question sits on the data governance page.
Every implementation plan has a migration workstream, and most are optimistic by the same margin. The reason is consistent: the effort is not in loading the data, it is in deciding what the data should say. Loading is mechanical. Agreeing that these 4,000 part records are the ones worth keeping, that this status code maps to that one, and that a customer with no valid tax ID is a customer you are not going to migrate, is a series of business decisions with no obvious owner.
Two habits change the outcome. Rehearse the load more than once, on a schedule, with a defined cut of source data each time, so the failure list shrinks between rehearsals instead of being discovered on cutover weekend. And treat validation as its own deliverable with its own sign-off rather than as the last step of loading, because IFS Cloud enforces its business rules at load time: well-formed source data can still be rejected for violating application logic nobody had read.
Further reading: the data migration checklist, how FNDMIG and the Data Migration Manager fit together, and the data migration section of the marketplace.
In most of the companies I work with, a large amount of operational knowledge lives in one person's head and one person's spreadsheet. The buyer who knows which supplier actually delivers on time regardless of what the lead time field says. The planner whose workbook reconciles two things the system does not reconcile. None of this shows up in an ERP assessment, and all of it walks out of the building when that person leaves.
An implementation is the one moment when you have a mandate to surface it. Every shadow spreadsheet is a documented requirement waiting to be read: it exists because the system does not do something, and finding out what that something is tells you more about your real process than a workshop will. Some of them should become configuration. Some should become a Quick Report. A few are genuinely someone's judgement and should stay human, but at least then you know where they are.
The same logic applies to the implementation record itself. Decisions taken in month two get questioned in month eleven by people who were not in the room, and a project that cannot answer "why is it set up this way" reopens settled arguments for the rest of its life.
Further reading: shadow spreadsheet risk, knowledge loss when people leave, buyer knowledge concentration, and the implementation documentation kit if you would rather not build the templates from scratch.
I am wary of quoting percentage improvements. Published ranges come from situations you cannot inspect, with baselines nobody defined, and a number borrowed from another company's business case is not evidence about yours. What I can offer is the short list of measures that survive contact with an actual steering committee.
Further reading: ERP ROI analysis, why go-live is a load test, the implementation crisis.
If you are live on IFS Cloud and this article has described your situation rather than your plan, the order that works is roughly this. Find out what is actually in your data before redesigning anything, because the exception population usually contradicts the received wisdom about where the problems are. Then fix the governance decisions that get harder with time: the role model, the report inventory, the ownership of master data. Automation comes after that, not before, because automating a process nobody owns only makes it produce wrong answers faster.
What I do is on the offer page, the platform view is on the IFS Cloud page, and the process side sits under business process optimisation. The applications themselves, including the read-only exception monitoring described in section 4, live on ifs-erp.com.
No, but the work changes shape. Before go-live it is a design decision that costs nothing extra. After go-live it is an inventory exercise: list everything built outside the Extensibility Framework, establish what each item actually does, and decide case by case whether to rebuild it inside the contract, replace it with standard functionality, or accept the maintenance cost knowingly. The last option is legitimate. What is not legitimate is not knowing which category each item falls into, which is the usual starting position.
No. In most projects I see, the unclaimed value sits in exceptions a plain query would find: orders nobody confirmed, receipts nobody invoiced, prices that moved. That is rule-based detection rather than machine learning, and it works on data that is merely adequate. Model-driven forecasting is worth doing once master data has an owner and a maintenance routine, and worth postponing until it does.
Yes, and that is the approach I prefer for anything that only needs to read. Standard OData projections plus an integration account with read permission are enough to detect the exception patterns in section 4. Nothing is installed in IFS, nothing is written back, and there is no object for the next R1 or R2 release to break. If you want to see the output before committing to anything ongoing, the five-day exception scan produces the same report in observation mode only.
Budget the triage, not the rebuild. Pulling usage statistics and getting a decision on what to retire takes longer than rebuilding the reports that survive, because it needs business sign-off rather than developer time. Start it in parallel with configuration rather than after it, and give the retire list an owner with the authority to say no. Teams that skip this step rebuild everything one for one and carry the whole inventory forward, including the part nobody has opened since 2019.
The configuration saving is small at that scale. The consistency saving is not, and it compounds: two sites configured independently will diverge on receiving, costing and reporting definitions within a couple of years, and reconciling them later is considerably more work than agreeing a shared template now. If there is any prospect of a fourth site, an acquisition, or a group-level report, treat it as worth it.
Dariusz Myśliwiec: 25+ years in ERP and supply chain, 17+ on IFS (Apps 7.5–10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Based in Kraków, delivering remotely across Europe and globally through an independent practice.
Selected clients: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
If you are scoping an IFS Cloud implementation, or you are already live and suspect the value case has quietly gone missing, a short call is the fastest way to work out which two or three of the eleven sections above are actually costing you something.
Independent IFS Cloud practice · Business Process Automation
IFS Cloud workflows are BPMN diagrams, built in the Workflow Designer and run by a workflow engine embedded in IFS Cloud Web, that automate steps of a business process. There are three types: User Interaction, Validation and Process Enrichment. Whether a workflow works in production depends less on the diagram than on what is decided before it is drawn: the type, when it runs and what starts it.
Key takeaways
An IFS Cloud workflow is a process model executed by the Business Process Automation engine inside IFS Cloud Web. IFS describes it this way: “a workflow engine has been embedded within IFS Cloud Web to enhance the automation and tailoring experience of our users” (Business Process Automation, docs.ifs.com).
A workflow is drawn with BPMN symbols and calls IFS Cloud through projections: it reads records and calls actions; it can also create, update or delete data. It belongs to the configuration tailoring type, next to Page Designer and custom events, which places it below custom code in the order of options described in the IFS Cloud customization strategy.
IFS states that “There are 3 types of Workflows”, and the type decides which BPMN symbols the Workflow Designer offers in its toolbox (What are Workflows?, docs.ifs.com).
| Type | What it does | Typical use | Limit to know |
|---|---|---|---|
| User Interaction | Asks the user for more information when they perform an action; the answer can drive a gateway decision or a projection call | A reason when a buyer overrides a price, a confirmation before a status change | User forms cannot be assigned to specific users or roles |
| Validation | IFS: “designed to conditionally prevent a user from completing an action”, with a localized error message | Block a purchase order to a supplier without approved bank details | The IFS Failure Event does not support dynamic error messages; use gateways with separate failure events |
| Process Enrichment | Creates, alters or deletes data through projection operations | Fill a default value, create a follow-up record, update a related record | An attribute defined as non-updatable cannot be given a value this way, even on insert |
The limit in the first row changes designs. IFS answers the question of assigning user forms with “The Workflows do not support the user/role base approval for user forms” (Workflow FAQs, docs.ifs.com). A workflow can ask the user in front of the screen. Routing a request to a named approver has to be designed separately from the workflow form, and that decision belongs in the design before the first diagram is drawn.
A workflow is started by one of three configurations and runs at one of three timings, and not every combination is allowed.
| Timing | How it runs | Restriction |
|---|---|---|
| Before | “executed as part of the user's action which caused the Workflow to execute” | Projection actions only |
| After | “invoked on completion of the main REST call as a reaction” | Not triggered by direct SQL changes or background jobs |
| Asynchronous | Runs separately from the user's call | “can only be used to perform Process Enrichment activities” |
Two consequences follow. To stop the user's action, a Validation workflow runs inside the user's transaction, and when it ends in an IFS Failure Event, IFS states that “the whole transaction gets rolled back”. And if the data you want to react to is changed by a background job or a direct database operation, only an event action with Asynchronous timing will start the workflow. How background jobs behave is covered in IFS Cloud background jobs.
The Workflow Designer is embedded in the Workflow Manager and has four areas: a toolbox with the BPMN shapes, a workspace, a control panel with save and deploy, and a properties panel for the selected task or event (Workflow Tooling, docs.ifs.com). IFS recommends building incrementally, and the order below follows its best practices (Best Practices, docs.ifs.com).
DEBUG_TIMEOUT_SECONDS_LIMIT, so large workflows are tested in sections.Workflow performance is decided by the number of API calls and loop iterations, and IFS publishes concrete tips for both (Performance Improvement Tips, docs.ifs.com).
$select instead of fetching whole entities.A Validation workflow runs every time a user performs the action it guards, so it gets the strictest version of these rules: one read with $select, a key filter and no loop. Naming variables after the attribute they hold costs nothing and saves the next person from opening every task to find out what var1 was.
A workflow should replace custom code when the logic is a validation, a user prompt or a data update that can be expressed through projection calls, because a configuration carries less release update work than extending on the inside. Less is not none: IFS places configurations at a level with a “higher risk that some configurations could be impacted when applying future releases”, handled by impact analysis (Tailoring Overview, docs.ifs.com).
Custom code still wins where a workflow would loop over large volumes, where logic has to run with rights the triggering user does not have (IFS states that a “Workflow executes on behalf of the user who triggers the Workflow”), or where the standard behaviour itself has to change. The comparison with custom events from the automation side is in IFS custom events explained, and an event set-up for emailing purchase orders is described in IFS Cloud email purchase orders: event set-up. The level-by-level cost is compared in IFS Cloud tailoring levels.
IFS Cloud workflows slow down the user's action when they run synchronously and make many API calls or loop over records. IFS recommends reading only the needed fields with $select, filtering on primary keys rather than ObjKey, consolidating API calls, avoiding nested loops and running long workflows asynchronously. Validation workflows run inside the user's action and need the leanest design.
An IFS Cloud workflow cannot route a user form to another user or role. IFS states that workflows do not support user or role based approval for user forms, and a workflow runs on behalf of the user who triggered it. Approval routing to a named approver has to be designed separately, while a workflow can validate or enrich the record around it.
IFS Cloud workflows are configurations built in the Workflow Designer, with troubleshooting that shows the execution path and variable values, and they call IFS Cloud only through projections. Custom PL/SQL code built in IFS Developer Studio is extending on the inside, which carries more release update work, but it handles volume better: for large loops IFS itself suggests batch processing with PL/SQL functions or procedures instead of a workflow loop.
An IFS Cloud workflow with After timing is not triggered by changes made through direct SQL operations or background jobs. Such changes can start a workflow only through an event action configured with Asynchronous timing, and Asynchronous workflows can only perform Process Enrichment, not validation or user interaction.
A team should start IFS Cloud workflows with one manual check that users perform each time they perform a single action, built as a Validation workflow with Before timing. The scope is small, the result is visible in UAT, and the team practises observations and troubleshooting on a small workflow before building enrichment workflows.
Dariusz Myśliwiec: 18 years hands-on with IFS (Apps 7.5 to 10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Independent practice based in Kraków, delivered remotely across Europe and globally. You talk to the consultant who does the work, not a sales layer.
Designing workflows, and deciding which custom code can be replaced by one, is part of my services for IFS Cloud.
Selected clients from my IFS work: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Bring the list of custom events and custom code in your solution. On a technical call we sort them into three groups: candidates for a workflow, items that should stay code, and items standard IFS Cloud now covers.
Book a call about your automations Read: IFS Cloud customization strategy
Independent IFS Cloud practice · Tailoring strategy
An IFS Cloud customization strategy is a rule for choosing, per requirement, between configuration, extending on the outside through APIs and extending on the inside with code. IFS documents these three tailoring types, and each one costs something different at a release update. The strategy picks the cheapest type that still meets the requirement and records the choice before anything is built.
Key takeaways
@overtake is a last resort after @override.IFS Cloud can be tailored by configuration, by extending on the outside and by extending on the inside, and the IFS Tailoring Overview describes each with its own tools and its own effect on updates (Tailoring Overview, docs.ifs.com).
The distinction is described at the level of single objects, with a worked example, in IFS Cloud tailoring levels. This article covers the decision rule and the governance around it.
The tailoring level of a solution decides how much work each IFS Cloud release update brings, and IFS describes three levels with a different update experience for each.
| Level | What it allows | Release update experience, as IFS describes it |
|---|---|---|
| Core | Personalization and navigation-related configuration only | “Automated using IFS Lifecycle Experience” |
| Configured | All configuration capabilities, plus extending on the outside with any API | “Impact analysis supported by IFS Lifecycle Experience”, with assisted updates of impacted configurations |
| Customized | Adds extending on the inside with the full developer toolset | “Developer Guidance on how to address occasional changes to Platform”, with assisted merging of overridden and added functionality |
The configured level is where expectations go wrong. IFS writes that it comes with a “higher risk that some configurations could be impacted when applying future releases”, and warns that it is “tempting to 'overuse' configurations” because they look easier or cheaper. A heavily configured page is cheaper to carry than custom code, but it is not zero work at the next release. The same page also notes that smaller customizations can be relatively easy to carry through updates, while large overrides and overtakes take more effort. The trade-off is argued from the cost side in the Clean Core illusion in IFS Cloud.
A CRIM describes the business outcome a project needs, while a tailoring type describes how that outcome is built, and IFS notes that one CRIM often combines several tailoring items. A supplier approval CRIM, for example, can consist of a custom attribute for the approval status, a Page Designer change that shows it, a validation workflow that blocks purchase orders to unapproved suppliers and a permission set for the approvers.
For governance this means the CRIM list alone is not enough. Each CRIM needs its tailoring items listed with their type and level, because the release update impact is assessed per item, not per CRIM. Testing works the same way: the CRIM is validated as a business outcome, the items are regression-tested one by one, as described in IFS testing: CRIM validation, ATT and cutover rehearsals.
A requirement should be tested against the options from the cheapest to the most invasive, stopping at the first one that meets it. IFS puts the principle in one line: “you also want to keep the tailoring level as low as possible”, without forcing a requirement into a type it does not fit.
@override preferred.Breaking the first rule looks like this: custom code that reads a custom attribute created in a designer. The attribute can be changed or removed by a key user without a developer build, and the custom code can then fail at runtime. Finding such failures afterwards is covered in silent custom code failure in IFS Cloud. What keeps extensions safe at updates, from the developer's side, is described in update-safe IFS Cloud extensions.
Tailoring stays under control when every item has an entry in a register and every configuration travels in a package. The register is a project artefact outside IFS Cloud; the package is the IFS mechanism for moving configurations.
| Register field | Why it is there |
|---|---|
| CRIM and item ID | Links the business outcome to each object that delivers it |
| Tailoring type and level | Tells the release update check how much analysis the item needs |
| Owner | The person who decides whether the item is still needed |
| Reason and options rejected | Stops the item from being rebuilt differently by the next team |
| Package or repository location | Where the item lives: the Application Configuration Package, the customer solution repository or the external system |
| Review event | After each release update, check whether new standard functionality replaces the item |
On packages, IFS states that “configurations are imported and exported using Application Configuration Packages” (Configuration Lifecycle Management, docs.ifs.com). One detail is worth knowing before the first clean-up: making an item obsolete in a delivery does not delete it from environments where it is already installed, so it has to be removed there manually. The reason column follows the format of the IFS Cloud decision register, and the check before each release is described in IFS Cloud upgrade readiness.
A customization strategy has to contain four risks, and each has a concrete counter-measure that can be agreed before build.
| Risk | Effect | Counter-measure |
|---|---|---|
| Scope creep | Every workshop adds tailoring items until budget and plan no longer hold | Change control: no item is built without a register entry and an accepted decision |
| Slow pages and processes | Workflows with loops and many API calls run inside the user's action | Performance review of workflows and custom code before deployment, with test data of production size |
| Orphaned configuration | Nobody knows why an attribute or event exists, so nobody dares to remove it | Owner and reason per item; review event after each release update |
| Users working around the system | Tailoring built for one group is ignored by another | Key users from each affected group in the decision and in UAT |
Configuration in IFS Cloud uses designers and tooling for consultants and power users, such as Page Designer or the Workflow Designer, and is handled as part of the customer solution. Customization, which IFS calls extending on the inside, builds or changes business logic in IFS Developer Studio. Customization is the only way to change some standard behaviour and is the most invasive tailoring type.
Configurations in IFS Cloud are cheaper to carry through release updates than custom code, but they are not exempt. IFS describes the configured tailoring level as carrying a higher risk that some configurations are impacted by future releases, with impact analysis supported by IFS Lifecycle Experience. Each configuration therefore needs an owner and a place on the checklist reviewed before every release update.
A CRIM in an IFS Cloud project is an item on the list of configurations, reports, integrations and modifications that the project adds to standard IFS Cloud. A CRIM describes the business outcome, and IFS notes that one CRIM often combines several tailoring items, for example a custom attribute, a page configuration and a workflow. Release update impact is assessed per tailoring item.
Extending IFS Cloud on the outside fits when the logic belongs to another system or can run outside the ERP and needs only to read or write IFS Cloud data through its REST APIs. The code then lives outside the customer solution repository. IFS recommends Premium APIs where available, because they are better documented and more stable over time.
An IFS Cloud solution stays understandable when every tailoring item has a register entry that names its CRIM and its tailoring level. The entry also records an owner and a reason, plus a review event, and every configuration is kept in an Application Configuration Package. After each release update the owners check whether new standard functionality can replace their items.
Dariusz Myśliwiec: 18 years hands-on with IFS (Apps 7.5 to 10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Independent practice based in Kraków, delivered remotely across Europe and globally. You talk to the consultant who does the work, not a sales layer.
Reviewing a CRIM list and deciding the tailoring level per item is part of my services for IFS Cloud. The outcome can be to keep an item, rebuild it at a lower level or drop it in favour of standard.
Selected clients from my IFS work: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Send the CRIM list or the gap list from your project. On a technical call we take a sample of items and check the tailoring level and owner of each, and the cost each one adds to the next release update.
Independent IFS Cloud practice · Data governance
IFS Cloud data modeling decides which entities and attributes carry your business data, and how they relate. Data governance decides who owns each of them and which rules the data must meet. The two meet in configuration: a governance rule that never becomes a field, a validation, a permission or a log setting stays a policy document that IFS Cloud cannot check.
Key takeaways
Data modeling in an IFS Cloud project means choosing and extending the standard data model, because the entities and their relationships are delivered by IFS. The project team does not draw a database from scratch. It decides how the business is represented in what already exists.
In practice that is four sets of decisions:
Users and integrations reach these entities through projections, which matters for governance: access rights and automation are both configured against projections and the entities behind them.
Data governance decides who owns each data object, which rules it must satisfy, how quality is measured and who may change a rule. It produces decisions, not records: a data owner for suppliers, a naming convention for parts, a rule that a supplier cannot be used for purchasing until its tax and bank details are approved.
Those decisions are only useful when the model has a place for them. A naming convention with no validation behind it depends on every buyer remembering it. The definition, the four components and the roles are set out in the definition of data governance. Standing rules that outlive the project belong in the enterprise book of rules.
Each type of governance rule maps to one configuration mechanism in IFS Cloud, and choosing the right one is the actual data modeling work of the project.
| Governance rule | IFS Cloud control | What to know |
|---|---|---|
| The record must carry information the standard entity does not have | Custom attribute on the entity | It must be approved and the entity published before Page Designer can place it on a page. |
| A field must always be filled in on a page | Page Designer | IFS lists “Set fields to mandatory” among Page Designer functions. Saved changes stay invisible to users until they are published. |
| A value is allowed only in combination with another value | Conditional field validation | Each rule has a case (when it applies), a validate expression and a message shown on failure. |
| Only some roles may use a function | Permission set | Grants access to projections. It does not filter records. |
| A user sees only the records of their area | Custom data access control | Access control lists filter records on attributes of a projection entity. |
| Changes to a sensitive field must be traceable | History log | Configured per table and column. On update, the old and the new value are logged. |
| The data owner must know when a record changes | Custom event with an event action | Custom events fire when entities are created, updated or removed. |
| A business action must be blocked when a rule fails | Validation workflow | Stops the transaction with an error message; covered in IFS Cloud workflows. |
Two of these controls are easy to mix up. IFS states that “Permission Sets grant users access to Projections (APIs) but do not manage data access”, and that record filtering is the job of data access control (Custom Data Access Control, docs.ifs.com). For the history log, logging “is on the table level” and saving the settings generates database triggers, so log the columns a rule names and not whole entities (History Log Configuration, docs.ifs.com). Role design is covered in IFS Cloud permission sets and segregation of duties.
Governance and the data model change each other in every project phase: governance states the rule, the model gives it a control, and running the control shows where the rule or the model was wrong.
| Phase | Governance gives the model | The model gives governance |
|---|---|---|
| Design | Requirements such as GDPR consent, approval of new suppliers, part naming | The attributes and reference values that store them |
| Build and test | Which fields are mandatory, which combinations are invalid, who may see what | Page configurations, validations, permission sets and access control lists that enforce it |
| Operation | Quality measures and the owner who acts on them | History log entries and event notifications that show where data goes wrong |
The decision behind each control, for example why supplier approval was built as a validation and not as a permission, is worth one entry in an IFS Cloud decision register. When the data owner changes, that entry keeps the reason.
Supply chain master data is shared across departments, so one badly governed attribute shows up in purchasing, in the warehouse and in finance at once. A part status decides whether a part can be bought, stocked or sold, and the flags behind it are described in part status in IFS Cloud. The valuation settings on an inventory part decide what finance sees on the balance sheet, which is explained in inventory valuation methods and cost levels.
When the owners of those attributes are named and their rules are configured, a buyer, a warehouse planner and a controller read the same status in the same way. A lobby built on that data then shows figures that nobody has to reconcile first; building one is covered in lobbies and custom dashboards in IFS Cloud.
Governance controls built as configuration are carried into each release update, but they are not exempt from it. IFS describes the configured tailoring level as carrying a “higher risk that some configurations could be impacted when applying future releases”, with impact analysis supported by IFS Lifecycle Experience (Tailoring Overview, docs.ifs.com).
Three habits keep the controls manageable:
Data governance can start after go-live, but save-time controls then reach existing data only slowly. A new mandatory field or validation is checked when a record is saved, so records already in the system are not re-checked until someone saves them again, and their gaps remain until a cleansing task fixes them. Access controls such as permission sets and data access control apply to all records from publishing. That cleansing has to run alongside daily operations, with the same people who also process orders.
The cheaper moment is data migration, when every record passes through a mapping and a load anyway. A rule agreed before the load can be applied to legacy data once, instead of being retrofitted object by object; the sequence is described in the IFS Cloud data migration plan.
Data modeling in IFS Cloud decides which standard entities and reference codes hold the business data, and which custom attributes extend them. Data mapping matches those IFS Cloud fields to the fields of an external source, such as a legacy system during migration or a partner system in an integration. Mapping depends on modeling, because a field has to exist in IFS Cloud before anything can be mapped to it.
IFS Cloud enforces data governance rules through configuration: custom attributes for missing information, Page Designer for mandatory fields, conditional field validations for invalid value combinations, permission sets for access to projections, custom data access control for record visibility, the history log for traceability of changes, and custom events or validation workflows for notifications and blocked actions.
Permission sets in IFS Cloud do not control which records a user can see. They grant access to projections, which are the APIs behind pages and integrations. Filtering records, for example limiting a buyer to the suppliers of one site, is done with custom data access control, which applies access control lists based on attributes of a projection entity.
Data governance can be introduced after IFS Cloud go-live. A new mandatory field or validation is checked when a record is saved, so records already in the system are not re-checked until someone saves them again, and their gaps remain until a cleansing task fixes them during live operations. Access controls such as permission sets and data access control apply to all records from publishing. Agreeing the rules before data migration is cheaper, because every legacy record already passes through mapping and load at that point.
Custom attributes and validations in IFS Cloud are configurations, which IFS places at the configured tailoring level. That level carries a risk that some configurations are affected by a future release, so they need an impact analysis before each release update. Keeping them in an Application Configuration Package, with an owner per control, makes that analysis a checklist instead of a search.
Dariusz Myśliwiec: 18 years hands-on with IFS (Apps 7.5 to 10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Independent practice based in Kraków, delivered remotely across Europe and globally. You talk to the consultant who does the work, not a sales layer.
Turning data rules into IFS Cloud controls is part of my services for IFS Cloud; when the rules have to be applied to legacy data, that work sits in data migration services.
Selected clients from my IFS work: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Bring your list of data owners and rules, or the policy document that replaced it. On a technical call we go through it rule by rule and mark which ones IFS Cloud already enforces, which need a configuration and which nobody owns.
Book a call about your data rules Read: the definition of data governance