aPlanner is in MVP validation (Oct–Dec 2026). Figures are design targets. Join the 2027 Korea pilot →
ARCHITECTURE & INTEGRATION

Fits the fab's existing stack. Data never leaves the site.

aPlanner connects to what the fab already has — MES, SAP, yield databases, even the planners' spreadsheets — through read-only connectors first. Nothing is ripped out.

Join the 2027 Korea pilot programTalk to the founder
aPlanner service logic: fab data sources → data layer → AI core → planner → back to MES / ERP
Service logic — MES · ERP · yield / bin DB · spreadsheets → data layer (aFlow · aConnect) → AI core → planner workspace → back to MES / ERP

How data flows

From the fab's systems into one versioned planning model, through the AI core, to the planner, and back.

1

Fab data sources

MES (WIP, tool status) · SAP ERP (orders, BOM) · yield / bin database · planner spreadsheets

2

Data layer

aConnect connectors · aFlow pipelines · unified planning model · on-prem / private cloud

3

AI core (aCore)

Forecast · optimize · simulate · explain — the four modules on one versioned plan

4

Planner workspace

Korean / English UI · compare scenarios · approve, edit or reject every change

5

Back to MES / ERP

Approved plan written back after sign-off; live KPIs and anomalies retrain the models

Deployment, integration, governance

Deployment

On-premise or private cloud inside the fab network — no production data leaves the site
Air-gapped option for the most restrictive fabs
SaaS on the AWS Seoul region for suppliers and SMEs
Kubernetes packaging — the same code everywhere

Integration

Pre-built connectors for in-house MES, SAP ERP, yield / bin databases and Excel imports
Read-only first; write-back of approved plans only after sign-off
Korean SI / MES partners for delivery; Siemens Industry Software architects advise on MES / PLM integration
REST APIs and file-based exchange for everything else

Security & governance

Role-based access control and SSO
Full, immutable audit trail of every plan change
Planner-approval workflow — AI recommends, people decide
Roadmap: SOC 2 Type II (planned 2027–28) · ISO 27001 (2028) · K-ISMS (planned)
Service topology of the aPlanner MVP
Service topology of the MVP
TECHNOLOGY

Same code on-prem and in the cloud

BackendPython / FastAPI
DataPostgreSQL + TimescaleDB
OptimizationOR-Tools / MILP (CP-SAT)
AI / MLPyTorch, XGBoost
FrontendReact (KR / EN)
RuntimeKubernetes on-prem or AWS Seoul

70%+ AI-assisted development. The MVP runs on synthetic fab data; connectors are exercised against representative MES / ERP schemas until the first pilot.

Connectors

The Korean fab stack is the default, not a project. Read-only first; write-back of approved plans only after sign-off.

MES

In-house fab MES
Commercial MES via Korean SI / MES partners
WIP, lot states, tool status — read-only first

ERP

SAP S/4HANA
SAP ECC
Orders, BOM, commitments

Yield / bin data

Probe & sort databases
SPC / metrology feeds
Yield and bin distributions per step

Planner spreadsheets

Excel imports
CSV / SFTP drops
Bootstrap the model before full integration

PLM / recipe master data

Route and recipe masters (advisory scope)
Recipe and route master data

Custom systems

Legacy and homegrown applications
REST API, file-based exchange

Start with a planning readiness assessment

In 2–4 weeks we review your MES, ERP and yield data, your constraints and your planning process, and scope the pilot on one line.

Join the 2027 Korea pilot programTalk to the founder