What IoT.Factora is

IoT.Factora is FactoraERP Module 11. It is the plant IoT layer: device registry, live telemetry, alerts, floor map, production counters, OEE, energy, maintenance, Command Center, Executive (admin), and an evidence-bound copilot.

It is not a second ERP. Do not sell it as Inventory, Procurement, QC, Warehouse, HR, or Finance. Those stay in FactoraERP (or another ERP). Settings can store a Factora org/plant code or an integration pack. Live ERP sync is later, not today.

Two hosts

Ops is not a factory account. A plant operator cannot open /ops on the plant host.

Plant roles (from login, not a switch)

• Admin: registry, tokens, simulator (demo only), connectors, team, OEE config, Executive
• Maintenance: alerts, work orders, Connect and Audit; no Executive
• Operator: floor, production, ack alerts, shift, view OEE/energy/maintenance/copilot

Ops roles: owner (create/patch/enter factories) and viewer (read fleet only).

Demo vs live

Starter and demo plants use telemetryMode=demo. The simulator ticks and the UI must show DEMO. A live plant (telemetryMode=live) does not run the simulator. Never present simulator numbers as customer production.

Demo factory codes: demo-food, demo-pharma, demo-construction, demo-processing. Local demo passwords are {slug}-{role} (example demo-food / admin / demo-food-admin). Production new factories get random passwords returned once at create.

What production ingest actually is

Customers send a numeric reading with a device ingest token:

• HTTP POST /api/ingest with Authorization: Bearer <token> and {"value": 4.2}
• MQTT to iot.factoraerp.com:1883, username = device code, password = ingest token, topic factora/{factory-slug}/devices/{device-code}/telemetry

That is the supported live path. LoRaWAN, Modbus, and OPC land here after a vendor gateway or network server.