Contract-capacity overruns often go unnoticed until the bill arrives. Three short clips show how meters connected to CGate warn you before demand reaches contract capacity, show where the power goes, and keep the power records carbon accounting calls for.
Taipower determines overruns from the month’s highest 15-minute average demand and bills the excess at two to three times the basic rate. The three clips below show how each situation plays out with power monitoring in place. All values shown are illustrative.
You only find out from the monthly bill that demand went over last month.
If the meter provides a demand value, CGate reads it directly. When demand stays near the set threshold for the configured time, the CGate web page flags it and emails the person in charge.
The bill shows a single total, with no way to tell where the power went.
Each circuit is logged hourly, and the CGate web page makes it plain: at 2 a.m., with no one in the room, one circuit is still drawing power.
Someone digs out a year of bills and compiles them by hand, and even then they only have a plant-wide total.
A remote energy-management or carbon-accounting system can read each circuit’s power data straight from CGate and allocate it by production line.
More and more supply-chain customers ask their suppliers for power-use and emissions data. For most manufacturers, purchased electricity is a major emissions source.
Emissions from purchased electricity are usually calculated as monthly kWh multiplied by the grid emission factor. For a plant-wide figure, the power bill is enough.
If a customer wants the figure for one production line, you need hourly logs per circuit to allocate it. CGate logs every circuit, so power use can be split by line.
The figures come from hourly meter readings, and logging continues even when the network is down. A remote energy-management or carbon-accounting system can also read them straight from CGate over Modbus TCP or MQTT.
CGate supplies the power data. It doesn’t apply emission factors or produce the inventory report; that still follows your chosen standard or your verifier’s requirements.
Behind all three moments is one system: a multifunction meter on the main incomer and a meter on each branch circuit, daisy-chained over RS-485 to a CGate inside the panel. CGate logs every reading and provides a web interface and email alerts over the local network.
Reads the meters, logs continuously to its built-in database, and provides a web interface and email alerts
No. Billing is always based on Taipower’s meter. Meters you install yourself show where power is used across the plant and warn you early as demand approaches contract capacity.
CGate itself handles monitoring and notification. For automatic load shedding under set conditions, pair it with our RIO series, which switches loads through a relay module and is planned around your site.
If they have RS-485 and support Modbus, yes. They connect using their register maps, so there’s no need to replace them.
No. CGate keeps logging on site, and the records can still be exported once the network is back. If the switch room has no network cable, 4G is available as an option.
It can serve as a source of Scope 2 power data and be allocated by circuit to each production line. The inventory report itself still has to follow the standard you use or your verifier’s requirements.
Meter count, circuit layout, alarm conditions and notification methods (such as LINE) can all be tailored to your site. Tell us about your panels and power use, and our sales team will help you plan the setup.
