The Operational Intelligence Hub is the fourth layer of Ekyam’s Platform Architecture.  It is the primary interface where the business users interact with the insights and power of the Ekyam Platform. More than just being a reporting tool, iIt is a unified, dynamic system where the users can monitor, analyze, and transform the complex, real-time data from the Ekyam Retail Knowledge Graph (RKG) into an intelligent action. The hub is the COMMAND Centre, that allows the user to: → Monitor: Carefully monitoring the Key Performance Indicators (KPIs), and receiving alerts for critical events such as low stock levels etc. → Analyze: Identify the issues and work towards implementing a solution.  → Act: Automate responses and trigger workflows directly from the insights.

​
• Ekyam Reports: Help to Understand the Past Performance

Ekyam reports will help the users to understand trends, evaluate past performances, strategize plans by selecting the metrics and dimensions directly from the ontology.   A Use Case Unveiled: Let us understand a common use case when a retailer is trying to analyze the performance of a recent collection. There could be a possibility if a “Quarterly Product Performance Report” could be generated that presents itself with the following structure: → Goal: To understand which products in the “Spring 2025 Collection” were most and least successful. → Filters: Collection.collection_name = “Spring 2025”, Timeframe = “Q1 2025”. → Dimensions (Rows): The report would be structured by Product.product_name and broken down further by each Item.sku. → Metrics (Columns): Key metrics would include Net Revenue, Units Sold, Gross Profit Margin, Sell-Through %, and Return Rate..
This report may provide the user a defined, SKU- level breakdown insight for further performance analysis.

​
• Dashboards for Monitoring Performance

Dashboards are designed to gauge performance, monitor the health of the business and investigate issues like a sudden increase in the price of a specific product. The dashboards are composed of multiple widgets like graphs, charts, that will help the user to real-time track the Key Performance Indicators (KPIs). It is like giving a dynamic and a live-view to the current operations to make the user understand the immediate need of the business requirements. 
Core Components of a Dashboard

1. Widgets: Displays information in the form of Graphs, Charts or Tables and provide a quick overview of a KPI 

2. Key Performance Indicators (KPIs): Measurable metrics used to track the progress.
 
3. Data Source: A system or a database from which the dashboard pulls its information
Let us understand a Use case: An e-commerce Manager would rely on “Daily e-commerce Operations Dashboard” to understand the entire activity. The dashboard in this case might include:
  • A “Today’s Net Revenue’’ scorecard that provides a quick snapshot of a financial KPI and a Year-On-Year (YOY) comparison to understand the performance. 
  • An “Orders By Hour” Line chart, which is a strong visualization tool to indicate trends and patterns in sales. 
  • The “Top 5 Returns Reasons” chart gives an immediate insight into customer feedback by showing the most common  Return.return_reason codes like “Wrong Size” or “Damaged”.
  • The “Live BOPIS Orders” Map widget, shows which Locationentities are handling a “Buy Online, Pick-up in Store” orders, to help monitor fulfillment efficiency.
    This Use case illustrates how a well-designed dashboard, with its specific combination of widgets, KPIs, and real-time data,helps to not only monitor performance but also to make quick, data-driven decisions.

​
• Alerts: Proactive Warnings for Critical Events

Position alerts are the automated early-warning system of Ekyam’s data platform. These alerts are the proactive notifications that are triggered when a specific,  critical condition or a pre-defined schedule is met within the RKG. The Alerts are vital for users to prevent potential problems before they escalate, thereby reducing significant damage. Use Case Low weeks of Supply (WOS) Alert A crucial use case to understand: → It Monitors: All Item entities are in “Active”Selling status.  → Its Condition: The alert triggers the moment the calculated Weeks of Supply (WOS) for any of these items drops below a set value, say 3 weeks. This threshold is dependent on customized factors like lead time for new orders or popularity of the product.  → The Logic: The system continuously evaluates the  Inventory_Level.sellable_qty in real-time from the RKG to show an accurate measure of how quickly the product is selling.  → The Result: The system immediately sends an alert to the team, that allows them to proactively initiate a new PurchaseOrder before the item goes out of stock.

​
• Notifications: Informational Updates

Notifications are automated informational updates that keep the users aware of normal and ongoing business processes. They are designed to keep the team informed to ensure that all the stakeholders are aware that a key action has been completed and the process can move on to the next stage.  Use case:
Let us see an example of “Purchase Order Received” notification. → It Monitors: The PurchaseOrders  Quantity → Its Condition: A notification is sent when a PurchaseOrders.status changes from “In-transit” to “Received”.  → The Trigger: The event is triggered when the warehouse staff scans the items from the PurchaseOrder shipment,the system updates the Inventoriesl.on_hand_qty in the RKG.  → The Result: A notification is sent to the inventory manager, who understands that the stock is available for allocation; and to the finance department to make them aware that the invoice from the Partners can be approved for payment. This automation reduces manual effort, streamlines the workflow and ensures that the teams are working with most updated information.

​
• Workflows: Automating Business Logic

Workflows are the most powerful capability of the Operational Intelligence Hub. It is an automated, multi-step series of actions that are triggered by an alert. This capability is not simply to notify the users, but to actively perform tasks, orchestrate processes and connect Ekyam to other applications in the technology stack.  Let us understand the below Illustration: High-Value Customer Retention Workflow → The Trigger: The workflow is initiated by a critical event.  An Alert is configured to fire when a Customers who is flagged as a “VIP” initiates a Returns for an Orders where the net_revenue was greater than $500. This highly specific condition ensures that the workflow is only activated for the most valuable customer interactions. → Workflow Steps:
  • Step 1 (Internal Tagging): The system automatically finds the corresponding Returns record and applies a “VIP Priority” tag, ensuring it is handled first.
  • Step 2 (Team Notification): The workflow sends a high-priority message to the VIP customer internal communication channel, containing the  customer_id and order_id, which helps the team to reach out to the customer if necessary. 
  • Step 3 (Coupon Generation): The workflow internally generates a unique, single-use Vouchers  for the customer’s next purchase. 
  • Step 4 (Personalized Outreach): The workflow executes an API call to the company’s email marketing platform to send a personalized email to the VIP customer. The email uses a template like “We’ve processed your return..” and includes the newly generated voucher code as a “thank you” for their loyalty.
Ekyam’s workflow automates complex business processes by linking data, action and logic. This eliminates the manual effort by orchestrating multi-step responses to specific events.