Skip to main contentSkip to footer

IFS Cloud Project Governance: Five Questions to Answer

Five questions every IFS Cloud steering group asks, where the answers should come from, and how a register-based tool such as Implementer helps.

Independent IFS Cloud practice · Project governance Five questions a steering group asks, and where the answers should come from Key takeaways Every IFS Cloud steering group asks the same five questions about versions, approvals, readiness, updates and evidence. If the answer to one of them takes an afternoon, the…

Read more

Time Fences in IFS Cloud: Demand and Planning Time Fence

How the demand and planning time fences work in IFS Cloud: what each protects, who sets the values, and how master scheduling and MRP react.

Independent IFS Cloud practice · Planning design Know where the plan is frozen and where the system may still change it The planning time fence and the demand time fence in IFS Cloud divide the planning horizon into periods in which master scheduling and MRP treat supply and demand differently. A planner who expects…

Read more

Master Production Schedule Level 1 in IFS Cloud Explained

How Master Production Schedule Level 1 works in IFS Cloud: Level 0 and Level 1 parts, the proposals it creates, dependent demand and time fences.

Independent IFS Cloud practice · Master scheduling design Describe the Level 0 and Level 1 structure before planners read the proposals Master Production Schedule Level 1 is the level of the IFS Cloud master schedule where you plan long-term demand for parts that are manufactured or purchased. Its calculation creates…

Read more

IFS Cloud Intraday Availability: Supply and Demand Timing

How IFS Cloud analyses short-term supply and demand down to the minute: the horizon, firm or non-firm items, balance fields and projected quantity.

Independent IFS Cloud practice · Short-term planning Check projected stock down to the minute for the next days IFS Cloud intraday availability is the analysis of the short-term supply and demand situation for inventory parts, considering the timings within the day down to minute level. It runs on the Inventory Parts…

Read more

Master Scheduling ATP in IFS Cloud: How Promising Works

How Master Scheduling Available to Promise works in IFS Cloud: the master schedule as data source, generic and customer-dimension checks, and set-up.

Independent IFS Cloud practice · Order promising design Decide what the master schedule promises before customer orders depend on it Master Scheduling Available to Promise (ATP) is a promising method in IFS Cloud that uses the master schedule (MPS) as the data source for customer order promising. A promise date from…

Read more

IFS Cloud Material Requisition: Statuses, Reserve, Issue

How IFS Cloud material requisition works for internal demand: statuses, reservation before issue, partial issue and closing a line.

Independent IFS Cloud practice · Internal demand design Decide who reserves, who issues and who closes before requisitions pile up An IFS Cloud material requisition is the document through which material is requested for internal demand, and it runs through its own flow: request, reservation, issue and closure. If the…

Read more

IFS Cloud Routing Lead Time: Fixed, Variable and Overlap

How IFS Cloud routing lead time is calculated: fixed and variable time, standard lot size, parallel operations and overlap, with worked examples.

Independent IFS Cloud practice · Manufacturing planning design Check your routing data against the calculation that produces the planned lead time IFS Cloud routing lead time is the lead time of a manufactured part calculated from its routing, and the page states that MRP and Master Scheduling use it. If the…

Read more

IFS Cloud Email Customer Documents: Set-Up Rules

IFS Cloud email customer documents: how the contact is found, what each of invoice, quotation and order confirmation needs, and the invoice lock.

Independent IFS Cloud practice · Sales output design Check the contact, the document and the event before customers say they never got the invoice To make IFS Cloud email customer documents reach customers, each document needs its own set-up: an invoice, a quotation and an order confirmation each have their own page…

Read more

IFS Cloud Lead Time: Purchase, Manufacturing and Expected

IFS Cloud lead time: how purchase, manufacturing and expected lead time are defined, where each is calculated and which one MRP reads.

Independent IFS Cloud practice · Planning data design Know which lead time a function reads before you fill the fields IFS Cloud lead time lives in several fields, and each field has its own meaning. If purchase, manufacturing and expected lead time are filled without knowing which one a function reads, planned dates…

Read more
Abstract illustration on a navy background with the article title: “Put every data rule where IFS Cloud enforces it”

Independent IFS Cloud practice · Data governance

Data modeling and data governance in IFS Cloud: put every rule where the system can enforce it

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

  • In an IFS Cloud project you do not design tables. You decide which standard entities and attributes you use, which reference codes you load, and what you add as custom attributes.
  • Each governance rule needs a named control in the system: a custom attribute, a mandatory field in Page Designer, a conditional field validation, a permission set, data access control, a history log setting or an event.
  • Permission sets decide which projections (APIs) a user may call. Data access control decides which records inside those projections the user sees. A rule about data visibility needs the second one.
  • Every control you add is a configuration, so it goes into an Application Configuration Package and into the impact analysis before each release update.
  • 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.

1.What does data modeling mean in an IFS Cloud project?

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:

  • Structure: companies, sites and warehouses, and which of them share master data.
  • Entities in use: customers, suppliers, inventory parts, sales parts, purchase orders, and which optional parts of each your processes need.
  • Reference values: the codes behind statuses and groups, loaded once and then reused by every transaction.
  • Extensions: information the standard entity does not hold. IFS documents that “Custom attributes make it possible to extend an Entity, in order to add specific information”, as either stored values or read-only values calculated from other attributes (Create custom attribute, docs.ifs.com).

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.

2.What does data governance decide?

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.

3.Which IFS Cloud control holds which governance rule?

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.

4.How do governance and the data model change each other during a project?

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.

5.Why does the link matter most for supply chain data?

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.

6.What happens to these controls at an IFS Cloud release update?

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:

  1. Package them. Custom attributes and page configurations go, together with event settings, into an Application Configuration Package, which is how IFS Cloud moves configurations between environments.
  2. Use contexts instead of copies. Page Designer stores changes “tied to a configuration context”, so a site or role that needs a different mandatory field gets a context, not a duplicated page (Page Designer Basics, docs.ifs.com).
  3. List them for the update check. Each control with its owner and the rule it enforces goes on the list that is reviewed before a release, as described in IFS Cloud upgrade readiness.

7.Can data governance start after go-live?

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.

8.Frequently asked questions

What is the difference between data modeling and data mapping in IFS Cloud?

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.

Which IFS Cloud features enforce data governance rules?

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.

Do permission sets in IFS Cloud control which records a user can see?

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.

Can data governance be introduced after the IFS Cloud go-live?

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.

Are custom attributes and validations safe at IFS Cloud release updates?

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.

9.About the author

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.

Which of your data rules has no control behind it?

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

×
Need Expert Guidance?
We've helped hundreds of businesses succeed. Get a free consultation to discuss your project requirements.
Get Free Consultation
17Years Experience
50Implementations
PRINCE2Certified
100%Success Rate

ROI Calculator

Calculate your return on investment

Input Values

€
€
€

Results

Annual Savings
€ 0
Payback Period
0 months
ROI
0%
Monthly Savings
€ 0

Get Detailed Report

Enter your details to receive a detailed ROI report.