Vietnam Production Management System: RFP Guide

A Vietnam production management system project is not mainly a translation exercise. The real design question is where to draw the boundary between electronic invoice and document data, employee or visitor personal data, lot and quality records owned by the Vietnam factory, and the shared items, routings, equipment definitions and KPIs governed by headquarters. This guide explains how to write those boundaries, bilingual masters, offline behavior, migration reconciliation, ERP/MES interfaces and acceptance evidence into an RFP before comparing products.

Why production management needs renewed attention in Vietnam

Vietnam’s National Statistics Office (NSO) reported that the Index of Industrial Production in July 2026 increased 1.2% month on month and 14.5% year on year. The first seven months increased 11.4% year on year, all 34 localities recorded growth, and employment in industrial enterprises as of 1 July increased 1.0% month on month and 3.1% year on year. In a separate first-half and second-quarter report, the NSO said the manufacturing inventory index as of 30 June was up 5.3% month on month and 13.3% year on year, while 36.3% of surveyed enterprises assessed second-quarter conditions as better than in the first quarter.

These official figures describe the operating environment. They do not prove that a production system caused industrial or inventory growth. They do show why changing volume, staffing and inventory make consistent planning, capacity, WIP, shortage and quality-hold data important. A factory that worked through spreadsheets and verbal coordination may spend more time establishing which number is authoritative as sites, products, subcontractors and customer audits increase.

The objective should therefore go beyond replacing paper with tablets. A sound system defines who confirms each event, when it becomes final, which application is the system of record, and what evidence proves completion without stopping local operations.

Define the decision scope before comparing products

Do not describe the scope merely as “the whole factory.” Define an executive decision and a process start and end: customer order to released production order, material receipt to lot consumption, operation reporting to ERP inventory and cost posting, or nonconformance detection to quarantine, disposition and release.

For each flow, document:

• who creates, freezes, changes and releases the plan;
• whether ERP, MES, production management, WMS, QMS or equipment systems own each record;
• who owns items, BOMs, routings, equipment, workers, lots and inspection specifications;
• which records support law, contract or customer requirements;
• what headquarters standardizes and what the Vietnam factory extends;
• what may continue during an outage and how recovery is reconciled; and
• whether completion is evidenced by a screen, log, report or reconciliation file.

A scope matrix should include trigger, completion criterion, exclusion, owner, dependent system and acceptance evidence. “Inventory management” is too broad. “Put accepted material into a location, separate inspection hold from available stock, and reconcile the resulting balance to ERP daily” can be proposed, priced and tested.

Boundary architecture for a Vietnam production management system

Avoid the false choice between total headquarters standardization and total local autonomy. For each data object, assign rights to create, approve, distribute, use, correct, retire and retain it.

Local electronic records and statutory interfaces

Vietnam’s Decree 254/2026/ND-CP was issued on 30 June 2026 and took effect on 1 July 2026. It concerns electronic invoices and electronic documents. Where shipment, quantity, price reference, business-partner, return or scrap data from production management feeds accounting and tax processes, define when those values become authoritative and where correction or cancellation is controlled.

Do not infer universal scope, timing, retention, signature or correction duties from a project article. Qualified Vietnamese tax and legal specialists should review the current official text and operating guidance. The system RFP should identify the data fields, owner, interface timing, retries, corrections, reconciliation and evidence at the statutory-system boundary. Clear responsibility makes a future regulatory change traceable to affected interfaces.

Treat personal data as more than a work-report field

Vietnam’s Personal Data Protection Law 91/2025/QH15 has been effective since 1 January 2026. Production systems may process employee names, IDs, terminal identifiers, qualifications, attendance or work results, images, video, biometrics or location data. Collection should be tied to an explicit purpose and need, with defined roles, access, retention, audit, processors and possible cross-border or headquarters access.

Replace a generic “privacy compliant” requirement with a personal-data inventory covering purpose, data subject, source, storage location, user groups, disclosure, cross-border possibility, retention, deletion, incident evidence and access review. Vietnamese privacy and legal specialists must determine the applicable obligations against the latest official materials.

