Customer Success Story - Permskaya Gres
Company Size
1,000+
Region
- Europe
Country
- Russia
Product
- GENESIS32™ Enterprise
- WebHMI™
- DataWorX™32
Tech Stack
- OPC
- Windows Server 2000
- Windows XP
- INFORMIX
- Microsoft SQL Server
Implementation Scale
- Enterprise-wide Deployment
Impact Metrics
- Cost Savings
- Productivity Improvements
Technology Category
- Application Infrastructure & Middleware - Data Exchange & Integration
- Application Infrastructure & Middleware - Middleware, SDKs & Libraries
Applicable Industries
- Utilities
Applicable Functions
- Maintenance
- Quality Assurance
Use Cases
- Predictive Maintenance
- Remote Asset Management
Services
- System Integration
About The Customer
Permskaya Gres is a thermal electric power plant located in Dobryanka, Russia. The revised plant was built and put into operation in 1986, 1987 and 1990 with three 800-megawatt power units. The station burns gas for fuel. Since it went into operation, Permskaya Gres has produced 112,000 million kilowatts of electricity. At times, its annual output reaches 14,000 million kilowatthours. The station produces and delivers electricity to the federal (all-Russian) wholesale electric power market. The thermal energy it produces is delivered to consumers in the town of Dobryanka.
The Challenge
Permskaya Gres, a thermal electric power plant in Russia, was facing a challenge of synchronizing real-time OPC information from several different information systems. These systems worked independently, had different hardware and software platforms, and were placed far from each other. The goal of the project was to increase the control efficiency and capacity for all power stations, which they called the “Planned Capacity Trend functionality”. The main purpose of the application was to provide information from different power generating control systems and delivering the information in real time to remote users.
The Solution
Permskaya Gres deployed GENESIS32™ Enterprise, WebHMI™ and DataWorX™32 throughout the plant. The GENESIS32 Enterprise system is monitoring and controlling over 11,000 OPC tags. DataWorX™32 is aggregating the data from 3 different OPC servers and delivering the data in real time to the ICONICS TrendWorX™32 and AlarmWorX™32 modules of GENESIS32. WebHMI™ from ICONICS also plays a critical role in the application. There are several remote monitoring stations in buildings 500-700 meters apart and WebHMI is used to allow the remote secure access. The list of WebHMI users range from senior machine operators in the power generating units to shift supervisors, department chiefs and engineers performing research in the laboratories.
Operational Impact
Quantitative Benefit
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
Related Case Studies.
Case Study
IoT Solutions for Smart City | Internet of Things Case Study
There were several challenges faced: It is challenging to build an appliance that can withstand a wide range of voltage fluctuations from as low at 90v to as high as 320v. Since the device would be installed in remote locations, its resilience was of paramount importance. The device would have to deal with poor network coverage and have the ability to store and re-transmit data if networks were not available, which is often the case in rural India. The device could store up to 30 days of data.
Case Study
Automation of the Oguz-Gabala-Baku water pipeline, Azerbaijan
The Oguz-Gabala-Baku water pipeline project dates back to plans from the 1970’s. Baku’s growth was historically driven by the booming oil industry and required the import of drinking water from outside of the city. Before the construction of the pipeline, some 60 percent of the city’s households received water for only a few hours daily. After completion of the project, 75 percent of the two million Baku residents are now served around the clock with potable water, based on World Health Organization (WHO) standards. The 262-kilometer pipeline requires no pumping station, but uses the altitude differences between the Caucasian mountains and the capital to supply 432,000 m³/d to the Ceyranbatan water reservoir. To the people of Baku, the pipeline is “the most important project not only in 2010, but of the last 20 years.”
Case Study
GPRS Mobile Network for Smart Metering
Around the world, the electricity supply industry is turning to ‘smart’ meters to lower costs, reduce emissions and improve the management of customer supplies. Smart meters collect detailed consumption information and using this feedback consumers can better understand their energy usage which in turn enables them to modify their consumption to save money and help to cut carbon emissions. A smart meter can be defined in many ways, but generally includes an element of two-way communication between the household meter and the utility provider to efficiently collect detailed energy usage data. Some implementations include consumer feedback beyond the energy bill to include online web data, SMS text messages or an information display in consumers’ premises. Providing a cost-effective, reliable communications mechanism is one of the most challenging aspects of a smart meter implementation. In New Zealand, the utilities have embraced smart metering and designed cost effective ways for it to be implemented. The New Zealand government has encouraged such a move to smart metering by ensuring the energy legislation is consistent with the delivery of benefits to the consumer while allowing innovation in this area. On the ground, AMS is a leader in the deployment of smart metering and associated services. Several of New Zealand’s energy retailers were looking for smart metering services for their residential and small business customers which will eventually account for over 500,000 meters when the multi-year national deployment program is concluded. To respond to these requirements, AMS needed to put together a solution that included data communications between each meter and the central data collection point and the solution proposed by Vodafone satisfied that requirement.
Case Study
NB-IoT connected smart meters to improve gas metering in Shenzhen
Shenzhen Gas has a large fleet of existing gas meters, which are installed in a variety of hard to reach locations, such as indoors and underground, meaning that existing communications networks have struggled to maintain connectivity with all meters. The meter success rate is low, data transmissions are so far unstable and power consumption is too high. Against this background, Shenzhen Gas, China Telecom, Huawei, and Goldcard have jointly trialed NB-IoT gas meters to try and solve some of the challenges that the industry faces with today’s smart gas meters.
Case Study
OneWireless Enabled Performance Guarantee Test
Tata Power's power generation equipment OEMs (M/s BHEL) is required to provide all of the instrumentation and measurement devices for conducting performance guarantee and performance evaluation tests. M/s BHEL faced a number of specific challenges in conducting PG tests: employing high-accuracy digital communications for instrumentation, shortening setup and dismantling time, reducing hardware required, making portable instrument setup, avoiding temporary cabling work and the material waste costs
Case Study
British Gas Modernizes its Operations with Innovative Smart Metering Deployment
The UK government has mandated that smart meters are rolled out as standard across Great Britain by end of 2020, and this roll-out is estimated to create £14 billion in net benefits to the UK in consumer energy savings and lower energy generation demand, according to the Oxford Economics report, “The Value of Smart Metering to Great Britain.” While smart-metering systems have been deployed in many countries, the roll-out in Great Britain is unique because it is led by energy retailers, who have responsibility for the Electricity and Gas meters. The decision to have a retailer-led roll out was made by DECC (Department of Energy and Climate Change) to improve customer experience and drive consumer benefits. It has also led to some unique system-level requirements to support the unique local regulatory model.
