Company Setup Suggestions Precast Segment

1. Company Setup SuggestionsPrecast Segment

2. Agenda Settings and templates Backup Integration

3. Settings and templates: Options   Settings stored locally  Settings stored on server Settings stored in model folder

4. Local, stand-alone Workstation Approach  Settings stored locally

5. Workstations (No Server) Tekla Structures Licenses in this case will be dedicated to that machine only. Each machine will operate independent of each other and not rely on any server. Sharing of information assumed limited or not by network. In this type of system there is no multi-user environment setup, TS is used in single user mode. Easier to setup initially but then hard to maintain.

6. FIRM License service TEMPLATE MODEL TEMPLATE Workstations (No Server) Software & License Service are on same machine. Models and settings (including FIRM, TEMPLATE, etc..) are on same machine. Each machine has setup duplicated; easy to travel!

7. Addons Workstations (No Server) Each workstation is a stand-alone mirror of all setup and template files needed to work on projects. Keep “Addons” in a separate location (network drive) and synchronize to local machine after each Tekla Structures installation.

8. Workstations (No Server) • Pros • No network needed • For small companies may be ideal • Portability • Licensing set up easier • Cons • Settings have to be synchronized • Sharing models more difficult

9. Settings and templates: Options   Settings stored locally  Settings stored on server Settings stored in model folder Multiple Workstations (Server Firm & Template Folder )

10. Multiple Workstations (Server)  Settings stored on server License service Central server maintained by administrator or 3rd party Tekla models and settings can live on server Licenses are on server and “floating” for any computer on network.

11. License service FIRM TEMPLATE MODEL TEMPLATE Multiple Workstations (Server) Setup is centralized on Server including Firm, Template, Model Templates, etc… Tekla Structures License service runs on server Tekla Structures installed just on client machines Clients can borrow a license & duplicate Firm,Template etc

12. Multiple Workstations (Server) Cons: • Settings are all live. • Could change during a project which could cause problems • Settings must be saved with projects so that later you can replicate setup to open project the way it was detailed originally • Laptops can borrow a license, but would then also need to duplicate Firm, Template, and other server based settings or use VPN Pros: • Harder to setup initially but then easier to maintain • Multiuser possible

13. FIRM FIRM FIRM FIRM TEMPLATE TEMPLATE TEMPLATE TEMPLATE MODEL TEMPLATE MODEL TEMPLATE MODEL TEMPLATE MODEL TEMPLATE Multiple Workstations (Server) If you do not want your project self contained and prefer that all projects share same base of standards you can create settings folders and have each computer point to these folders.

14. Settings and templates: Options   Settings stored locally  Settings stored on server Settings stored in model folder Model Template Approach (Settings stored in model folder)

15. Model Templates  Architectural MODEL TEMPLATE Skanska MODEL TEMPLATE Settings stored in model folder Garage MODEL TEMPLATE MODEL TEMPLATE • The model templates should live on the server when possible • can be on local machine and backed up routinely • Everything stored in a model is the 1st source of all settings and information, this makes the model folder compact and portable. • You can have multiple model templates, categorized for the different types of jobs you do.

16. What’s in a model template? All templates for that type of job. All settings for that type of job (including save as files) All custom parts (embeds), connections, seams, and details for that type of job (job specific + standard) The job itself, drawings, notes, etc…

17. Model Templates Years later model is then self contained, no other settings to be loaded or template to be found. Templates will often change, yet you want to see the project as it was detailed, not with today’s setup. Easy to send to 3rd party for collaboration Easy to maintain. You are essentially maintaining one or a few standard models instead of many files in different locations. When you make new projects you use this “standard model” as a template thereby avoiding import/export and settings all together!

18. MODEL TEMPLATE MODEL TEMPLATE Model Templates Standards (embeds and settings) change. The model template(s) always have latest standards - easy to maintain. New standards can easily be migrated to template folders. Model templates are self-contained project templates. Used once at job initiation Template model and project model are no longer connected.

19. Model Template Setup Create a new, empty model Import the sketches you want that model to have Customize the profile and other catalogs as needed or import the catalog files (see help for extensions) Import the custom parts, seams, connection, and details you want that model to contain Customize the options and advanced options to suit Customize the catalog tree folder as needed Edit the TeklaStructuresModel.xml inside that model folder. Use MS Word to edit the file and change the <IsTemplate>TRUE<IsTemplate> tag. Make sure to make this file “Read Only” afterwards.

20. Model Template Setup Move the entire model folder to a save location on the server where other computers can read. Point other computers to this location using the advanced option: XS_MODEL_ TEMPLATE_DIRECTORY= “xxx” Set this in the user.ini on each computer or have each computer’s user.ini point to a server.ini When you start new projects, simply select the new model template from the drop down list.

21.   Settings stored locally  Settings stored on server Settings stored in model folder Settings and templates: Options

22. Agenda Settings and templates Backup Integration

23. Backup Suggestions Whichever method you choose… • Backup your work at least nightly • Keep a minimum 5 day backup of previous work • For highly customized components - backup separately in the form of uel files. • Back up all customized “Addon” or system files • Keep image copies (pdf, tiff, jpg) of all drawings submitted somewhere safe and backed up • Use a 3rd party utility or server backup system to automatically back up your important data (like ViceVersa)

24. Agenda Settings and templates Backup Integration

25. Integration • Tekla only one part of your companies software base • Precast working towards number of goals for integration

26. Integration – Process Management • Actively pursing links to

27. Over Simplified Precast Workflow BID Docs Award Approvals Release Engineering Engineering Estimation E drawings Shop drawings Production Shipping Erection Punchlist RFIs Tekla Structures Sales model Production Model E Drawings RFI tracking in 3D Shop drawings Project management BOM (rebar) Project management       Product list 3D views BOM/Product list Drawings Drawings Status Prelim Schedule Shop tickets Ticket status BOM Scheduling info RFI data Piece tracking info E.g. storage/Shipping/Erection Status Accurate Estimation Production module Scheduling Production module Production module

28. Integration – Location based Services (LBS)

29. Integration – Databases • .NET app for Version 14.1 possible to ‘export’ directly to SQL database

31. For More Information/References… Model Templates: • See Administrator’s Guide at the end of the V14.0 Release Notes. Firm and Template Folders: • Help > Project and firm folders • Help > Folder search order Customizing TS: • Help > Customizing Tekla Structures • Help > General