Thailand Factory Energy Monitoring RFP: FAT/SAT and PoC

Thailand factory energy monitoring should not be commissioned merely to add attractive dashboards. Its purpose is to connect the utility bill, incoming supply, major loads, solar PV, BESS, compressed air and water on one time base and within defensible measurement boundaries. This guide explains how a factory can procure an energy monitoring system through an RFP and accept it through FAT, SAT and a 90-day PoC.

Procure Thailand factory energy monitoring as an evidence system

A common failure is to start a quotation with counts of meters, gateways, cloud licenses and charts. Every device may communicate, yet the result is unusable when clocks drift, signs are reversed, CT ratios are unknown or missing samples are silently replaced by zero. The utility bill, demand peak, PV self-consumption, BESS operation and compressed-air improvement then tell incompatible stories.

The procurement outcome should answer five practical questions:

• Can the utility bill and factory incoming measurement be reconciled after period, unit, multiplier and tariff window are aligned?
• Which load, production event and PV/BESS state coincided with a 15-minute demand peak?
• Can the gap between the incoming meter and major-load total be explained as unmetered load, losses, clock mismatch, meter uncertainty or bad data?
• Can changes in electricity, air and water be compared after production volume, product mix, operating hours and weather are considered?
• Can every KPI be traced back to a field tag, setting, calibration or verification record?

The RFP therefore needs more than “monitoring screens.” Require a measurement-boundary diagram, meter register, tag dictionary, time architecture, calculation specification, data-quality rules, tests, evidence and an operating-responsibility matrix.

Separate this RFP guide from the general and cost guides

Readers who first need the overall concept should begin with the factory energy-monitoring system guide. Readers comparing budget layers and rollout steps should use the energy-monitoring cost and implementation guide. This article starts at the next procurement stage: what a Thailand factory energy monitoring RFP must specify, how bids should be compared, and what FAT, SAT and 90-day PoC evidence is required for acceptance.

How to use Thailand’s 2026 tariff information safely

Tariffs matter, but copying an old rate table into a proposal and labelling it current creates more risk than value. Confirm from the bill and contract whether the site is served by PEA or MEA, the customer type, supply voltage, applicable schedule, TOU arrangement and power-factor conditions. PEA maintains an official tariff landing page. MEA’s Type 4 page defines the maximum 15-minute integrated demand in the applicable On-Peak and Partial-Peak periods under Type 4.1 TOD, while Type 4.2 TOU has a separate time schedule and monthly-demand description. Do not generalize one definition across Type 4; confirm the site’s bill, contract and current schedule. Rate figures on that page also have specific effective dates, so this article does not present them as universal 2026 rates.

The Thailand ERC official Ft table lists the retail Ft for September–December 2026 as 16.23 satang/kWh. That is a period-specific verified value, not a permanent rate. An RFP should require tariff version, effective date, source URL and approval owner instead of hard-coding a price. When Utility Green Tariff is relevant, check the ERC UGT page at decision time and keep contractual environmental attributes distinct from physical power-flow measurements.

Separate tariff calculations from equipment control

An EMS has two time layers. Seconds-to-minutes data supports diagnosis of compressor loading, process events and BESS response. Fixed 15-minute, time-band and monthly aggregates support demand and bill review. A billing-reproduction calculation should not be the same software object as real-time control logic. Raw data should remain available for recalculation under a revised tariff version without changing controller settings.

Define measurement boundaries before selecting hardware

Boundary clarity matters more than sensor count. Overlay the single-line diagram, piping diagram, plant layout, utility bills and existing meter list. Define at least these layers.

Give every boundary a unique field identity. “Main” and “Line 1” are inadequate without board, circuit, equipment and flow direction. When a retrofit changes a circuit, do not overwrite the historical tag. Manage effective start/end dates and revisions so historical data retains its meaning while the register follows the as-built plant.

Mandatory meter-register fields

Attach a register template to the RFP and make completeness an acceptance item.

“The value is visible” is not acceptance. Primary/secondary wiring, CT orientation, phase order, multipliers, units and signs must match the register. The value must also be plausible against a known operating condition or an appropriate reference instrument.

Align 15-minute demand monitoring with the billing boundary

The label “15-minute average” is insufficient. State whether the calculation uses fixed blocks or a rolling window; whether blocks begin at 00, 15, 30 and 45 minutes; how the clock is aligned with the utility meter; and which calendar version determines tariff periods. A rolling 15-minute value can be useful for early warning but may not reproduce billing demand.

