불확실한 세계에서의 가치, 그리고 안전성 추구 IHS CERAWeek의 창립 스폰서인 에머슨의 임원들은 올 해 열린 CERA Week 2016에 유수의 패널로서 참여하여 에너지에 대해 다양한 의견을 나누었습니다. CERAWeek 2016에서 에머슨의 사장 Ed Monser는Chevron의 Wesley Lohec, ERM의 Don Lloyd, 그리고 IHS 패널장인 Nilesh Dayal과 함께 현 경제 및 에너지 추세에 대한 운영 전략을 논의했습니다. 에머슨의 사장 에드몬저(Ed Monser, 왼쪽)와 CNBC의 브라이언 설리반(Brian Sullivan, 오른쪽) 글로벌 에너지 기업들은 운영상의 무결성을 유지하면서 건강, 안전 및 환경(HSE)을 고려한 결과를 창출할 의무가 있습니다. 오늘날의 모든 회사는 대부분.......
↧
Blog Post: 불확실한 세계에서의 가치, 그리고 안전성 추구
↧
Blog Post: Improving site safety with non-contacting radar
See how an aviation fuelling company increased site safety, optimised their fuel consumption and improved control of fuel flooding with Rosemount 5400 Non-Contacting Radar. View here http://bit.ly/21beNES
↧
↧
Blog Post: Improved Emissions and Lower Fuel Costs at RDM Blendecques
Italian recycled paperboard producer, Reno De Medici (RDM) Blendecques mill in Saint Omer, France had a big challenge to modernize a control system with a short time window during a planned shutdown. The control system managed two Heat Recovery Steam Generators (HRSGs) that produce steam for the process from two gas turbines and additional burners. Even more important was the need to reduce emissions by optimizing the combustion control. Optimizing combustion would also reduce the natural gas required to make steam. The cardboard production process requires large amounts of steam to achieve the desired humidity. Emerson’s Industrial Energy Management team, including Pete Makepeace , Jim Dunbar and Andrew Verdouw worked with the Emerson team in France, which had worked with the RDM team to develop the requirements specifications to address these challenges. From these specifications, the Industrial Energy consultants helped the RDM project team develop a plan and project execution timeline. Jim, based in the U.S., traveled to France to set up, configure, and train the operations team on the combustion solution . Pete, based in the UK, performed the internal and customer factory acceptance testing (FAT), and U.S.-based Andrew was brought into the project right before the FAT to perform start up and commissioning of the system. The schedule was extremely tight, but the team concluded the FAT at the mill and began the startup just 14 hours later. They started up the steam production process on time to meet the aggressive schedule for first production. This project’s successful execution truly represented an international collaboration among the Industrial Energy consulting team and mill staff. In addition, the combustion optimization solution reduced emissions more than was defined in the requirements. Improvements were also made to operational practices. For example, the boiler level that used to be manually controlled is now fully automated and adapts to load changes in the boiler. This results in better feed water stability, which in turn results in greater steam production stability. The combustion optimization solution reduced the excess oxygen by more than 50% in some cases, which not only reduced emissions, but also reduced the natural gas fuel consumption required to produce the steam. Overall combustion efficiency improved by 3%. These results paid back the project costs in under two years. The installed DeltaV system also provided more complete information across all the control rooms in the mill to allow for faster troubleshooting and improved collaboration among the mill staff. Looking forward more units and safety functions will be converted over to the DeltaV system and DeltaV SIS safety system to continue to improve the safety, reliability and efficiency of the operation. If you need to improve powerhouse performance, request a Powerhouse Energy Opportunity Survey or additional information from the Industrial Energy Management team . You can also connect and interact with other pulp & paper and industrial energy experts in the Pulp & Paper and Industrial Energy groups in the Emerson Exchange 365 community. Related Posts Optimize Energy Consumption with Additional Monitoring Improving HRSG Availability by Better Steam Temperature Control Effectively Managing Energy Consumption Controlling Combustion of Hydrogen Fuel Mixtures Reducing Plant Energy Consumption Industrial Energy Team Peels Reliability like Onion! The post Improved Emissions and Lower Fuel Costs at RDM Blendecques appeared first on the Emerson Process Experts blog.
↧
Forum Post: Can't communicate with Series 2700 Flow transmitter with HART communicator
Am having problems with the flow meter, and the faults point to check the test points with either a Hart communicator, or ProLink software. I have a hart 375 field communicator, but cannot get online with the transmitter. There are 3 other "working" transmitters in the panel, and I cannot get online with them either.
↧
Forum Post: DELTAV 12.3 MVIRTUAL & SVIRTUAL
HI my friends i have question about deltav 12.3 new feature in the adding new node.i just installed 12.3 and i want to know about Mvirtual and Svirtual in the node model as i said.what are they and what they do? thanks in advance.
↧
↧
Forum Post: RE: DELTAV 12.3 MVIRTUAL & SVIRTUAL
These two controller types are for the Virtual Machine controllers supported in a virtual host server. For offline development or Simulate multi Node systems, you can use virtual machine controllers and CIOC's instead of physical hardware. These show up in DeltaV Explorer like physical decommissioned devices that you assign to your controller place holders, and can download. There is a MiMiC SIO driver that allows the process simulation software to work with these virtual machine controllers as well. You can use VMware or Hyper-V to run virtual machines and connect these to our Offline DeltaV system. You can mix virtual machines and physical machines in an offline system, but typically, we use these for development of the system configuration, with all DeltaV nodes virtualized on a VM host. Very useful and much easier to manage than physical controllers.
↧
Forum Post: RE: Can't communicate with Series 2700 Flow transmitter with HART communicator
Hi PAB - I would recommend the first step would be to make sure the 375 communicator has the appropriate DDs loaded for the transmitter in question. Let me know if you need anything else.
↧
Forum Post: RE: Can't communicate with Series 2700 Flow transmitter with HART communicator
Hi PAB - I forgot to mention: here is a link to the DDs in case you want to view it - www2.emersonprocess.com/.../deviceinstallkitsearch.aspx
↧
Forum Post: RE: Can't communicate with Series 2700 Flow transmitter with HART communicator
Hi CWilmer-Thanks for the help!
↧
↧
Forum Post: faceplate help
Hi I am doubtful about modification on one of the faceplates,( EQM_FP faceplate). Please send me the original copy to compare. My Email: mohsenv@mail.ru Thanks
↧
Forum Post: RE: DELTAV 12.3 MVIRTUAL & SVIRTUAL
thank u for your response Andre Dicaire. what they need to work with? for example i add new mvirtual but deltav asked me that mvirtual needs license .
↧
Forum Post: Easy Security Agent installation in the deltav 11.3
hi my friends there is new software in the deltav 12.3 (Easy Security Agent) i want to know that is supported by 11.3 pro+ and other deltav workstations?
↧
Forum Post: Alarm Horn Retrigger
I am trying to see what the best approach is to retrigger the alarm horn after the operator has silenced it. As of now when an alarm comes in the operator hits the "up arrow" key, which we have a key macro to silence horn. Sometimes the alarm will go awhile before they even ack the alarm. So I was trying to figure out a way if they ignore this that after a period of time the horn will retrigger and go back off. I was looking at maybe a scheduler. I have tried it in a module just for that particular alarm by ack it through the code, and also disenabling it then reenalbing it but I am not sure that would be the correct way. I was looking for maybe a global way to do it. Anyone ever do anything like this?
↧
↧
Forum Post: diaphragm seal 1199
Hi I have one DP transmitter with diaphragm capillary seal, the ordering number for Seal is 1199DA356AFCS74VI00ZT . i try to find the detail configuration of ordering number, but in new document revision is meaningless. can you help me? the transmitter is built in 2000 (i think) Thanks
↧
Blog Post: 에머슨 프로세스 매니지먼트, 2016 컨트롤 매거진 독자 선정상(Readers’ Choice Awards) 수상!
에머슨 프로세스 매니지먼트, 2016 컨트롤 매거진 독자 선정상(Readers’ Choice Awards) 수상! 안전하고 효율적이면서 수준 높은 생산을 위해 자동화 시스템을 설계 및 설치하고, 유지하는 일은 상당한 능력을 요구합니다. 공정 제어의 기술과 기법을 제대로 파악하는 것뿐만 아니라 제조자의 원칙, 재정, 인원 등을 충분히 이해해야 하기 때문입니다. 그러나 자동화 전문가라고 해도, 플랜트 내부의 공정 제어 하드웨어부터 소프트웨어까지, 시스템의 모든 분야를 통달한다는 것은 쉽지 않은 일입니다. 때문에 각 부분에 맞는, 적합한 공급업체(Vendor)를 선택하는 것은 그 무엇보다 중요합니다. 이러한 의미에서 무척 의미 있다고 볼 수 있는.......
↧
Forum Post: RE: Alarm Horn Retrigger
Hi Bill, I have implemented this type of action at a customer site. In my approach, I built a composite that has as an input the parameter that you would alarm off of and as an output a parameter that the alarm is triggered from. Inside the composite I had the re-triggering timer logic. When the alarm is to be re-triggered, it drops the output for a scan and then re-sets it. The other method that I experimented with was using an Action block to set the .NALM field of the actual alarm to 0. The NALM field is the "New Unacknowledged" indicator for the alarm, and this would effectively re-trigger alarm as well. I looked through my notes to see why I went the first method I mentioned instead of the second, but I couldn't find a reason. I may have had an issue being able to write to the .NALM field in an Action block. Dave
↧
Forum Post: RE: Alarm Horn Retrigger
Caution: Although there may be value to retriggering the Alarm Horn, the first thing to do is identify if the alarm system is adequate. If alarms are properly designed, and operators trained, there should be little or no need to retrigger alarms. If the system is not performing properly due to too many alarms without consequence and Operator actions defined, adding additional Horn activations may simply contribute to more dysfunction within the handling of alarms. The challenge is to correctly identify those situations where a horn activation is warranted. Is this something the Operators are asking for? If not, would adding this capability accomplish anything, other than a periodic activation of the Horn Silence button? That said, are you wanting to remind the operator that there are unacknowledged alarms? Or are you trying to add logic to retrigger standing alarms to remind an operator that the alarm has not been cleared? Using HORN.F_CV Since the alarm horn sounds with each alarm that enters the Alarm List (If the alarm does not set the horn, is it really an alarm? and if you want this, the alarm should be auto acknowledged), then the only time you would need this feature is when there have been no new alarms for a period of time. So the pseudo code logic might be " IF (TopPriorityAlarm is Unacknowledge) and (Time since last Horn > X seconds) Then, Set the Horn parameter based on the Priority of the top unacknowledged alarm, Reset TimeSinceLastHorn endif The ALARMS parameter provides access to the Alarm List in a console, and the Time In value (TIN) may be useful. You may have to add an action in your macro key that resets the time since last horn parameter, and you may want to check the horn is actually active so Operators don't "learn" to reset this timer with habitual activation of the acknowledge button. The HORN.F_CV holds an integer that reflects the Alarm priority that set the HORN. Writing this value to 0 silences the HORN. Writing the appropriate number to the HORN.F_CV would set that priority sound. However, DeltaV documentation warns about manipulating this parameter from anywhere but the Alarm Banner. You are already doing so with a Macro Key script. I would recommend that you fully test the HORN parameter behavior to understand what values are written normally and what you should use if you do decide to affect this parameter. Note that this method does not affect the state of the alarms, so there would not be any record in the Event Chronicle that the Horn was reactivated. The downside is the Horn goes off but without a clear reason for the horn, it will become a nuisance. Using NALM: If the highest priority alarm is an acknowledged alarm, you could choose to write to the NALM, which would record an event as the alarm state would change. This would retrigger the Horn and require the Operator to re-acknowledge the alarm, and would record these events in the Journal. The alarm in the left most field of the Alarm Banner would change to Unacknowledged state. When there are no unacknowledged alarms, the highest priority Acknowledged alarm moves to the ALARM[1] position. If its TIN is > than X, you could reset its NALM. I'm not convinced this would be useful. Since we don't really know what the under lying issue you are trying to resolve, adding more alarm horn activations or retriggering alarms simply based on operator horn activity would not be my first choice. I encourage you to get input from your Operators as to what they need to improve their performance. Usually, the solution is a better performing alarm system, not more horn activations for no apparent reason.
↧
↧
Forum Post: RE: ProPlus Disaster Recovery
Hello Brian, Just wanted to let you know that we believe we were able to restore the Pro+ to a new hardware platform. 1.) Delete ghosted adapters 2.) Redefine existing adapters 3.) Reboot 4.) Restart DNS 5.) AD recovers on its own. 6.) Reboot 7.) Re-run workstation configuration. This forces a log-off log-on. However DeltaV services will not start. 8.) Reboot 9.) DeltaV services start normally on their own. 10.) Re-register Windows OS license. Thank you for your help. Per your suggestion, we will look more in to Emerson’s recommended solution for disaster recovery. This seems to be one area that Emerson does not advertise very well. Mr. Chris Williams – Controls Technology DAK Americas LLC, CA site
↧
Forum Post: RE: ProPlus Disaster Recovery
I am glad to hear that it all worked out for you! Thank you for coming back and letting us all know what the final solution ended up being. Brian
↧
Blog Post: Accurately Measure Process Temperature without a Thermowell or Process Penetration using Rosemount X-well Technology
In an earlier post, Online Calculation Tool for Thermowell Installations , we shared ways to avoid resonant frequencies caused by fluid flow around a thermowell inside of process piping. But what if you could eliminate the need for the thermowell entirely? I caught up with Emerson’s Ryan Leino who shared Rosemount X-well™ technology , which provides an accurate, repeatable, extrapolated process temperature measurement from a surface measurement. Just imagine being able to measure process temperature with no more leak points, no more process shutdowns due to maintaining thermowells, reduced design complexity which includes wake frequency calculations (WFCs) and more flexibility as project changes occur. Traditional thermowell installations introduce design complexity, installation expense and require ongoing maintenance. The required pipe penetration introduces a potential leak point and the thermowell is subject to corrosion, abrasion and bending stresses by the fluid flowing around it. Traditional surface sensors are one way you can go to avoid complexity and design issues associated with thermowells. However, this method gives you the temperature of the surface you are measuring, a value that does not provide an accurate or repeatable representation of an in-pipe process temperature. The new Rosemount X-well technology removes the challenges of a thermowell assembly while providing a process temperature measurement that a standard surface sensor cannot. From the chart, note the green Rosemount X-well line and how closely it tracks the process temperature as ambient temperature changes, especially in relation to the yellow surface temperature. The temperature of the process fluid is measured without the need for a process penetration or thermowell. This process temperature is calculated via a Rosemount X-well thermal conductivity algorithm in the Rosemount 648 wireless temperature transmitter and Rosemount 0085 pipe clamp and sensor assembly . Rosemount X-well technology works by measuring the ambient and pipe surface temperatures. These values combined with an understanding of the temperature measurement assembly’s thermal conductivity properties and information of the process pipe material and schedule provide the input for the calculations and extrapolations of the process fluid temperature inside the pipe. Ryan explained that Rosemount X-well accuracy is a function of ambient and process temperature differential. He shared several scenarios with me where the ambient temperature and the fluid inside the pipe were at various values. When process and ambient temperatures are similar, Rosemount X-well accuracy is approximately that of a traditional thermowell assembly. As process and ambient temperature diverge, Rosemount X-well accuracy becomes slightly less than that of traditional thermowell accuracy with a total probable error (TPE) less than 1.2% of process temperature reading at its most inaccurate level. Some good applications for the Rosemount X-well technology include: Pipeline monitoring Retrofit existing pipes that need new measurement points Pipelines requiring frequent cleaning High velocities Slurries and heavy particulate fluids Clean-In-Place (CIP) processes High viscosity fluids Harsh processes requiring exotic materials Wellhead monitoring And, unless the temperature measurement is part of a safety loop, custody transfer calculation or control loop, all pipeline temperature measurement applications are good candidates for the Rosemount X-well technology. Ryan indicated that the Rosemount X-well algorithm is currently available in the Rosemount 648 as a factory assembly with the 0085 pipe-clamp sensor. You can connect and interact with other temperature measurement experts in the Temperature group in the Emerson Exchange 365 community. Related Posts Fundamental Features Hidden Inside Your Temperature Transmitters RTD or Thermocouple for Temperature Measurement? Temperature Measurement Diagnostics Understanding Multivariable Transmitters Extending Measurement Device Stability to 15 Years Human Centered Design Improvements to Temperature Measurement The post Accurately Measure Process Temperature without a Thermowell or Process Penetration using Rosemount X-well Technology appeared first on the Emerson Process Experts blog.
↧