Separate quality traceability from shared KPI vocabulary

Decree 37/2026/ND-CP was issued and took effect on 23 January 2026 and relates to product quality and traceability. Product scope, obligations and record granularity should not be asserted without reviewing the source, ministry practice, customer requirements and certification context with specialists.

ISA-95, by contrast, is a reference for enterprise-control integration and interfaces between enterprise/logistics and manufacturing-control layers. ISO 22400-1 provides industry-neutral concepts and terminology for manufacturing operations management KPIs and was confirmed in 2025. Neither is Vietnamese regulation. Keeping legal and customer evidence separate from management KPI vocabulary prevents a regulatory change from unnecessarily breaking the entire corporate KPI model.

Bilingual master data is an operating control

Vietnam factory digitalization commonly mixes Vietnamese, English and Japanese. Adding another description column is not sufficient. Abbreviations, legacy names, field-length limits, synonyms, pronunciation and printed labels can diverge. Keep identifiers stable and separate display name, local name, search aliases, specification, unit, tax or accounting classification and quality classification.

An item record may require a headquarters item code, local purchasing code, customer code, Vietnamese and English names, unit and conversion, lot-control class, shelf life, inspection class, substitute relationships, effective period and approval state. A routing should link a standard operation code to local machines, teams and skills while separating user-facing wording from system identifiers.

The change process must cover request, translation, engineering review, quality review, local approval, headquarters distribution, effective date and retirement of the old version. Define emergency temporary codes, behavior when translation is pending, conflict priority and the ability to reproduce historical transactions with the old master.

Useful controls include use of unapproved or retired records, duplicate candidates, unit mismatch, missing translation, use before the effective date, and aging of ERP–MES discrepancies. These measures should reveal process congestion, not become simplistic penalties.

Model lot and quality traceability as transformation relationships

The GS1 Global Traceability Standard covers identification at class, batch/lot and instance levels and links inputs and outputs through transformations. A field that accepts a lot number is not enough. The system should show which material lots were consumed by an order and how splitting, mixing, rework, subcontracting, scrap, return and intermediate-to-finished conversion changed genealogy.

The RFP should specify use cases for identification level, label issue and reprint, scanning, consumption confirmation, quantity variance, split and merge, substitute input, rework, sample removal, inspection, hold, quarantine, concession and release. Test both backward and forward traces and define range, response, missing-data handling, authorization and export format.

Quality decisions should link specification revision, method, instrument, calibration state, sample, reading, assessor, time, retest and deviation approval. Never overwrite a corrected result; retain original value, corrected value, reason, approval and time. Reconcile physical quarantine against system status.

Design offline and outage behavior as explicit states

Connectivity varies by industrial estate, building, wireless conditions and terminal placement. “The network is normally available” is not an acceptance criterion. Model ONLINE, DEGRADED, LOCAL QUEUE, SYNCING, VALIDATE, COMMITTED, CONFLICT REVIEW and RECONCILED states.

Classify offline permissions by risk. Work start, quantity reporting, inspection or equipment-stop capture may continue under defined controls. A terminal with an obsolete master might finish safely active work but be prevented from starting a new order. Shipment release, critical approval or master change may require connectivity.

Every event should carry a terminal-generated unique ID, plant, terminal, user, business time, capture time, master version and prior state. Use idempotency keys so retries cannot duplicate production. Test reversed order, simultaneous changes to a lot, terminal clock skew, long disconnection, queue overflow and uncertain timeout outcomes.

Recovery reconciliation should count sent, received, deduplicated, held, conflicted, rejected and unresolved records. Automatic last-write-wins can erase a valid shop-floor record. Route conflicts that cannot be safely resolved by rule to an owned queue, show the evidence and require an accountable decision.

Example outage acceptance tests

1. Disconnect after work starts, then capture several production and inspection events.
2. Resend the same event and verify that it is not posted twice.
3. Change the same order from another terminal and confirm conflict detection on recovery.
4. Revise a master and verify allowed and prohibited actions on an old-version device.
5. Skew a terminal clock and confirm that business sequence is preserved.
6. Restore the server after a response timeout and reconcile the uncertain transaction.
7. Exceed queue capacity and verify warning, safe stop and recoverability.

