Module 11 of FactoraERP · Kenya
Live temperature, energy and machine data, in the same system as your production, maintenance and finance. Built in Kenya, priced in shillings.
Twenty minutes. Your rooms, not a slide deck. Sign in lives at the app, not here.
01
When the connection to the cloud drops, the gateway keeps readings and syncs them later. The screen shows a buffered count, and an operator can choose Sync now or Pause sync. That is store-and-forward for a dropped link. It is not a claim that a battery rides through a power cut.
02
Connectors are MQTT, OPC-UA, Modbus, PLC and Gateway. MQTT subscribes to a broker. OPC-UA is mapped node by node, for example ns=2;s=Line1.Crusher.Temperature. Readings can also arrive over HTTPS with an ingest token.
03
Alerts go out on WhatsApp, SMS and email, and they escalate if the person on shift does not take them.
04
Support is from the FactoraERP team in Kenya. The hours, and which channel answers a 2am cold-room alert, are not published.
The difference
A reading that stays on a dashboard is a notification. The path runs from the probe to a person, a work order, the batch and the cost.
A monitored point reports onto the floor: temperature, door, energy, vibration, machine state, and the rest of the catalog.
Alerts go out on WhatsApp, SMS and email, and they escalate if the person on shift does not take them.
An alarm opens a maintenance work order on its own, assigned to the shift, instead of waiting for someone to retype it.
The person on shift taps the card. The alert stores their name, not a role code. They can Resolve it, or ask the copilot about it.
Temperature records stay on the batch that was in the room, and the plant can produce a PDF compliance report from them.
Spoilage, energy and downtime land on the batch in finance, in the same record as the lot.
Product tour
Floor, map, alerts, dashboards and production are captures from the Demo food plant, with simulated telemetry. They are not a customer. The batch report is still a drawn layout. The film slot under the tour is sixty seconds, and it is empty on purpose.
LOT-1842, sample
Temperature against one lot · illustrative
| Time | Point | °C | Result |
|---|---|---|---|
| 00:48 | Room B | 3.9 | In band |
| 01:12 | Room B | 5.4 | Excursion |
| 01:18 | Acknowledged · Night-shift technician (sample) | ||
| 01:46 | Room B | 3.7 | Back in band |
0:60 · not published yet
60-second plant walk-throughA manager opens the live floor, a room leaves its band, someone acknowledges it by name, and the reading is still there in the morning. Drop an mp4 at public/tour.mp4 and set tourVideo.src in src/data/site.ts.
What it connects to
FactoraERP IoT runs at iot.factoraerp.com with your factory’s own sign-in. The ERP setting is FactoraERP, another ERP through an integration pack, or none. A plant does not have to replace its system to use the sensors. The parent system still covers production, inventory, quality and finance. A reading meets them because it is already in the plant record.
Recipes, runs and yields. Part of FactoraERP, published on factoraerp.com. Not a claim that every screen is wired to a probe.
Materials, packaging, finished goods. Part of FactoraERP, published on factoraerp.com. Not a claim that every screen is wired to a probe.
Suppliers, requests, spend. Part of FactoraERP, published on factoraerp.com. Not a claim that every screen is wired to a probe.
Lab tests and checkpoints. Part of FactoraERP, published on factoraerp.com. Not a claim that every screen is wired to a probe.
Locations and movements. Part of FactoraERP, published on factoraerp.com. Not a claim that every screen is wired to a probe.
Farm gate to dispatch. Part of FactoraERP, published on factoraerp.com. Not a claim that every screen is wired to a probe.
People, attendance, labour. Part of FactoraERP, published on factoraerp.com. Not a claim that every screen is wired to a probe.
Costing, invoices, payments. Part of FactoraERP, published on factoraerp.com. Not a claim that every screen is wired to a probe.
The KPIs management already asks for. Part of FactoraERP, published on factoraerp.com. Not a claim that every screen is wired to a probe.
Connectors are MQTT, OPC-UA, Modbus, PLC and Gateway. MQTT subscribes to a broker. OPC-UA is mapped node by node, for example ns=2;s=Line1.Crusher.Temperature. Readings can also arrive over HTTPS with an ingest token. PLC brands are the line we will not print until a unit has been read. Integrations.
Offline
Thin mobile coverage is a design constraint, not an edge case. A cloud chart that resumes in the morning with a hole where the link died is not a history of that hour.
When the connection to the cloud drops, the gateway keeps readings and syncs them later. The screen shows a buffered count, and an operator can choose Sync now or Pause sync. That is store-and-forward for a dropped link. It is not a claim that a battery rides through a power cut.
A power cut is a different test. The demo simulator can play one. That does not publish a battery, and the gateway’s make and model are still open.The offline page keeps the two questions apart.
Solutions
Milk reception, cold rooms and packhouses, stores and process areas are the example workflows on the FactoraERP IoT page. They are not customers. The pages below stay inside that line, and mark anything past it.
Cold chain
A cold room does not fail in the Tuesday meeting. It fails at 1am, while the consignment that has to fly or truck in the morning is already inside it. FactoraERP IoT puts that room on one screen and keeps the name of whoever answered.
Read the pageDairy
Reception is the last moment you still know whose milk it is. The cooling that follows is where a warm tank becomes everybody’s problem and nobody’s name. The product example is built around that handoff.
Read the pageFood and beverage
Most food plants in Thika, Ruaraka and Athi River already generate the numbers. They live on a panel, a chart recorder, or a book the line supervisor keeps. The missing piece is one list the next shift can trust.
Read the pageHorticulture
Flowers and vegetables leave a packhouse on a clock. The buyer does not want a screenshot of a gauge. They want a history: which room, which hours, whether it left the band, and who did something about it.
Read the pageManufacturing
Plants do not suffer from a lack of screens. They suffer from a reading that never becomes a job, and a job that never becomes a cost. FactoraERP IoT holds the floor, the work order and the batch cost in one sign-in.
Read the pagePharma storage
Medicine stores live inside a narrower band than a packhouse, often 2–8°C, and inside a stricter question: who knew, and when. FactoraERP IoT can show the reading and the name. It does not arrive with a validation pack we have not written.
Read the pageCompliance
Time in East Africa Time, the point, the reading, the band, the result, and the name that answered. Temperature records stay on the batch, and the plant can produce a PDF. The table on this page is a sample layout, not an export from the demo.
Sample only
Sample batch temperature logIllustrative layout of a batch temperature record. Not an export from the demo plant, and not a customer. Names and the lot number are samples.
| Time (EAT) | Point | °C | Band | Result | Acknowledged | Batch |
|---|---|---|---|---|---|---|
| 18:40 | Cold room A · probe 1 | 2.8 | 0–4 | In band | — | LOT-1842 |
| 21:05 | Cold room A · probe 1 | 3.5 | 0–4 | In band | — | LOT-1842 |
| 00:48 | Cold room B · probe 1 | 3.9 | 0–4 | In band | — | LOT-1842 |
| 01:12 | Cold room B · probe 1 | 5.4 | 0–4 | Excursion | Night-shift technician (sample) · 01:18 | LOT-1842 |
Pricing
USD 143 for four points on Watch, software only, illustrative.Hardware is not in that number.
KES 18,500Illustrative monthly software fee for four monitored points on Watch, as a bundle. Hardware is not included and has no price yet.
Example fee · first room
KES 5,000USD 39 per point / month
An example monthly software fee for a first room. The modules on this site are the product. This column is not a signed package.
Example fee · a running plant
KES 11,500USD 89 per point / month
A higher example fee once the plant is in production. Not a different feature list, and not a quotation.
Example fee · the record travels
KES 19,200USD 149 per point / month
A higher example fee when the temperature history has to leave with the lot. Not a quotation.
| What you are paying for | Watch | Run | Export |
|---|---|---|---|
| Floor, floor map, dashboards | Included | Included | Included |
| Production and batch traceability | Included | Included | Included |
| OEE, downtime Pareto, production events | Included | Included | Included |
| Alerts: name, Resolve, Ask about this | Included | Included | Included |
| Maintenance, energy, Command Center | Included | Included | Included |
| Copilot, Academy, 365-day audit CSV | Included | Included | Included |
| Store-and-forward when the link drops | Included | Included | Included |
| MQTT, OPC-UA, Modbus, HTTPS ingest | Included | Included | Included |
| WhatsApp, SMS and email, with escalation | Included | Included | Included |
| Alarm opens a work order | Included | Included | Included |
| Batch temperature record and PDF report | Included | Included | Included |
| Cost and finance linked to the batch | Included | Included | Included |
Proof
There are no logos on this site, and there will not be until a plant agrees to be named. FactoraERP already publishes a founding programme: hands-on onboarding, a direct line to the people who build it, and a say in what gets built next. IoT founding plants are the same offer, aimed at one room that is already costing you sleep.
We will not borrow a South African case study, a regulator’s crest, or a percentage uptime. If you want a reference call, the honest answer today is that we do not have one to give.
A cold room, a reception bay, or a store. A person on the night shift who will acknowledge by name.
Questions from the floor go to the FactoraERP team, not a queue in another country. Hours are still to be published.
What we ask of a founding plant, and what we will not invent in return.
Read the programmeSecurity and trust
MFA is required for every user. Roles are admin, maintenance and operator. A failed login is written to the audit log. Tap a card to acknowledge it. The person's name is stored on the alert, not a role code. From the same card you can Resolve it, or open Ask about this.
The audit log is append-only and kept for 365 days. A plant can export it as CSV. Command Center exports CSV as well.
No KEPHIS, KEBS, ISO, SOC or GDP certificate is claimed for FactoraERP IoT. No uptime percentage is published, and no public status feed is connected.
Questions
No. FactoraERP IoT Sensors is Module 11 of FactoraERP. It runs at iot.factoraerp.com with your factory’s own sign-in. This website explains that module. The rest of the manufacturing system lives at factoraerp.com.
At iot.factoraerp.com/login. The app is login-only. There is no public trial on this marketing site. Book a demo if you want a walk-through on your own rooms first.
Not yet, and this site will not invent them. FactoraERP runs a founding customer programme: hands-on onboarding, a direct line to the team, and a say in what gets built. That is the honest offer.
The pricing page shows example software fees in Kenya shillings and US dollars, inside the USD 30–250 per device per month range typical of this category. They are drafts for discussion, marked as placeholders, not a quotation. Hardware is not priced yet.
When the connection to the cloud drops, the gateway buffers readings and syncs them later. You can see the buffered count, and you can Sync now or Pause sync. A power cut that kills the gateway is a different test. We do not publish a battery or a gateway model. The offline page keeps those apart.
Connectors are MQTT, OPC-UA, Modbus, PLC and Gateway. MQTT subscribes to a broker. OPC-UA is mapped node by node. Readings can also arrive over HTTPS with an ingest token. No PLC brand is named on this site. Bring the nameplate and we will say whether that unit has been read.
Yes. An alarm opens a maintenance work order. The maintenance module also has a calendar, preventive plans, MTBF and maintenance cost. Acknowledgement is separate: tap the card, and the person’s name is stored on the alert, not a role code.
No certificate is claimed. A temperature log with times and a name is what buyers and inspectors usually ask to see. Certification, if it exists later, will be published with a number and a scope. It is not implied by this website.
Twenty minutes on your plant, not a slide deck. Have the room names, the temperature bands, and a photo of the panel ready. You will leave knowing what the live floor would show, and which claims on this site are still open.
No. The ERP setting is FactoraERP, another ERP through an integration pack, or none. The floor, production, maintenance, energy and alerts are the IoT app either way.
Book a demo
Bring the room names and the bands you already run. We will put them on the floor and say which commercial details on this site are still drafts.
