An i-Reporter implementation in Thailand cannot be approved on a feature comparison alone. A factory needs to prove usability in 30 days, build TCO from an official Thailand quotation, and agree on RFP, FAT and SAT acceptance criteria before rollout. This guide shows how management, plant operations, IT, quality and procurement can make the same Go/No-Go decision, starting with digitising daily production reports.
Start an i-Reporter implementation by defining the loss to remove
If the goal of a digital form project is merely “eliminate paper,” the factory may replace paper with tablets while retaining re-entry, approval delays, Excel consolidation and archive searches. The first decision should be which minutes, defects and risks the target process must remove.
Before the PoC, measure at least:
- time to complete one form and correct it later;
- time from completion to supervisor, quality and management approval;
- time spent re-entering paper data into Excel, ERP, MES or a quality database;
- counts of blanks, wrong digits, transcription errors, missed approvals and lost forms;
- time to find an old record and answer an audit or customer inquiry; and
- downtime caused by lost connectivity, insufficient devices or shift changes.
Paper volume is useful but should not dominate ROI. In many factories, the larger benefit comes from shortening the time until information becomes usable, an abnormal condition is acted upon, or evidence is retrieved.
Put production-report digitisation KPIs on one page
Too many KPIs obscure the decision. Select one or two each from operations, lead time, quality and IT. Record the baseline, target, measurement method and data owner.
| View | Baseline example | Example 30-day criterion | Measurement |
|---|---|---|---|
| Work | 18 minutes/form for entry and re-entry | at least 30% shorter | time the same paper and digital process |
| Lead time | approval on the following day | at least 90% within the same shift | completion and approval timestamps |
| Quality | 12 defects/100 forms | at least 50% fewer | classify return reasons |
| Search | 25 minutes to find a record | within 3 minutes | search for a specified lot |
| Availability | work stops offline | complete all agreed scenarios | disconnect and recovery test |
These are decision examples, not product guarantees. Agree targets that match your losses and investment case.
What is i-Reporter, and what do its published numbers mean?
i-Reporter is a digital field-form system designed to preserve familiar form layouts while allowing input from devices including iPad, iPhone and Windows terminals. Its official function page describes offline use, more than 30 input aids, numeric threshold checks, photographs, signatures, automatic calculation, mandatory-field checks and numbering. The official site also describes CSV, Excel and PDF output, Web API, ConMas Gateway, ConMas IoT, i-Repo Link, and links to systems including Oracle and PostgreSQL.
As checked on 30 August 2026, the official site states more than 4,500 customer companies and more than 220,000 users. It also displays a 46.5% market share. The cited basis is Fuji Chimera Research Institute’s 2026 report and specifically the 2024 vendor share by volume for the Japanese “field form paperless solution” category. It is not Thai market share, global share, customer satisfaction or an implementation success rate.
The figures help assess product maturity. They do not establish fit for your Thai factory. Language, shifts, connectivity, approval rights, device management and existing-system integration must be proven in the PoC.
When an i-Reporter implementation may or may not fit a Thai factory
Cases with a potentially strong fit
- The plant wants a phased migration while retaining familiar Excel or paper layouts.
- The same data is entered several times into paper, Excel and ERP.
- Numeric ranges, required fields, choices and calculations can improve data quality.
- Photos, signatures, timestamps and operator identity must stay with the record.
- Daily reports, inspection, quality and maintenance should share a common platform.
- CSV, API, database or equipment integration is part of the roadmap.
Cases requiring careful evaluation
- “Zero paper” is the only goal and no improvement KPI exists.
- The team assumes one product will also perform planning, inventory allocation and production scheduling.
- Every process will move at once without form and data standardisation.
- No one owns devices, charging, replacements, Wi-Fi or accounts.
- Thai wording, date and time formats, decimal notation and shop-floor terminology have not been tested.
- Integration scope, charges and incident responsibility are missing from the quotation.
A digital form platform is not automatically a replacement for MES or ERP. Treating it as the field-data entry and evidence layer clarifies scope and ownership. For the wider data-flow design, see Automating form data re-entry in Thailand.
i-Reporter price: separate Japanese public prices from the Thailand quotation
The following prices were displayed on the official Japanese price page on 30 August 2026. All are Japanese domestic reference prices, excluding tax.
| Plan | Minimum users | Official Japanese public price | Note |
|---|---|---|---|
| Cloud | 5 users | JPY 42,000/month or more | JPY 55,000 initial fee; support included |
| On-premises subscription | 5 users | JPY 37,500/month or more | support included; customer manages the server |
| Perpetual on-premises | 5 users | JPY 1,066,000 or more initially | maintenance JPY 159,900/year or more; first year required |
The official page explicitly says overseas sales prices differ. Do not convert these yen figures into Thai baht and present them as a Thai price, budget or estimate. For a Thai factory, request an official partner quotation based on the contracting entity, users, architecture, options, implementation support, taxes and payment terms.
Do not size accounts from the five-user price alone
The official page explains that one user is one account or login ID, and the same user can register multiple tablets and PCs. Size licensing from operational needs, not simply device count:
- concurrent operators and processes;
- supervisors, quality, maintenance, approvers and viewers;
- overlap at shift handover;
- personal-ID requirements for audit trails and security; and
- transfers, leavers, temporary staff and peak periods.
Shared IDs may weaken evidence of who entered or approved a record. Separate licence optimisation from governance and measure actual concurrency during the PoC.
TCO for an i-Reporter implementation: costs beyond the licence quote
Compare at least three years and separate initial, recurring, change and internal costs.
| TCO item | Initial | Recurring | Often-missed question |
|---|---|---|---|
| Software | yes | yes | added users, options, contract term |
| Implementation | yes | sometimes | requirements, form design, migration, PM |
| Devices | yes | yes | protection, charging, spares, replacement |
| Network | yes | yes | plant Wi-Fi, secure links, offline tests |
| Integration | yes | yes | API, Gateway, IoT, ERP/MES changes |
| Training | yes | yes | Thai materials, night shift, new starters |
| Operations | sometimes | yes | IDs, form changes, first-line support |
| Security | yes | yes | MDM, logs, vulnerabilities, audits |
| Change control | sometimes | yes | process, master-data and release changes |
Do not assign a zero value to internal effort. Include days spent by key users, IT, quality, procurement and finance. On the benefit side, include traceable savings from re-entry, consolidation, search, returns, approval delays, audit preparation and abnormal-condition response—not just paper.
A practical TCO formula
3-year TCO = initial licence and build + devices and infrastructure + 3 years of subscription/maintenance + integration and changes + training and internal operations
Separate measured benefits, assumptions and benefits not yet quantified. Unsupported revenue or quality claims make the business case less credible.
Reach an implementation decision with a 30-day PoC
A PoC is not a vendor demonstration. It uses your process data, devices, network and operators to test a small version of production acceptance. Start with two forms, one process and one shift.
Choose one high-volume, relatively simple production report with numbers, choices and required fields. Choose a second form containing the real difficulty: photographs, approval, calculation, offline work or integration. Moving every form at once turns the PoC into a form-building exercise. The same discipline is discussed in Small-start system implementation for Thai manufacturing.
Week 1: baseline and acceptance criteria
- inventory fields, calculations, approvals, retention and related systems;
- time entry, re-entry, review and search separately;
- decide where Thai, Japanese and English are required;
- classify personal, production, quality and audit data; and
- approve Go, Conditional Go and No-Go criteria before configuration.
Week 2: form build and desk FAT
- preserve a familiar layout while removing redundant fields;
- configure ranges, mandatory fields, choices, calculations, photos and approval;
- write tests for abnormal values, blanks, duplicates, access errors and disconnection;
- confirm field mapping, character encoding, time, units and keys for CSV or integration; and
- define form versioning and the change approver.
Week 3: shop-floor SAT and parallel operation
- test in the real shift, lighting, gloves, noise, device position and Wi-Fi;
- run paper and digital records in parallel for a controlled period;
- verify offline recovery, sync, duplicate prevention and missing-data handling;
- complete approval and return flows through supervisor and quality; and
- observe where Thai operators hesitate, then improve screen design rather than adding lectures.
Week 4: benefits and production decision
- compare before and after with identical KPI definitions;
- classify open issues as mandatory before go-live, later improvement or accepted risk;
- update the official quotation and three-year TCO;
- agree rollout order, training, support and migration; and
- obtain sign-off from plant, quality, IT, procurement and management.
| Decision | Condition | Action |
|---|---|---|
| Go | mandatory criteria met; no critical risk | deploy the process and expand in stages |
| Conditional Go | benefit proven; limited open items remain | proceed with owners, due dates and workarounds |
| No-Go | critical function, governance, adoption or TCO is unacceptable | redesign scope, process or product choice |
What to put in an RFP for a digital form system
An RFP is not merely a feature checklist. It creates a common basis for quotations and defines responsibility.
Process and form requirements
- factory, process, number of forms, monthly volume, shifts and users;
- input, formulas, thresholds, photos, signatures, approval, return and versioning;
- Thai/Japanese/English display, materials and support;
- offline actions, recovery, synchronisation and conflict rules; and
- retention, search, outputs and audit trail.
Technical and security requirements
- cloud/on-premises options and decision conditions;
- device OS, MDM, authentication, authorisation, ID lifecycle and logs;
- ERP, MES, quality, equipment and database integrations;
- backup, recovery, incident notification, maintenance windows and support; and
- data location, encryption, vulnerability management, certifications and subcontractors.
The official Cloud Service Level 2025.2 page describes inclusion within an ISMS scope based on ISO/IEC 27001:2022, third-party vulnerability assessment at least annually, staffed monitoring 24 hours a day, 365 days a year, and service on Azure in a Japanese region. Public information is not a substitute for your review. Check the current terms, SLA, data-processing conditions and Thai entity requirements in contractual documents.
Commercial requirements
- Thailand currency, taxes, withholding, payment terms and quote validity;
- separate lines for setup, recurring fees, options, implementation, integration and training;
- adding or reducing users, renewals, termination and upgrades;
- migration, defect correction, change requests, travel and remote-support rates; and
- deliverables, intellectual property, configuration return and exit migration.
Separate FAT and SAT acceptance
FAT confirms that design, configuration and integration meet requirements before production-site acceptance. SAT confirms that the solution works on the Thai factory’s real network, devices, shifts and operating model. “It worked in the vendor environment” is not equivalent to shop-floor adoption.
Core FAT tests
- normal, boundary, abnormal, blank, length and unit validation;
- calculations, rounding, dates, times and time zone;
- creation, approval, return, re-approval, versioning and segregation of duties;
- CSV/API/database mapping, duplicates, errors and retry; and
- audit logs, output, search, backup and recovery procedure.
Core SAT tests
- weak Wi-Fi zones, disconnection and recovery;
- tablet protection, glove use, camera, charging and replacement;
- Thai text, names, date format, decimals, units and local terms;
- concurrent use on day/night shifts and delegated approval; and
- incident contact, first-line diagnosis and vendor escalation.
Each test should retain ID, precondition, input, expected result, evidence, status, correction owner and due date. Set severity thresholds—for example, zero Critical issues and zero High issues without a workaround—according to your own safety and quality requirements.
Cloud or on-premises: do not decide on price alone
Cloud can start quickly with less server work, but requires review of connectivity, data location, contract and integration routes. On-premises may support internal control and local integration, while the customer owns server, backup, monitoring, patches and incident response.
| Criterion | Cloud questions | On-premises questions |
|---|---|---|
| Speed | connectivity and account readiness | procurement and build lead time |
| Ownership | provider scope versus customer duties | OS, DB, backup and monitoring |
| Integration | API routes and restrictions | internal DB access and controls |
| Availability | SLA, notifications, redundant links | redundancy, recovery targets, staff |
| Cost | fees, options and communications | licence, hardware and operations |
Use weighted evaluation of TCO, security, operating capability, integration and rollout speed. Japanese public prices alone cannot answer the choice.
Read official case studies for replication conditions
Published outcomes are useful, but they are not transferable guarantees.
| Official case | Published result | Condition to verify locally |
|---|---|---|
| Sekisui Seikei | daily-report preparation and management from 300 to 130 hours/month; 170 hours saved | current re-entry, consolidation, forms and extraction |
| Bingo Tsukemono | 182 hours saved/year; expanded to four departments in one year | cross-functional ownership and standardisation |
| Kyushu Yanagawa Seiki | about 190 lines; six hours/day of processing reduced to almost zero | kintone/kViewer architecture and sharing process |
| Mune Pharmaceutical | 50% less form entry, transcription errors almost zero, 75% shorter final checking | GMP, audit trail, Bluetooth capture, calculation and training |
These are company- and process-specific results from official i-Reporter sources. Do not use them as a universal reduction rate. Measure your baseline and repeat the comparison in the PoC.
Operating design for sustained use in Thailand
At minimum, assign:
- process owner for purpose, fields, approval and KPI;
- form administrator for configuration, testing, release and retirement;
- Thai-speaking key user for first-line help and improvement requests;
- IT owner for IDs, devices, network, integrations and incidents;
- quality/audit owner for records, retention, evidence and change control; and
- vendor manager for SLA, commercial matters and open issues.
Thai localisation is shop-floor design, not just translation
Validate abbreviations, equipment names, part numbers, units and defect categories used by operators. Short, consistent choices, input sequence, mandatory fields, normal ranges and photo examples usually reduce hesitation more effectively than long instructions. If managers need Japanese while operators need Thai, define how language versions share one controlled master.
Train scenarios—normal entry, abnormal condition, returned record, network loss and device replacement—across all shifts, and incorporate them into new-starter training.
Seven checks that prevent implementation failure
- Were baseline time and defects measured before the PoC?
- Is the Thailand price based on an official partner quotation, not converted yen?
- Are users sized by concurrency and personal-ID controls, not devices?
- Did SAT test disconnection, sync, duplicates and device failure?
- Are integration fields, error handling, retry and ownership defined?
- Are form change, account, training and support owners assigned?
- Is Go/Conditional Go/No-Go based on written acceptance criteria?
An open point does not always require stopping. Record its due date, owner, workaround and residual risk, then manage it as Conditional Go.
The one-page internal approval case
Provide management with:
- target process and baseline loss;
- 30-day KPI results and operator feedback;
- recommended cloud/on-premises architecture, users, devices and integrations;
- official quotation and three-year TCO;
- measured, assumed and unquantified benefits separated;
- FAT/SAT results and critical open issues;
- phased rollout, owners, training and support; and
- exact approval requested and stopping conditions.
This lets management, plant, quality, IT and procurement see what was proven and what remains uncertain.
FAQ: i-Reporter implementation, price and Thailand rollout
What is the i-Reporter price?
As checked on 30 August 2026, official Japanese domestic reference prices excluding tax are JPY 42,000/month or more for five cloud users plus JPY 55,000 initial fee; JPY 37,500/month or more for five on-premises subscription users; and JPY 1,066,000 or more initially plus JPY 159,900/year or more maintenance for perpetual on-premises. Overseas prices differ, so obtain a Thai quotation rather than converting yen.
Can i-Reporter be implemented in Thailand?
The official price page says overseas use is possible, but overseas sales prices differ. Validate language, network, devices, taxes, support and integrations through an RFP, official quotation and PoC.
Can we decide on production-report digitisation in 30 days?
A focused PoC can test two forms, one process and one shift through baseline, configuration, FAT, SAT and evaluation in 30 days. Company approval and complex integration may take longer; 30 days is a decision framework, not a guaranteed go-live duration.
Does a digital form system replace ERP or MES?
Not necessarily. It may act as the field-data capture and evidence layer while ERP or MES remains responsible for planning, inventory, cost or instruction. Define the system of record for each requirement in the RFP.
Should we choose cloud or on-premises?
Cloud favours speed and reduced server operations; on-premises may favour internal control and local integration. Compare TCO, security, connectivity, backup, support capability and integration—not price alone.
Can official case-study savings be used as our ROI?
They can inform hypotheses, not serve as your benefit. Results from Sekisui Seikei, Bingo Tsukemono, Kyushu Yanagawa Seiki and Mune Pharmaceutical are individual cases. Establish your own baseline and measure the PoC with the same definitions.
Conclusion: use 30 days to define the conditions for success
The key to an i-Reporter implementation is not the number of functions; it is quickly proving the conditions under which the system works in your Thai factory. Link a two-form, one-process, one-shift PoC to baseline KPIs, an official Thailand quotation, three-year TCO, RFP, FAT and SAT. Treat Japanese public pricing as a reference only and never convert it into a Thai price. Treat case-study figures as evidence for replication questions, not guarantees.
You can discuss form selection, 30-day acceptance criteria, RFP structure or quotation comparison before the requirements are complete. Contact TOMAS TECH with the target process and a sample of the current form.
References
- Official pricing, checked 30 August 2026: https://i-reporter.jp/price/
- Official site, installations, users, share and integrations: https://i-reporter.jp/
- Official case list: https://i-reporter.jp/interview/
- Sekisui Seikei: https://i-reporter.jp/interview/2447/
- Bingo Tsukemono: https://i-reporter.jp/interview/16076/
- Kyushu Yanagawa Seiki: https://i-reporter.jp/interview/15965/
- Mune Pharmaceutical: https://i-reporter.jp/interview/16332/
- Cloud Service Level: https://i-reporter.jp/cloud-service-level/
- Form input functions: https://i-reporter.jp/functions_cat/form-input/
- Basic operation guide: https://manuals.i-reporter.jp/start-guide/basicoperation-guide/introduction
- Official news: https://i-reporter.jp/news/
Note: prices and product figures reflect public information checked on 30 August 2026. Contract terms, prices, functions and service levels may change. Reconfirm them in current official documents and a formal partner quotation.
