https://emersonexchange365.com/community-hubs/valves-actuators-regulators/b/vcp-weblog/posts/turning-fuel-gas-conditioning-into-a-path-to-better-plant-performanceMon, 13 Jul 2026 01:00:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:7b74b21c-5052-4295-ba2c-f8a8a7fb4461Jim CahillCombined-cycle power plants pair gas turbines with a steam turbine to achieve roughly 60% overall efficiency, placing them among the most efficient large-scale generation technologies available today. Those gains depend entirely on precise fuel gas conditioning. The post Turning Fuel Gas Conditioning into a Path to Better Plant Performance appeared first on the Emerson Automation Experts blog.pressure regulatorValves, Actuators & RegulatorsAndrew PhangtartariniFisherHeeya Leehttps://emersonexchange365.com/worlds/south_korea/b/emerson-korea-blog/posts/2028-igc-2-in-1Sun, 12 Jul 2026 23:00:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:0a82f610-9dff-45b6-996e-067997405436Emerson South Korea Blog2028년 바뀌는 IGC 규정 대응법 |액화 가스 운반선을 위한 '2-in-1레이더 기술' 원문 : How ‘2-in-1’ Radar Technology Fulfills Requirement for Independent Tank Gauging and Safety Systems on Liquefied Gas Carriers 글쓴이: Mansa Pradhan 해상에서 액화가스를 운송하는 선박에는 특수 저장 탱크가 존재합니다. 그리고 이 탱크에는 탱크 게이징 시스템과 안전 시스템을 모두 장착해야 하죠. 특히 탱크 게이징 시스템은 재고 관리 및 상거래용으로서 지속적으로 액체 레벨을 측정해야 하며, 안전 시스템은 과충진을 방지하기 위한 알람이 함께 설치되어 있어야 합니다. 또한, 이러한 시스템은 국제해사기구(IMO)에서 정한 ‘액.......혁신 및 전문기술https://emersonexchange365.com/community-hubs/valves-actuators-regulators/b/vcp-weblog/posts/mastering-tank-pressure-practical-ways-to-reduce-risk-product-loss-and-emissionsFri, 10 Jul 2026 08:00:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:f7eb205f-22b6-43de-9f41-6b0ab6f07d84Jim CahillStorage tanks may look static, but pressure inside them is constantly changing. Filling, emptying, solar heating, rain cooling, vapor generation, inert gas supply, and connected recovery systems can all affect the pressure in the vapor space above the liquid. If those pressure changes are not managed, a tank can exceed its maximum allowable working pressure or fall below its maximum allowable working vacuum. The post Mastering Tank Pressure: Practical Ways to Reduce Risk, Product Loss, and Emissions appeared first on the Emerson Automation Experts blog.tank blanketingValves, Actuators & Regulatorspressure relief vacuum valveAnderson GreenwoodGerard Wittekoekpressure relief valvehttps://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11473/bypasses-and-simulations/25389Thu, 09 Jul 2026 15:15:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:f4e53ab7-24c6-4756-af0f-6d391122ec41Matt StonerCheck out this threadhttps://emersonexchange365.com/community-hubs/measurement-instrumentation/f/flow-discussions-questions/11468/suspected-production-shortfall-linked-to-test-separator/25388Thu, 09 Jul 2026 14:25:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:70a57fd1-d2ac-41b3-8eff-a14858c2e673Jared DrennenYou are correct that entrained gas will lower the mixture density, which results in an errantly high Oil Volume. However, Micro Motion's NOC software also includes built-in bubble-remediation capability to prevent this from happening when configured correctly. Please contact Flow.Support@Emerson.com (1-800-522-6277) to discuss your configuration and we will be happy to help optimize your production measurement.https://emersonexchange365.com/industries/power/b/power_-_blog/posts/ai-data-centers-are-rewriting-the-rules-of-power-infrastructureThu, 09 Jul 2026 12:25:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:9650e91d-1ffa-4a30-9112-7ce64608f45eJim CahillTL;DR AI data centers require far more power than traditional facilities. The electrical grid cannot yet support this scale or volatility. Onsite, islanded power systems are becoming the preferred approach. Project coordination is a major challenge across multiple suppliers. Automation providers play a key role in enabling speed-to-power. Why this matters now Many people are […] The post AI Data Centers Are Rewriting the Rules of Power Infrastructure appeared first on the Emerson Automation Experts blog.Data CentersOrchestrationgridEnergy InfrastructureEOPautomationAIBoundless Automationovationpower generationDeltaVAI Factoryhttps://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11473/bypasses-and-simulationsThu, 09 Jul 2026 12:15:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:7034bb06-cd5a-4acb-87a5-c3b905fe46e8B JohnsonLooking for ways to view all current bypasses and simulations in DeltaV version 15.https://emersonexchange365.com/industries/power/b/power_-_blog/posts/optimizing-power-plant-efficiency-with-pressure-relief-and-blowdown-valvesThu, 09 Jul 2026 03:30:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:8149179c-4826-4ca8-a1aa-4bb58664a656Jim CahillIn high-pressure, high-temperature service, small deviations in valve performance translate into measurable efficiency losses and safety risk. Code-compliant selection, proven design features, and factory-verified testing help operators avoid unplanned outages, extend maintenance intervals, and protect critical assets. The post Optimizing Power Plant Efficiency with Pressure Relief and Blowdown Valves appeared first on the Emerson Automation Experts blog.Balakrishnan BYarwayValves, Actuators & RegulatorsShaik Mohammad AliAnderson GreenwoodCrosbypower generationhttps://emersonexchange365.com/community-hubs/valves-actuators-regulators/b/vcp-weblog/posts/optimizing-power-plant-efficiency-with-pressure-relief-and-blowdown-valvesThu, 09 Jul 2026 03:30:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:5675921a-4105-43d9-b88c-2e3de2decd55Jim CahillIn high-pressure, high-temperature service, small deviations in valve performance translate into measurable efficiency losses and safety risk. Code-compliant selection, proven design features, and factory-verified testing help operators avoid unplanned outages, extend maintenance intervals, and protect critical assets. The post Optimizing Power Plant Efficiency with Pressure Relief and Blowdown Valves appeared first on the Emerson Automation Experts blog.Balakrishnan BYarwayValves, Actuators & RegulatorsShaik Mohammad AliAnderson GreenwoodCrosbypower generationhttps://emersonexchange365.com/worlds/south_korea/b/emerson-korea-blog/posts/oem-1367537705Wed, 08 Jul 2026 23:00:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:e62a00ff-9b76-46f0-bfa7-98b847c77282Emerson South Korea Blog원문 : Contributing to the Design of Energy‑Efficient, Robust Pyrolysis Plants at Scale Through Advanced Instrumentation 작성자 : Joanne Brooks-Kinder 최근 ‘고급 재활용(Advanced Recycling)’이 파일럿 프로젝트 단계를 넘어 유럽 전역의 산업 표준으로 자리 잡으면서 열분해 OEM의 중요성이 날로 높아지고 있습니다. 현재 관련 업계는 높은 에너지 효율성과 견고한 플랜트 설계, 그리고 안정적인 장기 운영을 보장함과 동시에 신속한 사업 확장을 달성해야 하는 복합적인 과제에 직면해 있습니다. 성공적인 공정 구현을 위해서는 개별 기기의 성능을 넘어, 고온의 가변적 공급 원료 공정의 특성을 깊이 이해하고 설계부터 배포까.......자동화솔루션https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11469/deltav-live---disable-evaluation-of-gems-online/25387Wed, 08 Jul 2026 18:49:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:a9bf6f90-6c56-48b7-97ef-d6b98431467bHugh BThanks Matt, This did achieve what I needed albeit it was a bit cumbersome to configure GEM overrides individually for all the components that would have bad status when no module tag is configured. For GEMs I am using the PCSD Gem package.https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11472/editing-values-of-alarm-prioritiesMon, 06 Jul 2026 20:06:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:a7e28ff5-65d0-46cc-b98b-afe05a6c07f8Mark BendeleWe assigned the wrong area sequence numbers or values to a couple of new alarm priorities. Now we are not able to edit their values. I'm talking about the values from 0 to 15 related to say log, advisory, warning and critical. Are we not able to edit because we have alarms configured with these alarm priorities? Also, can we delete the alarm priorities and recreate them with the right sequence numbers without causing problems other than a temporary loss of alarms? We have to do this work on-line then update, because we are not allowed to download. I'm wondering about deletion and re-creation, because we have reached the limit of the number of alarm priorities.https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11467/finding-where-a-given-gem-is-used-in-live/25386Mon, 06 Jul 2026 19:31:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:5fb6f202-7e52-4f2b-966d-b4473573a10eKentThanks! I think this is going to be manageable until we get moved to version 16. Your help has been greatly apricated.https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11467/finding-where-a-given-gem-is-used-in-live/25385Mon, 06 Jul 2026 19:25:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:329a577b-d2b3-40bd-ad1f-d778814da1acAndre DicaireIs it possible the is an issue in v14? I'd say yes. Lots of improvements in v16 for Live, especially in performance and such. You mention Event Viewer, which tells me that is where you see the OPC HDA messages. I was surprised when I found out Live used OPC HDA. Operate did not. why change it? but they did. Since it is transparent to the user, there was not much in BOL about that detail. We had some security issues with DCOM that impacted the OPC HDA connections, which is where I found OPC HDA messages in the event viewer. Anyway, it would be super useful to provide an example of the actual error message you are seeing. It helps to understand the lens with which you are seeing your issue. Bottom line, updating to v16 is your best path forward. If you still have issues, you will be at the latest version which will get the most attention. And if the issue has been addressed, you get the fix... Good luck.https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11467/finding-where-a-given-gem-is-used-in-live/25384Mon, 06 Jul 2026 17:34:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:e3e085c1-958c-4b64-8fe4-37fe08593013KentThanks again. We've been doing some experiments that could be shedding light on this. We turned off Live for one of the reactors with the error. The errors went away for that VM but another set of messages came up from a different reactor. We shut down Live on that reactor and the error messages stopped completely. We opened up a Live graphic for the first reactor where we had shut down Live but on a different VM and even opened faceplates on it. The errors did not come back. We are bringing Live back up on the other reactor in an orderly manner. Since we are working on version 14, is it possible that there was a glitch in that version where sometimes a faceplate opened and did not close properly and kept asking for the data? The only reason I noticed it was that I was in the Event Viewer troubleshooting another problem. At this moment, I'm not seeing the errors coming back. We're going to be upgrading to version 16 very soon so if the workaround is close and reopen Live more frequently, I can live with that as a workaround. I hope that his holds as a fix. Thanks again.https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11467/finding-where-a-given-gem-is-used-in-live/25383Mon, 06 Jul 2026 17:12:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:b32ed756-f720-4ef2-a3b3-73922442480aKent14LTShttps://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11467/finding-where-a-given-gem-is-used-in-live/25382Mon, 06 Jul 2026 16:04:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:8d6fd8d5-2a64-49f9-baed-b009726c15d8Andre DicaireBy the way, what version of DeltaV are you using?https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11467/finding-where-a-given-gem-is-used-in-live/25381Mon, 06 Jul 2026 16:02:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:4d0640eb-42ba-419f-b2e9-364da8833751Andre DicaireWhen you open a faceplate with a trend object, it opens a connection to the OPC HDA server of DVCH and asks for the constructed tag for history, which may or may not be there. It will then pull ongoing data from the Workstations local OPC server for that tag. That way, the trend works with or without history. The Trend does not ask the DVCH for history until it is re-initialized, so each time you open this faceplate from the GEM, the DVCH OPC HDA call is made. Can you post exactly where you see this message? Is it in a log, or in the Live Health monitor? Or is this in the Ejournal? You can also look at the Faceplate display and check how the Trend Gem is setup to confirm this is the same syntax of your OPC HDA error. Here is Emerson default EDC faceplate tha tuses the CD_FPTRN_3PEN_DC Gem. As you can see, it defines SP_D, PV_D and OUT_D for the parameters. Inside the GEM, the Trend is configured as With Gem.Tag coming from the "Dsp.Tag" and Gem.FB from "Dsp.Context1", the trend paths are resolved at run time when the faceplate opens. Interesting here is that SP_D and PV_D are set with the .STR qualifier, but OUT_D is not. This may explain why you don't see the OUT_D parameter as an error, and only see PV_D and SP_D. The .STR qualifier forces the comm layer to return the string rather than the integer value of the associated named set parameter. However, I'm not sure if this creates a discontinuity with DVCH where the configured path in history does not contain .STR. I saw an issue using the .NUM qualifier on an embedded trend, where history would not show for the tag, even though the tag was historized, but as a /PV.CV path. I removed .NUM and the trend started showing history data. There are many layers here to evaluate. I'd have to do testing to confirm if .STR is causing an issue. But fundamentally, trending SP_D, OUT_D and PV_D of a DC or EDC is not an effective use of your Historian licensing. I would consider trending only the OUT_D.CV. The SP_D is captured in Ejournal as User Change and any failed start or loss of confirm will generate an alarm and using an E-Chart in DeltaV will give you a history of abnormal conditions affecting the asset. One history tag allows the data to be viewed across the time line of the Chart, with all specific events listed in detail.https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11467/finding-where-a-given-gem-is-used-in-live/25380Mon, 06 Jul 2026 15:06:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:d2d0922d-0805-48a7-b273-f1047affc247KentThanks! This has been very puzzling. I'm going to try an experiment over this next weekend. The tags that are showing up in this error are all on workstations that are not used over the weekend. I'm going to try turning Live off on a few selected machines to see if the errors go away or at least switch to different tags on VMs that are running Live. Does the faceplate need to be open for the it to try to access the data? If the problem is somewhere in Live, am I correct in assuming that turning Live off would prevent the graphics used on that VM would no longer make those requests?https://emersonexchange365.com/community-hubs/deltav-community-connect/f/deltav-discussions-questions/11469/deltav-live---disable-evaluation-of-gems-online/25379Mon, 06 Jul 2026 14:56:00 GMTcd40bb2b-3d49-4868-939d-417119b40291:be00fb71-96b8-40de-80ee-f94491bdcb4eAndre DicaireWhy do you see errors when there is no physical unit in a specific position? Is it because the control module ends up with a Bad Status because there is no IO connected for that postion? DeltaV modules don't appear and disappear in the controllers, so your GEMs would still be bound to something. Would be good for you to explain this in more detail. The DeltaV LIve health check on open displays does flag references that have a Bad Status. If the module/parameter exists but its Status is now BAD, I'm thinking the Conditional Read may still return the bad status as the parameter does exist. I'm thinking that is a communication layer status error based on .CST. I'd have to do some testing to confirm. If the module/parameter exists but can be BAD but you don't care, perhaps adding the .NUM or .STR qualifiers to the path will allow Live to ignore the status. You would need to use a visibility expression to hide the "unused" location. Another approach might be to modify the parameter paths based on what location is currently available using a script, maybe a time script that can update periodically based on changing conditions. The GEM would then be modified to bind to the appropriate module or unit. so that it is adjusting the runtime references as needed. One Gem to rule them all. You could position the GEM on the display and indicate which unit it is bound to, but all its references would be made valid through the script. Hard to say what the best solution would be given sparse details on where the error is generated. You're only telling us where the error is appearing...