Specify ERP, MES and equipment integration as data contracts

In overseas factory production management, ERP often owns orders, purchasing, inventory and accounting; MES owns dispatch and execution; equipment systems own states and measurements. Actual responsibility varies. ISA-95 helps organize layers, but product labels do not determine ownership.

For every interface, document source, target, business event, fields, units, codes, timestamps, frequency, order, retry, duplicate handling, cancellation, correction, error ownership, monitoring, retention and security. An API syntax without business meaning and failure operations is incomplete.

Monitoring must prove business completion, not only an HTTP success. Link the source event ID to the target document number and reconcile generated, sent, received, committed, cancelled and unresolved records daily. Protect manual reprocessing with authorization and a reason.

Define whether timestamps are stored and displayed in ICT, UTC or headquarters time. Separate measurement, receipt and processing timestamps so a network delay is not confused with manufacturing sequence.

Do not accept data migration on record counts alone

Freeze scope and a cutoff date for legacy applications, spreadsheets and paper records. Decide which masters, open orders, inventory, lots, quality holds, equipment, worker qualifications and history move into production and which remain in a controlled archive.

A migration rulebook should list source field, target field, transformation, default, code mapping, missing-data treatment, exclusion reason and approver. Version the conversion script, input, run log, errors and approved mappings so the result can be reproduced.

Reconcile at several levels:

• counts: extracted, transformed, loaded, rejected, duplicate and excluded totals;
• quantity and value: inventory, WIP, remaining order, movement and valuation totals;
• relationships: BOM hierarchy, lot genealogy, order-to-result and inspection-to-lot references;
• states: a held lot must not become available and a completed order must not reopen;
• samples: high-value, aged, reworked, split/mixed and multilingual records; and
• business outcome: execute representative transactions through reports and ERP results.

The cutover runbook needs timestamped steps for legacy stop, final delta extraction, load, reconciliation, approval, start and monitoring. Define abort criteria and the rollback decision owner. Rollback must also explain how cutover transactions are reversed and duplicates prevented.

RFP deliverables for Vietnam system development

A feature checklist lets vendors answer “supported” under different assumptions. Make proposals comparable by requesting these deliverables:

1. current and future process maps with a responsibility matrix;
2. system boundary diagram and system-of-record register;
3. headquarters/local master and bilingual governance design;
4. lot, quality and nonconformance states and genealogy model;
5. personal-data, role, audit and retention inventory;
6. ERP/MES/WMS/QMS/OT data contracts;
7. offline states, synchronization, conflicts and reconciliation;
8. migration mapping, cleansing, reconciliation and cutover plan;
9. positive, negative, recovery, performance and security tests;
10. monitoring, backup, recovery, incident process and SLA;
11. source, configuration, build, deployment, training and handover; and
12. a register of items requiring legal, tax, privacy and quality advice.

Require vendors to separate standard capability, configuration, customization, third-party products and customer work, with assumptions, exclusions, dependencies and change-price conditions. Demonstrate with representative customer data and failure scenarios, not only a polished sample.

Evaluate boundary understanding, local operation, language support, migration, integration, offline design, evidence, maintenance and handover as well as price. For deeper boundary and integration questions, see our manufacturing application development guide. For gated deployment and acceptance examples, see production management system implementation cases. Their principles are useful, but Vietnam requirements must be revalidated rather than copied from Thailand.

Raise acceptance evidence above “the screen worked”

Link requirement IDs to test IDs. Record precondition, data, action, expected and actual results, evidence, executor, reviewer, time, environment and software version. Combine screenshots with input events, database or API outcomes, ERP read-back, reconciliation and audit logs.

Negative tests should include outage, duplicate submission, reversed sequence, insufficient privilege, stale master, unknown code, unit mismatch, closed accounting period, missing measurement, equipment restart, label reprint, lot split/mix, quality hold and failed recovery.

