MODULE EXPLORER
THE QUESTION IT HELPS ANSWER
CONCEPTUAL PRODUCT WORKFLOW
MANUFACTURING EXECUTION SYSTEM + INDUSTRIAL IoT
Every machine.
Every shift.
One clear picture.
Your production, machines, quality and people.
Connected in one manufacturing control layer.
See what’s happening. Understand what needs attention.
Keep your factory moving.
Built for the factory floor From one line to multiple plants
FACTORY COMMAND CENTERINTERACTIVE PRODUCT CONCEPT
PLANT 01 / PRODUCTION CELL A
CONNECTED DEVICE
PRODUCTION / PCS8,420 / 10,000
TARGET ACHIEVEMENT84.2% Progress you can see
MACHINE STATUS18 running 3 idle 1 breakdown
SELECT A MACHINE TO EXPLOREILLUSTRATIVE DATA · NOT A LIVE FEED
THE FACTORY HAS CHANGED.
YOUR VISIBILITY SHOULD TOO.Your factory already
YOUR VISIBILITY SHOULD TOO.
Your factory already
generates data.
Put it to work.
When plans live in Excel, updates live in WhatsApp, and machine data lives nowhere, the whole picture arrives too late. Poldu is designed to bring those pieces into one operating view.
FROM SCATTERED INFORMATION TO OPERATIONAL CONTROL
ONE FACTORY. TWO WAYS TO RUN IT.
Production spreadsheets Shift updates in chat Manual quality registers Disconnected machines
01 / THE MANUFACTURING CONTROL LAYER
One system.
The whole operation.
Explore the work behind every production number.
Select an area to see how it connects.
EXECUTE
CONTROL
UNDERSTAND
Company / Plant / Department / Line / Machine
02 / FROM PLAN TO PRODUCTION
A work order comes in.
Everyone knows what’s next.
Follow the job from customer demand to dispatch.
One work order. A traceable execution story.
RESPONSIBLE TEAM
Linked to WO-2026-0048
A SEPARATE PIECE-PRODUCTION EXAMPLE
TARGET10,000 pcsPRODUCED8,420=GOOD8,230+REJECTED19084.2%TARGET ACHIEVEMENT
Good and rejected quantities remain traceable to the plan, machine, shift, employee, and production entry.
THE MACHINE CONTROL CENTER
Don’t chase updates.
See the shop floor.
Running, idle, warning, or breakdown.
Go from a machine’s status to its operating context.
PLANT 01 — FLOOR PLANEXAMPLE CONFIGURATION
PRODUCTION AISLE / ZONE A
MATERIAL IN QC & PACKING
MACHINE DETAILS
Utilization
Production
Downtime
Last activity
BREAKDOWNINVESTIGATERESOLVERUN
QUALITY. TOOLING. RELIABILITY.
Protect what you make.
Look after what makes it.
Connect inspections to production.
Connect tooling care to actual usage.
01 / QUALITY CHECKPOINTCatch the issue.
Catch the issue.
Close the loop.
Configure checks for your product and process. Record the result, route rejected pieces, and keep rework visible.
PARAMETERACCEPTANCERESULT
Weight24.5–25.5 g25.1 g
Diameter30 ± 0.2 mm30.1 mm
SurfaceNo visible defects
Example parameters for a molded part. Click the surface result to explore pass / rework.
02 / DIE & TOOL LIFEEvery shot
Every shot
leaves a record.
LIFE USED%OF 500,000 SHOTS
INJECTION MOLD A-104
shots remaining
Production usage Shot count Service action
Illustrative 70% review threshold. Life and maintenance tracking—not a prediction of tool failure.
MAINTENANCE EXAMPLEInjection Molding Machine 08
LAST SERVICE12 Jul 2026
PLANNED SERVICE INTERVAL
NEXT SERVICE12 Aug 2026
UPCOMING IN THIS SAMPLE 03 / INDUSTRIAL IoT — THE PHYSICAL MEETS THE DIGITALBring the factory floor
Bring the factory floor
into Poldu.
A machine cycle is more than a signal. With the right connection and context,
it becomes a production record, a status update, or a reason to act.
SIGNAL JOURNEY / SELECT A CONNECTION
CONCEPTUAL ARCHITECTURE
CONTEXTUALIZED TELEMETRY
Production counts Machine status Role-based alerts MES dashboards
THE COUNTING LABCONCEPT EXPLAINER
A cycle. A piece. A die shot.
They aren’t the same number.
For a mold with multiple active cavities, one machine cycle may produce several pieces. Tooling usage still records the shot.
×
THEORETICAL PIECES
DIE SHOTS
Conceptual arithmetic, not a verified Poldu calculation. Actual good quantity depends on active cavities, rejects, validation rules, and the configured implementation.
Enter a whole number of cycles between 1 and 1,000,000.
SIGNALS THAT DEMAND ATTENTIONSIMULATED TELEMETRY
TemperatureExample threshold: above 90°C95°CCRITICAL
VibrationExample threshold: above 10 mm/s8.2mm/sNORMAL
PressureExample range: 4–6 bar4.8barNORMAL
Threshold crossed → alert raised.
Route the temperature exception to the responsible operator for investigation.
Sensor limits are examples, not engineering safety limits. Thresholds must be validated for the specific equipment and process.
DEVICE HEALTH / GW-PLANT01-08
HEARTBEAT
FIRMWARE / NETWORK1.0.0 / Internal device network
Device identity → company → machine → telemetry. The design uses authenticated device access and machine mapping. Protocols, API-key handling, buffering, and processing behavior require implementation and site validation. No real credentials are shown.
04 / SAME CONTROL LAYER. YOUR MANUFACTURING REALITY.
Your industry has its own language.
Your system should understand it.
These configurations explain how manufacturing requirements differ. They are not verified prebuilt templates, database features, or regulatory compliance claims.
05 / THE FACTORY, IN NUMBERS
From the shop floor.
To your next decision.
Explore a working interface preview.
Change the shift, inspect the numbers, find the priority.
MONDAY, 17 AUGUST 2026
Your factory at a glance.
Here’s how the floor is performing this shift.
2 operating priorities: investigate the temperature exception on IM-08 and check the breakdown on CUTTING-02.
Production of 10,000 planned pieces
Achievement %Target vs. actual
Good production first-pass good quantity
Downtime minReview machine events
Active work orders
View workflow ↗| Work order | Product | Progress | Status |
|---|---|---|---|
| WO-0048 | Modular kitchen | 52 / 80 | In production |
| WO-0049 | Cabinet panel | 460 / 500 | In quality check |
| WO-0050 | Drawer assembly | 50 / 200 | Material review |
Recent activity
SAMPLE FEEDQC batch cleared Cabinet panel · 2 min ago
Service threshold reachedDie A-104 · 8 min ago
24 IoT devices onlineGateway health · 10 min ago
Swipe to explore the full dashboard. Change the shift or chart to interact.
ONE SHARED TRUTH.
THE VIEW THAT MATTERS TO YOU.Different responsibilities.
THE VIEW THAT MATTERS TO YOU.
Different responsibilities.
The same factory.
A PRACTICAL PATH TO CONNECTED OPERATIONS
Start with your reality.
Build a connected workflow.
Map how your factory actually runs.
Then connect the next part of the picture.
VISIBILITYKnow what is happening.
RESPONSESee the issue earlier.
CONTROLGive the next action an owner.
BUILT AROUND MANUFACTURING.Practical questions.
Practical questions.
Clear answers.
Poldu’s product vision is a shared operating layer for production, machines, quality, people, tooling, and industrial data.
What you’re exploring
The screens on this website are interactive product concepts. Manufacturing integrations and workflows must be confirmed against your deployment. Use the enquiry form to prepare a demo email for the team.
What is a Manufacturing Execution System (MES)?+
An MES connects production plans with what actually happens on the factory floor. It brings work orders, machine activity, production quantities, people, quality checks, and losses into one operational record so teams can understand progress and follow up on exceptions.
Who is Poldu designed for?+
The product concept is intended for manufacturing businesses and the people who run them: factory owners, plant managers, production teams, quality leads, maintenance teams, and supervisors. A walkthrough should confirm fit against your actual process.
Can Poldu work across different industries?+
The proposed operating model can be adapted around different products, production units, processes, and QC parameters. The eight sector examples on this website are illustrative configurations, not verified prebuilt industry templates or compliance claims.
How would machine data reach Poldu?+
The conceptual flow is machine → PLC or sensor → device or gateway → authenticated API → company and machine mapping → telemetry processing. Protocol compatibility, sensor quality, buffering, and processing rules must be confirmed for each implementation.
Does all production have to come from IoT?+
No. The product architecture described in the brief includes production entries alongside IoT concepts. Manual entry and machine integration can be considered during discovery; which workflows are available must be confirmed against the deployed product.
How does quality management fit into production?+
The intended workflow links an inspection to a production entry, checks the configured product parameters, and records pass, rejection, or rework. The specific checks and release rules depend on the manufacturing process.
What does maintenance and tooling tracking cover?+
The concept includes downtime incidents, service history, tool and die usage, shot counts, and maintenance thresholds. A life-used indicator tracks recorded usage; it does not predict when a tool will fail.
How are companies, tenants, and roles handled?+
The supplied product brief describes a tenant-based structure with users, departments, roles, permissions, and audit logs. Tenant isolation and MES authorization cannot be verified from this marketing codebase and must be reviewed in the actual product.
Are these dashboards showing real factory data?+
No. Every machine status, counter, chart, work order, and sensor reading on this public website is an illustrative product preview. No factory equipment is connected to this website.
Does the website include live AI or predictive maintenance?+
No. The product vision includes contextual insights and a path toward predictive use cases, but this website does not run an AI service or predict equipment failures. Such capabilities require actual implementation, suitable historical data, and site validation.
YOUR FACTORY. YOUR WORKFLOW. YOUR NEXT STEP.See your factory
See your factory
through Poldu.
Tell us how your manufacturing operation works.
Let’s explore where better visibility could make the difference.
ONE FACTORY.ONE CONTROL LAYER.
FLOOR → SIGNAL → CONTEXT → DECISION