Showing posts with label Keynotes. Show all posts
Showing posts with label Keynotes. Show all posts

Thursday, February 27, 2020

Keynote Schedules Not Updating

I wrote a post in April last year when we were observing some projects that would not update their keynote schedules during printing.

When they issued 2018.3 that issue was reportedly resolved. Moving forward into 2019 and 2020 versions it seems true. However we've seen a few projects that seem to continue to exhibit the problem. Specifically a keynote schedule does not show all of the keynotes that are actually visible in views on the sheet.

With these troubled project files we can force a regeneration IF each sheet view is open during printing. Like before turning the annotation crop boundary off/on or on/off will cause a regeneration too. However printing is when it matters the most. More testing is required before I can be certain there is an ongoing issue in the more recent releases but these projects do exhibit the problem in more recent versions too.

The current solution is to open all the sheets that must print first and then print to PDF. Alternately open a sheet view and print and repeat for all required sheets. If all the views are open then the revision schedule regenerates (you can watch it happen). The sheet view does not have to have Revit's focus, just has to be open in the background at least. Any sheet views that are not open won't refresh.

Wednesday, April 24, 2019

Keynote Legends and Keynotes not Updating 2018.3

In Revit 2018.3.2.7 I am seeing and getting reports that keynote legends are not updating to show the current state of keynote tags visible in views. The existing workaround to force a refresh by turning on/off the Annotation Crop Boundary works but is entirely impractical to expect a team to open every sheet and do that task for each and every view on a sheet.

This past Knowledge Network post seems relevant. A portion of the text at that article suggests...

Workaround:
There are a few ways you could work around this behavior, and the best method will vary depending on the model geometry and number of affected tags. Here are a few options:

Temporary fixes (these will restore the display keynote tags, but future view changes will clear them again): 
Temporarily adjust the location of the Cut Plane so that is above the affected elements (this will restore the value to the tags) and then restore the original cut plane location. Note: Some customers have noted that for views with dependent views, this process is required:
  1. Open the parent view and adjust the cut plane upward.
  2. open all sheets containing dependent views belonging to this parent view to refresh the keynote tags.
  3. move the cut plane back to its original position in the parent view.
(Note: this may not work for some elements such as Duct; in that case, see the Non-temporary fix below.) Recreate the affected tags manually.

Non-temporary fix (This will prevent future changes to the view from clearing the keynote tag): Adjust view or elements so that the cut plane is above the affected elements. (This could be done with a Plan Region.)

We really need this fixed ASAP!!

Tuesday, August 18, 2015

KeyNotes - You Keep Using that Word...

A recent exchange went a little like this:
Them: "Steve! I need some help with my keynotes!" Me: "Okay, how are you doing them?" Them: "Huh? I just drag this family from the Project Browser and place it in the view. When I look at my keynote schedule I don't see the keynote being added."
When software uses the same word we routinely use to describe something we do it is supposed to make it easier to understand and use. Sometimes the opposite happens, as in this situation the word Keynote or the practice of key noting  (keynoting). A good many of us in the AEC business are familiar with the concept of using keynotes on drawings.
I find it interesting that I didn't find a definition readily available on the interwebs for what we do with and call keynotes. There were lots of trade specific sites but not the traditional dictionary or wiki version. Most refer to being the keynote speaker at an event or related to music.
Regardless, for us it is a system to reduce clutter on drawings by placing symbols that either carry numbers or letters or both to identify different conditions that we should look to a separate place (key, like a map key to symbols) to read more information. Ideally it means we get drawings that are cleaner looking instead of the clutter of long descriptions nestled among the graphics that describes the building itself. It's also a way to help reduce the chances of making spelling errors or stating things differently because more than one person is usually involved in the process of completing drawings.

In Revit there are three ways we can apply keynotes to drawings. First we have a formal tool called, not surprisingly, Keynote. Second we have an older slightly less formal technique using a Noteblock Schedule based on a Generic Annotation family. Third we have the old school approach where we use a Generic Annotation symbol and then separate Annotation (lines) and Text elements to provide the appearance of a formal schedule we are familiar with.

I've often referred to the Keynote feature as the rich man's keynotes because it requires ongoing rigor and advance planning/effort.


We have to manage an external keynote file (TXT) and use specific annotation tags that work with this external data. Our families can each store a keynote parameter value (which a tag reports) and we can create ad hoc User Keynotes too. Keynote Schedules can (a Filter option) display only those that appear in the views that are on each sheet, a distinct advantage over the other techniques.

