From incoming supply to equipment
Compare energy at incoming supplies, substations, lines and areas. Identify imbalances while accounting for supply topology, data completeness and measurement error.
TECHNICAL METERING · INTERNATIONAL EXPERIENCE FOR KAZAKHSTAN
From measurements
to energy management.
An automated technical electricity metering system: consumption by workshop and facility, energy balances, loss analysis and data for management decisions.
BalancesLoad profilesCost allocation
01 / SYSTEM PURPOSE
Understand where and how energy is used
Process costs
Allocate consumption by cost centre, shift and product type. Calculate specific consumption metrics using production data.
Peak demand control
Analyse power curves, exceedances and unplanned consumption. Prepare load-shifting decisions that account for production processes and supply conditions.
Technical and commercial metering serve different purposes. Technical metering supports internal technical and management accounting. Commercial volumes and settlements require an appropriate commercial metering system and agreed rules. Shared devices and infrastructure may be used where the design permits. Commercial metering →
02 / END-TO-END ARCHITECTURE
Four stages from devices to validated data
The proposed architecture uses the AMI approach: advanced metering infrastructure. HES handles device communications; MDMS handles storage, quality and data preparation. These roles may be provided by separate systems or modules of one platform.
- 01MEASUREMENT · HARDWARE
Devices at the facility
Meters record energy, load profiles and events. Profile intervals, such as 15, 30 or 60 minutes, depend on the task and device capabilities. Measurement intervals and transfer schedules are set separately.
STEM-300KZ →MCS301 → - 02TRANSFER · CONNECTIVITY
Communication channel and local archive
Data arrives directly or through an acquisition unit or concentrator via RS-485, Ethernet, PLC, radio or cellular networks. Buffering and backfilling cover communication outages. Interfaces are verified for each device variant.
RTU-325KZ →RTU-327 → - 03ACQUISITION · HEAD-END SYSTEM
HES: collect and monitor
Scheduled polling, profile and event log retrieval, retries and device availability monitoring. For DLMS/COSEM, OBIS objects, profiles, access rights and security settings are agreed. Raw values and statuses are retained for processing.
- 04PROCESSING · METER DATA MANAGEMENT
MDMS: validate and prepare
Map data to metering points, units and time; perform VEE, aggregation, balance calculations and export preparation. Measured, estimated and edited values retain distinct statuses.
How VEE works →
Energy management and ERP
Validated profiles, balances and departmental consumption feed reports, BI and enterprise management systems.
Commercial metering and billing
Volumes approved for settlement go to the billing system, which applies contractual tariffs and calculates charges in tenge. MDMS prepares data; it does not replace billing.
03 / TRUST IN DATA
VEE: validation, estimation and editing
Validation
Check missing and duplicate intervals, time errors, threshold breaches and register/profile inconsistencies. Assess zero consumption or reverse flow in operating context, including on-site generation.
Estimation
Missing data is estimated using an agreed method based on history, a reference point or comparable periods. Estimates receive a separate status and are reviewed when actual data arrives.
Editing
An authorised employee reviews disputed intervals and records the reason for an edit. Original values, author, timestamp and version history are retained; subsequent exports use the accepted version.
For technical analytics, the customer approves the estimation method. Use of estimates in commercial settlement follows applicable rules and contracts. Automatic substitution alone does not make a value valid for settlement.
04 / INTERNATIONAL EXPERIENCE
Applying architectural and operating practices
HES + MDMS + integration
Siconia separates device communications from data management. The published Groupe E project in Switzerland includes HES, MDMS, SAP integration and SaaS delivery.
Groupe E project · 2022 ↗Multiple communication technologies
The US Otter Tail Power project combines RF Mesh IP and cellular communications, meter data management, analytics and SaaS. It illustrates channel selection for local conditions and whole-life system operation.
Otter Tail Power project · 2022 ↗These international projects illustrate approaches and do not imply Almaty Project partnerships with, or supply of, those platforms. Architecture and software for Kazakhstan are selected to meet facility requirements.
05 / INTEGRATION IN KAZAKHSTAN
Developing existing infrastructure
We start by surveying devices, communication channels and existing software. Compatible equipment is retained and missing capabilities are added in stages.
RS-485 / Ethernet
Area and workshop meters, acquisition units, LAN and server. We check line length and topology, galvanic isolation, backup power and archive backfill capability.
PLC / radio network
PLC uses power wiring; radio uses dedicated wireless infrastructure. Selection is validated in a pilot: interference, attenuation, topology and concentrator availability matter more than general technology rankings.
Cellular / NB-IoT
Direct or gateway connectivity where coverage is confirmed. Kazakhstan operators offer NB-IoT; site availability, modem, SIM, latency and tariff are checked separately. LTE-M is considered where operator support is confirmed.
IoT connectivity example in Kazakhstan ↗Devices and protocols
Point register, transformer ratios, energy directions, OBIS, profile intervals and a common time base. Compatibility is verified through exchange with the specific model and software version, not merely a protocol name.
Software and enterprise systems
AlphaCENTER is considered for metering tasks, Integral-325 — for resource metering and process analytics. HES, MDMS and VEE requirements are matched against selected module capabilities; a separate component is included where needed. Integration with 1C, ERP and BI uses agreed APIs or files.
Commercial metering and KEGOC
For wholesale market participants, metering systems connect under the System Operator’s technical conditions: design, approval, testing and commissioning. The module “AlphaCENTER Kazakhstan Wholesale Market” generates and imports data and event files; the File Transfer module handles delivery. Intervals, formats and deadlines follow current technical conditions. KEGOC connection stages ↗
Security and continuity
The design defines access controls, channel and key protection, logging, redundancy and recovery testing. Data storage and processing locations account for applicable Kazakhstan requirements, facility classification and customer policy.
06 / DEPLOYMENT OPTIONS
On site, in a data centre or hybrid
On-premises system
Acquisition, archiving and processing in the customer’s infrastructure. Suits autonomy and access-control requirements. Requires resources to maintain servers and backups.
Private cloud / data centre
Hosting and support at an agreed site, including in Kazakhstan. Contracts specify SLAs, data rights, archive export and service exit arrangements.
Hybrid system
Local collection and buffering combine with central analytics. During external outages, measurements remain in the designed archive and are transferred after connectivity returns.
07 / PROJECT ECONOMICS
Ownership cost and measurable outcomes
Compare solutions in tenge over the same operating horizon. SaaS and service contracts are procurement options; capital and operating expense treatment follows contract terms and accounting policy.
System delivery
- Survey, design and integration.
- Devices, acquisition units, cabinets, installation and commissioning.
- Server infrastructure and licences according to the procurement model.
System operation
- Connectivity, hosting, support and updates.
- Software subscription, where included in the offer.
- Metrological verification, maintenance, backup and recovery.
COST MODEL
TCO = implementation + operation over the selected period + planned replacements
Compare unit cost as TCO / metering points / years. Phased connections use actual point-years; investment calculations also account for discounting.Data quality
Share of actual intervals received on time, separate from estimates. Duration of data gaps and archive recovery time.
Operating costs
Reading-collection visits and staff time spent on reporting and disputed data before and after implementation.
Energy performance impact
Changes in imbalances, specific consumption and peak demand. Savings are adjusted for production output, operating mode and tariff.
Budget and targets follow the survey and pilot. European per-point costs and foreign cloud tariffs are not used as ready-made Kazakhstan prices. An imbalance or device event triggers investigation; it is not proof of theft.
08 / IMPLEMENTATION
From pilot area to a unified system
- SurveySupply topology, metering points, equipment, communications, requirements and baseline metrics.
- Technical specificationIntervals, delivery deadlines, VEE methods, ERP interfaces, security and acceptance criteria.
- PilotTest connectivity, profile completeness, balances, failures and archive recovery.
- ScalingPhased site connections, archive migration, integration and training.
- OperationMonitor metrics, provide support and updates, and validate economic outcomes.
Official sources and materials
Prepared on 18 October 2026. The Kazakhstan architecture is Almaty Project’s design approach; international cases support specific technical and service practices.