VicoOffice April ReleaseNotes 2016support.vicosoftware.com/FlareFiles/Content/Release Notes/R5.3/Vico... · Tekla. Whendoingso,theywillprovideyouwiththe‘object.inp’filethatitcanbedroppedinto

Vico Office

Release Notes

April

2016

Vico Office R5.3 Release Notes

Page 2

Table of Contents

Vico Office R5.3 Release Notes 1

The Golden Rule of Upgrades - Back up all existing projects 1

Previous version files 1

Disk cleanup precautions 1

Anti-virus software 1

Installation 2

Networking 2

Administrative rights 2

The versant database 2

BIM connections 2

Trimble Solution Improvement 2

Feature Additions 3

Improved Product Stability 3

Tekla 2016 3

Info Filters 3

Defect Resolutions 5

3D View 5

Cost Planner 5

LBS Manager 5

Model register 6

Publisher / Importer 6

Report editor 6

Schedule planner 7

Takeoff manager 7

Vico Office client 8

VPS 8

Page 3

Known Issues 9

Cost explorer 9

Derived Elements 9

Document controller 9

Report Designer 9

Publishers 12

ArchiCAD 12

ArchiCAD and Revit 12

Revit 13

SketchUp 13

Tekla 13

Takeoff manager 14

Vico Project Server (vps) 14

Winest integration 14

Trimble GC/CM Division, Support Services 15


Copyright 2016 by Trimble Navigation, Ltd Page 1


Welcome to Vico Office! These notes include detailed insight for users upgrading to Vico Office R5.3.You will find details about new functions, fixed functions, known issues and best practices for usingthe program. This document should be read and understood by all users of Vico

The Golden Rule of Upgrades - Back up all existing projects

It is fundamentally important that all existing projects get backed up before upgrading to a new install-ation of Vico Office. Deployment environments can vary greatly and the safest way to mitigate anydata loss occurring during an upgrade is to back up all of your projects before any new installation ofVico Office.

Previous version files

All models that are part of projects that were created prior to Vico Office R4.0 have been deactivatedto apply a quantity calculation improvement. This applies to all projects located on the Vico ProjectServer. Models created in these earlier versions of Vico Office need to be reactivated after opening theproject for the first time.

Disk cleanup precautions

When running standard Windows Disk Cleanup, or other similar applications to free up disk space, it isalmost certain that all .log files will be deleted from your system. While most Windows .log files areexpendable, the Versant database logs are not!

Permanently deleting them from your systemwill destroy your Vico Office projects.

Anti-virus software

Some Anti-Virus software blocks or slows down the communication between Vico Office and the VicoProject Server. Exceptions should be added to the Anti-Virus software settings to prevent this – seethe Vico Office Installation Guide for these settings.


Page 2

Installation

Networking

IMPORTANT: When you use Vico Office in a configuration with separate server and client, make surethat both server and client(s) systems are updated to the latest version of Vico Office.

Administrative rights

Installation of Vico Office requires administrator rights and elevated access rights in cases where UserAccount Controls (UAC) are enabled; UACs may need to be modified, or turned off, via the ControlPanel.

When installing Vico Office while connected to a network domain, the UAC settings may be differentfrom an offline profile, which can result in changed hardware identification characteristics. Thechanged hardware characteristics may result in a “no valid license found” message. Reinstalling yourlicense will solve this issue.

The versant database

Versant is the backend database used to store and interact with information inside of the Vico ProjectServer (VPS). Most local installations of Vico Office will see a folder for the c:\Versant directory storedonto their machine for project storage. The project server can also be installed across a LAN for com-munal project access. See the installation guide for more details.

BIM connections

In some cases, the installer is unable to detect the folder in which ArchiCad, AutoCAD, Revit and Teklawas installed on your computer. If this happens, the Office installer allows for selecting the foldermanually. All required files will be copied to the specified folder.

Trimble Solution Improvement

When running the installation wizard, you are encouraged to participate in the 'Trimble SolutionImprovement' program.

When you select 'Yes', a crash report is automatically sent to Trimble. Only necessary informationrequired by developers to help them understand why a crash occurred is included in the report.