In the image below I'm using a cool tool called Keynote Manager to review keynotes. We have to organize the information that we want to be available for keynoting ahead of time or at least be prepared to stop and start when we realize we are missing something. The external data and process is more formal and rigorous. That's why I've observed it is also poorly adopted.


When we combine this process with Keynote Legends on sheets we have a consistent and predictable structure for keynoting activity.

In contrast the Noteblock approach, which I've often called the poor man's keynotes, depends on data stored in specific Annotation Symbol families.


It does require some rigor but not quite as much as the formal Keynotes tool and there is no external TXT file that keeps the data consistent. When we create a Noteblock Schedule we have to choose the correct Annotation Family to base it on. Then the schedule reports how many instances of that annotation family (symbol) we place in views, that are then placed on sheets. These are much harder to filter so we only show those that relate to specific views on sheets, there is no built in feature to filter them.

The third approach is not really any different than how I've seen it done for many years with CAD and hand drafting before that.


We place symbols, change the number/letter and then later create a legend on the sheet that provides a summary of the keynote symbols we've placed in the drawing. We examine the drawing and make an entry for each symbol we observe on the drawing. It isn't hard to do but it isn't fun and very error prone, especially as the project progresses and changes occur.

Referring back to the exchange at the beginning of the post, it turns out that the technique that was being used was the last one, symbols, lines and text. It helps a lot to figure out which technique is being used before launching into helpful responses that assume either of the other two possibilities are in play.

Friday, February 13, 2015

Revising Keynote Data

When you use keynotes and realize you need to revise existing keynote information it easy to change what the keynote text value is. We just need to edit the existing information and reload the keynote file.


It's a little different situation when you decide you need to change the numbering that is already in play. It's no problem if you are just shuffling note information around so you get the numbering sequence you prefer. As long as the keynote value remains in the list Revit will find it. You just need to make sure that any elements that are supposed to carry a certain keynote value still do after you shuffle them.

However, if you revise things and introduce a new numbering scheme and reload the file you'll find the keynotes will get confused. They stop displaying the correct information. For example let's say the keynote that was number 1 is now the letter A. There isn't a separate GUID that is guiding this alignment of data, Revit is relying on the information in the text file entirely. So Revit doesn't find the number 1 anymore and can't pair up the keynote value and keynote text anymore. The tag just reports 1 since that's what was stored to begin with.

The best place to check and revise the keynote assignment after revising numbers is in the keynote legend. You'll be able to review each keynote and activate the keynote table via the Keynote Value parameter, the little browse button that appears when you click on the value in the schedule.


You can select each confused keynote and map it to the correct keynote value. Once you've revisited all of the affected keynotes in the legend you'll find that the keynote tags throughout the documentation will show the correct information again.

Monday, June 30, 2014

Easy Keynoter

Phillip Miller, the brains behind the Family Browser and Kiwi Custom Solutions has a new offering called "Easy Keynoter". Here's what his new site page for the product has to say:

Easy Keynoter for Autodesk Revit 2015 is not just another glorified keynote text file editor. Easy Keynoter can do that plus so much more. The main features of Easy Keynoter are:
  • Fully integrated into the Revit UI
  • All Keynote data stored within a Database. No reliance on Revit reading txt files or the need to have intermediary xml files. This means that there are no issues of multiple users editing the keynotes at the same time as with other systems.
  • Add Edit and remove keynote changes are reflected immediately in the Revit project. No need to manual Load/Reload operation from within the Revit UI
  • Drag and Drop Keynotes from the Palette directly onto Revit Elements to keynote those elements.
  • Super fast search function. Easy keynoter will display all search compliant keynotes in seconds. We have tested this on a keynote file with over 20,000 keynotes and the results displayed within 1 second.
  • Easily Import/Export your existing old Keynote.txt files into and out of the Database.
  • User management. Create user groups and assign who is allowed to add/edit/remove keynotes from the database.
  • One Revit power user that has seen this product commented. “Mate, looks absolutly awesome, bring it on.”

Looking forward to checking it out!

Monday, November 25, 2013

Keynotes By Keynote vs By Sheet

If the choice is a little confusing perhaps the following explanation will help a little?


By Keynote uses the number of the keynote based on your keynote file.


This means a sheet can show keynote value like: 101, 204, 302, 601 etc. These aren't "sequential" in that there are gaps between numbers based on keynotes that exist but not used in any views on the sheet. This can result in questions from a contractor like: "Are keynotes 102-203 missing?" This approach also works best when you really want a keynote "number" to be consistent with another reference document, like specifications (CSI numbers).

By Sheet requires the view with keynotes to be on a sheet to receive a number.


