company setup suggestions precast segment

Company Setup Suggestions

Precast Segment

Agenda

Settings and templatesBackupIntegration

Settings and templates: Options

Settings stored on server

Settings stored in model folder

Settings stored locally


Local, stand-alone Workstation Approach

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.

• 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!


License service

• 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.


• 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






Multiple Workstations (ServerFirm & Template Folder )

Multiple Workstations (Server)

• 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.

License service


• 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


Licenseservice

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 VPNPros:• Harder to setup initially but then easier to maintain• Multiuser possible


• 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.






Model Template Approach (Settings stored in model folder)

Model Templates• 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.


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…

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!

• 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.

Model Templates

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.

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.

Agenda


Backup SuggestionsWhichever 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)

Agenda


Integration• Tekla only one part of your companies

software base• Precast working towards number of

goals for integration

Integration – Process Management

• Actively pursing links to

BID Docs

Estimation

Engineering

Award

E drawings Shop drawings

Approvals

Production Erection Punchlist

Engineering

Release

RFIs

Shipping

Sales model

Product list3D views

Accurate Estimation

Production ModelE Drawings

RFI tracking in 3D

BOM/Product list

DrawingsDrawings

StatusPrelim

Schedule

Production moduleScheduling

RFI data

Shop drawingsProject management

BOM (rebar)

Shop ticketsTicket status

BOM

Production module

Scheduling

info

Production module

Project management

Piece tracking infoE.g. storage/Shipping/Erection Status

Tekla Structures

Over Simplified Precast Workflow

Integration – Location based Services (LBS)

Integration – Databases • .NET app for Version 14.1 possible to

‘export’ directly to SQL database

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

company setup suggestions precast segment

Documents