At acceptance, list unresolved defects by severity with workaround, operating burden, residual risk, owner and due date. “Fix later” becomes a conditional acceptance only when tied to a change ID, target release, deadline and commercial responsibility.

Finally reconstruct one finished-product lot from material, order, equipment, operator, inspection, rework, completion, storage and shipment. Trace one material lot forward to affected finished lots and customer scope. Select one correction and show original value, reason, approval and downstream reflection.

Illustrative implementation sizing

The following is an illustration only and is not a price, schedule or outcome guarantee. Actual scope varies by plant, product, regulation, legacy environment, data quality, network, language and team.

Assume one plant, two product families, 8,000 items, 1,500 BOMs, 600 open orders, 25,000 inventory/lot lines, six ERP interfaces, ten equipment connections and 40 main scenarios. With one positive, two negative and one recovery test per scenario, there are 160 tests. Add 20 bilingual-display tests for Vietnamese and English, for 180 tests total.

A risk sample of 2% of 8,000 items is 160, 5% of 1,500 BOMs is 75 and 1% of 25,000 inventory/lot lines is 250: 485 sampled records, alongside full-count, quantity and relationship controls. These percentages are examples, not recommendations. High-value, quality-held, substituted, reworked or mixed-lot records may need complete or targeted review.

If five people can complete six evidenced tests each per day, 180 ÷ (5 × 6) = six working days. This excludes defect correction, retesting, data preparation, interpretation and production constraints. Plan decision time and retest buffer. Again, this is an illustration and not a price, schedule or outcome guarantee.

Gated deployment decisions

Start with a priority flow that exposes value and risk, such as receipt-to-consumption or operation-result-to-ERP posting. Do not choose an unrealistically simple screen; include outage, quality hold, rework, bilingual use and ERP integration.

Gate 1: authorize design

Confirm boundaries, systems of record, owners, lot scope, personal data, specialist-review items and current baseline measures. Do not push unresolved business decisions into vendor coding.

Gate 2: authorize pilot

Confirm the bilingual master, trial migration, interfaces, offline behavior, roles, audit and negative tests, plus training and incident contacts. Assess how remaining defects affect safety, statutory processing and operations.

Gate 3: scale, correct or stop

Review discrepancies, queue age, incorrect automatic commitments, quality-hold violations, duplicate postings, evidence and shop-floor workload—not just a headline KPI. Success means transactions finish correctly and exceptions are recoverable.

Common mistakes

1. Translating a Japanese screen while leaving local legal and quality responsibilities outside the design.
2. Assigning everything to ERP or MES based on product category instead of event ownership.
3. Loading masters once but not accepting the recurring translation, approval and retirement process.
4. Demonstrating only online positive cases and discovering duplicate results after an outage.
5. Reconciling migration counts while missing broken relationships, reversed states and unit errors.
6. Outsourcing legal interpretation to the software vendor instead of naming specialist decisions.
7. Accepting by impression without linking requirements, tests, evidence and defects.
8. Standardizing a KPI formula but not its denominator, time basis, exclusions and recalculation.

Pre-issue RFP checklist

• Process triggers, completions and exclusions are explicit.
• Local statutory, contractual, customer and headquarters-management data are classified.
• Legal, tax, privacy and quality specialist questions are registered.
• Headquarters masters and local extensions have owners, effective dates and translations.
• Split, mix, rework, outsourcing, scrap and return genealogy is testable.
• ERP/MES/WMS/QMS/OT systems of record and read/write responsibilities are agreed.
• Offline permissions, synchronization, conflict, reconciliation and overflow are tested.
• Migration has count, quantity, relationship, state and sample reconciliation.
• Negative, recovery, duplicate, sequence and authorization tests are included.
• Evidence, source, configuration, operation, training and handover are deliverables.
• Standard, configuration, custom work, customer work and exclusions are separated.
• Named owners decide scale, correction or stop at each gate.

Summary

