ASI Institute

cSignals Platform – FAQ

Signals Platform – FAQ

Version 1.1 | June 2026

Signals is a data orchestration enterprise alignment platform. It unifies external and internal data sources: BI, local ERP, CRM, procurement, inventory databases, etc – with the real-time external data they need. Examples: telemetry—commodity spots, macro indices, and supply chain updates. All under a secure, three-layer custom AI routing architecture.

Quick Links:
Project Page: https://asiinst.com/csignals | R&D Paper: Read the Paper | Repo: GitHub

Part 1: Introduction & Strategy

For business leaders, analysts, and operations managers.

1.1 What exact problem does Signals solve?

Signals solves the “Enterprise Data Tax” on strategic thinking.

Example: In commodity-exposed industries, analysts manually spend hours extracting data, normalising units, refreshing pivot tables, and writing comments before strategic analysis can even start. Signals automates this bridge, synthesizing internal BI, CRM, and ERP parameters with external market data in under 30 seconds with zero manual friction.

1.2 How is this different from our existing Power BI and SAP reports?

Traditional BI systems are built to report on historical internal data that has already been cleaned and structured. They do not bridge the gap to live, dynamic external market signals (e.g., crude pricing shifts affecting MDI feedstock costs with a 2–4 week lag).

Signals feeds your BI—it doesn’t replace it. It outputs clean, pivot-ready Excel workbooks directly into your Power BI inputs, and lets you drag and drop database exports to get instant market-contextualized reports.

1.3 What is a Signals “Avatar”?

An Avatar is a purpose-tuned vertical instance of the Signals platform configured for a specific industry’s inputs, feedstock chains, and decision criteria.

For example, ChemSignals (Avatar 1) is calibrated specifically for the petrochemical value chain, tracking crude derivatives, natural gas, feedstocks like benzene/aniline, and macroeconomic parameters to output weekly intelligence briefs and margin indicators.

1.4 What other industries can use the Avatar model?

The platform architecture is vertical-agnostic and generalizes to any sector where margins are driven by live inputs that fluctuate faster than the internal reporting cycle. Examples:

  • PharmaSignals: supply chains, contract manufacturing, FDA regulatory updates.
  • AgriSignals: Grain, oilseed, and livestock feedstocks, CBOT futures, weather metrics.
  • EnergySignals: Power spot prices, gas storage levels, renewable capacity, grid congestion.
  • MetalSignals: Steel, aluminum, rare earth inputs, LME prices, tariff policies.
1.5 What is the cost of data delay? Example: feedstock transmission lag.

In feedstock chains with a 2–4 week transmission delay (like crude-to-MDI), margin compression occurs silently before pricing renegotiations. A 1% margin compression from an undetected feedstock shock can cost a major chemical manufacturer millions of dollars in a single quarter. Signals detects these movements upstream, enabling proactive surcharge activation.

Part 2: Technical & Architecture

For CTOs, developers, and technical data auditors.

2.1 How does the iSLM ETL Router work?

The core of the architecture is an internal Small Language Model (iSLM) in the 7B–13B parameter range (e.g., Llama 3.1 8B, Mistral 7B). Rather than generating text directly, the iSLM acts as a deterministic router at temperature 0.0, classifying queries into four routing pathways:

  • RAG: routes queries to local static document databases.
  • MCP: queries live external APIs and databases via the Model Context Protocol.
  • hybrid: chains retrieval pipelines in sequence.
  • direct: handles queries directly from local context.
2.2 How do you guarantee corporate data privacy?

We enforce a strict policy of Data Locality.

The iSLM, RAG vector database, and MCP agents run entirely within the enterprise’s private cloud VPC or local infrastructure. No proprietary document chunks, procurement costs, or database parameters are sent to external, shared AI APIs. All data reasoning remains contained within the corporate boundary.

2.3 What role does the Model Context Protocol (MCP) play?

MCP provides a unified, open-standard connector layer. Instead of writing custom API wrappers for every source, MCP allows the platform’s orchestration layer to query live external market feeds (yfinance, FRED, RSS feeds) and internal systems (like SAP ERP exports) dynamically using the same model-accessible interface.

2.4 How does the platform prevent model hallucinations?

Hallucinations are eliminated by separating routing logic from synthesis:

  1. The iSLM acts solely as a router and does not generate data.
  2. The requested context is pulled deterministically from RAG (static docs) and MCP (live feeds).
  3. The synthesis layer receives this verified context and formats the output, matching every metric back to its original source hash.
2.5 What is the default technology stack?
  • Frontend: Next.js (React) using Recharts panels for data visualization.
  • Orchestration: Python pipelines integrating `yfinance` and the FRED API.
  • Integrations: SheetJS (`xlsx`) for generating pivot-ready bidirectional reports.
  • Routing & Inference: Local small language models (7B–13B) run via containerized endpoints.
Disclaimer: All analytical parameters are estimates based on active telemetry. Please review our Terms and Conditions for more details.