Piping systems are major investments for any company, organization, or municipality that requires them, but their costs aren’t limited to initial installation. In addition to the expenses involved in designing and building them, piping systems also come with a wide array of maintenance costs to ensure their efficient and ongoing operation. Optimizing these systems over their life cycles is key to maximizing both piping system performance and ROI.
How can engineering teams track their piping system performance? By calculating their “system power cost,” engineers can measure the energy required to operate and maintain the various components of a piping system. Using PIPE-FLO from Revalize’s System Power Cost feature, engineers can access the financial and equipment usage insights they need to optimize their fluid piping systems.
As a member of the ISO/ASME Pump system assessment 14414 standard, the PIPE-FLO team was tasked with developing a method for assessing a pumping system. The assessment considered the entire pumping system, from energy inputs to the work performed. Our primary goal was to determine the current energy consumption, identify ways to improve system efficiency, and present the results in a meaningful way to a diverse team of stakeholders, from technical to financial professionals.
PIPE-FLO simulates how the system operates, but the results are presented in a variety of engineering units, such as head, pressure, horsepower, kiloWatts, and capacity. In order to share the results in an easy-to-understand set of units, the engineers presented the amount of electricity used to power equipment motors each hour as standardized dollars per unit of time. This is otherwise known as the system power cost.
The figure above represents a system consisting of a supply tank, pump, heat exchanger, flow element, flow control valve, and destination tank. The drawing shows the calculated values for the installed instruments, specifically the level and pressures in the tanks, the pump suction and discharge pressures, the flow rate, and the corresponding position of the control valve.
This provides plant operators with the information needed to operate the system, but offers only limited insight on how efficiently the system is operating — and nothing about the operating cost.
PIPE-FLO fixes this by showing how the energy is used within the system to calculate costs, as shown in Figure 2 (below). The flow rate through the system is set to 400 gpm, based on the set point of control valve ST1-1-FCV1. The flow rate through the pump produced 204.7 feet head, with an efficiency of 51% based on the pump curve, and requires 43.79 horsepower into the motor shaft.
Via PIPE-FLO’s calculated results, you can see the energy supplied by the pump and observe the losses associated with the process and control elements. You can also see how much power is supplied to the pump to provide the required flow rate, along with pump efficiency. Notice the head loss across the heat exchanger and the head loss across the control valve needed to maintain the required flow rate. Finally, the calculations show the difference in static head that must be overcome for the system to work.
Looking at the results, only half of the power supplied to the pump is used to move the process fluid through the system. Approximately 40% of the power supplied by the pump is consumed by the control valve.
You might be left wondering: How much does your current system cost to operate, and what can be done to minimize the operating costs? PIPE-FLO v17.5 features a new System Power Cost capability designed to address those questions.
By entering the local cost of electrical power, and the length of time for system operation, PIPE-FLO calculates the cost to operate the pump element, and the operating cost of each item in the system. Figure 3 (below) shows the power cost for each item in our sample system. In this example, the power cost is $0.10 per kWhr (annualized), and the system is operating for 100% of the evaluation period.
With the dissipated power and cost values displayed, all stakeholders can access the financial insight into the system’s operation. Notice that the pump has an annual input power cost of $28,618. Of that, only 51% of the power is used to move the fluid through the system, highlighting the dissipated power, along with the dissipated power cost, for each item in the system.
Notice that the flow orifice ST-1-FE1 consumes 1.04 kW of power and costs $912 in annual operating costs. Furthermore, control valve ST1-1-FCV1 consumes 6.58 kW of power, with an annual operating cost of $5,766 per year, to limit the flow rate to 400 gpm.
With this financial insight, stakeholders can see how much it costs to operate the piping system, and how much power is consumed by the pump based on its efficiency.
Using the computational power of PIPE-FLO, engineers can insert a new and more efficient pump (possibly with a Variable Speed Drive) into the model to simulate system operation along with savings in operating cost. Then, document the values and savings using PIPE-FLO’s new System Cost Report. The tool allows users to create both pie charts and lists that feature pump input and output power, and the dissipated power cost for each item in the system. See Figure 4 (below) for more.
PIPE-FLO is the engineering standard for modeling and simulation calculations to manage your entire fluid system lifecycle. From design to digital twin simulations, our software is proven to save time and money.
Using PIPE-FLO’s System Power Cost feature provides your team with clear and actionable financial and sustainability insights on fluid piping systems — insights expressed in “dollars and cents,” which are measurements that resonate throughout an organization.
Cookie | Duration | Description |
---|---|---|
__hssc | 30 minutes | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
_GRECAPTCHA | 5 months 27 days | Google Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category. |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time. |
JSESSIONID | session | New Relic uses this cookie to store a session identifier so that New Relic can monitor session counts for an application. |
PHPSESSID | session | This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | Cloudflare set the cookie to support Cloudflare Bot Management. |
_icl_visitor_lang_js | 1 day | WPML sets this cookie to store the redirected language. |
drift_aid | 1 year 1 month 4 days | Drift sets this cookie as a session identifier token. It is used to tie the visitor on your website to a current website session within the Drift system. This enables session-specific features, such as popping up a message only once during a 30 minute session to prevent a disruptive experience. |
drift_campaign_refresh | 30 minutes | Drift sets this cookie as a unique ID for the specific user. This allows the website to target the user with relevant offers through its chat functionality. |
driftt_aid | 1 year 1 month 4 days | Drift sets this cookie as an anonymous identifier token. As people come onto the site, they will get this cookie. |
li_gc | 5 months 27 days | Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
wp-wpml_current_language | session | WordPress multilingual plugin sets this cookie to store the current language/language settings. |
wpml_browser_redirect_test | session | This cookie is set by WPML WordPress plugin and is used to test if cookies are enabled on the browser. |
Cookie | Duration | Description |
---|---|---|
__lotl | 5 months 27 days | Lucky Orange sets this cookie to identify the traffic source URL of the visitor's original referrer, if any. |
_lo_uid | 1 year 1 month 4 days | Lucky Orange sets this cookie as a unique identifier for the visitor. |
_lo_v | 1 year | Lucky Orange sets this cookie to identify the total number of visitor's visits. |
_lorid | 10 minutes | Lucky Orange sets this cookie to record the current ID of visitors. |
Cookie | Duration | Description |
---|---|---|
__hstc | 5 months 27 days | Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
_fbp | 3 months | Facebook sets this cookie to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising after visiting the website. |
_ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
_ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
_gcl_au | 3 months | Google Tag Manager sets the cookie to experiment advertisement efficiency of websites using their services. |
_gd_session | 4 hours | This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded. |
_gd_svisitor | 1 year 1 month 4 days | This cookie is set by the Google Analytics. This cookie is used for tracking the signup commissions via affiliate program. |
_gd_visitor | 1 year 1 month 4 days | This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads. |
AnalyticsSyncHistory | 1 month | Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie. |
CONSENT | 2 years | YouTube sets this cookie via embedded YouTube videos and registers anonymous statistical data. |
hubspotutk | 5 months 27 days | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
ifso_visit_counts | 1 year | If So sets this cookie to store number of visits. |
ln_or | 1 day | Linkedin sets this cookie to registers statistical data on users' behaviour on the website for internal analytics. |
vuid | 1 year 1 month 4 days | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. |
Cookie | Duration | Description |
---|---|---|
bcookie | 1 year | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs. |
bscookie | 1 year | LinkedIn sets this cookie to store performed actions on the website. |
li_sugr | 3 months | LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant. |
VISITOR_INFO1_LIVE | 5 months 27 days | YouTube sets this cookie to measure bandwidth, determining whether the user gets the new or old player interface. |
YSC | session | Youtube sets this cookie to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt-remote-device-id | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt.innertube::nextId | never | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
_an_uid | 7 days | No description available. |
_gd1687981540406 | session | Description is currently not available. |
6suuid | 1 year 1 month 4 days | No description available. |
ifso_page_visits | 1 year 1 month 4 days | No description available. |
oribi_cookie_test | session | Description is currently not available. |
oribili_user_guid | 1 year | Description is currently not available. |