Ontology-Driven ERP Generation: Business Rules Auto-Create Documents & Metrics
This article outlines a business-centric ontology approach to automatically generate ERP systems by standardizing entities, relationships, rules, actions, and metric definitions, enabling business users to maintain logic without coding, and detailing key metrics across sales, procurement, inventory, production, cost, finance, quality, and supply chain domains with strict caliber rules.
Core premise: Use ontology to standardize enterprise business "nouns, relationships, rules, actions, statistical calibers" so the system auto-assembles ERP documents, processes, permissions, reports, and cost-calculation logic — instead of hard-coding separate sales, procurement, and production modules. Ontology here is essentially a unified business dictionary + business rule library defined by business people, not programmers.
I. Complete Business-Side Generation Path (Business Operation Sequence)
1. Organize Business Entities (Business Nouns, Ontology "Classes")
Business first inventories all master data and documents in the ERP:
Master data: Material, Customer, Supplier, Department, Personnel, Warehouse, Bin, Operation, Work Center, Accounting Subject, Cost Center, Shift, Version (ECN)
Business documents: Sales Order, Delivery Order, Purchase Request, Purchase Order, Receipt Order, Inspection Order, Put-away Order, Issue Order, Production Order, Completion Order, Return Order, Inventory Count Order, Payable Order, Receivable Order, Voucher
Ontology role: unify naming. E.g., some call it "goods", others "material"; ontology forces unification to Material and defines its business attributes, preventing caliber conflicts across ERP modules.
2. Define Business Relationships (Who Relates to Whom, Process Skeleton)
Business answers questions such as:
Which customer owns a sales order? Which material does an order line correspond to?
Which materials (BOM) and operations (routing) does a work order consume?
Which purchase order does a receipt correspond to? Which business document generates a voucher?
Who owns substitute materials, outsourcing, customer pricing, supplier quotations?
Not database foreign keys, but business-meaning relationships : A "consumes" B, A "produces" B, A "references" B. ERP later auto-fills reference links and auto-joins.
3. Enter Business Rules (Core Business Part, Auto-Control)
Business writes oral and policy constraints into the ontology; the generated ERP executes them automatically without code changes. Example rules:
Customer has credit limit; if arrears + current order amount exceeds limit → order audit blocked.
Material batch management: outbound must specify batch, FIFO enforced.
BOM must have version; after ECN change takes effect, old BOM locked, work orders cannot select old version.
Receipt must pass inspection; non-conforming cannot enter qualified warehouse.
Issue cannot exceed work order quota (over-issue ratio configurable).
Inventory count variance must go through approval before adjusting stock.
This is the core value of ontology-driven ERP: business maintains rules itself; changing rules does not require changing code .
4. Define Business Actions (Clickable Operations in ERP)
Business defines what operations each document supports, preconditions, and results:
Sales Order: Create, Audit, Lock, Change, Close, Cancel
Work Order: Release, Issue, Report Completion, Put-away, Rework, Close
Procurement: Request, Order, Receive, Reconcile, Invoice, Pay
Actions must specify which data changes upon completion (inventory, receivables, payables, WIP, available quantity).
5. Define Business Metrics & Calibers (Your Focus)
Metrics are not arbitrary formulas; ontology solidifies the metric's business caliber so reports auto-generate and everyone sees the same number.
Common ERP pain point: sales revenue ≠ finance revenue; ontology locks the caliber.
6. Auto-Generate Business ERP Capabilities
After ontology model validation, the system auto-produces: document pages, fields, approval flows, available-quantity calculation logic, cost allocation logic, reports, alerts, permission scopes. Adding a new business type (e.g., consignment, outsourcing) only requires new entities + rules in ontology — no module redevelopment.
II. Business Must-Manage Metric List (By Domain, Business Perspective, No Technical Metrics)
✅ Sales Domain Metrics
Orders: order qty, order amount, shipped qty, unfilled qty, overdue orders, order delivery timeliness rate
Revenue: invoiced amount, uninvoiced revenue, collected amount, collection rate, receivables balance, aging
Customer: credit utilization, customer gross margin, order frequency, return rate, complaint rate
Price: sales unit price, discount, price adjustment records
✅ Procurement & Supplier Domain Metrics
Procurement: request qty, order qty, receipt qty, in-transit qty, on-time receipt rate, incoming defect rate
Supplier: on-time delivery rate, incoming pass rate, reconciliation cycle, payables balance, purchase unit price
Cost: purchase price fluctuation, substitute material price difference
✅ Inventory Domain Metrics (Most Prone to Caliber Chaos)
Stock: on-hand, available, frozen, in-inspection, WIP, in-transit
Turnover: inventory turnover days, inventory age, obsolete qty/amount, scrap qty
Batch: batch remaining qty, FIFO execution status
✅ Production Manufacturing Domain Metrics (Discrete Manufacturing Core)
Work Order: released qty, completed put-away, scrap qty, rework qty, work order closure rate
Capacity: operation reported hours, hour achievement rate, equipment utilization, yield
BOM: BOM loss rate, standard consumption, over-issue qty, substitute material usage
MRP: planned requirements, net requirements, planned orders, lead time, shortage alerts
✅ Cost Domain Metrics (Finance-Business Integration)
Material cost, labor cost, manufacturing overhead, work order unit cost, completed cost, WIP cost
Cost variances: material price variance, quantity variance, work order variance, scrap loss
✅ Finance Domain Metrics
Receivables, payables, advances received, advances paid, GL account balances, revenue, cost, expense, profit
✅ Quality Domain Metrics
Incoming IQC defects, in-process IPQC defects, final FQC defects, return defects, rework/repair loss
✅ Supply Chain Collaboration Metrics
Kit completeness rate, shortage count, order kit delivery rate
III. Business-Side Metric Caliber Rules (Must Define in Ontology, Else Metrics Invalid)
For every metric, business must answer five questions and write them into the ontology:
Statistical scope: Which documents included? (e.g., does revenue include returns? include uninvoiced?)
Time dimension: Order time / shipment time / invoice time?
Filter conditions: Exclude voided/canceled orders?
Calculation formula: (Business language, not SQL) Example: Order delivery timeliness rate = on-time delivery orders ÷ due delivery orders
Attribution dimension: Split by customer / product line / warehouse / workshop / salesperson
Ontology value: binds this caliber set to the metric entity; any report or dashboard pulling the metric automatically follows the same rules — not one algorithm per report.
IV. Business Boundary (Critical to Avoid Misunderstanding)
Ontology-generated ERP ≠ AI auto-understands business. Prerequisite: business must clearly define all entities, relationships, process rules, and metric calibers above. Ontology is the business's "standardized container"; the generator merely translates this business definition into ERP documents, processes, and calculation logic. If business defines incorrectly, generated ERP logic is wrong; if rules are incomplete, ERP lacks controls.
V. Business-Side Implementation Sequence (Simplified for Business Owners)
Align business: Sales / Procurement / Warehouse / Production / Finance unify master data list.
Map document flow relationships (Order → Inbound → Production → Finance Voucher).
Organize existing policies, extract hard control rules (block, alert, approval).
List all daily metrics, unify each metric's statistical caliber.
Enter, review, consistency-check in ontology platform (e.g., logical conflicts: BOM loops, credit rule conflicts).
One-click generate ERP business model, go live trial; business changes only modify ontology rules, no code changes.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