A fixed-interval concept can be written as:

Interval demand [kW] = interval energy [kWh] × 60 ÷ interval minutes

For a 15-minute interval, interval minutes equals 15. This dimensional example does not replace the site’s billing rules. If cumulative counters are differenced, detect reset, rollover, out-of-order delivery and gaps. If sampled kW is averaged, specify how irregular sampling and missing values are weighted.

Design demand management as forecast, confirmation and action

Demand management needs an operating playbook, not one red alarm.

1. Forecast block-end demand from elapsed time, accumulated energy and time remaining.
2. Overlay scheduled starts of chillers, compressors, ovens, chargers and production lots.
3. Validate PV output and usable BESS power/energy with quality flags.
4. Define who may adjust which load, for how long and under what safety/quality conditions.
5. Record the action and its effects on production, safety, quality and energy.

Automatic shedding needs a separate engineering review of process safety, product quality, interlocks, authority and fail-safe behavior. A monitoring KPI must never justify unsafe interruption of a critical load.

Reconcile incoming power, major loads, PV and BESS

Power visualization is an accounting model, not a pie chart. Adopt one sign convention and field-test every point. A conceptual interval balance is:

Grid import + PV generation + BESS discharge = plant load + BESS charge + grid export + losses/unmetered difference

Do not collapse BESS charge and discharge into one unsigned tag. Decide whether the source of record is the PCS, BMS, revenue meter or point-of-connection meter; whether values are AC- or DC-side; and whether auxiliaries are included. Apply the same discipline to inverter totals and a PV AC meter. BESS safety monitoring is a separate layer from energy performance; see Factory BESS fire-safety monitoring in Thailand.

Do not immediately label the residual as “loss.” It can combine boundary misalignment, wrong ratio, unmetered circuits, transformer losses, meter uncertainty and communication gaps. Code the known causes and observe how the residual changes as metering coverage improves. If voltage events and power quality are in scope, include the approach in Thailand factory voltage and power-quality monitoring.

Put utility monitoring on the same clock

When compressed air and water are isolated in separate clouds, their relationship with electricity and production is hard to prove. Put them on a common time architecture and join them by equipment ID, shift, product and machine state. Preserve each utility’s physical quantity and boundary; do not force every value into one unit.

Compressed air

Relate compressor electricity, supply flow, header pressure, quality/dew-point status and loaded/unloaded state. A possible indicator is kWh/Nm³, but comparisons are invalid unless the reference condition, meter compensation and inclusion of dryers and auxiliaries are defined. Non-production base flow can guide a leak survey, but purge and legitimate continuous demand must be excluded before calling the whole value leakage.

Water

Define incoming water, storage, process distribution, cooling-tower makeup, domestic use and discharge boundaries. For pulse inputs, test the pulse constant, debounce, reverse flow and totalizer persistence after restart. A water-balance residual can include storage-level change, timing, evaporation, discharge and unmetered use—not only leaks.

Production energy intensity

Simple energy ÷ production can hide product mix, yield, start-up, idle time and ambient conditions. ISO’s energy information identifies ISO 50006:2023 as guidance on energy performance indicators and energy baselines, while ISO 50002-1:2025 sets general requirements and guidance for conducting energy audits. Separate a management-level overall indicator from condition-specific process indicators. ISO 50001:2018 was reviewed and confirmed in 2024 and remains current as an energy-management-system reference; this article does not claim certification is mandatory.

Ten requirements for a factory EMS RFP

An RFP should define an acceptable result rather than a preferred brand.

1. Scope and boundaries: diagram site, building, board, equipment, PV, BESS, air and water in/out.
2. Data dictionary: define tag, meaning, unit, sign, multiplier, uncertainty information and quality flag.
3. Time architecture: define UTC storage, ICT display, synchronization, fixed 15-minute blocks and late data.
4. Acquisition: state protocol, scan interval, edge buffer, replay, bandwidth and loss-of-link behavior.
5. Calculations: version energy differences, demand, tariffs, intensity, PV/BESS and utility balances.
6. Data quality: retain missing, stale, out-of-range, manual and estimated states separately from values.
7. Security: require segmentation, least privilege, authentication, logs, patching and remote-access approval.
8. Operations: provide a RACI for alarms, register changes, calibration, backup and incident response.
9. Testing: agree FAT, SAT and PoC cases, inputs, expected results, evidence, approver and defect handling.
10. Handover: deliver as-built records, settings, calculations, licenses, training, restore procedure and support terms.

