Bentleys Content Options

Compound Cells are stored as individual models within a BXC file.  They are static cells (not parametric) that are able to store 3D Geometry, 2D Symbols (for simplified drawing graphics), and Perforators (for cutting forms, slabs, or solids when placed).  These are basically cells with enhancements to support the needs of BIM that CAD did not require.  

Parametric Frame Builder (BXF) and Parametric Cell Studio (PAZ/PAC) are both parametric engines that can do a lot of the same things.  Most people believe that you can create content much quicker with Frame Builder, but you are able to create more complex parametric geometries using PC Studio.  PAZ & PAC are both file types from PC Studio, the only difference is that the PAZ file format is generated when you publish the PAC which compresses some of the data of the PAC.  

HTH,

Travis

It might seem confusing to a newcomer, but some of these different formats are due to the history of the product development. One of Bentley's strong commitments is to not drop support for past formats so that you should always be able to open and modify previous projects. This is a good thing I believe. As for your question about the different formats, here is my understanding as a long term user of Bentley's Architectural products.

Cel - up to version 7 this was a different file format. In V8, a Cel file is just a different extension for a dgn file. It is no different to any other dgn with multiple models. Perhaps the only other factor is the models need to have the toggle for being able to be placed as cells, but the file format is no different to a V8 dgn file.

PAC and PAZ are the same thing exept that the PAZ is a compacted (or Published) version of the PAC file. When you make an object in PC Studio there are often things left in the file that are unnecessary so when you "publish" the PAC file it become a PAZ in name only, but the process strips out any unnecessary elements so the parametric cell is as small as possible - assuming you might use many of these in your model. PCStudio is best used for relatively simple framed parametric objects. The modeling tools are pretty basic. For framed objects it can do some pretty good things, but it can take a lot of time to develop a single cell. I would avoid it for one-off objects as it isn't worth the time - unless you have nothing better to do. If you have parametric objects that you will use multiple times over multiple projects, then it is well worth developing these in PCStudio, especially for things that are not handled by the PFB (see later description of that).

BXC is the format for a Compound cell library. This was developed by the original developers of an external product which Bentley bought and has since been called Triforma and then Bentley Architecture and will become AECOsim as you mentioned. Compound cells are best used for Static non-parametric  objects, but can also contain "Frames" from the Parametric Frame builder, although I tend to keep those separate as BXF files. A lot of people like to build standard sized doors with standard solids or forms as compound cells mainly because the are, essentially non-parametric. It just means you need a different cell for each size and can prevent easy modification of the door size once it is in the model - which some people like.

BXF - So this is for "frames" created by the older Parametric Frame Builder (PFB) - a much maligned (wrongly IMO) and misunderstood tool that also came from the original developers pre-Bentley. The BXF file is just a text recipe file which contains the parameters and commands that the PFB reads in order to replicate the object. It can be used for creating Windows and doors along with other objects such as joinery. The key to the PFB is understanding that it uses a settings file to control the default elements sizes, parts, etc.  When you understand it, it is far easier and much, much quicker  to use for simple doors and windows than PCStudio, though you have to be happy with the simplified construction of those objects as well. I happen to like the PFB, but I have been working with it a long time and understand it's place.

TRS I am not familiar with. Similarly with GC, which I know is parametrics on steriods - and you really need something significantly parametric to make it worth learning. But by all means go for it and have fun if you have the need, the time and/or the inclination.

As well as this you also have basic Parametric (& non parametric) solids as a part of core Microstation.

When you work with these tools long enough you get a feel for how to do things the best way, and this might simply be forgoing any of the framing or parametric tools and just modelling the objects which you can move and stretch as you would other geometry.

But perhaps of most importance, if your client is asking for Bentley BIM, then you probably need to find out what their preference is as far as parametric objects, cells etc., is, and work to that. From an archival and file transfer point of view it might be that the more simple the model, the better.

TRS is a Roof Truss Settings File...old school.

WOW, thank you Steve, and as usual, Travis….

Unfortunately the client does not know exactly what they want, they just know they use Microstation and they want “BIM”. I think we finally have a good handle on the change in workflow(dynamic views and such), now were moving on to content. Myself and another colleague are tasked with developing/converting our Autodesk (Revit) content to Bentley BIM where needed. The basic building content in Bentley BIM is there OTB, doors, windows, etc. It’s just all the custom equipment and such that we will have to recreate.

Ill fess up and confess (as Travis already knows) I’m coming from a Revit background trying to learn Bentley BIM. I’m used to working in a very dynamic 3d modeling content creation environment and regardless of how basic or complicated, I used the same environment. here is a small sample of the type of content I’m going to need to recreate. Some of them are Static but most of them have minor differences between models that need to be reflected. Ideally, I want them to be dynamic so I don’t have to maintain 6 different models for one piece of equipment for only a couple inches difference. If its easier to use compound cells, I’ll do what I have to….

I figured if push came to shove, I could insert our existing content into its naive format files and convert to DGN. I could then take the converted content and make them Cells or something.

here is an example i tried yesterday, the top one is obviously PCS and the bottom one is the original in Revit. I was able to do it but it, took me all day. i probably should have just done it as a BXC? This is one were the width will change up to 24" depending on the model, along with a couple other variations (I’m still working getting that to work) :-).

I’m pretty sure I didn’t make it optimally.... but I’m still learning.....