This allows keynote values visible on a sheet to be sequential, 1, 2, 3, 4 etc. If a keynote tag is empty then that view has not been placed on a sheet yet in order to determine what number it should receive. This also means that a keynote for Gypsum Wall Board may be numbered "3" on one sheet and "15" on another, all depending on how many other elements have keynotes applied. This approach reduces the likelihood that a contractor will ask about "missing" keynote values. This works best when it is more important to provide sequential numbering unique to each sheet.

Wednesday, May 22, 2013

Keynoting Sheets and Worksets

Ryan wrote a post yesterday at The Revit Clinic describing a couple scenarios that result in borrowing sheet views while keynoting views. These affect versions 2012 and 2013 in particular. If you've encountered some quirkiness on your project using keynotes it is worth a read. A subtle point made at the end of the post reveals that 2014 has been tweaked to help resolve these issues. Ryan wrote:
    For Revit 2014 keynote and revision functionality has been improved. Sheet view worksets are no longer borrowed during the same process, which should give larger project teams additional flexibility (especially during documentation-heavy project phases).

Btw, Ryan is also one of the author's of the Revit Essentials book I mentioned the other day.

Monday, August 13, 2012

A Case for User Keynotes

I wrote the following (April 2012) in a reply to a thread at RevitForum.org. It is one example of how a user keynote can be applied effectively to reuse instructions and avoid stating them differently in different places, as is easy to do with regular text elements.

Imagine a data receptacle plan. The data receptacles are essentially all the same (lets pretend they are all 2 drops) except for where they are installed. Some are mounted in a wall, some in a cabinet at a sales desk, some in a kiosk (free standing display), some are available for visitors to use and others are not. As far as a schedule to summarize them, then purchasing and installing them is concerned the faceplates and back boxes are potentially identical. To apply a keynote to define how they are different in use we'd have to consider separate families or separate types so we could get different keynote values.

If we create four or five unique keynote entries we can apply them to the data outlet according to their use as User Keynotes. The keynote legend would display the information for each condition on the sheet and/or in the master keynote legend. The same information could be displayed using a tag showing a custom instance parameter but not summarized in a list on the side of the sheet as easily. Nor could we avoid different values being entered by different people.

An example User Keynote might be:

"Kiosk mounted data receptacles are to be mounted at 12" above counter surface. Provide one extra run of CAT 6 cable without terminations, for future expansion."

The same device could also have a User Keynote that says:

"Data faceplate color selection must be coordinated with interior design final material and color selections with owner."

In the plan view we'd see one device and two keynote tags with different numbers adjacent to each other. If I needed to do the same thing for other receptacles I'd have to create new types every time I needed a keynote to say something even slightly different.

Keynotes as a practice is derived from the desire to reduce clutter on the sheet and reduce the chance of writing instructions differently on different sheets. Using types to control the information is still risky because we could type different information in different types and in different families. If we are going to supply instance parameter values routinely we run the risk of similar mistakes while trying to be consistent. Since User Keynotes are pulled from the same source, as long as we all click on the same keynote the information will be the same everywhere.

Wednesday, February 15, 2012

Keynotes - Files, Tags and Legends

Here are a few quirky "gotcha" items you can encounter when you get serious about using the keynoting tools.