When you select 'No', a crash report is NOT automatically sent to Trimble. However, you can send thisreport manually. A prompt will be available on the UI after the crash has occurred.



Feature Additions

Improved Product Stability

Countless testing hours have been performed on numerous scenarios to capture memory and processintensive areas. Armed with a thorough understanding of these scenarios, significant enhancementswere made to improve stability throughout the application.

Tekla 2016

Tekla Structures 2016 is now supported in this release of Vico Office. For a list of supported publishers,see 'Supported Publishers and Importers' in the Vico Office Installation Guide.

Info Filters

The Info column on the Takeoff Manager and Takeoff Pad displays information and warning icons thatprovide additional information for each takeoff item. Using the new filter option, you can now easilyidentify which takeoff items need to be addressed.

You can choose from the list of available filters:

Or you can customize your own:

a. Select > (Custom).

b. Enter the filter criteria. Click to add additional criteria. Click to remove it.

c. Click Apply.


Page 4

Note: Select >(Clear all Filters) to remove any applied filter.



Defect Resolutions

3D View

Description Reference

A customer reported an issue where an imported Revit model appearedsegmented. When the Revit model was exported to IFC and then re-importedto Vico, the issue was resolved.

D-13275 TSR-1205281

Addressed a customer-specific issue where Vico Office crashed when tryingto open the 3D view. This issue was specific to one customer and aworkaround solution has been provided.

D-13572 TSR-1225971

Cost Planner


Different quantities were reported whether or not an LBS existed. This issuewas resolved in R5.2 MR1. However, to view the correct quantities, the modelmust be republished.

D-13189 TSR-1198698TSR-1204507

After activating and then deactivating components, the Min and Max UnitCosts were removed. This issue has been resolved.

D-13150 TSR-1196404

Clarified how the Formula Editor resolves Takeoff Quantities. The formularesult for the component is the sumof the location-based results for all theselected locations in the Formula Editor dialog.

D-13155 TSR-1181169

Resolved a customer-specific issue where Tasks that were linked to Cost Plancomponents had Quantities of '0'.

D-13568 TSR-1225091

LBS Manager


Quantity variances were reported at the project level when there is an LBSpresent. This issue has been resolved.

D-13318 TSR-1209354

After setting up the LBS structure, elements assigned to a 'Project' level hada zero Source Quantity. This issue has been resolved.

D-13381 TSR-1213621

An issue occurred where LBS splitting resulted in incorrect Takeoff quantitiesand zero quantities at Cost Plan. This issue was resolved after ensuring thatthe 'Project' node was fully checked (not grayed out) beforedeactivating/activating the model.

D-13484 TSR-1219533TSR-1223813

After setting up LBS zones, some Revit Floor elements did not split, thusresulting in incorrect quantities per location. This issue has been resolved byusing the 'Reset Shape' tool on all the Floors in Revit, and then re-publishingand re-activating the model.

D-13063 TSR-1192488


Page 6


Clarified why ArchiCAD Slab Edge Perimeter did not split in LBS. Slab EdgePerimeter quantity cannot be split; therefore, its entire value went to a singlelocation, which is its dominant location.

D-12933 TSR-1173156

Model register


Resolved an issue where a Sketchup model that was created with Sketchupversion 2016 could not be imported into Vico Office. Version 2016 was notsupported in the previous Vico Office release. However, support for Sketchup2016 is now available in this release of Vico Office R5.3.

D-13142 TSR-1196066TSR-1212115

Publisher / Importer


Clarified some confusion as to why 'Rooms' were not published fromRevit. Topublish rooms with filtered content, ensure that the 'Publish Revit rooms'check box is selected and the 'Publish only filtered content' check box iscleared.

D-13402 TSR-1212754

An error appeared when publishing a model from Revit 2016 to a projectserver located on the network. This issue has been resolved.

D-13253 TSR-1202255TSR-1207269

The 'Volume' and 'Tread Surface Area' from a Vectorworks IFC 'stair' elementwere not calculated correctly. This was due to how stairs were modeled.When modeled, they consisted of two pieces, whereas in Vico Office, theywere handled as one piece. This issue has been resolved.

D-12639

D-12605

TSR-0940500

