Plant 3d Model
Derrick Drescher
A plant in control theory is the combination of process and actuator. A plant is often referred to with a transfer function(commonly in the s-domain) which indicates the relation between an input signal and the output signal of a system without feedback, commonly determined by physical properties of the system. An example would be an actuator with its transfer of the input of the actuator to its physical displacement. In a system with feedback, the plant still has the same transfer function, but a control unit and a feedback loop (with their respective transfer functions) are added to the system.
Plant modeling is the process of creating a digital replica of every process, piece of equipment, and workflow within a plant. Process manufacturing plants are already fully equipped with sensors which gather data from every inch of the system; with plant modeling, engineers draw on that data to build an accurate representation of everything that takes place within the system and constantly update it in real-time.
Plant modeling is the foundation for many applications of industry 4.0, such as digital twins, predictive monitoring, integrated systems, and remote troubleshooting and repair. A digital twin is essentially a fully modeled plant with the addition of constantly updated process data.
Plant models are also used for plant design, with engineers producing a trustworthy model of the plant alongside the design process. This way, they can identify any issues with the structure of the plant, view the impact of design decisions on human traffic flow and employee activities, and check that every element within the plant can interact effectively and efficiently. Any problems can be spotted and rectified before construction begins.
There are a number of different approaches to plant modeling, including 2D modeling and 3D modeling. Plant models are becoming increasingly complex, but the more complicated the model, the harder it can be to validate the conclusions it draws. Simple models can be powerful and effective.
Plant modeling can enable process plants to take advantage of cutting-edge technology like digital twins, smart glasses, and advanced analytics, thereby boosting plant productivity, efficiency, and profitability while reducing costs, increasing throughput, and extending your competitive edge.
We use cookies so that we can continually improve our web site and its design. A cookie is a small piece of text data that our web site saves on your device. By continuing to use our website, you agree to our cookie policy. More information
The site is secure.
The ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.
Proximity labeling is a powerful approach for detecting protein-protein interactions. Most proximity labeling techniques use a promiscuous biotin ligase or a peroxidase fused to a protein of interest, enabling the covalent biotin labeling of proteins and subsequent capture and identification of interacting and neighboring proteins without the need for the protein complex to remain intact. To date, only a few studies have reported on the use of proximity labeling in plants. Here, we present the results of a systematic study applying a variety of biotin-based proximity labeling approaches in several plant systems using various conditions and bait proteins. We show that TurboID is the most promiscuous variant in several plant model systems and establish protocols that combine mass spectrometry-based analysis with harsh extraction and washing conditions. We demonstrate the applicability of TurboID in capturing membrane-associated protein interactomes using Lotus japonicus symbiotically active receptor kinases as a test case. We further benchmark the efficiency of various promiscuous biotin ligases in comparison with one-step affinity purification approaches. We identified both known and novel interactors of the endocytic TPLATE complex. We furthermore present a straightforward strategy to identify both nonbiotinylated and biotinylated peptides in a single experimental setup. Finally, we provide initial evidence that our approach has the potential to suggest structural information of protein complexes.
I'm trying to model a chiller plant (two cooling towers, three chillers ((staged)) and multiple pumps) that serves multiple buildings. I am doing a trial run for one building, but am having trouble coming up with the best way to tackle modeling the system. I am using SketchUp/openstudio.
My first instinct was to build the plant, which I will replicate into a model for each building, then attach the "demand side" system on a building and zone level. Is this the best way to go about this type of model? if so I am a little confused as to what components (besides those mentioned above) are mandatory for the model to run? I am also a confused as to which node to place the components on. example: should all three chillers go on the same line on nodes that are horizontal to one another or on separate lines that are vertical from one another?
A common approach to modeling central plants is to do your building-level modeling in separate models, then output the hourly cooling loads to individual profiles that are fed into a separate central plant model. These cooling load profiles can be added to secondary chilled water loops that represent each building in the central plant model. The downside to this approach is that the building model and the plant model are not connected, so any changes to the building model means that you have to update the profiles that are being fed into the plant model, though this is pretty easy to do and does not pose a significant inconvenience.
As to whether your chillers should be connected in parallel (what I assume you mean by "horizontal") or series (what I assume you mean by "vertical"), I can say that most chiller plants will have chillers connected in parallel, so that they can be staged on and off depending on the load, and can include a low-load chiller. However, I have heard that series configurations can be very efficient in some applications and increase the available chiller capacity. If you wan to go with a "typical" configuration, though, use parallel.
As for the chiller connections, I was referring to the node placement within the "HVAC Systems" tab of open studio. The software does make some decisions for you by arranging the equipment but the placement isn't always the same. I have attached a screen shot of the layout that I have currently to the original question.
I agree 100% with Anna's load profile comments. I have used this approach recently to show that serial chillers can indeed be more efficient than parallel chillers (within the limitations of EnergyPlus' Chiller:Electric:EIR model).
On the screenshot of the plant you attached, I must say, I have never seen this arrangement before, Normally, the chillers are put in one plant loop (Loop Type Cooling), and the cooling towers are put in another plant loop (Loop Type Condenser). Also, it seems yo have too many pumps, some of which may in fact bypass chillers and towers altogether.
If I were to rearrange the loops to match your description, would the cooling towers be on the supply side in one loop and the chillers on the demand side, then in the second loop the chillers on the supply side and the cooling coil on the demand side? or would they be completely separated? I am still a little confused as to how the hierarchy of the system structure works in open studio.
You got it. The Condenser loop has the towers on the supply side and the chillers on the demand side. The Cooling loop has the chillers on the supply side and the cooling coils on the demand side. The condenser pump is typically on the outlet side of the towers, the cooling pump is typically on the inlet side of the chillers, But there are never pumps in parallel with the towers or chillers.
Often engineers will use a separate software to model the plant to be able to better capture system operation and control. You can also refer to the engineering documentation for EnergyPlus and implement the same chiller and cooling tower logic in a spreadsheet with known loads and weather data. I would recommend this approach if you have many large buildings.
However, if you have many small buildings all part of the same project, it is possible to model this directly in the OpenStudio. If you use this approach, I recommend reading the OpenStudio tutorial on creating HVAC system plant loops to get an idea of how your setup should look.
Chilled water loop - you have chillers on the supply side and cooling coils on the demand side. The little circle icons above and below the chiller indicate that it is attached to another loop (the condenser loop). Clicking the circle will bring you to the condenser loop:
If you want to control the sequence of the chillers and cooling towers in a specific way, you need to specify that in your model. See these recent questions on the forum: Sequential load distribution scheme seems not working and Optimal operation of plant chillers (EnergyPlus).
Thanks for the clear and thorough response! If I model each building served by the central plant individually using district heating and cooling as a "place holder" will I be able to combine the models into one and add the central plant and remove the district heating and cooling once all the models are finished and working properly.
No. You could combine the geometries, but you would need to remake the HVAC systems. Whether you split them depends on your use case. I've modeled several buildings together when all I was doing was looking at glazing options vs. plant size. For other projects doing central plant design with different ages of existing buildings and new buildings, I've modeled the plant separately.
The Plant model is one of the first conductance-based models developedto explain the mechanism underlying parabolic bursting oscillations observed in themembrane potential of the R15 pacemakerneuron from the abdominal ganglion of the mollusk Aplysia.
c80f0f1006