If you apply User Keynotes and then change the number values (the Key Value parameter) for them in your keynote file they don't change in the Revit project to reflect the new numbers, even after you Reload the file. That strikes me as undesirable but I believe I understand why. There is no GUID to keep track of. I'm wrong, actually there is one, it's the Key Value parameter but it isn't effective as one. When you change it...Revit can no longer reference it in the project. In order for Revit to update the Key Value too there would need to be a separate GUID (that we can't change), so it could keep track of them.

When this happens Revit keeps the old value intact. You'll have to select the keynote tag and redirect it to the correct value. You can also type in the correct value in the Properties Palette. Yet another way to manage this issue (in a project) is to have a master User Keynote legend (drafting or legend view). Place an array of a small detail component (not grouped and associated though) and apply each User Keynote to them so you end up with one keynote for each unique one you plan to use throughout the project. This view serves as your master "fixer" view. You can go through them all in this one view and fix any that need to be updated. All the others that have been placed throughout the project will inherit the change...change in one place...changes it everywhere else, phew.
    Does that make sense? How or why would this even happen? Need a practical example? Let's say you create your own keynotes for architectural finishes that use the numbering scheme A200 and there are values that run from A201-225. You apply keynotes to a lot of stuff. During a design review the project manager decides that we should revise our existing A200 series to AW200 (wood finishes) and create a new AM200 series for metal finishes. Never question the pm :)

    When you renumber the A200 series and reload the keynote file into the project the existing numbers in the keynote tags don't change. If you click on the tag and then the keynote value Revit will open the keynote file but it won't expand the list to show it is associated with the correct keynote, you'll have to do that. As I mentioned before you can just select the keynote tag and in the properties palette type in the new value, inserting the new "W" in the number. That will fix it and when you open the keynote file to check it will work correctly. Not a big deal for one or two or ten. Hundreds is another story.
Another item is that keynotes will still show up in a legend (on the sheet) even if the item that has been tagged isn't visible in the view. For example, if you apply a keynote tag to an element and then use Visibility/Graphics to turn that category off, the keynote legend still sees the keynote tag...and it shows up in the list.

Yet another item is that keynote tags that are in Legend Views aren't included (selected) when you use the Select all Instances option In Entire project.


If, for some reason, you decide you want to use that to delete all the keynotes you won't get the ones in Legend views. You'll have to open those views to track down any refugees. If you want to test it out yourself just add some keynotes to elements in the project. Also add a keynote to something in a legend view. Go back to the other project view(s), right click on a keynote tag and use Select all Instances - In Entire Project, then Delete them. Now visit the project browser and try to delete the keynote tag there. You'll get an error message telling you there is still a keynote tag in the project, like this message.


Unsolicited plug, if you do anything with keynotes at all, are you using Steve Faust's Keynote Manager (Revolution Design)? Why not? I really can't imagine spending any time dealing with keynotes without it, seriously.


Seriously nice little application. I should mention it supports multi-user editing and it creates backup files. That saved me and my recent client some heartache a few weeks ago. A quick search of the backups and back in business we were.

Monday, April 04, 2011

Keynote Application Update

Steve Faust is getting the word out that he has updated the application he created to improve our interaction with Revit Keynoting feature. I wrote about his application back in April 2009. Time flies and version 10 has been released HERE.


Jay Zallan wrote up a nice piece about it today, check it out too!

Friday, March 25, 2011

InterSpec - e-SPECS 6.0 and Revit Keynotes

Conversation last night reminded me of the news release that I intended to mention here but never did. Do you wrestle with Revit's keynoting features? If so you might consider having a closer look at e-SPECS new Keynote features in the 6.0 release they announced this past January.


...snip
e-SPECS v6.0 includes new Keynoting Management at the master and project levels with intelligent assignment of coordinated keynotes to Revit families and materials directly through the e-SPECS Revit Plug-In Console.
...snip

From their Revit page...
...snip
-SPECS for Revit generates project specific keynotes coordinated with your specifications to ensure accuracy in detailing. Rather than have your detailers select from hundreds to thousands of master keynotes, e-SPECS generates the list of only those used in your BIM project. In addition, e-SPECS for Revit generates automatic Outline Reports and a specification Table of Contents. These facilitate a design process ensuring the highest quality product is produced without the error prone and mundane manual efforts previously required without e-SPECS.

You can WATCH a ONLINE Demo if interested.

Thursday, April 23, 2009

Keynote Editor = New Cool Application

I must have been sleeping under a rock when this one surfaced back on March 13, 2009 in a POST at AUGI. Steve Faust with emc2 has made a Keynote Manager application whose goal is improving the lot of the person(s) who deals with Revit's keynote feature. Here's a screen capture.


You can download the FILE HERE!

Friday, June 27, 2008

School of Hard Knocks - Keynotes and Linked Files

A client email and subsequent phone call yesterday advised me that they were "butting their heads into a wall" using the Keynote Feature with the linked files. Scott Davis, with Autodesk, was able to respond to them earlier than me because I was preoccupied elsewhere, thanks for being so responsive Scott!

The bottom line is that it is not possible to generate a keynote legend that includes elements in a linked file. I assume that this is because a keynote legend is able to "sense" what keynotes are in use on a sheet's views and generate the list of keynotes accordingly. I therefore assume that the linked file does not communicate this information to the host project. The only indication that this won't work or isn't possible is that the "Include Elements in Linked Files" check box is disabled in the schedule properties dialog.

The suggested workaround is to generate the relevant keynote legend in the linked file itself and then either capture the result as an image or dwg export which can be added to a view in the host project. Alternatively this documentation should/could, if possible, be done soley in the linked file instead. Unfortunately the manner in which clients link files together varies and it may not be a reasonable suggestion.

The request/issue has been logged with support accordingly but if this is a concern for your firm too it would serve all of us if you share your concern with support as well.