TSR-0940444

Report editor


Resolved an issue where the Add-Ons in Reports were not calculatedproperly.

D-13140 TSR-1193852



Schedule planner


In Vico Office R5.2, the autosave function saved the backup file to theSchedule Planner Standard installation folder (C:\Program Files\VicoSoftware\Schedule Planner Standard) as '~Untitled.dpp'. Users without fullpermission to this folder received an error message stating that the backupfile could not be saved. This issue has been resolved by reverting to how VicoOffice backed up files prior to R5.2 . Backup files are now saved to the samefolder fromwhere the project dpp is opened. The backed up names are thesame as the project dpp file and prefixed with '~'.

D-13426 TSR-1219200TSR-1210055TSR-1210055

After entering the Actual Completion Date while in the Current mode, theCurrent Start Time was the same as the Current End Time. This preventedusers from comparing the baseline approved programwith the current one.This issue has been resolved.

D-13462 TSR-1216821

Resolved an issue where the Microsoft Excel Import function from SchedulePlanner was not working

D-06820 TSR-1201050TSR-1209731

Takeoff manager


Using Section Tools or Reference Planes to perform a Quantity Takeoff on a3Dmodel in the Takeoff Pad view, and then zooming in to view the model,caused Vico Office to crash. This issue has been resolved.

D-12885 TSR-1201456TSR-1198318TSR-1172191TSR-1169574TSR-1168724TSR-0916819TSR-1212033

A structural opening cut, which is used in Revit to cut a beam into irregularshapes, was no longer recognized in Vico Office. This caused the originalshape of beam to appear and increase its quantity. This issue has beenresolved.

D-13277 TSR-1201072

Joined geometry created in Revit was becoming 'unjoined' in Vico Office, thus,causing an increase in beamquantities. This issue has been resolved.

D-13333 TSR-1201072

Resolved a customer-specific issue where the floor of a project had theincorrect Gross Volume Quantities. To view the changes, re-publish themodel.

D-13055 TSR-1190061

Resolved a customer-specific ArchiCAD model that had missing quantities intheir Takeoff Items.

D-12832 TSR-1062140

Resolved an issue where Revit Slab Concrete volumes were calculatedincorrectly.

D-12606 TSR-0934302


Page 8

Vico Office client


Resolved a customer-specific project that could not be unpacked afterupdating it from R5.1 to R5.2 MR1.

D-13386 TSR-1211160

VPS


Resolved an issue where the 'VPSDaemon' service was missing afterinstalling/upgrading Vico Project Server.

D-13526 TSR-0846393TSR-0847300



Known Issues

Cost explorer

Only elements from the active model versions will be isolated or highlighted in the 3D View when select-ing a node representation of a Cost Version within the Cost Explorer view.

Derived Elements

l Derived elements are not always displaying perfectly when interacting with Running Modes andwithin LBS manager (e.g., elements may not appear in the expected location, or elements withstrange face displays may not be selectable). Derived elements exist when project locations areadded and a new representation of a partial element is needed to display the location-basedportion of an element. Please contact Technical Support if you experience this problem.

Document controller

l Some PDF font types may appear incorrectly (e.g., incorrect character spacing, missing char-acters, or replaced characters) when imported into Document Controller. We have tested mostcommon font types; however, some outliers may still exist. Please contact Technical Supportteam if you encounter such occurrences so that we can add support for your font type.

Report Designer

l Calculated fields that have custom tag values may not appear in a report when Print previewed.There are two ways to ensure that they appear in your reports: (D-13464)

o Change the Data Source for your calculated field to "none".

o Add calculated fields using the CalculateField Collection Editor.

1. Create a Tag (in this example, name it "Subcontractor") and assign it Values.

2. Edit the report template. The Report Designer is displayed.

3. On the Field List tab, right-click on Components > Edit Calculated Fields.


Page 10

4. On the CalculatedField Collection Editor dialog box, click Add.

5. Select the Data Member.



6. Select the expression for this calculated field.


Page 12

7. Choose the created tag value and click OK.

8. Bind this calculated field to a report and preview it.

Publishers

ArchiCAD

