Tracking Changes in BSD

Log Out | Topics | Search Moderators | Register | Edit Profile

Author Message Dewayne Dean Senior Member Username: ddean Post Number: 8 Registered: 02-2016 Posted on Thursday, February 25, 2016 - 10:49 am:    For you BSD users, how do you track changes? Sheldon Wolfe Senior Member Username: sheldon_wolfe Post Number: 901 Registered: 01-2003 Posted on Thursday, February 25, 2016 - 11:52 am:    Unless I'm missing something, this is one of SL's big shortcomings. I export the affected files to Word, make the changes in SL, export the changed files to Word, then use Word's Compare Documents to show the changes. BSD support suggested saving a copy of a project for each addendum or other modification, making changes in the new copy, then using SL's Compare Projects to show the changes. Which is fine if you don't have many changes, but with the usual number of addenda and changes during construction, it means a lot of copying projects and extracting affected sections. Dewayne Dean Senior Member Username: ddean Post Number: 10 Registered: 02-2016 Posted on Thursday, February 25, 2016 - 12:16 pm:    Thanks Sheldon. Being new to Spec Writing and BSD, I wasn't sure if I had missed something. Seems like a hassle either way. Richard Gonser AIA CSI CCCA SCIP Senior Member Username: rich_gonser Post Number: 119 Registered: 11-2008 Posted on Thursday, February 25, 2016 - 12:23 pm:    I do exactly the same as Sheldon. This method allows you to backtrack prior addenda or revisions. Additionally, you can collect just the changes and issue those as a package. Given how we have multiple consultants, many don't use SL. This method allows for those consultants that are clueless in marking revisions. Each Word version of the changes are labeled with track changes and a note in the footer indicating the addenda. I tag the file name with "- ADD xx" or something similar. In the SL TOC, on the right side, I add the addenda noted with the changes. As the addenda/revisions build up, the latest version is still known within SL. I also use compare changes with the TOC to highlight and flag the content of a particular release. It's much faster and clearer than re-writing the change content. Sheldon Wolfe Senior Member Username: sheldon_wolfe Post Number: 902 Registered: 01-2003 Posted on Thursday, February 25, 2016 - 12:56 pm:    Occasionally, when exporting a file, I get a file name like this: 07-2100 plainrtlchaf1afs18alang0abltrchf1fs18lang0langnp0langfe0langfenp0b THERMAL INSULATION.pdf Dewayne Dean Senior Member Username: ddean Post Number: 11 Registered: 02-2016 Posted on Thursday, February 25, 2016 - 01:27 pm:    Does BSD give you "plainrtlchaf1afs18alang0abltrchf1fs18lang0langnp0langfe0langfenp0b" or is this how you track changes? Richard Gonser AIA CSI CCCA SCIP Senior Member Username: rich_gonser Post Number: 120 Registered: 11-2008 Posted on Thursday, February 25, 2016 - 01:42 pm:    This sounds like something is pointed wrong in your file name settings in the print menu. I'd have to say check that first then call tech support. Sheldon Wolfe Senior Member Username: sheldon_wolfe Post Number: 903 Registered: 01-2003 Posted on Thursday, February 25, 2016 - 01:58 pm:    If it happened all the time, I would agree, but it happens only occasionally. I've contacted support several times. They have no idea why it happens. Richard Gonser AIA CSI CCCA SCIP Senior Member Username: rich_gonser Post Number: 121 Registered: 11-2008 Posted on Thursday, February 25, 2016 - 02:18 pm:    There is a big update pending anytime now. So maybe that will allow the problem to just get behind us. Sheldon Wolfe Senior Member Username: sheldon_wolfe Post Number: 904 Registered: 01-2003 Posted on Thursday, February 25, 2016 - 02:38 pm:    Sorry, Dewayne, I changed tracks; the weird filename had nothing to do with tracking changes. The strange text is not unique to that section, but has appeared in filenames for several different sections. Dewayne Dean Senior Member Username: ddean Post Number: 13 Registered: 02-2016 Posted on Thursday, February 25, 2016 - 03:00 pm:    No problem. I was somewhat enamored with BSD when just starting out. Now, not so much. How many of the posters here use BSD? Gary Berlin, AIA, LEED AP CSI Advanced Member Username: burnsmcdonnell Post Number: 5 Registered: 02-2014 Posted on Thursday, February 25, 2016 - 04:03 pm:    Every specification writing tool (SpecsIntact,e-Spec, Masterworks/Word Docs, etc.) has "pros" and "cons." SpecLink is by no means perfect but, in my opinion, the "pros" outweigh the "cons" and the software and content has only gotten better since I started using it 5 years ago. Plus one for being a SpecLink-e user Gary Berlin, AIA, LEED AP BD+C, CSI Specifications Manager Burns & McDonnell :: Quality Assurance Tom Gilmore, NCARB, CCS, CCCA Senior Member Username: tgilmore Post Number: 46 Registered: 04-2007 Posted on Saturday, February 27, 2016 - 02:44 pm:    I don't think using the software to track changes has ever been very effective either in Masterspec or Speclink. In Word the page's print area shrinks to make room for the tags. For tracking changes to be truly effective, it requires identifying every change by date and occasion (ADD# or CCD#), and I'm unaware of any software that can make that more automated. Having been a Speclink user since 1997, I agree with Gary. During construction I believe reissuing whole sections and tracking changes should be an add service, especially when the change is not the result of an error by the Architect. Chris Grimm, CSI, CCS, SCIP, LEED AP BD+C Senior Member Username: chris_grimm_ccs_scip Post Number: 350 Registered: 02-2014 Posted on Sunday, February 28, 2016 - 11:23 am:    Tom, the way you suggest for tracked changes to display in Word is not hard. It will take a few minutes to set up the first time, and can be left on or toggled instantly thereafter. It varies by version but you go to the settings for how tracked changes are displayed. I generally set mine to Balloons: Never, and a couple other tweaks that I prefer. Once you are familiar, you can even record macros of whatever view settings you like for tracked changes and other view settings like editor notes (hidden text) in a full-blown view with everything you want to see while editing the specs, and another view with only the final print items visible. Then assign keystrokes to those macros and/or put in quick access toolbar (or any toolbar if you use old old Word which is still way faster than everything 2007+). Another way is by using e-SPECS which has track changes built in already working the way you suggest, and has Normal View, Page View, Final Draft View to pick from using toolbar buttons or menus. Scott Piper Senior Member Username: spiper Post Number: 28 Registered: 08-2014 Posted on Monday, February 29, 2016 - 09:53 am:    We use BSD/Speclink-e in our office. We are happy with the program and we have stuck with it for over 15 years. We have always tracked addenda changes separate from construction changes. Our projects tend to be fairly small so tracking the addenda changes to the spec is typically not very complex but our method might not work for larger and more complex projects. Typically we will make addenda revisions to spec sections in SL and then export the changes to a pdf. We first copy the entire section to preserve the original bid document, then we make modifications to the spec in the new section. Change the section name to include "Addendum #X" in the title, use the strike-through function to delete any text that no longer applies, add text or even entire paragraphs to include new information. We then export the file to a pdf and highlight the new language in the pdf before issuing the addenda. This method has worked well for us and has been well received by the bidders. Dewayne Dean Senior Member Username: ddean Post Number: 24 Registered: 02-2016 Posted on Monday, February 29, 2016 - 10:33 am:    Thanks for all the comments. I am going to try Scott's method and see how it goes.