A Vietnam production management system succeeds by deliberately separating and connecting local electronic records, personal data and lot/quality evidence with headquarters masters and KPI governance—not by faithfully translating a Japanese application. Put the boundary diagram, bilingual masters, transformation genealogy, outage states, ERP/MES data contracts, migration reconciliation, negative and recovery tests, and acceptance evidence into the RFP. Applicable legal duties must always be confirmed from current official materials by qualified Vietnamese legal, tax, privacy and quality specialists.

TOMAS TECH can help map a Vietnam factory’s current process and turn system boundaries, masters, interfaces, migration and acceptance conditions into an RFP before a product is selected. If you are still defining scope or budget, you can contact us for an initial discussion without committing to a platform.

FAQ

Should Vietnam system development use a local or Japanese vendor?

Company origin alone is not decisive. Compare local legal and language understanding, headquarters ERP and quality integration, migration, offline behavior, acceptance evidence and handover against the same scenarios. A joint local delivery and headquarters architecture team can work, but multi-vendor responsibility must be explicit.

Where should Vietnam factory digitalization start?

Choose a flow tied to a clear decision and connected to ERP or quality, with representative exceptions. Receipt-to-consumption, order-to-ERP result, or nonconformance-to-release are candidates. A simple isolated screen will not expose deployment risks.

Can overseas factory production management KPIs be fully standardized?

Comparability improves when denominator, time basis, planned stops, rework, missing data, recalculation and cutoff are standardized as well as the formula. Keep common vocabulary and local source events separate so legitimate process differences remain explainable.

What are the cost and duration of a Vietnam production management system?

They depend on plants, processes, ERP, equipment, data, legal and customer requirements, bilingual scope, offline behavior and history migration. Define boundaries and scenarios, then separate standard, configuration, customization, migration and operation. Every calculation in this article is illustrative and not a price, schedule or outcome guarantee.

Does supporting e-invoices and personal data guarantee compliance?

No. A system can implement controls and preserve evidence, but the organization and its specialists decide applicable law, purpose, roles, retention, transfers and tax treatment. Review current official texts including Decree 254/2026, Law 91/2025 and Decree 37/2026 with Vietnamese specialists.

Should every operation continue during a network outage?

No. Low-risk, uniquely reconcilable reporting may continue, while shipment release, critical approval or master changes may require connectivity. Define risk, required master version, duplicate protection, conflict resolution and recovery evidence per operation.

Primary and official sources

• Vietnam NSO, July and seven months of 2026: https://www.nso.gov.vn/bai-top/2026/08/bao-cao-tinh-hinh-kinh-te-xa-hoi-thang-bay-va-7-thang-nam-2026/
• Vietnam NSO, Q2 and H1 2026: https://www.nso.gov.vn/en/data-and-statistics/2026/08/report-socio-economic-performance-in-second-quarter-and-the-first-half-of-2026/
• Decree 254/2026/ND-CP: https://vanban.chinhphu.vn/?classid=1&docid=218689&orggroupid=2&pageid=27160
• Government summary/full text of Decree 254/2026: https://xaydungchinhsach.chinhphu.vn/toan-van-nghi-dinh-so-254-2026-nd-cp-ve-hoa-don-dien-tu-chung-tu-dien-tu-119260713164251972.htm
• Personal Data Protection Law 91/2025/QH15: https://vanban.chinhphu.vn/?classid=1&docid=214590&pageid=27160&typegroupid=3
• Decree 37/2026/ND-CP: https://vanban.chinhphu.vn/?classid=1&docid=216764&orggroupid=2&pageid=27160
• ISA-95: https://www.isa.org/standards-and-publications/isa-standards/isa-95-standard
• ISO 22400-1: https://www.iso.org/standard/56847.html
• GS1 Global Traceability Standard: https://www.gs1.org/standards/gs1-global-traceability-standard/current-standard
• Vietnam MPI manufacturing digital-transformation roadmap: https://www.mpi.gov.vn/portal/Pages/2023-6-17/Chuyen-doi-so-cho-doanh-nghiep-san-xuat-Lo-trinh-c4bje4f.aspx