l Composite ArchiCADwall elements may show a different area selection to what might be auto-matically expected at the corner of walls. This is due to a change in how ArchiCAD now classifiesends and sides of walls. Quantities should be reviewed and the painting tool should be used ifdeemed necessary by the user to facilitate required quantities.

ArchiCAD and Revit

l Composite element wall or slab layers cannot currently be quantified fromRevit or ArchiCAD.Provisions have been made to deploy the best possible results via the current API availability. Ifquantities and/or TOI composition are not desirable when coming in from these systems, usersare advised to work out custom formulas (via TOM/TOP/CP) to come up with their own cal-culations that reflect their preferred takeoff of such composite elements.



Revit

l Modifying Sub Elements of Revit slabs to create sloping areas where the slab has inconsistentthicknesses (e.g., top surface modified with slopes and the bottom left flat) can occasionallycause incorrect volume calculations.

l Revit models that are linked together and published into Vico Office do not always behavepredictably. In some cases, linked models do not respect the filtering constraints that were puton the publishing view and can result in undesired outputs and/or duplicate quantities. Usersare advised to remove the link between files and publish them separately.

SketchUp

l SketchUp does not store reference information in the same way as some other BIM authoringapplications, thus making it harder for Vico Office to provide some quantity types coming fromSketchUp. Also, some element type classification are not currently being read well. The newOnscreen Takeoff tools should help to supplement any occurrences of missing quantities, andelement types can be manually reassigned in TOM to address this. We are working with theSketchUp teamon a regular basis to resolve this.

Tekla

l Tekla content created and managed in the latest release using the ‘organizer’ tool may not beread correctly by Vico Office. When this happens, users may find that the element type recog-nition in TOM does not behave as expected. To resolve this, users can go into TOM and changethe elements to the desired type inside of Vico Office, or they can manage the classificationsmanually in Tekla.


Page 14

Please contact our technical support team if you wish to classify the elements manually inside ofTekla. When doing so, they will provide you with the ‘object.inp’ file that it can be dropped intoyour Tekla dataset. Doing so will automate the creation of ‘Vico 01, 02, 03 and Vico object type’inside of the Tekla classification tool. For more information, see our Knowledge Base articlesavailable on Vico Office SupportLink.

Takeoff manager

l Each release of Vico Office brings with it improved quantity calculations, as well as support fornew CAD applications. As such, the calculated values for takeoff quantities (TOQs) can changefrom release to release. The changes can be a result of how elements are quantified by Vico,how locations are derived by Vico, or how bodies are generated by the authoring application. Vico Office does not force the reactivation of models with each new release, however it isstrongly advised the users reactivate in each new release to take full advantage of the latestand greatest calculation methods.

Vico Project Server (vps)

Projects that are restored using only the VPSA backup command, rather than the packing func-tionality, cannot be properly updated into newer (R5.0) versions of Vico Office. To avoid this problem,users should rely on the packing functionality to preserve their historical projects, rather than simplyreplying on the VPSA backups.

Winest integration

The WinEst Integration utility must be reinstalled after Vico Office. This is because VOmay overwritethe default layout.xml information and the integration becomes unusable. A simple reinstallation ofthe connector will rectify the problem.



Trimble GC/CM Division, Support ServicesTrimble GC/CM Division Support Services is committed to offering timely, thorough, and efficient res-olutions to your installation and operation issues in accordance with your Trimble Support Contract.

To receive the best support possible, be sure to review the Trimble Support Services Handbook.

You can contact Trimble GC/CM Division, Support Services by:

l Email: [email protected]

l Internet: http://support.vicosoftware.com

The Trimble SupportLink includes a technical knowledge base, answers to frequently asked questions,technical documentation, and a form to submit specific support requests 24 hours a day, 365 days ayear.

https://docs.google.com/a/trimble.com/file/d/0B16ijxZiSTMMbDkycGVHQmtZX0k/edit

mailto:[email protected]

http://support.vicosoftware.com/

Documents

VicoOffice April ReleaseNotes 2016support.vicosoftware.com/FlareFiles/Content/Release Notes/R5.3/Vico... · Tekla. Whendoingso,theywillprovideyouwiththe‘object.inp’filethatitcanbedroppedinto