Building KPI definitions is where most BI projects die.
Every organization starts a BI project by saying "we need OEE" or "we need CLV." What they don't anticipate: defining OEE correctly requires resolving how downtime categories map from the MES, what shift definitions to use, how to handle planned vs. unplanned stops. This definitional work takes months — and the definitions differ between every analyst who builds them.
The definitions are already built. For your industry.
IntelliFabric's KPI library encodes the industry-standard definitions — with the flexibility to reflect your specific data model. OEE uses your shift codes, your downtime categories, your work order structure. CLV uses your product hierarchy, your return logic, your loyalty program. Pre-built doesn't mean generic.
From connection to insight in four steps.
Industry module selected at kickoff
At project start, your industry module (Manufacturing, Retail, Warehousing, or Healthcare) is activated. This loads the complete KPI library, data model templates, and dashboard layouts for your vertical.
KPI mapping to your source data
During the data discovery phase, IntelliFabric's team maps each KPI definition to your actual field names, codes, and hierarchies. OEE's downtime categories get mapped to your specific MES codes. Revenue maps to your specific transaction table.
Definitions encoded in semantic model
Every KPI is encoded as a measure in the Power BI semantic model — with the business logic, filters, and time intelligence built in. All downstream reports inherit the same definition automatically.
Validated before go-live
Every KPI is validated against your ERP or source system numbers before go-live. Finance signs off on revenue. Operations signs off on OEE. You go live knowing the numbers match reality.