For each requirement, the bidder should mark standard, configurable, custom development, excluded or customer dependency. Maintain traceability from requirement ID to test case, evidence and open item. A polished demonstration is not a substitute.

FAT must test calculations and failure modes

FAT uses simulated or replayed data before field deployment to prove the meaning of the design.

FAT evidence is more than screenshots. Retain input data, expected value, actual output, software/configuration revision, executor, timestamp, nonconformance and retest result.

SAT proves field identity, ratio, sign and recovery

SAT must prove that a software tag is the intended physical point. Under the factory’s electrical-safety system, reconcile board identity, nameplate, CT/PT, flow direction, network address, gateway settings and tag. This article is not an instruction for live electrical work; qualified people and site procedures are required.

Use known equipment states or suitable portable references; reconcile compatible periods with the utility meter/bill; test PV/BESS signs, pulse inputs, communication loss, edge restart and server recovery. Agree project-specific balance tolerances. They depend on meter class, range, interval, losses and intended use, so no universal acceptance percentage is stated here.

Do not leave defects as “monitor in operation.” Record severity, containment, owner, due date and retest condition. When a major tag mapping or multiplier remains unknown, its KPI, tariff calculation and savings claim should remain unaccepted until correction.

A 90-day PoC is not a guaranteed savings percentage

A 90-day PoC asks whether the data supports decisions across meaningful production and utility variation. Ninety days may not represent every season, product or maintenance state. A fixed savings promise can ignore production/weather effects and encourage disruptive control.

Assess four layers:

• Data health: agreed availability of mandatory points, clock alignment, quality flags and meter-register completeness.
• Balance integrity: explain the bill/incomer, incomer/loads, PV/BESS, air and water residuals.
• Operational adoption: alarm ownership, response, review meetings, change control and training function in practice.
• Improvement evidence: document boundary, baseline, adjustment variables, exclusions and persistence.

EVO’s official site identifies IPMVP Core Concepts 2022 as the current core reference. Quoting “IPMVP” does not itself prove savings. Agree a Measurement & Verification Plan covering boundary, baseline, adjustments, reporting period and missing-data treatment before the intervention. Combine this with the Thailand factory energy-saving measures guide to structure opportunity screening.

Compare vendors by how they manage uncertainty

Normalize more than meter price and cloud subscription.

Thailand BOI’s current Smart and Sustainable Industry page is a relevant primary source when reviewing investment promotion, but eligible assets, timing, evidence and incentives must be confirmed per project with BOI and advisers. The page also states that investment promotion for solar-power installation projects under the alternative-energy efficiency measure has not been available since 1 July 2025. Neither solar installation nor monitoring automatically secures an incentive. For renewable contracting, read the Thailand factory renewable-energy procurement guide and separate contractual attributes from physical metering.

Make data quality and security acceptance items

Replacing a gap with zero destroys the distinction between equipment stop and communication failure. Store the quality state separately: good, missing, stale, out-of-range, estimated, manual and maintenance. Never delete the raw value when applying a correction; retain reason, method, executor, approval and revision.

OT data collection does not require unrestricted bidirectional access. Require read-only acquisition where practical, segmentation, a controlled relay, least privilege, individual accounts, secure secret handling, audit logs and case-by-case remote-access approval. Any write-back to control needs a separate risk review, authorization, test and rollback procedure.

“Daily backup” is not enough. List configuration, tag dictionary, calculations, dashboards, identities, certificates and history in scope, then demonstrate restoration in another environment. Before contract award, confirm the export format and recovery path if the vendor or cloud service becomes unavailable.

Attach an acceptance matrix to the contract

Connect every requirement ID to its boundary, test method, acceptance evidence and approver before award. Targets must be agreed for the equipment and use case; the following are categories, not universal numerical thresholds.

For conditional acceptance, identify the data allowed for use, containment, correction due date and retest owner. The factory must also provide bills, known operating states, production permissions, PV/BESS conditions, reference instruments and witnesses. If a machine cannot run on the planned day, pre-agree replay data and a later field retest.

Protect evidence through change control

Equipment moves, board modifications, CT replacement, address changes, tariff revisions and product changes begin after handover. Every change request should record affected tags, reason, old/new value, effective time, affected calculations, dashboards, alarms and baselines, test and approval. Never edit a production setting without history.

