ArchiCAD Archive Files: let’s talk about the .PLA

ArchiCAD Archive Files: let’s talk about the .PLA
ArchiCAD Archive

If you don’t load your libraries or are missing objects, you’ll see a dot wherever there is a missing part. Even one dot is too many.

If you use ArchiCAD, which presumably readers of this blog do (or soon will), then you’ve created a .PLN file before. This is like saying water is wet, or that videos showing how to model a TIE Fighter in ArchiCAD are mesmerizing. Quite simply, a .PLN file is the standard ArchiCAD file format. Unless we are working off the BIM Server, we are unconsciously working with .PLN files daily.

But the .PLN is not the only ArchiCAD file. We also have .BPN files (backup files), .TPL files (template files), .GSM files (object files), .LCF (library container files), plus a ton of ever more obscure file types, which we can talk about another time.  See the full list of file types here. Teaser: Do you know what a .2DL file is? Know of anyone who has created one? In addition to all those file types, there is also the wonderful .PLA file: the ArchiCAD Archive file type.

a .PLN without any objects lacks value.

a .PLN without any objects lacks value.

When you create a .PLA file, ArchiCAD saves all library parts, linked images and textures associated with the project. The Archive file type stores the critical information in one compact location. This is super useful for several reasons.

  1. If your file is missing linked objects and libraries your file will be covered in dots (what ArchiCAD turns missing objects into).
  2. If your file is missing linked objects and libraries your 3D views will be devoid of windows, doors, textures, and much else.
  3. Firms change where old libraries and old files are located so files can’t always automatically find the libraries they need (resulting in broken and lost links).
  4. Firms lose old libraries or forget to keep them on company servers when upgrading hardware and software (because the people upgrading don’t know that the ancient files are still needed).
  5. Firms (especially in the olden days) might have deleted old “unused” libraries to save hard drive space. This is 100% unnecessary today with our giant hard drives.
  6. New employees who need to open old projects don’t know where to look for old libraries.
  7. Files migrate from one computer to another, and even from one company to another.
  8. The list goes on and on…
ArchiCAD PLA

A .PLA with all the objects looks correct.

With some good BIM management practices and our essentially infinitely large hard drives that are progressively getting cheaper and cheaper, many of the above reasons can be easily mitigated. Nothing should be deleted, libraries should be stored in a central location forever, etc. This means for backup purposes, where I once very diligently saved all my projects to .PLA at the end of their life cycle and stored a copy on a burned CD in an off-site location, now I feel a little differently. In my opinion, it is better to save everything, keep the projects as .PLN files (though saved up to new versions periodically), never move the files, keep the old libraries (ArchiCAD libraries and company libraries for each version of ArchiCAD you’ve ever used) in a logical, clear, and visible location, and then have a robust local and cloud backup. By the way, for each new version of ArchiCAD you should make a new version of your company library (so have an ArchiCAD 16 Company Library, an ArchiCAD 17 Company Library, etc.). If you just keep adding to your company library instead of making a copy for each new version, the library will become bulky and harder to use with old (and new) files.

BIM is Object Driven

ArchiCAD Archive

Options when saving an archive file

Now that I’ve explained why I don’t save .PLA files for archive purposes anymore, let’s look at why the .PLA is still VERY important to know about and use. While I rarely use the .PLA file type to archive my old projects, I still do regularly use it (and ask for it) when I’m sharing projects—whether giving a client a copy of their project or sharing information with other ArchiCAD users. The critical thing about a .PLA file is that it embeds all the necessary data for a project. As should be drilled into your brain amidst all our BIM talk, BIM is object driven; sharing or storing a BIM file (ArchiCAD or otherwise) and not having the objects makes the file pretty much useless. Saving an Archive file is a great way to make sure all the pertinent data is centralized and connected. A .PLA file is self-contained and whole.

If you are interested in Freelancing or Training (on either end of either equation), a .PLA file is the most important thing to be able to share and look at. When I am involved in freelancing or training, I want to see .PLA files. They give a complete picture of what’s going on. Even if someone is sending me a project using the latest version of ArchiCAD, I still want to see a .PLA because everyone uses extra data and objects not in the standard ArchiCAD library. Or as we’ve discussed elsewhere, there is more than one ArchiCAD version and Library, so my standard library might not be your standard library. There’s always something missing from .PLN files that are shared. Always. And even if there’s nothing missing, I don’t know that for sure (I prefer to avoid unknown unknowns). A .PLA, however, is complete. It contains all the used Objects. It can be trusted (better). One can argue that BIM is primarily about better communication and collaboration during the design and construction process. A .PLA file is critical to clear understanding when the conversation is between non-BIM Server based ArchiCAD users.

ArchiCAD PLAWhat I ask for when taking over someone else’s work: .PLN (to work from), .PLA (to verify I have everything), custom libraries (to link to), and a .PDF set (to verify everything looks the way my partners think it should).

Some helpful links and posts:

One more reason you should ask for .PLA files. It’s a test. Ask for a .PLA file and if you don’t get it, then you know one of two things: either the person you’re talking to isn’t listening to all the details you’re asking for, or they don’t know ArchiCAD as well as they think. Either way, good information to know.

2 Comments

  1. Jared, good post.
    Not convinced about not saving PLA files for backup, but I get your point: If all libraries are intact, good. Except the file might travel elsewhere in the future, and then what do you do?
    Another point that needs a mention is that the PLA does NOT save everything: The sad exception is macro objects called by custom objects embedded in the file. I have found this out the hard way, so if I DropBox a PLA to someone I have to make sure they also have my folder of macros to load as a library so all my cupboard doors, handles, faucets etc. show up.

    Reply
  2. Daniel, very true. Great counterpoint. And I did not know about the macro object issue. That is a great addition to this post.

    I think either way .PLA or no .PLA, accessing old files is about good management. I guess with my views on saving all old data, probably the best solution is to keep both the final .PLN and save out a .PLA. That way you have the benefits of both. And it probably makes sense to make a simple text file with project close out info. Like “X was the last user, libraries used are X,Y, and Z, etc.” That’d be a cool bonus feature to saving out a .PLA. Half formed thought…

    Reply

Submit a Comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>