Industrial AI · SaaS Platform

Factory data that
explains itself.

Febriansyah Tech System is an AI-powered manufacturing intelligence platform that connects factory PLC and machine data with Claude. It turns real-time production data into insight for OEE monitoring, anomaly detection, production analysis and machine performance — and lets your production team ask questions in plain language.

Built on ClaudeRead-only plant integrationOn-prem or cloud
< 1s
Telemetry to context
4
Core analytics modules
NL
Natural-language querying
Line A · Shift 2 live
87%
OEE
Availability94.2%
Performance91.6%
Quality99.1%
Cycle time · last 12 batchesspike detected
!
Anomaly · Press-02

Cycle time drifted +14% over the last 9 batches. Matches a tooling-wear signature last seen 41 days ago.

Claude · analysis

“Shift 2 lost 12 min at Press-02 to micro-stops — 68% of the shift’s shortfall.”

Reads from the floor
Siemens S7Allen-BradleyModbus TCPOPC-UAMQTTHistorian / SCADA
The gap on the floor

Factories generate the data. Nobody has time to read it.

Production data already exists in PLCs, SCADA and historians — but it reaches people as dashboards nobody opens or spreadsheets compiled after the shift is already lost.

Today

Data-rich, insight-poor

  • Dashboards report what happened, hours after the fact
  • Anomalies found by operators noticing something feels off
  • Root-cause analysis manual across SCADA, ERP and paper logs
  • Analyst time spent exporting, not interpreting

With Febriansyah Tech System

Ask, and get an explanation

  • Metrics kept live and contextualised against the asset model
  • Anomalies surfaced with the time window and signature that caused them
  • “Why did Line A miss target last night?” answered in seconds
  • Every answer cites the production data it was derived from

Platform capabilities

Four lenses on the same production reality

Claude sits on top of a manufacturing data model, so each module shares one version of the truth about your line.

01

OEE Monitoring

Availability, performance, and quality streamed from the line in real time — with loss trees that point to the exact station eating your capacity.

02

Anomaly Detection

Statistical baselines plus Claude reasoning flag drift, micro-stops, and out-of-tolerance cycles before they become scrap or downtime.

03

Production Analysis

Shift, batch, recipe, and SKU-level breakdowns generated on request. Ask for last night's shortfall and get the contributing causes.

04

Machine Performance

Cycle time, throughput, and utilisation per asset — benchmarked against its own history so degradation is visible, not assumed.

Ask the plant · natural language layer
Production Manager
Why did Line A miss target on the night shift, and what should we fix first?
Febriansyah Tech System · Claude
Grounded in Shift 2 · Line ALine A finished at 87% OEE against a 93% target. The shortfall breaks down as:

1. Micro-stops at Press-02 — 12 min lost, a +14% cycle-time drift consistent with tooling wear (last observed 41 days ago).
2. Material wait at Station 4 — 6 min, correlated with a late upstream batch release at 02:14.

Fix first: schedule a tooling check on Press-02 before the next run — it accounts for 68% of the gap and typically returns within one cycle.
Every answer cites its metrics & time window·No control-loop writes·Audit trail per query
How it works

From PLC register to plain-language answer

A four-stage pipeline that keeps industrial data trustworthy all the way to the reasoning layer.

STEP 01

Connect

Edge collectors read PLC registers and machine telemetry on the plant floor. Read-only, no changes to control logic.

OPC-UA · Modbus TCP
Siemens S7 · Allen-Bradley
MQTT · Historian
STEP 02

Contextualise

Raw tags are normalised into a manufacturing ontology: assets, lines, shifts, recipes, and units of measure.

Time-series store
Asset model
Shift & recipe graph
STEP 03

Reason

Claude works over retrieved production context — metrics, events, maintenance notes — through RAG and agentic tool use.

Retrieval (RAG)
Tool-calling agents
Evaluation harness
STEP 04

Explain

Answers come back as language your production team can act on, with the numbers and time windows they were derived from.

Natural language
Cited metrics
Shift-ready summaries

Who’s building this

Built by someone who has stood on the factory floor

Independent, bootstrapped software company. Founded and engineered by a developer with 9+ years in manufacturing IT — not a theory-first AI project.

F
Febriansyah
Founder & Software Engineer

9+ years building production systems for manufacturing — real-time OEE telemetry on automotive assembly lines, MES/LES support for FMCG plants, and SAP ERP integrations at enterprise scale.

Based inBekasi, West Java, Indonesia
FundingBootstrapped
FocusIndustrial AI & SaaS
Factory-floor track record
Musashi Auto Parts IndonesiaIT Programmer & IoT Engineer

Built a real-time OEE telemetry dashboard on the factory floor using Node.js, WebSockets, Node-RED and industrial PLC hardware — cutting downtime-tracking latency from hours to sub-second.

Metrodata GroupAnalyst & Application Developer

Sustained 99.9% uptime for Logistic & Manufacturing Execution Systems (LES/MES) across manufacturing facilities, resolving critical production incidents.

Sukanda DjayaFull Stack Developer

Architected an SAP ERP integration portal that replaced external vendor contracts, saving 800 million IDR per year.

This is why the platform starts with PLC reality and production constraints — not with a model demo.


What we’re looking for

We’re looking for Claude API credits and technical guidance

We want to develop and validate the platform against real manufacturing data — and we need both runway on the Claude API and engineering depth to get the architecture right.

Support · 01
Claude API credits

Credits let us run the platform against continuous, high-volume factory telemetry during pilots — measuring latency, cost per query, and reasoning quality on real production data instead of synthetic samples.

Purpose: validate with real manufacturing data
Support · 02

Technical guidance

G1
RAG over industrial dataRetrieval design that keeps metric semantics, asset hierarchy, and time windows intact — so answers are grounded, not hallucinated.
G2
Agentic workflowsTool-calling patterns for querying time-series, comparing shifts, and chaining diagnostics across multiple machines.
G3
Production AI architectureLatency, cost, and reliability trade-offs for serving Claude against continuously arriving factory telemetry.
G4
Evaluation & reliabilityEval sets built from real manufacturing data, so we can measure answer accuracy before a factory trusts the output.

This support helps us validate the product with factories and scale it into a production SaaS platform.

Roadmap

Validate, prove, then scale

Phase 01 — Now

Validate on real data

Wire live PLC and machine feeds from partner factories into the platform and prove the analytics against ground-truth production records.

Seeking pilot factories
Phase 02 — Next

Prove it with factories

Run structured pilots with production teams, harden the anomaly models, and build the evaluation sets that make results defensible.

Design partners
Phase 03 — Later

Scale into SaaS

Multi-tenant onboarding, connector library, and predictable unit economics — a production SaaS platform for manufacturing intelligence.

Commercial release
Work with Febriansyah Tech System

Let’s put your factory data to work.

If you run a plant and want to pilot the platform on real production data — or you’re on the Claude team and can support us with credits and technical guidance — we’d like to talk.

SeekingClaude API credits
SeekingRAG & agentic workflow guidance
SeekingPilot factories with real machine data