Production systems for the factory floor.

Internal routes and line-side replenishment cycles, balanced against takt. The constraint model is built from your plant's rules, not fitted to a template.

Inbound and outbound shipments, carrier assignment, load consolidation, dock and delivery-window scheduling, freight cost tracked against plan.

Continuous analysis of maritime, energy and geopolitical signals, scoring pressure on each corridor before spot rates move — so you re-route, pre-book or hedge on notice rather than on news.

Raw data cleaned and reconciled on the way in. Every planning run kept, so any decision can be reconstructed months later.

Every unit checked at production speed. Surface, weld, assembly and dimensional defects classified and logged with part-level attribution.

The model learns your defect library, your tolerances, your lighting — and is retrained as the process changes. A model trained on a general dataset finds general defects; yours finds the ones that actually come back from your customers.

Every decision recorded with its confidence score. Detection rate and false-reject rate published per model, per line. Borderline cases route to an operator, and that sign-off becomes part of the record.

SPC charts on live data, non-conformance reports raised from the defect itself, corrective actions tracked to closure, PPM trends and defect Pareto by line, shift and station.

Start from a defective unit and find every other unit that shares its cause. Start from a suspect raw batch and find everywhere it went. Scope a recall to the units actually affected instead of the whole month's output.

Component, sub-assembly and finished unit linked through production, including rework and re-inspection history.

Export packs formatted for automotive, electronics and export-market requirements, with the audit trail attached.

Every lost minute attributed to a cause and a machine: changeover, minor stops, speed loss, startup rejects. A single OEE percentage tells you there is a problem. The loss tree tells you where to stand tomorrow morning.

Station-level call for help with escalation timers. Response and resolution times are recorded, so the improvement conversation moves from "the line stopped" to "it took eleven minutes for anyone to arrive."

The same definitions everywhere, so a shift comparison means something and a plant comparison is not an argument about methodology.

Computed from connections the foundation already carries.

Controlled documents are classified at rest and watched at the endpoint. When one is attached to an email, sent through Zalo or uploaded to a website, the send is held and routed to the named approver, who sees the file, the destination and the stated reason before anything moves. Approved, it goes with that decision attached to the record. Declined, it never leaves the machine.

We surveyed the commercial DLP market before building this. Every manager-approval workflow we could find is tied to Microsoft Exchange or Microsoft 365 — which excludes any plant that does not run its mail on Microsoft. DocGuard sits on the endpoint and on the send path, so it works with the mail client and the messaging app your staff already use.

AES-256 at rest, TLS 1.3 in transit, and field-level encryption for personal and commercially sensitive columns. Keys live in your KMS or HSM, under your rotation policy and your separation of duties. We do not hold a key that opens your data — a property you can verify rather than a promise you have to accept.

Access granted by role, down to the column. Production data masked in test and development copies. Privileged-account activity monitored, with bulk reads and out-of-hours exports flagged. Every read and every change to a sensitive table written to an audit log the database administrator cannot quietly edit.

Vietnam's personal data protection framework — Luật Bảo vệ dữ liệu cá nhân and Nghị định 356/2025/NĐ-CP — took effect on 1 January 2026. Data inventory, lawful basis, retention limits, deletion on request, cross-border transfer records and incident reporting are obligations that sit with the enterprise, not with its vendors. The system is what turns them from a policy document into something you can demonstrate on the day you are asked.