Monthly review should cover billing residuals, quality flags, clock drift, unused tags, manual corrections, ignored alarms and register/field differences. Activate a new tariff or Ft revision only after source, effective date and dual review are recorded; retain historical calculation under the historical revision. When a permanent production or equipment change requires a new baseline, preserve the old one and document why the new revision exists.

Implementation roadmap from survey to 90-day PoC

Final check before issuing the RFP

Have procurement, production, facility, energy, IT and safety owners review the boundary together. Confirm the current single-line and board names, bills and tariff history, existing meter ratios/access/verification, PV/BESS sign conventions, air/water storage and bypasses, the production-data source of record, OT access lead time, FAT data confidentiality, SAT operating windows and the owner of weekly PoC actions. Do not invent an answer to an unknown. Mark it unverified and ask bidders to separate survey work, assumptions, unit rates and decision deadlines. This makes a superficially cheap exclusion visible.

1. Pre-RFP survey

Collect bills, contract, single-line and piping diagrams, asset registers, existing BMS/SCADA/PLC, network information, PV and BESS documents. Walk down the site, record as-built differences and separate decision-critical points from future extensions.

2. RFP and baseline freeze

Agree boundaries, requirement IDs, dictionary, tests, responsibilities and exclusions. Freeze baseline revision and its change-approval process before PoC start. Put unresolved assumptions in a log with an owner and due date.

3. Design and FAT

Design network, time, tags, calculations, dashboards, reports, alarms and authorization. Test normal, abnormal and boundary conditions. Use open nonconformities in the field-deployment go/no-go decision.

4. Installation and SAT

Install under a safe work plan. Prove identity, ratios, signs, time, communication, restart and bill reconciliation. Update the as-built register and train operators until they can distinguish process events from data faults.

5. 90-day PoC and handover

Review data quality, balances, alarms and hypotheses weekly. At close, decide go, revise or stop using not only savings but also residuals, open work, additional-meter priorities, operating workload and expansion cost.

FAQ: energy monitoring systems for Thailand factories

Is 15-minute data enough for Thailand factory energy monitoring?

It is central to billing-demand reconciliation, but root-cause analysis may need shorter intervals. Preserve fast/raw data where justified, fixed 15-minute aggregates and monthly billing layers. Do not increase every point’s rate; prioritize incoming supply, variable loads, PV/BESS and compressors.

What percentage tolerance should demand monitoring meet?

There is no universal value. A rational band depends on period alignment, meter class, CT/PT, transformer loss, unmetered load and data quality. Agree tolerances by use case and the investigation process when exceeded.

Can a factory EMS PoC guarantee energy savings?

No. Monitoring supports discovery and verification; installation alone does not guarantee a fixed reduction. Evaluate operational action, equipment change, production conditions and baseline adjustment under an M&V plan.

Can solar PV and BESS use one meter?

A connection-point meter may not separate PV generation, self-consumption, BESS charge/discharge and grid exchange. Define AC/DC boundary, PCS/BMS, auxiliaries and source-of-record meters, then ensure the balance can close.

May utility monitoring be installed separately from electricity?

Phased deployment is possible, but specify a common clock, equipment IDs, quality flags and integration interface from the start. Separate screens alone make later correlation of compressor power, air flow and production difficult.

May current Thai electricity prices be hard-coded?

Avoid it. Tariffs, Ft, time bands and contract/tax conditions have effective periods. Version the source, date and approval so past data can be recalculated with the applicable rule. ERC lists 16.23 satang/kWh for September–December 2026 Ft, but that does not establish the next period.

Conclusion: accept evidence, not dashboards

For Thailand factory energy monitoring, prioritize one time base, defensible boundaries, quality-tagged raw data, reproducible calculations and FAT/SAT/PoC evidence. When the bill, incomer, major loads, PV, BESS, compressed air and water connect, teams can debate demand, intensity and improvements with shared facts. When they do not, more charts do not reduce uncertainty.

TOMAS TECH can help a Thailand factory review existing meters and OT networks and structure the boundary, RFP, FAT/SAT and 90-day PoC before a product is selected. If you need to determine what must be measured to connect the bill with operational improvement, contact us at the planning stage.

Primary references

• PEA tariff information
• Thailand ERC Ft table
• Thailand ERC Utility Green Tariff
• MEA Type 4 Large General Service
• ISO 50001:2018
• ISO energy standards overview (ISO 50006:2023 and ISO 50002-1:2025)
• EVO IPMVP
• Thailand BOI Smart and Sustainable Industry measure