Fieldbus Part 2

1 of 2 < 1 | 2 View on one page

Genzyme Corp. recently installed a multi-bus control system platform at its 12-year-old pharmaceutical facility in Allston, Mass. This was our first introduction to bus technology at Genzyme, and our subsequent selection of bus technologies was based on the process equipment needs within a cell-culture and protein-purification manufacturing environment. Bus technology is used in process areas electrically rated General Purpose and Class 1, Div. 2.

Part 1 of this article ("Tales from the Front: Applying Fieldbus at Genzyme, Part 1"), focused on why Genzyme decided to use fieldbus, how and where it was deployed, and what architecture was used. Part 2 continues coverage of how Genzyme’s fieldbus segments were designed.

The buses selected included powered buses Foundation fieldbus (FF) and AS-i, while the unpowered buses are Profibus-DP and DeviceNet. The goal was to have the stick-built process equipment use an identical segment design. This allowed us to develop segment design standards that were followed by our engineering design contractor and the skid vendors.

In the third picture in Figure 1 (p. 34), you can see green modules near the bottom of the panel. These are discrete I/O modules that are attached to the AS-i segment in this cabinet enclosure. Transfer panel proximity switches are hardwired from the transfer panel location to these modules. There was a concern about not exceeding the AS-i bus segment length, and so the segment length was minimized by placing the I/O modules in the field termination box (FTB) and not at the individual transfer panels. Today, this may not be a concern because segment length is less restrictive with AS-i segment tuners, which didn’t exist when our project was implemented.

It’s typical in biopharmaceutical facilities to use portable equipment for more than one process unit, such as a bioreactor, because of the clean-in-place (CIP) process, which requires manual setup with transfer panels and hoses to ready a process unit for cleaning. The cleaning process is highly automated, with sequencing of various piping flow paths done by manipulating open/close diaphragm valves. Cleaning bioreactor units requires a portable valve cart (Figure 2, p. 35) to be hose-connected manually to various process piping headers on the bioreactor. This particular cart includes five automated diaphragm valves that are part of an AS-i segment. The AS-i protocol immediately recognizes these valves by their unique addresses. The single bus connection represents five discrete outputs for the valve actuator solenoids and 10 discrete inputs for the open/close limits for each valve. If this weren’t a bus design, then we may have had to wire 15 cable pairs or 30 conductors to a larger portable connector.

Unpowered Buses

Profibus-DP and DeviceNet involve very straightforward wiring practices. They both follow a multi-drop wiring or daisy-chain wiring schema.

Wired in a similar fashion to each device is the required 24-VDC power supply. As mentioned earlier, DeviceNet is used to interface variable-speed and single-speed motors. Our motor-control center is scattered about the facility and tends to serve more than one process unit. For example, two bioreactors and one seed reactor have all their respective motors in the same motor-control center (MCC). To maintain independent process units, three separate DeviceNet trunks feed this MCC, including one from each of the two bioreactor trains’ controllers and one from the seed reactor controller. Since each unit has its own separate controller, it follows that the MCC interface should be unique for each.

Fieldbus in Hazardous Settings

Most of our purification space is classified as Class 1, Div. 2, Group C and D. Our first introduction to fieldbus was in the cell-culture side of the facility, and this space is electrically rated as General Purpose. Moving segment designs already in place for general-purpose areas into an electrically classified environment required changing which buses we would employ from those used in cell culture. Immediately, AS-i wasn’t appropriate due to its high power levels. However, FF can be used in a Class 1, Div. 2 electrical environment and in a Class 1, Div. 1 space.

Added to the market at the time of our implementation was FF’s Fieldbus Intrinsically Safe Concept (FISCO). It has many desirable attributes, such as eliminating the requirement for entity parameter calculations. It also requires less documentation to develop and maintain; instruments can be added later to the segment without the need for further segment analysis; and higher power levels allow more devices per segment. Before FISCO, segment-device count usually couldn’t exceed four devices for an Entity IS segment, but the count could be as high as 12 with FISCO.

Because it was new, our design presented a concern regarding the availability of field devices certified for a FISCO implementation. We found that all the devices we used on the cell-culture side of the facility that would be used in purification were FISCO-certified, and so we could continue to use the same suppliers and devices. Though the FISCO implementation is designed for a Class 1, Div. 1 electrical environment and our space classification is Class 1, Div. 2, we decided to pursue the FISCO design because it meant that all segment and device maintenance and troubleshooting could be accomplished with a powered segment or device.

Shortly after FISCO was introduced, another non-incendive design appeared. This Fieldbus Non-Incendive Concept (FNICO) is intended specifically for Class 1, Div. 2 electrical environments. There was a comfort level in the facility with intrinsically safe (IS) implementation, which ensures that facilities personnel never have to think about powering down instrumentation prior to performing maintenance or troubleshooting.

1 of 2 < 1 | 2 View on one page
Show Comments
Hide Comments

Join the discussion

We welcome your thoughtful comments.
All comments will display your user name.

Want to participate in the discussion?

Register for free

Log in for complete access.

Comments

No one has commented on this page yet.

RSS feed for comments on this page | RSS feed for all comments